Re: [bess] New bess WG Co-Chair

[Dolganow, Andrew (Nokia - SG/Singapore)]

Martin, thanks for all the hard work at BESS and all the best in a new role.

Mathew, welcome to BESS

Andrew

From: BESS  on behalf of Alvaro Retana 

Date: Wednesday, February 14, 2018 at 12:11 AM
To: "bess@ietf.org" 
Subject: [bess] New bess WG Co-Chair

Dear bess WG:

As you know, Martin has been selected as a Routing AD starting next month at 
IETF 101 in London.  As a result, he will be stepping down as bess co-chair.  
Martin: thank you for all the work and time you have dedicated to the WG — we 
all look forward to working with you in your new role.  Congratulations!

In consultation with Stephane and the other ADs, we have asked Matthew Bocci to 
take on the role of bess Co-Chair.  Matthew is an experienced Chair (he is also 
the Co-Chair of nvo3, and has served in other WGs) and has been participating 
in the IETF for over a decade.

I am adding Matthew as a third Chair to facilitate the transition.  The 
expectation is that he will fully take over for Martin at IETF 101.  Welcome 
Matthew!

Matthew can be reached at 
matthew.bo...@nokia.com.

Thanks!

Alvaro.

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

[bess] I-D Action: draft-ietf-bess-evpn-irb-mcast-00.txt

[internet-drafts]

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the BGP Enabled ServiceS WG of the IETF.

Title   : EVPN Optimized Inter-Subnet Multicast (OISM) 
Forwarding
Authors : Wen Lin
  Zhaohui Zhang
  John Drake
  Eric C. Rosen
  Jorge Rabadan
  Ali Sajassi
Filename: draft-ietf-bess-evpn-irb-mcast-00.txt
Pages   : 72
Date: 2018-02-13

Abstract:
   Ethernet VPN (EVPN) provides a service that allows a single Local
   Area Network (LAN), i.e., a single IP subnet, to be distributed over
   multiple sites.  The sites are interconnected by an IP or MPLS
   backbone.  Intra-subnet traffic (either unicast or multicast) always
   appears to the endusers to be bridged, even when it is actually
   carried over the IP backbone.  When a single "tenant" owns multiple
   such LANs, EVPN also allows IP unicast traffic to be routed between
   those LANs.  This document specifies new procedures that allow inter-
   subnet IP multicast traffic to be routed among the LANs of a given
   tenant, while still making intra-subnet IP multicast traffic appear
   to be bridged.  These procedures can provide optimal routing of the
   inter-subnet multicast traffic, and do not require any such traffic
   to leave a given router and then reenter that same router.  These
   procedures also accommodate IP multicast traffic that needs to travel
   to or from systems that are outside the EVPN domain.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-irb-mcast/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-bess-evpn-irb-mcast-00
https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-irb-mcast-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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

Re: [bess] New bess WG Co-Chair

[Gaurav Dawra]

Martin, Thanks for all your help and for being great WG Chair on multiple
documents.

Welcome, Matthew!

Cheers,

Gaurav

On Tue, Feb 13, 2018 at 8:11 AM, Alvaro Retana 
wrote:

> Dear bess WG:
>
> As you know, Martin has been selected as a Routing AD starting next month
> at IETF 101 in London.  As a result, he will be stepping down as bess
> co-chair.  Martin: thank you for all the work and time you have dedicated
> to the WG — we all look forward to working with you in your new role.
> Congratulations!
>
> In consultation with Stephane and the other ADs, we have asked Matthew
> Bocci to take on the role of bess Co-Chair.  Matthew is an experienced
> Chair (he is also the Co-Chair of nvo3, and has served in other WGs) and
> has been participating in the IETF for over a decade.
>
> I am adding Matthew as a third Chair to facilitate the transition.  The
> expectation is that he will fully take over for Martin at IETF 101.
> Welcome Matthew!
>
> Matthew can be reached at matthew.bo...@nokia.com.
>
> Thanks!
>
> Alvaro.
>
>
> ___
> 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] New bess WG Co-Chair

