Shane Amante | 1 Aug 2010 04:38

Re: [PWE3] ELI as a reserved label

Hi Curtis,

I had some time to think about this some more on the plane ride home.  See below.

On Jul 30, 2010, at 14:02 GMT+02:00, Curtis Villamizar wrote:
> In message <0DEFA7EF-8DC4-4EF2-ABDF-0404FC32B992 <at> castlepoint.net>
> Shane Amante writes:
>> 
>> Curtis,
>> 
>> On Jul 30, 2010, at 11:06 GMT+02:00, Curtis Villamizar wrote:
>>> The Entropy Label Indicator (ELI) is called for in
>>> draft-kompella-mpls-entropy-label-01.txt
>>> 
>>> After brief discussion with Stewart and with Kireeti and Lucy Yong,
>>> there were three uses of ELI that would benefit from making the ELI a
>>> reserved label.  It may be premature to make any such request and the
>>> remaining reserved label number space is sparse, so this will be
>>> floated as a separate draft, and put on hold awaiting advancement of
>>> the drafts that depend on it.
>>> 
>>> The three benefits of making ELI a reserved label are in:
>>> 
>>> 1.  Extending any use of entropy-label to P2MP (where there are
>>>     multiple egress and the possibility of each egress requiring a
>>>     separate entropy label value is problematic for the ingress).
>>> 
>>> 2.  Extending any use of entropy-label to any arbitrary position in
>>>     the label stack such that in an aggregation LSP with aggregates
>>>     both MPLS-TP and MPLS LSP, load split on the MPLS LSPs is
(Continue reading)

liu.guoman | 2 Aug 2010 03:43
Picon

Re: a question about draft-cheung-mpls-tp-mesh-protection-01


Jeong-dong,
I don't completely understand your describles.
in former part, you think the protection locking message is not a reply message ,but is
a originator of request message.
while in your last sentence. the Message is not originated by a SEN.
so I can't see this locking message is originator of Locking request message or only a reply
to protection switching Request message arrived at the SEN?
if it is the former, SEN as MIP of a path, it can't actively initiate a request messgae.
else if it  is only the reply to protection switching request message. IMO, for the following
example:
 
          A------B------C  D------E------F
           \   LPD1   /        \   LPD3  /
             \            /            \            /
              P-----Q----------R-----S
             /                                   \
            /           LPD2                \
           /                                        \
          G--------------H---------------J

when a path G-H-J have failure, end node G firstly initiate a protection switching event message to
 SEN node P, R. if SEN node P,R would relpy to the protection switching event, the Reply message(locking
 message) should be sent to the end nodes G or J of LPD2, can't be sent to the end nodes D,F of LPD3;

 my understanding to your opinions may be wrong?

  best regards
  liu
 




"Ryoo, Jeong-dong" <ryoo <at> etri.re.kr>

2010-07-30 18:22

请答复 给
"Ryoo, Jeong-dong" <ryoo <at> etri.re.kr>

收件人
<liu.guoman <at> zte.com.cn>, "Taesik Cheung" <cts <at> etri.re.kr>
抄送
<mpls <at> ietf.org>, <mpls-bounces <at> ietf.org>, <mpls-tp <at> ietf.org>
主题
RE: Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01





Liu,
 
What you described in your email is aligned with the operations stated in the MPLS-TP mesh protection draft.
The protection locking message is not exactly a reply message, which goes to the originator of the request message.
It is certainly destined to other nodes, which share the common facility,
This is an additional function of SEN to provide the shared mesh protection.
What I would like to emphasize is that this message is not originated by a SEN (a MIP of the path for linear protection) if there is no protection switching event message arrived at the SEN,
 
Best regards,
 
Jeong-dong    
==============================================
Jeong-dong Ryoo, Ph.D.
Principal Member of Research Staff
Network Research Department
Electronics and Telecommunications Research Institute (ETRI)
Phone: +82-42-860-5384, Fax: +82-42-860-6342
Email: ryoo <at> etri.re.kr
==============================================

-----Original Message-----
From: "liu.guoman <at> zte.com.cn" <liu.guoman <at> zte.com.cn>
From Date: 2010-07-30 PM 6:21:08
To: "Taesik Cheung" <cts <at> etri.re.kr>
Cc: "mpls <at> ietf.org" <mpls <at> ietf.org>, "mpls-bounces <at> ietf.org" <mpls-bounces <at> ietf.org>, "mpls-tp <at> ietf.org" <mpls-tp <at> ietf.org>, "ryoo <at> etri.re.kr" <ryoo <at> etri.re.kr>
Subject: Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01


Taesik
thank you for replying .but I don't agree your opinions
According to your describles in the draft. I think the protection locking message isn't  a response to the protection state change notification message sent from a MEP.
and it is activley generate a Locking Request message for the SEN node.
for example. the following figure :
         A------B------C  D------E------F
           \   LPD1   /        \   LPD3  /
             \            /            \            /
              P-----Q----------R-----S
             /                                   \
            /           LPD2                \
           /                                        \
          G--------------H---------------J
a. Node G detects the failure, and initiates the linear protection
     switching for the failed working path G-H-J;

  b. At the same time, node G generates the protection switching event
     message saying that a protection switching event happened to node
     P and R, which are SENs for J->H->G.

  c. The SEN P compares the protection switching priority of LPD2 with
     that of LPD1. In this example, as the priority of LPD1 is higher
     than LPD2, SEN P does not take an action to node A.
     The SEN R compares the protection switching priority of LPD2 with
     that of LPD3. In this example, as the priority of LPD3 is lower
     than LPD2, SEN R sends the protection locking message requesting
     LoP to node D.(if the Locking message is a response to the protection
     state change , I think the Locking message should send to Node G ,
     not node D. because at the time there is no protection state change for LPD2 .
    Node D can't send any state change request to SEN node R firstly.
    do you think so?  )

  d. Node D takes the protection locking message as an input to the
     linear protection switching, and follows the linear protection
     switching procedure to process the end-to-end LoP command

maybe my understanding be wrong?

 best regards
  liu
     
   




"Taesik Cheung" <cts <at> etri.re.kr>
?件人:  mpls-bounces <at> ietf.org

2010-07-30 16:45

?答? ?
Taesik Cheung <cts <at> etri.re.kr>


收件人
<liu.guoman <at> zte.com.cn>, <ryoo <at> etri.re.kr>
抄送
mpls <at> ietf.org, mpls-tp <at> ietf.org
主?
Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01


   





Hi Liu,
 
Thank you for the comments.
Please see in-line.
 
Regards,
Taesik
 

-----Original Message-----
From: "liu.guoman <at> zte.com.cn" <liu.guoman <at> zte.com.cn>
From Date: 2010-07-30 PM 5:06:30
To: "ryoo <at> etri.re.kr" <ryoo <at> etri.re.kr>, "cts <at> etri.re.kr" <cts <at> etri.re.kr>
Cc: "mpls <at> ietf.org" <mpls <at> ietf.org>, "mpls-tp <at> ietf.org" <mpls-tp <at> ietf.org>
Subject: a question about draft-cheung-mpls-tp-mesh-protection-01


hi,
today I reviewed your this draft, I have a few questions for mesh protection
1 in section 3, In my mind, there is a sentence : In both cases, 1:1 or 1+1 protection may be used.
 if there use 1+1 protection for each working path. it is no necessary to apply mesh protection.
 beacause the bandwidth resource of protection is equal to the sum of bandwidth resource of all
 protected path. so I think 1+1 protection should not be used in the mesh protection.
 do you think so?
[Taesik] Yes, if 1+1 protection is used, shared mesh protection is not necessary. The sentence is just generic one. Right after the sentence, we described that if 1:1 protection is used, the segment PQR can be shared by two protection paths.

2 about the Shared node SEN will send the protection locking message requesting
    LoP to the end node of protected LSP. IMO, as SEN node is MIP of the protected
    LSP , it can't generate unsolicit OAM packet to send other node. so how to generate
  the protection locking message requesting LOP in the SEN node ?
[Taesik] The protection locking message is a response to the protection state change notification message sent from a MEP. It is similar to LTM/LTR or Lock Intruct / Lock Report relationship.
 

Maybe i miss something important?
thank you

best regards
liu

 
   
   




--------------------------------------------------------
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.
_______________________________________________
mpls mailing list
mpls <at> 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.



-------------------------------------------------------- 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.
_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls
Ryoo, Jeong-dong | 2 Aug 2010 05:10
Picon
Picon

Re: a question about draft-cheung-mpls-tp-mesh-protection-01

Liu,
 
I think you have correct understanding on the mesh protection draft.
 
What I wanted to say was that the locking message from a SEN is generated due to the event message arrived at the SEN from an end node of the linear protection domain that suffers a failure,
The locking message is not exactly a reply to the event message as the locking message does not go to the source of the event message, but it can be viewed as a kind of such a message since the locking message cannot be generated without an event message.  
 
Best regards
 
Jeong-dong

 
==============================================
Jeong-dong Ryoo, Ph.D.
Principal Member of Research Staff
Network Research Department
Electronics and Telecommunications Research Institute (ETRI)
Phone: +82-42-860-5384, Fax: +82-42-860-6342
Email: ryoo <at> etri.re.kr
==============================================

-----Original Message-----
From: "liu.guoman <at> zte.com.cn" <liu.guoman <at> zte.com.cn>
From Date: 2010-08-02 AM 10:43:55
To: "Ryoo, Jeong-dong" <ryoo <at> etri.re.kr>
Cc: "Taesik Cheung" <cts <at> etri.re.kr>, "mpls <at> ietf.org" <mpls <at> ietf.org>, "mpls-bounces <at> ietf.org" <mpls-bounces <at> ietf.org>, "mpls-tp <at> ietf.org" <mpls-tp <at> ietf.org>
Subject: RE: Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01


Jeong-dong,
I don't completely understand your describles.
in former part, you think the protection locking message is not a reply message ,but is
a originator of request message.
while in your last sentence. the Message is not originated by a SEN.
so I can't see this locking message is originator of Locking request message or only a reply
to protection switching Request message arrived at the SEN?
if it is the former, SEN as MIP of a path, it can't actively initiate a request messgae.
else if it  is only the reply to protection switching request message. IMO, for the following
example:
 
          A------B------C  D------E------F
           \   LPD1   /        \   LPD3  /
             \            /            \            /
              P-----Q----------R-----S
             /                                   \
            /           LPD2                \
           /                                        \
          G--------------H---------------J

when a path G-H-J have failure, end node G firstly initiate a protection switching event message to
 SEN node P, R. if SEN node P,R would relpy to the protection switching event, the Reply message(locking
 message) should be sent to the end nodes G or J of LPD2, can't be sent to the end nodes D,F of LPD3;

 my understanding to your opinions may be wrong?

  best regards
  liu
 
   




"Ryoo, Jeong-dong" <ryoo <at> etri.re.kr>

2010-07-30 18:22

?答? ?
"Ryoo, Jeong-dong" <ryoo <at> etri.re.kr>

收件人
<liu.guoman <at> zte.com.cn>, "Taesik Cheung" <cts <at> etri.re.kr>
抄送
<mpls <at> ietf.org>, <mpls-bounces <at> ietf.org>, <mpls-tp <at> ietf.org>
主?
RE: Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01

   




Liu,
 
What you described in your email is aligned with the operations stated in the MPLS-TP mesh protection draft.
The protection locking message is not exactly a reply message, which goes to the originator of the request message.
It is certainly destined to other nodes, which share the common facility,
This is an additional function of SEN to provide the shared mesh protection.
What I would like to emphasize is that this message is not originated by a SEN (a MIP of the path for linear protection) if there is no protection switching event message arrived at the SEN,
 
Best regards,
 
Jeong-dong    
==============================================
Jeong-dong Ryoo, Ph.D.
Principal Member of Research Staff
Network Research Department
Electronics and Telecommunications Research Institute (ETRI)
Phone: +82-42-860-5384, Fax: +82-42-860-6342
Email: ryoo <at> etri.re.kr
==============================================

-----Original Message-----
From: "liu.guoman <at> zte.com.cn" <liu.guoman <at> zte.com.cn>
From Date: 2010-07-30 PM 6:21:08
To: "Taesik Cheung" <cts <at> etri.re.kr>
Cc: "mpls <at> ietf.org" <mpls <at> ietf.org>, "mpls-bounces <at> ietf.org" <mpls-bounces <at> ietf.org>, "mpls-tp <at> ietf.org" <mpls-tp <at> ietf.org>, "ryoo <at> etri.re.kr" <ryoo <at> etri.re.kr>
Subject: Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01


Taesik
thank you for replying .but I don't agree your opinions
According to your describles in the draft. I think the protection locking message isn't  a response to the protection state change notification message sent from a MEP.
and it is activley generate a Locking Request message for the SEN node.
for example. the following figure :
         A------B------C  D------E------F
           \   LPD1   /        \   LPD3  /
             \            /            \            /
              P-----Q----------R-----S
             /                                   \
            /           LPD2                \
           /                                        \
          G--------------H---------------J
a. Node G detects the failure, and initiates the linear protection
     switching for the failed working path G-H-J;

  b. At the same time, node G generates the protection switching event
     message saying that a protection switching event happened to node
     P and R, which are SENs for J->H->G.

  c. The SEN P compares the protection switching priority of LPD2 with
     that of LPD1. In this example, as the priority of LPD1 is higher
     than LPD2, SEN P does not take an action to node A.
     The SEN R compares the protection switching priority of LPD2 with
     that of LPD3. In this example, as the priority of LPD3 is lower
     than LPD2, SEN R sends the protection locking message requesting
     LoP to node D.(if the Locking message is a response to the protection
     state change , I think the Locking message should send to Node G ,
     not node D. because at the time there is no protection state change for LPD2 .
    Node D can't send any state change request to SEN node R firstly.
    do you think so?  )

  d. Node D takes the protection locking message as an input to the
     linear protection switching, and follows the linear protection
     switching procedure to process the end-to-end LoP command

maybe my understanding be wrong?

 best regards
  liu
     
   




"Taesik Cheung" <cts <at> etri.re.kr>
?件人:  mpls-bounces <at> ietf.org

2010-07-30 16:45

?答? ?
Taesik Cheung <cts <at> etri.re.kr>


收件人
<liu.guoman <at> zte.com.cn>, <ryoo <at> etri.re.kr>
抄送
mpls <at> ietf.org, mpls-tp <at> ietf.org
主?
Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01


   





Hi Liu,
 
Thank you for the comments.
Please see in-line.
 
Regards,
Taesik
 

-----Original Message-----
From: "liu.guoman <at> zte.com.cn" <liu.guoman <at> zte.com.cn>
From Date: 2010-07-30 PM 5:06:30
To: "ryoo <at> etri.re.kr" <ryoo <at> etri.re.kr>, "cts <at> etri.re.kr" <cts <at> etri.re.kr>
Cc: "mpls <at> ietf.org" <mpls <at> ietf.org>, "mpls-tp <at> ietf.org" <mpls-tp <at> ietf.org>
Subject: a question about draft-cheung-mpls-tp-mesh-protection-01


