IETF Logo Mail Archive

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

Simon Hobson <dhcp1@thehobsons.co.uk> Thu, 14 December 2017 19:56 UTC

Return-Path: <dhcp1@thehobsons.co.uk>
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 D655F127286; Thu, 14 Dec 2017 11:56:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham 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 FlpVJFf4RprZ; Thu, 14 Dec 2017 11:56:27 -0800 (PST)
Received: from patsy.thehobsons.co.uk (ruthandcrusoe.plus.com [81.174.150.186]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC34E124E15; Thu, 14 Dec 2017 11:56:26 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from simons-macbookpro.lan (unknown [80.229.10.150]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id EFEDB1A071; Thu, 14 Dec 2017 19:46:55 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <dhcp1@thehobsons.co.uk>
In-Reply-To: <0D8F77A1-3B91-4D6E-A7F2-5720EF0AFA51@gmx.com>
Date: Thu, 14 Dec 2017 19:46:45 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <A60591D3-7598-4BFB-9F30-A69257D65E01@thehobsons.co.uk>
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>
To: dhcwg@ietf.org, draft-ietf-dhc-dhcpv6-yang@ietf.org
X-Mailer: Apple Mail (2.1510)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/wCS6UBT5m07b4cYDqn09IUHrbrQ>
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 19:56:29 -0000

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.

v2.23.0 | Report a Bug | By Email