[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: FW: Questions on draft-ietf-mpls-bundle-00
Hi Ed,
I agree, comments below.
Regards,
steve atkinson
> -----Original Message-----
> From: Edward Harrison [mailto:eph@dataconnection.com]
> Sent: Thursday, September 13, 2001 11:06 AM
> To: 'Yakov Rekhter'
> Cc: Nic Larkin; 'ccamp@ops.ietf.org'
> Subject: RE: FW: Questions on draft-ietf-mpls-bundle-00
>
>
> Yakov,
>
> > > Can you clarify whether you are proposing removing the
> COMPONENT_IF_UPSTREAM
> > > TLV from the INTERFACE_ID hop object (or were you just
> saying that Steve
> > > needn't use it if he doesn't want to)?
> >
> > I am proposing to remove the COMPONENT_IF_UPSTREAM.
>
> In this case, am I right in thinking it makes sense to remove
> COMPONENT_IF_DOWNSTREAM too, and signal the (single)
> component interface
> identifier, in the IPv4, IPv6 or IF_INDEX TLV?
This is how I felt it should work. I don't see any additional
value in COMPONENT_IF_DOWNSTREAM that can't be handled by
the IF_INDEX TLV. Both carry the same information, the
unnumbered interface identifier.
>
> We'd be interested to hear if anyone on the mailing list
> finds this approach
> overly restrictive.
>
> Ed.
>
> -----Original Message-----
> From: Yakov Rekhter [mailto:yakov@juniper.net]
> Sent: 13 September 2001 14:58
> To: Edward Harrison
> Cc: 'Yakov Rekhter'; Nic Larkin; 'ccamp@ops.ietf.org'
> Subject: Re: FW: Questions on draft-ietf-mpls-bundle-00
>
>
> Ed,
>
> > Can you clarify whether you are proposing removing the
> COMPONENT_IF_UPSTREAM
> > TLV from the INTERFACE_ID hop object (or were you just
> saying that Steve
> > needn't use it if he doesn't want to)?
>
> I am proposing to remove the COMPONENT_IF_UPSTREAM.
>
> Yakov.
>