RE: WGLC for BFD over Link Aggregate Group Interfaces - ends November 8

["Bhatia, Manav (Manav)" <[e-mail]>]

Hi Mahesh,

> I do not know about you, but when I read interface there are specific
> implications in my mind of what it means. To a certain extent I can see
> that is in this response from Manav. It means something very specific.
> 
> On Oct 27, 2013, at 4:37 AM, Bhatia, Manav (Manav) wrote:
> 
> > Can you explain the scenario where you think its not possible for a
> system to know the ifindex of the IP interface over which an incoming
> packet arrived?

I had given a general comment in response to your email where you had said that its not possible for systems to be aware of the interface a control packet arrives on.

This draft *never* talks about the ifindex. All we're saying is that when you get a uBFD packet you should somehow know which interface and member port of the LAG the packet arrived on. How you do that is an implementation specific issue and will NEVER affect interoperability. 

I don't understand why we're discussing an implementation specific issue that has no bearing on interoperability.

> 
> My point is that if you believe that by "interface information" you do
> not necessarily mean the interface (ifIndex) itself or that it is a
> fairly generic reference to an identification of a member link of LAG,
> then just say so. Or better still, say what it should mean. What is

Can you point to the text in the draft that gives you the impression that we are talking about an "ifIndex"? 

Cheers, Manav

> wrong with being more clear? If I mis-read what was meant, so will
> others.
> 
> Cheers.
> 
> Mahesh Jethanandani
> [e-mail]
> 
>