The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2001-Feb> msg00258



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

LSP control mode of peer...

  • From: Abhijit <gabhijit@ee.iitb.ernet.in>
  • Date: Thu, 22 Feb 2001 22:56:18 +0530 (IST)
  • cc: mpls@UU.NET
  • X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by cell.onecall.net id MAA22634


amar,

I think its not at all necessary to know the Downstream Label Distribution
Control Mode. If thats what u r asking.. An LSR acting as Ru will never
mind whether the bindings it receives is independent or ordered as long as
it receives them . (However its a job of Downstream LSR to suppply
bindings properly.) 

perhaps following diagram might help.

   Ru........ Rd1.........Rd2

consider things at Rd1
PushConditional/unConditional depends upon whether after receiving request
from Ru1(Assuming Ru is reqWhenNeeded and ingress) Rd1 should distribute
binding to Ru1 independently (pushUnconditional) or only if it has
received it from Rd2(pushConditional -- assuming all conditions in 5.1.1.
are met.) So its not at all needed by Ru1 to know the Control mode of
Rd1..

However if Rd1 chooses to use pushConditional with requestNever with
Downsteam on Demand mode (thr' misconfiguration probably) ( READ
specifically section 5.2.3 of rfc3031), then its in serious problems as
it will never request anything but is expecting a mapping from downstream.

Hope it is clear

-abhijit

On Thu, 22 Feb 2001, Amarnath Honnavalli Anantharamaiah wrote:

>Hi vijay,
>
>Given a combination of upstream LSR (Ru) and downstream LSR (Rd) -
>Distribution procedure is Downstream's distribution procedure & Request
>procedure is upstreams. Hence in the combination below,
><PushUnConditional, RequestWhenNeeded, RequestNoRetry,ReleaseOnChange,
>*> Distribution procedure represents donwstream ' distribution procedure
>and Request Procedure is Upstream.
>
>Am I wrong ?
>
>The above conclution is made from the mpls architechture draft (or RFC)
>5.1.1 Downstream LSR: Distribution Procedure
>5.1.2 Upstream LSR: Request Procedure
>
>Regards
>Amar
>
>Vijayanand Chandrasekar wrote:
>
>>  Amar,This information is needed for configuring the LSRs' on what
>> schemes WE support. For example PushConditional means Unsolicited
>> Ordered control is used by us when we distribute labels as a
>> downstream.It is not what is used ny our downstream.Your question is
>> why you are not allowed to use -  (PushUnCond)UnsolicitedIndependent
>> with (RWN)Conservative .Unsolicited Independent and Conservative are
>> not used in combination,You can look at the mail archives for this.The
>> question should not be not whether ur downstream is ordered or
>> independent? Vijay
>>
>>      -----Original Message-----
>>      From: Amarnath Honnavalli Anantharamaiah
>>      [mailto:amarnath.honnavalli@wipro.com]
>>      Sent: Thursday, February 22, 2001 5:39 PM
>>      To: Vijayanand Chandrasekar
>>      Cc: Bob Thomas
>>      Subject: Re: LSP control mode of peer...
>>
>>      Vijay,
>>
>>      [1] No, basically question was,  From the list of valid
>>      schemes supported  for  merge capable LSR, we don't find
>>      this combination.
>>      <PushUnConditional, RequestWhenNeeded,
>>      RequestNoRetry,ReleaseOnChange, *>
>>       however we can find the following combination
>>      <PushConditional, RequestWhenNeeded,
>>      RequestNoRetry,ReleaseOnChange, *>
>>
>>      Now, how do we know if downstream is PushConditional or
>>      PushUnconditional ???
>>
>>      [2] If this is not needed to know, Why is this combination
>>      given in the list ?
>>
>>      Regards
>>      Amar
>>
>>      Vijayanand Chandrasekar wrote:
>>
>>     > Vinay,I don't think you need to know whether your
>>     > downstream is Ordered or Independent. You need to just
>>     > know if it is Ondemand or Unsolicited. Regards,Vijay
>>     >
>>     >      -----Original Message-----
>>     >      From: owner-mpls@UU.NET
>>     >      [mailto:owner-mpls@UU.NET]On Behalf Of Vinay
>>     >      Vernekar
>>     >      Sent: Thursday, February 22, 2001 1:41 PM
>>     >      To: 'mpls@uu.net'
>>     >      Subject: LSP control mode of peer...
>>     >      Hello,I have a query which came up when
>>     >      implementing the LDP as in rfc3036 - "LDP
>>     >      Specification", keeping in mind the MPLS
>>     >      architecture as given be rfc3031.As discussed in
>>     >      rfc3031 - 5.2.1. Schemes for LSRs that Support
>>     >      Label Merging -If Ru and Rd are label
>>     >      distribution peers, and both support
>>     >      labelmerging one of the supported scheme is - 3.
>>     >      <PushConditional, RequestWhenNeeded,
>>     >      RequestNoRetry,ReleaseOnChange, *>This implies
>>     >      that the label retention mode of the upstream
>>     >      can be conservative given that the downstream is
>>     >      operating in Unsolicited label distribution mode
>>     >      and its LSP control mode is Ordered. But how can
>>     >      the LSP control mode of the peer be determined?
>>     >      This is not available in any of the LDP
>>     >      messages/TLVs. Thanks &
>>     >      RegardsVinay~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>     >
>>     >      Yesterday is history. Tomorrow is mystery.
>>     >      Today is a gift. That’s why it’s called the
>>     >      Present!!
>>     >
>>     >      ****************************************************************************
>>     >
>>     >      Vinay H. Vernekar
>>     >      Sr. Software Engineer - Global R&D Solutions
>>     >      Wipro Technologies
>>     >      No.26, Hosur Main Road, Bommanahalli,
>>     >      Bangalore-560 068, India.
>>     >
>>     >      ****************************************************************************
>>     >
>