[16NG] review of the new revision (ipv6 over ipcs)

Jari Arkko <jari.arkko@piuha.net> Tue, 23 January 2007 19:04 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9Qwm-0006Er-LB; Tue, 23 Jan 2007 14:04:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9Qwl-0006EH-2y for 16ng@ietf.org; Tue, 23 Jan 2007 14:04:43 -0500
Received: from p130.piuha.net ([193.234.218.130]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9Qwi-0002UM-Gg for 16ng@ietf.org; Tue, 23 Jan 2007 14:04:43 -0500
Received: from p130.piuha.net (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id B8A1219876D; Tue, 23 Jan 2007 21:04:38 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id 6B32C19876C; Tue, 23 Jan 2007 21:04:38 +0200 (EET)
Message-ID: <45B65C47.9020802@piuha.net>
Date: Tue, 23 Jan 2007 21:04:39 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.9 (X11/20070104)
MIME-Version: 1.0
To: Basavaraj Patil <basavaraj.patil@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: 16ng@ietf.org
Subject: [16NG] review of the new revision (ipv6 over ipcs)
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, all

I reviewed the new version of this spec, and
I'm generally quite happy with it. I found three
small remaining issues which are listed below:
>          +-----+   CID1    +-----+          +-----------+
>          | MS1 |----------/| BS1 |----------|     AR    |-----[Internet <http://tools.ietf.org/html/draft-ietf-16ng-ipv6-over-ipv6cs-06#ref-Internet>]
>          +-----+         / +-----+          +-----------+
>             .           /        ____________
>             .     CIDn /        ()__________()
>          +-----+      /            L2 Tunnel
>          | MSn |-----/
>          +-----+
>
>
>    Figure 5: The IPv6 AR is separate from the BS, which acts as a bridge
>   
The part about the BS acting as a bridge seems surprising.
Is this really the case? A standard bridge function?

>  This
>  section presents a model for the last mile link, i.e. the link to
>  which MSs attach themselves.
I would remove this sentence. You need to explain
how the link looks like from an IP perspective.
And I think you are doing that. Whether there
is a distributed or integrated BS/AR at the other
end is really not a key issue.

>  IEEE
>    802.16 also defines a secondary management connection that can be
>    used for host configuration.  However support for secondary
>    management connections is not mandatory.  A transport connection has
>    the advantage of it being used for host configuration as well as for
>    user data.
Are you specifying something about the use of the
management connections? If not, take it out.

> Each MS belongs to
>    a different link.  No two MSs belong to the same link.
Duplication. Remove the first sentence.

Jari


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