[dhcwg] draft-ietf-dhc-dhcpv6-yang-04 - DUID representation in the model
"Bernie Volz (volz)" <volz@cisco.com> Mon, 11 December 2017 15:33 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 A5D5A1270FC; Mon, 11 Dec 2017 07:33:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level:
X-Spam-Status: No, score=-14.52 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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
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 RQPe0QnrR32E; Mon, 11 Dec 2017 07:33:18 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9681D1270A0; Mon, 11 Dec 2017 07:33:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14389; q=dns/txt; s=iport; t=1513006398; x=1514215998; h=from:to:subject:date:message-id:mime-version; bh=CdqNqtUXiAs/1HlY0zY0UZ7P/A383rZsEErmScyeknQ=; b=I4eA7VRDC/4Gc4l3gp66OGvyozRJr2zATKChBXqgrijRF0ft7Hvrre9F 0yO05kNAk1dh3gjVWjYJzvIrJnf0YRoOKAVqVDTLWIlQVKx4um+YRDbWx Xoy+nXRzTMCMiZd1siSGdvYljkHPJiAA1JLeUCT0k7bphqIyW/OopuARe Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CwAgAepC5a/4oNJK1bGQEBAQEBAQEBAQEBAQcBAQEBAYJKdGZ0Lp0Zkz6FS4IVCiOKDEEWAQEBAQEBAQEBayiFVl4BgQAmAQQBGok8ZBCqM4pkAQEBAQEBAQECAQEBAQEBARwFg2iCC4M/jkIFoxECh3eHWoVFgkCRLI0KiScCERkBgToBJgkpgU9vFYJkglEcgWeJQoEVAQEB
X-IronPort-AV: E=Sophos;i="5.45,392,1508803200"; d="scan'208,217";a="320604233"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 Dec 2017 15:33:17 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id vBBFXHPB015098 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 11 Dec 2017 15:33:17 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 11 Dec 2017 09:33:16 -0600
Received: from xch-aln-003.cisco.com ([173.36.7.13]) by XCH-ALN-003.cisco.com ([173.36.7.13]) with mapi id 15.00.1320.000; Mon, 11 Dec 2017 09:33:16 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>, "draft-ietf-dhc-dhcpv6-yang@ietf.org" <draft-ietf-dhc-dhcpv6-yang@ietf.org>
Thread-Topic: draft-ietf-dhc-dhcpv6-yang-04 - DUID representation in the model
Thread-Index: AdNylPRYYNiWUyemQc6F5qfpDSooBA==
Date: Mon, 11 Dec 2017 15:33:16 +0000
Message-ID: <0cab196d775e45668ef2fec69f317ce1@XCH-ALN-003.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.98.1.196]
Content-Type: multipart/alternative; boundary="_000_0cab196d775e45668ef2fec69f317ce1XCHALN003ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/oamnArkvtkznKX1GZyu2ky33Qr4>
Subject: [dhcwg] draft-ietf-dhc-dhcpv6-yang-04 - DUID representation in the model
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 11 Dec 2017 15:33:21 -0000
Hi: One comment regarding the 04 version is that for the DUID, you need to: 1. Include the DUID-UUID (see RFC 6355) 2. Handle DUIDs that do NOT follow these conventions (I know of at least one model device that does not). So, you need a way to represent that (the vendor sadly has no type even before the text serial number of the device). This would also accommodate new DUID types that are not yet defined for a new model. Frankly, I'd prefer that we NOT explode these fields at all and just treat the data as binary data. Exploding out values here just causes issues for the above cases and makes the model harder to implement. If you see https://tools.ietf.org/html/draft-ietf-dhc-rfc3315bis-10#section-11, you will notice the following text: Clients and servers MUST treat DUIDs as opaque values and MUST only compare DUIDs for equality. Clients and servers SHOULD NOT in any other way interpret DUIDs. Clients and servers MUST NOT restrict DUIDs to the types defined in this document, as additional DUID types may be defined in the future. It should be noted that an attempt to parse a DUID to obtain a client's link-layer address is unreliable as there is no guarantee that the client is still using the same link- layer address as when it generated its DUID. And, such an attempt will be more and more unreliable as more clients adopt privacy measures, such as those defined in [RFC7844<https://tools.ietf.org/html/rfc7844>]. It is recommended to rely on the mechanism defined in [RFC6939<https://tools.ietf.org/html/rfc6939>]. By exploding out the values you are just encouraging people to violate these MUSTs. - Bernie
- [dhcwg] draft-ietf-dhc-dhcpv6-yang-04 - DUID repr… Bernie Volz (volz)
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-yang-04 - DUID … Ian Farrer
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-yang-04 - DUID … Ian Farrer
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-yang-04 - DUID … Bernie Volz (volz)
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-yang-04 - DUID … Ted Lemon
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-yang-04 - DUID … Ian Farrer
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-yang-04 - DUID … Simon Hobson
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-yang-04 - DUID … Bernie Volz (volz)
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-yang-04 - DUID … Ted Lemon
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-yang-04 - DUID … hezihao9512
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-yang-04 - DUID … Ted Lemon
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-yang-04 - DUID … Simon Hobson
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-yang-04 - DUID … hezihao
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-yang-04 - DUID … Ted Lemon
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-yang-04 - DUID … hezihao
- Re: [dhcwg] draft-ietf-dhc-dhcpv6-yang-04 - DUID … Ted Lemon