Re: [Geopriv] I-D Action: draft-ietf-geopriv-flow-identity-01.txt

I'll request IETF LC on this version.

Everyone please note carefully the strengthening of the deprecation in 
this change. If you are not ok with the SHOULD NOT -> MUST NOT change, 
speak up during IETF LC.

RjS

On 2/13/13 5:35 AM, Ray Bellis wrote:
> On 13 Feb 2013, at 11:04, internet-drafts@ietf.org wrote:
>
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> This draft is a work item of the Geographic Location/Privacy Working Group of the IETF.
>>
>> 	Title           : Flow Identity Extension for HELD
>> 	Author(s)       : Ray Bellis
>> 	Filename        : draft-ietf-geopriv-flow-identity-01.txt
>> 	Pages           : 14
>> 	Date            : 2013-02-13
>>
> I've submitted this version in response to AD and proto writeup comments, mostly around how it updates RFC 6155.
>
> The abstract has been rewritten somewhat to make it clearer, and to explicitly mention that this document deprecates the port elements from RFC 6155.
>
> What was the final paragraph of §3 has been moved into the Introduction and rewritten thus:
>
>   Since the Location Recipient may not know in advance whether the
>   Target is behind a NAT device the port number elements from Section
>   3.3 of [RFC6155] are deprecated and MUST NOT be used.  This document
>   provides a more generally applicable means of identifying a Device
>   based on the parameters of a network flow of which it is an endpoint.
>
> Alissa had proposed the following text in her proto writeup:
>
> "It updates RFC 6155 to include this extension ..."
>
> I've explicitly *not* included such text because technically this document is a *new* extension, not an addition to the RFC 6155 schema.
>
> Ray
>
> _______________________________________________
> Geopriv mailing list
> Geopriv@ietf.org
> https://www.ietf.org/mailman/listinfo/geopriv