Re: 6MAN WG Last Call: <draft-ietf-6man-prefixlen-p2p-00.txt>
Pekka Savola <pekkas@netcore.fi> Fri, 19 November 2010 10:07 UTC
Return-Path: <pekkas@netcore.fi>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D6E13A68D3 for <ipv6@core3.amsl.com>; Fri, 19 Nov 2010 02:07:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h3agOX+I+NrD for <ipv6@core3.amsl.com>; Fri, 19 Nov 2010 02:07:17 -0800 (PST)
Received: from netcore.fi (eunet-gw.ipv6.netcore.fi [IPv6:2001:670:86:3001::1]) by core3.amsl.com (Postfix) with ESMTP id 24A2F3A68AF for <ipv6@ietf.org>; Fri, 19 Nov 2010 02:07:16 -0800 (PST)
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.13.8/8.13.8) with ESMTP id oAJA7t2h024361 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Nov 2010 12:07:55 +0200
Received: from localhost (pekkas@localhost) by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id oAJA7su4024358; Fri, 19 Nov 2010 12:07:54 +0200
Date: Fri, 19 Nov 2010 12:07:54 +0200
From: Pekka Savola <pekkas@netcore.fi>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: 6MAN WG Last Call: <draft-ietf-6man-prefixlen-p2p-00.txt>
In-Reply-To: <49FD0299-C85A-47AA-A349-06837E9B5135@gmail.com>
Message-ID: <alpine.LRH.2.02.1011191150450.23769@netcore.fi>
References: <49FD0299-C85A-47AA-A349-06837E9B5135@gmail.com>
User-Agent: Alpine 2.02 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Virus-Scanned: clamav-milter 0.96.4 at otso.netcore.fi
X-Virus-Status: Clean
Cc: Brian Haberman <brian@innovationslab.net>, 6man Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Nov 2010 10:07:19 -0000
On Thu, 18 Nov 2010, Bob Hinden wrote: > as a Proposed Standard. Substantive comments and statements of > support for advancing this document should be directed to the > mailing list. Editorial suggestions can be sent to the authors. > This last call will end on December 6, 2010. I think the document needs work before it can be progressed. I do think this is a useful document (esp section 5.1 and 5.2). The document should probably mark in its header RFC3627 obsolete, and mark itself as updating RC4291 (in practise Section 6 appears to do so). Section 3, second paragraph does not reflect operational reality: For the purposes of this document, an inter-router point-to-point link is a link to which only two routers and no hosts are attached. This may include Ethernet links which are configured to be point-to- point. In such cases, there is no need to support Neighbor Discovery for address resolution, and other general scenarios like the use of stateless address autoconfiguration are not relevant. .. Please educate me on implementations that allow you to configure Ethernet link as point-to-point (in ifconfig IFFLAGS sense). Section 4 does not describe the root cause (i.e. why /127 can be used successfully) i.e. that Subnet-router anycast addresses have not been implemented, or if they have been implemented, it has been done only with prefixlen=64 (similar to what was suggested in RFC3627 point 4): 4. Problems identified with 127-bit prefix lengths in the past .. Though the analyses in the RFCs are correct, operational experience with IPv6 has shown that /127 prefixes can be used successfully. Section 6 should probably be renamed "Conformance" instead of recommendations (it's giving out MUST advice etc.) I think there will be pushback on the brief security considerations section. I think the document could be clearer wrt terminology of 'point-to-point'. In some context it means a link where there should be only two nodes connected. In some contexts it means a link which by its nature can only have two nodes connected and does not perform neighbor discovery. -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
- 6MAN WG Last Call: <draft-ietf-6man-prefixlen-p2p… Bob Hinden
- Re: 6MAN WG Last Call: <draft-ietf-6man-prefixlen… Randy Bush
- Re: 6MAN WG Last Call: <draft-ietf-6man-prefixlen… Pekka Savola
- Re: 6MAN WG Last Call: <draft-ietf-6man-prefixlen… Brian E Carpenter
- Re: 6MAN WG Last Call: <draft-ietf-6man-prefixlen… Ed Jankiewicz
- Re: 6MAN WG Last Call: <draft-ietf-6man-prefixlen… Randy Bush
- Re: 6MAN WG Last Call: <draft-ietf-6man-prefixlen… Shane Amante
- Re: 6MAN WG Last Call: <draft-ietf-6man-prefixlen… Mark Smith
- RE: 6MAN WG Last Call: <draft-ietf-6man-prefixlen… Miya Kohno
- Re: 6MAN WG Last Call: <draft-ietf-6man-prefixlen… Mark Smith
- RE: 6MAN WG Last Call: <draft-ietf-6man-prefixlen… George, Wes E [NTK]
- Re: 6MAN WG Last Call: <draft-ietf-6man-prefixlen… Randy Bush
- Re: 6MAN WG Last Call: <draft-ietf-6man-prefixlen… Randy Bush
- Re: 6MAN WG Last Call: <draft-ietf-6man-prefixlen… Randy Bush
- RE: 6MAN WG Last Call: <draft-ietf-6man-prefixlen… George, Wes E [NTK]
- RE: 6MAN WG Last Call: <draft-ietf-6man-prefixlen… Miya Kohno