[bess] WGLC, IPR, implementation poll for draft-ietf-bess-evpn-irb-extended-mobility

slitkows.ietf@gmail.com Wed, 20 September 2023 12:39 UTC

Return-Path: <slitkows.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 6D142C1526FB; Wed, 20 Sep 2023 05:39:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0kqzA_o-U7SP; Wed, 20 Sep 2023 05:39:22 -0700 (PDT)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3887C1524A3; Wed, 20 Sep 2023 05:39:22 -0700 (PDT)
Received: by mail-lj1-x236.google.com with SMTP id 38308e7fff4ca-2c124adf469so7027101fa.0; Wed, 20 Sep 2023 05:39:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695213561; x=1695818361; darn=ietf.org; h=content-language:thread-index:mime-version:message-id:date:subject :in-reply-to:references:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=pf5WebmdMoB7HNpucP1XcAt8Tf5nQSlXVNjLJkCcpho=; b=iZSeWn4AuSp5O4+/55gBeqoDIQiDPTXkOhFLnVV3S0Zpq79jrDuAHvq2eSxVgb46t8 V1b0u9bvwZInIiLW4QZjBoQpEdrAgS7lXTo5VVH2b7/L7XP8at9NXZeyeQe9V1eDx9KK 7DCKlAOhlMB/KWxPeBFvEXhjTi9k5/TXavk2C/runAr+ffRR35uCL/I9BrUI43PnGLof l7mP050FSYnPsCUKK5fOllEw3+UBoOZ8ilV6+7TkzL9X0R1D+xjZegjhGdKNZEb/rEei sQnqIg0kqkAJIqu86dV62NZFgzOqJ3gpznAMdBvhJmppcofEI4x8P9j/PBVZp0pUzzaa LMKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695213561; x=1695818361; h=content-language:thread-index:mime-version:message-id:date:subject :in-reply-to:references:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=pf5WebmdMoB7HNpucP1XcAt8Tf5nQSlXVNjLJkCcpho=; b=bUIwURBZWBnvMYLpC4KDLFjSFhQLvziwMVxnwJYGbo1blkqqAzlM7fH1KLx/K+/+kO w4PedhaG4nW4ibyLUikx67MTZnkOoXbFAqUH18mbtQ6UhAKryB6VOwrkGFPD5YvSe21d 7uCeUgvR84q4bMkEQS2O3/1c3A2nPoBCvfRzMR7NXiNclrtHUfleMxQ8mgNaHIyhsZIA h4B8Ey7teFZ/vn9/YElLZiDOrwKBx2pTNd6UG3b00c6C1TDL5+8W1Gf44yFZYZ16SjpE 1wC8OcKtj7WCY3ZotD+h8YHP5uhuuL0BcfCJrI4DBFq2JSS0jELCcEEcyiQ0JDL0XFMM f2qw==
X-Gm-Message-State: AOJu0Ywp/jjaZvpw6fS5UcNZcdSuItEyXb3O0So/DZPyuPLIaGvHD4Vt a/twrQGMzO3z7Kj7J3WtWbViTzl2gQ==
X-Google-Smtp-Source: AGHT+IF6o09hJGaUS78vHHNuZRjR5R/8sJJHmSJNp1gPGkRH6mEvVpFIuDn6d+YYMy3CZzFy88KInQ==
X-Received: by 2002:a2e:9988:0:b0:2c0:298d:32df with SMTP id w8-20020a2e9988000000b002c0298d32dfmr2256995lji.9.1695213560203; Wed, 20 Sep 2023 05:39:20 -0700 (PDT)
Received: from CSCOWPF2QW8Y3 ([173.38.220.58]) by smtp.gmail.com with ESMTPSA id se1-20020a170906ce4100b0099bc2d1429csm9261733ejb.72.2023.09.20.05.39.19 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Sep 2023 05:39:19 -0700 (PDT)
From: slitkows.ietf@gmail.com
To: bess@ietf.org
Cc: bess-chairs@ietf.org
References: <078201d9eacd$33d45910$9b7d0b30$@gmail.com> <SJ0PR11MB5770E410ECC37EEACB6BD2FFB0FAA@SJ0PR11MB5770.namprd11.prod.outlook.com>
In-Reply-To: <SJ0PR11MB5770E410ECC37EEACB6BD2FFB0FAA@SJ0PR11MB5770.namprd11.prod.outlook.com>
Date: Wed, 20 Sep 2023 14:39:18 +0200
Message-ID: <00a801d9ebbf$79b13dc0$6d13b940$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A9_01D9EBD0.3D3BBB70"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: Adnrv1cy5QuzafJdSEW710qC8axziA==
Content-Language: fr
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/NzsKzVOrdArGQqNJDl5Ve_n1w8M>
Subject: [bess] WGLC, IPR, implementation poll for draft-ietf-bess-evpn-irb-extended-mobility
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 20 Sep 2023 12:39:23 -0000

Quick Errata : there is one IPR currently disclosed (initial email said
there's no).

 

 

Hi WG,

 

This email starts a two-week Working Group Last Call on
draft-ietf-bess-evpn-irb-extended-mobility-14 [1]. Note that the document
already had a WGLC and comments were raised by the WG. These comments are
normally addressed by the Authors but feel free to review again and provide
feedback.

 

This poll runs until Tuesday 3rd October.

 

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 one 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,

Stephane, Matthew, Jeffrey

 

[1]
<https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-irb-extended-mobility
/>
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-irb-extended-mobility/

[2]
<https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw>
https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw