idnits 2.17.00 (12 Aug 2021) /tmp/idnits52764/draft-boucadair-rfc6153-update-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (August 21, 2013) is 3188 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 3315 (Obsoleted by RFC 8415) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Boucadair 3 Internet-Draft France Telecom 4 Updates: 6153 (if approved) August 21, 2013 5 Intended status: Standards Track 6 Expires: February 22, 2014 8 Updates to DHCPv4 and DHCPv6 Options for Access Network Discovery and 9 Selection Function (ANDSF) Discovery 10 draft-boucadair-rfc6153-update-01 12 Abstract 14 This document updates RFC 6153 by correcting IANA allocations made 15 for DHCPv4 and DHCPv6 options for Access Network Discovery and 16 Selection Function (ANDSF) Discovery. This document assigns a code 17 for DHCPv6 option for ANDSF and withdraws an already assigned DHCPv4 18 option code. 20 Requirements Language 22 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 23 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 24 document are to be interpreted as described in RFC 2119 [RFC2119]. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on February 22, 2014. 43 Copyright Notice 45 Copyright (c) 2013 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 61 2. Update to RFC 6153 . . . . . . . . . . . . . . . . . . . . . 2 62 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 63 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 64 4.1. DHCPv6 Option . . . . . . . . . . . . . . . . . . . . . . 3 65 4.2. DHCPv4 Option . . . . . . . . . . . . . . . . . . . . . . 3 66 5. Normative References . . . . . . . . . . . . . . . . . . . . 4 67 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 69 1. Introduction 71 [RFC6153] defines a DHCPv4 option (called OPTION-IPv4_Address-ANDSF) 72 [RFC2131] and a DHCPv6 option (called OPTION-IPv6_Address-ANDSF) 73 [RFC3315] to enable a mobile node to discover Access Network 74 Discovery and Selection Function (ANDSF) entities in an IP network. 75 Unfortunately, the IANA considerations section in [RFC6153] was 76 ambiguous, and as a result two DHCPv4 option codes were assigned 77 instead of one DHCPv4 option code and one DHCPv6 option code. 79 This document updates [RFC6153] by assigning a code for DHCPv6 option 80 for ANDSF and withdrawing an already assigned DHCPv4 option code. 82 2. Update to RFC 6153 84 In order to be backward compatible with existing implementations, 85 IANA MUST assign 143 as a DHCPv6 option code for OPTION-IPv6_Address- 86 ANDSF. 88 This document changes section 6 of [RFC6153] as follows: 90 OLD: 92 This document defines two new DHCP options as described in Sections 2 93 and 3: 95 ANDSF IPv4 Address Option for DHCPv4 (OPTION-IPv4_Address-ANDSF) 142 96 ANDSF IPv6 Address Option for DHCPv6 (OPTION-IPv6_Address-ANDSF) 143 98 NEW: 100 IANA has assigned the following new DHCPv6 Option Code in the 101 registry maintained in 102 http://www.iana.org/assignments/dhcpv6-parameters: 104 Option Name Value 105 ------------------------- ----- 106 OPTION-IPv6_Address-ANDSF 143 108 IANA has assigned the following new DHCPv4 Option Code in the 109 registry maintained in http://www.iana.org/assignments/bootp-dhcp- 110 parameters/: 112 Option Name Value 113 ------------------------- ----- 114 OPTION-IPv4_Address-ANDSF 142 116 3. Security Considerations 118 Security considerations are discussed in [RFC6153]. 120 4. IANA Considerations 122 4.1. DHCPv6 Option 124 IANA is requested to assign the following new DHCPv6 Option Code in 125 the registry maintained in http://www.iana.org/assignments/ 126 dhcpv6-parameters: 128 Option Name Value 129 ------------------------- ----- 130 OPTION-IPv6_Address-ANDSF 143 132 4.2. DHCPv4 Option 134 IANA is requested to return the following value to the available 135 DHCPv4 Option Codes space maintained in http://www.iana.org/ 136 assignments/bootp-dhcp-parameters/: 138 Option Name Value 139 ------------------------- ----- 140 OPTION-IPv6_Address-ANDSF 143 142 5. Normative References 144 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 145 Requirement Levels", BCP 14, RFC 2119, March 1997. 147 [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC 148 2131, March 1997. 150 [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., 151 and M. Carney, "Dynamic Host Configuration Protocol for 152 IPv6 (DHCPv6)", RFC 3315, July 2003. 154 [RFC6153] Das, S. and G. Bajko, "DHCPv4 and DHCPv6 Options for 155 Access Network Discovery and Selection Function (ANDSF) 156 Discovery", RFC 6153, February 2011. 158 Author's Address 160 Mohamed Boucadair 161 France Telecom 162 Rennes 35000 163 France 165 Email: mohamed.boucadair@orange.com