IETF Logo Mail Archive

Re: [Geopriv] Fwd: New Version Notification for draft-bellis-geopriv-flow-identity-00.txt

Richard Barnes <rbarnes@bbn.com> Wed, 29 February 2012 16:42 UTC

Return-Path: <rbarnes@bbn.com>
X-Original-To: geopriv@ietfa.amsl.com
Delivered-To: geopriv@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18B8421F872F for <geopriv@ietfa.amsl.com>; Wed, 29 Feb 2012 08:42:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.519
X-Spam-Level:
X-Spam-Status: No, score=-107.519 tagged_above=-999 required=5 tests=[AWL=1.080, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BTaXuN8B-45H for <geopriv@ietfa.amsl.com>; Wed, 29 Feb 2012 08:42:21 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 7EDE721F867A for <geopriv@ietf.org>; Wed, 29 Feb 2012 08:42:21 -0800 (PST)
Received: from [128.89.255.189] (port=52486) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1S2mbZ-000OlN-2P; Wed, 29 Feb 2012 11:42:17 -0500
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset="us-ascii"
From: Richard Barnes <rbarnes@bbn.com>
In-Reply-To: <999913AB42CC9341B05A99BBF358718D0128F925@FIESEXC035.nsn-intra.net>
Date: Wed, 29 Feb 2012 22:12:12 +0530
Content-Transfer-Encoding: quoted-printable
Message-Id: <D913FECD-6083-47E4-B52F-FC3DD307E5D4@bbn.com>
References: <20120229162612.28594.63549.idtracker@ietfa.amsl.com> <C92632FB-9896-4B0C-9CAE-7E54E579680D@nominet.org.uk> <999913AB42CC9341B05A99BBF358718D0128F925@FIESEXC035.nsn-intra.net>
To: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: GEOPRIV WG <geopriv@ietf.org>
Subject: Re: [Geopriv] Fwd: New Version Notification for draft-bellis-geopriv-flow-identity-00.txt
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/geopriv>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Feb 2012 16:42:22 -0000

> Since the idea of HELD is to find out where the entity (as described by an IP address, etc.) is I wonder why it would be useful to include the destination address and port number (which is what a flow information adds).

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

v2.23.0 | Report a Bug | By Email