Re: [mpls] Last Call: draft-ietf-mpls-tp-survive-fwk (Multiprotocol Label Switching Transport Profile Survivability Framework) to Informational RFC

hi,all
I review this draft, I maybe have a few confusions  about the draft. maybe 
there is a little error editors in  this draft.
1 in section 1.3, there is a a describles for associated bidirection LSP 
recovery
 " This may also be the case for associated
   bidirectional LSPs where the two directions of the LSP follow
   different paths through the network.  This causes direct interaction
   between the recovery processes affecting the two directions of an
   LSP, so that both directions of the LSP are recovered at the same
   time (i.e., bidirectional recovery is a consequence of fate-sharing)."
IMO, this mean it should need to have fate-sharing for associated 
bidirection lsp?
if one direction working path have failure, another direction working path 
must
switch into protection path?

2 in section 2 Terminology and Reference
  there are two the same definitions for Restoration 
  maybe delete one definitions for Restortion;

3 there are MPLS-TP Section level and Link layer concept. I want to 
  know what difference between MPLS-TP Section Level and MPLS-TP Link 
layer?

4 Section 4.7.3 P2MP Linear Protection
  As there is a requirement of P2MP support 1:n protection in RFC 5654,
  so I suggest to add 1:n protection solution in this section or further
  study for 1:n protection of p2mp ;

best regards
liu

The IESG <iesg-secretary@ietf.org> 
发件人:  mpls-bounces@ietf.org
2010-04-23 03:03
请答复 给
ietf@ietf.org

收件人
IETF-Announce <ietf-announce@ietf.org>
抄送
mpls@ietf.org
主题
[mpls] Last Call: draft-ietf-mpls-tp-survive-fwk (Multiprotocol Label 
Switching Transport Profile Survivability Framework) to Informational RFC

The IESG has received a request from the Multiprotocol Label Switching WG 
(mpls) to consider the following document:

- 'Multiprotocol Label Switching Transport Profile Survivability 
   Framework '
   <draft-ietf-mpls-tp-survive-fwk-05.txt> as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2010-05-06. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-survive-fwk-05.txt

IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=18472&rfc_flag=0

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.