Re: [Autoconf] Working Group Last Call for draft-ietf-autoconf-addr-model-01

Thomas Narten <narten@us.ibm.com> Tue, 05 January 2010 19:58 UTC

Return-Path: <narten@us.ibm.com>
X-Original-To: autoconf@core3.amsl.com
Delivered-To: autoconf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2EF4E3A68DA for <autoconf@core3.amsl.com>; Tue, 5 Jan 2010 11:58:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 ZlJuF5wDmWdG for <autoconf@core3.amsl.com>; Tue, 5 Jan 2010 11:58:21 -0800 (PST)
Received: from e3.ny.us.ibm.com (e3.ny.us.ibm.com [32.97.182.143]) by core3.amsl.com (Postfix) with ESMTP id 50A383A694A for <autoconf@ietf.org>; Tue, 5 Jan 2010 11:58:21 -0800 (PST)
Received: from d01relay07.pok.ibm.com (d01relay07.pok.ibm.com [9.56.227.147]) by e3.ny.us.ibm.com (8.14.3/8.13.1) with ESMTP id o05JmSoU029229 for <autoconf@ietf.org>; Tue, 5 Jan 2010 14:48:28 -0500
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay07.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id o05Jw5AR1429622 for <autoconf@ietf.org>; Tue, 5 Jan 2010 14:58:05 -0500
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.14.3/8.13.1/NCO v10.0 AVout) with ESMTP id o05Jw4wS006862 for <autoconf@ietf.org>; Tue, 5 Jan 2010 14:58:04 -0500
Received: from cichlid.raleigh.ibm.com (sig-9-65-239-33.mts.ibm.com [9.65.239.33]) by d01av04.pok.ibm.com (8.14.3/8.13.1/NCO v10.0 AVin) with ESMTP id o05Jw3Cr006837 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <autoconf@ietf.org>; Tue, 5 Jan 2010 14:58:04 -0500
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.3/8.12.5) with ESMTP id o05Jw3vF025489 for <autoconf@ietf.org>; Tue, 5 Jan 2010 14:58:03 -0500
Message-Id: <201001051958.o05Jw3vF025489@cichlid.raleigh.ibm.com>
To: autoconf@ietf.org
In-reply-to: <3A8500A3-A75A-49A8-B48C-EED53A17E722@computer.org>
References: <3A8500A3-A75A-49A8-B48C-EED53A17E722@computer.org>
Comments: In-reply-to Thomas Heide Clausen <t.clausen@computer.org> message dated "Thu, 10 Dec 2009 02:37:03 +0100."
Date: Tue, 05 Jan 2010 14:58:03 -0500
From: Thomas Narten <narten@us.ibm.com>
Subject: Re: [Autoconf] Working Group Last Call for draft-ietf-autoconf-addr-model-01
X-BeenThere: autoconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Ad-Hoc Network Autoconfiguration WG discussion list <autoconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/autoconf>
List-Post: <mailto:autoconf@ietf.org>
List-Help: <mailto:autoconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jan 2010 19:58:22 -0000

Two comments on this document.

The document uses but does not really define the term "routing
domain". It should define and/or explain what this term means and why
the term is important (in the context of this document).

> 6.1.  IPv6 Model
> 
>    For IPv6, the principles described in Section 4 and Section 5 suggest
>    the following rules:
> 
 ...
>    o  No on-link subnet prefix is configured on this interface.
> 

But:

> 6.2.  IPv4 Model
> 
>    For IPv4, the principles described in Section 4 and Section 5 suggest
>    rules similar to those mentioned for IPv6 in Section 6.1, that are:
> 
...
>    o  Any subnet prefix configured on this interface should be of length
>       /32.

I don't see a lot of difference between an IPv6 "on-link" prefix and
an IPv4 subnet prefix. It doesn't make sense to me that IPv6 and IPv4
are treated differently.

Thomas