[mpls] RFC 7167 on A Framework for Point-to-Multipoint MPLS in Transport Networks

rfc-editor@rfc-editor.org Mon, 14 April 2014 18:05 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0521F1A06AC; Mon, 14 Apr 2014 11:05:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level:
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 jTn_ILuRWRIz; Mon, 14 Apr 2014 11:05:43 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id CC9EE1A06C2; Mon, 14 Apr 2014 11:05:42 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C446A1801B0; Mon, 14 Apr 2014 11:05:20 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140414180520.C446A1801B0@rfc-editor.org>
Date: Mon, 14 Apr 2014 11:05:20 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/mpls/i0tPsjvHKoa5iY5QCmPXb5uQB-s
Cc: drafts-update-ref@iana.org, mpls@ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] RFC 7167 on A Framework for Point-to-Multipoint MPLS in Transport Networks
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 14 Apr 2014 18:05:51 -0000

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

        
        RFC 7167

        Title:      A Framework for Point-to-Multipoint MPLS 
                    in Transport Networks 
        Author:     D. Frost, S. Bryant,
                    M. Bocci, L. Berger
        Status:     Informational
        Stream:     IETF
        Date:       April 2014
        Mailbox:    frost@mm.st, 
                    stbryant@cisco.com, 
                    matthew.bocci@alcatel-lucent.com,
                    lberger@labn.net
        Pages:      12
        Characters: 23842
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-tp-p2mp-framework-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7167.txt

The Multiprotocol Label Switching Transport Profile (MPLS-TP) is the
common set of MPLS protocol functions defined to enable the
construction and operation of packet transport networks.  The MPLS-TP
supports both point-to-point and point-to-multipoint transport paths.
This document defines the elements and functions of the MPLS-TP
architecture that are applicable specifically to supporting
point-to-multipoint transport paths.

This document is a product of the Multiprotocol Label Switching Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

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

For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://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