[mpls] RFC 8277 on Using BGP to Bind MPLS Labels to Address Prefixes
rfc-editor@rfc-editor.org Fri, 20 October 2017 05:17 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0288E12ECEC; Thu, 19 Oct 2017 22:17:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham 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 cuRGvemcUvXK; Thu, 19 Oct 2017 22:17:53 -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 B357B133075; Thu, 19 Oct 2017 22:17:53 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E5A85B801FD; Thu, 19 Oct 2017 22:17:29 -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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, mpls@ietf.org
Message-Id: <20171020051729.E5A85B801FD@rfc-editor.org>
Date: Thu, 19 Oct 2017 22:17:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/FP7lS87ZHJnKGB8DfRlXTJF84Uo>
Subject: [mpls] RFC 8277 on Using BGP to Bind MPLS Labels to Address Prefixes
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Oct 2017 05:17:55 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8277
Title: Using BGP to Bind MPLS
Labels to Address Prefixes
Author: E. Rosen
Status: Standards Track
Stream: IETF
Date: October 2017
Mailbox: erosen@juniper.net
Pages: 23
Characters: 56512
Obsoletes: RFC 3107
I-D Tag: draft-ietf-mpls-rfc3107bis-04.txt
URL: https://www.rfc-editor.org/info/rfc8277
DOI: 10.17487/RFC8277
This document specifies a set of procedures for using BGP to advertise
that a specified router has bound a specified MPLS label (or a
specified sequence of MPLS labels organized as a contiguous part of a
label stack) to a specified address prefix. This can be done by
sending a BGP UPDATE message whose Network Layer Reachability
Information field contains both the prefix and the MPLS label(s) and
whose Next Hop field identifies the node at which said prefix is bound
to said label(s). This document obsoletes RFC 3107.
This document is a product of the Multiprotocol Label Switching 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