Re: [16NG] Re: Last Call: draft-ietf-16ng-ipv6-over-ipv6cs (IPv6 Over the IP Specific part of the Packet Convergence sublayer in 802.16 Networks) to Proposed Standard
Alexandru Petrescu <alexandru.petrescu@gmail.com> Wed, 14 March 2007 16:48 UTC
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1HRWdx-00028a-Ia; Wed, 14 Mar 2007 12:48:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1HRWdu-000287-Rr; Wed, 14 Mar 2007 12:48:02 -0400
Received: from mail153.messagelabs.com ([216.82.253.51])
by ietf-mx.ietf.org with smtp (Exim 4.43)
id 1HRWdt-0004wa-GN; Wed, 14 Mar 2007 12:48:02 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-14.tower-153.messagelabs.com!1173890879!5007464!1
X-StarScan-Version: 5.5.10.7.1; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 9121 invoked from network); 14 Mar 2007 16:48:00 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
by server-14.tower-153.messagelabs.com with SMTP;
14 Mar 2007 16:48:00 -0000
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l2EGlxQS020415;
Wed, 14 Mar 2007 09:47:59 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id l2EGlwK5011915;
Wed, 14 Mar 2007 11:47:58 -0500 (CDT)
Message-ID: <45F8273D.9020108@gmail.com>
Date: Wed, 14 Mar 2007 17:47:57 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Basavaraj Patil <basavaraj.patil@nokia.com>
Subject: Re: [16NG] Re: Last Call: draft-ietf-16ng-ipv6-over-ipv6cs (IPv6
Over the IP Specific part of the Packet Convergence sublayer in 802.16
Networks) to Proposed Standard
References: <C21B3FE0.3148E%basavaraj.patil@nokia.com>
In-Reply-To: <C21B3FE0.3148E%basavaraj.patil@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: ipv6@ietf.org, ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>,
16ng@ietf.org
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
<mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org
Basavaraj Patil wrote: > Hello, > > A slightly revised version of the I-D is now available at: > http://people.nokia.net/~patil/IDs/draft-ietf-16ng-ipv6-over-ipv6cs-09.txt > > This revision incorporates changes based on some of the comments made by the > directorate. It will be submitted to the ID repository as soon as the gates > are opened. Raj, is there a plan to deal with the interoperability issue where the AP tells the Station to auto-configure statelessly and the AR tells it statefully? The AP may send REG-RSP telling the Station to use DHCP. The AR may send an RA telling the Station to use SLAAC. There may be an interoperability issue, if the two indicators are different. This issue can of course be considered as a network management issue, where advice could be given to network deployers of AR and AP to configure their networks correctly. And this is a time when both 802.16 is changing (Corrigendum 2 under discussion but still allows AP to indicate to MN what autoconf method to use) and the RA definition is changing (draft-2462bis indicates 'M' flag may not be used, but an 'autonomous' flag instead). What do you think? Do I get this issue correctly? Or is the issue important, less important, etc. Thanks, Alex ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ _______________________________________________ 16NG mailing list 16NG@ietf.org https://www1.ietf.org/mailman/listinfo/16ng
- [16NG] Re: Last Call: draft-ietf-16ng-ipv6-over-i… Basavaraj Patil
- [16NG] Last Call: draft-ietf-16ng-ipv6-over-ipv6c… The IESG
- [16NG] Re: Last Call: draft-ietf-16ng-ipv6-over-i… James Carlson
- Re: [16NG] Re: Last Call: draft-ietf-16ng-ipv6-ov… Alexandru Petrescu
- [16NG] Re: Last Call: draft-ietf-16ng-ipv6-over-i… Basavaraj Patil
- [16NG] Re: Last Call: draft-ietf-16ng-ipv6-over-i… James Carlson
- [16NG] Re: Last Call: draft-ietf-16ng-ipv6-over-i… Basavaraj Patil
- Re: terminology (was: [16NG] Re: Last Call: draft… Alexandru Petrescu
- Re: terminology (was: [16NG] Re: Last Call: draft… Basavaraj Patil
- [16NG] Re: Last Call: draft-ietf-16ng-ipv6-over-i… James Carlson
- Re: terminology (was: [16NG] Re: Last Call: draft… Alexandru Petrescu
- [16NG] RE: Last Call: draft-ietf-16ng-ipv6-over-i… Manfredi, Albert E
- Re: [16NG] Re: Last Call: draft-ietf-16ng-ipv6-ov… Basavaraj Patil
- RE: [16NG] RE: Last Call: draft-ietf-16ng-ipv6-ov… Riegel, Maximilian
- Re: [16NG] Re: Last Call: draft-ietf-16ng-ipv6-ov… Alexandru Petrescu
- re: [16NG] Re: Last Call: draft-ietf-16ng-ipv6-ov… qinxia
- RE: [16NG] Re: Last Call: draft-ietf-16ng-ipv6-ov… qinxia