Subject: [Sipping] RE: [Sip-implementors] help

From: "Attila Sipos" <[email-masked]>
Date: Wed, 21 Sep 2005 14:21:20 +0100

The Remote-Party-Id (RPID) seems to be depracated now.
It was originally conceived in the "privacy" drafts
(one of which is draft-ietf-sip-privacy-04.txt).
I think all drafts for this have expired.

If Remote-Party-Id was an RFC then there would not
be a need for the Diversion header since you can
indicate the information in the RPID.

It seems that two other RFC's have effectively
replaced the Remote-Party-Id draft:
RFC 3323 - A Privacy Mechanism for the Session Initiation Protocol (SIP)
RFC 3325 - Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks

And to carry the diversion information, you also need use
"Diversion Indication in SIP" (one of the drafts
is draft-levy-sip-diversion-08.txt).

Regards,

Attila

Attila Sipos
Software Engineer
http://www.vegastream.com

>> -----Original Message-----
>> From: [email-masked]
>> [mailto:[email-masked]]On Behalf Of
>> [email-masked]
>> Sent: 21 September 2005 12:55
>> To: [email-masked]; [email-masked]
>> Subject: [Sip-implementors] help
>> 
>> 
>> 
>> 
>> 
>> Hi All,
>> 
>> I would like to know why we need both Rpid header and 
>> Diversion header,
>> if both headers do have same functionalities (like capturing the OCDN
>> and RN number in a SIP message).
>> Could you please answer to this question?
>> 
>> Thanks,
>> Sushma
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> Confidentiality Notice
>> 
>> The information contained in this electronic message and any 
>> attachments to this message are intended
>> for the exclusive use of the addressee(s) and may contain 
>> confidential or privileged information. If
>> you are not the intended recipient, please notify the sender 
>> at Wipro or [email-masked] immediately
>> and destroy all copies of this message and any attachments.
>> 
>> _______________________________________________
>> Sip-implementors mailing list
>> [email-masked]
>> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [email-masked] for questions on current sip
Use [email-masked] for new developments of core SIP