The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2002-Jul> msg00405



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

AW: AW: AW: initiating a discussion on mpls singaling protocols

  • From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
  • Date: Mon, 29 Jul 2002 17:09:11 +0200
  • Cc: "'MPLS wg'" <mpls@UU.NET>


 


Does this all mean that you are carrying the ER-Hop/ Bandwidth etc from
the egress (root) towards the ingress (head)? Applications?

Bandwidth reservation for all sections of the mp2p merge tree:
It is assumed that the root (egress) knows how much bandwidth is required for the sake of each leaf(ingress).
In compliance with the merging branches, the root may compute the accumulated bandwidth demand for each non-branching tree section. By proper placement of a Nodes-Info-Begin-TLV (which contains the accumulated bandwidth size and also a unique
"sequence number") and of a Nodes-Info-End-TLV (which contains the respective "sequence number" as well), each node 
at the begin, in the middle, and at the end of the particular non-branching tree section will be alerted to make the
appropriate bandwidth reservation.  
Consider some non-branching tree section somewhere in the middle of the tree. The respective TLV-pair will be forwarded
from the root to the nearest node of this section. That nearest node will recognize which child link is of concern, and
will be alerted to make the right bandwidth reservation. The Nodes-Info-Begin-TLV would not be removed before it becomes
placed next to the respective Nodes-Info-End-TLV. I.e. it may alert all the nodes of this section. Thereafter, both TLVs will drop out.



/Sumit