RE: Protocol Action: 'Reserved IPv6 Interface Identifiers' to Proposed Standard
"Dunn, Jeffrey H." <jdunn@mitre.org> Sat, 13 December 2008 02:18 UTC
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipngwg-archive@lists.ietf.org
Delivered-To: ietfarch-ipngwg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 78F183A68A4; Fri, 12 Dec 2008 18:18:24 -0800 (PST)
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B6B733A68A4; Fri, 12 Dec 2008 18:18:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 eMHfUFkhgjb4; Fri, 12 Dec 2008 18:18:21 -0800 (PST)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id A0A6B3A67A8; Fri, 12 Dec 2008 18:18:21 -0800 (PST)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id mBD2IEC0005815; Fri, 12 Dec 2008 21:18:15 -0500
Received: from imcfe2.MITRE.ORG (imcfe2.mitre.org [129.83.29.4]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id mBD2IEPA005800; Fri, 12 Dec 2008 21:18:14 -0500
Received: from IMCSRV7.MITRE.ORG ([129.83.20.57]) by imcfe2.MITRE.ORG with Microsoft SMTPSVC(6.0.3790.1830); Fri, 12 Dec 2008 21:18:13 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: Protocol Action: 'Reserved IPv6 Interface Identifiers' to Proposed Standard
Date: Fri, 12 Dec 2008 21:18:11 -0500
Message-ID: <0AC4B700F00DBB4C94F95727E09914140161872E@IMCSRV7.MITRE.ORG>
In-Reply-To: <20081212175407.328433A6B08@core3.amsl.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Protocol Action: 'Reserved IPv6 Interface Identifiers' to Proposed Standard
Thread-Index: AclcgueRjuw4S/YVQGKiI5Lt1k7O7wARXxeQ
References: <20081212175407.328433A6B08@core3.amsl.com>
From: "Dunn, Jeffrey H." <jdunn@mitre.org>
To: The IESG <iesg-secretary@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-OriginalArrivalTime: 13 Dec 2008 02:18:13.0928 (UTC) FILETIME=[0D5EFA80:01C95CC9]
Cc: 6man chair <6man-chairs@tools.ietf.org>, 6man mailing list <ipv6@ietf.org>, Steve_Eiserman@ao.uscourts.gov, Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org
Colleagues, I have a question about the following language in section 2.0: "For all unicast addresses, except those that start with the binary value 000, Interface IDs are required to be 64 bits long and to be constructed in Modified EUI-64 format. " Although I do not see a MUST in this sentence, it appears that the proposed standard is mandating that all interface IDs be 64-bits long. This is not a requirement in several RFCs listed below. As a result, I believe that this requirement should be stricken from the document. RFC 2460, 5095 RFC 2463, 4443, 4884 RFC 2461, 3971, 4861 RFC 2462, 4862, 4941 RFC 3315, 3633, 3736, 4361 RFC 1981 RFC 2526, 3879, 4007, 4291 RFC 2671, 3596, 3986 RFC 3493, 3542, 3678, 4584, 5014 RFC 2740, 4552 RFC 1772, 2545, 4271, 4760 RFC 3948, 4301, 4302, 4303, 4308, 4809 RFC 4306, 4307, 4945 RFC 4213 RFC 2573, 2784, 4891 RFC 4798 RFC 3411, 3412, 3413, 3414 RFC 3289, 4022, 4087, 4113, 4292, 4293, 4295, 4807 RFC 3810, 4604 RFC 4601, 4609 RFC 2474, 2475, 2597, 2983, 3086, 3140, 3168, 3246, 3247, 3260, 3494 RFC 5072 Best Regards, Jeffrey Dunn Info Systems Eng., Lead MITRE Corporation. (301) 448-6965 (mobile) -----Original Message----- From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of The IESG Sent: Friday, December 12, 2008 12:54 PM To: IETF-Announce Cc: 6man chair; Internet Architecture Board; 6man mailing list; RFC Editor Subject: Protocol Action: 'Reserved IPv6 Interface Identifiers' to Proposed Standard The IESG has approved the following document: - 'Reserved IPv6 Interface Identifiers ' <draft-ietf-6man-reserved-iids-03.txt> as a Proposed Standard This document is the product of the IPv6 Maintenance Working Group. The IESG contact persons are Jari Arkko and Mark Townsley. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-6man-reserved-iids-03.tx t Technical Summary Interface Identifiers in IPv6 unicast addresses are used to identify interfaces on a link. They are required to be unique within a subnet. Several RFCs have specified interface identifiers or identifier ranges that have a special meaning attached to them. An IPv6 node autoconfiguring an interface identifier in these ranges will encounter unexpected consequences. Since there is no centralized repository for such reserved identifiers, this document aims to create one. Working Group Summary The 6MAN working group has done extensive reviews of this document and it reflects the consensus of the working group. Document Quality This document has been reviewed by numerous members of the ipv6@ietf.org mailing list and by the 6MAN WG chairs. Personnel Brian Haberman is the Document Shepherd, and Jari Arkko is the responsible Area Director. RFC Editor Note Make this change in Appendix A: OLD: The following RFCs that generate interface identifiers need to be updated if they wish to avoid conflicts with the reserved interface identifier ranges. NEW: Implementations of the following RFCs need to be aware of the reserved interface identifier ranges when they allocate new addresses. Future revisions of these RFCs should ensure that this is either already sufficiently clear or that the text is amended to take this into account. -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 -------------------------------------------------------------------- -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
- Protocol Action: 'Reserved IPv6 Interface Identif… The IESG
- RE: Protocol Action: 'Reserved IPv6 Interface Ide… Dunn, Jeffrey H.
- Re: Protocol Action: 'Reserved IPv6 Interface Ide… Brian E Carpenter
- Re: Protocol Action: 'Reserved IPv6 Interface Ide… Jari Arkko
- RE: Protocol Action: 'Reserved IPv6 Interface Ide… Dunn, Jeffrey H.
- RE: Protocol Action: 'Reserved IPv6 Interface Ide… Templin, Fred L
- RE: Protocol Action: 'Reserved IPv6 Interface Ide… Dunn, Jeffrey H.
- Re: Protocol Action: 'Reserved IPv6 Interface Ide… Thomas Narten
- Re: Protocol Action: 'Reserved IPv6 Interface Ide… Brian Haberman