I can name that tune in 3 letters: CGN.
--Ricahrd
>
> Ciao
> Hannes
>
>
> From: geopriv-bounces@ietf.org [mailto:geopriv-bounces@ietf.org] On Behalf Of ext Ray Bellis
> Sent: Wednesday, February 29, 2012 6:29 PM
> To: GEOPRIV WG
> Subject: [Geopriv] Fwd: New Version Notification for draft-bellis-geopriv-flow-identity-00.txt
>
> I've just submitted the draft detailed below, available at:
>
> http://tools.ietf.org/html/draft-bellis-geopriv-flow-identity-00
>
> Textually, it's somewhat rough, but I wanted to get feedback on the general idea (and the validity of the XSD) before spending too much time on the words themselves.
>
> Ray
>
>
> From: <internet-drafts@ietf.org>
> Subject: New Version Notification for draft-bellis-geopriv-flow-identity-00.txt
> Date: 29 February 2012 16:26:12 GMT
> To: <ray.bellis@nominet.org.uk>
>
> A new version of I-D, draft-bellis-geopriv-flow-identity-00.txt has been successfully submitted by Ray Bellis and posted to the IETF repository.
>
> Filename: draft-bellis-geopriv-flow-identity
> Revision: 00
> Title: Flow Identity Extension for HELD
> Creation date: 2012-02-29
> WG ID: Individual Submission
> Number of pages: 12
>
> Abstract:
> Identity Extensions using an IP address and port number to request a
> location based on an individual packet flow have been previously
> specified by the GEOPRIV Working Group.
>
> However certain kinds on NAT require that identifiers for both ends
> of the packet flow must be specified in order to unambiguously
> satisfy the location request.
>
> This document specifieds a Flow Identity Extension for the HTTP-
> Enabled Location Delivery (HELD) Protocol to support this
> requirement.
>
>
> _______________________________________________
> Geopriv mailing list
> Geopriv@ietf.org
> https://www.ietf.org/mailman/listinfo/geopriv
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
