idnits 2.17.1 draft-zhu-dhc-vlan-id-option-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (April 17, 2013) is 4026 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 3315 (Obsoleted by RFC 8415) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DHC WG C. Zhu 3 Internet-Draft Y. Tu 4 Intended status: Standards Track ZTE Corporation 5 Expires: October 19, 2013 April 17, 2013 7 VLAN Identifier option in DHCP 8 draft-zhu-dhc-vlan-id-option-01.txt 10 Abstract 12 This document defines a new option for the Dynamic Host Configuration 13 Protocol for IPv4 and IPv6. This option can be used by the DHCP 14 server to carry the VLAN identifier to the DHCP client to distinguish 15 different connections in the access network. 17 Status of this Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on October 19, 2013. 34 Copyright Notice 36 Copyright (c) 2013 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 2. Conventions & Terminology . . . . . . . . . . . . . . . . . . . 3 53 2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3. VLAN ID Option Format . . . . . . . . . . . . . . . . . . . . . 3 56 4. DHCP Client Behavior . . . . . . . . . . . . . . . . . . . . . 5 57 5. DHCP Server Behavior . . . . . . . . . . . . . . . . . . . . . 5 58 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 59 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 60 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 61 9. Normative References . . . . . . . . . . . . . . . . . . . . . 5 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 64 1. Introduction 66 There are some use cases where the mobile node can access to one core 67 network through another access network, such as using WLAN access to 68 the 3GPP EPC network. Currently the mobile node will always 69 establish one connection using the WLAN network, but 3GPP EPC network 70 can support multiple connections to be established for one mobile 71 node. As the WLAN is a kind of share link access network, to support 72 multiple connections establishment, some kinds of identifiers can be 73 used to distinguish the different connections associated with the 74 mobile node, and the VLAN identifier is proposed to be used here. 76 The Dynamic Host Configuration Protocol (DHCP) is built on a client- 77 server model, where designated DHCP server allocate network addresses 78 and deliver configuration parameters to dynamically configured hosts. 79 The DHCP server is the right network entity to carry the VLAN 80 identifier for each connection to the DHCP client which collocated 81 with the mobile node. 83 The changes to [RFC2131,RFC3315] defined in this document introduce a 84 new DHCP option to carry the VLAN identifier by the DHCP server to 85 the DHCP client. 87 2. Conventions & Terminology 89 2.1. Conventions 91 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 92 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 93 document are to be interpreted as described in RFC 2119 [RFC2119]. 95 2.2. Terminology 97 All the DHCP related terms used in this document to be interpreted as 98 defined in the Dynamic Host Configuration Protocol v4 99 (DHCPv4)[RFC2131] and Dynamic Host Configuration Protocol v6 100 (DHCPv6)[RFC3315] specifications. DHCP refers to both DHCPv4 and 101 DHCPv6 messages and entities throughout this document. 103 3. VLAN ID Option Format 105 VLAN Identifier option carries information to identify the different 106 connections associate with one mobile node. 108 The format of the VLAN-Identifier option is shown below. 110 0 1 2 3 111 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 112 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 113 | VLAN-ID | option-Len | VLAN-ID Value... 114 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 116 Figure 1: VLAN-ID Option for DHCPv4 118 option-code 120 8-bit code VLAN Identifier 122 option-length 124 8-bit unsigned integer indicating length in octets of this option 126 VLAN-ID Value 128 12-bits field containing the VLAN identifier as specified in IEEE 129 802.11. 131 0 1 2 3 132 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 133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 | VLAN-ID | option-Len | 135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 136 | VLAN-ID Value | 137 +-+-+-+-+-+-+-+-+-+-+-+-+ 139 Figure 2: VLAN-ID Option for DHCPv6 141 option-code 143 16-bit code VLAN Identifier 145 option-length 147 16-bit unsigned integer indicating length in octets of this option 149 VLAN-ID Value 150 12-bits field containing the VLAN identifier as specified in IEEE 151 802.11. 153 4. DHCP Client Behavior 155 The DHCP Client may ignore the VLAN identifier option in the payload 156 of downstream DHCP messages from DHCP server if it is unable to 157 understand. 159 5. DHCP Server Behavior 161 DHCP server may include the VLAN identifier option in the payload of 162 DHCP messages sent to the DHCP client. The VLAN identifier 163 information in the DHCP server is generated by other network 164 elements, such as WLAN Access Gateway, and how can these information 165 to be carried to DHCP server is out of scope of this document. 167 6. IANA Considerations 169 TBD 171 7. Security Considerations 173 This document does not have security considerations. 175 8. Acknowledgements 177 The author would like to acknowledge all the discussions related to 178 this document in the DHC working group. 180 9. Normative References 182 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 183 Requirement Levels", BCP 14, RFC 2119, March 1997. 185 [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", 186 RFC 2131, March 1997. 188 [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., 189 and M. Carney, "Dynamic Host Configuration Protocol for 190 IPv6 (DHCPv6)", RFC 3315, July 2003. 192 Authors' Addresses 194 Chunhui Zhu 195 ZTE Corporation 196 68,Zijinghua RD,Yuhuatai District 197 Nanjing, Jiangsu 210012 198 China 200 Email: zhu.chunhui@zte.com.cn 202 Yangwei Tu 203 ZTE Corporation 204 68,Zijinghua RD,Yuhuatai District 205 Nanjing, Jiangsu 210012 206 China 208 Email: tu.yangwei@zte.com.cn