draft-ietf-dhc-agent-vpn-id-00.txt   draft-ietf-dhc-agent-vpn-id-01.txt 
Network Working Group Kim Kinnear Network Working Group Kim Kinnear
INTERNET DRAFT Mark Stapp INTERNET DRAFT Mark Stapp
Richard Johnson Richard Johnson
Jay Kumarasamy Jay Kumarasamy
Cisco Systems Cisco Systems
July 2001 March 2002
Expires January 2002 Expires August 2002
VPN Identifier sub-option VPN Identifier sub-option
for the Relay Agent Information Option for the Relay Agent Information Option
<draft-ietf-dhc-agent-vpn-id-00.txt> <draft-ietf-dhc-agent-vpn-id-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 1, line 39 skipping to change at page 1, line 39
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.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract Abstract
In some environments, a relay agent resides in a network element In some environments, a relay agent resides in a network element
which also has access to one or more VPNs. If one DHCP server wishes which also has access to one or more VPNs. If one DHCP server wishes
to offer service to DHCP clients on those different VPNs the DHCP to offer service to DHCP clients on those different VPNs the DHCP
server needs to know the VPN on which each client resides. The vpn- server needs to know the VPN on which each client resides. The vpn-
id sub-option of the relay-agent-information option is used by the id sub-option of the relay-agent-information option is used by the
relay agent to tell the DHCP server the VPN for every DHCP request it relay agent to tell the DHCP server the VPN for every DHCP request it
passes on to the DHCP server, and is also used to properly forward passes on to the DHCP server, and is also used to properly forward
skipping to change at page 5, line 51 skipping to change at page 5, line 51
general) communicate directly back to the program that sent in the general) communicate directly back to the program that sent in the
malicious DHCP packet, the entire cycle of creating a lease will not malicious DHCP packet, the entire cycle of creating a lease will not
be completed. Certainly many leases could be offered, which would be completed. Certainly many leases could be offered, which would
result in a form of address-pool exhaustion. result in a form of address-pool exhaustion.
Under the current DHCP security model there are no methods available Under the current DHCP security model there are no methods available
to completely circumvent this type of attack. to completely circumvent this type of attack.
5. IANA Considerations 5. IANA Considerations
IANA has assigned the value of TBD for the VPN Identifier sub-option
from the DHCP Relay Agent Sub-options space [RFC 3046] for the VPN
Identifier sub-option defined in Section 3.
This document defines a number space for the type byte of the vpn-id This document defines a number space for the type byte of the vpn-id
sub-option. Certain allowable values for this byte are defined in sub-option. Certain allowable values for this byte are defined in
this specification. New values may only be defined by IETF Con- this specification (see Section 3). New values may only be defined
sensus, as described in [RFC 2434]. Basically, this means that they by IETF Consensus, as described in [RFC 2434]. Basically, this means
are defined by RFCs approved by the IESG. that they are 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-id option. The made concurrently in the type byte codes of the vpn-id option. The
type bytes and data formats of the vpn-id option and vpn-id sub- type bytes and data formats of the vpn-id option and vpn-id sub-
option MUST always be identical. option MUST always be identical.
6. Acknowledgments 6. Acknowledgments
None (yet). None (yet).
skipping to change at page 6, line 43 skipping to change at page 6, line 47
3046, January 2001. 3046, January 2001.
8. Author's information 8. Author's information
Kim Kinnear Kim Kinnear
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) 497-8000
EMail: kkinnear@cisco.com EMail: kkinnear@cisco.com
mjs@cisco.com mjs@cisco.com
Jay Kumarasamy Jay Kumarasamy
Richard Johnson Richard Johnson
Cisco Systems Cisco Systems
170 W. Tasman Dr. 170 W. Tasman Dr.
San Jose, CA 95134 San Jose, CA 95134
Phone: (408) 526-4000 Phone: (408) 526-4000
EMail: jayk@cisco.com EMail: jayk@cisco.com
raj@cisco.com raj@cisco.com
skipping to change at page 7, line 15 skipping to change at page 7, line 18
Richard Johnson Richard Johnson
Cisco Systems Cisco Systems
170 W. Tasman Dr. 170 W. Tasman Dr.
San Jose, CA 95134 San Jose, CA 95134
Phone: (408) 526-4000 Phone: (408) 526-4000
EMail: jayk@cisco.com EMail: jayk@cisco.com
raj@cisco.com raj@cisco.com
9. Full Copyright Statement 9. Intellectual Property Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. The IETF takes no position regarding the validity or scope of any intel-
lectual property 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; neither does it represent that it has made any effort to
identify any such rights. Information on the IETF's procedures with
respect to rights in standards-track and standards-related documentation
can be found in BCP-11. Copies of claims of rights made available for
publication 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 implementors or users of this
specification can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights
which may cover technology that may be required to practice this stan-
dard. Please address the information to the IETF Executive Director.
10. Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to oth- This document and translations of it may be copied and furnished to oth-
ers, and derivative works that comment on or otherwise explain it or ers, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and dis- assist in its implementation may be prepared, copied, published and dis-
tributed, in whole or in part, without restriction of any kind, provided tributed, in whole or in part, without restriction of any kind, provided
that the above copyright notice and this paragraph are included on all that the above copyright notice and this paragraph are included on all
such copies and derivative works. However, this document itself may not such copies and derivative works. However, this document itself may not
be modified in any way, such as by removing the copyright notice or be modified in any way, such as by removing the copyright notice or
references to the Internet Society or other Internet organizations, references to the Internet Society or other Internet organizations,
except as needed for the purpose of developing Internet standards in except as needed for the purpose of developing Internet standards in
which case the procedures for copyrights defined in the Internet Stan- which case the procedures for copyrights defined in the Internet Stan-
dards process must be followed, or as required to translate it into dards process must be followed, or as required to translate it into
languages other than English. languages other than English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
 End of changes. 

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