hi,
today I reviewed your this draft, I have a few questions for mesh protection
1 in section 3, In my mind, there is a sentence : In both cases, 1:1 or 1+1 protection may be used.
 if there use 1+1 protection for each working path. it is no necessary to apply mesh protection.
 beacause the bandwidth resource of protection is equal to the sum of bandwidth resource of all
 protected path. so I think 1+1 protection should not be used in the mesh protection.
 do you think so?
[Taesik] Yes, if 1+1 protection is used, shared mesh protection is not necessary. The sentence is just generic one. Right after the sentence, we described that if 1:1 protection is used, the segment PQR can be shared by two protection paths.

2 about the Shared node SEN will send the protection locking message requesting
    LoP to the end node of protected LSP. IMO, as SEN node is MIP of the protected
    LSP , it can't generate unsolicit OAM packet to send other node. so how to generate
  the protection locking message requesting LOP in the SEN node ?
[Taesik] The protection locking message is a response to the protection state change notification message sent from a MEP. It is similar to LTM/LTR or Lock Intruct / Lock Report relationship.
 

Maybe i miss something important?
thank you

best regards
liu

 
   
   




--------------------------------------------------------
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.
_______________________________________________
mpls mailing list
mpls <at> 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.



-------------------------------------------------------- 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.
_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls
Ryoo, Jeong-dong | 2 Aug 2010 06:44
Picon
Picon

Re: a question about draft-cheung-mpls-tp-mesh-protection-01

Liu,
 
LCK instruction/report are the functions of OAM,
What we are interested in here is "Lockout of Protection (LoP)" in protection switching,
When an end node of linear protection domain receives the protection locking message from a SEN,
it acts in the same way as an LoP command is issued.

Jeong-dong
 
==============================================
Jeong-dong Ryoo, Ph.D.
Principal Member of Research Staff
Network Research Department
Electronics and Telecommunications Research Institute (ETRI)
Phone: +82-42-860-5384, Fax: +82-42-860-6342
Email: ryoo <at> etri.re.kr
==============================================

-----Original Message-----
From: "liu.guoman <at> zte.com.cn" <liu.guoman <at> zte.com.cn>
From Date: 2010-08-02 PM 1:24:07
To: "Ryoo, Jeong-dong" <ryoo <at> etri.re.kr>
Cc: "Taesik Cheung" <cts <at> etri.re.kr>, "mpls <at> ietf.org" <mpls <at> ietf.org>, "mpls-bounces <at> ietf.org" <mpls-bounces <at> ietf.org>, "mpls-tp <at> ietf.org" <mpls-tp <at> ietf.org>
Subject: RE: Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01


Jeong-dong,
IMO, Lock message mainly include two type of message: one is Lock instuction, another is Lock reporting.
if Lock mesage is similar to Lock instruction, it should be only generated by MEP of LSP to lock LSP path
in the peer MEP. not be generated by SEN(MIP of LSP);
if lock message is similar to Lock reporting, it may  be generated in MIP of LSP when the server layer is lock state.
but this draft is not the situation, why to generate Lock messasge in MIP of LSP.

can this function be added just now?

best regards
liu
   




"Ryoo, Jeong-dong" <ryoo <at> etri.re.kr>

2010-08-02 11:10

?答? ?
"Ryoo, Jeong-dong" <ryoo <at> etri.re.kr>

收件人
<liu.guoman <at> zte.com.cn>
抄送
"Taesik Cheung" <cts <at> etri.re.kr>, <mpls <at> ietf.org>, <mpls-bounces <at> ietf.org>, <mpls-tp <at> ietf.org>
主?
RE: Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01

   




Liu,
 
I think you have correct understanding on the mesh protection draft.
 
What I wanted to say was that the locking message from a SEN is generated due to the event message arrived at the SEN from an end node of the linear protection domain that suffers a failure,
The locking message is not exactly a reply to the event message as the locking message does not go to the source of the event message, but it can be viewed as a kind of such a message since the locking message cannot be generated without an event message.  
 
Best regards
 
Jeong-dong


==============================================
Jeong-dong Ryoo, Ph.D.
Principal Member of Research Staff
Network Research Department
Electronics and Telecommunications Research Institute (ETRI)
Phone: +82-42-860-5384, Fax: +82-42-860-6342
Email: ryoo <at> etri.re.kr
==============================================

-----Original Message-----
From: "liu.guoman <at> zte.com.cn" <liu.guoman <at> zte.com.cn>
From Date: 2010-08-02 AM 10:43:55
To: "Ryoo, Jeong-dong" <ryoo <at> etri.re.kr>
Cc: "Taesik Cheung" <cts <at> etri.re.kr>, "mpls <at> ietf.org" <mpls <at> ietf.org>, "mpls-bounces <at> ietf.org" <mpls-bounces <at> ietf.org>, "mpls-tp <at> ietf.org" <mpls-tp <at> ietf.org>
Subject: RE: Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01


Jeong-dong,
I don't completely understand your describles.
in former part, you think the protection locking message is not a reply message ,but is
a originator of request message.
while in your last sentence. the Message is not originated by a SEN.
so I can't see this locking message is originator of Locking request message or only a reply
to protection switching Request message arrived at the SEN?
if it is the former, SEN as MIP of a path, it can't actively initiate a request messgae.
else if it  is only the reply to protection switching request message. IMO, for the following
example:
 
         A------B------C  D------E------F
          \   LPD1   /        \   LPD3  /
            \            /            \            /
             P-----Q----------R-----S
            /                                   \
           /           LPD2                \
          /                                        \
         G--------------H---------------J

when a path G-H-J have failure, end node G firstly initiate a protection switching event message to
SEN node P, R. if SEN node P,R would relpy to the protection switching event, the Reply message(locking
message) should be sent to the end nodes G or J of LPD2, can't be sent to the end nodes D,F of LPD3;

my understanding to your opinions may be wrong?

 best regards
 liu
 
   




"Ryoo, Jeong-dong" <ryoo <at> etri.re.kr>

2010-07-30 18:22

?答? ?
"Ryoo, Jeong-dong" <ryoo <at> etri.re.kr>


收件人
<liu.guoman <at> zte.com.cn>, "Taesik Cheung" <cts <at> etri.re.kr>
抄送
<mpls <at> ietf.org>, <mpls-bounces <at> ietf.org>, <mpls-tp <at> ietf.org>
主?
RE: Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01


   





Liu,
 
What you described in your email is aligned with the operations stated in the MPLS-TP mesh protection draft.
The protection locking message is not exactly a reply message, which goes to the originator of the request message.
It is certainly destined to other nodes, which share the common facility,
This is an additional function of SEN to provide the shared mesh protection.
What I would like to emphasize is that this message is not originated by a SEN (a MIP of the path for linear protection) if there is no protection switching event message arrived at the SEN,
 
Best regards,
 
Jeong-dong    
==============================================
Jeong-dong Ryoo, Ph.D.
Principal Member of Research Staff
Network Research Department
Electronics and Telecommunications Research Institute (ETRI)
Phone: +82-42-860-5384, Fax: +82-42-860-6342
Email: ryoo <at> etri.re.kr
==============================================

