Re: [dhcwg] Question regarding RFC 8415 - DHCPv6

"Bernie Volz (volz)" <volz@cisco.com> Fri, 01 May 2020 23:40 UTC

Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4FDC3A1515 for <dhcwg@ietfa.amsl.com>; Fri, 1 May 2020 16:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.419
X-Spam-Level:
X-Spam-Status: No, score=-10.419 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.82, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=OJ1kQvrW; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=AzOKj638
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 dbJRx0HY0lU9 for <dhcwg@ietfa.amsl.com>; Fri, 1 May 2020 16:40:16 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B6923A1512 for <dhcwg@ietf.org>; Fri, 1 May 2020 16:40:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7747; q=dns/txt; s=iport; t=1588376416; x=1589586016; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=odcSsgXT8CFCe7kMYPkX/Yie/pW6hsw6yAYU2wx01QI=; b=OJ1kQvrWwjaRfjQZVVKz6yW73ZH0Td0eynd/Amcd705TyQ44D3P8YfWe /qFb120Q3FdMD+ZADVpFr38tXKMWrJENJB475/sq5FRbJtRjwz9GOOWST 1PIV6KiC7am7KWjeZFHtaIpDIhoNcKPV7UdRl+cttKhFz8/9TUC3AmpCx E=;
IronPort-PHdr: 9a23:N0HwMRJ6cYSZ8zivZtmcpTVXNCE6p7X5OBIU4ZM7irVIN76u5InmIFeGvK8/jVLVU8Pc8f0Xw+bVsqW1X2sG7N7BtX0Za5VDWlcDjtlehA0vBsOJSCiZZP7nZiA3BoJOAVli+XzoMEVJFoD5fVKB6nG35CQZTxP4Mwc9L+/pG4nU2sKw0e36+5DabwhSwjSnZrYnJxStpgKXvc4T0oY=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BaDQD0sqxe/4YNJK1mHQEBPAEFBQECAQkBgVwCgSMvJC0FgUYvKgqEGINGA40iJYl5iVmEY4EuFIEQA1QLAQEBDAEBLQIEAQGERAIXghkkNAkOAgMBAQsBAQUBAQECAQUEbYVWDIVyAQEBAgESER0BATcBBAsCAQhCAgICHxElAgQOBSKDBIF/TQMOIAGpdAKBOYhhdoEygwABAQWCSYMHDQuCDgmBOAGCYolhGoIAgRAoDBCCHy4+gQSBGoF2IoMqM4ItkUiGGJojSgqCRpNEhEkdnRuEbpc4kQICBAIEBQIOAQEFgVI5gVZwFTsqAYI+UBgNkFqDWopWdDYCBgEHAQEDCXyNFwGBDwEB
X-IronPort-AV: E=Sophos;i="5.73,342,1583193600"; d="scan'208,217";a="753289589"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 01 May 2020 23:40:12 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by alln-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id 041NeCEl013540 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 1 May 2020 23:40:12 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 1 May 2020 18:40:11 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 1 May 2020 19:40:10 -0400
Received: from NAM10-MW2-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Fri, 1 May 2020 18:40:10 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=KIbhZ8awPZhm2+cw1Uw9jFIvshFmNtn0TIsbPIKXBGhSFNsaXqzGRj2xzqeUMvgSxQV6yBWkes5shRlgFqiiEzD8IatYoyhp67OZRHAdLoCY2Zdfnwr2IjxHlTTdZfPoc9TMk8bJ7/smmhYr4/+U01iseltRnjaU0f5Tcxo1bXwyMU3Hv0skTFpP0oUuzN/RapouOPylv/53UOyipWY6/6VGCN7eGCNG5NOyXPVVlTL6Nf6B2QxvQ0aqVmNFJsd28AL9AMgeMB6dUqU4TrnwQYVWYIjpEldxtAwqECPTgoUjfOCqSsLGRnWqVj0/2A/mCpWwhatPysYAgxccSOnftg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=odcSsgXT8CFCe7kMYPkX/Yie/pW6hsw6yAYU2wx01QI=; b=UFYl1b4plybpHD/0DVfFDkmxmf72pdMYfsq+Yvptjzj3MJ4vY/RJg7qlcFsgGsQJ+k0cIuMXR9sHcJPoB5K+FAOILhPAj4/H+nF3nrjt591vGL6dFAguuTFhy5ylXeccyuQ1Es4FkE57UIfNYJqJqnHMxgaw+v24sPYFdjBF2biEdOco6vme9EkHbIz97/lQEQUSbQj9rWe7f3wqOM/Sl1bkwcio2wqkxNO4z/BUZ08F43bS7WF6IbdxKcQVIuV89OS1NoUQFPf7vaj8Ix+p1jkRekmzdtLOzS89Qucpxp1Py46hGNCd6QCUC1pFHTwaohJzFPkzFjAfWSKffHY3WQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=odcSsgXT8CFCe7kMYPkX/Yie/pW6hsw6yAYU2wx01QI=; b=AzOKj638G6cT7+NOYcKvbrFQLrGFET9rFEU4uwBOTC6bXQtK+eeOz9BwMDzB93hAwBjf6UhMTW3ZY+z0sa+fR3GC0K0k+X742f6qaAw0bzlcenDFGrsGq9o/2SnNe9Rk2Zec7KWiXU27YHc2QYZgaifp/vMqyk6DINooTXcOgFE=
Received: from BN7PR11MB2547.namprd11.prod.outlook.com (2603:10b6:406:af::18) by BN7PR11MB2628.namprd11.prod.outlook.com (2603:10b6:406:b2::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2937.22; Fri, 1 May 2020 23:40:09 +0000
Received: from BN7PR11MB2547.namprd11.prod.outlook.com ([fe80::7d1c:98b:2131:d35]) by BN7PR11MB2547.namprd11.prod.outlook.com ([fe80::7d1c:98b:2131:d35%3]) with mapi id 15.20.2937.028; Fri, 1 May 2020 23:40:09 +0000
From: "Bernie Volz (volz)" <volz@cisco.com>
To: gulaschsuppe2 <gulaschsuppe2@gmail.com>
CC: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Question regarding RFC 8415 - DHCPv6
Thread-Index: AQHWH/tgFgxaUghwlUm1iDqGSWGKKqiT47x8
Date: Fri, 01 May 2020 23:40:09 +0000
Message-ID: <6275ED50-4C53-4272-8088-20AC4FBDB124@cisco.com>
References: <CANV1LX6xzd2EqiPjoKJL6kaBUH=tDFDLQzZfSKnCaEnxaC2PWA@mail.gmail.com>
In-Reply-To: <CANV1LX6xzd2EqiPjoKJL6kaBUH=tDFDLQzZfSKnCaEnxaC2PWA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [24.233.121.124]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 2eb5251d-1e17-421b-5f4b-08d7ee28fc58
x-ms-traffictypediagnostic: BN7PR11MB2628:
x-microsoft-antispam-prvs: <BN7PR11MB2628210085FD3886EB5344AFCFAB0@BN7PR11MB2628.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0390DB4BDA
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BN7PR11MB2547.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(136003)(39860400002)(376002)(396003)(346002)(366004)(66476007)(5660300002)(6512007)(2906002)(66446008)(33656002)(4326008)(6486002)(91956017)(478600001)(71200400001)(6916009)(86362001)(36756003)(66946007)(66556008)(76116006)(316002)(8936002)(6506007)(186003)(26005)(8676002)(2616005)(64756008)(53546011); DIR:OUT; SFP:1101;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: dsaq0jSbhf5dfWrNkFBlRVImSghSP5c9mlionMFJOn6R0SNfPzlrMBqVJ4PCOxvN02VN+Y/bFifVrIR2vtuaubmQ0M/X7d/G5s3aTzD0JmLudYTQguA3bH7KdgUa3l4DUpXth51WU6QP6y30mOvREOVkYMm3d/szLyI7ly9ZHRXzawYA8Tdzj8D2Z7BG6tOV6/da6dZvornOFaSU/5vXGP/J9zG/Nw4uSYa1yJszF0etCQBv3UxadpFiR1jiYy+EuqV/IrK7hEf7NOsXEzw5oydqYcGqegDCFZEsF/gAvBjUwvs5g34xzgX7M4MQpgDqamVVMHlCr8vZzcmMHAPWTjVw2GxyZB04DRGQ8BFuQFSidvkhdt6hn3dlITrzHxAUdGyhTVg5ACjfTmm2WCVsFkWMKKPfw9oC8DmbnwWGsUfE5Ri53g5JJpEHgXqzJqdw
x-ms-exchange-antispam-messagedata: P+CWiNdsc1Xc08nqn2Cni2rhlX5Apxn7MjMbGWMJ7Jj8nD6oihkcMmq8O4iPZkEDYcEHLXw96ISBdnVPjfmzR3/vqQwmZw2AZNHQ552fB3y786wzHp+vFKWQmH3Ee2UDSgx0nd/mFQaFBefX95b9Vu++l7weyXh6wgEWshdko8hOUu/ToomXC89llGLHt45ukrNKQnfvGKDtPsyqREqRTrGLjljz92r4lX21b7SzycFPFPqw6lxXkhQX5l8mVgmx/3uqGTmnUgpfIFgiXnlDZg/32uPgQJSlJsOxmA3PRYmfOO++tp5BTnIjW96ysSN84DmYf2u2fUg/fIcwndZwM6WWSMFbQ8tEoVSjENb3zol5+V+FRY21oelEwg13GEmqP18xrKdl0ahCWbuV8YrA5eOECBm9NWmYMk6nnAA3spcudSCB49Faq8SGBP/HYR0JoOC0CEFlpVxjDoFoUP+XySPgSWZ1hbcnXaOrjhSWudzb33dITQNbiqykBCPrR/Ed64jZ/XU5dYOjNGIewXV0EFiYzy3Tj49G9jd0CIQe6kViB7uLzY9Rna4ciW+oLc0B4Pon3w2Q+beOBbJCormmQ143nUGkeANV/xghgng4t0SPG04C5hyZoWJvS91nEfgZKIQUDPAtofHM30zqyNWiwdZ0LxlyP/Ii30TdvOadP5AfLvdvmpby/ETVJ6x7DtqWKOUmWf25288Rx2b/Y9E4s6DyFt6cdcjWYZRkuc9NvlWBPU0kPQbrCe2u8EJMbXN0QPav/+AdixlR/Pq+01jUmmwkml9vlEO4HUu5Wg41am8=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_6275ED504C534272808820AC4FBDB124ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 2eb5251d-1e17-421b-5f4b-08d7ee28fc58
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 May 2020 23:40:09.4807 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: wVCYfTC5DnZ8fRC4MG6bCodGeAPAMFTNVpn1wHX8IQJv0b8XW0+95lQKNM/2UYUO
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN7PR11MB2628
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.12, xch-aln-002.cisco.com
X-Outbound-Node: alln-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/b_74pCJ26M7VIOlYfh9grWS2VrE>
Subject: Re: [dhcwg] Question regarding RFC 8415 - DHCPv6
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 May 2020 23:40:19 -0000

Likely it was a timing issue, as this section may have been written before work on 7943 was done as the process to get RFC8415 completed was a multi-year one and no one caught updating the list. RFC7943 is also informational so not critical as it is just one of many methods one can use. The point of the references that are there was to provide background on the issue and suggested algorithms (the server I work on uses something close to what is in 4941 and has worked well).

You can always file an errata if you feel strongly that this is an issue.

- Bernie

On May 1, 2020, at 4:59 PM, gulaschsuppe2 <gulaschsuppe2@gmail.com> wrote:


Dear Mr. Volz,

i have a question regarding the latest revision of DHCPv6 - RFC 8415:

In Section 13.1 - "Selecting Addresses for Assignment to an IA_NA" it is described that...

> By default, DHCP server implementations SHOULD NOT generate
> predictable addresses (see Section 4.7 of [RFC7721]).  Server
> implementers are encouraged to review [RFC4941], [RFC7824], and
> [RFC7707] as to possible considerations for how to generate
> addresses.

As far as i understand, because SLAAC originally used the modified MAC address as an Interface Identifier, RFC 7217 described an algorithm to create "Stable and Opaque IIDs". Such an RFC for "Stable and Opaque IIDs" was also created for DHCPv6 with RFC 7943, but RFC 7943 is never mentioned in the DHCPv6 revision which came 2 years later (at least when it comes to the mentioned month and year in the RFCs).

I wonder, is there is a specific reason that RFC 7943 was not mentioned in the DHCPv6 revision RFC 8415, because it addresses exactly the problem of predictable addresses mentioned in Section 13.1?

Is RFC 7943 in any way discouraged?

I hope i didn't bother you to much.

Thanks in advance,
Best wishes

René Engel