The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2001-Jan> msg00014



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

ERO and strict/loose subobject

  • From: Yangguang Xu <xuyg@lucent.com>
  • Date: Wed, 03 Jan 2001 10:52:30 -0500
  • CC: "'mpls@uu.net'" <mpls@UU.NET>
  • Organization: Lucent Technologies, Inc.


> > The "L" bit for a node doesn't mean the node is loose.
> 
> That is exactly what it means.
> 
> > Indeed, the node is
> > strict but the path from preceding node to this node is
> > loose. Am I right?
> >

> If you have a "loose prior abstract node," the address *may* be the previous
> hop in the ERO list.  If you have a "strict prior abstract node," the
> address *must* be the previous hop in the ERO list.
> 
> Bill


Bill,

Because node marked as "loose" can also be interpreted as that the node itself
is not necessary in the ERO. What I am saying is that no matter the abstract
node is marked as loose or strict, it has to be in the ERO, however somewhere
depending on its being loose or strict. 

Thanks,

Yangguang