Hi, >The mechanism of dynamic blocking of caller identities got approved in 3GPP. The text got included in the latest version of 22.173. So, why can't you use the existing mechanisms in 3GPP (XCAP etc)? Regards, Christer > From: Christer Holmberg [mailto:christer.holmberg@xxxxxxxxxxxx] > Sent: Tuesday, March 03, 2009 1:54 PM > To: Avasarala Ranjit-A20990; sipping@xxxxxxxx > Subject: RE: New Internet Draft for Caller Identity Blocking > > > Hi, > > The draft talks alot about 3GPP, and the work on IMS supplementary > services. Why? Is your intention to bring this to 3GPP? If > so, why can't > the existing service configuration mechanisms in 3GPP be used > for this? > > Regards, > > Christer > > > ________________________________________ > > From: sipping-bounces@xxxxxxxx > > [mailto:sipping-bounces@xxxxxxxx] On Behalf Of Avasarala > Ranjit-A20990 > > Sent: Monday, March 02, 2009 3:45 AM > > To: sipping@xxxxxxxx > > Subject: New Internet Draft for Caller Identity Blocking > > > > Hi All > > I have just submitted an I-D on blocking caller identities during > > ringing and call termination phases by extending SIP Reason > header to > > be included in SIP BYE and CANCEL methods. > > Please review and comment > > The URL of the draft is: > > http://www.ietf.org/internet-drafts/draft-avasarala-sipping-re > > ason-header-dynamic-icb-00.txt > > Thanks > > Regards > > Ranjit > > _______________________________________________ > > Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping > > This list is for NEW development of the application of SIP Use > > sip-implementors@xxxxxxxxxxxxxxx for questions on current sip Use > > sip@xxxxxxxx for new developments of core SIP > > > _______________________________________________ Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip Use sip@xxxxxxxx for new developments of core SIP