-----Original Message-----
From: "liu.guoman <at> zte.com.cn" <liu.guoman <at> zte.com.cn>
From Date: 2010-07-30 PM 6:21:08
To: "Taesik Cheung" <cts <at> etri.re.kr>
Cc: "mpls <at> ietf.org" <mpls <at> ietf.org>, "mpls-bounces <at> ietf.org" <mpls-bounces <at> ietf.org>, "mpls-tp <at> ietf.org" <mpls-tp <at> ietf.org>, "ryoo <at> etri.re.kr" <ryoo <at> etri.re.kr>
Subject: Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01


Taesik
thank you for replying .but I don't agree your opinions
According to your describles in the draft. I think the protection locking message isn't  a response to the protection state change notification message sent from a MEP.
and it is activley generate a Locking Request message for the SEN node.
for example. the following figure :
        A------B------C  D------E------F
          \   LPD1   /        \   LPD3  /
            \            /            \            /
             P-----Q----------R-----S
            /                                   \
           /           LPD2                \
          /                                        \
         G--------------H---------------J
a. Node G detects the failure, and initiates the linear protection
    switching for the failed working path G-H-J;

 b. At the same time, node G generates the protection switching event
    message saying that a protection switching event happened to node
    P and R, which are SENs for J->H->G.

 c. The SEN P compares the protection switching priority of LPD2 with
    that of LPD1. In this example, as the priority of LPD1 is higher
    than LPD2, SEN P does not take an action to node A.
    The SEN R compares the protection switching priority of LPD2 with
    that of LPD3. In this example, as the priority of LPD3 is lower
    than LPD2, SEN R sends the protection locking message requesting
    LoP to node D.(if the Locking message is a response to the protection
    state change , I think the Locking message should send to Node G ,
    not node D. because at the time there is no protection state change for LPD2 .
   Node D can't send any state change request to SEN node R firstly.
   do you think so?  )

 d. Node D takes the protection locking message as an input to the
    linear protection switching, and follows the linear protection
    switching procedure to process the end-to-end LoP command

maybe my understanding be wrong?

best regards
 liu
   
   




"Taesik Cheung" <cts <at> etri.re.kr>
?件人:  mpls-bounces <at> ietf.org

2010-07-30 16:45

?答? ?
Taesik Cheung <cts <at> etri.re.kr>


收件人
<liu.guoman <at> zte.com.cn>, <ryoo <at> etri.re.kr>
抄送
mpls <at> ietf.org, mpls-tp <at> ietf.org
主?
Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01



   






Hi Liu,

Thank you for the comments.
Please see in-line.

Regards,
Taesik


-----Original Message-----
From: "liu.guoman <at> zte.com.cn" <liu.guoman <at> zte.com.cn>
From Date: 2010-07-30 PM 5:06:30
To: "ryoo <at> etri.re.kr" <ryoo <at> etri.re.kr>, "cts <at> etri.re.kr" <cts <at> etri.re.kr>
Cc: "mpls <at> ietf.org" <mpls <at> ietf.org>, "mpls-tp <at> ietf.org" <mpls-tp <at> ietf.org>
Subject: a question about draft-cheung-mpls-tp-mesh-protection-01


hi,
today I reviewed your this draft, I have a few questions for mesh protection
1 in section 3, In my mind, there is a sentence : In both cases, 1:1 or 1+1 protection may be used.
if there use 1+1 protection for each working path. it is no necessary to apply mesh protection.
beacause the bandwidth resource of protection is equal to the sum of bandwidth resource of all
protected path. so I think 1+1 protection should not be used in the mesh protection.
do you think so?
[Taesik] Yes, if 1+1 protection is used, shared mesh protection is not necessary. The sentence is just generic one. Right after the sentence, we described that if 1:1 protection is used, the segment PQR can be shared by two protection paths.

2 about the Shared node SEN will send the protection locking message requesting
   LoP to the end node of protected LSP. IMO, as SEN node is MIP of the protected
   LSP , it can't generate unsolicit OAM packet to send other node. so how to generate
 the protection locking message requesting LOP in the SEN node ?
[Taesik] The protection locking message is a response to the protection state change notification message sent from a MEP. It is similar to LTM/LTR or Lock Intruct / Lock Report relationship.


Maybe i miss something important?
thank you

best regards
liu

 
   
   





--------------------------------------------------------
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.
_______________________________________________
mpls mailing list
mpls <at> 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.



--------------------------------------------------------
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.



-------------------------------------------------------- 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.
_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls
Ryoo, Jeong-dong | 2 Aug 2010 10:59
Picon
Picon

Re: a question about draft-cheung-mpls-tp-mesh-protection-01

Liu,
 
The two messages that are introduced in the draft are specific to the mesh protection.
Therefore, those messages cannot be included in the set of the linear protection protocol messages.
And they are not OAM messages, either.
 
The encapsulations of those messages are not deternined.
If you have any suggestions, please let us know.
 
Jeong-dong

 
==============================================
Jeong-dong Ryoo, Ph.D.
Principal Member of Research Staff
Network Research Department
Electronics and Telecommunications Research Institute (ETRI)
Phone: +82-42-860-5384, Fax: +82-42-860-6342
Email: ryoo <at> etri.re.kr
==============================================

-----Original Message-----
From: "liu.guoman <at> zte.com.cn" <liu.guoman <at> zte.com.cn>
From Date: 2010-08-02 PM 3:09:59
To: "Ryoo, Jeong-dong" <ryoo <at> etri.re.kr>
Cc: "mpls <at> ietf.org" <mpls <at> ietf.org>, "mpls-bounces <at> ietf.org" <mpls-bounces <at> ietf.org>, "mpls-tp <at> ietf.org" <mpls-tp <at> ietf.org>
Subject: Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01


Jeong-dong,
I know here Lock message is not Lock instuction/report. but the message should be
encapusalted into APS/PSC or other OAM packet to transported to other nodes.
if the Lock message is in the APS/PSC packet, they should run between the peer MEPs in the
section, lsp and PW . not run between MEP and MIP for a LSP.
if the lock message is in OAM packet, it may be similar to Lock instruct/report to use to
lock of protection. not lock of LSP.

best regards
liu
   




"Ryoo, Jeong-dong" <ryoo <at> etri.re.kr>
?件人:  mpls-bounces <at> ietf.org

2010-08-02 12:44

?答? ?
"Ryoo, Jeong-dong" <ryoo <at> etri.re.kr>

收件人
<liu.guoman <at> zte.com.cn>
抄送
mpls <at> ietf.org, mpls-bounces <at> ietf.org, mpls-tp <at> ietf.org
主?
Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01

   




Liu,
 
LCK instruction/report are the functions of OAM,
What we are interested in here is "Lockout of Protection (LoP)" in protection switching,
When an end node of linear protection domain receives the protection locking message from a SEN,
it acts in the same way as an LoP command is issued.

Jeong-dong
 
==============================================
Jeong-dong Ryoo, Ph.D.
Principal Member of Research Staff
Network Research Department
Electronics and Telecommunications Research Institute (ETRI)
Phone: +82-42-860-5384, Fax: +82-42-860-6342
Email: ryoo <at> etri.re.kr
==============================================

-----Original Message-----
From: "liu.guoman <at> zte.com.cn" <liu.guoman <at> zte.com.cn>
From Date: 2010-08-02 PM 1:24:07
To: "Ryoo, Jeong-dong" <ryoo <at> etri.re.kr>
Cc: "Taesik Cheung" <cts <at> etri.re.kr>, "mpls <at> ietf.org" <mpls <at> ietf.org>, "mpls-bounces <at> ietf.org" <mpls-bounces <at> ietf.org>, "mpls-tp <at> ietf.org" <mpls-tp <at> ietf.org>
Subject: RE: Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01


Jeong-dong,
IMO, Lock message mainly include two type of message: one is Lock instuction, another is Lock reporting.
if Lock mesage is similar to Lock instruction, it should be only generated by MEP of LSP to lock LSP path
in the peer MEP. not be generated by SEN(MIP of LSP);
if lock message is similar to Lock reporting, it may  be generated in MIP of LSP when the server layer is lock state.
but this draft is not the situation, why to generate Lock messasge in MIP of LSP.

can this function be added just now?

best regards
liu
   




"Ryoo, Jeong-dong" <ryoo <at> etri.re.kr>

2010-08-02 11:10

?答? ?
"Ryoo, Jeong-dong" <ryoo <at> etri.re.kr>


收件人
<liu.guoman <at> zte.com.cn>
抄送
"Taesik Cheung" <cts <at> etri.re.kr>, <mpls <at> ietf.org>, <mpls-bounces <at> ietf.org>, <mpls-tp <at> ietf.org>
主?
RE: Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01


   





Liu,
 
I think you have correct understanding on the mesh protection draft.
 
What I wanted to say was that the locking message from a SEN is generated due to the event message arrived at the SEN from an end node of the linear protection domain that suffers a failure,
The locking message is not exactly a reply to the event message as the locking message does not go to the source of the event message, but it can be viewed as a kind of such a message since the locking message cannot be generated without an event message.  
 
Best regards
 
Jeong-dong


==============================================
Jeong-dong Ryoo, Ph.D.
Principal Member of Research Staff
Network Research Department
Electronics and Telecommunications Research Institute (ETRI)
Phone: +82-42-860-5384, Fax: +82-42-860-6342
Email: ryoo <at> etri.re.kr
==============================================

-----Original Message-----
From: "liu.guoman <at> zte.com.cn" <liu.guoman <at> zte.com.cn>
From Date: 2010-08-02 AM 10:43:55
To: "Ryoo, Jeong-dong" <ryoo <at> etri.re.kr>
Cc: "Taesik Cheung" <cts <at> etri.re.kr>, "mpls <at> ietf.org" <mpls <at> ietf.org>, "mpls-bounces <at> ietf.org" <mpls-bounces <at> ietf.org>, "mpls-tp <at> ietf.org" <mpls-tp <at> ietf.org>
Subject: RE: Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01


Jeong-dong,
I don't completely understand your describles.
in former part, you think the protection locking message is not a reply message ,but is
a originator of request message.
while in your last sentence. the Message is not originated by a SEN.
so I can't see this locking message is originator of Locking request message or only a reply
to protection switching Request message arrived at the SEN?
if it is the former, SEN as MIP of a path, it can't actively initiate a request messgae.
else if it  is only the reply to protection switching request message. IMO, for the following
example:

        A------B------C  D------E------F
         \   LPD1   /        \   LPD3  /
           \            /            \            /
            P-----Q----------R-----S
           /                                   \
          /           LPD2                \
         /                                        \
        G--------------H---------------J

when a path G-H-J have failure, end node G firstly initiate a protection switching event message to
SEN node P, R. if SEN node P,R would relpy to the protection switching event, the Reply message(locking
message) should be sent to the end nodes G or J of LPD2, can't be sent to the end nodes D,F of LPD3;

my understanding to your opinions may be wrong?

best regards
liu
 
   




"Ryoo, Jeong-dong" <ryoo <at> etri.re.kr>

2010-07-30 18:22

?答? ?
"Ryoo, Jeong-dong" <ryoo <at> etri.re.kr>


收件人
<liu.guoman <at> zte.com.cn>, "Taesik Cheung" <cts <at> etri.re.kr>
抄送
<mpls <at> ietf.org>, <mpls-bounces <at> ietf.org>, <mpls-tp <at> ietf.org>
主?
RE: Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01



   






Liu,

What you described in your email is aligned with the operations stated in the MPLS-TP mesh protection draft.
The protection locking message is not exactly a reply message, which goes to the originator of the request message.
It is certainly destined to other nodes, which share the common facility,
This is an additional function of SEN to provide the shared mesh protection.
What I would like to emphasize is that this message is not originated by a SEN (a MIP of the path for linear protection) if there is no protection switching event message arrived at the SEN,

Best regards,

Jeong-dong    
==============================================
Jeong-dong Ryoo, Ph.D.
Principal Member of Research Staff
Network Research Department
Electronics and Telecommunications Research Institute (ETRI)
Phone: +82-42-860-5384, Fax: +82-42-860-6342
Email: ryoo <at> etri.re.kr
==============================================

-----Original Message-----
From: "liu.guoman <at> zte.com.cn" <liu.guoman <at> zte.com.cn>
From Date: 2010-07-30 PM 6:21:08
To: "Taesik Cheung" <cts <at> etri.re.kr>
Cc: "mpls <at> ietf.org" <mpls <at> ietf.org>, "mpls-bounces <at> ietf.org" <mpls-bounces <at> ietf.org>, "mpls-tp <at> ietf.org" <mpls-tp <at> ietf.org>, "ryoo <at> etri.re.kr" <ryoo <at> etri.re.kr>
Subject: Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01


Taesik
thank you for replying .but I don't agree your opinions
According to your describles in the draft. I think the protection locking message isn't  a response to the protection state change notification message sent from a MEP.
and it is activley generate a Locking Request message for the SEN node.
for example. the following figure :
       A------B------C  D------E------F
         \   LPD1   /        \   LPD3  /
           \            /            \            /
            P-----Q----------R-----S
           /                                   \
          /           LPD2                \
         /                                        \
        G--------------H---------------J
a. Node G detects the failure, and initiates the linear protection
   switching for the failed working path G-H-J;

b. At the same time, node G generates the protection switching event
   message saying that a protection switching event happened to node
   P and R, which are SENs for J->H->G.

c. The SEN P compares the protection switching priority of LPD2 with
   that of LPD1. In this example, as the priority of LPD1 is higher
   than LPD2, SEN P does not take an action to node A.
   The SEN R compares the protection switching priority of LPD2 with
   that of LPD3. In this example, as the priority of LPD3 is lower
   than LPD2, SEN R sends the protection locking message requesting
   LoP to node D.(if the Locking message is a response to the protection
   state change , I think the Locking message should send to Node G ,
   not node D. because at the time there is no protection state change for LPD2 .
  Node D can't send any state change request to SEN node R firstly.
  do you think so?  )

d. Node D takes the protection locking message as an input to the
   linear protection switching, and follows the linear protection
   switching procedure to process the end-to-end LoP command

maybe my understanding be wrong?

best regards
liu
   
   




"Taesik Cheung" <cts <at> etri.re.kr>
?件人:  mpls-bounces <at> ietf.org

2010-07-30 16:45

?答? ?
Taesik Cheung <cts <at> etri.re.kr>


收件人
<liu.guoman <at> zte.com.cn>, <ryoo <at> etri.re.kr>
抄送
mpls <at> ietf.org, mpls-tp <at> ietf.org
主?
Re: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01




   







Hi Liu,

Thank you for the comments.
Please see in-line.

Regards,
Taesik


-----Original Message-----
From: "liu.guoman <at> zte.com.cn" <liu.guoman <at> zte.com.cn>
From Date: 2010-07-30 PM 5:06:30
To: "ryoo <at> etri.re.kr" <ryoo <at> etri.re.kr>, "cts <at> etri.re.kr" <cts <at> etri.re.kr>
Cc: "mpls <at> ietf.org" <mpls <at> ietf.org>, "mpls-tp <at> ietf.org" <mpls-tp <at> ietf.org>
Subject: a question about draft-cheung-mpls-tp-mesh-protection-01


