Re: <draft-ietf-6man-default-iids> update to rfc2464bis

Bob Hinden <bob.hinden@gmail.com> Thu, 12 January 2017 23:57 UTC

Return-Path: <bob.hinden@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 9EA2C1294EB for <ipv6@ietfa.amsl.com>; Thu, 12 Jan 2017 15:57:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 512YUpgQUerk for <ipv6@ietfa.amsl.com>; Thu, 12 Jan 2017 15:57:41 -0800 (PST)
Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A8E6129434 for <ipv6@ietf.org>; Thu, 12 Jan 2017 15:57:41 -0800 (PST)
Received: by mail-qk0-x22b.google.com with SMTP id a20so38479782qkc.1 for <ipv6@ietf.org>; Thu, 12 Jan 2017 15:57:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=xuzOfyQaPBxlLSaexFYy1Cox4Bv6jcw0UhngjEZ8bb8=; b=ckhIVyIdewuDFhkhBC1szU9znW25i0aPOKAhq1pnaMtx5SDVyDAJaPmIXzh15GUMMZ SB7x7URZ9J6vs9UqJDhco5DJz4H4v4fT2pTiz2SQQ/tr/X8nu5OwnnJzr4/HhyZbLRYl GNBthw3k7DL4cN8BDXYiiiG6qgVajt5RxynLSEPUji6Ct+icLMxubmDsmANDuCf7s+W8 fT6AcK2UPn4ADabdNNM/+VI4d2YxUatvuJd8pEEi9sI/sMAuxv7gJYZF8mGCx3KHPIcv 1XKo2BEhJ3rAsbY0LgDhpiacwYcg5Bi49ukBmEXPQ5MxQCyBoGCSQjFoMaW+G0NYyCxV KOGw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=xuzOfyQaPBxlLSaexFYy1Cox4Bv6jcw0UhngjEZ8bb8=; b=fY9PbIAj0+vKiIRU7SHLBWmqeuxH/awFDGcZbu5s692VrtEjP9wjDf06mZKsiZk4k5 8sT5tbaJY7cB7tGlkUmIZMbkyDwWYNW/UCGDHpi79b+pl91OxRdFix3m3cCGdS6C7Fg9 sLQOzw9WWcbiFEwJe98NmGaPVYlOKMltK0tpndSXe+6RJE+3V2EzMSBY0Dd52MjL/wXz qkchD3J1FDmdX+g4+17jIxDrPNI/BoP77/TmHh6XF6ibEHhIagjFG0LbXbdZtilErdWu KeQOXHhDD12RWwVJAnXKMVQgQnWuKReUI35XK+hBbkHVBSTqz6YJVumttRyo70QsIR/+ Y7ng==
X-Gm-Message-State: AIkVDXLUW/9U/fAvo+q9zvTFtn7QBOUT3GvJ9NtIYZeFSSbLM7K5D0oJg0rp95D7bfrIsQ==
X-Received: by 10.55.86.196 with SMTP id k187mr17026419qkb.203.1484265460237; Thu, 12 Jan 2017 15:57:40 -0800 (PST)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id d20sm7847834qtb.17.2017.01.12.15.57.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Jan 2017 15:57:38 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: <draft-ietf-6man-default-iids> update to rfc2464bis
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <CAKD1Yr0O6gnXZc3qEY7bqkBYu-sx1_erwum2DRwpe+Vv+jmdiw@mail.gmail.com>
Date: Thu, 12 Jan 2017 15:57:36 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <30097699-804D-40EA-8EAE-6D4745FE5E5C@gmail.com>
References: <1E7F90AC-79BB-49BE-B397-EC829EA95AA4@gmail.com> <CAKD1Yr0O6gnXZc3qEY7bqkBYu-sx1_erwum2DRwpe+Vv+jmdiw@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/GtVA8BT_xZrJtuQgE9RjVpG1fM8>
Cc: IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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, 12 Jan 2017 23:57:42 -0000

Lorenzo,

> On Jan 11, 2017, at 9:21 PM, Lorenzo Colitti <lorenzo@google.com> wrote:
> 
> On Tue, Jan 10, 2017 at 5:40 AM, Bob Hinden <bob.hinden@gmail.com> wrote:
>    It is not recommended that Interface Identifiers for an Ethernet
>    interface be based on IEEE MAC-layer addresses.
> 
> Please include the word "stable" in this sentence. (See below.)

I agree, this is consistent with draft-ietf-6man-default-iids.

>    Earlier versions of
>    this document described a method of forming interface identifiers
>    derived from IEEE MAC-layer addresses called Modified EUI-64 format.
>    This is described in Appendix A of [I-D.ietf-6man-rfc4291bis] and is
>    no longer recommended.
> 
> Based on my reading of draft-ietf-6man-default-iids-16 , it's not correct to say that this approach is "not recommended". This approach is not recommended for use with stable MAC addresses, but there is no recommendation against using it for non-stable MAC addresses. We do recommended that nodes use RFC7217 addresses by default, but only if the node wishes to create stable addresses, and there is no requirement that a node do so.

Would it be better to say (incorporating the change above):

   It is not recommended that Interface Identifiers for an Ethernet
   interface be based on stable IEEE MAC-layer addresses.  Earlier versions of
   this document described a method of forming interface identifiers
   derived from stable IEEE MAC-layer addresses called Modified EUI-64 format.
   This is described in Appendix A of [I-D.ietf-6man-rfc4291bis] and is
   no longer recommended.

That is, add “stable”.

Would it then make sense to be explicit to add a new sentence like:

   This approach may be used to create Interface Identifiers based on non-stable (e.g.,
   random) IEEE Mac-layer addresses.

with a reference to the appropriate IEEE specification.

Thanks,
Bob