Re: [bess] Call for adoption: draft-sajassi-bess-evpn-igmp-mld-proxy-01

2017-01-31 Thread Keyur Patel 
Support as a co-author. I am not aware of any IPR related to this draft.

Regards,
Keyur

On 1/31/17, 1:30 PM, "Ali Sajassi (sajassi)"  wrote:


Support as a co-author. I am not aware of any IPR related to this draft
that hasn¹t already been disclosed.

Regards,
Ali

On 1/31/17, 6:58 AM, "Thomas Morin"  wrote:

>Hello working group,
>
>This email starts a two-week poll on adopting
>draft-sajassi-bess-evpn-igmp-mld-proxy-01 [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 14th**.
>
>*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://datatracker.ietf.org/doc/draft-sajassi-bess-evpn-igmp-mld-proxy-01



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

Re: [bess] Call for adoption: draft-sajassi-bess-evpn-igmp-mld-proxy-01

2017-01-31 Thread Ali Sajassi (sajassi) 

Support as a co-author. I am not aware of any IPR related to this draft
that hasn¹t already been disclosed.

Regards,
Ali

On 1/31/17, 6:58 AM, "Thomas Morin"  wrote:

>Hello working group,
>
>This email starts a two-week poll on adopting
>draft-sajassi-bess-evpn-igmp-mld-proxy-01 [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 14th**.
>
>*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://datatracker.ietf.org/doc/draft-sajassi-bess-evpn-igmp-mld-proxy-01

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

Re: [bess] The BESS WG has placed draft-sajassi-bess-evpn-igmp-mld-proxy in state "Call For Adoption By WG Issued"

2017-01-31 Thread Patrice Brissette (pbrisset) 
I support.
That draft is quite well written and cover an important problem to solve,

Regards,
Patrice Brissette

On 2017-01-31, 9:58 AM, "BESS on behalf of IETF Secretariat" 
 wrote:


The BESS WG has placed draft-sajassi-bess-evpn-igmp-mld-proxy in state 
Call For Adoption By WG Issued (entered by Thomas Morin)

The document is available at
https://datatracker.ietf.org/doc/draft-sajassi-bess-evpn-igmp-mld-proxy/

___
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

Re: [bess] Call for adoption: draft-sajassi-bess-evpn-igmp-mld-proxy-01

2017-01-31 Thread Jeff Tantsura 
Yes/support

 
Cheers,
Jeff
 >> -Original Message-
>> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin
>> Sent: Tuesday, January 31, 2017 9:58 AM
>> To: bess@ietf.org
>> Cc: draft-sajassi-bess-evpn-igmp-mld-pr...@ietf.org
>> Subject: [bess] Call for adoption: 
draft-sajassi-bess-evpn-igmp-mld-proxy-01
>> 
>> Hello working group,
>> 
>> This email starts a two-week poll on adopting
>> draft-sajassi-bess-evpn-igmp-mld-proxy-01 [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 14th**.
>> 
>> *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://datatracker.ietf.org/doc/draft-sajassi-bess-evpn-igmp-mld-proxy-01
>> 
>> ___
>> 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 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

Re: [bess] Call for adoption: draft-sajassi-bess-evpn-igmp-mld-proxy-01

2017-01-31 Thread Sami Boutros 
Support.

Sami

> On Jan 31, 2017, at 7:44 AM, Jeffrey (Zhaohui) Zhang  
> wrote:
> 
> Support.
> 
>> -Original Message-
>> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin
>> Sent: Tuesday, January 31, 2017 9:58 AM
>> To: bess@ietf.org
>> Cc: draft-sajassi-bess-evpn-igmp-mld-pr...@ietf.org
>> Subject: [bess] Call for adoption: draft-sajassi-bess-evpn-igmp-mld-proxy-01
>> 
>> Hello working group,
>> 
>> This email starts a two-week poll on adopting
>> draft-sajassi-bess-evpn-igmp-mld-proxy-01 [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 14th**.
>> 
>> *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://datatracker.ietf.org/doc/draft-sajassi-bess-evpn-igmp-mld-proxy-01
>> 
>> ___
>> 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 mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] The BESS WG has placed draft-sajassi-bess-evpn-igmp-mld-proxy in state "Call For Adoption By WG Issued"

2017-01-31 Thread Ali Sajassi (sajassi) 

Support as a co-author. This draft is targeted to be available in some of
Cisco products this year.

Regards,
Ali

On 1/31/17, 6:58 AM, "IETF Secretariat" 
wrote:

>
>The BESS WG has placed draft-sajassi-bess-evpn-igmp-mld-proxy in state
>Call For Adoption By WG Issued (entered by Thomas Morin)
>
>The document is available at
>https://datatracker.ietf.org/doc/draft-sajassi-bess-evpn-igmp-mld-proxy/
>

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

Re: [bess] Call for adoption: draft-sajassi-bess-evpn-igmp-mld-proxy-01

2017-01-31 Thread Jeffrey (Zhaohui) Zhang 
Support.

> -Original Message-
> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin
> Sent: Tuesday, January 31, 2017 9:58 AM
> To: bess@ietf.org
> Cc: draft-sajassi-bess-evpn-igmp-mld-pr...@ietf.org
> Subject: [bess] Call for adoption: draft-sajassi-bess-evpn-igmp-mld-proxy-01
> 
> Hello working group,
> 
> This email starts a two-week poll on adopting
> draft-sajassi-bess-evpn-igmp-mld-proxy-01 [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 14th**.
> 
> *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://datatracker.ietf.org/doc/draft-sajassi-bess-evpn-igmp-mld-proxy-01
> 
> ___
> 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] The BESS WG has placed draft-sajassi-bess-evpn-igmp-mld-proxy in state "Call For Adoption By WG Issued"

2017-01-31 Thread IETF Secretariat 

The BESS WG has placed draft-sajassi-bess-evpn-igmp-mld-proxy in state 
Call For Adoption By WG Issued (entered by Thomas Morin)

The document is available at
https://datatracker.ietf.org/doc/draft-sajassi-bess-evpn-igmp-mld-proxy/

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

[bess] Call for adoption: draft-sajassi-bess-evpn-igmp-mld-proxy-01

2017-01-31 Thread Thomas Morin 

Hello working group,

This email starts a two-week poll on adopting 
draft-sajassi-bess-evpn-igmp-mld-proxy-01 [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 14th**.

*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://datatracker.ietf.org/doc/draft-sajassi-bess-evpn-igmp-mld-proxy-01


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

[bess] WG feedback on early allocation requests for new EVPN Route types

2017-01-31 Thread Martin Vigoureux 

Dear WG,

we have received early allocation requests from the authors of
draft-ietf-bess-evpn-prefix-advertisement and 
draft-ietf-bess-evpn-bum-procedure-updates: (see details below).


Please let us know if you are aware of any code-point conflict, or
if you have issues with the WG moving forward with this early allocation.

We envisage to proceed with the request on the 6th of February.

Thank you
M

---
"EVPN Route Types" from registry defined by RFC7432
https://www.iana.org/assignments/evpn/evpn.xhtml

5 - IP Prefix route
9 - Per-Region I-PMSI A-D route
   10 - S-PMSI A-D route
   11 - Leaf A-D route
---

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

[bess] Fwd: Re: Request for Assignment of EVPN Route Types

2017-01-31 Thread Thomas Morin 


--- Begin Message ---
Hi Thomas, Martin,

Ali’s request to IANA also included three route types defined in 
https://tools.ietf.org/html/draft-ietf-bess-evpn-bum-procedure-updates-01:

 + 9  - Per-Region I-PMSI A-D route
 + 10 - S-PMSI A-D route
 + 11 - Leaf A-D route

This is in collaboration with authors of other EVPN drafts that involve EVPN 
route types. We believe it satisfies the following requirement:


   c.  The specifications of these code points must be stable; i.e., if

   there is a change, implementations based on the earlier and later

   specifications must be seamlessly interoperable.

We would like to proceed with an early allocation request.

Thanks.
Jeffrey


On 1/18/17, 6:27 AM, "Thomas Morin" 
> wrote:

Hi John,

Thanks for the extra information.

Just to make sure: do we have a common understanding that we need to follow 
RFC7120 for EVPN route types (section 3.1) ?

Assuming so, the first step for asking for early allocation would be 
(separately for each of these drafts) an email from an author/editor to us 
chairs asking for the early allocation (see item 1 in section 3.1 of RFC7120), 
and providing rationale that items (c) of section 2 are met (what you just did 
for type 5 is the info we need).  The answer by chairs or ADs for each of the 
three drafts may end up being different ; i particular because they are not at 
the same stage in the process (e.g. draft-sajassi-bess-evpn-igmp-mld-proxy is 
not even yet a WG document).

Thanks,

-Thomas

2017-01-18, John E Drake:
Thomas,

The email from Ali to IANA is below (I understand that he subsequently amended 
it to include RT-5).  Route types 6, 7, and 8 are defined in:  
https://tools.ietf.org/html/draft-sajassi-bess-evpn-igmp-mld-proxy-01.

Cisco, Juniper, and Nokia have had interoperable implementations of the RT-5 
draft for several years, and all three are currently working on implementations 
of the IGMP Proxy draft mentioned above.

Yours Irrespectively,

John

From: Ali Sajassi (sajassi) [mailto:saja...@cisco.com]
Sent: Wednesday, November 9, 2016 2:04 PM
To: iana-questi...@iana.org
Cc: John E Drake ; Ali Sajassi 
(sajassi) 
Subject: Request for Assignment of EVPN Route Types



Contact Name:
Ali Sajassi

Contact Email:
saja...@cisco.com

Type of Assignment:
EVPN Route Types

Registry:
EVPN Route Types
http://www.iana.org/assignments/evpn/evpn.xhtml#route-types

0x06 - Selective Multicast Ethernet Tag Route
0x07 - IGMP Join Synch Route
0x08 - IGMP Leave Synch Route
0x09 - Per-Region I-PMSI A-D route
0x0A - S-PMSI A-D route
0X0B - Leaf A-D route

Description:
These EVPN route types are defined in the following EVPN drafts and some of 
these drafts are being implemented and thus the immediate need for allocation 
of these code points for the purpose of interoperability:

https://tools.ietf.org/html/draft-sajassi-bess-evpn-igmp-mld-proxy-01
https://www.ietf.org/id/draft-ietf-bess-evpn-bum-procedure-updates-00.txt


Additional Info:
Please refer to the above drafts.


Regards,
Ali



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

[bess] Fwd: Early allocation for EVPN route type 5 - draft-ietf-bess-evpn-prefix-advertisement

2017-01-31 Thread Thomas Morin 


--- Begin Message ---




Dear chairs,
As per RFC7120, and on behalf of my co-authors too, I would like to request an IANA early allocation for an EVPN route type, in particular value 5, as defined in draft-ietf-bess-evpn-prefix-advertisement.
Value 5
Description:   IP Prefix
Reference:    draft-ietf-bess-evpn-prefix-advertisement
 
Thank you!
Jorge



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

[bess] Fwd: Tags changed for draft-ietf-bess-virtual-subnet-fib-reduction

2017-01-31 Thread Thomas Morin 

FYI

-Thomas

--- Begin Message ---

The tags on draft-ietf-bess-virtual-subnet-fib-reduction have been
changed by Thomas Morin:
https://datatracker.ietf.org/doc/draft-ietf-bess-virtual-subnet-fib-reduction/

Tag "Other - see Comment Log" added.



Comment:
One vendor has provided information on intent to implement.
Pending at least an actual implementation this draft is kept on hold.
--- End Message ---
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

[bess] bess - New Meeting Session Request for IETF 98

2017-01-31 Thread "IETF Meeting Session Request Tool" 


A new meeting session request has just been submitted by Thomas Morin, a Chair 
of the bess working group.


-
Working Group Name: BGP Enabled ServiceS
Area Name: Routing Area
Session Requester: Thomas Morin

Number of Sessions: 1
Length of Session(s):  2 Hours
Number of Attendees: 100
Conflicts to Avoid: 
 First Priority: rtgwg spring idr sfc sidr l2sm
 Second Priority: mpls pim nvo3 bier pals
 Third Priority: i2rs


Special Requests:
  
-

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