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

Thomas Heide Clausen <ietf@thomasclausen.org> Thu, 07 January 2010 12:47 UTC

Return-Path: <ietf@thomasclausen.org>
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 442883A6835 for <autoconf@core3.amsl.com>; Thu, 7 Jan 2010 04:47:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.98
X-Spam-Level:
X-Spam-Status: No, score=-2.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
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 eXedR+P0rlw4 for <autoconf@core3.amsl.com>; Thu, 7 Jan 2010 04:47:02 -0800 (PST)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 913A93A67AA for <autoconf@ietf.org>; Thu, 7 Jan 2010 04:47:02 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 4D0074300A3; Thu, 7 Jan 2010 04:47:01 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.216.22.248] (unknown [80.10.46.72]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTP id 9B6374300A0; Thu, 7 Jan 2010 04:47:00 -0800 (PST)
References: <3A8500A3-A75A-49A8-B48C-EED53A17E722@computer.org> <201001051958.o05Jw3vF025489@cichlid.raleigh.ibm.com>
Message-Id: <D2375F20-6EEF-4987-BEFE-876658767D54@thomasclausen.org>
From: Thomas Heide Clausen <ietf@thomasclausen.org>
To: Thomas Narten <narten@us.ibm.com>
In-Reply-To: <201001051958.o05Jw3vF025489@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
X-Mailer: iPhone Mail (7D11)
Mime-Version: 1.0 (iPhone Mail 7D11)
Date: Thu, 7 Jan 2010 13:47:46 +0100
Cc: "autoconf@ietf.org" <autoconf@ietf.org>
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: Thu, 07 Jan 2010 12:47:03 -0000

Hi Thomas,

Thanks for your review.

Happy new year.

I  will comment on one thing in your email, leaving the "routing  
domain" discussion for elsewhere.

On 5 Jan 2010, at 20:58, Thomas Narten <narten@us.ibm.com> wrote:
>

<snip>

>
>> 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.
>

I believe that Dave Thaler mentioned that there in no definition of an  
"on link prefix" for IPv4, and that this is the reason for the text  
being thus different for v4 and v6.

Thomas


> Thomas
> _______________________________________________
> Autoconf mailing list
> Autoconf@ietf.org
> https://www.ietf.org/mailman/listinfo/autoconf