IETF Logo Mail Archive

Re: [netext] Access Network Information option for Proxy Mobile IPv6

Sri Gundavelli <sgundave@cisco.com> Thu, 14 July 2011 20:11 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 7CB0411E8079 for <netext@ietfa.amsl.com>; Thu, 14 Jul 2011 13:11:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.157
X-Spam-Level:
X-Spam-Status: No, score=-5.157 tagged_above=-999 required=5 tests=[AWL=-2.558, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FmD9cd0s2x0V for <netext@ietfa.amsl.com>; Thu, 14 Jul 2011 13:11:00 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id AF2E321F86B6 for <netext@ietf.org>; Thu, 14 Jul 2011 13:10:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=sgundave@cisco.com; l=1060; q=dns/txt; s=iport; t=1310674243; x=1311883843; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version:content-transfer-encoding; bh=PQuMoEYLH+sn9NcRVPjkWB7+7by5n89w/5mbW3hCQuw=; b=Ntqb3DiczTZMqnhd7QZ50vDHZj5Ybm5sGRzkqmIUL7offKONTGzPEmzu BniLE+OBwIL3iTWNSVeZ7JFFbTUvCLiz37lOSx/nbFpMHN7DkXFeztYZ6 KzYnEH41k/ai/rP7bWsAWI9NRatPL3QapPUccVpDJE3ebJKtynyQQ70RM I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAHpMH06rRDoG/2dsb2JhbABUp2B3iHqkB54ThjoEh1OLEYUJhFOHFQ
X-IronPort-AV: E=Sophos;i="4.65,531,1304294400"; d="scan'208";a="3060785"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by rcdn-iport-9.cisco.com with ESMTP; 14 Jul 2011 20:10:43 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p6EKAY5e006203; Thu, 14 Jul 2011 20:10:42 GMT
Received: from xmb-sjc-214.amer.cisco.com ([171.70.151.145]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 14 Jul 2011 13:10:40 -0700
Received: from 10.32.243.10 ([10.32.243.10]) by xmb-sjc-214.amer.cisco.com ([171.70.151.145]) with Microsoft Exchange Server HTTP-DAV ; Thu, 14 Jul 2011 20:10:40 +0000
User-Agent: Microsoft-Entourage/12.30.0.110427
Date: Thu, 14 Jul 2011 13:10:38 -0700
From: Sri Gundavelli <sgundave@cisco.com>
To: Ryuji Wakikawa <ryuji.wakikawa@gmail.com>
Message-ID: <CA449B4E.21026%sgundave@cisco.com>
Thread-Topic: [netext] Access Network Information option for Proxy Mobile IPv6
Thread-Index: AcxCYhj3dS1U5Xy620+lJVSvknw9qw==
In-Reply-To: <2473AFC4-5B17-4507-A29E-60E22DC28EFD@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 14 Jul 2011 20:10:40.0443 (UTC) FILETIME=[1A6C38B0:01CC4262]
Cc: netext@ietf.org
Subject: Re: [netext] Access Network Information option for Proxy Mobile IPv6
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: Thu, 14 Jul 2011 20:11:04 -0000

Hi Ryuji:



On 7/14/11 12:08 PM, "Ryuji Wakikawa" <ryuji.wakikawa@gmail.com> wrote:

> Hi Sri,
> 
> 
> On 2011/07/13, at 23:37, Sri Gundavelli wrote:
> 
>> Hi Ryuji,
>> 
>> Thanks for the quick review. Appreciate it.
>> 
>> Yes, static keying of the information is always an option. But, that will be
>> a provisioning nightmare and secondly the information may be multi-valued
>> for a given MAG ID and may not be 1:1. We fundamentally need a container for
>> carrying access network information, that may be specific to the SSID,
> 
> ok
> 
>> Operator Id ... of the AP ..., having this generic container will greatly
>> help deployments. In one of our deployments, we have a requirement to carry
>> the Geo-location of one of the AP's out of the several attached to the MAG.
>> Hence, we need this simple option.
> 
> For geo-location, do you assume lat-long? Don't you need to specify the format
> of  information?
> 

Yes, we need to carry that information element. We need to define a sub-type
for this.

Regards
Sri

v2.23.0 | Report a Bug | By Email