Re: [dispatch] New Version Notification for draft-bakker-dispatch-3gpp-ims-xml-body-handling-00.txt

Hi Gonzalo,

> I assume "3gpp-alternative-service" covers uses (1) and (3) and "3gpp-service-info" covers use 
> (2). Is this assumption correct? (In any case, the draft could be clearer on that point.)

That is correct. 
I am happy to further clarify that point in the draft.

> After reading the draft, it seems to me that "3gpp-ims+xml" bodies with disposition type 
> "3gpp-alternative-service" will always be carried in SIP responses while "3gpp-ims+xml" 
> bodies with disposition type "3gpp-service-info" will always be carried in SIP requests. 
> Is my understanding correct?

Today, indeed, "3gpp-ims+xml" bodies with disposition type "3gpp-alternative-service" are carried in SIP responses while "3gpp-ims+xml" bodies with disposition type "3gpp-service-info" are carried in SIP requests.
I don't know if that "will always" be the case.

Kind regards,

	John-Luc

-----Original Message-----
From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com] 
Sent: Wednesday, September 26, 2012 6:16 AM
To: John-Luc Bakker
Cc: dispatch@ietf.org
Subject: Re: [dispatch] New Version Notification for draft-bakker-dispatch-3gpp-ims-xml-body-handling-00.txt

Hi John Luc,

I have a quick question about this draft.

The Abstract identifies three uses for 3gpp-ims+xml bodies:

>  (1)
>    for redirecting the emergency session to use a different domain (e.g.
>    using a Circuit Switched call), (2) for delivering user profile
>    specific information from the SIP registrar to an Application Server,
>    and (3) for causing a UAC to attempt to re-register with the IMS.

Later, the draft defines two disposition types:

>       o 3gpp-alternative-service: the body (part) contains 3GPP IM CN
>       subsystem XML with the 'alternative-service' XML element as
>       described in Section 4.2; and
> 
>       o 3gpp-service-info: the body (part) contains 3GPP IM CN subsystem
>       XML with the 'service-info' XML element as described in Section
>       4.3.

I assume "3gpp-alternative-service" covers uses (1) and (3) and "3gpp-service-info" covers use (2). Is this assumption correct? (In any case, the draft could be clearer on that point.)

After reading the draft, it seems to me that "3gpp-ims+xml" bodies with disposition type "3gpp-alternative-service" will always be carried in SIP responses while "3gpp-ims+xml" bodies with disposition type "3gpp-service-info" will always be carried in SIP requests. Is my understanding correct?

Thanks,

Gonzalo

On 04/09/2012 6:30 PM, John-Luc Bakker wrote:
> Dear all,
> 
> I have submitted a new version of the previous "draft-bakker-sipping-3gpp-ims-xml-body-handling", taking into account the various comments received. The most notable change is to submit the draft to DISPATCH (instead of SIPPING) and to submit the draft for standards track consideration.
> 
> I welcome your comments.
> 
> Kind regards,
> 
> 	John-Luc
> 
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Tuesday, September 04, 2012 10:26 AM
> To: John-Luc Bakker
> Subject: New Version Notification for 
> draft-bakker-dispatch-3gpp-ims-xml-body-handling-00.txt
> 
> 
> A new version of I-D, 
> draft-bakker-dispatch-3gpp-ims-xml-body-handling-00.txt
> has been successfully submitted by John-Luc Bakker and posted to the IETF repository.
> 
> Filename:	 draft-bakker-dispatch-3gpp-ims-xml-body-handling
> Revision:	 00
> Title:		 Specification of 3GPP IM CN Subsystem XML body handling
> Creation date:	 2012-09-04
> WG ID:		 Individual Submission
> Number of pages: 8
> URL:             http://www.ietf.org/internet-drafts/draft-bakker-dispatch-3gpp-ims-xml-body-handling-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-bakker-dispatch-3gpp-ims-xml-body-handling
> Htmlized:        http://tools.ietf.org/html/draft-bakker-dispatch-3gpp-ims-xml-body-handling-00
> 
> 
> Abstract:
>    This document registers new disposition-types for the Content-
>    Disposition header field that apply to the application/3gpp-ims+xml
>    body (part) used by 3GPP [5].  The applicability of these content-
>    disposition values are limited to 3GPP IMS [5].  The application/
>    3gpp-ims+xml body (part) has the following three distinct uses: (1)
>    for redirecting the emergency session to use a different domain (e.g.
>    using a Circuit Switched call), (2) for delivering user profile
>    specific information from the SIP registrar to an Application Server,
>    and (3) for causing a UAC to attempt to re-register with the IMS.
> 
>                                                                                   
> 
> 
> The IETF Secretariat
> 
> 
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
> 

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.