Re: [bess] BESS charter [was: Re: John Scudder's Discuss on draft-ietf-bess-bgp-sdwan-usage-20: (with DISCUSS and COMMENT)]

John: IPsec VPNs + IPsec VPN – were part of a discussion from IDR + BESS over the last 2-3 years. You’ll find this comes up with Intent-Based (color) routing as well. In general, we tried to split mechanism to IDR and Usage to BESS. BESS-IDR chair meetings have tried to deal with Glad to

[bess] Genart early review of draft-ietf-bess-evpn-mvpn-seamless-interop-06

Reviewer: Susan Hares Review result: Almost Ready GEN-ART review Status: Almost ready Summary Comment: == Multicast distribution can aid the network, so it is important to have a solid standard. Wow! This is an amazing amount of work to combine EVPN and MVPN. I went between RFC6513

Re: [bess] WG Adoption Poll for draft-ietf-bess-bgp-sdwan-uasge-16

I support the adoption of this draft. Cheerily, Sue Hares From: BESS On Behalf Of Matthew Bocci (Nokia) Sent: Thursday, October 5, 2023 6:45 AM To: bess@ietf.org Cc: draft-ietf-bess-bgp-sdwan-us...@ietf.org Subject: [bess] WG Adoption Poll for draft-ietf-bess-bgp-sdwan-uasge-16 WG This email

Re: [bess] Review of draft-ietf-bess-ebgp-dmz-03

ya Mohanty (satyamoh) Sent: Wednesday, August 2, 2023 12:49 PM To: Susan Hares ; BESS Cc: Andrew Alston Subject: Re: [bess] Review of draft-ietf-bess-ebgp-dmz-03 Hi Sue, Thanks for your comments. Yes, we are in discussion with other vendors regarding link-bandwidth and we will together put a documen

Re: [bess] Appointment of additional WG Chair

Congratulations Jeffrey! Sue Hares ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess

[bess] Review of draft-ietf-bess-ebgp-dmz-03

Sue Full text draft-ietf-bess-ebgp-dmz-03 IDR Chair review Reviewer: Susan Hares Issues with this draft: 1. Protocol Content Four drafts deal with link bandwidth for a BGP router passed in an extended communities attribute or the entropy attribute outside of BGP-LS reporting. a) draft-iet

[bess] FW: Request for BESS WG feedback on adoption call for draft-zzhang-idr-rt-derived-community-03.txt (1/20 to 2/3)

Greetings: The IDR WG did a call for draft-zzhang-idr-rt-derived-community-03.txt. https://mailarchive.ietf.org/arch/msg/idr/uwY3Hdrk2ned2hqMimpB6alhd9U/ We have received a lite support and no objections. The IDR chairs are inclined to adopt this draft, but we would like feedback from the BESS

[bess] Request for BESS WG feedback on adoption call for draft-zzhang-idr-rt-derived-community-03.txt (1/20 to 2/3)

Greetings: The IDR WG did a call for draft-zzhang-idr-rt-derived-community-03.txt. https://mailarchive.ietf.org/arch/msg/idr/uwY3Hdrk2ned2hqMimpB6alhd9U/ We have received a lite support and no objections. The IDR chairs are inclined to adopt this draft, but we would like feedback from the BESS

[bess] FW: IDR Interim on 10/13/2022

IDR will hold an interim on 10/13/2022 - 10:00-12:30 ET Topics: 1. CAR CT (60 minutes) 1.1 CAR-CT interoperability a) draft-haas-idr-bgp-diffract (Jeff Haas) b) CAR-CT interoperability (Keyur Patel) 1.2 Updates on color proposals CAR, CT, and draft-wang-idr-cpr-00 1.3) update on requirements

[bess] IDR Interim on 10/13/2022

IDR will hold an interim on 10/13/2022 - 10:00-12:30 ET Topics: 1. CAR CT (60 minutes) 1.1 CAR-CT interoperability a) draft-haas-idr-bgp-diffract (Jeff Haas) b) CAR-CT interoperability (Keyur Patel) 1.2 Updates on color proposals CAR, CT, and draft-wang-idr-cpr-00 1.3) update on requirements

