Subject: draft-chang-mpls-path-protection

From: [email-masked]
Date: Tue, 15 Jan 2002 18:28:47 -0600

Hi 

three questions on the drafts draft-chang-mpls-path-protection and 
draft-owens-crldp-path-protection:
1. I understand that the PSL receives the ER -Protection ER-HOP TLV 
without an Path Protection TLV. 
Before forwarding the label request message, the PSL introduces the Path 

Protection TVL. Therefore, the PSL must decide which value the value of 
the Flags field in the Path Protection TLV. Based on what is this 
decision taken ? Network policy ? Would it not make sense that the 
ingress router tells the PSL how to choose the Flags field.
2. Once the PSL has decided how to set the Flags field, he needs to be 
able to distinguish between working and protection path to forward the 
data along the correct path. If CR-LDP is used, the work and protection 
path both have the same LSPID TLV (non-merged) or the same FEC TLV 
(merged). So what information does the LSR use to distinguisg between 
both paths ?
3. Why do you chose different common identifier for working and 
protection path in the merged and non-merged case ?

Thanks in advance

Claus

Dr. Claus Bauer
Research engineer
Tellabs Research Center
One Kendall Square
Bldg. 100, Suite 121
Cambridge, MA, 02139
USA

Tel.: +1 617 577 8787
Fax.: +1 617 494 0118
 
Dr. Claus Bauer
Research engineer
Tellabs Research Center
One Kendall Square
Bldg. 100, Suite 121
Cambridge, MA, 02139
USA

Tel.: +1 617 577 8787
Fax.: +1 617 494 0118