[Jeff Tantsura]

Martin - thank for all the great work done!

Matthew – welcome!

 

Cheers,

Jeff

From: BESS  on behalf of Alvaro Retana 

Date: Tuesday, February 13, 2018 at 08:11
To: 
Subject: [bess] New bess WG Co-Chair

 

Dear bess WG:

 

As you know, Martin has been selected as a Routing AD starting next month at 
IETF 101 in London.  As a result, he will be stepping down as bess co-chair.  
Martin: thank you for all the work and time you have dedicated to the WG — we 
all look forward to working with you in your new role.  Congratulations!

 

In consultation with Stephane and the other ADs, we have asked Matthew Bocci to 
take on the role of bess Co-Chair.  Matthew is an experienced Chair (he is also 
the Co-Chair of nvo3, and has served in other WGs) and has been participating 
in the IETF for over a decade.

 

I am adding Matthew as a third Chair to facilitate the transition.  The 
expectation is that he will fully take over for Martin at IETF 101.  Welcome 
Matthew!

 

Matthew can be reached at matthew.bo...@nokia.com.

 

Thanks!

 

Alvaro.

 

___ 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] New bess WG Co-Chair

[Henderickx, Wim (Nokia - BE/Antwerp)]

Thx for all the hard work Martin and enjoy the new endeavour.


From: BESS  on behalf of Jorge Rabadan 

Date: Tuesday, 13 February 2018 at 19:40
To: "Satya Mohanty (satyamoh)" , Ali Sajassi 
, Alvaro Retana , "bess@ietf.org" 

Subject: Re: [bess] New bess WG Co-Chair

+1

Excellent job, Martin, thank you very much for your time and dedication!

Jorge

From: BESS  on behalf of "Satya Mohanty (satyamoh)" 

Date: Tuesday, February 13, 2018 at 7:29 PM
To: "Ali Sajassi (sajassi)" , Alvaro Retana 
, "bess@ietf.org" 
Subject: Re: [bess] New bess WG Co-Chair

Second that.
Thanks Martin for all the work that you undertook while being chair.

Best Regards,
—Satya

From: BESS > on behalf of 
"Ali Sajassi (sajassi)" >
Date: Tuesday, February 13, 2018 at 9:27 AM
To: Alvaro Retana >, 
"bess@ietf.org" >
Subject: Re: [bess] New bess WG Co-Chair


Martin, thank you for all your work and efforts for this WG and reviewing/ 
shepherding many drafts.

Matthew, welcome to BESS.

Cheers,
Ali

From: BESS > on behalf of 
Alvaro Retana >
Date: Tuesday, February 13, 2018 at 8:11 AM
To: "bess@ietf.org" >
Subject: [bess] New bess WG Co-Chair

Dear bess WG:

As you know, Martin has been selected as a Routing AD starting next month at 
IETF 101 in London.  As a result, he will be stepping down as bess co-chair.  
Martin: thank you for all the work and time you have dedicated to the WG — we 
all look forward to working with you in your new role.  Congratulations!

In consultation with Stephane and the other ADs, we have asked Matthew Bocci to 
take on the role of bess Co-Chair.  Matthew is an experienced Chair (he is also 
the Co-Chair of nvo3, and has served in other WGs) and has been participating 
in the IETF for over a decade.

I am adding Matthew as a third Chair to facilitate the transition.  The 
expectation is that he will fully take over for Martin at IETF 101.  Welcome 
Matthew!

Matthew can be reached at 
matthew.bo...@nokia.com.

Thanks!

Alvaro.

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

Re: [bess] Request for WG call for draft-sajassi-bess-evpn-vpws-fxc-02.txt

[Ali Sajassi (sajassi)]

It has already been updated and the rev02 has been checked in.

Regards,
Ali

On 2/13/18, 6:43 AM, "Martin Vigoureux"  wrote:

ok, let us know when you've updated it, we'll call it for adoption fater 
that.

-m