Re: [bess] Adoption call for CAR/CT drafts (7/6 to 7/20/2022) - Please help us

. Would it be helpful to you and other BESS WG members, if I posted my weekly summaries of the discussion to the list? Thank you, Sue From: Santosh P K Sent: Monday, July 18, 2022 9:27 AM To: Susan Hares Cc: bess@ietf.org; idr-cha...@ietf.org Subject: Re: [bess] Adoption call for CAR/CT drafts

Re: [bess] [Pals] [EXTERNAL] Re: [spring] Martini Pseudowires and SR

Gyan: IDR WG have also adopted draft-ietf-idr-sr-p2mp-policy-00 Jeffrey Zhang has joined as co-author. Work is undergoing in the author group To help align it to other work. It will be WG LC in IDR and BESS. Cheers, Sue From:

[bess] Adoption call for CAR/CT drafts (7/6 to 7/20/2022) - Please help us

BESS: Today we started the WG adoption call for the the CAR/CT drafts. This adoption call has the following two parts: Part-1: Questions on technology direction https://mailarchive.ietf.org/arch/msg/idr/FhoK04HsSy9tR7ioV7AD0Vv6Ir4/ Part-2: Adoption of the drafts

[bess] FW: Call for publication of draft-ietf-idr-segment-routing-te-policy-18 - with multiple partial implementations (6/17 to 6/30)

dr-cha...@ietf.org<mailto:idr-cha...@ietf.org>). Cheers, Sue - From: Susan Hares Sent: Friday, June 17, 2022 9:15 AM To: i...@ietf.org<mailto:i...@ietf.org> Subject: Call for publication of draft-ietf-idr-segment-routing-te-policy-18 - with multiple partial imp

[bess] FW: WG adoption call for draft-chen-idr-bier-te-path-04.txt (6/22/2022 to 7/6/2022

directly to the bess chairs. The IDR Chairs will be checking with the bess chairs prior to finalizing the adoption of this attribute. Cheers, Sue Hares (IDR co-chair, document shepherd) From: Susan Hares Sent: Wednesday, June 22, 2022 12:05 PM To: i...@ietf.org Subject: WG adoption call for draft

[bess] FW: Call for publication of draft-ietf-idr-segment-routing-te-policy-18 - with multiple partial implementations (6/17 to 6/30)

below) to determine whether the IDR WG should publish with partial implementations. We welcome comments on the IDR mail thread, and Implementers may add details to the implementation report. Thank you, Sue Hares From: Susan Hares Sent: Friday, June 17, 2022 9:15 AM To: i...@ietf.org Subject

Re: [bess] [Idr] draft-hb-idr-sr-p2mp-policy (3/10 to 3/24/2022) - Adoption call - Consensus reached

The IDR has reached consensus to adopt draft-hb-idr-sr-p2mp-policy-05.txt. The authors should submit the draft as draft-ietf-idr-sr-p2mp-00.txt. The draft will be adopted into IDR, and the authors will work with the authors of draft-bess-multicast-controller-09.txt to create unique draft for

Re: [bess] [Idr] draft-hb-idr-sr-p2mp-policy (3/10 to 3/24/2022) - Adoption call

Jeffrey: The assumptions in the following email: https://mailarchive.ietf.org/arch/msg/idr/KObeSgKPu3HRbd0ZN7L7fWq_Eto/ are based on past assumptions. The BESS, IDR, and PIM WG Chairs have agreed to a joint WG adoptions to gain input from these 3 WGs into cohesive solutions.

Re: [bess] [Idr] draft-hb-idr-sr-p2mp-policy (3/10 to 3/24/2022) - Adoption call - Extended to 4/8/2022

on 4/8/2022. Sue Hares From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Gyan Mishra Sent: Tuesday, March 29, 2022 10:31 AM To: Jeffrey (Zhaohui) Zhang Cc: i...@ietf.org; p...@ietf.org; Bidgoli, Hooman (Nokia - CA/Ottawa); BESS; Susan Hares Subject: Re: [bess] [Idr] draft-hb-idr-sr

