Re: some thoughts on IPv6-over-IPv6CS (was: [16NG] Re: review of the new revision (ipv6 over ipcs))
"JinHyeock Choi" <jinchoe@gmail.com> Thu, 25 January 2007 07:52 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1H9zOt-0001vh-HK; Thu, 25 Jan 2007 02:52:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1H9zOr-0001vV-JK
for 16ng@ietf.org; Thu, 25 Jan 2007 02:52:01 -0500
Received: from ug-out-1314.google.com ([66.249.92.171])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9zOq-0002V2-9w
for 16ng@ietf.org; Thu, 25 Jan 2007 02:52:01 -0500
Received: by ug-out-1314.google.com with SMTP id 72so344447ugd
for <16ng@ietf.org>; Wed, 24 Jan 2007 23:51:59 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
b=eduwDtb2g0wVD1ruFSDw5Fojrgv3/ED59sesgRRbbjbT3iSDS3Il3LIYgPGHtqo1LnWYfkWOt9efCTjaZtZcvL2Xpl2QR4kPiXv0bHMWMi1SomRRSkmqFTdJA/cTuXEx3hY9FKstUERu8unc4+A5AuHJ0SsZ5q0yu15VbYHIzAQ=
Received: by 10.82.182.8 with SMTP id e8mr757193buf.1169711519160;
Wed, 24 Jan 2007 23:51:59 -0800 (PST)
Received: by 10.48.217.12 with HTTP; Wed, 24 Jan 2007 23:51:59 -0800 (PST)
Message-ID: <92e919fb0701242351x4d1e4b4al5f080c5e0503a376@mail.gmail.com>
Date: Thu, 25 Jan 2007 16:51:59 +0900
From: "JinHyeock Choi" <jinchoe@gmail.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
Subject: Re: some thoughts on IPv6-over-IPv6CS (was: [16NG] Re: review of the
new revision (ipv6 over ipcs))
In-Reply-To: <45B7AA42.7010004@motorola.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <C1DBCA4E.2CCDA%basavaraj.patil@nokia.com>
<45B7AA42.7010004@motorola.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
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
Dear Alex Kindly find my in-line comments. > >>> 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. > >> > > > > Not really specifying anything w.r.t the management connection. This > > came up during discussion with Alex Petrescu and I added it just for > > the sake of completeness. Within the scope of this I-D, the > > management connection has no relevance. I can take it out. > > Yes, the issue is that 802.16 recommends the RS/RA to happen on a > Secondary Management Connection (instead of on a Transport Connection). > Clarifications on the list suggested that probably nobody uses a SMC. > But that doesn't mean that the IEEE spec isn't saying so. As of my knowledge, 802.16 doesn't mandate which connection to use for RS/RA. Actually in the beginning of IPv6 over 802.16 IP CS work, we gave much thought on which connection to use for Neighbor Discovery messages such as RS/ RA or NS/ NA. (because those messages can carry multicast destination address and unspecified source address, special features are required for the connection.) Unfortunately 802.16 spec is not perfectly clear about this. While there are a few vague statements which may be interpreted to recommend the Secondary Management Connection, upon discussing with 802.16 & WiMAX people, we found out that neither the statements were written with that intention nor the actual 802.16 SS and BS were implemented that way. Transport Connection (especially Initial Service Flow for WiMAX case) is universally agreed as long as our experience & knowledge goes. If there is something missing or wrong, kindly let me know. Thanks for your kind consideration. Best Regards JinHyeock _______________________________________________ 16NG mailing list 16NG@ietf.org https://www1.ietf.org/mailman/listinfo/16ng
- [16NG] review of the new revision (ipv6 over ipcs) Jari Arkko
- [16NG] Re: review of the new revision (ipv6 over … Basavaraj Patil
- Re: some thoughts on IPv6-over-IPv6CS (was: [16NG… Alexandru Petrescu
- Re: some thoughts on IPv6-over-IPv6CS (was: [16NG… Basavaraj Patil
- Re: some thoughts on IPv6-over-IPv6CS (was: [16NG… JinHyeock Choi
- Re: some thoughts on IPv6-over-IPv6CS (was: [16NG… Alexandru Petrescu
- [16NG] Re: some thoughts on IPv6-over-IPv6CS Alexandru Petrescu
- Re: some thoughts on IPv6-over-IPv6CS (was: [16NG… Syam Madanapalli
- [16NG] Re: some thoughts on IPv6-over-IPv6CS JinHyeock Choi
- [16NG] Re: some thoughts on IPv6-over-IPv6CS Jari Arkko
- [16NG] Re: some thoughts on IPv6-over-IPv6CS Alexandru Petrescu