[v6ops] BCP 198, RFC 7608 on IPv6 Prefix Length Recommendation for Forwarding

rfc-editor@rfc-editor.org Thu, 23 July 2015 13:41 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AC4B1ACD1C; Thu, 23 Jul 2015 06:41:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CNzfuEtDh7vd; Thu, 23 Jul 2015 06:41:13 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 84A491A21A0; Thu, 23 Jul 2015 06:41:06 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CBBAC18046F; Thu, 23 Jul 2015 06:37:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150723133708.CBBAC18046F@rfc-editor.org>
Date: Thu, 23 Jul 2015 06:37:08 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/HQihGZrS9zPekH3yLOskfMvAypk>
Cc: v6ops@ietf.org, rfc-editor@rfc-editor.org
Subject: [v6ops] BCP 198, RFC 7608 on IPv6 Prefix Length Recommendation for Forwarding
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jul 2015 13:41:20 -0000

A new Request for Comments is now available in online RFC libraries.

        BCP 198        
        RFC 7608

        Title:      IPv6 Prefix Length Recommendation for 
                    Forwarding 
        Author:     M. Boucadair, A. Petrescu,
                    F. Baker
        Status:     Best Current Practice
        Stream:     IETF
        Date:       July 2015
        Mailbox:    mohamed.boucadair@orange.com, 
                    alexandre.petrescu@cea.fr, 
                    fred@cisco.com
        Pages:      6
        Characters: 10818
        See Also:   BCP 198

        I-D Tag:    draft-ietf-v6ops-cidr-prefix-03.txt

        URL:        https://www.rfc-editor.org/info/rfc7608

        DOI:        http://dx.doi.org/10.17487/RFC7608

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.

This document is a product of the IPv6 Operations Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC