RFC 7625 on Architecture of an IP/MPLS Network with Hardened Pipes
rfc-editor@rfc-editor.org Mon, 31 August 2015 23:35 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6137C1B68F5 for <ietf-announce@ietfa.amsl.com>; Mon, 31 Aug 2015 16:35:59 -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 dE_hiN8gN_Fp for <ietf-announce@ietfa.amsl.com>; Mon, 31 Aug 2015 16:35:56 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 4A1401B6B4F for <ietf-announce@ietf.org>; Mon, 31 Aug 2015 16:35:54 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 13301187E50; Mon, 31 Aug 2015 16:35:25 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7625 on Architecture of an IP/MPLS Network with Hardened Pipes
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150831233525.13301187E50@rfc-editor.org>
Date: Mon, 31 Aug 2015 16:35:25 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/HpP0sgMzjSEnCkvOShbwBrdpdwU>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Aug 2015 23:35:59 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7625
Title: Architecture of an IP/MPLS Network
with Hardened Pipes
Author: J. T. Hao, P. Maheshwari,
R. Huang, L. Andersson, M. Chen
Status: Informational
Stream: Independent
Date: August 2015
Mailbox: haojiangtao@huawei.com,
praveen.maheshwari@in.airtel.com,
river.huang@huawei.com,
loa@mail01.huawei.com,
mach.chen@huawei.com
Pages: 15
Characters: 30486
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-hao-mpls-ip-hard-pipe-02.txt
URL: https://www.rfc-editor.org/info/rfc7625
DOI: http://dx.doi.org/10.17487/RFC7625
This document describes an IP/MPLS network that has an infrastructure
that can be separated into two or more strata. For the
implementation described in this document, the infrastructure has
been separated into two strata: one for the "Hard Pipes", called the
"Hard Pipe Stratum", and one for the normal IP/MPLS traffic, called
the "Normal IP/MPLS Stratum".
This document introduces the concept of a Hard Pipe -- an MPLS Label
Switched Path (LSP) or a pseudowire (PW) with a bandwidth that is
guaranteed and can neither be exceeded nor infringed upon.
The Hard Pipe stratum does not use statistical multiplexing; for the
LSPs and PWs set up within this stratum, the bandwidth is guaranteed
end to end.
The document does not specify any new protocol or procedures. It
does explain how the MPLS standards implementation has been deployed
and operated to meet the requirements from operators that offer
traditional Virtual Leased Line (VLL) services.
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
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