hi,
today I reviewed your this draft, I have a few questions for mesh protection
1 in section 3, In my mind, there is a sentence : In both cases, 1:1 or 1+1 protection may be used.
if there use 1+1 protection for each working path. it is no necessary to apply mesh protection.
beacause the bandwidth resource of protection is equal to the sum of bandwidth resource of all
protected path. so I think 1+1 protection should not be used in the mesh protection.
do you think so?
[Taesik] Yes, if 1+1 protection is used, shared mesh protection is not necessary. The sentence is just generic one. Right after the sentence, we described that if 1:1 protection is used, the segment PQR can be shared by two protection paths.

2 about the Shared node SEN will send the protection locking message requesting
  LoP to the end node of protected LSP. IMO, as SEN node is MIP of the protected
  LSP , it can't generate unsolicit OAM packet to send other node. so how to generate
the protection locking message requesting LOP in the SEN node ?
[Taesik] The protection locking message is a response to the protection state change notification message sent from a MEP. It is similar to LTM/LTR or Lock Intruct / Lock Report relationship.


Maybe i miss something important?
thank you

best regards
liu


   
   






--------------------------------------------------------
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.
_______________________________________________
mpls mailing list
mpls <at> 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.



--------------------------------------------------------
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.



--------------------------------------------------------
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.

_______________________________________________
mpls mailing list
mpls <at> 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.
_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls
Curtis Villamizar | 2 Aug 2010 15:50

Re: [PWE3] ELI as a reserved label


In message <6F8F5330-91F8-456F-BFDC-FF5735CFDD9E <at> castlepoint.net>
Shane Amante writes:
>  
> Curtis,
>  
> On Jul 30, 2010, at 14:02 GMT+02:00, Curtis Villamizar wrote:
> > In message <0DEFA7EF-8DC4-4EF2-ABDF-0404FC32B992 <at> castlepoint.net>
> > Shane Amante writes:
> >> On Jul 30, 2010, at 11:06 GMT+02:00, Curtis Villamizar wrote:
>  
> [--snip--]
>  
> >>> 3.  Providing a means to carry indication of large flow as described
> >>>     in draft-yong-pwe3-enhance-ecmp-lfat-01.txt and
> >>>     draft-yong-pwe3-lfc-fat-pw-01.txt without changing the use of TC
> >>>     in a forwarding LSP label.
> >> 
> >> I'm unclear how a single, reserved label would be a means of signaling
> >> a large vs. small flow.  How can a single label represent two states
> >> (large vs. small flow)?
> > 
> > That's the slightly ugly part.  If ELI carries a TTL=0 then it can't
> > be used to forward and among those that discussed this (in one of the
> > "hallway sessions" near the registration desk) it was not seen as too
> > horribly ugly if TC meaned something else in the ELI label stack entry
> > only.
> > 
> > Lucy has a different way to do multipath and this is an enabler.  If
> > your LSRs don't use it, then it does no harm as long as the hashed
> > entropy value is there too.
>  
> Understood.
>  
> I would note that in draft-kompella-mpls-entropy-label-01 it is NOT envisioned that there will be a
"standalone ELI" in all cases.  Specifically, in the case where application labels are in use, (e.g.: 2547
VPN's, 6PE, etc.), the application label itself is intended to serve the purpose of an ELI, indicating
that the label that immediately follows the application label is an entropy-label, i.e.:
>  
> +----------------+
> |  Tunnel Label  |
> +----------------+
> |   App. Label   |
> +----------------+
> | Entropy Label  |
> +----------------+
>  
> In these cases, there wouldn't be a reserved label used for a ELI in the label stack.  Thus, I'm not sure you
can count on the LFC-bit *only* being set in entropy-labels that are immediately preceded by a reserved
ELI label.
>  
> So, with respect to LFC, IMO it's:
> a)  orthogonal to the discussion of whether or not a reserved label for the ELI is absolutely _required_ or
just nice-to-have; and,
> b)  the MPLS WG needs to weigh in with a definitive answer on whether changing the semantics of the MPLS TC is
appropriate to accommodate end-users who desire LFC.
>  
> -shane

This doesn't work in the following cases:

  1.  P2MP (multiple egress, therefore multiple ELI values).

  2.  Label stack depth is limited in order to accommodate MPLS-TP
      (midpoints must know to look past the ELI to include the entropy
      label in the hash).

Since Lucy's large flow work needed TC, using TTL=0, and reserving one
TC bit for large flow seemed to do no harm.

I spoke to Stewart and Kireeti about this at IETF.  Perhaps either or
both of them could weigh in on this topic on the list.

Curtis

_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls

Curtis Villamizar | 2 Aug 2010 16:17

Re: [PWE3] ELI as a reserved label


In message <8B7721F4-8C12-4C88-9036-B19592BE686E <at> castlepoint.net>
Shane Amante writes:
>  
> Hi Curtis,
>  
> I had some time to think about this some more on the plane ride home.
> See below.
>  
> On Jul 30, 2010, at 14:02 GMT+02:00, Curtis Villamizar wrote:
> > In message <0DEFA7EF-8DC4-4EF2-ABDF-0404FC32B992 <at> castlepoint.net>
> > Shane Amante writes:
> >> 
> >> Curtis,
> >> 
> >> On Jul 30, 2010, at 11:06 GMT+02:00, Curtis Villamizar wrote:
> >>> The Entropy Label Indicator (ELI) is called for in
> >>> draft-kompella-mpls-entropy-label-01.txt
> >>> 
> >>> After brief discussion with Stewart and with Kireeti and Lucy Yong,
> >>> there were three uses of ELI that would benefit from making the ELI a
> >>> reserved label.  It may be premature to make any such request and the
> >>> remaining reserved label number space is sparse, so this will be
> >>> floated as a separate draft, and put on hold awaiting advancement of
> >>> the drafts that depend on it.
> >>> 
> >>> The three benefits of making ELI a reserved label are in:
> >>> 
> >>> 1.  Extending any use of entropy-label to P2MP (where there are
> >>>     multiple egress and the possibility of each egress requiring a
> >>>     separate entropy label value is problematic for the ingress).
> >>> 
> >>> 2.  Extending any use of entropy-label to any arbitrary position in
> >>>     the label stack such that in an aggregation LSP with aggregates
> >>>     both MPLS-TP and MPLS LSP, load split on the MPLS LSPs is
> >>>     simplified and not impacted by limiting label stack depth for
> >>>     the MPLS-TP LSPs.  This is when label stack hash is limited to
> >>>     support MPLS-TP as proposed in
> >>>     draft-villamizar-mpls-tp-multipath-00.txt .
> >> 
> >> I agree there are benefits to a reserved label for the above two
> >> applications.  Most importantly, a receiving node would have pretty
> >> clearly semantics that what [immediately] follows a reserved ELI is
> >> the entropy-label, regardless of where the ELI is in the MPLS label
> >> stack and without needing to be in the signaling path to know what is
> >> the ELI value.
> > 
> > "Now don't be sad ... 'cause two out of three aint bad".  [meatloaf]
> > 
> > Its good to hear that you consider these to be useful.
> > 
> > Note that an ingress LSR still needs to determine that egress LSR
> > understands ELI to do anything.  To support MPLS-TP in MPLS the
> > ingress needs to veryify that all LSR on the path support MPLS in a
> > way that provides a compliant path for a contained TP LSP, but that is
> > out of scope of this discussion.
>  
> I need to revise my statements wrt entropy-labels and P2MP LSP's.
> After thinking about this some more, I no longer believe it makes
> sense to use a reserved ELI value for P2MP LSP's.  More specifically,
> for a given P2MP LSP, all receivers /MUST/ agree to receive entropy
> labels, because it would be silly to (for example) expect core LSR's
> to strip-off the ELI and an entropy-label mid-flight toward receivers
> that don't understand (or, can't receive) entropy-labels.  The
> ramifications of this are that if a head-end detects any receivers of
> a P2MP LSP that can't receive entropy-labels, then the head-end
> LER/LSR must either: a) re-signal the whole P2MP LSP toward all
> receivers so that the head-end will not send any entropy-labels at all
> on the P2MP LSP; or, b) signal 2 separate P2MP LSP's: one for
> entropy-label capable receivers and a second for non-entropy-label
> capable receivers.  I don't know that we want to mandate one of those
> two behaviors over the other, because SP's may make separate choices
> depending on whether they want to avoid extra replication in the
> network at the expense of not being able to do flow-based
> load-balancing, i.e.: Option (a), or don't mind the extra replication
> of (potentially) 2 parallel P2MP trees on the same links in order to
> attain some amount of flow-based load-balancing of the P2MP traffic.

