[rfc-dist] RFC 9252 on BGP Overlay Services Based on Segment Routing over IPv6 (SRv6)

rfc-editor@rfc-editor.org Mon, 18 July 2022 18:27 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 ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 47CD0C16ECD0; Mon, 18 Jul 2022 11:27:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1658168822; bh=2VHJA/wcFgXQ8dj3t4H3aL2LPum7W2J0Opt18l1jbO4=; h=To:From:Cc:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=CHj9nHNCcyoTbKC0luoXc4MpxAhI40R5CgNHDC1Zq83Ohr3TxA2PseXptdvZxrzkQ 4VjGaJaNyRVPXcZpIAzar4tCS9g/T8HERWvGgXo+YZ3G/rLJwYJF88s/Q3gd7gC119 80nzO75Xx0yUwYPU08CordkWypcsuZqfkzHi0Lxo=
X-Mailbox-Line: From rfc-dist-bounces@rfc-editor.org Mon Jul 18 11:27:02 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D63C9C15A729; Mon, 18 Jul 2022 11:27:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1658168821; bh=2VHJA/wcFgXQ8dj3t4H3aL2LPum7W2J0Opt18l1jbO4=; h=To:From:Cc:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=XMjFxPYvsaHi+326yd9FnIVFQ7H0AZvOC9anvt1GhfYPOzzBEfhBVGCZjBKWIuzxx I6qhPz6R8VFzG41mD9ellWsSzcSmVNEdstKZ+eaan87b3/jP0QCIopK3rX06RCFJd3 mz+8w46VGgFvoKHVAQwmom4yV9vj8X5WLBNB4tnk=
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C560BC14CF06; Mon, 18 Jul 2022 11:27:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YgYEivYPYJg6; Mon, 18 Jul 2022 11:26:57 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0AEDEC14F74B; Mon, 18 Jul 2022 11:26:56 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 3DA674C087; Mon, 18 Jul 2022 11:26:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, bess@ietf.org
Message-Id: <20220718182656.3DA674C087@rfcpa.amsl.com>
Date: Mon, 18 Jul 2022 11:26:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/tlDz9a63w6_T6CP3LoUBj4OaNR4>
Subject: [rfc-dist] RFC 9252 on BGP Overlay Services Based on Segment Routing over IPv6 (SRv6)
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
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 9252

        Title:      BGP Overlay Services Based on 
                    Segment Routing over IPv6 (SRv6) 
        Author:     G. Dawra, Ed.,
                    K. Talaulikar, Ed.,
                    R. Raszuk,
                    B. Decraene,
                    S. Zhuang,
                    J. Rabadan
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2022
        Mailbox:    gdawra.ietf@gmail.com,
                    ketant.ietf@gmail.com,
                    robert@raszuk.net,
                    bruno.decraene@orange.com,
                    zhuangshunwan@huawei.com,
                    jorge.rabadan@nokia.com
        Pages:      29
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bess-srv6-services-15.txt

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

        DOI:        10.17487/RFC9252

This document defines procedures and messages for SRv6-based BGP
services, including Layer 3 Virtual Private Network (L3VPN), Ethernet
VPN (EVPN), and Internet services. It builds on "BGP/MPLS IP Virtual
Private Networks (VPNs)" (RFC 4364) and "BGP MPLS-Based Ethernet VPN"
(RFC 7432).

This document is a product of the BGP Enabled ServiceS 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://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org