Re: [netext] Stephen Farrell's No Objection on draft-ietf-netext-ani-location-08: (with COMMENT)

"Rajesh Pazhyannur (rpazhyan)" <rpazhyan@cisco.com> Thu, 05 March 2015 19:20 UTC

Return-Path: <rpazhyan@cisco.com>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 742A51A8741; Thu, 5 Mar 2015 11:20:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wE5_OEKjttxC; Thu, 5 Mar 2015 11:20:19 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97E411A873E; Thu, 5 Mar 2015 11:20:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1924; q=dns/txt; s=iport; t=1425583219; x=1426792819; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=r4Lu5z7YwetZvFnPXMe+yxiLuvEQ5tfOprnc/djw2/k=; b=DadRmKWsoslpgJR+xyqVUT4MJWfQwc9B0vqXbh8TePmhZLHcCluw4h11 bzueXd9daxGuGn5IWMVvj42+ofpgN4khbirYZ0+sCrd4TYzuvPHjcCi1k F7vdhPFmI9NlNP6/Rd9/QSLAR0PW2M+oa+dPqCs9QlEpi8JXlrvU55w/7 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DVCgBLq/hU/5FdJa1agwZSWgS7OYNIgjaFcAKBO00BAQEBAQF8hBABAQRnEhACAQhGMiUCBAENBQmIJQEN2C4BAQEBAQEBAQEBAQEBAQEBAQEBARiLF4QMEQFQAgWEKwWFd4RAhVCDY4VqgRo5gm2PLyOCMoE8bwGBCjl/AQEB
X-IronPort-AV: E=Sophos;i="5.11,348,1422921600"; d="scan'208";a="401234245"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-3.cisco.com with ESMTP; 05 Mar 2015 19:20:18 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t25JKI88022166 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 5 Mar 2015 19:20:18 GMT
Received: from xmb-aln-x09.cisco.com ([169.254.4.43]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.03.0195.001; Thu, 5 Mar 2015 13:20:18 -0600
From: "Rajesh Pazhyannur (rpazhyan)" <rpazhyan@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, The IESG <iesg@ietf.org>
Thread-Topic: Stephen Farrell's No Objection on draft-ietf-netext-ani-location-08: (with COMMENT)
Thread-Index: AQHQV1vtJw49ArvUAU2P1NimIKbc3p0OIpaA
Date: Thu, 5 Mar 2015 19:20:17 +0000
Message-ID: <D11DEBBA.1D86E%rpazhyan@cisco.com>
References: <20150305154630.11284.40854.idtracker@ietfa.amsl.com>
In-Reply-To: <20150305154630.11284.40854.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.6.141106
x-originating-ip: [171.70.241.212]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <CEFA8C900021B249824413F36C03A1F3@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/netext/wF9UAr15eRP-23KQOn12hHc2A_E>
Cc: "netext@ietf.org" <netext@ietf.org>, "netext-chairs@ietf.org" <netext-chairs@ietf.org>, "draft-ietf-netext-ani-location.all@ietf.org" <draft-ietf-netext-ani-location.all@ietf.org>
Subject: Re: [netext] Stephen Farrell's No Objection on draft-ietf-netext-ani-location-08: (with COMMENT)
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext/>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Mar 2015 19:20:21 -0000

On 3/5/15, 7:46 AM, "Stephen Farrell" <stephen.farrell@cs.tcd.ie>; wrote:

>Stephen Farrell has entered the following ballot position for
>draft-ietf-netext-ani-location-08: No Objection
>
>When responding, please keep the subject line intact and reply to all
>email addresses included in the To and CC lines. (Feel free to cut this
>introductory paragraph, however.)
>
>
>Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
>for more information about IESG DISCUSS and COMMENT positions.
>
>
>The document, along with other ballot positions, can be found here:
>http://datatracker.ietf.org/doc/draft-ietf-netext-ani-location/
>
>
>
>----------------------------------------------------------------------
>COMMENT:
>----------------------------------------------------------------------
>
>
>
>- What if the network being identified here was a tethering
>n/w or any other kind of n/w that's carried about by a person?
>In that case ANI, and these new options, would be privacy
>invasive. Does that statement exist in one of the RFCs
>referred to in section 6? If not, would it be worth adding
>here, even though it might better belong elsewhere?

Copying BrianĀ¹s answer as well for context.
<brian>
That isn't applicable as far as I know.  The location option is used
between the two infrastructure devices (LMA and MAG) providing the proxy
mobility service.  The actual user's location is not being carried and
the MAG is not a mobile platform.

</brian>

Yes, I agree. The civic location is that of the MAG (and not the end-user)
and the MAG is typically on a router, access point, etc.

>
>- intro: What if a WLAN operator has no realm?

The operator-identifier (which contains realm) is optional. They can
choose to not send it if they have no realm.

>
>- intro: DPI? What's that got to do with it? I'd suggest
>removing that.

Ok.

>
>