IETF Logo Mail Archive

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

Ted Lemon <mellon@fugue.com> Thu, 14 December 2017 23:13 UTC

Return-Path: <mellon@fugue.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 4BC811270AE for <dhcwg@ietfa.amsl.com>; Thu, 14 Dec 2017 15:13:21 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 1yTfLNYLjEDF for <dhcwg@ietfa.amsl.com>; Thu, 14 Dec 2017 15:13:19 -0800 (PST)
Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6313127005 for <dhcwg@ietf.org>; Thu, 14 Dec 2017 15:13:18 -0800 (PST)
Received: by mail-qt0-x229.google.com with SMTP id g10so10019673qtj.12 for <dhcwg@ietf.org>; Thu, 14 Dec 2017 15:13:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=dJTjWZI17wqJKcWDFcyE34H2rMqSbTHI8A0OfWkBYu8=; b=JfdXuhX6nGMBEZudVzRiyCmrneV9AeE5iG++5u0+Gji53/abnRS4C0yJ8OE6Y29XbR +BCFbqLMkfyToKdAPssrHhZThMzNlQYPscXNdD6DfZ71HgfjsKxtk8XG1o1mymOuk1++ 0fAbuUKx++rwkHVTXDI1/gDDmfsAJphXtqdYFrNItId6qK2YXTPq+2YzQFN7vSdlcEKg k9q5Hps2DcN7fctN3cLMaG4znpdx0Z1pWHLihWj+m7bZrnyI3EFnbjP0Ax8E29PCyrYn 0OnwWeWq6MNPW34iLFp73qMNumk08K4nonR7/Q7KxAW5jhAUxYgiBw8DUKkbtEjzhjHE wThg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=dJTjWZI17wqJKcWDFcyE34H2rMqSbTHI8A0OfWkBYu8=; b=mtu8QtM1Y8P48kHFEZ4FyBcuz8gfvHJaSTz4dTf7bh1N3xpFfDkrVyTWQhBAFYKgSe hWmlQLzz0Z+SqZ2ciyd+FF5bFA/euen2zkW9sYsc0t4s0LFmBnhMbld56//65Z0rSRIC 0GU5Vanx88MTC7wrmRGZjp6NEhU6WAOhUrmr+QRXmpmDdyrEszA3ZHsODXP8zXBxQ8eJ uoctQYU71d7J9TWgNZ97QdLETLcpp+Wvh8v8BLhFGIVoxj/jrvn//95ntXVbOIEAYdcZ MBUfVrIaz/bPJddL825KBwK389uAQ/TJ/uu25vR26EAd5CEbMn63BCu/UzWka8jHfQ/P /eUw==
X-Gm-Message-State: AKGB3mKmuslw4RAX3MOMAdJTh4M3qFCCFNkQfu8KXBieOyQOYkCBzRNu +VAzdtXF4Akh3rc2yJKCPYqfPg==
X-Google-Smtp-Source: ACJfBovJnNyJ9pNlYHXn3FxUkx5vTQN2I/INNI5XiNiJae9quQ9DuNmsIjV51rZj5BjJOQqnTZq+vQ==
X-Received: by 10.200.42.211 with SMTP id c19mr18128078qta.70.1513293197967; Thu, 14 Dec 2017 15:13:17 -0800 (PST)
Received: from [10.0.30.153] (c-24-60-163-103.hsd1.nh.comcast.net. [24.60.163.103]) by smtp.gmail.com with ESMTPSA id k1sm3347775qtf.11.2017.12.14.15.13.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 Dec 2017 15:13:17 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <A748CBA5-B787-484D-B73B-A30EFBF19631@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D6FBB039-6D93-4D1B-9637-AAF1519D0EC3"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Thu, 14 Dec 2017 18:13:15 -0500
In-Reply-To: <D97294FF-5684-43B2-AD85-DB0C47D1A204@cisco.com>
Cc: Simon Hobson <dhcp1@thehobsons.co.uk>, "dhcwg@ietf.org" <dhcwg@ietf.org>, "draft-ietf-dhc-dhcpv6-yang@ietf.org" <draft-ietf-dhc-dhcpv6-yang@ietf.org>
To: "Bernie Volz (volz)" <volz@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> <D97294FF-5684-43B2-AD85-DB0C47D1A204@cisco.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/kb07jjz3h-FP4-KkwEkNiyw-1hs>
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:13:21 -0000

On Dec 14, 2017, at 6:04 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> I just don’t see why we bother to separate out anything - just treat it as an opaque “blob” of data.

This is a valid point; realistically, when we defined DUID, we defined it as a blob, and then specified ways of doing it, but insisted that from the perspective of being used as an identifier, it was just a blob; the "how to make" part of the spec is to avoid collisions, not to make the information in the DUID available for the server to parse.

It would be reasonable to say that the yang data model should just present that binary blob to whatever is talking to it, and if that thing wants to have heuristics for picking it apart, that's fine, but the data model doesn't need to do so.

v2.23.0 | Report a Bug | By Email