Re: [bess] [Idr] FW: Review of draft-ietf-bess-evpn-ipvpn-interworking-05.txt

h for your review! We've just published rev 06 which addresses some of your comments. Please see below in-line with [jorge]. Thanks. Jorge From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Susan Hares Sent: Tuesday, July 27, 2021 12:19 PM To: <mailto:bess@ietf.org> bess@ietf.org

[bess] IDR review of BESS drafts

The IDR chairs keep a wiki page listing the drafts BESS has requested feedback on the IDR wiki: https://trac.ietf.org/trac/idr/wiki The page for BESS reviews is: https://trac.ietf.org/trac/idr/wiki/Feedback%20for%20BESS%20drafts We have 3 drafts on this list:

Re: [bess] [Idr] FW: Review of draft-ietf-bess-evpn-ipvpn-interworking-05.txt

Jorge: Thank you for the ping! I apologize that I missed your email. I will respond your email later today. Please note this is a personal review since no-one responded to your draft on the idr mail list. (7/27/2021) - my initial draft

[bess] draft-hb-idr-sr-p2mp-policy (3/10 to 3/24/2022)

? Cheers, Susan Hares ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess

Re: [bess] IPR call for draft-dskc-bess-bgp-car-03 (3/4 to 3/10) - Prior to adoption of CAR/CT solutions

for a discussion on these drafts. After all IPR statements have been submitted and the IETF 113 discussion, we will start the formal adoption call. Cheers, Sue From: Susan Hares [mailto:sha...@ndzh.com] Sent: Monday, March 7, 2022 8:33 AM To: 'Dhananjaya Rao (dhrao)' Cc: spring

Re: [bess] IPR call for draft-dskc-bess-bgp-car-03 (3/4 to 3/10) - Prior to adoption of CAR/CT solutions

Dhananjaya: Your request at the IDR interim is sufficient. Thank you for your query. Sue From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Dhananjaya Rao (dhrao) Sent: Monday, March 7, 2022 7:03 AM To: Susan Hares; bess@ietf.org; i...@ietf.org Cc: spring-cha...@ietf.org

[bess] IPR call for draft-dskc-bess-bgp-car-03 (3/4 to 3/10) - Prior to adoption of CAR/CT solutions

Greetings Bess and IDR: The IDR chairs request that each of the authors of draft-dskc-bess-bgp-car-03.txt. submit an IPR statement in response to this email. The motivation for this IPR call is below. We expect IPR responses from the authors: Dhananjaya Rao, Swadesh Agrawal,

Re: [bess] [Idr] Review request for draft-ietf-bess-srv6-services-11

Matthew: Thank you for extending the deadline. Sue From: Idr [mailto:idr-boun...@ietf.org] On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Friday, February 18, 2022 3:05 PM To: i...@ietf.org Cc: ; draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: Re: [Idr] Review request

[bess] IDR interims - 8/23, 9/13, 9/27, 10/11

-encapsulation-label-stack Each draft will be allotted 15-20 minutes for a longer discussion. Authors of drafts may request a time slot to present. If bess chairs or WG has concerns regarding overlap on these drafts. Cheerily, Susan Hares ___ BESS

Re: [bess] [Idr] 2 Week WG LC on draft-ietf-idr-rfc7752bis (7/9/2021 to 7/25/2021) - WG call concluded

. If the bess or spring working groups know of any errors, please send message to the IDR work and/or contact the idr chairs. Cheerily, Susan Hares ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess

[bess] Review of draft-ietf-bess-evpn-ipvpn-interworking-05.txt

Bess chairs reminded me that IDR WG was requested at IETF 110 to review draft-ietf-bess-evpn-ipvpn-interworking-05.txt. Since we did not receive reviews from the IDR WG, the IDR chairs have taken on the task of reviewing this document. Full review is at:

[bess] IDR WG last call for draft-ietf-idr-bgp-ext-com-registry-01 (3/11 to 3/25/2021)

This begins a 2 week WG last call for draft-ietf-idr-bgp-ext-com-registry-01 from 3/11 to 3/25. You can find the draft at: https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ext-com-registry/ This draft suggest a cleanup on several BGP Extended Community registries in order to