Le 2018-02-13 à 3:50, Ali Sajassi (sajassi) a écrit :
> Hi Martin, Stephane:
> 
> This is one of the draft in my plate that I needed to update and ask for 
> a WG call. It has already been implemented by number of vendors and has 
> had pretty good consensus.
> 
> Regards,
> 
> Ali
> 


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

Re: [bess] New bess WG Co-Chair

[Rabadan, Jorge (Nokia - US/Mountain View)]

+1

Excellent job, Martin, thank you very much for your time and dedication!

Jorge

From: BESS  on behalf of "Satya Mohanty (satyamoh)" 

Date: Tuesday, February 13, 2018 at 7:29 PM
To: "Ali Sajassi (sajassi)" , Alvaro Retana 
, "bess@ietf.org" 
Subject: Re: [bess] New bess WG Co-Chair

Second that.
Thanks Martin for all the work that you undertook while being chair.

Best Regards,
—Satya

From: BESS > on behalf of 
"Ali Sajassi (sajassi)" >
Date: Tuesday, February 13, 2018 at 9:27 AM
To: Alvaro Retana >, 
"bess@ietf.org" >
Subject: Re: [bess] New bess WG Co-Chair


Martin, thank you for all your work and efforts for this WG and reviewing/ 
shepherding many drafts.

Matthew, welcome to BESS.

Cheers,
Ali

From: BESS > on behalf of 
Alvaro Retana >
Date: Tuesday, February 13, 2018 at 8:11 AM
To: "bess@ietf.org" >
Subject: [bess] New bess WG Co-Chair

Dear bess WG:

As you know, Martin has been selected as a Routing AD starting next month at 
IETF 101 in London.  As a result, he will be stepping down as bess co-chair.  
Martin: thank you for all the work and time you have dedicated to the WG — we 
all look forward to working with you in your new role.  Congratulations!

In consultation with Stephane and the other ADs, we have asked Matthew Bocci to 
take on the role of bess Co-Chair.  Matthew is an experienced Chair (he is also 
the Co-Chair of nvo3, and has served in other WGs) and has been participating 
in the IETF for over a decade.

I am adding Matthew as a third Chair to facilitate the transition.  The 
expectation is that he will fully take over for Martin at IETF 101.  Welcome 
Matthew!

Matthew can be reached at 
matthew.bo...@nokia.com.

Thanks!

Alvaro.

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

Re: [bess] New bess WG Co-Chair

[Satya Mohanty (satyamoh)]

Second that.
Thanks Martin for all the work that you undertook while being chair.

Best Regards,
—Satya

From: BESS > on behalf of 
"Ali Sajassi (sajassi)" >
Date: Tuesday, February 13, 2018 at 9:27 AM
To: Alvaro Retana >, 
"bess@ietf.org" >
Subject: Re: [bess] New bess WG Co-Chair


Martin, thank you for all your work and efforts for this WG and reviewing/ 
shepherding many drafts.

Matthew, welcome to BESS.

Cheers,
Ali

From: BESS > on behalf of 
Alvaro Retana >
Date: Tuesday, February 13, 2018 at 8:11 AM
To: "bess@ietf.org" >
Subject: [bess] New bess WG Co-Chair

Dear bess WG:

As you know, Martin has been selected as a Routing AD starting next month at 
IETF 101 in London.  As a result, he will be stepping down as bess co-chair.  
Martin: thank you for all the work and time you have dedicated to the WG — we 
all look forward to working with you in your new role.  Congratulations!

In consultation with Stephane and the other ADs, we have asked Matthew Bocci to 
take on the role of bess Co-Chair.  Matthew is an experienced Chair (he is also 
the Co-Chair of nvo3, and has served in other WGs) and has been participating 
in the IETF for over a decade.

I am adding Matthew as a third Chair to facilitate the transition.  The 
expectation is that he will fully take over for Martin at IETF 101.  Welcome 
Matthew!

Matthew can be reached at 
matthew.bo...@nokia.com.

Thanks!

Alvaro.

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

[bess] AD Review of draft-ietf-bess-evpn-prefix-advertisement-09

[Alvaro Retana]

Dear authors:

