Re: [dhcwg] dhcpv6-24: use of DNS names in DUIDs

Ralph Droms <rdroms@cisco.com> Thu, 09 May 2002 00:04 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26791 for <dhcwg-archive@odin.ietf.org>; Wed, 8 May 2002 20:04:22 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id UAA07075 for dhcwg-archive@odin.ietf.org; Wed, 8 May 2002 20:04:31 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA05933; Wed, 8 May 2002 19:51:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA05908 for <dhcwg@optimus.ietf.org>; Wed, 8 May 2002 19:51:46 -0400 (EDT)
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26413 for <dhcwg@ietf.org>; Wed, 8 May 2002 19:51:37 -0400 (EDT)
Received: from rdroms-w2k.cisco.com (sjc-vpn1-536.cisco.com [10.21.98.24]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id TAA27842; Wed, 8 May 2002 19:51:12 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020508192815.00b6da90@funnel.cisco.com>
X-Sender: rdroms@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 08 May 2002 19:30:06 -0400
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] dhcpv6-24: use of DNS names in DUIDs
Cc: rdroms@cisco.com
In-Reply-To: <200205081533.g48FXU519550@rotala.raleigh.ibm.com>
References: <Message from "Wed, 08 May 2002 11:00:44 EDT." <4.3.2.7.2.20020508105641.0320ce68@funnel.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org

Comments in line

- Ralph

At 11:33 AM 5/8/2002 -0400, Thomas Narten wrote:
> > Thomas - the VUID-DN format is useful for vendors that have a DNS name but
> > do not have an enterprise number.
>
>I think you need to also add: "and cannot easily obtain one". My
>understanding is that they are easy to obtain. See
>http://www.iana.org/assignments/enterprise-numbers. There is also an
>online application form on the IANA page.

Adding the text makes sense...


> > I argue for the domain name representation to be in the base spec to cover
> > all possible future uses of domain names in options, even if none of those
> > options appear in the base spec.  With the definition in the base spec, we
> > are guaranteed uniformity of domain name representation across all future
> > options.
>
>I can live with this.
>
> > If there is a conflcit between the spec in section 8 and in the VUID-DN
> > definition, we should fix (or drop) the VUID-DN definition.
>
>The VUID-DN definition says the DNS name is in ascii.

Good catch - I think the use of ASCII is a legacy in the example;
the example should be changed to use RFC1035 representation.


>Thomas
>
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/dhcwg


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg