idnits 2.17.1 draft-ietf-6man-iana-routing-header-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.i or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) 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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC2460, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC2460, updated by this document, for RFC5378 checks: 1997-07-30) -- 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 (October 12, 2009) is 5281 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 2460 (Obsoleted by RFC 8200) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Arkko 3 Internet-Draft Ericsson 4 Updates: 2460 (if approved) S. Bradner 5 Intended status: Standards Track Harvard University 6 Expires: April 15, 2010 October 12, 2009 8 IANA Allocation Guidelines for the IPv6 Routing Header 9 draft-ietf-6man-iana-routing-header-00 11 Status of this Memo 13 This Internet-Draft is submitted to IETF in full conformance with the 14 provisions of BCP 78 and BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on April 15, 2010. 34 Copyright Notice 36 Copyright (c) 2009 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents in effect on the date of 41 publication of this document (http://trustee.ietf.org/license-info). 42 Please review these documents carefully, as they describe your rights 43 and restrictions with respect to this document. 45 Abstract 47 This document specifies the IANA guidelines for allocating new values 48 for the Routing Type field in the IPv6 Routing Header. 50 1. Introduction 52 This document specifies the IANA guidelines [RFC5226] for allocating 53 new values for the Routing Type field in the IPv6 Routing Header 54 [RFC2460]. Previously, no IANA guidance existed for such 55 allocations. 57 2. IANA Considerations 59 New Routing Type values are allocated through IETF Review or IESG 60 Approval [RFC5226]. 62 Note that two experimental values (253 and 254) are already available 63 for use [RFC4727]. 65 3. Security Considerations 67 This specification does not change the security properties of the 68 Routing Header. However, past experience shows that it is easy to 69 design routing headers that have significant problems [RFC5095]. 71 4. References 73 4.1. Normative References 75 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 76 (IPv6) Specification", RFC 2460, December 1998. 78 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 79 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 80 May 2008. 82 4.2. Informative References 84 [RFC4727] Fenner, B., "Experimental Values In IPv4, IPv6, ICMPv4, 85 ICMPv6, UDP, and TCP Headers", RFC 4727, November 2006. 87 [RFC5095] Abley, J., Savola, P., and G. Neville-Neil, "Deprecation 88 of Type 0 Routing Headers in IPv6", RFC 5095, 89 December 2007. 91 Appendix A. Changes from RFC 2460 93 This document specifies only the IANA rules associated with the 94 Routing Type field. 96 Authors' Addresses 98 Jari Arkko 99 Ericsson 100 Jorvas 02420 101 Finland 103 Email: jari.arkko@piuha.net 105 Scott Bradner 106 Harvard University 107 Cambridge, MA 02138 108 US 110 Phone: +1 617 495 3864 111 Email: sob@harvard.edu