Re: [Sip] I-D Action:draft-barnes-sip-rfc4244bis-00.txt

["Mary Barnes" <mary.barnes at nortel.com>]

Hi Christer, 

Yes, we can remove a lot of the extra examples in the appendix - that
was what we had in mind for the next revision, since they all need to be
updated (all of them are dated in that they use strict routing). Also,
since there is now a document like target-uri that has better use cases,
we really don't need so many in the protocol spec. So, perhaps, you can
consider adding some detailed flows to target-uri?  

And, you have to keep in mind that the normative text in 4244 is
comprised of about 12 pages (7-18), so yes the size of the document is
misleading in terms of what really has to be implemented

Mary. 

-----Original Message-----
From: Christer Holmberg [mailto:christer.holmberg at ericsson.com] 
Sent: Wednesday, March 11, 2009 7:55 AM
To: Barnes, Mary (RICH2:AR00); Audet, Francois (SC100:3055)
Cc: sip at ietf.org
Subject: RE: [Sip] I-D Action:draft-barnes-sip-rfc4244bis-00.txt


Hi,

My first comment/question on the draft: eventhough there are lots of
examples, do we really need 46 pages? Are we really making History-Info
more clear if we still need that many pages?

I know my comment is not that useful, since I don't propose what to
change/remove, but just as a general comment.

Regards,

Christer




> -----Original Message-----
> From: i-d-announce-bounces at ietf.org
> [mailto:i-d-announce-bounces at ietf.org] On Behalf Of 
> Internet-Drafts at ietf.org
> Sent: 04 March 2009 15:15
> To: i-d-announce at ietf.org
> Subject: I-D Action:draft-barnes-sip-rfc4244bis-00.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> 
> 	Title           : An Extension to the Session Initiation
> Protocol (SIP) for Request History Information
> 	Author(s)       : M. Barnes, F. Audet
> 	Filename        : draft-barnes-sip-rfc4244bis-00.txt
> 	Pages           : 49
> 	Date            : 2009-03-04
> 
> This document defines a standard mechanism for capturing the history 
> information associated with a Session Initiation Protocol (SIP) 
> request.  This capability enables many enhanced services by providing 
> the information as to how and why a call arrives at a specific 
> application or user.  This document defines a new optional SIP header,

> History-Info, for capturing the history information in requests.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-barnes-sip-rfc4244bis-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.
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors at cs.columbia.edu for questions on current sip Use 
> sipping at ietf.org for new developments on the application of sip
>