Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-mvpn-fast-failover

Hi Working Group, First of all many thanks to Rob and Greg who did all the most for the last iterations of this drafts. On 22/11/2018 08:54, stephane.litkow...@orange.com wrote: If you are listed as an Author or a Contributor of this Document please respond to this email and indicate whether

Re: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with Ingress Replication

> Don ; Marco Marzetti > Cc: bess@ietf.org > Subject: RE: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with Ingress > Replication > > Thomas, > > I completely agree w/ your email, below. > > Yours Irrespectively, > > John > > > > -Original Message

Re: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with Ingress Replication

-Thomas > From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Marco Marzetti > Sent: Thursday, December 14, 2017 9:21 AM > To: Thomas Morin > Cc: bess@ietf.org > Subject: Re: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with Ingress > Replication > > Hello, >

Re: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with Ingress Replication

Hi Marco, Marco Marzetti, 2017-12-14 12:25: > I am writing this email asking you to clarify what's the suggested > behavior when PMSI Tunnel Type is set to "Ingress Replication" (type > 6) as draft-ietf-bess-evpn-overlay-10 only suggests what to do with > multicast tunnel trees. > > I think the or

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

Ali, A few nits, sorry for not answering earlier: > > I added the following paragraph to section 6 for clarification: > “When a PE advertises multiple supported encapsulations, it MUST > advertise encapsulations that use the same EVPN procedures including > procedures associated with split-hori

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

Ali Sajassi (sajassi), 2017-12-08 03:01: > M8.2. These should also be Normative: RFC7348, NVGRE, VXLAN- > > GPE, RFC4023 > > > > [Ali] Please refer to Thomas explanation on this which is copied > > here for your convenience: > > “My process fu is weakening, but if this specification is standard >

Re: [bess] A question about Tunnel Identifier in PMSI Tunnel Attribute etc.

Hi Tsuno, (below) Hiroshi Tsunoda, 2017-08-08 22:20: > > a) Format and examples of Tunnel Identifier in PMSI Tunnel Attribute > >    L2L3-VPN-MCAST-TC-MIB provides a textual convention >    (L2L3VpnMcastProviderTunnelId) representing >    the Tunnel Identifier of a P-tunnel. > >    a-1) I woul

[bess] WG Last Call for draft-ietf-bess-mvpn-expl-track

Hello Working Group, This email starts a Working Group Last Call on draft-ietf-bess-mvpn-expl-track-02 [1] which is considered mature and ready for a final working group review. Please read this document if you haven't read the most recent version yet, and send your comments to the list, no

[bess] Adoption of draft-sajassi-bess-evpn-igmp-mld-proxy (was Re: Call for adoption: draft-sajassi-bess-evpn-igmp-mld-proxy-01 (extended to Feb 23))

ith a revision ? Many thanks! -Thomas 2017-02-09, Thomas Morin: Hi working group, Given the two IPR disclosures made very recently [1], this call is extended to close on February 23rd. -Thomas [1] https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-sajassi-bess-evpn-igmp-

[bess] Call for adoption: draft-sajassi-bess-evpn-igmp-mld-proxy-01 (extended to Feb 23)

Hi working group, Given the two IPR disclosures made very recently [1], this call is extended to close on February 23rd. -Thomas [1] https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-sajassi-bess-evpn-igmp-mld-proxy

