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

Mark Townsley <townsley@cisco.com> Wed, 20 January 2010 18:22 UTC

Return-Path: <townsley@cisco.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 16EF83A6895 for <autoconf@core3.amsl.com>; Wed, 20 Jan 2010 10:22:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.539
X-Spam-Level:
X-Spam-Status: No, score=-10.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 UdoyESPKMmog for <autoconf@core3.amsl.com>; Wed, 20 Jan 2010 10:22:24 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 48BD83A6867 for <autoconf@ietf.org>; Wed, 20 Jan 2010 10:22:23 -0800 (PST)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArcEAFvYVkurR7Ht/2dsb2JhbACBRsM3lVuENgQ
X-IronPort-AV: E=Sophos;i="4.49,311,1262563200"; d="scan'208";a="234152577"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-2.cisco.com with ESMTP; 20 Jan 2010 18:22:19 +0000
Received: from iwan-view3.cisco.com (iwan-view3.cisco.com [171.70.65.13]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o0KIMJiq012116; Wed, 20 Jan 2010 18:22:19 GMT
Received: from Saturn.local (ams3-vpn-dhcp455.cisco.com [10.61.65.199]) by iwan-view3.cisco.com (8.11.2/CISCO.WS.1.2) with ESMTP id o0KIMHW26559; Wed, 20 Jan 2010 10:22:17 -0800 (PST)
Message-ID: <4B5749D8.40503@cisco.com>
Date: Wed, 20 Jan 2010 19:22:16 +0100
From: Mark Townsley <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
References: <3A8500A3-A75A-49A8-B48C-EED53A17E722@computer.org> <201001051958.o05Jw3vF025489@cichlid.raleigh.ibm.com> <4B56E834.4060800@cisco.com> <201001201351.o0KDpCnG015304@cichlid.raleigh.ibm.com>
In-Reply-To: <201001201351.o0KDpCnG015304@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: autoconf@ietf.org, Dave Thaler <dthaler@microsoft.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: Wed, 20 Jan 2010 18:22:25 -0000

cc'ing Dave Thaler directly, I need his advice here. Please see inline...

On 1/20/10 2:51 PM, Thomas Narten wrote:
> Mark,
>
>
>    
>>> 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 think I was the one who actively supported treating IPv6 and IPv4
>> differently in the document. IPv6 has a ULA range, IPv4 doesn't. IPv4
>> has a Private range, IPv6 doesn't.
>>      
> This isn't a real difference. Net 10 is "private" in IPv4 and spans
> multiple links/subnets. That is no different than a ULA in IPv6.
>
> Yes, there are some important differences between ULAs and net 10
> addresses (namely global uniqueness), but that doesn't change how
> prefixes out of those networks are assigned to individual links, and
> whether they are to be treated as being on-link (or not), which is
> what is at issue.
>
>    
>> IPv4 global space is constrained, IPv6 isn't. IPv4 stacks remove
>> IPv4 link-local addresses from an interface when a global or private
>> is assigned, IPv6 stacks do not...  etc... etc... So, while there
>> certainly are commonalities in the models, there are enough
>> differences that describing each model separately seems to reduce
>> the chance of misunderstanding the differences that do exist between
>> one version vs. the other.
>>      
> This doesn't really answer my core question. There is no real
> difference between a /32 in IPv4 and a /128 in IPv6. What is the
> justification for saying /32 should be used in IPv4 but no on-link
> prefix is used in IPv6?
>    
Indeed, in the previous draft we had this text:

>    o  (An IPv6) subnet prefix configured on this interface should be 
> of length
>       /128.
> and
>
>    o  Any (IPv4) subnet prefix configured on this interface should be 
> of length
>       /32.

However, Dave convinced us at the last IETF that the better way in IPv6 
to describe what we really want to say is that on-link subnet prefixes 
should simply not be configured at all. Practically speaking, I don't 
think we have this same luxury in IPv4.

- Mark
> BTW, I'd be fine with having the IPv6 section say on-link with a
> /128. That is what I would have expected for consistency.
>
> I don't think doing this is a big deal, unless you have IPv4 and IPv6
> be different, with no good technical justification, which is how I see
> things at the moment.
>
> Thomas
>
>