IETF Logo Mail Archive

Re: Last Call: <draft-ietf-6man-default-iids-16.txt> (Recommendation on Stable IPv6 Interface Identifiers) to Proposed Standard

worley@ariadne.com (Dale R. Worley) Fri, 25 November 2016 15:13 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D8EA129F03 for <ietf@ietfa.amsl.com>; Fri, 25 Nov 2016 07:13:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level:
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no 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 C_vc7hl8BlM3 for <ietf@ietfa.amsl.com>; Fri, 25 Nov 2016 07:13:48 -0800 (PST)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (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 B03C212A5AB for <ietf@ietf.org>; Fri, 25 Nov 2016 06:55:38 -0800 (PST)
Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-10v.sys.comcast.net with SMTP id AHuac7ye6RingAHuccbpRf; Fri, 25 Nov 2016 14:55:38 +0000
Received: from hobgoblin.ariadne.com ([198.40.235.178]) by resomta-ch2-05v.sys.comcast.net with SMTP id AHsUc1ZhH7bz5AHsXcOy9G; Fri, 25 Nov 2016 14:53:36 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id uAPErOVn022853; Fri, 25 Nov 2016 09:53:24 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id uAPErOHi022850; Fri, 25 Nov 2016 09:53:24 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: IETF-Announce <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-6man-default-iids-16.txt> (Recommendation on Stable IPv6 Interface Identifiers) to Proposed Standard
Sender: worley@ariadne.com
Date: Fri, 25 Nov 2016 09:53:24 -0500
Message-ID: <87a8cnr4pn.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfK72nSRcSGwxEvu72SnaJjw7ogQk2tvwsGB9U1mJKM4XCskg+5UTquobjyuW0xgT1RhBYPf92xIaaskns1MOdgSy8zvTI6O1GjIa0///VCPj3TJUUVki Nv8hvyc4q88/xJmk27dW8dBWL7pIXIpt/vmtx8sPjnUY8hnnYY7lCXgUBGAG9rod/bb1LETneW/TSDJn0VTJWjGe0fevsh9VG4EXD1x/FzzUdMN2GU1oPZyu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UMKRGQgdVLC8Mg-k5u55LLXwsoE>
Cc: draft-ietf-6man-default-iids@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Nov 2016 15:13:49 -0000

Just a couple of places where the text could be made clearer:

In the Abstract is this text:

   This document changes the recommended default IID generation scheme
   for cases where SLAAC is used to generate a stable IPv6 address.  It
   recommends using the mechanism specified in RFC7217 in such cases,
   and recommends against embedding stable link-layer addresses in IPv6
   Interface Identifiers.

However, it would be useful for readers who aren't deeply familiar with
the subject to provide a brief description of "the mechanism specified
in RFC7217".  I suggest

   It recommends using semantically opaque IIDs generated by the
   mechanism specified in RFC7217 in such cases, and recommends against
   embedding stable link-layer addresses in IPv6 Interface Identifiers.

Similarly, the introduction contains

   As a result of the aforementioned issues, this document changes the
   recommended default IID generation scheme for generating stable IPv6
   addresses with SLAAC to that specified in [RFC7217], and recommends
   against embedding stable link-layer addresses in IPv6 Interface
   Identifiers, such that the aforementioned issues are mitigated.

which would be more informative as

   As a result of the aforementioned issues, in order to use
   semantically opaque IIDs, this document changes the
   recommended default IID generation scheme for generating stable IPv6
   addresses with SLAAC to that specified in [RFC7217], and recommends
   against embedding stable link-layer addresses in IPv6 Interface
   Identifiers, such that the aforementioned issues are mitigated.

Dale

v2.23.0 | Report a Bug | By Email