IETF Logo Mail Archive

Re: [netext] I-D Action: draft-ietf-netext-access-network-option-07.txt

Sri Gundavelli <sgundave@cisco.com> Sun, 26 February 2012 04:12 UTC

Return-Path: <sgundave@cisco.com>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2D7B21F85A1 for <netext@ietfa.amsl.com>; Sat, 25 Feb 2012 20:12:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.834
X-Spam-Level:
X-Spam-Status: No, score=-8.834 tagged_above=-999 required=5 tests=[AWL=1.765, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 BWX-qvk9yQ58 for <netext@ietfa.amsl.com>; Sat, 25 Feb 2012 20:12:45 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 43CA621F8569 for <netext@ietf.org>; Sat, 25 Feb 2012 20:12:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=sgundave@cisco.com; l=2342; q=dns/txt; s=iport; t=1330229565; x=1331439165; h=date:subject:from:to:message-id:in-reply-to:mime-version: content-transfer-encoding; bh=ynGF6QSAhjZedEOfI+96Qn4WKG99dpoc7dPxSOZzoJ0=; b=kJMn/mEzYJ+AVs2h0Hi8NAkmrXysI6q63RWQkXOO825NyXE5ATua3IQ/ 0kS9n0tM1knwCpWt8Lsqz9faKX+JJI0EDBUbcGskzBQp4GswYwvaroiV6 0HRty9hbTXqydMJwL9n4uskZBRGu5vH/bhirbJ7dYSpcYGAzSYurjvgTp o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAOqwSU+rRDoH/2dsb2JhbABDsyqBB4FzAQEBAwEBAQEPAScCATEdAQhtMAEBBBMJGYdfBAELn1OBJwGWAY0ODQMTAgINAgJBBgEGBAkChUMBDQcEBhoOgx4EiE+MbpMP
X-IronPort-AV: E=Sophos;i="4.73,483,1325462400"; d="scan'208";a="32564372"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 26 Feb 2012 04:12:45 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q1Q4CiAD024424 for <netext@ietf.org>; Sun, 26 Feb 2012 04:12:44 GMT
Received: from xmb-sjc-214.amer.cisco.com ([171.70.151.145]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Sat, 25 Feb 2012 20:12:44 -0800
Received: from 10.21.64.143 ([10.21.64.143]) by xmb-sjc-214.amer.cisco.com ([171.70.151.145]) with Microsoft Exchange Server HTTP-DAV ; Sun, 26 Feb 2012 04:12:44 +0000
User-Agent: Microsoft-Entourage/12.32.0.111121
Date: Sat, 25 Feb 2012 20:12:39 -0800
From: Sri Gundavelli <sgundave@cisco.com>
To: netext@ietf.org
Message-ID: <CB6EF137.3C5A2%sgundave@cisco.com>
Thread-Topic: [netext] I-D Action: draft-ietf-netext-access-network-option-07.txt
Thread-Index: Acz0POCV3yuKy1PdMkSgibWcH/sRKg==
In-Reply-To: <20120226040253.14732.68490.idtracker@ietfa.amsl.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 26 Feb 2012 04:12:44.0908 (UTC) FILETIME=[E41AD2C0:01CCF43C]
Subject: Re: [netext] I-D Action: draft-ietf-netext-access-network-option-07.txt
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 26 Feb 2012 04:12:46 -0000

Minor change to one of the network-name sub-option, based on the offline
inputs from few people. The change is for including the AP-name in addition
to the SSID. This appears to be a critical information element based on WLAN
deployments that are out there today. For applying location specific
services, we need both the SSID and AP-name. SSID is too broad, it literally
identifies the operator and hence cannot be used for applying any location
specific services. For example, some WLAN operators want to display a HTTP
Page based on the location to which the user is attached and others want to
apply different service tariffs.


Regards
Sri



On 2/25/12 8:02 PM, "internet-drafts@ietf.org" <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 Network-Based Mobility
> Extensions Working Group of the IETF.
> 
> Title           : Access Network Identifier (ANI) Option for Proxy Mobile IPv6
> Author(s)       : Sri Gundavelli
>                           Jouni Korhonen
>                           Mark Grayson
>                           Kent Leung
>                           Rajesh Pazhyannur
> Filename        : draft-ietf-netext-access-network-option-07.txt
> Pages           : 17
> Date            : 2012-02-25
> 
>    This specification defines a mechanism and a related mobility option
>    for carrying the access network identifier and the access operator
>    identification information from the mobile access gateway to the
>    local mobility anchor over Proxy Mobile IPv6.  Based on the received
>    information, the local mobility anchor is able to provide access
>    network and access operator specific handling or policing for the
>    mobile node traffic.
> 
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-netext-access-network-option-07
> .txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-netext-access-network-option-07.
> txt
> 
> _______________________________________________
> netext mailing list
> netext@ietf.org
> https://www.ietf.org/mailman/listinfo/netext

v2.23.0 | Report a Bug | By Email