IETF Logo Mail Archive

Re: 64bit IIDs are both recommended and required

Nick Hilliard <nick@foobar.org> Sun, 16 July 2017 22:58 UTC

Return-Path: <nick@foobar.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A3C5129562 for <ipv6@ietfa.amsl.com>; Sun, 16 Jul 2017 15:58:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 QOXoqknBPLbp for <ipv6@ietfa.amsl.com>; Sun, 16 Jul 2017 15:58:32 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41C4E12009C for <ipv6@ietf.org>; Sun, 16 Jul 2017 15:58:31 -0700 (PDT)
X-Envelope-To: ipv6@ietf.org
Received: from crumpet.local (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id v6GMwSf3032786 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 16 Jul 2017 23:58:28 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.local
Message-ID: <596BEF93.6080805@foobar.org>
Date: Sun, 16 Jul 2017 23:58:27 +0100
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.15 (Macintosh/20170609)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: David Farmer <farmer@umn.edu>, 6man WG <ipv6@ietf.org>
Subject: Re: 64bit IIDs are both recommended and required
References: <CAN-Dau17W=CYNFzYJoZ=p71kmBEUp3qRWgyU_=OXyYvk==tydQ@mail.gmail.com> <CAN-Dau12zWLVx4_n_n5P5kYSArwAdOxJEtaC4dwhKbrFcffxkA@mail.gmail.com> <e01073f3-f088-71e5-6c60-8e3e847d337f@gmail.com>
In-Reply-To: <e01073f3-f088-71e5-6c60-8e3e847d337f@gmail.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/IoyNjcMM61nSvnUZ6ki-y-p58Wo>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 16 Jul 2017 22:58:34 -0000

Brian E Carpenter wrote:
> This is valid commentary, but I don't want to lose the clarity of the latest
> draft:
> 
>    Interface Identifiers are 64 bit long except if the first three bits
>    of the address are 000, or when the addresses are manually
>    configured, or by exceptions defined in standards track documents.
> 
> At this point I'm completely past caring whether it says "are" or
> "must" or "recommended", as long as all three exceptions are included.

it would be appropriate for the exception list to include any address
assignment mechanism where addresses are assigned by the network (as
opposed to addresses which are self-selected by the host).

Nick

v2.23.0 | Report a Bug | By Email