I just finished reading this document.  I am glad to finally get to process
it -- thank you for the work!

I do have a long list of comments (see below).  Many of my major ones are
related to the use of Normative Language and some other clarifications,
including places where I think the technology might still be underspecified.

Central to the technology specified in this document is the use of an
Overlay Index.  The use cases make clear the use, but there is no place
where it is discussed what it is (except for "An Overlay Index is a
next-hop that requires a recursive resolution...", which doesn't provide
significant information) or how/when to use it (except for the use cases in
Section 4).   I think the readability would be improved if there was a
section (or paragraph) that explicitly talked about the concept.
Suggestion: put it somewhere in Section 2.1, *before* the name is
introduced ("...associated to an Overlay Index that can be a VA IP address,
a floating IP address, a MAC address or an ESI.").

Thanks!

Alvaro.


Major:

M1. Support for RT-5

M1.1. Section 3 says:

   The support for this new route type is OPTIONAL.

   Since this new route type is OPTIONAL, an implementation not
   supporting it MUST ignore the route, based on the unknown route type
   value, as specified by Section 5.4 in [RFC7606].

(1) I understand what you mean by "OPTIONAL" above -- from an IETF process
point of view it means that you're not formally Updating rfc7432, so EVPN
compliant implementations (according to rfc7432) may not support this new
route.  However, from the point of view of this specification, the support
cannot be optional because otherwise then there would be no point in
writing this document; IOW, if you want to use RT-5, then you MUST support
it.

(2) You cannot specify in this document what implementations not supporting
this specification should do (much less use a MUST to describe that),
because, by definition, those implementations don't know about this
document.  The text above just repeats what rfc7606 already says...so in
reality you seem to be making a statement about backwards compatibility:
nothing bad will happen if an implementation not supporting this
specification receives the new route because of rfc7606.

Suggestion:
NEW>
   According to Section 5.4 in [RFC7606], a node that doesn't recognize the
RT-5 will ignore it.  Add something about backwards compatibility...

[This change would also allow rfc7606 to become an Informative Reference.]

M1.2. I do have a question.  If the operation of the network, for instance
in the case described in 2.2, depends on the RT-5, but a node ignores it
(because it doesn't support it yet), what is the effect?  I'm assuming that
the result will be that none of the routes associated to vIP23 will be
known, so no traffic will be sent to it (even if the ownership is known).
That seems to mean that all nodes (NVEs) MUST support RT-5 for the system
to work, right?  (This relates back to the "OPTIONAL" nature in the text
above.)  Please include this operational consideration somewhere.



M2. Section 3.1 (IP Prefix Route Encoding)

M2.1. "RD, Ethernet Tag ID and MPLS Label fields will be used as defined in
[RFC7432] and [EVPN-OVERLAY]."  Both documents use those fields in
different ways depending on the route type and the application -- you need
to be more specific.  Note also that a couple of bullets later there is a
specification for the MPLS Label field.

M2.1.1. Depending on the specifics, we may need EVPN-OVERLAY to be a
Normative reference.

M2.2. "The IP Prefix will be a 32 or 128-bit field (ipv4 or ipv6). The size
of this field does not depend on the value of the IP Prefix Length field."
 Does that mean that the IP Prefix Length field can be set (for example) to
a number > 32 while the IP Prefix and GW IP Address fields both contain
IPv4 addresses?  That doesn't make sense, but the text currently allows it!

M2.3. BTW, there's nothing in the document that talks about what should be
an error and what do to about them.  An example is the case above...another
one would be if the IP Prefix Length is set to anything > 128...etc.

M2.4. [minor] I noticed that rfc7432 uses IP Address Length/IP Address
instead of IP Prefix Length/IP Prefix...and that the setting and meaning
are slightly different.  For my own education, why the change?  Having
discrete values for the length, for example, seems cleaner and simpler than
a range...

M2.5. [minor] s/GW IP (Gateway IP Address)/GW (Gateway) IP Address field

M2.6. [minor] The figure shows the lengths in octets, but the description
talks about bits for the IP addresses.  Please be consistent.

M2.7. [minor] The figures in 3 and 3.1 don't have names.



M3. Section 3.2 says that "an Overlay Index can be an ESI, IP address in
the address space of the tenant or MAC address".  How do I know which one?
Table 1 provides an answer, but I think there are a couple of
inconsistencies and contradictions...and 

Re: [bess] New bess WG Co-Chair

[Ali Sajassi (sajassi)]

Martin, thank you for all your work and efforts for this WG and reviewing/ 
shepherding many drafts.

Matthew, welcome to BESS.

Cheers,
Ali

From: BESS  on behalf of Alvaro Retana 

Date: Tuesday, February 13, 2018 at 8:11 AM
To: "bess@ietf.org" 
Subject: [bess] New bess WG Co-Chair

Dear bess WG:

As you know, Martin has been selected as a Routing AD starting next month at 
IETF 101 in London.  As a result, he will be stepping down as bess co-chair.  
Martin: thank you for all the work and time you have dedicated to the WG — we 
all look forward to working with you in your new role.  Congratulations!

In consultation with Stephane and the other ADs, we have asked Matthew Bocci to 
take on the role of bess Co-Chair.  Matthew is an experienced Chair (he is also 
the Co-Chair of nvo3, and has served in other WGs) and has been participating 
in the IETF for over a decade.

I am adding Matthew as a third Chair to facilitate the transition.  The 
expectation is that he will fully take over for Martin at IETF 101.  Welcome 
Matthew!

Matthew can be reached at 
matthew.bo...@nokia.com.

Thanks!

Alvaro.

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

[bess] New bess WG Co-Chair

[Alvaro Retana]

Dear bess WG:

As you know, Martin has been selected as a Routing AD starting next month
at IETF 101 in London.  As a result, he will be stepping down as bess
co-chair.  Martin: thank you for all the work and time you have dedicated
to the WG — we all look forward to working with you in your new role.
Congratulations!

In consultation with Stephane and the other ADs, we have asked Matthew
Bocci to take on the role of bess Co-Chair.  Matthew is an experienced
Chair (he is also the Co-Chair of nvo3, and has served in other WGs) and
has been participating in the IETF for over a decade.

I am adding Matthew as a third Chair to facilitate the transition.  The
expectation is that he will fully take over for Martin at IETF 101.
Welcome Matthew!

Matthew can be reached at matthew.bo...@nokia.com.

Thanks!

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

Re: [bess] Request for WG call for draft-sajassi-bess-evpn-vpws-fxc-02.txt

[Martin Vigoureux]

ok, let us know when you've updated it, we'll call it for adoption fater 
that.


-m

Le 2018-02-13 à 3:50, Ali Sajassi (sajassi) a écrit :

Hi Martin, Stephane:

This is one of the draft in my plate that I needed to update and ask for 
a WG call. It has already been implemented by number of vendors and has 
had pretty good consensus.


Regards,

Ali



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

Re: [bess] Call for adoption: draft-lin-bess-evpn-irb-mcast

[Martin Vigoureux]

All,

there is support and all authors have reported back on the list 
regarding the IPR question so we have a new WG doc.


To the authors, could you please republish as 
draft-ietf-bess-evpn-irb-mcast-00?


thank you
M

Le 2018-01-11 à 11:11, Martin Vigoureux a écrit :

Hello working group,

This email starts a two-week call for adoption on 
draft-lin-bess-evpn-irb-mcast-04 [1] as a BESS Working Group Document.


Please state on the list if you support the adoption or not (in both 
cases, please also state the reasons).


This poll runs until *the 26th of January*.

We are also polling for knowledge of any undisclosed IPR that applies
to this Document, 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 an Author or a Contributor of this Document please
respond to this email and indicate whether or not you are aware of any
relevant undisclosed IPR. The Document won't progress without answers
from all the Authors and Contributors.

Currently no IPR has been disclosed against this Document.

If you are not listed as an Author or a 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 & Stéphane
bess chairs

[1] https://datatracker.ietf.org/doc/draft-lin-bess-evpn-irb-mcast/

___
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