One document matched: draft-bhandari-dhc-access-network-identifier-03.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!-- One method to get references from the online citation libraries.
There has to be one entity for each item to be referenced.
An alternate method (rfc include) is described in the references. -->
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC2131 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2131.xml">
<!ENTITY RFC2132 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2132.xml">
<!ENTITY RFC3315 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3315.xml">
<!ENTITY RFC5213 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5213.xml">
<!ENTITY RFC5844 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5844.xml">
<!ENTITY RFC4649 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4649.xml">
<!ENTITY RFC3046 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3046.xml">
<!ENTITY RFC6225 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6255.xml">
<!ENTITY RFC2939 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2939.xml">
<!ENTITY RFC1035 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1035.xml">
<!ENTITY RFC2434 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2434.xml">
<!ENTITY RFC3118 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3118.xml">
<!ENTITY DHCPv6-IANA-Registry SYSTEM "http://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xml">
<!ENTITY DHCPv4-IANA-Registry SYSTEM "http://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.xml#options">
<!ENTITY I-D.draft-ietf-netext-access-network-option SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-netext-access-network-option-08.xml">
]>
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" docName="draft-bhandari-dhc-access-network-identifier-03"
ipr="trust200902">
<front>
<title abbrev="DHCPv4 & v6 ANI options">Access-Network-Identifier
Option in DHCP</title>
<author fullname="Shwetha Bhandari" initials="S." surname="Bhandari">
<organization>Cisco Systems</organization>
<address>
<postal>
<street>Cessna Business Park, Sarjapura Marathalli Outer Ring
Road</street>
<city>Bangalore</city>
<region>KARNATAKA</region>
<code>560 087</code>
<country>India</country>
</postal>
<phone>+91 80 4426 0474</phone>
<email>shwethab@cisco.com</email>
</address>
</author>
<author fullname="Sri Gundavelli" initials="S." surname="Gundavelli">
<organization>Cisco Systems</organization>
<address>
<postal>
<street>170 West Tasman Drive</street>
<city>San Jose</city>
<region>CA</region>
<code>95134</code>
<country>USA</country>
</postal>
<email>sgundave@cisco.com</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<author fullname="Jouni Korhonen " initials="J." surname="Korhonen">
<organization>Renesas Mobile</organization>
<address>
<postal>
<street>Linnoitustie 6</street>
<city>FIN-02600 Espoo</city>
<region></region>
<code></code>
<country>Finland</country>
</postal>
<phone></phone>
<email>jouni.nospam@gmail.com</email>
</address>
</author>
<author fullname="Mark Grayson" initials="M." surname="Grayson">
<organization>Cisco Systems</organization>
<address>
<postal>
<street>11 New Square Park</street>
<city>Bedfont Lakes</city>
<region>FELTHAM</region>
<code>TW14 8HA</code>
<country>ENGLAND</country>
</postal>
<email>mgrayson@cisco.com</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<date day="02" month="April" year="2013" />
<abstract>
<t>This document specifies the format and mechanism that is to be used
for encoding access network identifiers in DHCPv4 and DHCPv6 messages by
defining new access network identifier options and sub-options.</t>
</abstract>
<note title="Requirements Language">
<t>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 <xref
target="RFC2119">RFC 2119</xref>.</t>
</note>
</front>
<middle>
<section title="Introduction">
<t>Access network identification of a network device has a range of
application. The local mobility anchor in a Proxy Mobile IPv6 domain is
able to provide access network and access operator specific handling or
policing of the mobile node traffic using information about the access
network to which the mobile node is attached.</t>
<t>This document specifies Dynamic Host Configuration Protocol v4
(DHCPv4) <xref target="RFC2131"></xref> and Dynamic Host Configuration
Protocol v6 (DHCPv6) <xref target="RFC3315"></xref> options for access
network identification that is added by Client or Relay agent in the
DHCPv4 or DHCPv6 messages towards the Server.</t>
<t>Dynamic Host Configuration Protocol (DHCP) client or DHCP relay agent
aware of the access network and access operator add this information in
the DHCP messages. DHCP relay agent or DHCP server in the mobile access
gateway can pass this information towards local mobility anchor either
via Proxy Mobile IPv6 signaling or by relaying the DHCP messages to DHCP
entity within the local mobility anchor.</t>
</section>
<section title="Motivation">
<t>Proxy mobile IPv6 <xref target="RFC5213"></xref> can be used for
supporting network-based mobility management in various type of network
deployments. The network architectures, such as Service provider Wi-Fi
access aggregation or, WLAN integrated mobile packet core are examples
where Proxy Mobile IPv6 is a component of the overall architecture. Some
of these architectures require the ability of the local mobility anchor
(LMA) <xref target="RFC5213"></xref> to provide differentiated services
and policing of traffic to the mobile nodes based on the access network
to which they are attached. Policy systems in mobility architectures
such as PCC <xref target="TS23203"></xref> and ANDSF <xref
target="TS23402"></xref> in 3GPP system allow configuration of policy
rules with conditions based on the access network information. For
example, the service treatment for the 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 roaming partner. The service treatment can
also be different based on the configured Service Set Identifiers (SSID)
in case of IEEE 802.11 based access networks. Other examples of services
include the operator's ability to apply tariff based on the
location.</t>
<t>The PMIPv6 extension as specified in <xref
target="I-D.ietf-netext-access-network-option"></xref> defines PMIPv6
options to carry access network identifiers in PMIPv6 signaling from
Mobile Access Gateway (MAG) to LMA. MAG can learn this information from
DHCP options as inserted by DHCP client or Relay agent before MAG. If
MAG relays DHCP messages to LMA as specified in <xref
target="RFC5844"></xref> this information can be inserted by MAG towards
LMA in the forwarded DHCP messages.</t>
<t>Figure 1 illustrates an example Proxy Mobile IPv6 deployment where
Access Points (AP) inserts access network identifiers in DHCP messages.
The mobile access gateway learns this information over DHCP and delivers
the information elements related to the access network to the local
mobility anchor over Proxy Mobile IPv6 signaling messages. In this
example, the additional information could comprise the SSID of the used
IEEE 802.11 network and the identities of the operators running the IEEE
802.11 access network infrastructure.</t>
<t><figure title="Access Networks attached to MAG">
<preamble></preamble>
<artwork><![CDATA[ SSID: IETF-1
Operator-Id: provider1.example.com
+--+ DHCP
|AP|-------. {Access Specific Policies)
+--+ | _-----_ |
+-----+ _( )_ +-----+
| MAG |-=====( PMIPv6 )======-| LMA |-
+-----+ (_ Tunnel_) +-----+
+--+ DHCP | '-----'
|AP|-------'
+--+
SSID: IETF-2
Operator-Id: provider2.example.com
]]></artwork>
<postamble></postamble>
</figure></t>
</section>
<section title="Terminology">
<t>All the DHCP related terms used in this document to be interpreted as
defined in the Dynamic Host Configuration Protocol v4 (DHCPv4) <xref
target="RFC2131"></xref> and Dynamic Host Configuration Protocol v6
(DHCPv6) <xref target="RFC3315"></xref> specifications. DHCP refers to
both DHCPv4 and DHCPv6 messages and entities throughout this
document.</t>
<t>All the mobility related terms used in this document are to be
interpreted as defined in the Proxy Mobile IPv6 specifications <xref
target="RFC5213"></xref> and <xref target="RFC5844"></xref>.
Additionally, this document uses the following abbreviations:</t>
<t>Service Set Identifier Service Set Identifier (SSID) identifies the
name of the IEEE 802.11 network. SSID differentiates from one network to
the other.</t>
<t>Vendor ID The Vendor ID is the SMI Network Management Private
Enterprise Code of the IANA-maintained Private Enterprise Numbers
registry <xref target="SMI"></xref>.</t>
</section>
<section title="DHCPv4 Access-Network-Identifier Option">
<t>Access network identifier option carries information to identify the
access network to which the client is attached to. This information
includes access technology type, network identifier and access network
operator identifiers. <figure suppress-title="true">
<preamble>The format of the DHCPv4 Access-Network-Identifier option
is shown below.</preamble>
<artwork><![CDATA[
Code Len ANI Sub-options
+------+------+------+------+------+-- --+-----+
| code | len | s1 | s2 | s2 | ... | sn |
+------+------+------+------+------+-- --+-----+
code: 8-bit code carrying Access Network Identifier sub-options,
If added by relay agent: Relay Agent Information Option (82)
If added by client: OPTION_ACCESS_NETWORK_ID (TBD1)
len: 8 bit indicating total length of the included suboptions.
ANU Sub-options: The ANI Sub-options consists of a
sequence of SubOpt/Length/Value tuples for each sub-option, encoded
in the following manner:
SubOpt Len Sub-option Value
+------+------+------+------+------+------+--...-+------+
| code | N | s1 | s2 | s3 | s4 | | sN |
+------+------+------+------+------+------+--...-+------+
ANI Sub-options are defined in following sections.
]]></artwork>
<postamble></postamble>
</figure></t>
<section title="DHCPv4 Access-Network-Identifier Sub-options">
<t>Access network identifier information will be defined in multiple
sub-options. The initial assignment of DHCP access network identifier
Sub-options is as follows:<figure suppress-title="true">
<preamble></preamble>
<artwork><![CDATA[ Sub-option Code Sub-Option Description
--------------- ----------------------
TBD5 Access-Network-Type Sub-option
TBD6 Network-Identifier Sub-option
TBD7 Operator-Identifier Sub-option
]]></artwork>
<postamble></postamble>
</figure></t>
</section>
</section>
<section title="DHCPv6 Access-Network-Identifier options">
<t>The Access Network Identifier option defined here will be added by
DHCPv6 client in upstream DHCPv6 messages or by the Relay in
Relay-forward messages. <figure suppress-title="true">
<preamble></preamble>
<artwork><![CDATA[ Option Code Option Descrption
--------------- ----------------------
TBD2 Access-Network-Type option
TBD3 Network-Identifier option
TBD4 Operator-Identifier option
]]></artwork>
<postamble></postamble>
</figure></t>
</section>
<section title="DHCPv4 and DHCPv6 Access-Network-Identifier Options">
<t>This section defines DHCPv4 suboption and DHCPv6 options for access
network identification.</t>
<section title="Access-Network-Type option">
<t>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 single instance of this specific option in any DHCPv6
message or single instance of this specific sub-option in DHCPv4
OPTION_ACCESS_NETWORK_ID or Relay Agent information option. Its format
is as follows:</t>
<t><figure>
<artwork><![CDATA[
DHCPv4:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| suboption-code| Length | ATT |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
suboption-code: 8-bit code, it should be set to value of (TBD5),
indicating that its a Access-Network-Type sub-option
Length: 8-bit unsigned integer indicating the length of this suboption
in octets, excluding the suboption-code and length fields.
This field MUST be set to 2.
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 (TBD2) | OptLen |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ATT +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: 16-bit code OPTION_ANI_ATT (TBD2)
option-length: 16-bit unsigned integer indicating length
in octets of this option
Common format applicable to DHCPv4 and DHCPv6:
Access Technology Type (ATT)
An 16-bit field that specifies the access technology through
which the client is connected to the access link.
The values is as populated from the IANA name space
Access Technology Type Option type values as requested in [RFC5213]
0: Reserved ("Reserved")
1: Virtual ("Logical Network Interface")
2: PPP ("Point-to-Point Protocol")
3: IEEE 802.3 ("Ethernet")
4: IEEE 802.11a/b/g ("Wireless LAN")
5: IEEE 802.16e ("WIMAX")
]]></artwork>
</figure></t>
</section>
<section title="Network-Identifier option">
<t>This option 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
Identifier <xref target="TS23003"></xref> in case of 3GPP access ), to
which the client is attached. There can only be a single instance of
this specific option in any DHCPv6 message or single instance of this
specific sub-option in DHCPv4 OPTION_ACCESS_NETWORK_ID or Relay Agent
information option. The format of this option is defined below.<figure
suppress-title="true">
<preamble></preamble>
<artwork><![CDATA[
DHCPv4:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| suboption code | Length |E| Reserved | Net-Name Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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),
indicating that its a Network-Identifier sub-option
Length: 8-bit indicating Total length of this sub option,
excluding the suboption code and length fields.
The value can be in the range of 2 to 32 octets.
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 (TBD3) | OptLen |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|E| Reserved | Net-Name Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Network Name (e.g., SSID or PLMNID) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AP-Name Len | Access-Point Name ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: 16-bit code OPTION_ANI_NETWORK_ID (TBD3)
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:
'E'-bit: 1-bit flag for representing the encoding of the following
name field. MUST be set to zero (0) if the network name is
encoded using 8-bit octets or to one (1) if the network name is
encoded using UTF-8.
Reserved: 7 bits MUST be set to zero when sending and ignored when
received.
Net-Name Length: 8-bit field for representing the length of the
network name to be followed.
Network Name: The name of the access network to which the client
is attached. The type of the network-name is dependent on
the Access Technology to which the mobile node is attached. If
its 802.11 access, the network-name is 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].
When encoding the PLMN Identifier, both MNC and MCC codes 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.
AP-Name Length: 8-bit field for representing the length of the
access point name to be followed. If the access point name is not
carried, this length should be set to zero.
Access-Point Name: The name of the access point (physical device
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.
]]></artwork>
<postamble></postamble>
</figure></t>
</section>
<section title="Operator-Identifier option">
<t>The Operator-Identifier option can be used for carrying the
operator identifier of the access network to which the client is
attached.There can only be a single instance of this specific option
in any DHCPv6 message or single instance of this specific sub-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
follows:</t>
<t><figure>
<artwork><![CDATA[
DHCPv4:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| suboption code | Length | Op-ID Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Operator Identifier ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
suboption code: 8 bit code, It should be set to value of (TBD7),
indicating that it is Operator-Identifier sub-option
Length: Total length of this sub option, excluding the suboption code
and length fields.
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Op-ID Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Operator Identifier ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: 16-bit code OPTION_ANI_OPERATOR_ID (TBD4)
option-length: 16-bit unsigned integer indicating length
in octets of this option.
Common format applicable to DHCPv4 and DHCPv6:
Operator Identifier (Op-ID) Type: 8-bit unsigned integer indicating
the type of the Operator Identifier. Currently the following
types are defined:
0 - Reserved.
1 - Vendor ID as a four octet Private Enterprise Number [SMI].
2 - 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].
Operator Identifier: Up to 253 octets of the operator identifier.
The encoding of the identifier depends on the used Operator-ID
Type. Numeric values are encoded in network byte order and
strings have no terminating '\0' mark.
]]></artwork>
</figure></t>
</section>
</section>
<section title="Client Behavior">
<t>All hosts or clients MAY include access network identifier options in
all the upstream DHCP messages to inform the receiver about the access
network it is attached to.</t>
</section>
<section title="Relay Agent Behavior">
<t>DHCP Relay Agents MAY include these options before forwarding the
DHCP message to provide information about the access network over which
DHCP messages from the client is received.</t>
</section>
<section title="Server Behavior">
<t>If DHCP Server is unable to understand this option it MUST be
ignored. There is no requirement that a server return this option and
its data in a downstream DHCP message.</t>
</section>
<section anchor="IANA" title="IANA Considerations">
<t>This document defines DHCPv4 Access Network Identifier option which
requires assignment of DHCPv4 option code TBD1 assigned from "Bootp and
DHCP options" registry
(http://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.xml),
as specified in <xref target="RFC2939"></xref>.</t>
<t>IANA is requested to assign Sub-option codes for the following DHCPv4
Sub-options from the "DHCP Relay Agent Sub-Option Codes"<figure
suppress-title="true">
<preamble></preamble>
<artwork><![CDATA[ Sub-option Code Sub-Option Description
--------------- ----------------------
TBD5 Access-Network-Type Sub-option
TBD6 Network-Identifier Sub-option
TBD7 Operator-Identifier Sub-option
]]></artwork>
<postamble></postamble>
</figure></t>
<t>IANA is requested to assign option codes for the following DHCPv6
options from the "DHCPv6 and DHCPv6 options" registry
(http://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xml).</t>
<t><figure>
<preamble></preamble>
<artwork><![CDATA[ Option Code Descrption
--------------- ----------------------
TBD2 OPTION_ANI_ATT
TBD3 OPTION_ANI_NETWORK_ID
TBD4 OPTION_ANI_OPERATOR_ID
]]></artwork>
<postamble></postamble>
</figure></t>
<section title="DHCPv4 Access-Network-Identifier Sub-option registry">
<t>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 <xref target="RFC2434"></xref>. 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.</t>
</section>
</section>
<section anchor="Security" title="Security Considerations">
<t>Since there is no privacy protection for DHCP messages, an
eavesdropper who can monitor the link between the DHCP server, relay
agent and client can discover access network information.</t>
<t>To minimize the unintended exposure of this information, this option
SHOULD be included by DHCP entities only when it is configured. Where
critical decisions might be based on the value of this option, DHCP
authentication as defined in "Authentication for DHCP Messages" <xref
target="RFC3118"></xref> and "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)" <xref target="RFC3315"></xref> SHOULD be used to protect
the integrity of the DHCP options. Link-layer confidentiality and
integrity protection may also be employed to reduce the risk of
disclosure and tampering.</t>
<t>Security issues related DHCPv6 are described in section 23 of <xref
target="RFC3315"></xref>.</t>
</section>
<section anchor="Acknowledgements" title="Acknowledgements">
<t>The authors would like to thank Kim Kinnear, Ted Lemon, Gaurav
Halwasia for their valuable inputs.</t>
</section>
<section title="Change log">
<t>Changes from 00 - 01<list style="symbols">
<t>Modified v4 top level option to be either option 82 if added by
relay or a new top level option if added by client</t>
<t>Removed DHCPv6 container option</t>
<t>Reorganized the options to converge v4 and v6 option
descriptions</t>
</list></t>
<t>Changes from 01-02<list style="symbols">
<t>Modified v4 DHCP option format to align with the 1 byte code,
len</t>
<t>Corrected typos</t>
</list></t>
<t>Changes from 02-03<list style="symbols">
<t>No change</t>
</list></t>
</section>
</middle>
<!-- *****BACK MATTER ***** -->
<back>
<!-- References split into informative and normative -->
<!-- There are 2 ways to insert reference entries from the citation libraries:
1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (as shown)
2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml"?> here
(for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.xml")
Both are cited textually in the same manner: by using xref elements.
If you use the PI option, xml2rfc will, by default, try to find included files in the same
directory as the including file. You can also define the XML_LIBRARY environment variable
with a value containing a set of directories to search. These can be either in the local
filing system or remote ones accessed by http (http://domain/dir/... ).-->
<references title="Normative References">
&RFC2119;
&RFC3315;
&RFC2131;
&RFC5213;
&RFC5844;
&RFC2939;
&RFC2434;
&RFC3118;
&I-D.draft-ietf-netext-access-network-option;
<reference anchor="ANI">
<front>
<title>Interoperability Specification (IOS) for High Rate Packet
Data (HRPD) Radio Access Network Interfaces with Session Control in
the Access Network, A.S0008-A v3.0</title>
<author fullname="3GPP2" surname="">
<organization></organization>
</author>
<date month="October" year="2008" />
</front>
</reference>
<reference anchor="SMI">
<front>
<title>PRIVATE ENTERPRISE NUMBERS, SMI Network Management Private
Enterprise Codes</title>
<author fullname="IANA" surname="">
<organization></organization>
</author>
<date month="February " year="2011" />
</front>
</reference>
<reference anchor="TS23003">
<front>
<title>Numbering, addressing and identification</title>
<author fullname="3GPP" surname="">
<organization></organization>
</author>
<date month="" year="2011" />
</front>
</reference>
<reference anchor="TS23203">
<front>
<title>Policy and Charging Control Architecture</title>
<author fullname="3GPP" surname="">
<organization></organization>
</author>
<date month="" year="2012" />
</front>
</reference>
<reference anchor="TS23402">
<front>
<title>Architecture enhancements for non-3GPP accesses</title>
<author fullname="3GPP" surname="">
<organization></organization>
</author>
<date month="" year="2012" />
</front>
</reference>
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 08:53:40 |