Jerry, I guess you did not get my problem.
Let me rephrase my question, why do we need a P-Associsted-URI with wmpty list ??? And other problem is whatz the ABNF syntax for defining zero or more number of P-Associated-URI header values... (similar to zero or more header parameters...) It would be similar to specifying the zero or more parameters of any header, but if whole header could be NULL, how do we specify in ABNF syntax definition? I feel what is been mentioned in RFC looks to be one or more NOT zero or more..... Thanks & Regards, Nataraju A.B. -----Original Message----- From: King Jeremy [mailto:[EMAIL PROTECTED] Sent: Saturday, January 21, 2006 10:36 AM To: Nataraju A B Cc: [email protected] Subject: Re: [Sip-implementors] doubt/bug with RFC-3455 Nataraju, Comments inline ... Regards, Jerry > ------------------------------ > > Message: 2 > Date: Fri, 20 Jan 2006 11:56:43 +0530 > From: "Nataraju A B" <[EMAIL PROTECTED]> > Subject: [Sip-implementors] doubt/bug with RFC-3455 > To: <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="us-ascii" > > Hi All, > > I have a doubt in the rfc 3455 with respect to P-Associated-URI syntax, > > Excerpt from RFC-3455 > <<< > 4.1.2 Usage of the P-Associated-URI header > > The registrar inserts the P-Associated-URI header field into the 200 > OK response to a REGISTER request. The header field value is > populated with a list containing zero or more URIs that are > associated to the address-of-record. > If the registrar supports the P-Associated-URI header extension, then > the registrar MUST always insert the P-Associated-URI header field in > all the 200 OK responses to a REGISTER request, regardless of whether > the REGISTER was an initial registration, re-registration, or > de-registration and regardless of whether there are zero or more > associated URIs. > >>> > > it says if the registrar supports P-Associated-URI, then it has to > insert the P-Asserted-URI in 200 OK response for REGISTER > while defining the ABNF for the same its been mentioned as > > P-Associated-URI = "P-Associated-URI" HCOLON > (p-aso-uri-spec) > *(COMMA p-aso-uri-spec) > p-aso-uri-spec = name-addr *(SEMI ai-param) > ai-param = generic-param > > This ABNF syntax says as one or more, not zero or more number of > p-aso-uri-spec, > > Now my question is? > 1) Why do we need to insert the P-Associated-URI header if there are no > entry to fill in ? <Jerry>3GPP TS 24.229 Section 5.1.1.2, Initial registration, describes the usage of the P-Associated-URI header. Hope this helps.</Jerry> > 2) How do we specify the zero or more P-Associated-URI header values ? > <Jerry>See Section 4.1.2.2 in RFC 3455</Jerry> > Best Regards, > Nataraju A.B. > Kodiak Networks Ind Pvt Ltd > "Change your thoughts, and you change your world." > > > > ------------------------------ _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
