IANA Allocation Guidelines for the IPv6 Routing Header
draft-ietf-6man-iana-routing-header-00

Status of this Memo

This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress.”

The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.

The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.

This Internet-Draft will expire on April 16, 2010.

Copyright Notice

Copyright (c) 2009 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 in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.

Abstract

This document specifies the IANA guidelines for allocating new values for the Routing Type field in the IPv6 Routing Header.

1.  Introduction

This document specifies the IANA guidelines [RFC5226] (Narten, T. and H. Alvestrand, “Guidelines for Writing an IANA Considerations Section in RFCs,” May 2008.) for allocating new values for the Routing Type field in the IPv6 Routing Header [RFC2460] (Deering, S. and R. Hinden, “Internet Protocol, Version 6 (IPv6) Specification,” December 1998.). Previously, no IANA guidance existed for such allocations.

2.  IANA Considerations

New Routing Type values are allocated through IETF Review or IESG Approval [RFC5226] (Narten, T. and H. Alvestrand, “Guidelines for Writing an IANA Considerations Section in RFCs,” May 2008.).

Note that two experimental values (253 and 254) are already available for use [RFC4727] (Fenner, B., “Experimental Values In IPv4, IPv6, ICMPv4, ICMPv6, UDP, and TCP Headers,” November 2006.).

3.  Security Considerations

This specification does not change the security properties of the Routing Header. However, past experience shows that it is easy to design routing headers that have significant problems [RFC5095] (Abley, J., Savola, P., and G. Neville-Neil, “Deprecation of Type 0 Routing Headers in IPv6,” December 2007.).

4.  References

4.1. Normative References

4.2. Informative References

Appendix A.  Changes from RFC 2460

This document specifies only the IANA rules associated with the Routing Type field.

Authors' Addresses