Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard

JORDI PALET MARTINEZ <> Tue, 14 February 2017 15:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DFF48129459 for <>; Tue, 14 Feb 2017 07:55:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key); domainkeys=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id GtxGeOJjitFq for <>; Tue, 14 Feb 2017 07:55:39 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4808D126CD8 for <>; Tue, 14 Feb 2017 07:55:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple;; s=MDaemon; t=1487087608; x=1487692408; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=e7hvvC91v+Psesf+k8R72vAFN 735HCD9ztaONUFqh4I=; b=hXRmHZgfeyosr/AGhXZENb6ci1Pm5Pr5vm1n7Kmu2 lqZz/YLA/sOwSfBYSHlQRj76mJuZKChNaXvB49vkj5RgfoSuhEyN2FAzp3XgDozx Yei5VrmgCyu86VKWZjUsfa8bR5NKu1N71tr+QOfZPTDhVOPe1uQsgPTjkV4tKHBz Go=
DomainKey-Signature: a=rsa-sha1; s=MDaemon;; c=simple; q=dns; h=from:message-id; b=WKb81CBBIgS6RtaDImN6yBXPYHtMlD1SIqulcq2CvZps0R+QqFfzOPVHn97A uFBZj73qsLjErpbPH3ZTkOi2ziCH99IyZ6TVKgd2ppM8t727ojA17/w38 DYpFFQHebgJxbsIMZqGDzMMopBOSL+atxE+9nL1HDWqOFC/05LO/W0=;
X-MDAV-Processed:, Tue, 14 Feb 2017 16:53:28 +0100
X-Spam-Processed:, Tue, 14 Feb 2017 16:53:26 +0100
Received: from [] by (MDaemon PRO v11.0.3) with ESMTP id md50005367310.msg for <>; Tue, 14 Feb 2017 16:53:25 +0100
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-HashCash: 1:20:170214:md50005367310::PIsHnlGFEoppyelo:00000BVd
User-Agent: Microsoft-MacOutlook/f.1e.0.170107
Date: Tue, 14 Feb 2017 16:53:24 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: <>, <>, 6man WG <>, IETF-Discussion Discussion <>
Message-ID: <>
Thread-Topic: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
References: <> <> <> <>
In-Reply-To: <>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 14 Feb 2017 15:55:41 -0000

Agree, we shouldn’t change that. Must be 64 bits.


-----Mensaje original-----
De: ietf <> en nombre de David Farmer <>
Responder a: <>
Fecha: martes, 14 de febrero de 2017, 16:27
Para: Brian E Carpenter <>
CC: <>rg>, <>rg>, 6man WG <>rg>, IETF-Discussion Discussion <>
Asunto: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard

    Actually, in addition to your text there still needs to be a recommendation for 64 bit IIDs in all other cases.  64 bit IIDs are(and should remain) the norm for IPv6, I do not want to change that.  But the current language say IIDs are always 64 bit except when an address begins with binary 000, leaving no room for any other exception.  And this is plainly incorrect, I provided two clear exceptions that are already standardized.  Furthermore, IIDs other than 64 bits are in operational use, with manual configuration and DHCPv6.  
    So I'd suggest;
    However, the Interface ID of unicast addresses used for
    Stateless Address Autoconfiguration [RFC4862] is required
    to be 64 bits long, in all other cases it is recommended to 
    be 64 bits long.  
    The other option is to enumerate all the exceptions, requiring the document to be updated every time a new exception is standardized.
    On Mon, Feb 13, 2017 at 4:53 PM, Brian E Carpenter <> wrote:
    At an earlier stage I suggested restricting the applicability
    of the "However..." sentence to SLAAC [RFC4862]. A short way
    of doing this would be
    However, the Interface ID of unicast addresses used for
    Stateless Address Autoconfiguration [RFC4862] is required
    to be 64 bits long.
    On 14/02/2017 11:32, David Farmer wrote:
    > I have concerns with the following text;
    >    IPv6 unicast routing is based on prefixes of any valid length up to
    >    128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
    >    on inter-router point-to-point links. However, the Interface ID of
    >    all unicast addresses, except those that start with the binary value
    >    000, is required to be 64 bits long.  The rationale for the 64 bit
    >    boundary in IPv6 addresses can be found in [RFC7421]
    > The third sentence seems to limit exceptions to 64 bit IIDs to exclusively
    > addresses that start with binary vale of 000.  There are at least two other
    > exceptions from standards track RFCs, that should be more clear accounted
    > for in this text.  First is [RFC6164] point-to-point links, as mentioned in
    > the previous sentence.  I think the clear intent of [RFC6164] is to allow
    > one(1) Bit IIDs for point to point-to-point links using any Global Unicast
    > Address, not just those that start with 000.  Second is, [RFC6052], which
    > updates [RFC4921] and seems to allow 32 bit IIDs or /96 prefixes for any
    > Global Unicast Address when used for IPv4/IPv6 translation, referred to as
    > ""Network-Specific Prefix" unique to the organization deploying the address
    > translators," in section 2.2 of [RFC6052].
    > Thanks.
    > On Wed, Feb 1, 2017 at 5:51 PM, The IESG <> wrote:
    >> The IESG has received a request from the IPv6 Maintenance WG (6man) to
    >> consider the following document:
    >> - 'IP Version 6 Addressing Architecture'
    >>   <draft-ietf-6man-rfc4291bis-07.txt> as Internet Standard
    >> The IESG plans to make a decision in the next few weeks, and solicits
    >> final comments on this action. Please send substantive comments to the
    >> mailing lists by 2017-03-01. Exceptionally, comments may be
    >> sent to instead. In either case, please retain the
    >> beginning of the Subject line to allow automated sorting.
    >> Abstract
    >>    This specification defines the addressing architecture of the IP
    >>    Version 6 (IPv6) protocol.  The document includes the IPv6 addressing
    >>    model, text representations of IPv6 addresses, definition of IPv6
    >>    unicast addresses, anycast addresses, and multicast addresses, and an
    >>    IPv6 node's required addresses.
    >>    This document obsoletes RFC 4291, "IP Version 6 Addressing
    >>    Architecture".
    >> The file can be obtained via
    >> IESG discussion can be tracked via
    >> No IPR declarations have been submitted directly on this I-D.
    >> --------------------------------------------------------------------
    >> IETF IPv6 working group mailing list
    >> Administrative Requests:
    >> --------------------------------------------------------------------
    > --------------------------------------------------------------------
    > IETF IPv6 working group mailing list
    > Administrative Requests:
    > --------------------------------------------------------------------
    David Farmer      <>
    Networking & Telecommunication Services
    Office of Information Technology
    University of Minnesota   
    2218 University Ave SE        Phone: 612-626-0815
    Minneapolis, MN 55414-3029   Cell: 612-812-9952

IPv4 is over
Are you ready for the new Internet ?
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.