Re: [mpls] New Version Notification for draft-liu-mpls-tp-interconnected-ring-protection-04.txt

liu.guoman@zte.com.cn Tue, 23 April 2013 02:44 UTC

Return-Path: <liu.guoman@zte.com.cn>
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 4730421E80CB for <mpls@ietfa.amsl.com>; Mon, 22 Apr 2013 19:44:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.663
X-Spam-Level:
X-Spam-Status: No, score=-99.663 tagged_above=-999 required=5 tests=[AWL=-1.268, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ggx474+aTGGO for <mpls@ietfa.amsl.com>; Mon, 22 Apr 2013 19:44:21 -0700 (PDT)
Received: from zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id C8F8321E80B0 for <mpls@ietf.org>; Mon, 22 Apr 2013 19:44:20 -0700 (PDT)
Received: from zte.com.cn (unknown [192.168.168.120]) by Websense Email Security Gateway with ESMTP id 1B8421275F69 for <mpls@ietf.org>; Tue, 23 Apr 2013 10:43:57 +0800 (CST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id 545C3CBD68F for <mpls@ietf.org>; Tue, 23 Apr 2013 10:43:55 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id r3N2hpZV055915 for <mpls@ietf.org>; Tue, 23 Apr 2013 10:43:51 +0800 (GMT-8) (envelope-from liu.guoman@zte.com.cn)
To: "mpls@ietf.org" <mpls@ietf.org>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF1BEEE1B1.D35D491C-ON48257B56.0003F0AA-48257B56.000F49B7@zte.com.cn>
From: liu.guoman@zte.com.cn
Date: Tue, 23 Apr 2013 10:43:49 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2013-04-23 10:43:49, Serialize complete at 2013-04-23 10:43:49
Content-Type: multipart/alternative; boundary="=_alternative 000F49B648257B56_="
X-MAIL: mse01.zte.com.cn r3N2hpZV055915
Subject: Re: [mpls] New Version Notification for draft-liu-mpls-tp-interconnected-ring-protection-04.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 23 Apr 2013 02:44:22 -0000

All,hi
I have upload a new version 04 of 
draft-liu-mpls-tp-interconnected-ring-protection. 
in this version, adding context of recovery mechanism for interconnection 
node failure
in the scenario of chained interconnection in section 3.2 and correct a 
few error word
in this document.
welcome more comments and suggestions for this draft, thank you!

best regards
liu



internet-drafts@ietf.org 
2013-04-22 22:37

收件人
Masahiro Daikoku <ms-daikoku@kddi.com>, Takeshi Maruyama 
<ta-maruyama@kddi.com>, Guoman Liu <fu.zhentao@zte.com.cn>, Guoman Liu 
<liu.guoman@zte.com.cn>
抄送

主题
New Version Notification for 
draft-liu-mpls-tp-interconnected-ring-protection-04.txt







A new version of I-D, 
draft-liu-mpls-tp-interconnected-ring-protection-04.txt
has been successfully submitted by Guoman Liu and posted to the
IETF repository.

Filename:                 draft-liu-mpls-tp-interconnected-ring-protection
Revision:                 04
Title:                            MPLS-TP protection for interconnected 
rings
Creation date:            2013-04-19
Group:                            Individual Submission
Number of pages: 12
URL:             
http://www.ietf.org/internet-drafts/draft-liu-mpls-tp-interconnected-ring-protection-04.txt

Status:          
http://datatracker.ietf.org/doc/draft-liu-mpls-tp-interconnected-ring-protection

Htmlized:        
http://tools.ietf.org/html/draft-liu-mpls-tp-interconnected-ring-protection-04

Diff:            
http://www.ietf.org/rfcdiff?url2=draft-liu-mpls-tp-interconnected-ring-protection-04


Abstract:
   The requirements for MPLS Transport Profile include a requirement
   (R93) that requires MPLS-TP must support recovery mechanisms for a
   network constructed from interconnected rings that protect user data
   that traverses more than one ring.  In particular, This includes
   protecting against cases of failure at the ring-interconnect nodes
   and links.  This document presents different scenario of
   interconnected rings and special mechanism to address recovery of the
   failure of ring-interconnect nodes and links.  .

   This document is a product of a joint Internet Engineering Task
   Force(IETF) / International Telecommunications Union
   Telecommunications Standardization Sector (ITU-T) effort to include
   an MPLS Transport Profile within the IETF MPLS and PWE3 architectures
   to support the capabilities and functionalities of a packet transport
   network as defined by the ITU-T.

  


The IETF Secretariat


--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s).  If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited.  If you have received this mail in error, please delete it and notify us immediately.
--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s).  If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited.  If you have received this mail in error, please delete it and notify us immediately.