RE: [Sipping] Last Call: draft-ietf-sipping-service-examples (Ses sion Initiation Protocol Service Examples) to BCP

["Hutton, Andrew" <andrew.hutton at siemens.com>]

Whilst the document contains some useful examples of how services might be
implemented it does not I believe represent the BCP for some services and
publishing this as BCP may not help interoperability.

For example the document describes the service "Call Hold" and indicates
that "a=sendonly" should be used but also states that "a UA that places the
other party on hold will generally also stop sending media, resulting in no
media exchange between the Uas".

The use of "a=sendonly" in the case where no media is to be sent is clearly
not best practice as in this case "a=inactive" should be used. 

The draft-ietf-sipping-sip-offeranswer contains a much better description of
how media should be held and resumed.

Regards
Andy



However,   Older UAs may set the
   connection address to 0.0.0.0 when initiating hold.  However, this
   behavior has been deprecated in favor of using the a=sendonly SDP
   attribute.



> -----Original Message-----
> From: The IESG [mailto:iesg-secretary at ietf.org] 
> Sent: 08 November 2007 13:42
> To: IETF-Announce
> Cc: sipping at ietf.org
> Subject: [Sipping] Last Call: 
> draft-ietf-sipping-service-examples (Session Initiation 
> Protocol Service Examples) to BCP
> 
> The IESG has received a request from the Session Initiation Proposal 
> Investigation WG (sipping) to consider the following document:
> 
> - 'Session Initiation Protocol Service Examples '
>    <draft-ietf-sipping-service-examples-13.txt> as a BCP
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send substantive 
> comments to the
> ietf at ietf.org mailing lists by 2007-11-22. Exceptionally, 
> comments may be sent to iesg at ietf.org instead. In either case, please 
> retain the beginning of the Subject line to allow automated sorting.
> 
> The file can be obtained via
>
http://www.ietf.org/internet-drafts/draft-ietf-sipping-service-examples-
13.txt
> 
> 
> IESG discussion can be tracked via
> https://datatracker.ietf.org/public/pidtracker.cgi?command=vie
> w_id&dTag=8508&rfc_flag=0
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors at cs.columbia.edu for questions on current sip
> Use sip at ietf.org for new developments of core SIP
> 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sip at ietf.org for new developments of core SIP

_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf