RE: comments on draft-kohno-ipv6-prefixlen-p2p-00.txt

Miya Kohno <mkohno@juniper.net> Mon, 09 November 2009 06:47 UTC

Return-Path: <mkohno@juniper.net>
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 AF2D728C16B for <ipv6@core3.amsl.com>; Sun, 8 Nov 2009 22:47:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.799
X-Spam-Level:
X-Spam-Status: No, score=-6.799 tagged_above=-999 required=5 tests=[AWL=-0.800, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_MED=-4]
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 VYLDM1Jt0f67 for <ipv6@core3.amsl.com>; Sun, 8 Nov 2009 22:47:48 -0800 (PST)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by core3.amsl.com (Postfix) with ESMTP id 99C5728C0F8 for <ipv6@ietf.org>; Sun, 8 Nov 2009 22:47:48 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKSve7KrFVKiADE0I4bSRAwFIKMYOohszh@postini.com; Sun, 08 Nov 2009 22:48:15 PST
Received: from EmailHK1.jnpr.net (172.27.128.41) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server id 8.1.375.2; Sun, 8 Nov 2009 22:44:41 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Subject: RE: comments on draft-kohno-ipv6-prefixlen-p2p-00.txt
Date: Mon, 09 Nov 2009 14:44:38 +0800
Message-ID: <AC69DA36E7838140ADA1C2B9026F8DD60A78910B@emailhk1.jnpr.net>
In-Reply-To: <m2k4y0xnrw.wl%jinmei@isc.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: comments on draft-kohno-ipv6-prefixlen-p2p-00.txt
Thread-Index: Acpg/p1t6HHVnGaISjum4nlmceI1/QACLctQ
References: <m2k4y0xnrw.wl%jinmei@isc.org>
From: Miya Kohno <mkohno@juniper.net>
To: JINMEI Tatuya / 神明達哉 <jinmei@isc.org>, Becca Nitzan <nitzan@juniper.net>, randy@psg.com, maz@iij.ad.jp
Cc: 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: Mon, 09 Nov 2009 06:47:49 -0000

Thank you, Tatsuya, for your thorough review. 

I think both of your points are apposite. We'll reflect them into the -01 version.

Thanks again,
Miya 
> -----Original Message-----
> From: JINMEI Tatuya / 神明達哉 [mailto:jinmei@isc.org] 
> Sent: Monday, November 09, 2009 2:37 PM
> To: Miya Kohno; Becca Nitzan; randy@psg.com; maz@iij.ad.jp
> Cc: ipv6@ietf.org
> Subject: comments on draft-kohno-ipv6-prefixlen-p2p-00.txt
> 
> (resending as I seem to have submitted the original one from the wrong
> address)
> 
> I've read this draft.  I don't have a strong opinion on the 
> proposal per se, but have a couple of minor comments:
> 
> 1. In Section 4, the draft says:
> 
>    However, Subnet-router
>    anycast address has not been implemented and in practice, this has
>    not been a problem.
> 
> I'm afraid "has not been implemented" is too strong.  In 
> fact, we have "implemented" it in the KAME/BSD IPv6 stack in 
> that we implemented special restrictions (at that time) on 
> anycast addresses and had experimentally assigned 
> subnet-router anycast addresses on PC-based
> IPv6 routers.  In general, it's difficult to declare 
> something hasn't been implemented because it eliminates any 
> minor implementation activity, which is almost impossible to prove.
> 
> I have no objection to the conclusion itself (i.e. not a problem in
> practice) and would rephrase it to something like this:
> 
>    However, Subnet-router anycast addresses have not been (widely)
>    deployed, and this has not been a problem in practice.
> 
> 2. In section 5, it states:
> 
>          1) A rule described in ICMPv6 [RFC4443] indicates that a
>          Destination Unreachable (Code 3) message should be sent by a
>          router rather than forwarding packets back onto 
> point-to-point
>          links from which they were received if their destination
>          address belongs to the link itself.
> 
> This sentence is clear, but IMO is not perfectly accurate 
> because an address doesn't belong t(or isn't assigned to) a 
> *link*; it's assigned to an interface.  The corresponding 
> text of RFC4443 reads:
> 
>    One specific case in which a Destination Unreachable 
> message is sent
>    with a code 3 is in response to a packet received by a 
> router from a
>    point-to-point link, destined to an address within a 
> subnet assigned
>    to that same link (other than one of the receiving router's own
>    addresses).
> 
> where it's a *subnet* that is assigned to the link.  So, to 
> be very accurate, I'd propose to revise the text (e.g.) as follows:
> 
>          1) A rule described in ICMPv6 [RFC4443] indicates [...]
>          if their destination address matches a subnet that belongs to
>          the link itself.
> 
> ---
> JINMEI, Tatuya
> Internet Systems Consortium, Inc.
>