idnits 2.17.1 draft-ietf-dhc-dhcpv6-reconfigure-rebind-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 152. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 163. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 170. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 176. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. 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 RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 16, 2006) is 6370 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 3315 (ref. '2') (Obsoleted by RFC 8415) Summary: 4 errors (**), 0 flaws (~~), 2 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group D. Evans 3 Internet-Draft ARRIS International, Inc. 4 Intended status: Informational R. Droms 5 Expires: May 20, 2007 Cisco Systems, Inc. 6 November 16, 2006 8 Rebind Capability in DHCPv6 Reconfigure Messages 9 draft-ietf-dhc-dhcpv6-reconfigure-rebind-01.txt 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on May 20, 2007. 36 Copyright Notice 38 Copyright (C) The Internet Society (2006). 40 Abstract 42 This document updtaes RFC 3315 to allow the Rebind message type to 43 appear in the Reconfigure Message option of a Reconfigure message, 44 which allows DHCPv6 servers to instruct clients to perform a Rebind 45 operation as well as a Renew operation. 47 1. Introduction 49 DHCPv6 [2] allows a server to send an unsolicited Reconfigure message 50 to a client. The client's response to a Reconfigure message, 51 according to [2] is either a Renew or an Information-Request message, 52 depending on the contents of the msg-type field in the Reconfigure 53 Message option of the Reconfigure message. 55 In a network with multiple DHCPv6 servers, the Reconfigure message 56 may not be sent by the same server as the one from which the client 57 last obtained configuration and/or addressing information. If the 58 Reconfigure message commands the client to perform a Renew, [2] does 59 not specify to which server the client should send the Renew. This 60 difficulty is avoided if the server commands the client to perform an 61 Information-Request, since such messages are multicast. However, 62 Information-Request messages do not cause addressing configuration to 63 be returned. 65 This document expands the allowed values of the msg-type field to 66 allow the server to indicate that the client is to attempt to perform 67 a Rebind; since Rebind messages are multicast, this avoids the 68 necessity of the client contacting a particular server. Rebind 69 messaegs also cause all configuration information, including 70 addresses, to be returned from a server. 72 This document updates section 19 of RFC 3315. 74 2. Terminology 76 The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, 77 SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be 78 interpreted as described in [1]. 80 3. The Reconfigure Message option of the DHCPv6 Reconfigure Message 82 A server includes a Reconfigure Message option in a Reconfigure 83 message to indicate to the client whether the client responds with a 84 Renew, an Information-request, or a Rebind message. 86 The format of this option is: 88 0 1 2 3 89 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 90 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 91 | OPTION_RECONF_MSG | option-len | 92 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 93 | msg-type | 94 +-+-+-+-+-+-+-+-+ 96 option-code OPTION_RECONF_MSG (19). 97 option-len 1. 98 msg-type 5 for Renew message, 6 for Rebind, 11 for 99 Information-request message. 101 4. Security Considerations 103 This document adds no new security considerations beyond those 104 present in [2]. 106 5. IANA Considerations 108 There are no actions for IANA associated with this document. 110 6. Normative References 112 [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement 113 Levels", BCP 14, RFC 2119, March 1997. 115 [2] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. 116 Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", 117 RFC 3315, July 2003. 119 Authors' Addresses 121 D. R. Evans 122 ARRIS International, Inc. 123 7912 Fairview Road 124 Boulder, CO 80303 125 USA 127 Phone: +1 303.494.0394 128 Email: N7DR@arrisi.com 129 Ralph Droms 130 Cisco Systems, Inc. 131 1414 Massachusetts Avenue 132 Boxborough, MA 01719 133 USA 135 Phone: +1 978.936.1674 136 Email: rdroms@cisco.com 138 Full Copyright Statement 140 Copyright (C) The Internet Society (2006). 142 This document is subject to the rights, licenses and restrictions 143 contained in BCP 78, and except as set forth therein, the authors 144 retain all their rights. 146 This document and the information contained herein are provided on an 147 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 148 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 149 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 150 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 151 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 152 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 154 Intellectual Property 156 The IETF takes no position regarding the validity or scope of any 157 Intellectual Property Rights or other rights that might be claimed to 158 pertain to the implementation or use of the technology described in 159 this document or the extent to which any license under such rights 160 might or might not be available; nor does it represent that it has 161 made any independent effort to identify any such rights. Information 162 on the procedures with respect to rights in RFC documents can be 163 found in BCP 78 and BCP 79. 165 Copies of IPR disclosures made to the IETF Secretariat and any 166 assurances of licenses to be made available, or the result of an 167 attempt made to obtain a general license or permission for the use of 168 such proprietary rights by implementers or users of this 169 specification can be obtained from the IETF on-line IPR repository at 170 http://www.ietf.org/ipr. 172 The IETF invites any interested party to bring to its attention any 173 copyrights, patents or patent applications, or other proprietary 174 rights that may cover technology that may be required to implement 175 this standard. Please address the information to the IETF at 176 ietf-ipr@ietf.org. 178 Acknowledgment 180 Funding for the RFC Editor function is provided by the IETF 181 Administrative Support Activity (IASA).