Re: Link addressing

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 25 March 2014 01:48 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAFE11A008D for <ipv6@ietfa.amsl.com>; Mon, 24 Mar 2014 18:48:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4
X-Spam-Level:
X-Spam-Status: No, score=-4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CIAuf2DGVmMI for <ipv6@ietfa.amsl.com>; Mon, 24 Mar 2014 18:48:52 -0700 (PDT)
Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 4B9FD1A0079 for <ipv6@ietf.org>; Mon, 24 Mar 2014 18:48:52 -0700 (PDT)
Received: by mail-pa0-f48.google.com with SMTP id hz1so6232416pad.7 for <ipv6@ietf.org>; Mon, 24 Mar 2014 18:48:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=6aKk6tVXeImQ5rr4wWCEJictvFgLJZ0JCGlq4anLIiE=; b=IHWpUbBKyn1SN6iZox2OTTT2eBh6AUDR19HAw+CA/ji+C0w8LaLZRD8wiDvbtX3YbG Z3a1cZTOXfEfVmZhWGy7gxiM/Wga8IrrpIAvJK6/ckILl/Yh3Hg8AYEiW3Z2eDHzr4n3 O1CWyXwA99yeta4hRiIM08khKIZ/XUSnXLuZZ1W7VXHMtwRM2UGXyJxvjpEZnGQbv/r9 IRCQH0gB1sK7ZeW2GwuugEvoOeUwV4ghO9kp/gvZZZoogjaBmCBjG74tW8yTKYnnr41N 8dXn9g4VI08l2u35vbNxew2VvG7h7n7We6dITTp7eFJtU5BwXSshANWwGGIwGuc3cuja 5zlQ==
X-Received: by 10.66.149.7 with SMTP id tw7mr75718445pab.72.1395712131469; Mon, 24 Mar 2014 18:48:51 -0700 (PDT)
Received: from [192.168.178.23] (193.198.69.111.dynamic.snap.net.nz. [111.69.198.193]) by mx.google.com with ESMTPSA id vf7sm37351197pbc.5.2014.03.24.18.48.48 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 24 Mar 2014 18:48:50 -0700 (PDT)
Message-ID: <5330E081.70005@gmail.com>
Date: Tue, 25 Mar 2014 14:48:49 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>
Subject: Re: Link addressing
References: <E2C06D73-99FF-42B5-A3BE-337C307BCB0E@gmail.com> <84411F3C-455C-4382-88E2-8EE397A907B9@gdt.id.au> <0E222788-7CDA-4962-B03B-BD069956A471@employees.org> <5AFA59A4-A4F1-48C4-B402-0CAA1E752ED1@gdt.id.au> <862E0FF1-09B6-46DE-83E2-BA3AF3512895@employees.org>
In-Reply-To: <862E0FF1-09B6-46DE-83E2-BA3AF3512895@employees.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/Mjj-kTHLnoCf-xXAcHxVsRDANrY
Cc: RJ Atkinson <rja.lists@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 25 Mar 2014 01:48:55 -0000

On 24/03/2014 23:26, Ole Troan wrote:
> Glen,
> 
>>> that seems like a misunderstanding. manual configuration of addresses has always been part of the IPv6 addressing architecture.
>> Hello Ole,
>>
>> It's not a statically addressed subnet, it's a EUI-64 autoconf subnet.
> 
> routers (as defined in RFC4861) don't autoconfigure addresses using SLAAC. that's a host function.
> a router may automatically create an EUI-64 based interface-id, but this is based on configuration, not on SLAAC.
> on an IPv6 link there are many ways of creating interface-identifiers. manually configured, EUI-64, random, etc. all of these can co-exist on a link.

I suspect that needs to be written in bold letters in many
places. Unfortunately the mandatory language of RFC 2464 has
often been interpreted as meaning more than was intended.

    Brian

>> Operationally it is extremely useful to select the router's address, overriding autoconf for that address whilst allowing other machines to autoconf as per usual. Autoconfing the router's address escalates a simple "remote hands card replacement" into "engineer to examine configuration and test operation of all IPv6 router features after card replacement" because of the possibility that the interface's address is mentioned in the router's configuration (ACLs, source address for protocols, etc).
> 
> yes, indeed. I configure most of my router interfaces with interface-id <prefix>::1.
> there is obviously nothing prohibiting that in the IPv6 addressing architecture, nor has anything around that changed, or dare I say will ever change.
> 
> cheers,
> Ole
> 
> 
> ------------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------