draft-ietf-dhc-vpn-option-00.txt   draft-ietf-dhc-vpn-option-01.txt 
Request for Comments: DRAFT Richard Johnson Request for Comments: DRAFT Richard Johnson
Kim Kinnear Kim Kinnear
Mark Stapp Mark Stapp
Jay Kumarasamy Jay Kumarasamy
Cisco Systems, Inc. Cisco Systems, Inc.
July 2001 November 2001
Expires January 2001 Expires May 2001
DHCP VPN Information option DHCP VPN Information option
<draft-ietf-dhc-vpn-option-00.txt> <draft-ietf-dhc-vpn-option-01.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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.
skipping to change at page 2, line 5 skipping to change at page 2, line 5
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ds.internic.net (US East Coast), nic.nordu.net Directories on ds.internic.net (US East Coast), nic.nordu.net
(Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific
Rim). Rim).
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
DRAFT DHCP VPN Information option July 2001 DRAFT DHCP VPN Information option November 2001
Abstract Abstract
This memo defines a new DHCP option for passing VPN information This memo defines a new DHCP option for passing VPN information
between the DHCP client and the DHCP server. It is intended for use between the DHCP client and the DHCP server. It is intended for use
primarily by DHCP proxy clients in situations where VPN information primarily by DHCP proxy clients in situations where VPN information
needs to be passed to the DHCP server for proper address allocation needs to be passed to the DHCP server for proper address allocation
to take place. to take place.
Introduction Introduction
skipping to change at page 3, line 5 skipping to change at page 3, line 5
Code Len Type VPN Information octets Code Len Type VPN Information octets
+-----+-----+------+-----+-----+-----+--- +-----+-----+------+-----+-----+-----+---
| TBD | n | t | v1 | v2 | v3 | ... | TBD | n | t | v1 | v2 | v3 | ...
+-----+-----+------+-----+-----+-----+--- +-----+-----+------+-----+-----+-----+---
Type: 0 NVT ASCII VPN identifier Type: 0 NVT ASCII VPN identifier
1 RFC2685 VPN-ID 1 RFC2685 VPN-ID
2-255 Not Allowed 2-255 Not Allowed
DRAFT DHCP VPN Information option July 2001 DRAFT DHCP VPN Information option November 2001
The option minimum length (n) is 2. The option minimum length (n) is 2.
There are two types of identifiers which can be placed in the VPN There are two types of identifiers which can be placed in the VPN
Information Suboption. The first type of identifier which can be Information Suboption. The first type of identifier which can be
placed in the VPN Information Suboption is an NVT ASCII string. It placed in the VPN Information Suboption is an NVT ASCII string. It
MUST NOT be terminated with a zero byte. MUST NOT be terminated with a zero byte.
The second type of identifier which can be placed in the VPN The second type of identifier which can be placed in the VPN
Information Suboption is an RFC2685 VPN-ID [RFC 2685], which is Information Suboption is an RFC2685 VPN-ID [RFC 2685], which is
skipping to change at page 4, line 5 skipping to change at page 4, line 5
In the event that a VPN Informmation Option and a VPN Information In the event that a VPN Informmation Option and a VPN Information
Relay Suboption are both received in a particular DHCP client packet, Relay Suboption are both received in a particular DHCP client packet,
the information from the VPN Information Suboption MUST be used in the information from the VPN Information Suboption MUST be used in
preference to the information in the VPN Information Option. preference to the information in the VPN Information Option.
Servers that do not understand this option will allocate an address Servers that do not understand this option will allocate an address
using their normal algorithms and will not return this option in the using their normal algorithms and will not return this option in the
DHCPOFFER or DHCPACK. In this case the client will discard the DHCPOFFER or DHCPACK. In this case the client will discard the
DHCPOFFER or DHCPACK. Servers that understand this option but are DHCPOFFER or DHCPACK. Servers that understand this option but are
DRAFT DHCP VPN Information option July 2001 DRAFT DHCP VPN Information option November 2001
administratively configured to ignore the option MUST ignore the administratively configured to ignore the option MUST ignore the
option, use their normal algorithms to allocate an address, and MUST option, use their normal algorithms to allocate an address, and MUST
NOT return this option in the DHCPOFFER or DHCPACK. In this case the NOT return this option in the DHCPOFFER or DHCPACK. In this case the
client will discard the DHCPOFFER or DHCPACK. In other words, this client will discard the DHCPOFFER or DHCPACK. In other words, this
option MUST not appear in a DHCPOFFER from a server unless it was option MUST not appear in a DHCPOFFER from a server unless it was
used by the server in making the address allocation requested. used by the server in making the address allocation requested.
Security Considerations Security Considerations
skipping to change at page 5, line 5 skipping to change at page 5, line 5
in this document. No assignment of values for the type field need be in this document. No assignment of values for the type field need be
made at this time. New values may only be defined by IETF Consensus, made at this time. New values may only be defined by IETF Consensus,
as described in [RFC 2434]. Basically, this means that they are as described in [RFC 2434]. Basically, this means that they are
defined by RFCs approved by the IESG. defined by RFCs approved by the IESG.
Moreover, any changes or additions to the type byte codes MUST be Moreover, any changes or additions to the type byte codes MUST be
made concurrently in the type byte codes of the VPN Information made concurrently in the type byte codes of the VPN Information
Option. The type bytes and data formats of the VPN Information Option. The type bytes and data formats of the VPN Information
Option and VPN Information Suboption MUST always be identical. Option and VPN Information Suboption MUST always be identical.
DRAFT DHCP VPN Information option July 2001 DRAFT DHCP VPN Information option November 2001
Acknowledgements Acknowledgements
This document is the result of work done within Cisco Systems. This document is the result of work done within Cisco Systems.
Thanks to Kim Kinnear, Mark Stapp, and Jay Kumarasamy for their work Thanks to Kim Kinnear, Mark Stapp, and Jay Kumarasamy for their work
on this option definition and the other related work for which this on this option definition and the other related work for which this
is necessary. is necessary.
References References
skipping to change at page 6, line 5 skipping to change at page 6, line 5
Mark Stapp Mark Stapp
Cisco Systems Cisco Systems
250 Apollo Drive 250 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Phone: (978) 244-8000 Phone: (978) 244-8000
EMail: kkinnear@cisco.com EMail: kkinnear@cisco.com
mjs@cisco.com mjs@cisco.com
DRAFT DHCP VPN Information option July 2001 DRAFT DHCP VPN Information option November 2001
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/