[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
James Carlson <james.d.carlson@sun.com> Wed, 14 March 2007 16:26 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 1HRWIv-0005yA-7H; Wed, 14 Mar 2007 12:26:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1HRW77-0004TA-Es; Wed, 14 Mar 2007 12:14:09 -0400
Received: from sca-ea-mail-4.sun.com ([192.18.43.22])
by ietf-mx.ietf.org with esmtp (Exim 4.43)
id 1HRW74-0005xQ-0V; Wed, 14 Mar 2007 12:14:09 -0400
Received: from eastmail2bur.East.Sun.COM ([129.148.13.40])
by sca-ea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
l2EGE52S026458; Wed, 14 Mar 2007 16:14:05 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
by eastmail2bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with
ESMTP id l2EGE4mS023610; Wed, 14 Mar 2007 12:14:04 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
by phorcys.east.sun.com (8.14.0+Sun/8.14.0) with ESMTP id
l2EGE4ZB011574; Wed, 14 Mar 2007 12:14:04 -0400 (EDT)
Received: (from carlsonj@localhost)
by phorcys.east.sun.com (8.14.0+Sun/8.14.0/Submit) id l2EGE4CF011571;
Wed, 14 Mar 2007 12:14:04 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17912.8012.320182.743610@gargle.gargle.HOWL>
Date: Wed, 14 Mar 2007 12:14:04 -0400
From: James Carlson <james.d.carlson@sun.com>
To: Basavaraj Patil <basavaraj.patil@nokia.com>
In-Reply-To: <C21B3FE0.3148E%basavaraj.patil@nokia.com>
References: <E1HQlyH-0006lc-EJ@stiedprstage1.ietf.org>
<C21B3FE0.3148E%basavaraj.patil@nokia.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
X-Mailman-Approved-At: Wed, 14 Mar 2007 12:26:19 -0400
Cc: ipv6@ietf.org, ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>,
16ng@ietf.org
Subject: [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
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 writes: > 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 I've read through the document as well as (most of) the mailing list discussion, and I don't see anything that directly addresses one possible issue here. That issue is the exclusive use of IPv4 or IPv6 on Packet CS. Why must it be exclusive? The first four bits of the datagram tell you conclusively whether you're looking at IPv4 or IPv6, so why is strict segregation needed? Can't both run on the same link? (I'm also a bit concerned that this proposal will end up rediscovering RFC 1547 over time, as other unnegotiated point-to-point mechanisms have in the past, and the reasons why PPP's negotiation exists. I'm certainly not arguing for the use of PPP over Ethernet CS -- that'd be worse still -- but I think the IEEE may have made a mistake in defining an IP Packet CS rather than a PPP Packet CS.) -- James Carlson, Solaris Networking <james.d.carlson@sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ 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