Updated draft - draft-ietf-dnsext-dhcid-rr-12.txt

"Bernie Volz \(volz\)" <volz@cisco.com> Wed, 01 March 2006 04:04 UTC

From: "Bernie Volz (volz)" <volz@cisco.com>
Subject: Updated draft - draft-ietf-dnsext-dhcid-rr-12.txt
Date: Tue, 28 Feb 2006 23:04:42 -0500
Lines: 22
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-From: dhcwg-bounces@ietf.org Wed Mar 01 05:05:17 2006
Return-path: <dhcwg-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.02,155,1139212800"; d="scan'208"; a="22765136:sNHT22461384"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Updated draft - draft-ietf-dnsext-dhcid-rr-12.txt
Thread-Index: AcY85UTAFxA+PKOdTk2lIWV8Rdd3cA==
To: namedroppers@ops.ietf.org, dhcwg@ietf.org
X-OriginalArrivalTime: 01 Mar 2006 04:04:43.0543 (UTC) FILETIME=[455B5A70:01C63CE5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org
X-Message-ID:
Message-ID: <20140418072135.2560.61520.ARCHIVE@ietfa.amsl.com>

I've just submitted another update of the dhcid-rr draft.

The changes are:
1. Added DHCID RDATA that was missing. Three people (myself, Mark Stapp,
and Olafur) independently calculated the values. Thanks to Mark and
Olafur for doing this.
2. Updated references from RFC 2535 to RFC 3548 in section 3.2 and RFC
4034 in section 3.5.
3. Revised the wording to clarify what is used from the DHCPv4 client
identifier option, i.e., the entire option's data (type and identifier)
is used.
4. Broke out the last 3 paragraphs as subsections to section 3.5 (3.5.1,
3.5.2, and 3.5.3) to separate out how the RDATA is generated.

These changes were suggested by Olafur to improve the quality of the
draft. Thanks Olafur.

What I submitted is available at
ftp://ftpeng.cisco.com/volz/draft-ietf-dnsext-dhcid-rr-12.txt until it
is published on the IETF site.

- Bernie