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

[Ashesh Mishra <[e-mail]>]

Thanks Marc. Having individual Tx/Rx pair for each member link does make the implementation simpler! 

Regards,
Ashesh

> Date: Fri, 1 Nov 2013 13:29:13 -0700
> From: [e-mail]
> To: [e-mail]
> CC: [e-mail]
> Subject: Re: WGLC for BFD over Link Aggregate Group Interfaces - ends November 8
> 
> Hello Ashesh,
> 
> > the receiving end will have a Rx session for every member of the LAG?
> 
> Yes. You have a sending and a receiving session per LAG member link.
> 
> > If so, how will the session negotiation work with more than one 
> > endpoint on the peer node?
> 
> section 2.2 explains it. Here the part for starting the session:
> 
>    The demultiplexing of a received BFD packet is solely based on the
>    Your Discriminator field, if this field is nonzero.  For the initial
>    Down BFD packets of a BFD session this value MAY be zero.  In this
>    case demultiplexing MUST be based on some combination of other fields
>    which MUST include the interface information of the member link.
> 
> 
> In other words your implementation "binds" a particular Rx/Tx session 
> to one member interface (I use quotation marks to indicate the details 
> are up to your implementation).
> 
> 
> Regards, Marc
> 
> 
> 
> On Fri, 1 Nov 2013 11:58:54 -0700, Ashesh Mishra wrote:
> > Hi all,
> > 
> > Does the mechanism proposed in this draft suggest that the 
> > transmitting end will multicast the BFD CC frames over the LAG and 
> > the receiving end will have a Rx session for every member of the LAG?
> > 
> > If so, how will the session negotiation work with more than one 
> > endpoint on the peer node?
> > 
> > --
> > Ashesh