Re: <draft-hinden-6man-rfc2464bis-01>
Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 06 July 2017 15:27 UTC
Return-Path: <alexandre.petrescu@gmail.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 106D11201FA for <ipv6@ietfa.amsl.com>; Thu, 6 Jul 2017 08:27:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] 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 8X0daRV1gmTK for <ipv6@ietfa.amsl.com>; Thu, 6 Jul 2017 08:27:44 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 5108712EBF4 for <ipv6@ietf.org>; Thu, 6 Jul 2017 08:27:44 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v66FRgP9003349 for <ipv6@ietf.org>; Thu, 6 Jul 2017 17:27:42 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5B813202D00 for <ipv6@ietf.org>; Thu, 6 Jul 2017 17:27:42 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 526C0202CC3 for <ipv6@ietf.org>; Thu, 6 Jul 2017 17:27:42 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v66FRfUL012530 for <ipv6@ietf.org>; Thu, 6 Jul 2017 17:27:42 +0200
Subject: Re: <draft-hinden-6man-rfc2464bis-01>
To: ipv6@ietf.org
References: <7370FF51-5B19-49BB-A849-435B11F9A2CC@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <5aa80068-1d9d-909a-49db-aa6480a1d268@gmail.com>
Date: Thu, 06 Jul 2017 17:27:41 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <7370FF51-5B19-49BB-A849-435B11F9A2CC@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/buRR067zSquhsztSbLbZwsA3Ews>
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: Thu, 06 Jul 2017 15:27:47 -0000
Hi, There is s typo in there: > 8. Differences from RFC 4291 ^^^^ > > This document has the following changes from RFC2464, "Transmission > of IPv6 Packets over Ethernet Networks ". Numbers identify the > Internet-Draft version that the change was made.: There is a question about this: > 4. Stateless Autoconfiguration > > The default approach to create stable Interface Identifiers > [I-D.ietf-6man-rfc4291bis] for use with SLAAC on an Ethernet > interface should be based on [RFC7217]. > > It is not recommended that Interface Identifiers for an Ethernet > interface be based on stable IEEE MAC-layer addresses. The question is the following: in case I manually change the MAC address on the interface, will SLAAC form a new address based on that MAC address that I create? I am not asking whether it is recommended or not (because I understand the above text recommends against MAC-in-IP). But I am asking whether or not when I manually change the MAC address will SLAAC generate a new address? By 'MAC address' I mean a 48bit number that can be generated out of the blue (1234...), or can be even starting with an OUI reserved in oui.txt. Alex Le 09/01/2017 à 21:24, Bob Hinden a écrit : > Hi, > > I published a new version of rfc2464bis <draft-hinden-6man-rfc2464bis-01>. Links below. > > This draft brings in the two updates and errata. The changes include: > > Incorporate update from draft-ietf-6man-default-iids > (currently in RFC Editor queue). Revised Section 4 to say > IIDs should be formed based on RFC7217 and that it not > recommended to use hardware based IIDs. > > Incorporate update from RFC6085. Added to Section 7 that an > IPv6 multicast packet may be mapped to a unicast Ethernet > Link layer address and that nodes receiving packets with this > address mapping should not drop these packets. > > Updates to resolve the open Errata on RFC2464. These are: > > Errata ID: 430: Correct reference to EUI-64. Note, the > corrected URL specified in the Errata isn't working, the > reference now points to one that does work. > > Errata ID: 4855: This errata is not correct, and will be > marked as rejected. No change is required. Also, the > text that this Errata proposed to change was removed when > the update from draft-ietf-6man-default-iids was > incorporated. > > Editorial changes. > > A diff from the previous version can be found at: > > https://tools.ietf.org/rfcdiff?url2=draft-hinden-6man-rfc2464bis-01.txt > > I plan to send separate emails on each update, explaining the changes and asking a few questions. > > This is part of the project to move the core IPv6 specifications to Internet Standard. > > Thanks, > Bob > >> >> A new version of I-D, draft-hinden-6man-rfc2464bis-01.txt >> has been successfully submitted by Robert M. Hinden and posted to the >> IETF repository. >> >> Name: draft-hinden-6man-rfc2464bis >> Revision: 01 >> Title: Transmission of IPv6 Packets over Ethernet Networks >> Document date: 2017-01-09 >> Group: Individual Submission >> Pages: 9 >> URL: https://www.ietf.org/internet-drafts/draft-hinden-6man-rfc2464bis-01.txt >> Status: https://datatracker.ietf.org/doc/draft-hinden-6man-rfc2464bis/ >> Htmlized: https://tools.ietf.org/html/draft-hinden-6man-rfc2464bis-01 >> Diff: https://www.ietf.org/rfcdiff?url2=draft-hinden-6man-rfc2464bis-01 >> >> Abstract: >> This document specifies the frame format for transmission of IPv6 >> packets and the method of forming IPv6 link-local addresses and >> statelessly autoconfigured addresses on Ethernet networks. It also >> specifies the content of the Source/Target Link-layer Address option >> used in Router Solicitation, Router Advertisement, Neighbor >> Solicitation, Neighbor Advertisement and Redirect messages when those >> messages are transmitted on an Ethernet. >> >> This document replaces RFC 2464 "Transmission of IPv6 Packets over >> Ethernet Networks", which will become historic. >> >> >> >> >> -------------------------------------------------------------------- >> IETF IPv6 working group mailing list >> ipv6@ietf.org >> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 >> --------------------------------------------------------------------
- <draft-hinden-6man-rfc2464bis-01> Bob Hinden
- Re: <draft-hinden-6man-rfc2464bis-01> Alexandre Petrescu