See below. Thanks, Neel.
> -----Original Message----- > From: [email protected] [mailto:sip- > [email protected]] On Behalf Of Iñaki Baz > Castillo > Sent: Thursday, December 11, 2008 2:28 PM > To: [email protected] > Subject: Re: [Sip-implementors] Empty Proxy-Authorization Header > > El Jueves, 11 de Diciembre de 2008, Brett Tate escribió: > > > I agree that the header value is not optional within > > Proxy-Authorization. However an empty header value is valid within > some > > headers such as Supported. > > "Supported" header does NOT allow empty value: > > -------- > Supported = ( "Supported" / "k" ) HCOLON [option-tag *(COMMA option- > tag)] [Neelakantan Balasubramanian] Section 20.37 Supported The Supported header field enumerates all the extensions supported by the UAC or UAS. The Supported header field contains a list of option tags, described in Section 19.2, that are understood by the UAC or UAS. A UA compliant to this specification MUST only include option tags corresponding to standards-track RFCs. If empty, it means that no extensions are supported. So, it can be empty. If my understating id right, anything in "[" "]" is optional. > option-tag = token > > token = 1*( alphanum > / "-" / "." / "!" / "%" / "*" > / "_" / "+" / "`" / "'" / "~" ) > --------- > > It requires, at least, one value. > > > -- > Iñaki Baz Castillo > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
