draft-ietf-dhc-dhcpv6-vendor-message-00.txt   draft-ietf-dhc-dhcpv6-vendor-message-01.txt 
DHC B. Volz DHC B. Volz
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended status: Standards Track January 12, 2009 Intended status: Standards Track August 3, 2009
Expires: July 16, 2009 Expires: February 4, 2010
DHCPv6 Vendor-specific Message DHCPv6 Vendor-specific Message
<draft-ietf-dhc-dhcpv6-vendor-message-00.txt> <draft-ietf-dhc-dhcpv6-vendor-message-01.txt>
Status of this Memo Status of this Memo
S
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 16, 2009. This Internet-Draft will expire on February 4, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents in effect on the date of
(http://trustee.ietf.org/license-info) in effect on the date of publication of this document (http://trustee.ietf.org/license-info).
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document.
to this document.
Abstract Abstract
This document requests a vendor-specific DHCPv6 message assignment. This document requests a vendor-specific DHCPv6 message assignment.
This message can be used for vendor specific and experimental This message can be used for vendor specific and experimental
purposes. purposes.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
skipping to change at page 3, line 7 skipping to change at page 3, line 7
3. Vendor-specific Message . . . . . . . . . . . . . . . . . . . . 3 3. Vendor-specific Message . . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
6.1. Normative References . . . . . . . . . . . . . . . . . . . 6 6.1. Normative References . . . . . . . . . . . . . . . . . . . 6
6.2. Informative References . . . . . . . . . . . . . . . . . . 6 6.2. Informative References . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
The DHCPv6 [RFC3315] protocol specifies a mechanism for the DHCPv6 [RFC3315] specifies a mechanism for the assignment of
assignment of addresses and configuration information to nodes. The addresses and configuration information to nodes. The protocol
protocol provides for 256 possible message codes, of which a small provides for 256 possible message codes, of which a small number are
number are assigned ([DHCPv6Params]). Each of the assigned message assigned ([DHCPv6Params]). Each of the assigned message codes have
codes have specific purposes. New message codes are assigned through specific purposes. New message codes are assigned through Standards
IETF Standards Action as defined in [RFC2434] (see Section 24 of Action (see Section 24 of [RFC3315]).
[RFC3315]).
There may be a need for vendors of DHCPv6 clients, relay agents, or There may be a need for vendors of DHCPv6 clients, relay agents, or
servers to experiment with new capabilities that require new messages servers to experiment with new capabilities that require new messages
to be exchanged between these elements. Thus, this document defines to be exchanged between these elements. Thus, this document defines
the format for and requests that a new message code be reserved for the format for and requests that a new message code be reserved for
vendor-specific and experimental purposes. vendor-specific and experimental purposes.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 4, line 20 skipping to change at page 4, line 20
| msg-type | enterprise-number | | msg-type | enterprise-number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| enterprise- | vendor | | | enterprise- | vendor | |
| number (contd)| msg-type | . | number (contd)| msg-type | .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ .
. options . . options .
. (variable length) . . (variable length) .
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
msg-type VENDOR-SPECIFIC (to-be-assigned) msg-type VENDOR-SPECIFIC (TBD)
enterprise-number The vendor's registered Enterprise Number as enterprise-number The vendor's registered Enterprise Number as
registered with [EID]. registered with [EID].
vendor-msg-type The vendor's message-type. The values are vendor-msg-type The vendor's message-type. The values are
defined by the vendor identified in the defined by the vendor identified in the
enterprise-number field and are not managed enterprise-number field and are not managed
by IANA. by IANA.
options The vendor specific options carried in this options The vendor specific options carried in this
skipping to change at page 6, line 19 skipping to change at page 6, line 19
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
[EID] IANA, "Private Enterprise Numbers. [EID] IANA, "Private Enterprise Numbers.
http://www.iana.org/assignments/enterprise-numbers". http://www.iana.org/assignments/enterprise-numbers".
6.2. Informative References 6.2. Informative References
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998.
[DHCPv6Params] [DHCPv6Params]
IANA, "Dynamic Host Configuration Protocol for IPv6 IANA, "Dynamic Host Configuration Protocol for IPv6
(DHCPv6). (DHCPv6).
http://www.iana.org/assignments/dhcpv6-parameters". http://www.iana.org/assignments/dhcpv6-parameters".
Author's Address Author's Address
Bernard Volz Bernard Volz
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Ave. 1414 Massachusetts Ave.
 End of changes. 8 change blocks. 
22 lines changed or deleted 16 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/