Also note that these vendor specific extensions will be ignored by everyone else. So, if they are providing a critical function, you've just introduced a proprietary solution. Service providers should be cautious about purchasing such products. -Jonathan R. --- Jonathan D. Rosenberg 72 Eagle Rock Ave. Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 [EMAIL PROTECTED] FAX: (973) 952-5050 http://www.cs.columbia.edu/~jdrosen PHONE: (973) 952-5000 http://www.dynamicsoft.com > -----Original Message----- > From: Henning Schulzrinne [mailto:[EMAIL PROTECTED]] > Sent: Monday, March 19, 2001 5:22 PM > To: Jean-Francois Mule > Cc: [EMAIL PROTECTED] > Subject: Re: [Sip-implementors] Some vendors are using special header > lines: is this allowed?? > > > Vendor-specific header lines are ok. Just be prepared that > the IETF will > redefine your favorite header, so documenting your extension, > according > to the published IANA procedures, is far superior. > > Jean-Francois Mule wrote: > > > > Some vendors are inserting some vendor-specific request header lines > > (one example we have is in the INVITE for example). I do > not believe > > this is allowed. > > > > The particular vendor-specific header line is in the form of: > > vendorx-hname: vendorx-hvalue > > > > If this is allowed, it seems to be a recipe for allowing > *:* in our sip > > parsers... > > Proxies need to be handle any valid header, i.e., Header: > something-or-other > _______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
