Me too plz

Sent from my iPhone

> On Mar 21, 2014, at 7:34 PM, Amit Kumar Mishra <[email protected]> 
> wrote:
> 
> Hi,
> Remove me form this mailing list.
> 
> Regards,
> Amit
> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Sreejith 
> Sadaasivan
> Sent: Friday, March 21, 2014 9:57 PM
> To: [email protected]; Paul Kyzivat
> Subject: Re: [Sip-implementors] Query on Contact header parameter
> 
> Hello,
> 
> Please remove me from this mailing list.
> 
> Regards,
> SREE
> --------------------------------------------
> On Fri, 21/3/14, Paul Kyzivat <[email protected]> wrote:
> 
> Subject: Re: [Sip-implementors] Query on Contact header parameter
> To: [email protected]
> Date: Friday, 21 March, 2014, 8:43 AM
> 
> You have now received answers to the
> question you asked.
> But not to the one you should have asked: how can you do  this in a way that 
> doesn't violate standards?
> 
> The procedure for managing new header field parameters was  updated by RFC 
> 3968. There is an IANA registry, and you need  an RFC to define a new one. I 
> assume you haven't published  an RFC to define your proprietary parameter.
> 
> An alternative that is open to you is a feature tag, as  defined in RFC 3840. 
> In particular you can use feature tags  from the "URI tree" to express 
> vendor-specific features.
> 
> UAs are expected to ignore parameters they don't understand,  so you can "get 
> away" with using an illegal unregistered  parameter, but you may run into 
> trouble if the name you  choose is later chosen as the name of some standard 
> option.
> Or if you do interop testing, someone may identify you as  non-complying for 
> using a non-standard option.
> 
>     Thanks,
>     Paul
> 
>> On 3/21/14 6:33 AM, J C Sunil Kumar Reddy wrote:
>> Hi All,
>> 
>> I need to send a proprietary parameter in contact  header in an INVITE  > 
>> message to other end.
>> Something like this:
>> 
>> Contact: "Sunil"
> <sip:[email protected];transport=tcp>;category:strvalue
>> 
>> Here "category:strvalue" is my proprietary parameter.
> Where "category" is a
>> param name and "strvalue" is the value.
>> 
>> What does the SIP standard specify? whether it should  be colon(:) or  > 
>> Equals(=)?
>> I mean according to SIP standards, which is the correct  one?
>> 
>> category:strvalue
>> or
>> category=strvalue
>> or something else?
>> 
>> Regards,
>> Sunil
>> _______________________________________________
>> Sip-implementors mailing list
>> [email protected]
>> https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
> 
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
> 
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
> 
> 
> 
> 
> ===============================================================================
> Please refer to http://www.aricent.com/legal/email_disclaimer.html
> for important disclosures regarding this electronic communication.
> ===============================================================================
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to