Debian Codegraph @

rfc7839.html

raw
1 <pre>Internet Engineering Task Force (IETF) S. Bhandari
2 Request for Comments: 7839 S. Gundavelli
3 Category: Standards Track M. Grayson
4 ISSN: 2070-1721 B. Volz
5 Cisco Systems
6 J. Korhonen
7 Broadcom Limited
8 June 2016
9
10
11 <span class="h1">Access-Network-Identifier Option in DHCP</span>
12
13 Abstract
14
15 This document specifies the format and mechanism that is to be used
16 for encoding Access-Network Identifiers in DHCPv4 and DHCPv6 messages
17 by defining new Access-Network-Identifier options and sub-options.
18
19 Status of This Memo
20
21 This is an Internet Standards Track document.
22
23 This document is a product of the Internet Engineering Task Force
24 (IETF). It represents the consensus of the IETF community. It has
25 received public review and has been approved for publication by the
26 Internet Engineering Steering Group (IESG). Further information on
27 Internet Standards is available in <a href="./rfc7841#section-2">Section&nbsp;2 of RFC 7841</a>.
28
29 Information about the current status of this document, any errata,
30 and how to provide feedback on it may be obtained at
31 <a href="http://www.rfc-editor.org/info/rfc7839">http://www.rfc-editor.org/info/rfc7839</a>.
32
33 Copyright Notice
34
35 Copyright (c) 2016 IETF Trust and the persons identified as the
36 document authors. All rights reserved.
37
38 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
39 Provisions Relating to IETF Documents
40 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
41 publication of this document. Please review these documents
42 carefully, as they describe your rights and restrictions with respect
43 to this document. Code Components extracted from this document must
44 include Simplified BSD License text as described in Section 4.e of
45 the Trust Legal Provisions and are provided without warranty as
46 described in the Simplified BSD License.
47
48
49
50
51
52 <span class="grey">Bhandari, et al. Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc7839">RFC 7839</a> ANI Options for DHCPv4 and DHCPv6 June 2016</span>
55
56
57 Table of Contents
58
59 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
60 <a href="#section-2">2</a>. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
61 <a href="#section-3">3</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
62 <a href="#section-4">4</a>. DHCPv4 Access-Network-Identifier Option . . . . . . . . . . . <a href="#page-5">5</a>
63 <a href="#section-4.1">4.1</a>. DHCPv4 Access-Network-Identifier Sub-options . . . . . . <a href="#page-5">5</a>
64 <a href="#section-4.2">4.2</a>. DHCPv4 Access-Technology-Type Sub-option . . . . . . . . <a href="#page-6">6</a>
65 <a href="#section-4.3">4.3</a>. DHCPv4 Network-Identifier Sub-options . . . . . . . . . . <a href="#page-7">7</a>
66 <a href="#section-4.3.1">4.3.1</a>. DHCPv4 Network-Name Sub-option . . . . . . . . . . . <a href="#page-7">7</a>
67 <a href="#section-4.3.2">4.3.2</a>. DHCPv4 Access-Point-Name Sub-option . . . . . . . . . <a href="#page-8">8</a>
68 <a href="#section-4.3.3">4.3.3</a>. DHCPv4 Access-Point-BSSID Sub-option . . . . . . . . <a href="#page-9">9</a>
69 <a href="#section-4.4">4.4</a>. DHCPv4 Operator-Identifier Sub-options . . . . . . . . . <a href="#page-9">9</a>
70 <a href="#section-4.4.1">4.4.1</a>. DHCPv4 Operator-Identifier Sub-option . . . . . . . . <a href="#page-9">9</a>
71 <a href="#section-4.4.2">4.4.2</a>. DHCPv4 Operator-Realm Sub-option . . . . . . . . . . <a href="#page-10">10</a>
72 <a href="#section-5">5</a>. DHCPv6 Access-Network-Identifier Options . . . . . . . . . . <a href="#page-10">10</a>
73 <a href="#section-5.1">5.1</a>. DHCPv6 Access-Technology-Type Option . . . . . . . . . . <a href="#page-11">11</a>
74 <a href="#section-5.2">5.2</a>. DHCPv6 Network-Identifier Options . . . . . . . . . . . . <a href="#page-11">11</a>
75 <a href="#section-5.2.1">5.2.1</a>. DHCPv6 Network-Name Option . . . . . . . . . . . . . <a href="#page-12">12</a>
76 <a href="#section-5.2.2">5.2.2</a>. DHCPv6 Access-Point-Name Option . . . . . . . . . . . <a href="#page-12">12</a>
77 <a href="#section-5.2.3">5.2.3</a>. DHCPv6 Access-Point-BSSID Option . . . . . . . . . . <a href="#page-13">13</a>
78 <a href="#section-5.3">5.3</a>. DHCPv6 Operator-Identifier Options . . . . . . . . . . . <a href="#page-13">13</a>
79 <a href="#section-5.3.1">5.3.1</a>. DHCPv6 Operator-Identifier Option . . . . . . . . . . <a href="#page-13">13</a>
80 <a href="#section-5.3.2">5.3.2</a>. DHCPv6 Operator-Realm Option . . . . . . . . . . . . <a href="#page-14">14</a>
81 <a href="#section-6">6</a>. Relay Agent Behavior . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
82 <a href="#section-7">7</a>. Server Behavior . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
83 <a href="#section-8">8</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
84 <a href="#section-9">9</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
85 <a href="#section-10">10</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
86 <a href="#section-10.1">10.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
87 <a href="#section-10.2">10.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
88 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
89 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a>
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Bhandari, et al. Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc7839">RFC 7839</a> ANI Options for DHCPv4 and DHCPv6 June 2016</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 Access-network identification of a network device has a range of
116 applications. For example, the Local Mobility Anchor (LMA) in a
117 Proxy Mobile IPv6 (PMIPv6) domain is able to provide service
118 treatment for the mobile node's traffic based on the access network
119 to which the mobile node is attached.
120
121 This document specifies the Dynamic Host Configuration Protocol for
122 IPv4 (DHCPv4) [<a href="./rfc2131" title="&quot;Dynamic Host Configuration Protocol&quot;">RFC2131</a>] and the Dynamic Host Configuration Protocol
123 for IPv6 (DHCPv6) [<a href="./rfc3315" title="&quot;Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">RFC3315</a>] options for access-network identification
124 that is added by the relay agent in the DHCPv4 or DHCPv6 messages
125 sent towards the server. The scope of applicability for this option
126 is between a DHCP relay agent and a mobile access gateway where the
127 same operator typically operates both these functions
128
129 A DHCP relay agent that is aware of the access network and access
130 operator adds this information in the DHCP messages. This
131 information can be used to provide differentiated services and
132 policing of traffic based on the access network to which a client is
133 attached. Examples of how this information can be used in mobile
134 networks can be found in [<a href="./rfc6757" title="&quot;Access Network Identifier (ANI) Option for Proxy Mobile IPv6&quot;">RFC6757</a>].
135
136 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Motivation</span>
137
138 PMIPv6 [<a href="./rfc5213" title="&quot;Proxy Mobile IPv6&quot;">RFC5213</a>] can be used for supporting network-based mobility
139 management in various types of network deployments. The network
140 architectures, such as service provider Wi-Fi access aggregation or
141 WLAN integrated mobile packet core, are examples where PMIPv6 is a
142 component of the overall architecture. Some of these architectures
143 require the ability of the LMA [<a href="./rfc5213" title="&quot;Proxy Mobile IPv6&quot;">RFC5213</a>] to provide differentiated
144 services and policing of traffic to the mobile nodes based on the
145 access network to which they are attached. Policy systems in
146 mobility architectures, such as Policy and Charging Control (PCC)
147 [<a href="#ref-TS23203" title="&quot;Policy and charging control architecture&quot;">TS23203</a>] and Access Network Discovery and Selection Function (ANDSF)
148 [<a href="#ref-TS23402" title="&quot;Architecture enhancements for non-3GPP accesses&quot;">TS23402</a>] in the 3GPP system, allow configuration of policy rules
149 with conditions based on the access-network information. For
150 example, the service treatment for the mobile node's traffic may be
151 different when they are attached to an access network owned by the
152 home operator than when owned by a roaming partner. In the case of
153 access networks based on IEEE 802.11, the service treatment can also
154 be different based on the configured Service Set Identifiers (SSIDs).
155 Other examples of services include the operator's ability to apply
156 tariff based on the location.
157
158 The PMIPv6 extension as specified in [<a href="./rfc6757" title="&quot;Access Network Identifier (ANI) Option for Proxy Mobile IPv6&quot;">RFC6757</a>] defines PMIPv6 options
159 to carry Access-Network Identifiers in PMIPv6 signaling from the
160 Mobile Access Gateway (MAG) to the LMA. The MAG can learn this
161
162
163
164 <span class="grey">Bhandari, et al. Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc7839">RFC 7839</a> ANI Options for DHCPv4 and DHCPv6 June 2016</span>
167
168
169 information from the DHCP options as inserted by the DHCP relay agent
170 in the access network. If the MAG relays the DHCP messages to the
171 LMA as specified in [<a href="./rfc5844" title="&quot;IPv4 Support for Proxy Mobile IPv6&quot;">RFC5844</a>], this information can be inserted by
172 the MAG towards the LMA in the forwarded DHCP messages.
173
174 Figure 1 illustrates an example of PMIPv6 deployment. In this
175 example, the access network is based on IEEE 802.11 technology, the
176 DHCP relay agent function is located on the Access Point (AP), and
177 the DHCP server function is located on the MAG. The MAG delivers the
178 information elements related to the access network to the LMA over
179 PMIPv6 signaling messages. The MAG obtains these information
180 elements from the DHCP relay agent as per this specification. The
181 information elements related to the access network include the SSID
182 of the used IEEE 802.11 network, the geo-location of the access
183 network to which the mobile node is attached, and the identity of the
184 operator running the IEEE 802.11 access-network infrastructure.
185
186 SSID: IETF-1
187 Operator-Identifier: provider1.example
188
189 +--+
190 |AP|-----------. {Access-Specific Policies)
191 +--+ | (DHCP Server) _-----_ |
192 (DHCP Relay) +-----+ _( )_ +-----+
193 | MAG |-=========( PMIPv6 )======-| LMA |-
194 +-----+ (_ Tunnel_) +-----+
195 +--+ | '-----'
196 |AP|-----------'
197 +--+
198 (DHCP Relay)
199
200 SSID: IETF-2
201 Operator-Identifier: provider2.example
202
203 Access Networks Attached to MAG
204
205 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Terminology</span>
206
207 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
208 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
209 document are to be interpreted as described in [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
210
211 All the DHCP-related terms used in this document are to be
212 interpreted as defined in DHCPv4 [<a href="./rfc2131" title="&quot;Dynamic Host Configuration Protocol&quot;">RFC2131</a>] and DHCPv6 [<a href="./rfc3315" title="&quot;Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">RFC3315</a>]
213 specifications. "DHCP message" refers to both DHCPv4 and DHCPv6
214 messages throughout this document.
215
216
217
218
219
220 <span class="grey">Bhandari, et al. Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc7839">RFC 7839</a> ANI Options for DHCPv4 and DHCPv6 June 2016</span>
223
224
225 All the mobility-related terms used in this document are to be
226 interpreted as defined in the PMIPv6 specifications [<a href="./rfc5213" title="&quot;Proxy Mobile IPv6&quot;">RFC5213</a>] and
227 [<a href="./rfc5844" title="&quot;IPv4 Support for Proxy Mobile IPv6&quot;">RFC5844</a>]. Additionally, this document uses the following
228 abbreviations:
229
230 Service Set Identifier (SSID)
231
232 The Service Set Identifier (SSID) identifies the name of the IEEE
233 802.11 network. The SSID differentiates from one network to the
234 other.
235
236 Operator-Identifier
237
238 The Operator-Identifier is the Structure of Management Information
239 (SMI) Network Management Private Enterprise Code of the IANA-
240 maintained "Private Enterprise Numbers" registry [<a href="#ref-SMI" title="&quot;PRIVATE ENTERPRISE NUMBERS, SMI Network Management Private Enterprise Codes&quot;">SMI</a>]. It
241 identifies the operator running the access network where the
242 client is attached.
243
244 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. DHCPv4 Access-Network-Identifier Option</span>
245
246 The Access-Network Identifier (ANI) carries information related to
247 the identity of the access network to which the client is attached.
248 This information includes access-technology type, network identifier,
249 and access network operator identifiers.
250
251 Relay agents that include ANI information include one or more sub-
252 options (see <a href="#section-4.1">Section 4.1</a>) in the Relay Agent Information option
253 [<a href="./rfc3046" title="&quot;DHCP Relay Agent Information Option&quot;">RFC3046</a>].
254
255 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. DHCPv4 Access-Network-Identifier Sub-options</span>
256
257 The Access-Network-Identifier information will be defined in multiple
258 sub-options allocated from the "DHCP Relay Agent Sub-Option Codes"
259 registry.
260
261 ANI Sub-options: The ANI sub-options consist of a sequence of Sub-
262 Option Code, Length, and Value tuples for each sub-option, encoded in
263 the following manner:
264
265 Subopt Len Sub-option Data
266 +------+------+------+------+------+------+--...-+------+
267 | code | N | s1 | s2 | s3 | s4 | | sN |
268 +------+------+------+------+------+------+--...-+------+
269
270 Subopt code
271 The 1-octet code for the sub-options defined in the following
272 sections.
273
274
275
276 <span class="grey">Bhandari, et al. Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc7839">RFC 7839</a> ANI Options for DHCPv4 and DHCPv6 June 2016</span>
279
280
281 Len
282 An unsigned 8-bit integer giving the length of the Sub-option Data
283 field in this sub-option in octets.
284
285 Sub-option Data (s1 to sN)
286 The data area for the sub-option.
287
288 The initial assignment of the DHCP Access-Network-Identifier sub-
289 options is as follows:
290
291 +=================+=======================================+
292 | SUB-OPTION CODE | SUB-OPTION DESCRIPTION |
293 +=================+=======================================+
294 | 13 | Access-Technology-Type Sub-option |
295 +=========================================================+
296 | 14 | Access-Network-Name Sub-option |
297 +=========================================================+
298 | 15 | Access-Point-Name Sub-option |
299 +=========================================================+
300 | 16 | Access-Point-BSSID Sub-option |
301 +=========================================================+
302 | 17 | Operator-Identifier Sub-option |
303 +=========================================================+
304 | 18 | Operator-Realm Sub-option |
305 +=========================================================+
306
307 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. DHCPv4 Access-Technology-Type Sub-option</span>
308
309 This sub-option is used for exchanging the type of the access
310 technology of the network to which the client is attached. Its
311 format is as follows:
312
313 0 1 2 3
314 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
315 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
316 | Subopt Code | Length | Reserved | ATT |
317 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
318
319 Subopt Code
320 13
321
322 Length
323 2
324
325 Reserved
326 An 8-bit field that is unused for now. The value MUST be
327 initialized to 0 by the sender and MUST be ignored by the
328 receiver.
329
330
331
332 <span class="grey">Bhandari, et al. Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc7839">RFC 7839</a> ANI Options for DHCPv4 and DHCPv6 June 2016</span>
335
336
337 Access-Technology-Type (ATT)
338 An 8-bit field that specifies the access technology through which
339 the client is connected to the access link from the IANA name
340 space "Access Technology Type Option type values" registry defined
341 in [<a href="./rfc5213" title="&quot;Proxy Mobile IPv6&quot;">RFC5213</a>].
342
343 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. DHCPv4 Network-Identifier Sub-options</span>
344
345 These sub-options are used for carrying the name of the access
346 network (e.g., an SSID in the case of an IEEE 802.11 access network
347 or a Public Land-based Mobile Network (PLMN) Identifier [<a href="#ref-TS23003" title="&quot;Numbering, addressing and identification&quot;">TS23003</a>] in
348 the case of a 3GPP access network) and the Access-Point Name to which
349 the client is attached. The format of these sub-options is defined
350 in the following sections. The Network-Identifier sub-options are
351 only for the currently known access-technology types.
352
353 <span class="h4"><a class="selflink" id="section-4.3.1" href="#section-4.3.1">4.3.1</a>. DHCPv4 Network-Name Sub-option</span>
354
355 0 1 2 3
356 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
357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
358 | Subopt Code | Length | |
359 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
360 . .
361 . Network-Name (e.g., SSID or PLMNID) .
362 . .
363 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
364
365 Subopt Code
366 14
367
368 Length
369 The length of the Network-Name field.
370
371 Network-Name
372 The name of the access network to which the mobile node is
373 attached. The encoding MUST be UTF-8 as described in [<a href="./rfc3629" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">RFC3629</a>].
374
375 The type of the Network-Name is dependent on the access technology
376 to which the mobile node is attached. For networks based on IEEE
377 802.11, the Network-Name will be the SSID of the network. For
378 3GPP access-based networks, it is the PLMN Identifier of the
379 access network, and for 3GPP2 access, the Network-Name is the ANI
380 [<a href="#ref-ANI" title="&quot;Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Radio Access Network Interfaces with Session Control in the Access Network&quot;">ANI</a>].
381
382
383
384
385
386
387
388 <span class="grey">Bhandari, et al. Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc7839">RFC 7839</a> ANI Options for DHCPv4 and DHCPv6 June 2016</span>
391
392
393 When encoding the PLMN Identifier, both the Mobile Network Code
394 (MNC) [<a href="#ref-TS23003" title="&quot;Numbering, addressing and identification&quot;">TS23003</a>] and Mobile Country Code (MCC) [<a href="#ref-TS23003" title="&quot;Numbering, addressing and identification&quot;">TS23003</a>] MUST be
395 three digits. If the MNC in use only has two digits, then it MUST
396 be preceded with a '0'.
397
398 <span class="h4"><a class="selflink" id="section-4.3.2" href="#section-4.3.2">4.3.2</a>. DHCPv4 Access-Point-Name Sub-option</span>
399
400 0 1 2 3
401 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
402 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
403 | Subopt Code | Length | |
404 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
405 . .
406 . Access-Point-Name .
407 . .
408 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
409
410 Subopt Code
411 15
412
413 Length
414 The length of the Access-Point-Name field.
415
416 Access-Point-Name
417 The name of the access point (physical device name) to which the
418 mobile node is attached. This is the identifier that uniquely
419 identifies the access point. While the Network-Name (e.g., SSID)
420 identifies the operator's access network, the Access-Point-Name
421 identifies a specific network device in the network to which the
422 mobile node is attached. In some deployments, the Access-Point-
423 Name can be set to the string representation of the Media Access
424 Control (MAC) address of the device as specified in [<a href="./rfc6991" title="&quot;Common YANG Data Types&quot;">RFC6991</a>] (see
425 mac-address typedef) or some unique identifier that can be used by
426 the policy systems in the operator network to unambiguously
427 identify the device. The encoding MUST be UTF-8 as described in
428 [<a href="./rfc3629" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">RFC3629</a>].
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444 <span class="grey">Bhandari, et al. Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc7839">RFC 7839</a> ANI Options for DHCPv4 and DHCPv6 June 2016</span>
447
448
449 <span class="h4"><a class="selflink" id="section-4.3.3" href="#section-4.3.3">4.3.3</a>. DHCPv4 Access-Point-BSSID Sub-option</span>
450
451 0 1 2 3
452 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
453 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
454 | Subopt Code | Length | |
455 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
456 | Access-Point-BSSID |
457 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
458
459 Subopt Code
460 16
461
462 Length
463 6
464
465 Access-Point-BSSID
466 The 48-bit Basic SSSID (BSSID) of the access point to which the
467 mobile node is attached.
468
469 <span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. DHCPv4 Operator-Identifier Sub-options</span>
470
471 The Operator-Identifier sub-options can be used for carrying the
472 Operator-Identifiers of the access network to which the client is
473 attached. The format of these sub-options is defined below.
474
475 <span class="h4"><a class="selflink" id="section-4.4.1" href="#section-4.4.1">4.4.1</a>. DHCPv4 Operator-Identifier Sub-option</span>
476
477 0 1 2 3
478 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
479 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
480 | Subopt Code | Length | .
481 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
482 . Operator-Identifier |
483 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
484
485 Subopt Code
486 17
487
488 Length
489 4
490
491 Operator-Identifier
492 The Operator-Identifier is a variable-length Private Enterprise
493 Number (PEN) [<a href="#ref-SMI" title="&quot;PRIVATE ENTERPRISE NUMBERS, SMI Network Management Private Enterprise Codes&quot;">SMI</a>] encoded in a network byte order. Please refer
494 to <a href="./rfc6757#section-3.1.3">Section&nbsp;3.1.3 of [RFC6757]</a> for additional details.
495
496
497
498
499
500 <span class="grey">Bhandari, et al. Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc7839">RFC 7839</a> ANI Options for DHCPv4 and DHCPv6 June 2016</span>
503
504
505 <span class="h4"><a class="selflink" id="section-4.4.2" href="#section-4.4.2">4.4.2</a>. DHCPv4 Operator-Realm Sub-option</span>
506
507 0 1 2 3
508 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
509 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
510 | Subopt Code | Length | |
511 |-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
512 . .
513 . Operator-Realm .
514 . .
515 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
516
517 Subopt Code
518 18
519
520 Length
521 The length of the Operator-Realm field.
522
523 Operator-Realm
524 Realm of the operator (e.g., EXAMPLE.COM). Please refer to
525 <a href="./rfc6757#section-3.1.3">Section&nbsp;3.1.3 of [RFC6757]</a> for additional details.
526
527 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. DHCPv6 Access-Network-Identifier Options</span>
528
529 The Access-Network-Identifier options defined here may be added by
530 the DHCPv6 relay agent in Relay-forward messages.
531
532 +=================+=======================================+
533 | OPTION CODE | OPTION DESCRIPTION |
534 +=================+=======================================+
535 | 105 | OPTION_ANI_ATT |
536 +=========================================================+
537 | 106 | OPTION_ANI_NETWORK_NAME |
538 +=========================================================+
539 | 107 | OPTION_ANI_AP_NAME |
540 +=========================================================+
541 | 108 | OPTION_ANI_AP_BSSID |
542 +=========================================================+
543 | 109 | OPTION_ANI_OPERATOR_ID |
544 +=========================================================+
545 | 110 | OPTION_ANI_OPERATOR_REALM |
546 +=========================================================+
547
548
549
550
551
552
553
554
555
556 <span class="grey">Bhandari, et al. Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc7839">RFC 7839</a> ANI Options for DHCPv4 and DHCPv6 June 2016</span>
559
560
561 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. DHCPv6 Access-Technology-Type Option</span>
562
563 This option is used for exchanging the type of access technology the
564 client uses to attach to the network. Its format is as follows:
565
566 0 1 2 3
567 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
568 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
569 | OPTION_ANI_ATT | Option-Len |
570 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
571 | Reserved | ATT |
572 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
573
574 Option-Code
575 OPTION_ANI_ATT (105)
576
577 Option-Len
578 2
579
580 Reserved
581 An 8-bit field that is unused for now. The value MUST be
582 initialized to 0 by the sender and MUST be ignored by the
583 receiver.
584
585 Access-Technology-Type (ATT):
586 The contents of this field are the same as the ATT field described
587 in <a href="#section-4.2">Section 4.2</a>.
588
589 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. DHCPv6 Network-Identifier Options</span>
590
591 These options can be used for carrying the name of the access network
592 (e.g., an SSID in the case of an IEEE 802.11 access network or a PLMN
593 Identifier [<a href="#ref-TS23003" title="&quot;Numbering, addressing and identification&quot;">TS23003</a>] in the case of a 3GPP access network) and an
594 Access-Point Name to which the client is attached. The format of
595 these options is defined below.
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612 <span class="grey">Bhandari, et al. Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc7839">RFC 7839</a> ANI Options for DHCPv4 and DHCPv6 June 2016</span>
615
616
617 <span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>. DHCPv6 Network-Name Option</span>
618
619 0 1 2 3
620 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
621 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
622 | OPTION_ANI_NETWORK_NAME | Option-Len |
623 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
624 . .
625 . Network-Name (e.g., SSID or PLMNID) .
626 . .
627 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
628
629 Option-Code
630 OPTION_ANI_NETWORK_NAME (106)
631
632 Option-Len
633 The length of the Network-Name field.
634
635 Network-Name
636 The contents of this field are the same as the Network-Name field
637 described in <a href="#section-4.3.1">Section 4.3.1</a>.
638
639 <span class="h4"><a class="selflink" id="section-5.2.2" href="#section-5.2.2">5.2.2</a>. DHCPv6 Access-Point-Name Option</span>
640
641 0 1 2 3
642 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
643 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
644 | OPTION_ANI_AP_NAME | Option-Len |
645 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
646 . .
647 . Access-Point-Name .
648 . .
649 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
650
651 Option-Code
652 OPTION_ANI_AP_NAME (107)
653
654 Option-Len
655 The length of the Access-Point-Name field.
656
657 Access-Point-Name
658 The contents of this field are the same as the Access-Point-Name
659 field described in <a href="#section-4.3.2">Section 4.3.2</a>.
660
661
662
663
664
665
666
667
668 <span class="grey">Bhandari, et al. Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc7839">RFC 7839</a> ANI Options for DHCPv4 and DHCPv6 June 2016</span>
671
672
673 <span class="h4"><a class="selflink" id="section-5.2.3" href="#section-5.2.3">5.2.3</a>. DHCPv6 Access-Point-BSSID Option</span>
674
675 0 1 2 3
676 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
677 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
678 | OPTION_ANI_AP_BSSID | Option-Len |
679 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
680 | Access-Point-BSSID |
681 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
682 | |
683 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
684
685 Option-Code
686 OPTION_ANI_AP_BSSID (108)
687
688 Option-Len
689 6
690
691 Access-Point-BSSID
692 The contents of this field are the same as the Access-Point-BSSID
693 field described in <a href="#section-4.3.3">Section 4.3.3</a>.
694
695 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. DHCPv6 Operator-Identifier Options</span>
696
697 The Operator-Identifier options can be used for carrying the
698 Operator-Identifier of the access network to which the client is
699 attached. The format of these options is defined below.
700
701 <span class="h4"><a class="selflink" id="section-5.3.1" href="#section-5.3.1">5.3.1</a>. DHCPv6 Operator-Identifier Option</span>
702
703 0 1 2 3
704 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
705 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
706 | OPTION_ANI_OPERATOR_ID | Option-Len |
707 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
708 | Operator-Identifier |
709 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
710
711 Option-Code
712 OPTION_ANI_OPERATOR_ID (109)
713
714 Option-Len
715 4
716
717 Operator-Identifier
718 The contents of this field are the same as the DHCPv4 Operator-
719 Identifier Sub-option field described in <a href="#section-4.4.1">Section 4.4.1</a>.
720
721
722
723
724 <span class="grey">Bhandari, et al. Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc7839">RFC 7839</a> ANI Options for DHCPv4 and DHCPv6 June 2016</span>
727
728
729 <span class="h4"><a class="selflink" id="section-5.3.2" href="#section-5.3.2">5.3.2</a>. DHCPv6 Operator-Realm Option</span>
730
731 0 1 2 3
732 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
733 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
734 | OPTION_ANI_OPERATOR_REALM | Option-Len |
735 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
736 . .
737 . Operator-Realm .
738 . .
739 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
740
741 Option-Code
742 OPTION_ANI_OPERATOR_REALM (110)
743
744 Option-Len
745 The length of the Operator-Realm field.
746
747 Operator-Realm
748 The contents of this field are the same as the Operator-Realm
749 field described in <a href="#section-4.4.2">Section 4.4.2</a>.
750
751 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Relay Agent Behavior</span>
752
753 DHCPv4 relay agents MAY include sub-options as defined in <a href="#section-4.2">Section 4.2</a>
754 through 4.4 of [<a href="./rfc3046" title="&quot;DHCP Relay Agent Information Option&quot;">RFC3046</a>] in the Relay Agent Information option for
755 providing information about the access network over which DHCP
756 messages from the client are received.
757
758 The DHCPv4 relay agent MUST include the DHCPv4 Access-Technology-Type
759 Sub-option (<a href="#section-4.2">Section 4.2</a>) when including any of these sub-options in
760 the DHCP message: DHCPv4 Network-Name Sub-option (<a href="#section-4.3.1">Section 4.3.1</a>),
761 DHCPv4 Access-Point-Name Sub-option (<a href="#section-4.3.2">Section 4.3.2</a>), and DHCPv4
762 Access-Point-BSSID Sub-option (<a href="#section-4.3.3">Section 4.3.3</a>).
763
764 DHCPv6 Relay Agents MAY include options (defined in <a href="#section-5">Section 5</a>) in the
765 Relay-forward message when forwarding any DHCPv6 message type from
766 clients to the servers to provide information about the access
767 network over which DHCPv6 messages from the client are received.
768
769 The DHCPv6 relay agent MUST include the DHCPv6 Access-Technology-Type
770 Option (<a href="#section-5.1">Section 5.1</a>) when including any of these options in the DHCP
771 message: DHCPv6 Network-Name Option (<a href="#section-5.2.1">Section 5.2.1</a>), DHCPv6 Access-
772 Point-Name Option (<a href="#section-5.2.2">Section 5.2.2</a>), and DHCPv6 Access-Point-BSSID
773 Option (<a href="#section-5.2.3">Section 5.2.3</a>).
774
775
776
777
778
779
780 <span class="grey">Bhandari, et al. Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc7839">RFC 7839</a> ANI Options for DHCPv4 and DHCPv6 June 2016</span>
783
784
785 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Server Behavior</span>
786
787 The DHCPv4 base specification [<a href="./rfc2131" title="&quot;Dynamic Host Configuration Protocol&quot;">RFC2131</a>] requires that the DHCPv4
788 server ignore the DHCPv4 Access-Network-Identifier Option if it does
789 not understand the option.
790
791 If the DHCPv4 server does not understand the received sub-option
792 defined in Sections <a href="#section-4.1">4.1</a> through <a href="#section-4.4">4.4</a> of [<a href="./rfc3046" title="&quot;DHCP Relay Agent Information Option&quot;">RFC3046</a>], the DHCPv4 Relay-
793 Agent-Information Option, it MUST ignore those sub-options only. If
794 the DHCPv4 server is able to process the DHCPv4 Access-Network-
795 Identifier sub-options defined in Sections <a href="#section-4.1">4.1</a> through <a href="#section-4.4">4.4</a> of
796 [<a href="./rfc3046" title="&quot;DHCP Relay Agent Information Option&quot;">RFC3046</a>], the DHCPv4 Relay-Agent-Information Option, it MAY use this
797 information obtained from the sub-option for address pool selection
798 or for policy decisions as per its configured policy. This
799 information obtained from the sub-option SHOULD NOT be stored unless
800 it is absolutely needed. However, if it is stored, the information
801 MUST be deleted as quickly as possible to eliminate any possibility
802 of the information getting exposed to an intruder.
803
804 The DHCPv4 server MUST ignore the received DHCPv4 Access-Network-
805 Identifier Option and process the rest of the message as per the base
806 DHCPv4 specifications if the received DHCPv4 message does not include
807 the DHCPv4 Access-Technology-Type Sub-option (<a href="#section-4.2">Section 4.2</a>) but does
808 include any one of these other options: DHCPv4 Network Name Sub-
809 option (<a href="#section-4.3.1">Section 4.3.1</a>), DHCPv4 Access-Point-Name Sub-option
810 (<a href="#section-4.3.2">Section 4.3.2</a>), or DHCPv4 Access-Point-BSSID Sub-option
811 (<a href="#section-4.3.3">Section 4.3.3</a>).
812
813 DHCPv6 base specification [<a href="./rfc3315" title="&quot;Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">RFC3315</a>] requires that the DHCPv6 server
814 ignore the DHCPv6 Access-Network-Identifier Option if it does not
815 understand the option.
816
817 If the DHCPv6 server receives the options defined in <a href="#section-5">Section 5</a> and is
818 configured to use the options defined in <a href="#section-5">Section 5</a>, it SHOULD look
819 for the DHCPv6 Access-Network-Identifier options in the Relay-forward
820 message of the DHCPv6 relay agent(s) based on its configured policy.
821 The server MAY use received ANI options for its address pool
822 selection policy decisions as per its configured policy. This
823 information obtained from the options SHOULD NOT be stored unless it
824 is absolutely needed. However, if it is stored, the information MUST
825 be deleted as quickly as possible to eliminate any possibility of the
826 information getting exposed to an intruder.
827
828 The DHCPv6 server MUST ignore the received DHCPv6 Access-Network-
829 Identifier Option and process the rest of the message as per the base
830 DHCPv6 specifications if the received DHCPv6 message does not include
831 the DHCPv6 Access-Technology-Type Option (<a href="#section-5.1">Section 5.1</a>) but it does
832 includes any one of these other options: DHCPv6 Network-Name Option
833
834
835
836 <span class="grey">Bhandari, et al. Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc7839">RFC 7839</a> ANI Options for DHCPv4 and DHCPv6 June 2016</span>
839
840
841 (<a href="#section-5.2.1">Section 5.2.1</a>), DHCPv6 Access-Point-Name Option (<a href="#section-5.2.2">Section 5.2.2</a>), or
842 DHCPv6 Access-Point-BSSID Option (<a href="#section-5.2.3">Section 5.2.3</a>).
843
844 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
845
846 IANA has assigned sub-option codes for the following DHCPv4 sub-
847 options from the "DHCP Relay Agent Sub-Option Codes" registry,
848 &lt;<a href="http://www.iana.org/assignments/bootp-dhcp-parameters">http://www.iana.org/assignments/bootp-dhcp-parameters</a>&gt;:
849
850 +=================+=======================================+
851 | SUB-OPTION CODE | SUB-OPTION DESCRIPTION |
852 +=================+=======================================+
853 | 13 | Access-Technology-Type Sub-option |
854 +=========================================================+
855 | 14 | Access-Network-Name Sub-option |
856 +=========================================================+
857 | 15 | Access-Point-Name Sub-option |
858 +=========================================================+
859 | 16 | Access-Point-BSSID Sub-option |
860 +=========================================================+
861 | 17 | Operator-Identifier Sub-option |
862 +=========================================================+
863 | 18 | Operator-Realm Sub-option |
864 +=========================================================+
865
866 IANA has assigned option codes for the following DHCPv6 options from
867 the "Option Codes" registry for DHCPv6,
868 &lt;<a href="http://www.iana.org/assignments/dhcpv6-parameters">http://www.iana.org/assignments/dhcpv6-parameters</a>&gt;, as specified in
869 [<a href="./rfc3315" title="&quot;Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">RFC3315</a>]:
870
871 +=================+=======================================+
872 | OPTION CODE | OPTION DESCRIPTION |
873 +=================+=======================================+
874 | 105 | OPTION_ANI_ATT |
875 +=========================================================+
876 | 106 | OPTION_ANI_NETWORK_NAME |
877 +=========================================================+
878 | 107 | OPTION_ANI_AP_NAME |
879 +=========================================================+
880 | 108 | OPTION_ANI_AP_BSSID |
881 +=========================================================+
882 | 109 | OPTION_ANI_OPERATOR_ID |
883 +=========================================================+
884 | 110 | OPTION_ANI_OPERATOR_REALM |
885 +=========================================================+
886
887
888
889
890
891
892 <span class="grey">Bhandari, et al. Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc7839">RFC 7839</a> ANI Options for DHCPv4 and DHCPv6 June 2016</span>
895
896
897 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Security Considerations</span>
898
899 Since there is no privacy protection for DHCP messages, an
900 eavesdropper who can monitor the link between the DHCP server and
901 relay agent can discover access-network information.
902
903 [<a id="ref-RFC3118">RFC3118</a>] and [<a href="./rfc3315" title="&quot;Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">RFC3315</a>] describe many of the threats in using DHCP.
904 [<a href="./rfc3118" title="&quot;Authentication for DHCP Messages&quot;">RFC3118</a>] and [<a href="./rfc3315" title="&quot;Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">RFC3315</a>] each provide a solution; the Authentication
905 Option for DHCPv4 and DHCPv6 (respectively). However, neither of
906 these options are in active use and therefore are not a viable
907 mitigation option. DHCP itself is inherently insecure and thus link-
908 layer confidentiality and integrity protection SHOULD be employed to
909 reduce the risk of disclosure and tampering.
910
911 It is possible for a rogue DHCP relay agent to insert or overwrite
912 with incorrect Access-Network-Identifier options for malicious
913 purposes. A DHCP client can also pose as a rogue DHCP relay agent by
914 sending incorrect Access-Network-Identifier options. While the
915 introduction of fraudulent DHCP relay agent information options can
916 be prevented by a perimeter defense that blocks these options unless
917 the DHCP relay agent is trusted, a deeper defense using the
918 authentication sub-option for the DHCPv4 Relay-Agent-Information
919 Option [<a href="./rfc4030" title="&quot;The Authentication Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option&quot;">RFC4030</a>] SHOULD be deployed as well. Administrators SHOULD
920 configure DHCP servers that use this option to communicate with their
921 relay agents using IPsec, as described in <a href="./rfc3315#section-21.1">Section&nbsp;21.1 of [RFC3315]</a>.
922
923 The information elements that this document is exposing are the
924 client's access-network information. These pertain to the access
925 network to which the client is attached, such as Access-Technology
926 Type (e.g., WLAN, Ethernet, etc.), Access-Point Identity (Name,
927 BSSID), and Operator-Identifier and Operator-Realm. In deployments
928 where this information cannot be secured using IPsec [<a href="./rfc4301" title="&quot;Security Architecture for the Internet Protocol&quot;">RFC4301</a>] or
929 other security protocols, administrators SHOULD disable the
930 capability specified in this document on the DHCP entities.
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948 <span class="grey">Bhandari, et al. Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc7839">RFC 7839</a> ANI Options for DHCPv4 and DHCPv6 June 2016</span>
951
952
953 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span>
954
955 <span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative References</span>
956
957 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
958 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
959 DOI 10.17487/RFC2119, March 1997,
960 &lt;<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>&gt;.
961
962 [<a id="ref-RFC2131">RFC2131</a>] Droms, R., "Dynamic Host Configuration Protocol",
963 <a href="./rfc2131">RFC 2131</a>, DOI 10.17487/RFC2131, March 1997,
964 &lt;<a href="http://www.rfc-editor.org/info/rfc2131">http://www.rfc-editor.org/info/rfc2131</a>&gt;.
965
966 [<a id="ref-RFC3046">RFC3046</a>] Patrick, M., "DHCP Relay Agent Information Option",
967 <a href="./rfc3046">RFC 3046</a>, DOI 10.17487/RFC3046, January 2001,
968 &lt;<a href="http://www.rfc-editor.org/info/rfc3046">http://www.rfc-editor.org/info/rfc3046</a>&gt;.
969
970 [<a id="ref-RFC3315">RFC3315</a>] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins,
971 C., and M. Carney, "Dynamic Host Configuration Protocol
972 for IPv6 (DHCPv6)", <a href="./rfc3315">RFC 3315</a>, DOI 10.17487/RFC3315, July
973 2003, &lt;<a href="http://www.rfc-editor.org/info/rfc3315">http://www.rfc-editor.org/info/rfc3315</a>&gt;.
974
975 <span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span>
976
977 [<a id="ref-ANI">ANI</a>] "Interoperability Specification (IOS) for High Rate Packet
978 Data (HRPD) Radio Access Network Interfaces with Session
979 Control in the Access Network", 3GPP2 A.S0008-C v4.0,
980 April 2011.
981
982 [<a id="ref-RFC3118">RFC3118</a>] Droms, R., Ed. and W. Arbaugh, Ed., "Authentication for
983 DHCP Messages", <a href="./rfc3118">RFC 3118</a>, DOI 10.17487/RFC3118, June 2001,
984 &lt;<a href="http://www.rfc-editor.org/info/rfc3118">http://www.rfc-editor.org/info/rfc3118</a>&gt;.
985
986 [<a id="ref-RFC3629">RFC3629</a>] Yergeau, F., "UTF-8, a transformation format of ISO
987 10646", STD 63, <a href="./rfc3629">RFC 3629</a>, DOI 10.17487/RFC3629, November
988 2003, &lt;<a href="http://www.rfc-editor.org/info/rfc3629">http://www.rfc-editor.org/info/rfc3629</a>&gt;.
989
990 [<a id="ref-RFC4030">RFC4030</a>] Stapp, M. and T. Lemon, "The Authentication Suboption for
991 the Dynamic Host Configuration Protocol (DHCP) Relay Agent
992 Option", <a href="./rfc4030">RFC 4030</a>, DOI 10.17487/RFC4030, March 2005,
993 &lt;<a href="http://www.rfc-editor.org/info/rfc4030">http://www.rfc-editor.org/info/rfc4030</a>&gt;.
994
995 [<a id="ref-RFC4301">RFC4301</a>] Kent, S. and K. Seo, "Security Architecture for the
996 Internet Protocol", <a href="./rfc4301">RFC 4301</a>, DOI 10.17487/RFC4301,
997 December 2005, &lt;<a href="http://www.rfc-editor.org/info/rfc4301">http://www.rfc-editor.org/info/rfc4301</a>&gt;.
998
999
1000
1001
1002
1003
1004 <span class="grey">Bhandari, et al. Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc7839">RFC 7839</a> ANI Options for DHCPv4 and DHCPv6 June 2016</span>
1007
1008
1009 [<a id="ref-RFC5213">RFC5213</a>] Gundavelli, S., Ed., Leung, K., Devarapalli, V.,
1010 Chowdhury, K., and B. Patil, "Proxy Mobile IPv6",
1011 <a href="./rfc5213">RFC 5213</a>, DOI 10.17487/RFC5213, August 2008,
1012 &lt;<a href="http://www.rfc-editor.org/info/rfc5213">http://www.rfc-editor.org/info/rfc5213</a>&gt;.
1013
1014 [<a id="ref-RFC5844">RFC5844</a>] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy
1015 Mobile IPv6", <a href="./rfc5844">RFC 5844</a>, DOI 10.17487/RFC5844, May 2010,
1016 &lt;<a href="http://www.rfc-editor.org/info/rfc5844">http://www.rfc-editor.org/info/rfc5844</a>&gt;.
1017
1018 [<a id="ref-RFC6757">RFC6757</a>] Gundavelli, S., Ed., Korhonen, J., Ed., Grayson, M.,
1019 Leung, K., and R. Pazhyannur, "Access Network Identifier
1020 (ANI) Option for Proxy Mobile IPv6", <a href="./rfc6757">RFC 6757</a>,
1021 DOI 10.17487/RFC6757, October 2012,
1022 &lt;<a href="http://www.rfc-editor.org/info/rfc6757">http://www.rfc-editor.org/info/rfc6757</a>&gt;.
1023
1024 [<a id="ref-RFC6991">RFC6991</a>] Schoenwaelder, J., Ed., "Common YANG Data Types",
1025 <a href="./rfc6991">RFC 6991</a>, DOI 10.17487/RFC6991, July 2013,
1026 &lt;<a href="http://www.rfc-editor.org/info/rfc6991">http://www.rfc-editor.org/info/rfc6991</a>&gt;.
1027
1028 [<a id="ref-SMI">SMI</a>] IANA, "PRIVATE ENTERPRISE NUMBERS, SMI Network Management
1029 Private Enterprise Codes", March 2016,
1030 &lt;<a href="https://www.iana.org/assignments/enterprise-numbers">https://www.iana.org/assignments/enterprise-numbers</a>&gt;.
1031
1032 [<a id="ref-TS23003">TS23003</a>] 3GPP, "Numbering, addressing and identification", 3GPP
1033 TS 23.003 13.4.0, December 2015.
1034
1035 [<a id="ref-TS23203">TS23203</a>] 3GPP, "Policy and charging control architecture", 3GPP
1036 TS 23.203 13.6.0, December 2015.
1037
1038 [<a id="ref-TS23402">TS23402</a>] 3GPP, "Architecture enhancements for non-3GPP accesses",
1039 3GPP TS 23.402 13.4.0, December 2015.
1040
1041 Acknowledgements
1042
1043 The authors would like to thank Kim Kinnear, Ted Lemon, Gaurav
1044 Halwasia, Hidetoshi Yokota, Sheng Jiang, and Francis Dupont for their
1045 valuable input. Also, thank you to Tomek Mrugalski for a thorough
1046 review of the document.
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060 <span class="grey">Bhandari, et al. Standards Track [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc7839">RFC 7839</a> ANI Options for DHCPv4 and DHCPv6 June 2016</span>
1063
1064
1065 Authors' Addresses
1066
1067 Shwetha Bhandari
1068 Cisco Systems
1069 Cessna Business Park, Sarjapura Marathalli Outer Ring Road
1070 Bangalore, KARNATAKA 560 087
1071 India
1072
1073 Phone: +91 80 4426 0474
1074 Email: [email protected]
1075
1076
1077 Sri Gundavelli
1078 Cisco Systems
1079 170 West Tasman Drive
1080 San Jose, CA 95134
1081 United States
1082
1083 Email: [email protected]
1084
1085
1086 Mark Grayson
1087 Cisco Systems
1088 11 New Square Park
1089 Bedfont Lakes, FELTHAM TW14 8HA
1090 England
1091
1092 Email: [email protected]
1093
1094
1095 Bernie Volz
1096 Cisco Systems
1097 1414 Massachusetts Ave
1098 Boxborough, MA 01719
1099 United States
1100
1101 Email: [email protected]
1102
1103
1104 Jouni Korhonen
1105 Broadcom Limited
1106 3151 Zanker Rd
1107 San Jose, CA 95134
1108 United States
1109
1110 Email: [email protected]
1111
1112
1113
1114
1115
1116 Bhandari, et al. Standards Track [Page 20]
1117 </pre>