Re: [bess] WGLC, IPR and Implementation Poll for draft-ietf-bess-evpn-fast-df-recovery-03
Anoop Ghanwani <anoop@alumni.duke.edu> Fri, 04 February 2022 17:50 UTC
Return-Path: <ghanwani@gmail.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B745F3A1CFE; Fri, 4 Feb 2022 09:50:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.398
X-Spam-Level:
X-Spam-Status: No, score=-1.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WzlBxpFx8j0I; Fri, 4 Feb 2022 09:50:22 -0800 (PST)
Received: from mail-lf1-f53.google.com (mail-lf1-f53.google.com [209.85.167.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 563C63A1CF8; Fri, 4 Feb 2022 09:50:22 -0800 (PST)
Received: by mail-lf1-f53.google.com with SMTP id x23so14224216lfc.0; Fri, 04 Feb 2022 09:50:22 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=e54mzKbOQdoSjm17yVv+da0JrGDlmfuo6ZWfUi+qDtQ=; b=g2V40cxWK4nMenwtzEwG/x6PEAMp4ud47GM+v5UMjQGZ/uWoos56H+p0xU75xnSBW1 ReA3LC+wUkCbQntnI7QRLYAyXwSxrSi9C0UWyRGUKzyC0qAywlEBoHe0SUuKH+C8EkvT P3pUs7MrY932Q32Z36EqSAYojdMhl/oZsWHTTveKD2xQ6mwtqtNBRqepBr3z06qiAUuD nivZ5vJd0xL9HuyATFkoX8H+6K8pC8c4aUquHYmxCuoDiEqgdWq315eHIa92pxz9sgEA KmVPMQW/x0xzcCOO+hxzu3n5UKOYFWZ+cztiiRNMgNXYLk/J39EF6O5gwGJr74xp/F8e acGg==
X-Gm-Message-State: AOAM531rvS8x08as4I4qaxQd3/+Djyu7BO0OiCVUo3weJTfiIoeRRTpB ZHC9XCVA/NGZ6vhd82pkexWQNXSfMt8pxDrRxeac/abM/3g=
X-Google-Smtp-Source: ABdhPJzSx9bBwI/SirIpRCp9raFD6JG0s8A/XOW/kR+G+1h/OyoDWMn+dBgQ+UHVQWobkAJyTeXrBCXVNdIoxVjAFBA=
X-Received: by 2002:a05:6512:1054:: with SMTP id c20mr36118lfb.654.1643997019364; Fri, 04 Feb 2022 09:50:19 -0800 (PST)
MIME-Version: 1.0
References: <VI1PR0701MB6991127811050E749055AD03EB259@VI1PR0701MB6991.eurprd07.prod.outlook.com>
In-Reply-To: <VI1PR0701MB6991127811050E749055AD03EB259@VI1PR0701MB6991.eurprd07.prod.outlook.com>
From: Anoop Ghanwani <anoop@alumni.duke.edu>
Date: Fri, 04 Feb 2022 09:50:07 -0800
Message-ID: <CA+-tSzx7ryXrAtcUi+zSa+ksyb=_1bBxaot5QBLaC+eMh8yfPQ@mail.gmail.com>
To: "Bocci, Matthew (Nokia - GB)" <matthew.bocci@nokia.com>
Cc: "draft-ietf-bess-evpn-fast-df-recovery@ietf.org" <draft-ietf-bess-evpn-fast-df-recovery@ietf.org>, "bess@ietf.org" <bess@ietf.org>, "bess-chairs@ietf.org" <bess-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000059e16605d734e20e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/GhLnWwYZ5NtWjWrLW5hnB2mhh8U>
Subject: Re: [bess] WGLC, IPR and Implementation Poll for draft-ietf-bess-evpn-fast-df-recovery-03
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Feb 2022 17:50:27 -0000
I support publication of the document as an RFC. However, I think there are some editorial nits that need to be addressed (see below). Anoop == Abstract performed via a simple signaling between the recovered PE and each PEs in the multi-homing group. -> performed via simple signaling between the recovered PE and each of the other PEs in the multi-homing group. Multiple sections multi-homing Ethernet Segment -> multi-homed Ethernet Segment Ethernet-Segment -> Ethernet Segment There are some instances of use of ES (section 3.2). Either ES should be spelled out and used throughout or, which is what I would do, replace the 2 instances of ES in Section 3.2 with Ethernet Segment. It would also be good to provide captions for all figures since it makes it easy to reference. Section 1 EVPN solution [RFC7432] -> The EVPN specification [RFC7432] and it is performed via a simple signaling between the recovered PE and each PE in the multi- homing group. -> and it is performed via simple signaling between the recovered PE and each of the other PEs in the multi- homing group. Section 2 The current state of art (Highest Random Weight) -> The current state of art HRW (Highest Random Weight) duplication of DF roles for a give VLAN is possible. -> duplication of DF roles for a given VLAN is possible. Section 3.1 - A simple uni-directional signaling is all needed -> - A simple uni-directional signaling is all that is needed - (e.g .NTP, PTP, etc.) -> - (e.g. NTP, PTP, etc.) Section 3.2 It would be good to explicitly explain the fields below the figure, e.g. Timestamp Seconds (32 bits): ... Timestamp Fractional Seconds (17 bits): ... (provide details on how this part is created) If this is omitted because it is in some other doc, then provide a reference. [Looks like the figure is wrong about length for Timestamp Fractional Seconds which is why it would help to have a description as above.] PEs in the ES [there are 2 instances] -> PEs attached to the Ethernet Segment want the DF type be of HRW -> want the DF type to be HRW "The use of a 32-bit seconds and 16-bit fractional seconds yields adequate precision of 15 microseconds (2^-16 s)." The figure shows 17 bits for fractional seconds. Now that I double check, the figure is wrong! It uses only 7 bits for the Type which looks like it should be 8 bits. So it looks like Timestamp Fractional Seconds should be 16 bits. Section 3.4 - PE2, it starts its 3sec peering timer as per RFC7432 -> - PE2, starts its 3 sec peering timer as per RFC7432 [RFC7432] aims of favouring traffic black hole over duplicate traffic (Missing period at end of sentence.) Spell out first use of NDF. becomes a no-op -> becomes a non-issue. The usage of SCT approach remedies to the exposed problem with the usage of peering timer. The 3 seconds timer window is shorthen to few milliseconds. -> The usage of SCT approach remedies the problem with the usage of the peering timer. The 3 second timer window is shortened to a few milliseconds. Section 3.5 modulus based -> modulo-based running an baseline DF election -> running a baseline DF election shall simply discard unrecognized new SCT BGP extended community. -> will simply disregard the new SCT BGP extended community. "...all PEs in the Ethernet-Segment may revert back to the RFC7432 timer approach." Is this a "may" or should it be a "must"? On Mon, Jan 31, 2022 at 5:58 AM Bocci, Matthew (Nokia - GB) < matthew.bocci@nokia.com> wrote: > Hi WG, > > > > This email starts a two-week Working Group Last Call on draft-ietf-bess-evpn-fast-df-recovery-03 > [1]. > > > > This poll runs until Monday 14th February 2022. > > > > 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. > > > > 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. > > > > We are also polling for any existing implementation as per [2]. Please > indicate if you are aware of any implementations. > > > > Thank you, > > Matthew & Stephane > > > > [1] draft-ietf-bess-evpn-fast-df-recovery-03 - Fast Recovery for EVPN DF > Election > <https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-fast-df-recovery/> > > [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw > > > > > _______________________________________________ > BESS mailing list > BESS@ietf.org > https://www.ietf.org/mailman/listinfo/bess >
- [bess] WGLC, IPR and Implementation Poll for draf… Bocci, Matthew (Nokia - GB)
- Re: [bess] WGLC, IPR and Implementation Poll for … John E Drake
- Re: [bess] WGLC, IPR and Implementation Poll for … Acee Lindem (acee)
- Re: [bess] WGLC, IPR and Implementation Poll for … Mankamana Mishra (mankamis)
- Re: [bess] WGLC, IPR and Implementation Poll for … Rabadan, Jorge (Nokia - US/Sunnyvale)
- Re: [bess] WGLC, IPR and Implementation Poll for … Luc André Burdet
- Re: [bess] WGLC, IPR and Implementation Poll for … Patrice Brissette (pbrisset)
- Re: [bess] WGLC, IPR and Implementation Poll for … Gyan Mishra
- Re: [bess] WGLC, IPR and Implementation Poll for … Anoop Ghanwani
- Re: [bess] WGLC, IPR and Implementation Poll for … Jeff Tantsura
- Re: [bess] WGLC, IPR and Implementation Poll for … Luc André Burdet
- Re: [bess] WGLC, IPR and Implementation Poll for … Anoop Ghanwani
- Re: [bess] WGLC, IPR and Implementation Poll for … Ali Sajassi (sajassi)
- Re: [bess] WGLC, IPR and Implementation Poll for … UTTARO, JAMES
- Re: [bess] WGLC, IPR and Implementation Poll for … Bocci, Matthew (Nokia - GB)
- Re: [bess] WGLC, IPR and Implementation Poll for … Matthew Bocci (Nokia)
- Re: [bess] WGLC, IPR and Implementation Poll for … Luc André Burdet