[dhcwg] New Draft Notification - draft-dhcwg-dhc-rfc3315bis-00.txt

"Bernie Volz (volz)" <volz@cisco.com> Thu, 09 January 2014 03:09 UTC

Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B5A11AE051 for <dhcwg@ietfa.amsl.com>; Wed, 8 Jan 2014 19:09:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.038
X-Spam-Level:
X-Spam-Status: No, score=-10.038 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 MR7zOzEExvBH for <dhcwg@ietfa.amsl.com>; Wed, 8 Jan 2014 19:09:29 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id 4D2E51AE035 for <dhcwg@ietf.org>; Wed, 8 Jan 2014 19:09:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10274; q=dns/txt; s=iport; t=1389236960; x=1390446560; h=from:to:subject:date:message-id:references:mime-version; bh=LrmA9UrJjiLfHKWku1uijW1mV5kzJEPCj1xsfEP4mTk=; b=QGS1p17ApuLirwWVZIbrP6XENKM0KMylkiGpnfqM84dXxVs27oA92PkK lv7JoHKYyEBGOoTtYDmEqZtNJaH765D8/973f49XFI7OEbudgIBP0l6OK +mEaG1HQGQ+kF1uqyc+aHxRL3LiNU+ASszbb6WV7FVP9ggraKNoeXW8FT E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AigIAAkSzlKtJXG+/2dsb2JhbABZgws4g1StbYhVGHgWdIIlAQEBBCNUEgIBGQMBAh4KAwICAjAUCQgBAQQTCYd7DalxmlYXjiMRAT8NCgeCKUA1gRMEmBeBMJBlgy2BcQ
X-IronPort-AV: E=Sophos; i="4.95,628,1384300800"; d="scan'208,217"; a="11530422"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by alln-iport-6.cisco.com with ESMTP; 09 Jan 2014 03:09:18 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0939ItM006810 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Thu, 9 Jan 2014 03:09:18 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.37]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0123.003; Wed, 8 Jan 2014 21:09:18 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: New Draft Notification - draft-dhcwg-dhc-rfc3315bis-00.txt
Thread-Index: Ac8M6C645kTFUfcZSFCF+gvWTiCK6g==
Date: Thu, 09 Jan 2014 03:09:17 +0000
Message-ID: <901BBBD6-F803-4E88-B5C3-DCE4A2AA8C8E@cisco.com>
References: <20140109023726.19535.83055.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_901BBBD6F8034E88B5C3DCE4A2AA8C8Eciscocom_"
MIME-Version: 1.0
Subject: [dhcwg] New Draft Notification - draft-dhcwg-dhc-rfc3315bis-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 09 Jan 2014 03:09:36 -0000

This is the initial document, a conversion of RFC 3315 to xml (xml2rfc) format, which the dhcpv6bis team will start editing to merge in RFC 3633, apply errata, other issues reported for RFC 3315 and 3633, and perhaps a few other RFCs. We have already entered many of the known issues into our issues tracker. Fred Templin had done a thorough review of RFC 3315 many years ago which uncovered just under 30 issues (some may be duplicates of issues reported by others). Thanks Fred!! And sorry it has taken so long to start to look at them!

We wanted to provide this version so that all could see that we started from the original RFC 3315, excepting minor differences in formatting and complying with xml2rfc formatting (i.e., references, etc.).

Thanks to Tomek for doing the initial conversion (using nroff2xml), and to Michael Richardson for doing much of the cleanup.

Please feel free to use the ietf tools diff tool to compare this with RFC 3315.

If anyone knows of RFC 3315 or 3633 issues, please do let us know of them (you can see the existing "under consideration" issues at http://trac.tools.ietf/group/dhcpv6bis/report/1). Email me or dhcpv6bis@ietf.org<mailto:dhcpv6bis@ietf.org>.

- Bernie (for the dhcpv6bis team)

Begin forwarded message:

From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>
Date: January 8, 2014 at 9:37:26 PM EST
Subject: New Version Notification for draft-dhcwg-dhc-rfc3315bis-00.txt


A new version of I-D, draft-dhcwg-dhc-rfc3315bis-00.txt
has been successfully submitted by Bernie Volz and posted to the
IETF repository.

Name:        draft-dhcwg-dhc-rfc3315bis
Revision:    00
Title:        Dynamic Host Configuration Protocol for IPv6 (DHCPv6) bis
Document date:    2014-01-06
Group:        Individual Submission
Pages:        101
URL:            http://www.ietf.org/internet-drafts/draft-dhcwg-dhc-rfc3315bis-00.txt
Status:         https://datatracker.ietf.org/doc/draft-dhcwg-dhc-rfc3315bis/
Htmlized:       http://tools.ietf.org/html/draft-dhcwg-dhc-rfc3315bis-00


Abstract:
  The Dynamic Host Configuration Protocol for IPv6 (DHCP) enables DHCP
  servers to pass configuration parameters such as IPv6 network
  addresses to IPv6 nodes.  It offers the capability of automatic
  allocation of reusable network addresses and additional configuration
  flexibility.  This protocol is a stateful counterpart to "IPv6
  Stateless Address Autoconfiguration" (RFC 2462), and can be used
  separately or concurrently with the latter to obtain configuration
  parameters.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>.

The IETF Secretariat