The use of a reserved label doesn't remove the requirement to figure
out if the egress can support ELI.  It just removes the requirement to
put a separate ELI label on for each egress.

If some P2MP paths don't need to load balance (no multipath on that
leg) but other paths do, as long as all egress can support ELI, then
at worst it is 8 bytes of overhead that some paths don't need.

I don't see an alternative for P2MP in your paragraph above.  Are the
branch points assumed to selectively add a different ELI (or none) and
should branch point remove ELI and the entropy label if ELI is not
needed downstream or to the next branch point?  Would this be a lot
more complicated with different values of ELI per egress (and possibly
also per branch point)?

> So, in summary, I no longer see that draft-kompella-mpls-entropy-label
> has a requirement for reserved labels for either P2P or P2MP LSP's
> (scenario 1 in your original e-mail).  Furthermore, I still maintain
> that discussion of LFC and use of the MPLS TC field for indication of
> large vs. small flows is orthogonal to
> draft-kompella-mpls-entropy-label (scenario 3 in your original
> e-mail).  I haven't read draft-villamizar-mpls-tp-multipath-00
> (scenario 2 in your original e-mail) so I can't speak to whether or
> not there is a requirement for a reserved label there.

OK.

> Anyway, perhaps this will save you some time in that you don't need to
> write a whole new draft as you originally proposed and, instead, may
> only need to look at modifying your original draft.  :-)

For load balance to work with stack limited, then all midpoints would
need to know what ELI was being used.

This is a bit like each P2MP needing to know which ELI is needed
downstream of it, but not quite as bad.

OTOH, putting the ELI that is being used on a P2P LSP in the PATH or
RESV message for that P2P LSP would solve this for "Use of Multipath
with MPLS-TP and MPLS" aka draft-villamizar-mpls-tp-multipath-00.  I
could reference draft-kompella-mpls-entropy-label and make the request
that you put the ELI label in the PATH or RESV message somewhere.

> On a separate note, we intend to update
> draft-kompella-mpls-entropy-label shortly to cover P2MP LSP's (RSVP &
> mLDP), plus add details surrounding labelled BGP and RSVP P2P LSP's so
> that we have a more thorough treatment of all use cases to hopefully
> make all of this more clear.  (In fact, I got a good start on this
> text on this on the plane ride home :-).

OK.  Just try to get the ELI into the PATH or RESV so all LSR on the
PATH can see it.

BTW - There are some implications for facilities FRR.  On the
facilities backup path there is no per LSP PATH or RESV message to
look at to see what value of ELI is being used.  If the facilities
backup path is over multipath (ie: LAG, bundle, or RSVP ECMP), then
the value of ELI will not be known.  This might force detour style FRR
or use of GMPLS path protection (or segemenbt which is more
detour-like).  A fixed ELI would help here too (allowing bypass FRR).

> -shane

Maybe we should continue offline and then go back to the list.

Curtis
_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls

Greg Mirsky | 2 Aug 2010 18:12
Picon

Re: [PWE3] ELI as a reserved label


Dear Curtis,
interestingly, I was thinking of possible implications of EL and multipath in FRR Facility backup network.
You wrote:
BTW - There are some implications for facilities FRR.  On the
facilities backup path there is no per LSP PATH or RESV message to
look at to see what value of ELI is being used.  If the facilities
backup path is over multipath (ie: LAG, bundle, or RSVP ECMP), then
the value of ELI will not be known.  This might force detour style FRR
or use of GMPLS path protection (or segement which is more
detour-like).  A fixed ELI would help here too (allowing bypass FRR).

If the protected link is LAG or Link bundle, then I think it is more likly that LSPs will get squeezed as BW shrinks. Thus it might be not a local protection but restoration that will be playing in.
Another scenario, a singleton link protected by a path that has LAG or Link Bundle in it. I think that it would be up to local policy of the particular PLR to signal use of EL on the bypass tunnel regardless of whether EL been used on any of protected LSPs.

Regards,
Greg
_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls
John E Drake | 2 Aug 2010 22:58
Favicon

Re: [PWE3] ELI as a reserved label

Hi,

I think there is a misunderstanding.  EL support is loosely coupled  
between the ingress and egress and intermediate nodes have no  
knowledge of its usage.   Further, the ELI is normally *not* present.   
The normal mode of operation is for the egress to see a label for  
which it is expecting to see BOS set.  The fact that it isn't tells  
the egress that an EL is present.

ELI is for IPv4/6 forwarding where there is no label in which to check  
for BOS not being set.  Effectively, the ELI becomes that label.

This renders any transit router usage of an ELI with a reserved value  
moot since most of the time it won't be there.

Wrt p2mp, we cannot add either an EL or a reserved value ELI unless  
*all* receivers have indicated that they can receive it.

Thanks,

John

Sent from my iPhone

On Aug 2, 2010, at 10:18 AM, "Curtis Villamizar" <curtis <at> occnc.com>  
wrote:

