Hi Mary, >Sorry, I misunderstood your point - your email suggests to add text about why >P-Called-Party-ID was used (and didn't say >"NOT used").
Ok, sorry for that. >It's also not clear in your previous doc as you mention that 3GPP will >continue to use the P-Called-Party-ID. Yes, but that doesn't prevent them from using the H-I mechanism, should there be a requirement for that. P-CPI is used for another purpose than the problem we are trying to solve. >Either way, I still don't think we should discuss p-headers in a standard's >track document. I think Jonathan has put >forth reasonable use cases that show why the solution in this document works >and in general, I don't think we need to >consider P-headers to solve general problems. I don't see a reason why we can't indicate why a specific mechanism can not be used. That is part of the justification of the new H-I mechanism. >ISTM you might want a 3GPP specific doc describing why this document is >preferred over a solution that uses P-Called- >Party-ID. Again, P-CPI cannot be used :) Regards, Christer -----Original Message----- From: Christer Holmberg [mailto:[EMAIL PROTECTED] Sent: Thursday, November 13, 2008 5:15 PM To: Barnes, Mary (RICH2:AR00); Jonathan Rosenberg Cc: [email protected] Subject: VS: [Sip] draft-rosenberg-sip-target-uri-delivery-00.txt: P-Called-Party-ID Hi Mary, I am not sure I understand what you are saying. I am not asking to "define" anything. I am just asking to include the text which says why P-CPI can NOT be used. Regards, Christer -----Alkuperäinen viesti----- Lähettäjä: Mary Barnes [mailto:[EMAIL PROTECTED] Lähetetty: to 13.11.2008 17:36 Vastaanottaja: Christer Holmberg; Jonathan Rosenberg Kopio: [email protected] Aihe: RE: [Sip] draft-rosenberg-sip-target-uri-delivery-00.txt: P-Called-Party-ID I guess I might be dense, but why can't that be derived from the HI entry just before the one marked as the "target" entry? This was the whole concept behind capturing complete history info - you should always have the previous request URI and you can build a complete tree of the retargeting (where RFC 4244 defined that term to include both basic routing changes to the request URI as well as redirections). Also, I don't think it's appropriate that it would even be defined in this doc, even if you need it. You would need a separate doc in SIPPING and go through the normal expert review process. Mary. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christer Holmberg Sent: Friday, October 31, 2008 7:52 AM To: Jonathan Rosenberg Cc: [email protected] Subject: [Sip] draft-rosenberg-sip-target-uri-delivery-00.txt: P-Called-Party-ID Hi, The draft-holmberg-sip-target-uri-delivery-01.txt draft contained text on why the P-Called-Party-ID header was used. Would it be a good idea to keep that text in this spec, because I have already received questions regarding that. Regards, Christer > > A New Internet-Draft is available from the on-line Internet-Drafts > > directories. > > > > Title : Delivery of Request-URI Targets to User Agents > > Author(s) : J. Rosenberg > > Filename : draft-rosenberg-sip-target-uri-delivery-00.txt > > Pages : 12 > > Date : 2008-10-26 > > > > When a Session Initiation Protocol (SIP) proxy receives a request > > targeted at a URI identifying a user or resource it is responsible > > for, the proxy translates the URI to a registered contact URI of an > > agent representing that user or resource. In the process, the > > original URI is removed from the request. Numerous use cases have > > arisen which require this information to be delivered to the user > > agent. This document describes these use cases and defines an > > extension to the History-Info header field which allows it > to be used > > to support those cases. > > > > A URL for this Internet-Draft is: > > > http://www.ietf.org/internet-drafts/draft-rosenberg-sip-target-uri-del > > ivery-00.txt > > > > Internet-Drafts are also available by anonymous FTP at: > > ftp://ftp.ietf.org/internet-drafts/ > > > > Below is the data which will enable a MIME compliant mail reader > > implementation to automatically retrieve the ASCII version of the > > Internet-Draft. > > <mime-attachment>_______________________________________________ > > I-D-Announce mailing list > > [EMAIL PROTECTED] > > https://www.ietf.org/mailman/listinfo/i-d-announce > > Internet-Draft directories: http://www.ietf.org/shadow.html or > > ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > _______________________________________________ > Sip mailing list https://www.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP Protocol Use > [EMAIL PROTECTED] for questions on current sip Use > [EMAIL PROTECTED] for new developments on the application of sip > _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
