DHC WG C. Zhu
Internet-Draft Y. Tu
Intended status: Standards Track ZTE Corporation
Expires: October 19, 2013 April 17, 2013
VLAN Identifier option in DHCP
draft-zhu-dhc-vlan-id-option-01.txt
Abstract
This document defines a new option for the Dynamic Host Configuration
Protocol for IPv4 and IPv6. This option can be used by the DHCP
server to carry the VLAN identifier to the DHCP client to distinguish
different connections in the access network.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on October 19, 2013.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Zhu & Tu Expires October 19, 2013 [Page 1]
Internet-Draft VLAN Identifier option in DHCP April 2013
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions & Terminology . . . . . . . . . . . . . . . . . . . 3
2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3
3. VLAN ID Option Format . . . . . . . . . . . . . . . . . . . . . 3
4. DHCP Client Behavior . . . . . . . . . . . . . . . . . . . . . 5
5. DHCP Server Behavior . . . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5
9. Normative References . . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
Zhu & Tu Expires October 19, 2013 [Page 2]
Internet-Draft VLAN Identifier option in DHCP April 2013
1. Introduction
There are some use cases where the mobile node can access to one core
network through another access network, such as using WLAN access to
the 3GPP EPC network. Currently the mobile node will always
establish one connection using the WLAN network, but 3GPP EPC network
can support multiple connections to be established for one mobile
node. As the WLAN is a kind of share link access network, to support
multiple connections establishment, some kinds of identifiers can be
used to distinguish the different connections associated with the
mobile node, and the VLAN identifier is proposed to be used here.
The Dynamic Host Configuration Protocol (DHCP) is built on a client-
server model, where designated DHCP server allocate network addresses
and deliver configuration parameters to dynamically configured hosts.
The DHCP server is the right network entity to carry the VLAN
identifier for each connection to the DHCP client which collocated
with the mobile node.
The changes to [RFC2131,RFC3315] defined in this document introduce a
new DHCP option to carry the VLAN identifier by the DHCP server to
the DHCP client.
2. Conventions & Terminology
2.1. Conventions
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 RFC 2119 [RFC2119].
2.2. Terminology
All the DHCP related terms used in this document to be interpreted as
defined in the Dynamic Host Configuration Protocol v4
(DHCPv4)[RFC2131] and Dynamic Host Configuration Protocol v6
(DHCPv6)[RFC3315] specifications. DHCP refers to both DHCPv4 and
DHCPv6 messages and entities throughout this document.
3. VLAN ID Option Format
VLAN Identifier option carries information to identify the different
connections associate with one mobile node.
The format of the VLAN-Identifier option is shown below.
Zhu & Tu Expires October 19, 2013 [Page 3]
Internet-Draft VLAN Identifier option in DHCP April 2013
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VLAN-ID | option-Len | VLAN-ID Value...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: VLAN-ID Option for DHCPv4
option-code
8-bit code VLAN Identifier
option-length
8-bit unsigned integer indicating length in octets of this option
VLAN-ID Value
12-bits field containing the VLAN identifier as specified in IEEE
802.11.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VLAN-ID | option-Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VLAN-ID Value |
+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: VLAN-ID Option for DHCPv6
option-code
16-bit code VLAN Identifier
option-length
16-bit unsigned integer indicating length in octets of this option
VLAN-ID Value
Zhu & Tu Expires October 19, 2013 [Page 4]
Internet-Draft VLAN Identifier option in DHCP April 2013
12-bits field containing the VLAN identifier as specified in IEEE
802.11.
4. DHCP Client Behavior
The DHCP Client may ignore the VLAN identifier option in the payload
of downstream DHCP messages from DHCP server if it is unable to
understand.
5. DHCP Server Behavior
DHCP server may include the VLAN identifier option in the payload of
DHCP messages sent to the DHCP client. The VLAN identifier
information in the DHCP server is generated by other network
elements, such as WLAN Access Gateway, and how can these information
to be carried to DHCP server is out of scope of this document.
6. IANA Considerations
TBD
7. Security Considerations
This document does not have security considerations.
8. Acknowledgements
The author would like to acknowledge all the discussions related to
this document in the DHC working group.
9. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol",
RFC 2131, March 1997.
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003.
Zhu & Tu Expires October 19, 2013 [Page 5]
Internet-Draft VLAN Identifier option in DHCP April 2013
Authors' Addresses
Chunhui Zhu
ZTE Corporation
68,Zijinghua RD,Yuhuatai District
Nanjing, Jiangsu 210012
China
Email: zhu.chunhui@zte.com.cn
Yangwei Tu
ZTE Corporation
68,Zijinghua RD,Yuhuatai District
Nanjing, Jiangsu 210012
China
Email: tu.yangwei@zte.com.cn
Zhu & Tu Expires October 19, 2013 [Page 6]