Re: [bess] draft-morin-bess-mvpn-fast-failover

2015-10-22 Thread Jayant
Besides the below IPR, I am not aware of any other IP related to the draft. 
https://datatracker.ietf.org/ipr/2697/https://datatracker.ietf.org/ipr/2696/
From: kanwar.si...@alcatel-lucent.com
To: bess@ietf.org
Date: Wed, 21 Oct 2015 18:59:20 +
Subject: Re: [bess] draft-morin-bess-mvpn-fast-failover









Beside the below IPR, I am not aware of any other IP related to the draft.
 
https://datatracker.ietf.org/ipr/2697/
https://datatracker.ietf.org/ipr/2696/
 
Thanks,
Kanwar
 


From: BESS [mailto:bess-boun...@ietf.org]
On Behalf Of Henderickx, Wim (Wim)

Sent: Wednesday, October 21, 2015 10:18 AM

To: bess@ietf.org

Subject: Re: [bess] draft-morin-bess-mvpn-fast-failover


 



Besides the below IPR I am not aware of any other IP related to this draft




 



https://datatracker.ietf.org/ipr/2697/


https://datatracker.ietf.org/ipr/2696/






___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess  
  ___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess


[bess] IPR Disclosure Alcatel-Lucent's Statement about IPR related to draft-morin-bess-mvpn-fast-failover

2015-10-22 Thread IETF Secretariat
Dear Thomas Morin, Robert Kebler:


An IPR disclosure that pertains to your Internet-Draft entitled "Multicast
VPN fast upstream failover" (draft-morin-bess-mvpn-fast-failover) was
submitted to the IETF Secretariat on  and has been posted on the "IETF Page of
Intellectual Property Rights Disclosures"
(https://datatracker.ietf.org/ipr/2696/). The title of the IPR disclosure is
"Alcatel-Lucent's Statement about IPR related to
draft-morin-bess-mvpn-fast-failover"


Thank you

IETF Secretariat

___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess


[bess] Comments on "draft-sajassi-bess-evpn-igmp-mld-proxy-00"

2015-10-22 Thread Haoweiguo
Hi Ali,

I have read through the draft, i think the procedures is fine for IGMP/MLD 
proxy. However, this draft doesn't consider multicast router scenario, better 
to be added.

Scenario 1:

 An EVPN PE acts as multicast router and runs PIM protocol with the 
outside multicast routers.

Scenario 2:

 An EVPN PE connects to a multicast router on port1, no IGMP receiver 
on the port.  The PE sends IGMP/MLD to the multicast router.



In both scenarios, the EVPN PE should announce its role through the extended 
route type6 to indicate it connects to a multicast router or acts as multicast 
router itself.

Other EVPN PEs having local multicast source should forward the multicast 
traffic to the PE announcing multicast router role, the PE announcing multicast 
router role should not be pruned for all multicast traffic.

For the PE connecting to a multicast router, it should translate  EVPN route 
type-6 message to IGMP/MLD message, it's already described in your draft. For 
the PE acting as multicast router, it should translate EVPN route type-6 
message to PIM protocol, this part has not been covered in your draft, better 
to be added.



Thanks,

weiguo
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess


[bess] Poll for adoption: draft-hao-bess-inter-nvo3-vpn-optionc

2015-10-22 Thread Thomas Morin

Hello working group,

This email starts a two-week poll on adopting
draft-hao-bess-inter-nvo3-vpn-optionc-03 [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 **November 13th**.
(3 weeks to account for the busy IETF week)


*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-hao-bess-inter-nvo3-vpn-optionc-03



















___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess