Re: Detailed review of Significance of IPv6 Interface Identifiers

"Fred Baker (fred)" <fred@cisco.com> Wed, 14 August 2013 22:56 UTC

Return-Path: <fred@cisco.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 DB87021E80B6 for <ipv6@ietfa.amsl.com>; Wed, 14 Aug 2013 15:56:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.556
X-Spam-Level:
X-Spam-Status: No, score=-110.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HCgIUQkYPz95 for <ipv6@ietfa.amsl.com>; Wed, 14 Aug 2013 15:56:16 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 54A6F11E81BE for <6man@ietf.org>; Wed, 14 Aug 2013 15:56:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1348; q=dns/txt; s=iport; t=1376520976; x=1377730576; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ssdkH5+d+z4eLaAXVgLTzDdBKuiyDWroAg06p0gWUWY=; b=Es6+bfqZnPtKJygWxQHG0kDTNkv/UQfdqBD/xxuulR3EtfdBTN4Kpphe BQwDCsc9/GzCkV0uqTAvmZvRLIvpMEYhJtGRDLS6b2+7GXseCXZ1W9nWC el6/cHOe0RnGwE06f895N9o2PUEirFvAN5cvnDPOWled9m0wA2brnGtpk g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFABYKDFKtJV2d/2dsb2JhbABbgwaBBb8jgSAWdIIlAQEBAzo/EAIBCCIUECERJQIEDgUIh3YDD7A4DYhejVWCSAIxB4MbdwOVe44UhSeDG4Iq
X-IronPort-AV: E=Sophos;i="4.89,880,1367971200"; d="scan'208";a="247267377"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-1.cisco.com with ESMTP; 14 Aug 2013 22:56:16 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r7EMuG82025717 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 14 Aug 2013 22:56:16 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.136]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.02.0318.004; Wed, 14 Aug 2013 17:56:15 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Detailed review of Significance of IPv6 Interface Identifiers
Thread-Topic: Detailed review of Significance of IPv6 Interface Identifiers
Thread-Index: AQHOmMIUTRP1UB+py0q//B44aVYR8JmVjIuAgAAYtAA=
Date: Wed, 14 Aug 2013 22:56:14 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B9979F5@xmb-rcd-x09.cisco.com>
References: <520B3529.80802@si6networks.com> <520BF653.8060603@gmail.com>
In-Reply-To: <520BF653.8060603@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.19.64.121]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2C43E13BD4716543952B37182B4724E7@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@ietf.org>, "<draft-ietf-6man-ug@tools.ietf.org>" <draft-ietf-6man-ug@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 14 Aug 2013 22:56:22 -0000

On Aug 14, 2013, at 2:27 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

>> * Section 3:
>>> To the extent that each method of IID creation specifies the values 
>>> of the "u" and "g" bits, and that each new method is carefully 
>>> designed in the light of its predecessors, these bits tend to reduce 
>>> the chances of duplicate IIDs.
>> 
>> Not sure what you mean. Do you mean that *if* each IID-generation method
>> were to use a different combination of "ug", colisions between them
>> would be avoided? If so, I'd argue that since there's no coordination of
>> which combinations should be used for which method, that's unfeasible.
>> For instance, traditional SLAAC uses all combinations (modulo
>> "illegal/unused" combinations of ug).
> 
> The argument is fuzzy and the sentence needs to be rewritten.
> 
> (I would actually suggest that in a pseudo-random method, now that we
> are clear that the bits have no meaning, it would be best to use them to
> provide two more bits of entropy rather than giving them fixed values.)

Good grief. If the bits don't mean anything - and they never did, since nobody ever interpreted them except in IETF dancing-on-heads-of-pins discussions - could we simply say that they are as random in value as any of the other bits in the IID are?