Re: I-D ACTION:draft-ietf-sip-location-conveyance-05.txt

I think this draft has much improved. However, there remains an issue with 
the ABNF:

Geolocation        =  "Geolocation" HCOLON (locationURI *(COMMA
                          locationURI))
locationURI        =  sip-URI / sips-URI / pres-URI / cid-URI
                          / absoluteURI
cidURI             =  "cid:" content-id
content-id         =  addr-spec ; URL encoding of RFC3261 addr-spec
I would suggest to use '<' '>' around the URI, and allow for generic header 
parameters. This is inline with the second example used in section 4.2:

Geolocation        =  "Geolocation" HCOLON (locationValue *(COMMA
                          locationValue))locationValue      =  LAQUOT 
locationURI RAQUOT *(SEMI generic-param)locationURI        =  sip-URI / 
sips-URI / pres-URI / cid-URI
                          / absoluteURI
cidURI             =  "cid:" content-id
content-id         =  addr-spec ; URL encoding of RFC3261 addr-spec
Second comment: section 3.5 still contains the phrase "Appearance of the 
option tag in the Require header is a request for location to be conveyed." 
Such  semantics are not common for Require

Regards,
Jeroen


[email protected] wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Session Initiation Protocol Working
>> Group of the IETF.
>>
>> Title : Session Initiation Protocol Location Conveyance
>> Author(s) : J. Polk, B. Rosen
>> Filename : draft-ietf-sip-location-conveyance-05.txt
>> Pages : 26
>> Date : 2006-10-19
>>
>> This document defines an extension to the Session Initiation
>>   Protocol (SIP) to convey geographic location information from one
>>   SIP entity to another SIP entity.  The extension covers end to end
>>   conveyance as well as location-based routing, where proxy servers
>>   make routing decisions based on the location of the UAC.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-sip-location-conveyance-05.txt
>>
>> To remove yourself from the I-D Announcement list, send a message to
>> [email protected] with the word unsubscribe in the body
>> of
>> the message.
>> You can also visit
>> https://www1.ietf.org/mailman/listinfo/I-D-announce
>> to change your subscription settings.
>>
>> Internet-Drafts are also available by anonymous FTP. Login with the
>> username "anonymous" and a password of your e-mail address. After
>> logging in, type "cd internet-drafts" and then
>> "get draft-ietf-sip-location-conveyance-05.txt".
>>
>> A list of Internet-Drafts directories can be found in
>> http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>> Internet-Drafts can also be obtained by e-mail.
>>
>> Send a message to:
>> [email protected].
>> In the body type:
>> "FILE /internet-drafts/draft-ietf-sip-location-conveyance-05.txt".
>>
>> NOTE: The mail server at ietf.org can return the document in
>> MIME-encoded form by using the "mpack" utility.  To use this
>> feature, insert the command "ENCODING mime" before the "FILE"
>> command.  To decode the response(s), you will need "munpack" or
>> a MIME-compliant mail reader.  Different MIME-compliant mail readers
>> exhibit different behavior, especially when dealing with
>> "multipart" MIME messages (i.e. documents which have been split
>> up into multiple messages), so check your local documentation on
>> how to manipulate these messages.
>>
>> 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://www1.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://www1.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