[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: About using LMP for Address translation



Hi Amit,

> > Below are the steps involved in signaling:
> >
> > - When a PATH message is received with a ERO(containing data plane
> > hops) the outgoing PATH message should be double IP encapsulated.
> > The top IP header destination should be TE router Id of the data next
> > hop.
>
> 1. See above for double encapsulation.
>
> 2. The use of the TE Router ID here is the basis for the debate.
> The authors of the addressing draft are suggesting that the use of the
> TE Router ID provides a well-known and stable routable control plane
> address and are suggesting that its use be RECOMMENDED.
> Dimitri has pointed out that *any* control plane address is adequate but
> that it is sensible to use a stable routable control plane address.
>
> <Amit> TE Router Id is the only common IP shared by Data and control
> plane. If we have to use anyother control plane IP, then resolving the
> TE-Link to Control plane IP(using TEDB) would be a bit impossible. As
> TEDB will most probably have TE router Id info, and no any other control
> plane IP.

I like "a bit impossible" :-)
If the information is not in the TED, then you clearly can't use the TED.
However, the information can be deduced from IGP advertisements.
Further, it could come from other sources.

No-one is saying that you MUST use a different address.
Dimitiri is just saying that there is no reason to prohibit the use of
another address.


> > - Once the TE Router ID has been determined, the RSVP message can be
> > sent out (based on the routing table entry for the data next hop TE
> > Router ID) through the control channel.
>
> Basically right, but I'd pick up on a few of your words. You say "based
> on the routing table entry for the data next hop TE Router ID" and this
may
> be confusing. I think what you mean is "based on the (control plane)
> routing table entry for the TE Router ID of the data next hop".
>
> <Amit> According to me, routing table is necessary only for Control
> Plane network in case of out-of-band signaling.

You are welcome to hold that opinion.

Adrian