Re: [bess] Shepherd's Review of draft-ietf-bess-evpn-pref-df

Luc Andre: I’m pleased to see your issue of tie-breaking that pushes for specific order and definitions in the DF election. I also would suggest you have a mandated algorithm and define whether policy change this mandatory algorithm. Since you are in the middle of defining the

Re: [bess] [Idr] IETF 109 draft idr agenda

Acee: Linda’s started out in IDR as a replacement of IP-Sec tunnels for Tunnel encapsulation. The Application draft for SDWAN is in BESS. Due to the shorten meeting time, I recommended to Linda and her co-authors to only do the mechanism presentation in either BESS or IDR. I

Re: [bess] IPSec Tunnels and draft-sajassi-bess-secure-evpn

...@juniper.net] Sent: Sunday, August 2, 2020 11:37 AM To: Rabadan, Jorge (Nokia - US/Mountain View); Ali Sajassi (sajassi); Susan Hares; bess@ietf.org; i...@ietf.org Cc: Hu, Jun (Nokia - US/Mountain View) Subject: RE: [bess] IPSec Tunnels and draft-sajassi-bess-secure-evpn Hi, I also agree

Re: [bess] IPSec Tunnels and draft-sajassi-bess-secure-evpn

] [Shepherd hat on] I will await the authors response to your queries on EVPN. [Shepherd hat off] Thank you for bring up the EVPN related issues. Cheerily, Susan Hares From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Rabadan, Jorge (Nokia - US/Mountain View) Sent: Saturday, August

Re: [bess] IPSec Tunnels and draft-sajassi-bess-secure-evpn - tunnel encapsulation draft

