idnits 2.17.1 draft-evans-dhc-dhcpv6-reconfigure-rebind-00.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 167. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 144. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 151. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 157. ** 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 'Intended status' indicated for this document; assuming Proposed Standard 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 (April 17, 2006) is 6584 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 (ref. '2') (Obsoleted by RFC 8415) Summary: 4 errors (**), 0 flaws (~~), 3 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group D. R. Evans 3 Internet-Draft ARRIS International, Inc. 4 Expires: October 19, 2006 R. Droms 5 Cisco Systems, Inc. 6 April 17, 2006 8 Rebind Capability in DHCPv6 Reconfigure Messages 9 draft-evans-dhc-dhcpv6-reconfigure-rebind-00.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 October 19, 2006. 36 Copyright Notice 38 Copyright (C) The Internet Society (2006). 40 Abstract 42 The Rebind message type in the Reconfigure Message option of a 43 Reconfigure message allows DHCPv6 servers to instruct clients to 44 perform a Rebind operation. 46 1. Introduction 48 DHCPv6 [2] allows a server to send an unsolicited Reconfigure message 49 to a client. The client's response to a Reconfigure message, 50 according to [2] is either a Renew or an Information-Request message, 51 depending on the contents of the msg-type field in the Reconfigure 52 Message option of the Reconfigure message. 54 In a network with multiple DHCPv6 servers, the Reconfigure message 55 may not be sent by the same server as the one from which the client 56 last obtained configuration and/or addressing information. If the 57 Reconfigure message commands the client to perform a Renew, [2] does 58 not specify to which server the client should send the Renew. This 59 difficulty is avoided if the server commands the client to perform an 60 Information-Request, since such messages are multicast. However, 61 Information-Request messages do not cause addressing configuration to 62 be returned. 64 This document expands the allowed values of the msg-type field to 65 allow the server to indicate that the client is to attempt to perform 66 a Rebind; since Rebind messages are multicast, this avoids the 67 necessity of the client contacting a particular server. Rebind 68 messaegs also cause all configuration information, including 69 addresses, to be returned from a server. 71 2. Terminology 73 The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, 74 SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be 75 interpreted as described in [1]. 77 3. The Reconfigure Message option of the DHCPv6 Reconfigure Message 79 A server includes a Reconfigure Message option in a Reconfigure 80 message to indicate to the client whether the client responds with a 81 Renew, an Information-request, or a Rebind message. The format of 82 this option is: 84 0 1 2 3 85 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 86 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 87 | OPTION_RECONF_MSG | option-len | 88 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 89 | msg-type | 90 +-+-+-+-+-+-+-+-+ 92 option-code OPTION_RECONF_MSG (19). 93 option-len 1. 94 msg-type 5 for Renew message, 6 for Rebind, 11 for 95 Information-request message. 97 4. Security Considerations 99 This document adds no new security considerations beyond those 100 present in [2]. 102 5. IANA Considerations 104 There are no actions for IANA associated with this document. 106 6. Normative References 108 [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement 109 Levels", BCP 14, RFC 2119, March 1997. 111 [2] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. 112 Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", 113 RFC 3315, July 2003. 115 Authors' Addresses 117 D. R. Evans 118 ARRIS International, Inc. 119 7912 Fairview Road 120 Boulder, CO 80303 121 USA 123 Phone: +1 303.494.0394 124 Email: N7DR@arrisi.com 126 Ralph Droms 127 Cisco Systems, Inc. 128 1414 Massachusetts Avenue 129 Boxborough, MA 01719 130 USA 132 Phone: +1 978.936.1674 133 Email: rdroms@cisco.com 135 Intellectual Property Statement 137 The IETF takes no position regarding the validity or scope of any 138 Intellectual Property Rights or other rights that might be claimed to 139 pertain to the implementation or use of the technology described in 140 this document or the extent to which any license under such rights 141 might or might not be available; nor does it represent that it has 142 made any independent effort to identify any such rights. Information 143 on the procedures with respect to rights in RFC documents can be 144 found in BCP 78 and BCP 79. 146 Copies of IPR disclosures made to the IETF Secretariat and any 147 assurances of licenses to be made available, or the result of an 148 attempt made to obtain a general license or permission for the use of 149 such proprietary rights by implementers or users of this 150 specification can be obtained from the IETF on-line IPR repository at 151 http://www.ietf.org/ipr. 153 The IETF invites any interested party to bring to its attention any 154 copyrights, patents or patent applications, or other proprietary 155 rights that may cover technology that may be required to implement 156 this standard. Please address the information to the IETF at 157 ietf-ipr@ietf.org. 159 Disclaimer of Validity 161 This document and the information contained herein are provided on an 162 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 163 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 164 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 165 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 166 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 167 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 169 Copyright Statement 171 Copyright (C) The Internet Society (2006). This document is subject 172 to the rights, licenses and restrictions contained in BCP 78, and 173 except as set forth therein, the authors retain all their rights. 175 Acknowledgment 177 Funding for the RFC Editor function is currently provided by the 178 Internet Society.