Browse Prior Art Database

IPv6 Prefix Length Recommendation for Forwarding (RFC7608)

IP.com Disclosure Number: IPCOM000242550D
Original Publication Date: 2015-Jul-01
Included in the Prior Art Database: 2015-Jul-24
Document File: 12 page(s) / 11K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Boucadair: AUTHOR [+3]

Abstract

Discussions on the 64-bit boundary in IPv6 addressing ([RFC7421]) revealed a need for a clear recommendation on which bits must be used by forwarding decision-making processes. However, such a recommendation was out of scope for that document.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 24% of the total text.

Internet Engineering Task Force (IETF)                      M. Boucadair Request for Comments: 7608                                France Telecom BCP: 198                                                     A. Petrescu Category: Best Current Practice                                CEA, LIST ISSN: 2070-1721                                                 F. Baker                                                            Cisco Systems                                                                July 2015

             IPv6 Prefix Length Recommendation for Forwarding

Abstract

   IPv6 prefix length, as in IPv4, is a parameter conveyed and used in    IPv6 routing and forwarding processes in accordance with the    Classless Inter-domain Routing (CIDR) architecture.  The length of an    IPv6 prefix may be any number from zero to 128, although subnets    using stateless address autoconfiguration (SLAAC) for address    allocation conventionally use a /64 prefix.  Hardware and software    implementations of routing and forwarding should therefore impose no    rules on prefix length, but implement longest-match-first on prefixes    of any valid length.

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/rfc7608.

Boucadair, et al.         Best Current Practice                 [Page 1]
 RFC 7608                                                       July 2015

 Copyright Notice

   Copyright (c) 2015 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 in Section 4.e of    the Trust Legal Provisions and are provided w...