[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ason-routing-reqts: issue 2 architecture
Seems you are all a bit hung up on the definition
of a "router".
Because GMPLS comes from a perspective where an
LSR was a router was a single bearer plane device you are assuming that the
identity advertised it the router id. But really the "TE router id" is the
physical node id (or the logical router id - Ln in my figure).
Stephen has it when he says...
> One instantiation that is possible would be
for R1 in Adrian's diagram to
> advertise on behalf of each of the
P1/P2/P3 nodes, not as one abstract node.
> In that case, it would be
confusing to scope the P1-P2 link using the router
> id of
R1.
This is exactly right. And why would you scope
the P1-P2 link using the router id of R1?
Why not use the node id P1 or the logical router
id L1?
Adrian
>
>
------------------ ------
>
>
|R1
| |R2 |
>
>
| -- -- -- | |
-- | ------
>
> |
|L1| |L2| |L3| | | |L4| |
|R3 |
>
>
| -- -- -- | |
-- | | -- |
>
>
| : : :
| | : | | |L5| |
> >
Control ---+-----+-----+--
---+-- | -- |
> >
Plane
: :
:
: | : |
> >
----------------+-----+-----+----------+------+---+--+-
> >
Data
: :
:
: | : |
> >
Plane
-- :
--
-- | -- |
>
>
----|P1|--------|P3|-------|P4|-----+-|P5|-+-
>
>
-- \ : / --
-- | -- |
>
>
\ --
/
| |
>
>
|P2|
------
>
>
--
> >
> > Pn is a physical (bearer/data/transport plane)
node.
> > Rn is a control plane "router"
> > Ln is a logical
control plane entity that manages a single
> >
physical node.
> >
> > Thus:
> > R3 represents an
LSR with all components collocated.
> > R2 shows how the "router"
component may be disjoint from
> > the switch
>
> R1 shows how a single "router" may manage multiple
switches