Internet DRAFT - draft-blatherwick-dhc-mitel-site-options-usage
draft-blatherwick-dhc-mitel-site-options-usage
Dynamic Host Configuration Working Group Peter Blatherwick
Internet-Draft Mitel Networks
Expires: November 28, 2005 May 27, 2005
Mitel Usage of DHCPv4 Vendor Options 128 - 135
draft-blatherwick-dhc-mitel-site-options-usage-00.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 28, 2005.
Copyright Notice
Copyright (C) The Internet Society (2005).
Abstract
This informational document describes Mitel Network's current usage
of DHCPv4 options 128 - 135, in order to provide input for the
process of reclassifying the DHCPv4 site-specific options range as
part of RFC 3942. This is also intended to complete the process of
requesting options 128 - 135 be placed in the "Tentatively Assigned"
state by IANA, as described in RFC 3942.
Blatherwick Expires November 28, 2005 [Page 1]
Internet-Draft Mitel DHCPv4 Vendor Options May 2005
Table of Contents
1. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Current Usage of DHCPv4 Options 128 - 135 . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . 4
6. Normative References . . . . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 4
Intellectual Property and Copyright Statements . . . . . . . . 5
Blatherwick Expires November 28, 2005 [Page 2]
Internet-Draft Mitel DHCPv4 Vendor Options May 2005
1. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
2. Introduction
RFC 3942 reclassifies DHCPv4 options in the range 128 - 223 as
"publicly defined", and open to standardization. Formerly, RFC 2132
had defined options in this range as "site-specific", to be used for
site-specific needs. RFC 3942 also defines a process for vendors to
publish their current usage of options in the reclassified range, and
request that these options be placed in "Tentatively Assigned" state
by IANA.
This document is in response to that process, providing information
on Mitel Network's current usage of DHCPv4 options in the range
128 - 135 (inclusive), and requests these options be placed in
Tentatively Assigned.
3. Current Usage of DHCPv4 Options 128 - 135
Mitel Networks currently makes use of DHCPv4 options 128 - 135
(inclusive), in the RFC 3942 reclassified range. Specific usage is
given in the table below, along with a brief description of each.
All are related to configuration of IP Phones (and similar devices)
in a Voice over Internet Protocol (VoIP) environment.
Option Usage
====== =====
128 TFPT Server IP address (for IP Phone-specific software load)
129 Call Server IP address
130 Discrimination string (to identify vendor)
131 Remote statistics server IP address
132 802.1P VLAN ID
133 802.1Q L2 Priority
134 Diffserv Code Point
135 HTTP Proxy for phone-specific applications
4. IANA Considerations
This document describes DHCPv4 options 128 - 135 (inclusive)
currently in use by Mitel Networks. It is requested that IANA place
these options in "Tentatively Assigned" state, as described in
[RFC3942].
Blatherwick Expires November 28, 2005 [Page 3]
Internet-Draft Mitel DHCPv4 Vendor Options May 2005
5. Security Considerations
This document in and by itself provides no security, nor does it
impact existing security.
6. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2132] Alexander, S. and Droms R., "DHCP Options and BOOTP Vendor
Extensions", RFC 2132, March 1997.
[RFC3942] Volz, B., "Reclassifying Dynamic Host Configuration
Protocol version 4 (DHCPv4) Options", RFC 3942, November
2004.
Author's Address
Peter Blatherwick
Mitel Networks
350 Legget Dr.
Ottawa, Ontario, K2K 2W7
Canada
Phone: +1 613-592-5660
EMail: peter_blatherwick@mitel.com
Blatherwick Expires November 28, 2005 [Page 4]
Internet-Draft Mitel DHCPv4 Vendor Options May 2005
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
Blatherwick Expires November 28, 2005 [Page 5]
