Support as a co-author.  Not aware of any IPR.  This solution provides 
efficient multicast delivery if multicast support in the underlay cannot be 
used or is undesirable.

Wen

From: BESS <[email protected]<mailto:[email protected]>> on behalf of 
Ravi Shekhar <[email protected]<mailto:[email protected]>>
Date: Sunday, January 31, 2016 at 12:30 PM
To: Aldrin Isaac <[email protected]<mailto:[email protected]>>
Cc: "EXT - [email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>, 
"[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, 
"[email protected]<mailto:[email protected]>"
 
<[email protected]<mailto:[email protected]>>
Subject: Re: [bess] Poll for adoption: draft-rabadan-bess-evpn-optimized-ir-02


Support as co-author. A solution without percolating multicast forwarding state 
on every device in the core or edge is very desirable. Not aware of any IPR.

- Ravi Shekhar.

On Jan 31, 2016 8:48 AM, Aldrin Isaac 
<[email protected]<mailto:[email protected]>> wrote:
Support as co-author. IETF should adopt this use-case -- optimized 
multi-destination forwarding for overlays where multicast support is not 
available in the underlay. I am not aware of any related IPR.

On Tue, Jan 26, 2016 at 12:12 AM Thomas Morin 
<[email protected]<mailto:[email protected]>> wrote:
Hello working group,

This email starts a two-week poll on adopting
draft-rabadan-bess-evpn-optimized-ir-02 [1] as a working group item.

Please send comments to the list and state if you support adoption or
not (in the later case, please also state the reasons).

This poll runs until **February 9th**.


*Coincidentally*, we are also polling for knowledge of any IPR that
applies to this draft, to ensure that IPR has been disclosed in
compliance with IETF IPR rules (see RFCs 3979, 4879, 3669
and 5378 for more details).

==> *If* you are listed as a document author or contributor please
respond to this email and indicate whether or not you are aware of any
relevant IPR.

The draft will not be adopted until a response has been received from
each author and contributor.

If you are not listed as an author or contributor, then please
explicitly respond only if you are aware of any IPR that has not yet
been disclosed in conformance with IETF rules.

Thank you,

Martin & Thomas
bess chairs

[1] https://tools.ietf.org/html/draft-rabadan-bess-evpn-optimized-ir-02













_______________________________________________
BESS mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/bess
_______________________________________________
BESS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bess

Reply via email to