[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 **Febr

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

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" mailto:thomas.mo...@orange.com>> wrote: Hi John, Thanks for the extra information. Just to make sure: do we have a comm

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

--- 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 Referenc

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

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 info

[bess] early allocation of evpn route type 5 (was Re: FW: New Version Notification for draft-surajk-evpn-access-security-00.txt)

Hi Jorge, It sounds a lot like we should register an early allocation for route type 5 ? As the editor of draft-ietf-bess-evpn-prefix-advertisement , would you be ok to bootstrap the early allocation process [1] ? Thi

Re: [bess] shepherd review of draft-ietf-bess-evpn-etree

in order to alleviate additional configuration overhead associated with "to alleviate additional configuration overhead associated with ..." -> "to alleviate the configuration overhead associated with ..." ? using two RTs per EVI at the expense of having un

Re: [bess] shepherd review of draft-ietf-bess-evpn-etree

Hi Ali, 2016-12-13, Ali Sajassi (sajassi): 2016-12-10, Ali Sajassi (sajassi): Your suggestion regarding multiple MAC-VRFs per EVI for E-TREE, impacts lot more sections than just section 2.2 for which you suggested some texts. It drastically impacts section 3.1 (known unicast traffic), and i

Re: [bess] shepherd review of draft-ietf-bess-evpn-etree

Hi Ali, 2016-12-10, Ali Sajassi (sajassi): Your suggestion regarding multiple MAC-VRFs per EVI for E-TREE, impacts lot more sections than just section 2.2 for which you suggested some texts. It drastically impacts section 3.1 (known unicast traffic), and it also impacts section 3.2 (BUM traff

[bess] WGLC on one addition in draft-ietf-bess-evpn-overlay-07

Hi working group, draft-ietf-bess-evpn-overlay-07 has just been published with a new section on "Unknown Unicast Traffic Designation". This email starts a one week Last Call, for comments specific to this new section, to close on December 8th. Thanks, -Thomas internet-dra...@ietf.org :

Re: [bess] Comments on draft-ietf-bess-evpn-overlay-05.txt

. Thanks, -Thomas On 11/14/16, 6:20 AM, "Thomas Morin" wrote: Hi Ali, 2016-11-11, Ali Sajassi (sajassi): Here are a two comments on the changes in draft-ietf-bess-evpn-overlay-05: 5.1.3 Constructing EVPN BGP Routes In EVPN, an MPLS label identifying forwarding table is dist

Re: [bess] Comments on draft-ietf-bess-evpn-overlay-05.txt

Hi Ali, 2016-11-11, Ali Sajassi (sajassi): Here are a two comments on the changes in draft-ietf-bess-evpn-overlay-05: 5.1.3 Constructing EVPN BGP Routes In EVPN, an MPLS label identifying forwarding table is distributed by "identifying forwarding table" was inserted above in -05 Is the

[bess] Comments on draft-ietf-bess-evpn-overlay-05.txt

Hi authors of draft-ietf-bess-evpn-overlay, Here are a two comments on the changes in draft-ietf-bess-evpn-overlay-05: 5.1.3 Constructing EVPN BGP Routes In EVPN, an MPLS label identifying forwarding table is distributed by "identifying forwarding table" was inserted above in -05 Is the

[bess] IMPORTANT: please resend your slots requests for BESS WG session - IETF 97 - Seoul !

Hi everyone, You need to resend your request for a slot (unless the WG or Thomas were Cc'd in your initial email). The reason behind this is that Martin's PC suffered from a crash today. With our apologies for the inconvenience and for being late to post an agenda... Thomas/Martin Martin

Re: [bess] Poll for adoption: draft-rabadan-bess-evpn-ac-df

Hi everyone, We have a new WG document. Authors, can you please repost as draft-ietf-bess-evpn-ac-df-00 ? Thanks in advance, -Thomas/Martin 2016-08-30, Thomas Morin: Hello working group, This email starts a two-week poll on adopting draft-rabadan-bess-evpn-ac-df-05 [1] as a Working Group

[bess] Adopted: draft-dhjain-bess-bgp-l3vpn-yang-02 ! (was Re: Call for adoption: draft-dhjain-bess-bgp-l3vpn-yang-01)

Hi working group, draft-dhjain-bess-bgp-l3vpn-yang is adopted as a working group document. Can authors please repost as **draft-ietf-bess-l3vpn-yang-00** ? Thanks, -Thomas 2016-08-16, Thomas Morin: Hello working group, This email starts a two-week poll on adopting draft-dhjain-bess-bgp

Re: [bess] shepherd review of draft-ietf-bess-evpn-etree

Hi Ali, Thanks for the quick respin, which covers many of the points. (inlined below, skipping the resolved points) 2016-09-02, Ali Sajassi (sajassi): sites albeit for different EVIs. +-++-+ | PE1 || PE

[bess] Poll for adoption: draft-rabadan-bess-evpn-ac-df

Hello working group, This email starts a two-week poll on adopting draft-rabadan-bess-evpn-ac-df-05 [1] as a Working Group document. Please state on the list if you support adoption or not (in both cases, please also state the reasons). This poll runs until *September 14th*. We are also poll

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-overlay

Hi working group, authors, A quick update on draft-ietf-bess-evpn-overlay, as mentioned during BESS meeting in Berlin: - the door for comments is still open to have more reviews on this important document - reminder to authors: the outcome of the discussion right before/during WGLC haven't yet

Re: [bess] shepherd review of draft-ietf-bess-evpn-etree

My previous email was missing comments on the References section... 9 References 9.1 Normative References [KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC7432] Sajassi et al., "BGP MPLS Based Etherne

[bess] shepherd review of draft-ietf-bess-evpn-etree

Hi, Here is the review I did while preparing the shepherd write-up for draft-ietf-bess-evpn-etree . There is one thing that stands out: the document uses the most significant bit of the "PMSI Tunnel Attribute" Tunnel Type field, which cant't be done I think without updating the structure of

Re: [bess] draft minutes from our session at IETF 96

Hi Greg, I've just uploaded updated minutes to address your comment. Best, -Thomas, as WG co-chair 2016-07-26, Greg Mirsky: Hi Thomas, et. al, my note is regarding the presentation and the discussion of draft-ietf-bess-mvpn-fast-failover. Minutes state "some discussion on BFD boostraping an

[bess] Call for adoption: draft-dhjain-bess-bgp-l3vpn-yang-01

Hello working group, This email starts a two-week poll on adopting draft-dhjain-bess-bgp-l3vpn-yang [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 **August 30th**

Re: [bess] Poll for adoption: draft-boutros-bess-vxlan-evpn-01

Hi everyone, As announced during Berlin meeting, considering the small support base, this document is not adopted. We will consider doing a call for adoption again when/if we hear more about the actual needs for such a solution. Thomas/Martin 2016-06-20, Thomas Morin: Hello working

Re: [bess] still no slides for bess Berlin

Speakers, We are still missing 3 of the slide decks: draft-anshuverma-bess-vpls-best-site-id-02 10min, Anshu draft-zzhang-bess-mvpn-evpn-cmcast-enhancements-00 20min, Jeffrey draft-sajassi-bess-evpn-igmp-mld-proxy-00 10min, Ali Please post your slides tomorrow... Best, -Thomas 17/07/2016 à

[bess] Fwd: [IANA #915440] Early allocation request - draft-ietf-bess-evpn-optimized-ir

--- Begin Message --- Hi all, IANA has made the following early allocations under the Border Gateway Protocol (BGP) Parameters heading at http://www.iana.org/assignments/bgp-parameters: 1) In the P-Multicast Service Interface Tunnel (PMSI Tunnel) Tunnel Types registry, IANA has registered the

Re: [bess] Slots requests for BESS WG session - IETF 96 - Berlin

Patrice Brissette (pbrisset) : Please set me for Yang again. !0 min for L2VPN, EVPN and L3VPN. Well, implicitly we already assume slots requests are about non-zero time duration *. ;-) Typo joke aside, can you tell if you want 10 mins per draft, or if you plan to cover them all in one 10-m

Re: [bess] draft-ietf-bess-evpn-overlay / section 5.1.3 vs. section 9 (was Re: [Idr] draft-ietf-bess-evpn-overlay vs. draft-ietf-idr-tunnel-encaps)

Sounds good. Thanks, -Thomas 2016-06-15, John E Drake: Thomas, Comments inline. Yours Irrespectively, John -Original Message- From: Thomas Morin [mailto:thomas.mo...@orange.com] Sent: Wednesday, June 15, 2016 8:47 AM To: John E Drake; Rabadan, Jorge (Nokia - US); BESS; draft

[bess] draft-ietf-bess-evpn-overlay / section 5.1.3 vs. section 9 (was Re: [Idr] draft-ietf-bess-evpn-overlay vs. draft-ietf-idr-tunnel-encaps)

Hi John, Ali, Through the discussion below it appeared that section 9 and section 5.1.3 needed adjustments to be brought in sync, and indeed there were some changes in last revision. However, I don't think the cleanup/precision is complete yet: - section 5.1.3 says "the MPLS label field in th

Re: [bess] [Idr] draft-ietf-bess-evpn-overlay vs. draft-ietf-idr-tunnel-encaps

Hi Ali, The changes in -04 look good. I would have one suggestion: say explicitly that the "use the label as the VNI" behavior is the same as what the tunnel encap says. This could be done by adding something like the following to section 5.1.3 : Note that the procedure defined here to u

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

f flag SHOULD be set to 0 but ignored by the receiving routers. Therefore, why not set it to 1 to be consistent the MAC/IP route case? Because the flag is used for known unicast traffic and Leaf label for BUM traffic. We don¹t want to mix the two. Cheers, Ali Thanks. Jeffrey -Original

[bess] draft-shah-bess-l2vpn-yang is adopted (was Re: Poll for adoption: draft-shah-bess-l2vpn-yang)

thors and list everyone else in a "Contributors" section. Best, -Thomas 2016-05-04, Thomas Morin: Hello working group, This email starts a two-week poll on adopting draft-shah-bess-l2vpn-yang [1] as a working group document. Please state on the list if you support adoption or not

[bess] draft-brissette-bess-evpn-yang is adopted (was Re: Poll for adoption: draft-brissette-bess-evpn-yang)

Hi everyone, We have consensus for this draft to become a BESS WG document. Authors can you please repost as draft-ietf-bess-evpn-yang-00 with the agreed changes ? Best, -Thomas Thomas Morin : Hello working group, This email starts a two-week poll on adopting draft-brissette-bess-evpn

Re: [bess] [Idr] draft-ietf-bess-evpn-overlay vs. draft-ietf-idr-tunnel-encaps

eals > quite nicely with this situation. Of course we can deal with less-than-ideal... it doesn't mean we can't anticipate and do better. -Thomas *From:*Thomas Morin [mailto:thomas.mo...@orange.com] *Sent:* Wednesday, May 18, 2016 10:23 AM *To:* John E Drake; IDR; BESS;

Re: [bess] [Idr] draft-ietf-bess-evpn-overlay vs. draft-ietf-idr-tunnel-encaps

John, 2016-05-18, John E Drake: I spoke with Ali and he will reference the tunnel encapsulation draft rather than RFC 5512 but make it Informative. I think this is in the spirit of what you proposed in your email, below. Well, only for some definition of "in the spirit"... :-/ What I think w

[bess] Fwd: [IANA #907843] General Request for Assignment (bgp-extended-communities - draft-ietf-bess-service-chaining)

of the registry and the registrations' values and descriptions should be added to the document's IANA Considerations section. Best regards, Amanda Baber IANA Senior Specialist ICANN On Mon May 09 13:56:11 2016, thomas.mo...@orange.com wrote: > > Contact Name: > Thomas Morin

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

Hi Jorge, all, Jorge: 11) IANA considerations: the authors have agreed to request the value ‘4’ for the Extended Community Sub-Type, since there are existing implementations using that value. Note that given the FCFS policy of this part of the registry [1], you could ask for this value now

[bess] Poll for adoption: draft-shah-bess-l2vpn-yang

Hello working group, This email starts a two-week poll on adopting draft-shah-bess-l2vpn-yang [1] as a working group document. Please state on the list if you support adoption or not (in both cases, please also state the reasons). This poll runs until *May 25th*. This call runs in parallel w

[bess] Poll for adoption: draft-brissette-bess-evpn-yang

Hello working group, This email starts a two-week poll on adopting draft-brissette-bess-evpn-yang [1] as a working group document. Please state on the list if you support adoption or not (in both cases, please also state the reasons). This poll runs until *May 25th*. This call runs in parall

Re: [bess] draft-ietf-bess-evpn-overlay vs. draft-ietf-idr-tunnel-encaps

or VSID from a Label in a PMSI Tunnel Attribute and have draft-ietf-bess-evpn-overlay follow that. I understand that the existence of implementation makes this hard to change. ] -Thomas 2016-05-04, Thomas Morin: Hi, There are minor things that could be improved in draft-ietf-bess-evpn

[bess] draft-ietf-bess-evpn-overlay vs. draft-ietf-idr-tunnel-encaps

Hi, There are minor things that could be improved in draft-ietf-bess-evpn-overlay wrt. consistency with draft-ietf-idr-tunnel-encaps : * since draft-ietf-idr-tunnel-encaps will deprecate RFC5512, it would be better that draft-ietf-bess-evpn-overlay refers to draft-ietf-idr-tunnel-encaps and

Re: [bess] minutes of our IETF 95 meeting

dd my response to comments from Keyur and Wim: 4PE routers need IPv4 next hop information to install their IPv4 routing table. Thanks and Best Regards, li_zhenqi...@hotmail.com *From:* Thomas Morin <mailto:thomas.mo...@or

[bess] minutes of our IETF 95 meeting

Hi everyone, We have just posted draft minutes for today's meeting. You can read them at https://www.ietf.org/proceedings/95/minutes/minutes-95-bess Please send any comments you may have on these minutes. Many many thanks to Gunter for his minute taking! -Thomas/Martin

Re: [bess] IETF 95 meeting, *draft* agenda

The agenda posted below is the final agenda. Thank you, See you the next in Buenos Aires! -Thomas 2016-03-22, Thomas Morin: Hi everyone We've just posted the **draft** agenda (still subject to changes) for our meeting in Buenos Aires: https://www.ietf.org/proceedings/95/agenda/agen

Re: [bess] Ref: Call for adoption: draft-snr-bess-evpn-proxy-arp-nd-02

Hi Erik, Yes indeed, Monday morning Buenos Aires time. "The I-D submission tool will be reopened after 2016-04-03 23:59 ART (IETF-meeting local time). " [1] Best, -Thomas [1] https://datatracker.ietf.org/submit/ 2016-03-31, Erik Nordmark: On 3/30/16 1:52 PM, Thomas Morin

Re: [bess] Ref: Call for adoption: draft-snr-bess-evpn-proxy-arp-nd-02

Hi everyone, This draft is now a BESS working group document. Can authors please resubmit as draft-ietf-bess-evpn-proxy-arp-nd-00 ? Thanks in advance, -Thomas 2016-02-15, Iftekhar Hussain: Support. I have read the draft and found it to provide very useful operational information. Thanks

[bess] IETF 95 meeting, *draft* agenda

Hi everyone We've just posted the **draft** agenda (still subject to changes) for our meeting in Buenos Aires: https://www.ietf.org/proceedings/95/agenda/agenda-95-bess We were not able to accomodate for all requests for time, thank you for your understanding. Best, -Thomas/Martin WG St

Re: [bess] Poll for adoption: draft-fm-bess-service-chaining-02

FYI, the disclosure has been made March 8th: https://datatracker.ietf.org/ipr/2765/ -Thomas Le 07/03/2016 13:35, Martin Vigoureux a écrit : Hello Dhananjaya, thanks for the notice. WG, I'll let this poll run for at least a week after the disclosure is made. For those who have already stated t

[bess] draft-rabadan-bess-evpn-optimized-ir is adopted (was Re: Poll for adoption: draft-rabadan-bess-evpn-optimized-ir-02)

Hi everyone, This draft is now a WG document. Authors, can you please repost as draft-ietf-bess-evpn-optimized-ir ? Thanks, -Thomas 2016-01-26, Thomas Morin: Hello working group, This email starts a two-week poll on adopting draft-rabadan-bess-evpn-optimized-ir-02 [1] as a working group

Re: [bess] AD Review of draft-ietf-bess-multicast-damping-03

Hi Alvaro, Thanks for your very careful review. I may not agree with every comment made, but many will certainly improve the document. See inlined below... Thanks, -Thomas 2016-02-23, Alvaro Retana (aretana): The Abstract says that the procedures are "inspired from BGP unicast route dampi

[bess] Poll for adoption: draft-rabadan-bess-evpn-optimized-ir-02

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 9

[bess] WG Last Call on draft-ietf-bess-evpn-etree

Hello Working Group, This email starts a Working Group Last Call on draft-ietf-bess-evpn-etree [1] which is considered mature and ready for a final working group review. Please read the document if you haven't read the most recent version yet (-03), and send your comments to the list, no lat

Re: [bess] WG Last Call for draft-ietf-bess-pta-flags-01

Martin, Martin Vigoureux : *Coincidentally*, we are also polling for knowledge of any IPR that applies to draft-ietf-bess-multicast-damping, 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

[bess] Closing the call for adoption on draft-hao-bess-inter-nvo3-vpn-optionc

Hi working group, Based on this long discussion following the call for adoption, we consider that there is no consensus at this point to adopt draft-hao-bess-inter-nvo3-vpn-optionc as a working group document. Our understanding is that the problem to address and the different alternatives so

Re: [bess] Introducing a one-implementation requirement before WG last calls

f seriousness of the part of the implementor. Asking for greater commitment at WGLC is (imho) asking too much. Kireeti On Nov 24, 2015, at 01:03, Thomas Morin wrote: Hello everyone, Following the positive feedback received during BESS meeting in Yokohama about introducing a one-implementati

[bess] Introducing a one-implementation requirement before WG last calls

Hello everyone, Following the positive feedback received during BESS meeting in Yokohama about introducing a one-implementation requirement in BESS, we propose to do the following for future WG last calls: As a prerequisite before doing a working group last call on a document, the chairs wil

Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc

dures in draft-hao-bess-inter-nvo3-vpn-optionc based on current vswitch implementations of VXLAN, the lack of MPLS/MPLS/(UDP, GRE) support in commonplace vswitches seems to me as making that alternate solution you suggest harder to implement. WH> I would disagree to this. Tell me which switch/TOR

Re: [bess] Poll for adoption: draft-singh-bess-bgp-vpls-control-flags -> adopted

Hi working group, We have a new working group document. Authors, can you please repost as draft-ietf-bess-bgp-vpls-control-flags ? Thank you, -Thomas/Martin 2015-10-26, Ravi Singh: Hi Thomas, Martin Before adopting this draft, we would like hear people actually experiencing pain related to

Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc

Wim, Henderickx, Wim (Wim) : VXLAN has a dedicated UDP port and is very clear in the RFC7348 Well, having a port reserved for this use that won't be the default for another protocol is one thing, but that does not prevent in itself the same protocol to be applied on another range of ports. (

Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc

Lucy Yong : [Lucy1] Is this one? “If we want to describe a model C VPN interconnect with a IP fabric in a DC I recommend to do an informational RFC that describes this using VXLAN-GPE, MPLSoGRE or MPLSoUDP encapsulation and retain the E2E MPLS label we defined in RFC4364.” If yes, you sugge

Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc

how to implement the procedures in draft-hao-bess-inter-nvo3-vpn-optionc based on current vswitch implementations of VXLAN, the lack of MPLS/MPLS/(UDP, GRE) support in commonplace vswitches seems to me as making that alternate solution you suggest harder to implement. -Thomas

[bess] IDR accepting post-WGLC comments on draft-ietf-idr-rtc-no-rt

Hi working group, draft-ietf-idr-rtc-no-rt has passed working group last call in IDR on June 22th and the shepherd noticed that considering that specs being worked on in BESS are the primary use case, comments from BESS working group could have been solicited. Hence, IDR chairs have proposed

Re: [bess] draft-hao-bess-inter-nvo3-vpn-optionc

Hi Wim, I agree on the analysis that this proposal is restricted to implementations that supports the chosen encap with non-IANA ports (which may be hard to achieve for instance on hardware implementations, as you suggest), or to context where managing multiple IPs would be operationally viab

Re: [bess] One question about 'draft-ietf-bess-evpn-overlay-02'

Hi John, 2015-11-12, John E Drake: Why do you think it should be documented in Eric's draft rather than in the EVPN Overlay draft? The issue applies beyond the context of E-VPN overlay specs, and exist in any context where different kinds of MPLS(/x) encaps can be mixed (E-VPN non-overlay,

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

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

[bess] Agenda for Dallas

Hi everyone, Here is our final agenda for our meeting next week in Dallas (Wednesday, March 25, 9:00-11:30). Note well that all slots include the time for discussing the drafts. Monday 8pm (Dallas local time) is the _deadline_ for presenters to send us their slides, keeping in mind that send

[bess] Draft agenda for Dallas

Hi working group, Here is the draft agenda for our meeting in Dallas, scheduled Wednesday, March 25, 9:00-11:30. Note well that this agenda is still subject to change. Feel free to comment... Best, -Thomas/Martin http://www.ietf.org/pr

Re: [bess] Poll for adoption: draft-sajassi-bess-evpn-etree

Hello working group, This poll is now closed. We consider that strong-enough support to adopt the document has not been expressed at this time. Thank you, -Thomas/Martin 2015-02-02, Thomas Morin : Hello working group, This email starts a two-week poll on adopting draft-sajassi-bess-evpn

Re: [bess] Pete Resnick's No Objection on draft-ietf-l3vpn-acceptown-community-09: (with COMMENT)

Adrian, Pete, 2015-02-05, Adrian Farrel: I looked through the archive. The comments from the contributor were responded to with a polite email explaining how the authors disagreed and why. The contributor (whose original comments were more like "I would do it different") did not follow up, an

Re: [bess] Alia Atlas' Yes on draft-ietf-l3vpn-acceptown-community-09: (with COMMENT)

Hi Alia, Alia Atlas: In Sec 2,2, it says: "This implies that when propagating routes into a VRF, the ACCEPT_OWN community should not be propagated. Likewise, if a route carrying the ACCEPT_OWN community is received in an address family which does not allow the source VRF to be looke

Re: [bess] Stephen Farrell's No Objection on draft-ietf-l3vpn-acceptown-community-09: (with COMMENT)

Hi Stephen, all, Stephen Farrell: - section 6: I think I buy the argument that there are no new security issues here but that's only true I think if the security issues with route reflectors are somewhere (and if those cover cases where crypto is not used to enforce the "P" in VPN). Wouldn't a r

[bess] Poll for adoption: draft-sajassi-bess-evpn-etree

Hello working group, This email starts a two-week poll on adopting draft-sajassi-bess-evpn-etree-00 [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 16th**.

Re: [bess] Poll for adoption: draft-morin-bess-multicast-damping

Hi working group, I'm not aware of any undisclosed IPR related to this draft, and support adoption as a co-author. Best, -Thomas 2015-01-26, Martin Vigoureux: Hello working group, This email starts a two-week poll on adopting draft-morin-bess-multicast-damping [1] as a working group item.

Re: [bess] Poll for adoption: draft-rabadan-bess-dci-evpn-overlay / adopted !

Hi everyone, We have a new working group document. Can authors please re-post as draft-ietf-bess-dci-evpn-overlay ? Best, -Thomas 2014-12-05 14:13, Thomas Morin: Hello working group, This email starts a two-week poll on adopting draft-rabadan-bess-dci-evpn-overlay [1] as a working group

Re: [bess] Poll for adoption: draft-rosen-l3vpn-ir => adopted !

Hi everyone, We have a new working group document. Can authors please repost as draft-ietf-bess-ir-00 ? Best, -Thomas 2014-12-04 17:29, Thomas Morin : Hello working group, This email starts a two-week poll on adopting draft-rosen-l3vpn-ir [1] as a working group item. Please send comments

[bess] WG Last Call for draft-ietf-l3vpn-mvpn-bidir-ingress-replication

Hello working group, This email starts a Working Group Last Call on draft-ietf-l3vpn-mvpn-bidir-ingress-replication, which is considered mature and ready for a working group review. Please read the document if you haven't read the most recent version yet, and send your comments to the list,

Re: [bess] Adoption of draft-boutros-l2vpn-evpn-vpws-04 / adopted

this draft beyond what has already been disclosed. Thanks, Samer On 2014-12-19 1:05 AM, "Thomas Morin" wrote: [initially sent to l2vpn instead of bess] Hi everyone, Before formally adopting this in BESS, we need an answer from each co-author on this recurrent reminder question abou

[bess] Adoption of draft-boutros-l2vpn-evpn-vpws-04

[initially sent to l2vpn instead of bess] Hi everyone, Before formally adopting this in BESS, we need an answer from each co-author on this recurrent reminder question about existing knowledge of any IPR that applies to this draft, to ensure that IPR has been disclosed in compliance with IETF

Re: [bess] WG Last Call for draft-ietf-bess-mvpn-global-table-mcast

Hi everyone, This last call is now ended. We'll move the doc to the IESG as soon as the shepherd review is done. Thanks, -Thomas 2014-11-28, Thomas Morin : Hello working group, This email starts a Working Group Last Call on draft-ietf-bess-mvpn-global-table-mcast [1], which is consi

Re: [bess] Last Call Comment draft-ietf-l3vpn-end-system-04.txt / XML schema registration

Hi IANA, We need to find the right way to choose the URI for the XML schema in this draft, and understand based on RFC3688 that the registry at [1] is the right place. We need to identify whether a URL (like the one currently in the draft: http://www.ietf.org/bgp-l3vpn-unicast.xsd) is suitab

Re: [bess] [IANA #798045] IANA's comments on draft-ietf-l3vpn-end-system

ment has been made to support this draft. The original request for an assignment is below: Contact Name: Thomas Morin Contact Email: thomas.mo...@orange.com Type of Assignment: Assignement of a BGP parameter in a FCFS registry. Registry: BGP Tunnel Encapsulation Attribute Tunnel Types See: h

Re: [bess] [IANA #798045] RE: IANA's comments on draft-ietf-l3vpn-end-system

t; > > IANA's reviewer has the following comments/questions: > > > > IANA has a question about the IANA Considerations section of this document. > > > > Previously, an early assignment has been made to support this draft. The > > original requ

[bess] Poll for adoption: draft-rabadan-bess-dci-evpn-overlay

Hello working group, This email starts a two-week poll on adopting draft-rabadan-bess-dci-evpn-overlay [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 **December 19th*

[bess] Poll for adoption: draft-rosen-l3vpn-ir

Hello working group, This email starts a two-week poll on adopting draft-rosen-l3vpn-ir [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 **December 19th**. *Coincid

Re: [bess] Last Call Comment draft-ietf-l3vpn-end-system-04.txt

Hi Benson, 2014-12-03 19:38, Benson Schliesser: Simple: I agree that it should be relatively straight-forward to fix the namespace issue. While I'm not intimately familiar with it, I think that RFC 3688 describes how the appropriate namespace can be assigned. I'm comfortable describing this as

[bess] WG Last Call for draft-ietf-bess-mvpn-global-table-mcast

Hello working group, This email starts a Working Group Last Call on draft-ietf-bess-mvpn-global-table-mcast [1], which is considered mature and ready for a last working group review. Please read the document if you haven't read the most recent version yet, and send your comments to the list, no

[bess] Draft minutes for our IETF91 sessions

Hi everyone, Draft minutes for our 2 sessions during last IETF are at: http://tools.ietf.org/wg/bess/minutes These minutes where compiled based on the impressively extensive minutes taken by John Scudder, complemented by the minutes taken by Lucy Yong and some notes by chairs. Thanks John an

Re: [bess] Two minor last call comments on draft-ietf-l3vpn-acceptown-community-08.txt

Hi Adrian, Adrian Farrel : - Check whether you really need the pre-RFC5378 boilerplate and remove it if possible This was handled with authors during shepherd review: all agreed to grant appropriate rights, and removal of the boilerplate should be done in the next respin. Best, -Thomas

[bess] Last minute / agenda update for our session on Friday (service chaining)

Hi everyone, We've updated our agenda for tomorrow's session to accommodate for a discussion on service-chaining: Friday, 1150-1320 - Kahili * draft-sajassi-bess-evpn-virtual-eth-segment, Ali, 10' including questions * draft-sajassi-bess-evpn-etree, Ali, 10' including question

[bess] Flowspec for L2VPN and E-VPN

Hi WG, A heads up... These two drafts relate to BESS and thus may be of interest to us: - draft-hao-idr-flowspec-l2vpn (on idr agenda, being presented right now) - draft-hao-idr-flowspec-evpn

[bess] Request for publication of draft-ietf-l3vpn-acceptown-community

IESG, The L3VPN WG requests that draft-ietf-l3vpn-acceptown-community-08 be published as an RFC on the Standard track. The shepherd write-up is in the datatacker [1]. Thank you, -Thomas for the BESS WG [1] https://datatracker.ietf.org/doc/draft-ietf-l3vpn-acceptown-community/shepherdwriteu

  1   2   >