[bess] I-D Action: draft-ietf-bess-evpn-lsp-ping-02.txt
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 : LSP-Ping Mechanisms for EVPN and PBB-EVPN Authors : Parag Jain Samer Salam Ali Sajassi Sami Boutros Greg Mirsky Filename: draft-ietf-bess-evpn-lsp-ping-02.txt Pages : 15 Date: 2020-07-02 Abstract: LSP-Ping is a widely deployed Operation, Administration, and Maintenance (OAM) mechanism in MPLS networks. This document describes mechanisms for detecting data-plane failures using LSP Ping in MPLS based EVPN and PBB-EVPN networks. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-lsp-ping/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-bess-evpn-lsp-ping-02 https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-lsp-ping-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-evpn-lsp-ping-02 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
[bess] RtgDir review: draft-ietf-bess-evpn-inter-subnet-forwarding
Hello, I have been selected as the Routing Directorate reviewer for this draft. The Routing Directorate seeks to review all routing or routing-related drafts as they pass through IETF last call and IESG review, and sometimes on special request. The purpose of the review is to provide assistance to the Routing ADs. For more information about the Routing Directorate, please see http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir Although these comments are primarily for the use of the Routing ADs, it would be helpful if you could consider them along with any other IETF Last Call comments that you receive, and strive to resolve them through discussion or by updating the draft. Document: draft-ietf-bess-evpn-inter-subnet-forwarding Reviewer: Russ White Review Date: 2 July 2020 Intended Status: Standards Summary: No issues found. This document is ready for publication. Comments: This draft is very readable, with good figures and explanations. Major Issues: No major issues found. Minor Issues: No minor issues found. /r ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
[bess] bess - Requested session has been scheduled for IETF 108
Dear mankamana mishra, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. bess Session 1 (1:40 requested) Tuesday, 28 July 2020, Session I 1100-1240 Room Name: Room 5 size: 5 - iCalendar: https://datatracker.ietf.org/meeting/108/sessions/bess.ics Request Information: - Working Group Name: BGP Enabled ServiceS Area Name: Routing Area Session Requester: mankamana mishra Number of Sessions: 1 Length of Session(s): 100 Minutes Number of Attendees: 100 Conflicts to Avoid: Chair Conflict: idr nvo3 Technology Overlap: spring sfc mpls pim bier pals Key Participant Conflict: i2rs People who must be present: Matthew Bocci Martin Vigoureux Stephane Litkowski mankamana prasad mishra Resources Requested: Special Requests: - ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
[bess] I-D Action: draft-ietf-bess-bgp-multicast-controller-02.txt
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 : Controller Based BGP Multicast Signaling Authors : Zhaohui Zhang Robert Raszuk Dante Pacella Arkadiy Gulko Filename: draft-ietf-bess-bgp-multicast-controller-02.txt Pages : 14 Date: 2020-07-02 Abstract: This document specifies a way that one or more centralized controllers can use BGP to set up a multicast distribution tree in a network. In the case of labeled tree, the labels are assigned by the controllers either from the controllers' local label spaces, or from a common Segment Routing Global Block (SRGB), or from each routers Segment Routing Local Block (SRLB) that the controllers learn. In case of labeled unidirectional tree and label allocation from the common SRGB or from the controllers' local spaces, a single common label can be used for all routers on the tree to send and receive traffic with. Since the controllers calculate the trees, they can use sophisticated algorithms and constraints to achieve traffic engineering. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-bess-bgp-multicast-controller/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-bess-bgp-multicast-controller-02 https://datatracker.ietf.org/doc/html/draft-ietf-bess-bgp-multicast-controller-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-bgp-multicast-controller-02 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] WG Last Call and IPR Poll for draft-ietf-bess-evpn-oam-req-frmwk-02
Jorge Yes, you are correct. The WG Last Call should have read “informational document”. Matthew From: "Rabadan, Jorge (Nokia - US/Mountain View)" Date: Wednesday, 1 July 2020 at 17:59 To: "Parag Jain (paragj)" , "Bocci, Matthew (Nokia - GB)" , "draft-ietf-bess-evpn-oam-req-fr...@ietf.org" , "bess@ietf.org" Subject: Re: [bess] WG Last Call and IPR Poll for draft-ietf-bess-evpn-oam-req-frmwk-02 Matthew, Stephane, I assume you meant: “Also, please indicate if you support publishing the draft as an Informational RFC.” If so, I support it for publication as Informational RFC. Thanks. Jorge From: "Bocci, Matthew (Nokia - GB)" Date: Monday, June 15, 2020 at 3:55 AM To: "draft-ietf-bess-evpn-oam-req-fr...@ietf.org" , "bess@ietf.org" Subject: WG Last Call and IPR Poll for draft-ietf-bess-evpn-oam-req-frmwk-02 Resent-From: Resent-To: , Cisco Employee , , , Resent-Date: Monday, June 15, 2020 at 3:55 AM This email starts a two-week working group last call for draft-ietf-bess-evpn-oam-req-frmwk-02 Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 29th June 2020. 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. There is currently no IPR disclosed. Thank you, Matthew & Stephane ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
