Re: [16NG] Resolutions to issues raised during 2nd WGLC of I-D draft-ietf-16ng-ipv6-over-ipv6cs-04 [2]

Alexandru Petrescu <alexandru.petrescu@motorola.com> Fri, 12 January 2007 16:57 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H5Pia-0000eI-Kt; Fri, 12 Jan 2007 11:57:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H5PiZ-0000eD-LE for 16ng@ietf.org; Fri, 12 Jan 2007 11:57:27 -0500
Received: from mail119.messagelabs.com ([216.82.241.179]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1H5PiY-0000yr-6o for 16ng@ietf.org; Fri, 12 Jan 2007 11:57:27 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-15.tower-119.messagelabs.com!1168621043!8067058!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 5042 invoked from network); 12 Jan 2007 16:57:23 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-15.tower-119.messagelabs.com with SMTP; 12 Jan 2007 16:57:23 -0000
Received: from az33exr02.mot.com ([10.64.251.232]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l0CGvKVx023534; Fri, 12 Jan 2007 09:57:23 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117]) by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id l0CGvGPe014093; Fri, 12 Jan 2007 10:57:17 -0600 (CST)
Message-ID: <45A7BDEB.1000306@motorola.com>
Date: Fri, 12 Jan 2007 17:57:15 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Basavaraj Patil <basavaraj.patil@nokia.com>
Subject: Re: [16NG] Resolutions to issues raised during 2nd WGLC of I-D draft-ietf-16ng-ipv6-over-ipv6cs-04 [2]
References: <C1CCFB97.2C0AC%basavaraj.patil@nokia.com>
In-Reply-To: <C1CCFB97.2C0AC%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: 97adf591118a232206bdb5a27b217034
Cc: 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

Hi, please allow me to interfere with clarifications.

Basavaraj Patil wrote:
> 
> Comments by Bruno Sousa:
[skip parts I agree]
>> 4) IPv6 link in 802.16 " In 802.16, there exists an L2 Transport 
>> Connection between an MS and a BS which is used to transport user 
>> data, i.e IPv6 packets in this case.  A Transport Connection is 
>> represented by a CID (Connection Identifier) and multiple Transport
>>  Connections can exist between an MS and BS. " I think the first 
>> sentence is somehow contradictory with the rest of the paragraph. 
>> It is possible to have more then one transport connection between 
>> MS and BS. These transport connections are defined on the MAC layer
>>  (L2), so why refer "there exists an L2 Transport Connection?!"
>> 
>> (If my thoughts are correct) I propose to change the first sentence
>>  to:
>> 
>> In 802.16, the Transport Connection between an MS and a BS is used
>>  to transport user data, i.e. IPv6 packets in this case.
> 
> Agreed. Incorporated the proposed sentence.

But there are IPv6 packets that are sent on the Secondary Management
Connection as well (RS/RA at least) 6.3.9.10 802.16e-2005.  I suggest
saying that only _some_ of the IPv6 packets are transported on some 
Transport Connection, or along these lines.

Probably best for reader would be to enumerate the different types of
Connections the SS can handle and where do IPv6 packets appear.  What do
you think?

Alex

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng