IETF Logo Mail Archive

Re: [dhcwg] draft-ietf-dhc-dhcpv6-yang-04 - DUID representation in the model

"Bernie Volz (volz)" <volz@cisco.com> Thu, 14 December 2017 23:04 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 5D5D2128C84; Thu, 14 Dec 2017 15:04:46 -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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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
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 bkQn2oyvaH1m; Thu, 14 Dec 2017 15:04:43 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A7D41287A5; Thu, 14 Dec 2017 15:04:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1668; q=dns/txt; s=iport; t=1513292668; x=1514502268; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=no2LBJN8lHUN+4cut1wwxaOxzxEvV/r9s6sFyCX5N+E=; b=U09ERqsABY40D74ou+sig42+VyhcYOYw7J8Eqjv1BqKTGDkE4afes/Oe 4HSQsGqlk7nDhaBkAU1c0kXX+IVf4v2dc/AuSjjTFzcNrN3U67xlF3u4Q GSl/43EKSxhvDJNHDR28fb2dPc1StcT+uv94oZdnoRzhPnB/BNCpbPg0j A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DXAQDhAjNa/4UNJK1dGQEBAQEBAQEBAQEBAQcBAQEBAYMPL2Z0J4QCmSiBVyaZKwoYC4UYAhqEXUMUAQEBAQEBAQEBayiFIwEBAQMBAQEhEToLBQsCAQgOCgICJgICAiULFRABAQQOBYoSAw0IEKk2gieKYQEBAQEBAQEBAQEBAQEBAQEBAQEBARgFgQ+CVoIOgz8pC4J3gmpEAYFugxUxgjIFoyUClSiTbJZAAhEZAYE6ATYigU5vFToqAYF+glMcgWd4ilMBAQE
X-IronPort-AV: E=Sophos;i="5.45,402,1508803200"; d="scan'208";a="44280455"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 14 Dec 2017 23:04:27 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id vBEN4Rui018133 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 14 Dec 2017 23:04:27 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 14 Dec 2017 17:04:26 -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; Thu, 14 Dec 2017 17:04:26 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Simon Hobson <dhcp1@thehobsons.co.uk>
CC: "dhcwg@ietf.org" <dhcwg@ietf.org>, "draft-ietf-dhc-dhcpv6-yang@ietf.org" <draft-ietf-dhc-dhcpv6-yang@ietf.org>
Thread-Topic: [dhcwg] draft-ietf-dhc-dhcpv6-yang-04 - DUID representation in the model
Thread-Index: AdNylPRYYNiWUyemQc6F5qfpDSooBACYXfaA///QgOmAAHUjAIAAWqSA///SpyI=
Date: Thu, 14 Dec 2017 23:04:26 +0000
Message-ID: <D97294FF-5684-43B2-AD85-DB0C47D1A204@cisco.com>
References: <0cab196d775e45668ef2fec69f317ce1@XCH-ALN-003.cisco.com> <7E297315-1B5B-437D-A447-221E8DAA5388@gmx.com> <A670F3DD-DEBC-40D5-8890-A5D43233362F@cisco.com> <0D8F77A1-3B91-4D6E-A7F2-5720EF0AFA51@gmx.com>, <A60591D3-7598-4BFB-9F30-A69257D65E01@thehobsons.co.uk>
In-Reply-To: <A60591D3-7598-4BFB-9F30-A69257D65E01@thehobsons.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/ofwKCDkTZSzypmBbsQ3msdN3j_U>
Subject: Re: [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: Thu, 14 Dec 2017 23:04:46 -0000

This is definitely a mess. But these devices are out there.

Obviously there was is no collision today as my understanding is that these are ascii strings and so we have a lot of duid-types to assign before there would be a conflict.

I just don’t see why we bother to separate out anything - just treat it as an opaque “blob” of data.

That’s at least my personal position.

- Bernie (from iPhone)

> On Dec 14, 2017, at 2:56 PM, Simon Hobson <dhcp1@thehobsons.co.uk> wrote:
> 
> Ian Farrer <ianfarrer@gmx.com> wrote:
> 
>> We could make the type code explicit for defined DUIDs, omitting it for duid-string
> 
> Surely, if the DUID-String version does not have a defined type code, then there is nothing to stop the initial byte(s) of the string matching a defined type value - and thus screwing up anything that's trying to make sense of the DUID based on it's type.
> 
> Or put another way, if you allow an arbitrary string without a type code, then you might as well say that all DUIDs are freeform and it's impossible to reliably parse them.
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email