IETF Logo Mail Archive

Re: [bess] Mail regarding draft-ietf-bess-evpn-per-mcast-flow-df-election

Luc André Burdet <laburdet.ietf@gmail.com> Tue, 17 November 2020 19:34 UTC

Return-Path: <laburdet.ietf@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 896163A1595; Tue, 17 Nov 2020 11:34:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 j78g89DdC0fk; Tue, 17 Nov 2020 11:34:36 -0800 (PST)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (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 989BD3A1585; Tue, 17 Nov 2020 11:34:09 -0800 (PST)
Received: by mail-qt1-x835.google.com with SMTP id b16so16473502qtb.6; Tue, 17 Nov 2020 11:34:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :mime-version; bh=hrX2iCDt9lZOGMWlHu5afOB1zOrrFHgQRXCiiWh8WyA=; b=B6PBEMIzfhcCWXe49Hmm5A+wzxLuM0Z584e6peaWPHngCeNV0QrqSxDZs8OYzsJyf6 53n8QDQ/VwBStdp1P3wQkO/vmOeHGCenTZm13BV7Bq69igb3SZdn+8FNpvYjn8XG2Zqa O5BesJTZ4VeIeWQTVyEzfFeryoRTrwk1fFzkyj8xzuYaUaECsI6yutjKkDHrGo6mKjXH Jqa708KZsiUBukUxmBYjM2dhh0Yb+/W0wuLTFc2Kap/b2EId0gruBlJwPPHj+f5Tbbkl q/UxrjtD1hZ96zQj9bLgUWXSozSbdxMji2WXg1+p1iReorNgxaWHG61PqZNoEzi+i6hE gpnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:mime-version; bh=hrX2iCDt9lZOGMWlHu5afOB1zOrrFHgQRXCiiWh8WyA=; b=WhkBSB8aUIEx/bb+QQH0i9hMwMYGreR/dAfNfDFBxyruO2DsQbSmr0YM5Chd+8bRNG oZ/Z6e8enuLRHvHG6nVUdPNvbxyos0xpPTRFl+gum7jnOi2IrrdtYJVtR+6OTunywa5P VgeR6RYOIvF+m1P69dDbE7RpFsaYibX8nLKWjOaiZmBoy3ufjwNYXENGZphJTV/V6J0q GjZ8QLUCIxdmU24EOQ4aTWFXjcKwyMGuC0e34icUeYqWyIPYBnolpXNVG82E1fO1ve+e uWZt3Rr7UelmjMbw0RvzVXvsH7fD4bXnpfRuprVNtX1lscod6b+Uq+OqJ8FNxmlnyAae +seg==
X-Gm-Message-State: AOAM531aeEvq+HlpUGH3BF1wIuc+YnR4ZFgCgmFvWklHsigaIfodZOES 3DsNW8poPJRm6dK4HMsVDB3iJNVGGNtd/A==
X-Google-Smtp-Source: ABdhPJyFSH/0pO/Nj9Z959LbhVtw4RVrLjfKSYx3UC7uC5FfLYaVscqOcRw2aDnbepK4QNDiNndtwQ==
X-Received: by 2002:aed:3264:: with SMTP id y91mr1276105qtd.308.1605641648150; Tue, 17 Nov 2020 11:34:08 -0800 (PST)
Received: from DF4PR8401MB0650.NAMPRD84.PROD.OUTLOOK.COM ([2a01:111:f400:7509::5]) by smtp.gmail.com with ESMTPSA id f14sm3128251qkk.89.2020.11.17.11.34.06 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Nov 2020 11:34:07 -0800 (PST)
From: Luc André Burdet <laburdet.ietf@gmail.com>
To: "draft-ietf-bess-evpn-per-mcast-flow-df-election@ietf.org" <draft-ietf-bess-evpn-per-mcast-flow-df-election@ietf.org>
CC: "bess@ietf.org" <bess@ietf.org>
Thread-Topic: Mail regarding draft-ietf-bess-evpn-per-mcast-flow-df-election
Thread-Index: ATAzODY0PiR5RKI2WMVtlJaSIWySJ80TwMs/
X-MS-Exchange-MessageSentRepresentingType: 1
Date: Tue, 17 Nov 2020 19:34:05 +0000
Message-ID: <DF4PR8401MB0650E32571A2E694F872A009AFE20@DF4PR8401MB0650.NAMPRD84.PROD.OUTLOOK.COM>
References: <DM6PR07MB42521026DCE85889346853DDAF5F0@DM6PR07MB4252.namprd07.prod.outlook.com>
In-Reply-To: <DM6PR07MB42521026DCE85889346853DDAF5F0@DM6PR07MB4252.namprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator:
X-MS-Exchange-Organization-RecordReviewCfmType: 0
Content-Type: multipart/alternative; boundary="_000_DF4PR8401MB0650E32571A2E694F872A009AFE20DF4PR8401MB0650_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/Thdrf7c74CUrrBxJ75kxN3l7CR4>
Subject: Re: [bess] Mail regarding draft-ietf-bess-evpn-per-mcast-flow-df-election
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: Tue, 17 Nov 2020 19:34:38 -0000

Hi authors,

Please make sure to update -05 to drop mention of DF Types 2&3 (these are a Capability) and the pluralisation Nit raised below?
Thanks !

Regards,
Luc André

Luc André Burdet |  Cisco  |  laburdet.ietf@gmail.com  |  Tel: +1 613 254 4814


From: Luc André Burdet <laburdet.ietf@gmail.com>
Date: Friday, December 6, 2019 at 11:49
To: "draft-ietf-bess-evpn-per-mcast-flow-df-election@ietf.org" <draft-ietf-bess-evpn-per-mcast-flow-df-election@ietf.org>
Cc: "bess@ietf.org" <bess@ietf.org>
Subject: Mail regarding draft-ietf-bess-evpn-per-mcast-flow-df-election

Hi authors,
Quick note: can you make sure that in the next revision of this draft the DF Election EC section 3 is updated?
Fast-DF-recovery is claiming 2 DF Capability bits, not DF-Types


      *  Type 2: Handshake defines in

         [I-D.ietf-bess-evpn-fast-df-recovery<https://tools.ietf.org/html/draft-ietf-bess-evpn-per-mcast-flow-df-election-02#ref-I-D.ietf-bess-evpn-fast-df-recovery>]



      *  Type 3: Time-Synch defined in

         [I-D.ietf-bess-evpn-fast-df-recovery<https://tools.ietf.org/html/draft-ietf-bess-evpn-per-mcast-flow-df-election-02#ref-I-D.ietf-bess-evpn-fast-df-recovery>]

As a general comment to WG, the DF-Type and DF-Capabilities values are never pre-allocated for WG-adopted documents... making tracking & updating tedious.  Can we at/before 107 request pre-allocation of some of these in the WG drafts that have stabilised?

Nit:

The current proposal extends the existing extended community defined in

   [I-D.ietf-bess-evpn-df-election-framework<https://tools.ietf.org/html/draft-ietf-bess-evpn-per-mcast-flow-df-election-02#ref-I-D.ietf-bess-evpn-df-election-framework>]. This draft defines new a DF type.
-->Defines “two new DF Types”


Regards,
Luc André

Luc André Burdet |  Cisco  |  laburdet.ietf@gmail.com  |  Tel: +1 613 254 4814

v2.23.0 | Report a Bug | By Email