Guidelines for Creating New DHCPv6 Options (RFC7227)
Original Publication Date: 2014-May-01
Included in the Prior Art Database: 2014-May-10
Internet Society Requests For Comment (RFCs)
D. Hankins: AUTHOR [+4]
Most protocol developers ask themselves if a protocol will work, or work efficiently. These are important questions, but another less frequently considered question is whether the proposed protocol presents itself needless barriers to adoption by deployed software.
Internet Engineering Task Force (IETF) D. Hankins Request for Comments: 7227 Google BCP: 187 T. Mrugalski Updates: 3315 M. Siodelski Category: Best Current Practice ISC ISSN: 2070-1721 S. Jiang Huawei Technologies Co., Ltd. S. Krishnan Ericsson May 2014
Guidelines for Creating New DHCPv6 Options
This document provides guidance to prospective DHCPv6 option developers to help them create option formats that are easily adoptable by existing DHCPv6 software. It also provides guidelines for expert reviewers to evaluate new registrations. This document updates RFC 3315.
Status of This Memo
This memo documents an Internet Best Current Practice.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on BCPs is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7227.
Hankins, et al. Best Current Practice [Page 1]
RFC 7227 DHCPv6 Option Guidelines May 2014
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described...