RE: RFC4291bis
"Manfredi (US), Albert E" <albert.e.manfredi@boeing.com> Wed, 08 August 2018 00:07 UTC
Return-Path: <albert.e.manfredi@boeing.com>
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 0422112DD85 for <ipv6@ietfa.amsl.com>; Tue, 7 Aug 2018 17:07:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 77wnumMHMBBn for <ipv6@ietfa.amsl.com>; Tue, 7 Aug 2018 17:07:33 -0700 (PDT)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net [130.76.184.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BF95128CB7 for <ipv6@ietf.org>; Tue, 7 Aug 2018 17:07:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id w7807VDH038831; Tue, 7 Aug 2018 17:07:31 -0700
Received: from XCH15-01-12.nw.nos.boeing.com (xch15-01-12.nw.nos.boeing.com [137.136.239.188]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id w7807QOo038796 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Tue, 7 Aug 2018 17:07:26 -0700
Received: from XCH15-01-07.nw.nos.boeing.com (137.136.239.154) by XCH15-01-12.nw.nos.boeing.com (137.136.239.188) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Tue, 7 Aug 2018 17:07:25 -0700
Received: from XCH15-01-07.nw.nos.boeing.com ([137.136.239.154]) by XCH15-01-07.nw.nos.boeing.com ([137.136.239.154]) with mapi id 15.00.1367.000; Tue, 7 Aug 2018 17:07:25 -0700
From: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, 6man <ipv6@ietf.org>
Subject: RE: RFC4291bis
Thread-Topic: RFC4291bis
Thread-Index: AQHULqfua9E+o3R8/kKSedfLDVG79aS09Tyw
Date: Wed, 08 Aug 2018 00:07:25 +0000
Message-ID: <3068537452834bab9bc716f4ae775946@XCH15-01-07.nw.nos.boeing.com>
References: <f332beb5-2ee5-c12e-b2b5-d7b1742e4ca0@gmail.com>
In-Reply-To: <f332beb5-2ee5-c12e-b2b5-d7b1742e4ca0@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/bCABpK0Ieo2LM4_cxX8PzFfvjdo>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.27
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: Wed, 08 Aug 2018 00:07:35 -0000
-----Original Message----- From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Brian E Carpenter > NEW: Interface Identifiers for stateless address autoconfiguration are 64 bits 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. The rationale for using 64 bit Interface Identifiers can be found in [RFC7421]. An example of a standards track exception is [RFC6164] that standardises 127 bit prefixes on inter-router point-to-point links. The relationship between prefix length and Interface Identifier length is discussed in [I-D.farmer-6man-exceptions-64]. Note: In the case of manual configuration, the Prefix and Interface Identifier can be any length as long as they add up to 128. In all cases, routing and forwarding processes must be designed to process prefixes of any length up to /128 [BCP198]. But I think those exceptions are not SLAAC-related at all. So perhaps: NEWNEW Interface Identifiers for stateless address autoconfiguration are 64 bits long. Otherwise, IIDs are normally 64 bits 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. ... [Rest same as before.] I'm not sure if there's any reason to mention that these rules only apply to the 2000 prefix. Bert
- RFC4291bis Brian E Carpenter
- RE: RFC4291bis Manfredi (US), Albert E
- Re: RFC4291bis Michael Richardson
- Re: RFC4291bis Brian E Carpenter
- Re: RFC4291bis Brian E Carpenter
- Re: RFC4291bis Brian E Carpenter
- Re: RFC4291bis David Farmer
- Re: RFC4291bis David Farmer
- Re: RFC4291bis Mark Smith
- Re: RFC4291bis David Farmer
- Re: RFC4291bis 神明達哉
- Re: RFC4291bis Brian E Carpenter
- Re: RFC4291bis (historical sub-thread) Brian E Carpenter
- Re: RFC4291bis Brian E Carpenter