Do the spaces matter for SIP messages or their contents? According to 3840, the definitions for the "methods=" Feature Tag are in compliance with RFC2730, which specifies both textual and non-textual (ASN.1 encoded) representations for negotiating capabilities. I would be surprised if a SIP implementation - which is text based almost by definition - specified ASN.1 encoding for its message contents.
Then again, what do I know? I certainly haven't read the entire RFC. :-) Jeffrey D. Wright System Test Engineering Manager Aztek Networks, Inc. -----Original Message----- From: Paul Kyzivat [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 19, 2007 7:31 PM To: Jeff Wright Cc: Amit P. Ahuja; sip-implementors@lists.cs.columbia.edu Subject: Re: [Sip-implementors] Is it acceptable to have "methods=" param in theContact header for a REGISTER message Right. I would however mention that the spaces within the quoted string value are incorrect. So it should be: Contact: sip:[EMAIL PROTECTED]:5060;methods="INVITE,ACK,BYE,CANCEL,OPTIONS,INFO,MES SAGE,SUBSCRIBE,NOTIFY,PRACK,UPDATE,REFER" Paul Jeff Wright wrote: > Hello, > > I just stumbled across this myself in the following RFC: > > http://tools.ietf.org/html/rfc3840 > > See in particular Section 6, "Expressing Capabilities in a > Registration." > > Best regards, > > Jeffrey D. Wright > System Test Engineering Manager > Aztek Networks, Inc. > (303) 415 6149 > [EMAIL PROTECTED] > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Amit P. Ahuja > Sent: Wednesday, December 19, 2007 4:05 PM > To: sip-implementors@lists.cs.columbia.edu > Subject: [Sip-implementors] Is it acceptable to have "methods=" param in > theContact header for a REGISTER message > > One of the SIP hardphones that I use sends out a REGISTER message with > the > Contact header that looks like: > > Contact: sip:[EMAIL PROTECTED]:5060;methods="INVITE, ACK, BYE, CANCEL, > OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER" > > I could not find whether the "methods=" param in the Contact is > acceptable > as per RFC3261. I thought Allow: is the only way of specifying supported > > methods. > Would someone know if it is valid and which RFC specifies so? > > Thanks and Regards, > Amit Ahuja > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
