[rfc-dist] RFC 8654 on Extended Message Support for BGP

rfc-editor@rfc-editor.org Thu, 24 October 2019 23:15 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 297D8120019 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 24 Oct 2019 16:15:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 kyGP_Gd8jR1q for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 24 Oct 2019 16:15:47 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3613A120026 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 24 Oct 2019 16:15:47 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 42C24F40713; Thu, 24 Oct 2019 16:15:41 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id C7253F40711; Thu, 24 Oct 2019 16:15:40 -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: <20191024231540.C7253F40711@rfc-editor.org>
Date: Thu, 24 Oct 2019 16:15:40 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8654_on_Extended_Message_Support_for_BG?= =?utf-8?q?P?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, idr@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8654

        Title:      Extended Message Support for BGP 
        Author:     R. Bush, 
                    K. Patel,
                    D. Ward
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2019
        Mailbox:    randy@psg.com, 
                    keyur@arrcus.com, 
                    dward@cisco.com
        Pages:      7
        Updates:    RFC 4271

        I-D Tag:    draft-ietf-idr-bgp-extended-messages-36.txt

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

        DOI:        10.17487/RFC8654

The BGP specification (RFC 4271) mandates a maximum BGP message size
of 4,096 octets.  As BGP is extended to support new Address Family
Identifiers (AFIs), Subsequent AFIs (SAFIs), and other features,
there is a need to extend the maximum message size beyond 4,096
octets.  This document updates the BGP specification by extending the
maximum message size from 4,096 octets to 65,535 octets for all
messages except for OPEN and KEEPALIVE messages.

This document is a product of the Inter-Domain Routing Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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/retrieve/bulk

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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org