>
> In message <8B7721F4-8C12-4C88-9036-B19592BE686E <at> castlepoint.net>
> Shane Amante writes:
>>
>> Hi Curtis,
>>
>> I had some time to think about this some more on the plane ride home.
>> See below.
>>
>> On Jul 30, 2010, at 14:02 GMT+02:00, Curtis Villamizar wrote:
>>> In message <0DEFA7EF-8DC4-4EF2-ABDF-0404FC32B992 <at> castlepoint.net>
>>> Shane Amante writes:
>>>>
>>>> Curtis,
>>>>
>>>> On Jul 30, 2010, at 11:06 GMT+02:00, Curtis Villamizar wrote:
>>>>> The Entropy Label Indicator (ELI) is called for in
>>>>> draft-kompella-mpls-entropy-label-01.txt
>>>>>
>>>>> After brief discussion with Stewart and with Kireeti and Lucy  
>>>>> Yong,
>>>>> there were three uses of ELI that would benefit from making the  
>>>>> ELI a
>>>>> reserved label.  It may be premature to make any such request  
>>>>> and the
>>>>> remaining reserved label number space is sparse, so this will be
>>>>> floated as a separate draft, and put on hold awaiting  
>>>>> advancement of
>>>>> the drafts that depend on it.
>>>>>
>>>>> The three benefits of making ELI a reserved label are in:
>>>>>
>>>>> 1.  Extending any use of entropy-label to P2MP (where there are
>>>>>    multiple egress and the possibility of each egress requiring a
>>>>>    separate entropy label value is problematic for the ingress).
>>>>>
>>>>> 2.  Extending any use of entropy-label to any arbitrary position  
>>>>> in
>>>>>    the label stack such that in an aggregation LSP with aggregates
>>>>>    both MPLS-TP and MPLS LSP, load split on the MPLS LSPs is
>>>>>    simplified and not impacted by limiting label stack depth for
>>>>>    the MPLS-TP LSPs.  This is when label stack hash is limited to
>>>>>    support MPLS-TP as proposed in
>>>>>    draft-villamizar-mpls-tp-multipath-00.txt .
>>>>
>>>> I agree there are benefits to a reserved label for the above two
>>>> applications.  Most importantly, a receiving node would have pretty
>>>> clearly semantics that what [immediately] follows a reserved ELI is
>>>> the entropy-label, regardless of where the ELI is in the MPLS label
>>>> stack and without needing to be in the signaling path to know  
>>>> what is
>>>> the ELI value.
>>>
>>> "Now don't be sad ... 'cause two out of three aint bad".  [meatloaf]
>>>
>>> Its good to hear that you consider these to be useful.
>>>
>>> Note that an ingress LSR still needs to determine that egress LSR
>>> understands ELI to do anything.  To support MPLS-TP in MPLS the
>>> ingress needs to veryify that all LSR on the path support MPLS in a
>>> way that provides a compliant path for a contained TP LSP, but  
>>> that is
>>> out of scope of this discussion.
>>
>> I need to revise my statements wrt entropy-labels and P2MP LSP's.
>> After thinking about this some more, I no longer believe it makes
>> sense to use a reserved ELI value for P2MP LSP's.  More specifically,
>> for a given P2MP LSP, all receivers /MUST/ agree to receive entropy
>> labels, because it would be silly to (for example) expect core LSR's
>> to strip-off the ELI and an entropy-label mid-flight toward receivers
>> that don't understand (or, can't receive) entropy-labels.  The
>> ramifications of this are that if a head-end detects any receivers of
>> a P2MP LSP that can't receive entropy-labels, then the head-end
>> LER/LSR must either: a) re-signal the whole P2MP LSP toward all
>> receivers so that the head-end will not send any entropy-labels at  
>> all
>> on the P2MP LSP; or, b) signal 2 separate P2MP LSP's: one for
>> entropy-label capable receivers and a second for non-entropy-label
>> capable receivers.  I don't know that we want to mandate one of those
>> two behaviors over the other, because SP's may make separate choices
>> depending on whether they want to avoid extra replication in the
>> network at the expense of not being able to do flow-based
>> load-balancing, i.e.: Option (a), or don't mind the extra replication
>> of (potentially) 2 parallel P2MP trees on the same links in order to
>> attain some amount of flow-based load-balancing of the P2MP traffic.
>
> The use of a reserved label doesn't remove the requirement to figure
> out if the egress can support ELI.  It just removes the requirement to
> put a separate ELI label on for each egress.
>
> If some P2MP paths don't need to load balance (no multipath on that
> leg) but other paths do, as long as all egress can support ELI, then
> at worst it is 8 bytes of overhead that some paths don't need.
>
> I don't see an alternative for P2MP in your paragraph above.  Are the
> branch points assumed to selectively add a different ELI (or none) and
> should branch point remove ELI and the entropy label if ELI is not
> needed downstream or to the next branch point?  Would this be a lot
> more complicated with different values of ELI per egress (and possibly
> also per branch point)?
>
>> So, in summary, I no longer see that draft-kompella-mpls-entropy- 
>> label
>> has a requirement for reserved labels for either P2P or P2MP LSP's
>> (scenario 1 in your original e-mail).  Furthermore, I still maintain
>> that discussion of LFC and use of the MPLS TC field for indication of
>> large vs. small flows is orthogonal to
>> draft-kompella-mpls-entropy-label (scenario 3 in your original
>> e-mail).  I haven't read draft-villamizar-mpls-tp-multipath-00
>> (scenario 2 in your original e-mail) so I can't speak to whether or
>> not there is a requirement for a reserved label there.
>
> OK.
>
>> Anyway, perhaps this will save you some time in that you don't need  
>> to
>> write a whole new draft as you originally proposed and, instead, may
>> only need to look at modifying your original draft.  :-)
>
> For load balance to work with stack limited, then all midpoints would
> need to know what ELI was being used.
>
> This is a bit like each P2MP needing to know which ELI is needed
> downstream of it, but not quite as bad.
>
> OTOH, putting the ELI that is being used on a P2P LSP in the PATH or
> RESV message for that P2P LSP would solve this for "Use of Multipath
> with MPLS-TP and MPLS" aka draft-villamizar-mpls-tp-multipath-00.  I
> could reference draft-kompella-mpls-entropy-label and make the request
> that you put the ELI label in the PATH or RESV message somewhere.
>
>> On a separate note, we intend to update
>> draft-kompella-mpls-entropy-label shortly to cover P2MP LSP's (RSVP &
>> mLDP), plus add details surrounding labelled BGP and RSVP P2P LSP's  
>> so
>> that we have a more thorough treatment of all use cases to hopefully
>> make all of this more clear.  (In fact, I got a good start on this
>> text on this on the plane ride home :-).
>
> OK.  Just try to get the ELI into the PATH or RESV so all LSR on the
> PATH can see it.
>
> BTW - There are some implications for facilities FRR.  On the
> facilities backup path there is no per LSP PATH or RESV message to
> look at to see what value of ELI is being used.  If the facilities
> backup path is over multipath (ie: LAG, bundle, or RSVP ECMP), then
> the value of ELI will not be known.  This might force detour style FRR
> or use of GMPLS path protection (or segemenbt which is more
> detour-like).  A fixed ELI would help here too (allowing bypass FRR).
>
>> -shane
>
> Maybe we should continue offline and then go back to the list.
>
> Curtis
> _______________________________________________
> pwe3 mailing list
> pwe3 <at> ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls

Curtis Villamizar | 3 Aug 2010 02:03

Re: [PWE3] ELI as a reserved label


In message <AANLkTi=WNbHxa-k+DE34DD4fKudMcgQbvcVuNno8GU0m <at> mail.gmail.com>
Greg Mirsky writes:
>
>
> Dear Curtis,
>
> interestingly, I was thinking of possible implications of EL and
> multipath in FRR Facility backup network.
>
> You wrote:
>
>   BTW - There are some implications for facilities FRR.  On the
>   facilities backup path there is no per LSP PATH or RESV message to
>   look at to see what value of ELI is being used.  If the facilities
>   backup path is over multipath (ie: LAG, bundle, or RSVP ECMP), then
>   the value of ELI will not be known.  This might force detour style
>   FRR or use of GMPLS path protection (or segement which is more
>   detour-like).  A fixed ELI would help here too (allowing bypass
>   FRR).
>
> If the protected link is LAG or Link bundle, then I think it is more
> likly that LSPs will get squeezed as BW shrinks. Thus it might be not
> a local protection but restoration that will be playing in.  Another
> scenario, a singleton link protected by a path that has LAG or Link
> Bundle in it. I think that it would be up to local policy of the
> particular PLR to signal use of EL on the bypass tunnel regardless of
> whether EL been used on any of protected LSPs.
>
> Regards,
> Greg

Greg,

I would imagine that in networks where LAG (or link bundle or ECMP) is
important, EL would be enabled anywhere that it could be supported
except in outer tiers where capacity was small enough that single
links only were needed.

Curtis
_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls


Gmane