. It is inappropriate as a shepherd to speak for the authors until they do the first review. [shepherd hat off] Thank you for bringing up potential issues with the draft-ietf-tunnel-encapsulation-17.txt. Cheerily, Susan Hares From: Ali Sajassi (sajassi) [mailto:saja...@cisco.com

Re: [bess] IPSec Tunnels and draft-sajassi-bess-secure-evpn

:54 AM To: Susan Hares; bess@ietf.org; i...@ietf.org Cc: 'Hu, Jun (Nokia - US/Mountain View)' Subject: Re: IPSec Tunnels and draft-sajassi-bess-secure-evpn Sue, Before getting to the discussions of the three IPsec proposals, there are some elements of draft-ietf-idr-tunnel-encaps-

[bess] IPSec Tunnels and draft-sajassi-bess-secure-evpn

Ali and bess WG: IDR has 3 proposals for IPsec tunnels that impact draft-ietf-idr-tunnel-encaps-17.txt. As an IDR co-chair/shepherd, I have been discussing these three drafts (Ali and two other authors sets) to try to find out if we can have one general solutions. The discussion has

Re: [bess] Why are you specifying two new tunnel types for encapsulation for EVPN?

ess-secure-evpn-03.txt RFC6514 – PMSI Tunnel Attribute (PMSI) Cheerily, Sue From: Ali Sajassi (sajassi) [mailto:saja...@cisco.com] Sent: Tuesday, July 28, 2020 9:45 AM To: Susan Hares; bess@ietf.org Subject: Re: [bess] Why are you specifying two new tunnel types for encapsulation for E

[bess] Why are you specifying two new tunnel types for encapsulation for EVPN?

Ali: >From draft-sajassi-bess-secure-evpn: 6 BGP Encoding This document defines two new Tunnel Types along with its associated sub-TLVs for The Tunnel Encapsulation Attribute [TUNNEL-ENCAP

Re: [bess] WG adoption and IPR poll for draft-dunbar-bess-bgp-sdwan-usage-07

Support adoption. Read draft and sent comments to authors. Sue Hares From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Huaimo Chen Sent: Wednesday, June 24, 2020 10:59 AM To: slitkows.i...@gmail.com; bess@ietf.org Hello, This email begins a two-weeks WG adoption poll for

Re: [bess] IGMP / MLD Proxy Draft update (NLRI change)

John - Thank you for reminding folks of RFC7120. It exists due to lots of past pain Bess WG Please go toward the new code point scenario John Scudder describes and RFC7120 recommends. If at some point changes that are not backward compatible are nonetheless required, a

Re: [bess] [Idr] Seeking feedback of draft-dunbar-idr-sdwan-port-safi using SDWAN SAFI to encode SDWAN Instance ID in the NLRI

Gyan: +1 to Roberts comments.Robert, Linda and I have taken this topic off line. If you are interested, ping. Sue From: Idr [mailto:idr-boun...@ietf.org] On Behalf Of Gyan Mishra Sent: Tuesday, March 31, 2020 9:52 PM To: Robert Raszuk Cc: i...@ietf.org; Linda Dunbar; Huaimo

Re: [bess] [Idr] draft-ietf-idr-capabilities-registry-change-05.txt - WG LC []6/9/2019 to 6/16/2019] - extending this for a 3rd week (7/8 to 7/15)

like to send additional comments (support/no support), please continue to send these comments. Alvaro and the IESG read these lists to see how strong the consensus is on documents. Sue Hares From: Idr [mailto:idr-boun...@ietf.org] On Behalf Of Susan Hares Sent: Monday, July 8, 2019

Re: [bess] per VRF RD vs per address family RD

Qin: Please compare the BESS L3VPN Yang data model with the base BGP model handling of AFI/SAFI. Sue From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Qin Wu Sent: Thursday, July 25, 2019 2:23 PM To: bess@ietf.org; draft-ietf-bess-l3vpn-yang@ietf.org Subject: [bess] per VRF

Re: [bess] miss import and export policy within routing-policy under vpn-target

Qin: Just to make sure I have the context, the "BGP model" is the draft-bess-l3vpn-yang-draft or the base BGP protocol model? Sue From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Qin Wu Sent: Thursday, July 25, 2019 2:36 PM To: bess@ietf.org Cc:

[bess] backward compatibility issues - draft-boutros-bess-evpn-geneve

Bess Chair (Matthew and Stephane) If we are going forward to the Tunnel Encapsulation attribute, we need to consider whether we should send to RFC new work with the Encapsulation Extended Community. Otherwise, we are locked into the functionality of the Encapsulation Extended

[bess] [Idr] Next hop encoding - IDR list poll

parsed correctly. If it would help you to collect this to have this information in an web format that could be clicked through in less than 5 minutes, please let me know. I can put up a snappy web form at www.surveymonkey.com. Cheerily, Susan Hares

Re: [bess] [Idr] Can we have the IPSEC related drafts discussion before Friday during IETF 105?

:25 PM To: Paul Wouters Cc: i...@ietf.org; Linda Dunbar; bess@ietf.org; Susan Hares Subject: Re: [Idr] Can we have the IPSEC related drafts discussion before Friday during IETF 105? Me too. If it doesn’t collide with ACME, I2NSF, LAKE, IPSECME, or TLS I’m around. > On 1 Jul 2019, at 21:14, P

[bess] Issue 1: IPSEC related drafts

be requested as IDR or ISE draft. This email has two request: .. WG or authors please send any questions to Susan Hares, .. The IDR WG is encouraged to discuss requirements or needs in preparation for the TLV selection, and .. Please help me secure 2 IPSEC experts

Re: [bess] Poll to progress draft-ietf-bess-nsh-bgp-controlplane without implementation

Stephane: [RFC5575bis author hat on] In progressing the draft without an implementation, please review carefully to the error handling text that Adrian just added. Sue From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of stephane.litkow...@orange.com Sent: Tuesday, April 23,

Re: [bess] 答复: [I2nsf] 答复: [IPsec] using BGP signaling to achieve IPsec Tunnel configuration (draft-hujun-idr-bgp-ipsec): potential conflict with the I2NSF's Controller facilitated IPsec configuration

To: 'Susan Hares'; 'Alvaro Retana' Cc: rtg-...@ietf.org; i...@ietf.org; i2rs-cha...@ietf.org; bess@ietf.org Subject: Re: [bess] 答复: [I2nsf] 答复: [IPsec] using BGP signaling to achieve IPsec Tunnel configuration (draft-hujun-idr-bgp-ipsec): potential conflict with the I2NSF's Controller facilitated

Re: [bess] 答复: [I2nsf] 答复: [IPsec] using BGP signaling to achieve IPsec Tunnel configuration (draft-hujun-idr-bgp-ipsec): potential conflict with the I2NSF's Controller facilitated IPsec configuration

Alvaro: Can we set a date to discuss the IP sec tunnels? Do you want to talk as routing chairs before we include the IPSEC and I2NSF chairs? Sue Hares From: Alvaro Retana [mailto:aretana.i...@gmail.com] Sent: Tuesday, April 2, 2019 10:20 AM To: Linda Dunbar Cc: ip...@ietf.org WG;

[bess] operational problems for draft-brissette-bess-evpn-l2gw-proto

Greetings: In grow WG today, Randy Bush shared research that that communities may be erroneous sent up to 4 AS beyond the original sending. How does the technology in this draft prevent this from occurring? Is your only guarantee policy at the edge? Sue Hares

Re: [bess] draft-ietf-bess-security-00.txt

+1 on this question. I hope Ali will discuss. Sue From: Henderickx, Wim (Nokia - BE/Antwerp) [mailto:wim.henderi...@nokia.com] Sent: Monday, November 5, 2018 3:10 AM To: Susan Hares; bess@ietf.org Subject: Re: [bess] draft-ietf-bess-security-00.txt Also how does the solution

[bess] draft-ietf-bess-security-00.txt

Ali: It would be useful to indicate how you keep the IPSEC information from going outside the AS. For reference, this is Keyur Patel's question. Cheerily, Susan Hares ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo

Re: [bess] Call for adoption: draft-zzhang-bess-mvpn-msdp-sa-interoperation-01

Support. This is an necessary topic and a good start for the work. Sue From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Jeffrey (Zhaohui) Zhang Sent: Monday, February 26, 2018 7:02 AM To: stephane.litkow...@orange.com; bess@ietf.org Subject: Re: [bess] Call for adoption:

Re: [bess] New bess Co-Chair

Thomas: As one of the BGP family of Co-chairs you have been co-operative, helpful and pushed the BGP applications forward. Thank you for all you did in the last few years. Susan Hares -Original Message- From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Adrian Farrel Sent

Re: [bess] New bess Co-Chair

Stephane – Thanks for agreeing to be chair! Sue Hares From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Alvaro Retana Sent: Friday, December 1, 2017 11:17 AM To: bess@ietf.org Subject: [bess] New bess Co-Chair Dear bess WG: I am sad to report that Thomas Morin has decided

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

Support. I've read the document, and compared it against the bgp-model draft. It is a good place to start. Sue Hares 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

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

Support for draft-shah-bess-l2vpn-yang. It is a good start to this model. +1 to Giles comment that the bgp-parameters structure needs to be harmonized draft-dhjain-bess-bgp-l3vpn-yang. Both draft-shah-bess-l2vpn-yang and draft-dhjain-bess-bgp-l3vpn-yang should reference the base bgp model

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

Support for draft-bissette-bess-evpn-yang as a start for the yang module. A few questions for the authors: Do you intend to link the definitions of: "typedef bgp-rt-type" to other uses of the RT type? How do you see policy interacting with the RT values in grouping

Re: [bess] Benoit Claise's Discuss on draft-ietf-bess-mvpn-extranet-04: (with DISCUSS and COMMENT)

th textual change, but a spacing helps the person easily see the definition of the extended community. Sue -Original Message- From: Alvaro Retana (aretana) [mailto:aret...@cisco.com] Sent: Thursday, April 21, 2016 5:28 PM To: Susan Hares; Benoit Claise (bclaise); joe...@bogus.co

Re: [bess] Benoit Claise's Discuss on draft-ietf-bess-mvpn-extranet-04: (with DISCUSS and COMMENT)

at is in the overlap. The draft discusses a lot of the corner cases, and a lot of the scenarios in which things can go wrong. -Original Message- From: Eric C Rosen [mailto:ero...@juniper.net] Sent: Monday, December 21, 2015 2:59 PM To: Susan Hares; 'Benoit Claise'; 'The IESG'

Re: [bess] Benoit Claise's Discuss on draft-ietf-bess-mvpn-extranet-04: (with DISCUSS and COMMENT)

Stephen: They are adding 2 BGP Extended communities. They are modifying rules for distribution of BGP routes and PIM trees in the case of MPLS VPNs supporting multicast. The thing that worries me is they are stating that "breaking any of the policy rules" is a security consideration.

Re: [bess] [Rtg-yang-coord] IDR interim today at 10:00 - 11:30am ET - Agenda (web-ex correction)

[online request] https://ietf.webex.com/ietf/e.php?MTID=m8a391b9e59f0215e0a2251f10dac8aae Sue From: Rtg-yang-coord [mailto:rtg-yang-coord-boun...@ietf.org] On Behalf Of Susan Hares Sent: Monday, June 15, 2015 9:18 AM To: i...@ietf.org Cc: rtg-yang-co...@ietf.org; 'BESS'; net...@ietf.org; s

[bess] IDR interim to discuss status of BGP interims

Model (Susan Hares) 11:10 - 11:30 Discussion of I2RS BGP module Web-Ex: https://ietf.webex.com/ietf/j.php?MTID=mbb2d89722983f9d24990ba043332a856 Meeting number:649 169 095 Meeting password: yang.for.life Join by phone 1-877-668-4493 Call-in toll free

[bess] IDR BGP modules

Two models have been presented at IDR interims and the last 2-3 IETFs: http://datatracker.ietf.org/doc/draft-zhdankin-idr-bgp-cfg/ http://datatracker.ietf.org/doc/draft-shaikh-idr-bgp-model/ (Open Config group) The authors of these two BGP yang models have been working on creating

Re: [bess] Why transform draft-xu-softwire-encaps-udp to draft-xu-bess-encaps-udp

Xiaohu: That the draft came through softwire is self-evident. That it was appropriate to come to Softwire instead of IDR: (see https://tools.ietf.org/html/draft-ietf-idr-encaps-safi-00), this means the IDR chairs dropped the ball. I'm working hard to catch all the BGP related reviews, and I

Re: [bess] Request for WG adoption of draft-xu-bess-encaps-udp//RE: Why transform draft-xu-softwire-encaps-udp to draft-xu-bess-encaps-udp

Adrian: IDR also has a next-hop encapsulation draft pending adoption. May I suggest that perhaps the BESS/IDR chairs should collaborate on the tunnel drafts? Sue -Original Message- From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Adrian Farrel Sent: Saturday, February 14, 2015

Re: [bess] EVPN Draft Comments

Irrespectively, John -Original Message- From: Susan Hares [mailto:sha...@ndzh.com] Sent: Tuesday, February 03, 2015 12:25 AM To: 'Russ White'; John E Drake; 'Rabadan, Jorge (Jorge)' Cc: bess@ietf.org Subject: RE: [bess] EVPN Draft Comments Russ and John: I have concerns about

Re: [bess] EVPN Draft Comments

for the spam. Sue -Original Message- From: Ali Sajassi (sajassi) [mailto:saja...@cisco.com] Sent: Tuesday, February 03, 2015 12:38 PM To: Susan Hares; 'Russ White'; 'John E Drake'; 'Rabadan, Jorge (Jorge)' Cc: bess@ietf.org Subject: Re: [bess] EVPN Draft Comments Hi Sue, Two points: 1

Re: [bess] EVPN Draft Comments

mechanism in the future, but it must be deemed more efficient or better scaling. Best wishes, Sue -Original Message- From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Ali Sajassi (sajassi) Sent: Tuesday, February 03, 2015 2:52 AM To: Susan Hares; 'Russ White'; 'John E Drake'; 'Rabadan

Re: [bess] EVPN Draft Comments

Russ and John: I have concerns about the issues Russ has raised as well as other concerns regarding the EVPN. As I mentioned at the last IETF's BESS meeting, John Scudder and I have been discussing the next-hop issues in BESS drafts to see if IDR could create better BGP mechanism for the future