draft-bhandari-dhc-access-network-identifier-03.txt   draft-bhandari-dhc-access-network-identifier-04.txt 
Network Working Group S. Bhandari Network Working Group S. Bhandari
Internet-Draft S. Gundavelli Internet-Draft S. Gundavelli
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: October 4, 2013 J. Korhonen Expires: October 18, 2013 J. Korhonen
Renesas Mobile Renesas Mobile
M. Grayson M. Grayson
Cisco Systems Cisco Systems
April 02, 2013 April 16, 2013
Access-Network-Identifier Option in DHCP Access-Network-Identifier Option in DHCP
draft-bhandari-dhc-access-network-identifier-03 draft-bhandari-dhc-access-network-identifier-04
Abstract Abstract
This document specifies the format and mechanism that is to be used This document specifies the format and mechanism that is to be used
for encoding access network identifiers in DHCPv4 and DHCPv6 messages for encoding access network identifiers in DHCPv4 and DHCPv6 messages
by defining new access network identifier options and sub-options. by defining new access network identifier options and sub-options.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 4, 2013. This Internet-Draft will expire on October 18, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 23 skipping to change at page 2, line 23
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. DHCPv4 Access-Network-Identifier Option . . . . . . . . . . . 5 4. DHCPv4 Access-Network-Identifier Option . . . . . . . . . . . 5
4.1. DHCPv4 Access-Network-Identifier Sub-options . . . . . . . 5 4.1. DHCPv4 Access-Network-Identifier Sub-options . . . . . . . 5
5. DHCPv6 Access-Network-Identifier options . . . . . . . . . . . 6 5. DHCPv6 Access-Network-Identifier options . . . . . . . . . . . 6
6. DHCPv4 and DHCPv6 Access-Network-Identifier Options . . . . . 6 6. DHCPv4 and DHCPv6 Access-Network-Identifier Options . . . . . 6
6.1. Access-Network-Type option . . . . . . . . . . . . . . . . 6 6.1. Access-Network-Type option . . . . . . . . . . . . . . . . 6
6.2. Network-Identifier option . . . . . . . . . . . . . . . . 8 6.2. Network-Identifier options . . . . . . . . . . . . . . . . 8
6.3. Operator-Identifier option . . . . . . . . . . . . . . . . 9 6.3. Operator identifier options . . . . . . . . . . . . . . . 11
7. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . 11 7. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . 12
8. Relay Agent Behavior . . . . . . . . . . . . . . . . . . . . . 11 8. Relay Agent Behavior . . . . . . . . . . . . . . . . . . . . . 13
9. Server Behavior . . . . . . . . . . . . . . . . . . . . . . . 11 9. Server Behavior . . . . . . . . . . . . . . . . . . . . . . . 13
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
10.1. DHCPv4 Access-Network-Identifier Sub-option registry . . . 12 11. Security Considerations . . . . . . . . . . . . . . . . . . . 14
11. Security Considerations . . . . . . . . . . . . . . . . . . . 12 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13 13. Change log . . . . . . . . . . . . . . . . . . . . . . . . . . 14
13. Change log . . . . . . . . . . . . . . . . . . . . . . . . . . 13 14. Normative References . . . . . . . . . . . . . . . . . . . . . 15
14. Normative References . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
Access network identification of a network device has a range of Access network identification of a network device has a range of
application. The local mobility anchor in a Proxy Mobile IPv6 domain application. For e.g. The local mobility anchor in a Proxy Mobile
is able to provide access network and access operator specific IPv6 domain is able to provide access network and access operator
handling or policing of the mobile node traffic using information specific handling or policing of the mobile node traffic using
about the access network to which the mobile node is attached. information about the access network to which the mobile node is
attached.
This document specifies Dynamic Host Configuration Protocol v4 This document specifies Dynamic Host Configuration Protocol v4
(DHCPv4) [RFC2131] and Dynamic Host Configuration Protocol v6 (DHCPv4) [RFC2131] and Dynamic Host Configuration Protocol v6
(DHCPv6) [RFC3315] options for access network identification that is (DHCPv6) [RFC3315] options for access network identification that is
added by Client or Relay agent in the DHCPv4 or DHCPv6 messages added by Client or Relay agent in the DHCPv4 or DHCPv6 messages
towards the Server. towards the Server.
Dynamic Host Configuration Protocol (DHCP) client or DHCP relay agent Dynamic Host Configuration Protocol (DHCP) client or DHCP relay agent
aware of the access network and access operator add this information aware of the access network and access operator add this information
in the DHCP messages. DHCP relay agent or DHCP server in the mobile in the DHCP messages. This information can be used to provide
access gateway can pass this information towards local mobility differentiated services and policing of traffic based on the access
anchor either via Proxy Mobile IPv6 signaling or by relaying the DHCP network to which a client is attached. Examples of how this
messages to DHCP entity within the local mobility anchor. information can be used in mobile networks can be found in [RFC6757]
2. Motivation 2. Motivation
Proxy mobile IPv6 [RFC5213] can be used for supporting network-based Proxy mobile IPv6 [RFC5213] can be used for supporting network-based
mobility management in various type of network deployments. The mobility management in various type of network deployments. The
network architectures, such as Service provider Wi-Fi access network architectures, such as Service provider Wi-Fi access
aggregation or, WLAN integrated mobile packet core are examples where aggregation or, WLAN integrated mobile packet core are examples where
Proxy Mobile IPv6 is a component of the overall architecture. Some Proxy Mobile IPv6 is a component of the overall architecture. Some
of these architectures require the ability of the local mobility of these architectures require the ability of the local mobility
anchor (LMA) [RFC5213] to provide differentiated services and anchor (LMA) [RFC5213] to provide differentiated services and
skipping to change at page 3, line 47 skipping to change at page 3, line 48
such as PCC [TS23203] and ANDSF [TS23402] in 3GPP system allow such as PCC [TS23203] and ANDSF [TS23402] in 3GPP system allow
configuration of policy rules with conditions based on the access configuration of policy rules with conditions based on the access
network information. For example, the service treatment for the network information. For example, the service treatment for the
mobile node's traffic may be different when they are attached to a mobile node's traffic may be different when they are attached to a
access network owned by the home operator than when owned by a access network owned by the home operator than when owned by a
roaming partner. The service treatment can also be different based roaming partner. The service treatment can also be different based
on the configured Service Set Identifiers (SSID) in case of IEEE on the configured Service Set Identifiers (SSID) in case of IEEE
802.11 based access networks. Other examples of services include the 802.11 based access networks. Other examples of services include the
operator's ability to apply tariff based on the location. operator's ability to apply tariff based on the location.
The PMIPv6 extension as specified in The PMIPv6 extension as specified in [RFC6757] defines PMIPv6 options
[I-D.ietf-netext-access-network-option] defines PMIPv6 options to to carry access network identifiers in PMIPv6 signaling from Mobile
carry access network identifiers in PMIPv6 signaling from Mobile
Access Gateway (MAG) to LMA. MAG can learn this information from Access Gateway (MAG) to LMA. MAG can learn this information from
DHCP options as inserted by DHCP client or Relay agent before MAG. DHCP options as inserted by DHCP client or Relay agent before MAG.
If MAG relays DHCP messages to LMA as specified in [RFC5844] this If MAG relays DHCP messages to LMA as specified in [RFC5844] this
information can be inserted by MAG towards LMA in the forwarded DHCP information can be inserted by MAG towards LMA in the forwarded DHCP
messages. messages.
Figure 1 illustrates an example Proxy Mobile IPv6 deployment where Figure 1 illustrates an example Proxy Mobile IPv6 deployment where
Access Points (AP) inserts access network identifiers in DHCP Access Points (AP) inserts access network identifiers in DHCP
messages. The mobile access gateway learns this information over messages. The mobile access gateway learns this information over
skipping to change at page 5, line 30 skipping to change at page 5, line 30
+------+------+------+------+------+-- --+-----+ +------+------+------+------+------+-- --+-----+
| code | len | s1 | s2 | s2 | ... | sn | | code | len | s1 | s2 | s2 | ... | sn |
+------+------+------+------+------+-- --+-----+ +------+------+------+------+------+-- --+-----+
code: 8-bit code carrying Access Network Identifier sub-options, code: 8-bit code carrying Access Network Identifier sub-options,
If added by relay agent: Relay Agent Information Option (82) If added by relay agent: Relay Agent Information Option (82)
If added by client: OPTION_ACCESS_NETWORK_ID (TBD1) If added by client: OPTION_ACCESS_NETWORK_ID (TBD1)
len: 8 bit indicating total length of the included suboptions. len: 8 bit indicating total length of the included suboptions.
ANU Sub-options: The ANI Sub-options consists of a ANI Sub-options: The ANI Sub-options consists of a
sequence of SubOpt/Length/Value tuples for each sub-option, encoded sequence of SubOpt/Length/Value tuples for each sub-option, encoded
in the following manner: in the following manner:
SubOpt Len Sub-option Value SubOpt Len Sub-option Value
+------+------+------+------+------+------+--...-+------+ +------+------+------+------+------+------+--...-+------+
| code | N | s1 | s2 | s3 | s4 | | sN | | code | N | s1 | s2 | s3 | s4 | | sN |
+------+------+------+------+------+------+--...-+------+ +------+------+------+------+------+------+--...-+------+
ANI Sub-options are defined in following sections. ANI Sub-options are defined in following sections.
4.1. DHCPv4 Access-Network-Identifier Sub-options 4.1. DHCPv4 Access-Network-Identifier Sub-options
Access network identifier information will be defined in multiple Access network identifier information will be defined in multiple
sub-options. The initial assignment of DHCP access network sub-options. The initial assignment of DHCP access network
identifier Sub-options is as follows: identifier Sub-options is as follows:
Sub-option Code Sub-Option Description Sub-option Code Sub-Option Description
--------------- ---------------------- --------------- ----------------------
TBD5 Access-Network-Type Sub-option TBD7 Access-Network-Type Sub-option
TBD6 Network-Identifier Sub-option TBD8 Network-Name Sub-option
TBD7 Operator-Identifier Sub-option TBD9 AP-Name Sub-option
TBD10 Operator-Identifier Sub-option
TBD11 Operator-Realm Sub-option
5. DHCPv6 Access-Network-Identifier options 5. DHCPv6 Access-Network-Identifier options
The Access Network Identifier option defined here will be added by The Access Network Identifier option defined here will be added by
DHCPv6 client in upstream DHCPv6 messages or by the Relay in Relay- DHCPv6 client in upstream DHCPv6 messages or by the Relay in Relay-
forward messages. forward messages.
Option Code Option Descrption Option Code Descrption
--------------- ---------------------- --------------- ----------------------
TBD2 Access-Network-Type option TBD2 OPTION_ANI_ATT
TBD3 Network-Identifier option TBD3 OPTION_ANI_NETWORK_NAME
TBD4 Operator-Identifier option TBD4 OPTION_ANI_AP_NAME
TBD5 OPTION_ANI_OPERATOR_ID
TBD6 OPTION_ANI_OPERATOR_REALM
6. DHCPv4 and DHCPv6 Access-Network-Identifier Options 6. DHCPv4 and DHCPv6 Access-Network-Identifier Options
This section defines DHCPv4 suboption and DHCPv6 options for access This section defines DHCPv4 suboption and DHCPv6 options for access
network identification. network identification.
6.1. Access-Network-Type option 6.1. Access-Network-Type option
This option is used for exchanging the type of the access technology This option is used for exchanging the type of the access technology
by which the client is attached to the network. There can only be a the client is attached to the network. There can only be a single
single instance of this specific option in any DHCPv6 message or instance of this specific option in any DHCPv6 message or single
single instance of this specific sub-option in DHCPv4 instance of this specific sub-option in DHCPv4
OPTION_ACCESS_NETWORK_ID or Relay Agent information option. Its OPTION_ACCESS_NETWORK_ID or Relay Agent information option. Its
format is as follows: format is as follows:
DHCPv4: DHCPv4:
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| suboption-code| Length | ATT | | suboption-code| Length | ATT |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
suboption-code: 8-bit code, it should be set to value of (TBD5), suboption-code: 8-bit code, it should be set to value of (TBD7),
indicating that its a Access-Network-Type sub-option indicating that its a Access-Network-Type sub-option
Length: 8-bit unsigned integer indicating the length of this suboption Length: 8-bit unsigned integer indicating the length of this suboption
in octets, excluding the suboption-code and length fields. in octets, excluding the suboption-code and length fields.
This field MUST be set to 2. This field MUST be set to 2.
DHCPv6: DHCPv6:
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Code (TBD2) | OptLen | | Option Code (TBD2) | OptLen |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ATT + | ATT +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: 16-bit code OPTION_ANI_ATT (TBD2) option-code: 16-bit code OPTION_ANI_ATT (TBD2)
option-length: 16-bit unsigned integer indicating length option-length: 16-bit unsigned integer indicating length
in octets of this option in octets of this option
skipping to change at page 8, line 5 skipping to change at page 8, line 5
The values is as populated from the IANA name space The values is as populated from the IANA name space
Access Technology Type Option type values as requested in [RFC5213] Access Technology Type Option type values as requested in [RFC5213]
0: Reserved ("Reserved") 0: Reserved ("Reserved")
1: Virtual ("Logical Network Interface") 1: Virtual ("Logical Network Interface")
2: PPP ("Point-to-Point Protocol") 2: PPP ("Point-to-Point Protocol")
3: IEEE 802.3 ("Ethernet") 3: IEEE 802.3 ("Ethernet")
4: IEEE 802.11a/b/g ("Wireless LAN") 4: IEEE 802.11a/b/g ("Wireless LAN")
5: IEEE 802.16e ("WIMAX") 5: IEEE 802.16e ("WIMAX")
6.2. Network-Identifier option 6.2. Network-Identifier options
This option can be used for carrying the name of the access network These options can be used for carrying the name of the access network
(e.g., a SSID in case of IEEE 802.11 Access Network, or PLMN (e.g., a SSID in case of IEEE 802.11 Access Network, or PLMN
Identifier [TS23003] in case of 3GPP access ), to which the client is Identifier [TS23003] in case of 3GPP access ) and Access Point name,
attached. There can only be a single instance of this specific to which the client is attached. There can only be a single instance
option in any DHCPv6 message or single instance of this specific sub- of each of these options in any DHCPv6 message or single instance of
option in DHCPv4 OPTION_ACCESS_NETWORK_ID or Relay Agent information each of these sub-options in DHCPv4 OPTION_ACCESS_NETWORK_ID or Relay
option. The format of this option is defined below. Agent information option. The format of these options is defined
below.
DHCPv4: DHCPv4:
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| suboption code | Length |E| Reserved | Net-Name Len | |suboption code | Length | ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Name (e.g., SSID or PLMNID) ~ | Network Name (e.g., SSID or PLMNID) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AP-Name Len | Access-Point Name ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
suboption code: 8-bit code, it should be set to value of (TBD6), suboption code: 8-bit code, it should be set to value of (TBD8),
indicating that its a Network-Identifier sub-option indicating that its a Network-Name sub-option
Length: 8-bit indicating Total length of this sub option, Length: 8-bit indicating Total length of this sub option,
excluding the suboption code and length fields. excluding the suboption code and length fields.
The value can be in the range of 2 to 32 octets. The value can be in the range of 2 to 32 octets.
DHCPv6: DHCPv6:
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Code (TBD3) | OptLen | | Option Code (TBD3) | OptLen |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|E| Reserved | Net-Name Len | | Network Name (e.g., SSID or PLMNID) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Network Name (e.g., SSID or PLMNID) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AP-Name Len | Access-Point Name ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: 16-bit code OPTION_ANI_NETWORK_ID (TBD3) option-code: 16-bit code OPTION_ANI_NETWORK_NAME (TBD3)
option-length: 16-bit unsigned integer indicating length option-length: 16-bit unsigned integer indicating length
in octets of this option.The value can be in the in octets of this option.The value can be in the
range of 2 to 32 octets. range of 2 to 32 octets.
Common format applicable to DHCPv4 and DHCPv6: Common format applicable to DHCPv4 and DHCPv6:
'E'-bit: 1-bit flag for representing the encoding of the following Network Name: The name of the access network to which the mobile
name field. MUST be set to zero (0) if the network name is node is attached. The type of the Network Name is dependent on
encoded using 8-bit octets or to one (1) if the network name is the access technology to which the mobile node is attached. If it
encoded using UTF-8. is 802.11 access, the Network Name MUST be the SSID of the
network. If the access network is 3GPP access, the Network Name
is the PLMN Identifier of the network. If the access network is
3GPP2 access, the Network Name is the
Access Network Identifier [ANI].
Reserved: 7 bits MUST be set to zero when sending and ignored when When encoding the PLMN Identifier, both the Mobile Network Code
received. (MNC) [TS23003] and Mobile Country Code (MCC) [TS23003] MUST be 3
digits. If the MNC in use only has 2 digits, then it MUST be
preceded with a '0'. Encoding MUST be UTF-8.
Net-Name Length: 8-bit field for representing the length of the DHCPv4:
network name to be followed.
Network Name: The name of the access network to which the client 0 1 2 3
is attached. The type of the network-name is dependent on 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
the Access Technology to which the mobile node is attached. If +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
its 802.11 access, the network-name is the SSID of the network. |suboption code | Length | ~
If the access network is 3GPP access, the network-name is the PLMN +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Identifier of the network. If the access network is 3GPP2 access, | Access-Point Name ~
the network-name is the Access Network Identifier [ANI]. +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
When encoding the PLMN Identifier, both MNC and MCC codes MUST be suboption code: 8-bit code, it should be set to value of (TBD9),
3 digits. If the MNC in use only has 2 digits, then it MUST be indicating that its a Network-AP-Name sub-option
preceded with a '0'. Encoding MUST be UTF-8.
AP-Name Length: 8-bit field for representing the length of the Length: 8-bit indicating Total length of this sub option,
access point name to be followed. If the access point name is not excluding the suboption code and length fields.
carried, this length should be set to zero. The value can be in the range of 2 to 32 octets.
Access-Point Name: The name of the access point (physical device DHCPv6:
name) to which the client is attached. This is the
identifier that uniquely identifies the access point. In some
deployments the name can be set to the mac-address of the device.
The string is carried in UTF-8 representation.
6.3. Operator-Identifier option 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Code (TBD3) | OptLen |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access-Point Name ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Operator-Identifier option can be used for carrying the operator option-code: 16-bit code OPTION_ANI_AP_NAME (TBD4)
option-length: 16-bit unsigned integer indicating length
in octets of this option.The value can be in the
range of 2 to 32 octets.
Common format applicable to DHCPv4 and DHCPv6:
Access-Point Name: The name of the access point (physical device
name) to which the mobile node is attached. This is the
identifier that uniquely identifies the access point. While
Network Name (e.g., SSID) identifies the operator's access
network, Access-Point Name identifies a specific network device in
the network to which the mobile node is attached. In some
deployments, the Access-Point Name can be set to the Media Access
Control (MAC) address of the device or some unique identifier that
can be used by the policy systems in the operator network to
unambiguously identify the device. The string is carried in UTF-8
representation.
6.3. Operator identifier options
The Operator identifier options can be used for carrying the operator
identifier of the access network to which the client is identifier of the access network to which the client is
attached.There can only be a single instance of this specific option attached.There can only be a single instance of each of these options
in any DHCPv6 message or single instance of this specific sub-option in any DHCPv6 message or single instance of each of these sub-options
in DHCPv4 OPTION_ACCESS_NETWORK_ID or Relay Agent information option. in DHCPv4 OPTION_ACCESS_NETWORK_ID or Relay Agent information option.
The format of this option is defined below. option. Its format is as The format of these options is defined below.
follows:
DHCPv4: DHCPv4:
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| suboption code | Length | Op-ID Type | | suboptioncode | Length | ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Operator Identifier ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Operator Enterprise ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
suboption code: 8 bit code, It should be set to value of (TBD7), suboption code: 8 bit code, It should be set to value of (TBD10),
indicating that it is Operator-Identifier sub-option indicating that it is Operator-Identifier sub-option
Length: Total length of this sub option, excluding the suboption code Length: Total length of this sub option, excluding the suboption code
and length fields. and length fields.
DHCPv6: DHCPv6:
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Code (TBD4) | OptLen | | Option Code (TBD4) | OptLen |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Op-ID Type | | Operator Enterprise ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Operator Identifier ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: 16-bit code OPTION_ANI_OPERATOR_ID (TBD4) option-code: 16-bit code OPTION_ANI_OPERATOR_ID (TBD5)
option-length: 16-bit unsigned integer indicating length option-length: 16-bit unsigned integer indicating length
in octets of this option. in octets of this option.
Common format applicable to DHCPv4 and DHCPv6: Common format applicable to DHCPv4 and DHCPv6:
Operator Identifier (Op-ID) Type: 8-bit unsigned integer indicating Operator Enterprise ID: Vendor ID as a four octet
the type of the Operator Identifier. Currently the following Private Enterprise Number [SMI].
types are defined:
0 - Reserved. DHCPv4:
1 - Vendor ID as a four octet Private Enterprise Number [SMI]. 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| suboptioncode | Length | ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Operator Realm ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2 - Realm of the operator. Realm names are required to be suboption code: 8 bit code, It should be set to value of (TBD11),
unique, and are piggybacked on the administration of the DNS indicating that it is Operator-Realm sub-option
namespace. Realms are encoded using a domain name encoding
defined in [RFC1035].
Operator Identifier: Up to 253 octets of the operator identifier. Length: Total length of this sub option, excluding the suboption
The encoding of the identifier depends on the used Operator-ID code and length fields.
Type. Numeric values are encoded in network byte order and
strings have no terminating '\0' mark. DHCPv6:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Code (TBD4) | OptLen |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Operator Realm ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: 16-bit code OPTION_ANI_OPERATOR_REALM (TBD6)
option-length: 16-bit unsigned integer indicating length
in octets of this option.
Common format applicable to DHCPv4 and DHCPv6:
Operator Realm: Realm of the operator. Realm names are required to be
unique, and are piggybacked on the administration of the DNS
namespace. Realms are encoded using a domain name encoding
defined in [RFC1035].Up to 253 octets of the operator realm.
7. Client Behavior 7. Client Behavior
All hosts or clients MAY include access network identifier options in All hosts or clients MAY include access network identifier options in
all the upstream DHCP messages to inform the receiver about the all the upstream DHCP messages to inform the receiver about the
access network it is attached to. access network it is attached to.
8. Relay Agent Behavior 8. Relay Agent Behavior
DHCP Relay Agents MAY include these options before forwarding the DHCP Relay Agents MAY include these options before forwarding the
DHCP message to provide information about the access network over DHCP message to provide information about the access network over
which DHCP messages from the client is received. which DHCP messages from the client is received.
9. Server Behavior 9. Server Behavior
If DHCP Server is unable to understand this option it MUST be If DHCP Server is unable to understand this option it MUST be
ignored. There is no requirement that a server return this option ignored. There is no requirement that a server return this option
and its data in a downstream DHCP message. and its data in a downstream DHCP message. If DHCP Server is able to
process these options it MAY use it for address pool selection policy
decisions if configured. It MAY store this information along with
the lease for logging and audit purpose.
10. IANA Considerations 10. IANA Considerations
This document defines DHCPv4 Access Network Identifier option which This document defines DHCPv4 Access Network Identifier option which
requires assignment of DHCPv4 option code TBD1 assigned from "Bootp requires assignment of DHCPv4 option code TBD1 assigned from "Bootp
and DHCP options" registry (http://www.iana.org/assignments/ and DHCP options" registry (http://www.iana.org/assignments/
bootp-dhcp-parameters/bootp-dhcp-parameters.xml), as specified in bootp-dhcp-parameters/bootp-dhcp-parameters.xml), as specified in
[RFC2939]. [RFC2939].
IANA is requested to assign Sub-option codes for the following DHCPv4 IANA is requested to assign Sub-option codes for the following DHCPv4
skipping to change at page 12, line 4 skipping to change at page 13, line 30
10. IANA Considerations 10. IANA Considerations
This document defines DHCPv4 Access Network Identifier option which This document defines DHCPv4 Access Network Identifier option which
requires assignment of DHCPv4 option code TBD1 assigned from "Bootp requires assignment of DHCPv4 option code TBD1 assigned from "Bootp
and DHCP options" registry (http://www.iana.org/assignments/ and DHCP options" registry (http://www.iana.org/assignments/
bootp-dhcp-parameters/bootp-dhcp-parameters.xml), as specified in bootp-dhcp-parameters/bootp-dhcp-parameters.xml), as specified in
[RFC2939]. [RFC2939].
IANA is requested to assign Sub-option codes for the following DHCPv4 IANA is requested to assign Sub-option codes for the following DHCPv4
Sub-options from the "DHCP Relay Agent Sub-Option Codes" Sub-options from the "DHCP Relay Agent Sub-Option Codes"
Sub-option Code Sub-Option Description Sub-option Code Sub-Option Description
--------------- ---------------------- --------------- ----------------------
TBD5 Access-Network-Type Sub-option TBD7 Access-Network-Type Sub-option
TBD6 Network-Identifier Sub-option TBD8 Network-Name Sub-option
TBD7 Operator-Identifier Sub-option TBD9 AP-Name Sub-option
TBD10 Operator-Identifier Sub-option
TBD11 Operator-Realm Sub-option
IANA is requested to assign option codes for the following DHCPv6 IANA is requested to assign option codes for the following DHCPv6
options from the "DHCPv6 and DHCPv6 options" registry (http:// options from the "DHCPv6 and DHCPv6 options" registry (http://
www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xml). www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xml).
Option Code Descrption Option Code Descrption
--------------- ---------------------- --------------- ----------------------
TBD2 OPTION_ANI_ATT TBD2 OPTION_ANI_ATT
TBD3 OPTION_ANI_NETWORK_ID TBD3 OPTION_ANI_NETWORK_NAME
TBD4 OPTION_ANI_OPERATOR_ID TBD4 OPTION_ANI_AP_NAME
TBD5 OPTION_ANI_OPERATOR_ID
10.1. DHCPv4 Access-Network-Identifier Sub-option registry TBD6 OPTION_ANI_OPERATOR_REALM
IANA is required to maintain a new number space of "DHCPv4 Access
Network Identifier Sub-options", with the initial sub-options as
described in this document TBD5, TBD6, TBD7. IANA assigns future
DHCPv4 Access Network Identifier Sub-options with a "IETF Consensus"
policy as described in [RFC2434]. Future proposed sub-options are to
be referenced symbolically in the internet-drafts that describe them,
and shall be assigned numeric codes by IANA when and if the draft is
approved by IESG for Proposed Standard RFC status.
11. Security Considerations 11. Security Considerations
Since there is no privacy protection for DHCP messages, an Since there is no privacy protection for DHCP messages, an
eavesdropper who can monitor the link between the DHCP server, relay eavesdropper who can monitor the link between the DHCP server, relay
agent and client can discover access network information. agent and client can discover access network information.
To minimize the unintended exposure of this information, this option To minimize the unintended exposure of this information, this option
SHOULD be included by DHCP entities only when it is configured. SHOULD be included by DHCP entities only when it is configured.
Where critical decisions might be based on the value of this option, Where critical decisions might be based on the value of this option,
skipping to change at page 13, line 8 skipping to change at page 14, line 34
[RFC3315] SHOULD be used to protect the integrity of the DHCP [RFC3315] SHOULD be used to protect the integrity of the DHCP
options. Link-layer confidentiality and integrity protection may options. Link-layer confidentiality and integrity protection may
also be employed to reduce the risk of disclosure and tampering. also be employed to reduce the risk of disclosure and tampering.
Security issues related DHCPv6 are described in section 23 of Security issues related DHCPv6 are described in section 23 of
[RFC3315]. [RFC3315].
12. Acknowledgements 12. Acknowledgements
The authors would like to thank Kim Kinnear, Ted Lemon, Gaurav The authors would like to thank Kim Kinnear, Ted Lemon, Gaurav
Halwasia for their valuable inputs. Halwasia, Bernie Volz for their valuable inputs.
13. Change log 13. Change log
Changes from 00 - 01 Changes from 00 - 01
o Modified v4 top level option to be either option 82 if added by o Modified v4 top level option to be either option 82 if added by
relay or a new top level option if added by client relay or a new top level option if added by client
o Removed DHCPv6 container option o Removed DHCPv6 container option
skipping to change at page 13, line 22 skipping to change at page 15, line 4
Changes from 00 - 01 Changes from 00 - 01
o Modified v4 top level option to be either option 82 if added by o Modified v4 top level option to be either option 82 if added by
relay or a new top level option if added by client relay or a new top level option if added by client
o Removed DHCPv6 container option o Removed DHCPv6 container option
o Reorganized the options to converge v4 and v6 option descriptions o Reorganized the options to converge v4 and v6 option descriptions
Changes from 01-02 Changes from 01-02
o Modified v4 DHCP option format to align with the 1 byte code, len o Modified v4 DHCP option format to align with the 1 byte code, len
o Corrected typos o Corrected typos
Changes from 02-03 Changes from 02-03
o No change o No change
Changes from 03-04
o split network name and ap name into separate options, removed E
bit allowing different encoding
o corrected the option code, type alignment to match the boundary
o split operater id into enterprise id and realm as separate options
14. Normative References 14. Normative References
[ANI] "Interoperability Specification (IOS) for High Rate Packet [ANI] "Interoperability Specification (IOS) for High Rate Packet
Data (HRPD) Radio Access Network Interfaces with Session Data (HRPD) Radio Access Network Interfaces with Session
Control in the Access Network, A.S0008-A v3.0", Control in the Access Network, A.S0008-A v3.0",
October 2008. October 2008.
[I-D.ietf-netext-access-network-option]
Gundavelli, S., Korhonen, J., Grayson, M., Leung, K., and
R. Pazhyannur, "Access Network Identifier (ANI) Option for
Proxy Mobile IPv6",
draft-ietf-netext-access-network-option-08 (work in
progress), April 2012.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", [RFC2131] Droms, R., "Dynamic Host Configuration Protocol",
RFC 2131, March 1997. RFC 2131, March 1997.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434, IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998. October 1998.
skipping to change at page 14, line 26 skipping to change at page 16, line 8
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
[RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K., [RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K.,
and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008. and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008.
[RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy [RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy
Mobile IPv6", RFC 5844, May 2010. Mobile IPv6", RFC 5844, May 2010.
[RFC6757] Gundavelli, S., Korhonen, J., Grayson, M., Leung, K., and
R. Pazhyannur, "Access Network Identifier (ANI) Option for
Proxy Mobile IPv6", RFC 6757, October 2012.
[SMI] "PRIVATE ENTERPRISE NUMBERS, SMI Network Management [SMI] "PRIVATE ENTERPRISE NUMBERS, SMI Network Management
Private Enterprise Codes", February 2011. Private Enterprise Codes", February 2011.
[TS23003] "Numbering, addressing and identification", 2011. [TS23003] "Numbering, addressing and identification", 2011.
[TS23203] "Policy and Charging Control Architecture", 2012. [TS23203] "Policy and Charging Control Architecture", 2012.
[TS23402] "Architecture enhancements for non-3GPP accesses", 2012. [TS23402] "Architecture enhancements for non-3GPP accesses", 2012.
Authors' Addresses Authors' Addresses
 End of changes. 55 change blocks. 
143 lines changed or deleted 188 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/