The MPLS WG Archive
[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index]
mplsTunnelEntry index
-
From: abhay <abhay@multitech.co.in>
-
Date: Mon, 16 Jul 2001 18:42:08 +0530
-
CC: Koling Chang <koling@kchang.net>, mpls@UU.NET, cheenu@alphion.com, arun@force10networks.com
Hi Tom
I see what you mean,implementations keep changing for the better,;).
Regards,
Abhay
"Thomas D. Nadeau" wrote:
At 09:51 AM 7/16/2001 +0530, abhay wrote:
>Hi,
>
> There are two sides of the coin here.Walking through
the T.E MIB
> requires Chang's indexing idea
>
> But to have a LSP Management with the T.E MIB we can
have the original
> order of indices as mentioned
>
> by the authors.One way to achieve this is by actually
having Ingress
> Based Pointers to the original
>
> Tunnel Table Entries in the MIB.In this way,we
can get the specified
> management functionality and also
>
> satisfy the indices rules in the MIB.
>
> Moreover,the RSVP / CR-LDP Signaling protocols have a
small
> difference,the difference being the
>
> tunnel instance.So,if one is having both CR-LDP and RSVP
operating in a
> disjoint manner ,we may not
>
> consider how we have the Tunnel head configuration.
>
> As I understand that Cisco's implementation has a source
address NULL
> or zero to identify tunnel
>
> head configurations.
No, we follow the paradigm
I described earlier where the
tunnelInstance set to 0 to signify the head interface.
--Tom
| |
|