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

hezihao9512 <hezihao9512@gmail.com> Fri, 15 December 2017 05:17 UTC

Return-Path: <hezihao9512@gmail.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 72F7B126B7E; Thu, 14 Dec 2017 21:17:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.026
X-Spam-Level:
X-Spam-Status: No, score=-1.026 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 PtxRrEHf4esD; Thu, 14 Dec 2017 21:17:44 -0800 (PST)
Received: from mail-pg0-x243.google.com (mail-pg0-x243.google.com [IPv6:2607:f8b0:400e:c05::243]) (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 7C6331205F1; Thu, 14 Dec 2017 21:17:44 -0800 (PST)
Received: by mail-pg0-x243.google.com with SMTP id f12so5078712pgo.5; Thu, 14 Dec 2017 21:17:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version:content-transfer-encoding; bh=U7Y17ErOnYNYilpGjW2yNzsaUSNwbmuaoZTzOzQVhU8=; b=uSuETaHYkx9U9MpbeEzNlLVd4Jfqic3Eyz0PbzrIzVvgeuzXJXb5DrIU9qut4wOO3v sjHB5RahtnBgLsXThnwlJsO96MnnFwTZQXDbIoehjchd7BpqPaLMmAOwAH/FZtfvOYIt kFLq4v8IRXWP9Q7lGCmlRBDRJWvcpCFHFL1eCaAqqVgD9SruzqUgodt38nqcgMyL4vCF xV3l6YhaQHxqmM7ebQ3QVLedNFs/Rl0REUey9+ZB9PGfoaG3McuRIFUYNvsIJH1D4ha7 4+k742tpMueKO+Yv8AU3KwtDCDpnQq4rbWu4Q//wAO2cbqu/xzF2uHxLcbPMt9f5LJbs zmCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version:content-transfer-encoding; bh=U7Y17ErOnYNYilpGjW2yNzsaUSNwbmuaoZTzOzQVhU8=; b=eHhPBNHwBy0o46IdYRrllrQgT8JpptC4XOkSLMgxBm/BAGKeEcvoz3mNhnFg9VPKLn 3S5FT/DYrVZFRydxl3kIxXZwMODAXtR7tVLR9UKalhc7wLdlUPZURbdiCSrxiw2tKddn TzCWoTsyXcxP3SC2lZe5M2kYmwMbBu5XJPJS3+2ImETy/fzdPduFEhgMn4sw2lIY0ye9 SKRlvKJNJvslO8mqTxzOBru63+GPP1MrpKzAs+dUmQ/t24eMRCuz51CuHYaYXzF4EVyt 5B8b8+d4oaUo2YY4SafrgSX4ljaF069yFNEOgwDseRBAp9Ge4hebAgF8y6f1VNYiGgZb N94Q==
X-Gm-Message-State: AKGB3mId9LMI+XKlXPHJiFHY1sJymfh4n1uBynEGHZR7ybnKgahPU1db U5//lzlJ+sK8NM5yt2WWNq7duTrV
X-Google-Smtp-Source: ACJfBouc4bA/dBYVYh+9RzfED1EZubS3E168qkCXPjpHxBDZEk3ixpGqP+xBscu0t+RnnO4x+XIDCw==
X-Received: by 10.84.172.1 with SMTP id m1mr12214188plb.345.1513315063902; Thu, 14 Dec 2017 21:17:43 -0800 (PST)
Received: from DESKTOP-7HBCU2Q ([103.211.228.150]) by smtp.gmail.com with ESMTPSA id k9sm8648354pgo.53.2017.12.14.21.17.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 Dec 2017 21:17:43 -0800 (PST)
Date: Fri, 15 Dec 2017 13:18:10 +0800
From: hezihao9512 <hezihao9512@gmail.com>
To: Ted Lemon <mellon@fugue.com>
Cc: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>, "draft-ietf-dhc-dhcpv6-yang@ietf.org" <draft-ietf-dhc-dhcpv6-yang@ietf.org>, Simon Hobson <dhcp1@thehobsons.co.uk>
Message-ID: <33E83BAA-5314-402A-9A3B-ADF6C7BE42FE@gmail.com>
In-Reply-To: <A748CBA5-B787-484D-B73B-A30EFBF19631@fugue.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> <A748CBA5-B787-484D-B73B-A30EFBF19631@fugue.com>
X-Mailer: MailMasterPC/4.2.2.1003 (Windows 10 RS3)
X-CUSTOM-MAIL-MASTER-SENT-ID: 25DFDEBC-771D-4713-B7A0-220802640EEC
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/kYQPtcR-d3eQaXlNxn8-bj4EvHo>
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: Fri, 15 Dec 2017 05:17:45 -0000


As far as I am concerned, whether a DUID is presented in separated types or in a blob, it can both be treated as a blob.

However, it would be somewhat easier for a device to parse a DUID (if it does want to) in a multi-type presentation than just in a ‘blob’ presentation.

So, I think the separation of types might be better in a way.


On 12/15/2017 07:13Ted Lemon<mellon@fugue.com> wrote:
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.