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

JINMEI Tatuya / 神明達哉 <jinmei@isc.org> Wed, 11 November 2009 09:50 UTC

Return-Path: <jinmei@isc.org>
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 F0E9C28C0F4 for <ipv6@core3.amsl.com>; Wed, 11 Nov 2009 01:50:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.675
X-Spam-Level:
X-Spam-Status: No, score=0.675 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, NO_RELAYS=-0.001]
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 jTNr0J0lftGx for <ipv6@core3.amsl.com>; Wed, 11 Nov 2009 01:50:46 -0800 (PST)
Received: from mon.jinmei.org (mon.jinmei.org [IPv6:2001:4f8:3:36::162]) by core3.amsl.com (Postfix) with ESMTP id 576203A687E for <ipv6@ietf.org>; Wed, 11 Nov 2009 01:50:46 -0800 (PST)
Received: from jmb.jinmei.org (unknown [IPv6:2001:dfb:0:16:21b:63ff:fe08:3e64]) by mon.jinmei.org (Postfix) with ESMTPA id CAB8233C3B; Wed, 11 Nov 2009 01:51:10 -0800 (PST)
Date: Wed, 11 Nov 2009 18:51:09 +0900
Message-ID: <m2aaytwfsi.wl%jinmei@isc.org>
From: JINMEI Tatuya / 神明達哉 <jinmei@isc.org>
To: Pekka Savola <pekkas@netcore.fi>
Subject: Re: comments on draft-kohno-ipv6-prefixlen-p2p-00.txt
In-Reply-To: <alpine.LRH.2.00.0911100855200.14440@netcore.fi>
References: <m2ljigxojz.wl%jinmei@isc.org> <alpine.LRH.2.00.0911100855200.14440@netcore.fi>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.1 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="US-ASCII"
Cc: nitzan@juniper.net, randy@psg.com, 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: Wed, 11 Nov 2009 09:50:49 -0000

At Tue, 10 Nov 2009 09:07:52 +0200 (EET),
Pekka Savola <pekkas@netcore.fi> wrote:

> > 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 agree that the wording is a bit strong, and I'm ok with weakening 
> it, but I've yet to see an implementation that enables it by default 
> or even by an enable/disable configuration directive.
> 
> AFAIK, on KAME/BSD it's "implemented" in such a fashion that the 
> operator must manually configure it with "ifconfig".  I wouldn't call 
> that "implemented" myself. At least on my FreeBSD 7.2 router, subnet 
> router anycast address isn't configured automatically and I don't even 
> see system configuration parameters (e.g. in init scripts) which would 
> change this.

I won't try to win the debate of the definition of implementation.
It was not my point that the KAME/BSD may implement it.  The point is
that the original wording of the draft was unnecessarily strong.  And
since we both seem to agree on that point, I think we are done.

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.