Re: [bess] WG adoption call and IPR poll for draft-rabadan-bess-vendor-evpn-route-07

Jeff Tantsura <> Tue, 20 August 2019 17:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BDBD012018D for <>; Tue, 20 Aug 2019 10:24:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id q1w_4lHIduBA for <>; Tue, 20 Aug 2019 10:24:33 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::742]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5AF3212004C for <>; Tue, 20 Aug 2019 10:24:33 -0700 (PDT)
Received: by with SMTP id s14so5164299qkm.4 for <>; Tue, 20 Aug 2019 10:24:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=date:from:to:message-id:in-reply-to:references:subject:mime-version; bh=Mu2PM2GnLC3wonY6ntGCHhoXtD3zXLjw76i98RQGSEw=; b=DsTZNfU+J7nj3Sin1THvfCiz52htvFWewMmgqc+HXd5f5+VLN3Ol46UrsHewFkQzbf wpSwhvyO23HyYRFjF4MgcDEX1w0Z2OfCEDnUToREqhGXpJJ2Jr9OBf2R+UrDcpw3Vh2Y yqGf/MMG20yL2Z6M43E6+vzVjZ14yuh3f2GhXLGX4z1GbfXudoQYbL8smd+b4yzV13tE SvZ4vwgcPJKopcFhR4LE7bvsMTFzcpxoV7qHLCSwXpYoGXaBcbFumlqKr+VWz22B398y wXH2J4HbpdnjMRcOFmZhu9bcD0y8kSGb3yBJZZAcM78zK2hLLdK6TP1c+OghunBJIzTR /wew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version; bh=Mu2PM2GnLC3wonY6ntGCHhoXtD3zXLjw76i98RQGSEw=; b=r0ZTTEu5LiCczCVMNToXBesrXD6ROw03LR/jJpZN8KfyW3Rgul/euD7tvtlB5V1HjH 4wTuhiGluk5UEtd+fbeQIAZP/FlRoF39BF8WGTMLca72C4TqjrZabdqol96WABgd6TRY bAaorf1MLetOTBItNRo+R0134kLBim1tPHx9DTMPkuPIgLOChFI44Oo9o+uz8iLXNLHx PDfh7CXyJ6/IzIBfpSVzPD/q5ZmbmwPzIf5Y/NYX7s1X1+RCn0FI/H3sQJkmTJZhsgsB MF29pv1i9cZcFgrYEaKcm1S49pCBEdijUz3Uz7jc6kw0CfS0SBNMgF7ZmztrJ8dkDx4W QPzw==
X-Gm-Message-State: APjAAAV0uB/WVTxmWQp6URgmviYNuRi1MRQyZntyFQ1GB600reVV3hws lNuHCZCtp4QU024U4KJv9Ov2AD7J
X-Google-Smtp-Source: APXvYqxWgGEh4cppl5X4yxgNKZ64Oj9Q6MTtsirz4bJxteTkq9sslOGL3tqSpXm0/Mu71wsrl956mg==
X-Received: by 2002:a37:a06:: with SMTP id 6mr26890634qkk.185.1566321871984; Tue, 20 Aug 2019 10:24:31 -0700 (PDT)
Received: from [] ([]) by with ESMTPSA id f9sm8915750qkm.51.2019. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Aug 2019 10:24:31 -0700 (PDT)
Date: Tue, 20 Aug 2019 13:24:25 -0400
From: Jeff Tantsura <>
To:, Stephane Litkowski <>
Message-ID: <9d4b02b2-18b4-4e45-95bc-54a853c5a398@Spark>
In-Reply-To: <>
References: <>
X-Readdle-Message-ID: 9d4b02b2-18b4-4e45-95bc-54a853c5a398@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5d5c2cce_2a6de806_2a1"
Archived-At: <>
Subject: Re: [bess] WG adoption call and IPR poll for draft-rabadan-bess-vendor-evpn-route-07
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 20 Aug 2019 17:24:36 -0000

In general I support the adoption.

Could the authors please clarify how a company that doesn’t have OUI assigned should populate the OUI field and how interdependency between IEEE registration and EVPN implementation would be handled.

Informal references for IEEE OUI handling process would be useful too, perhaps this one -

On Aug 20, 2019, 5:15 AM -0400, Stephane Litkowski <>, wrote:
> Hi,
> This email begins a two-weeks WG adoption poll for draft-rabadan-bess-vendor-evpn-route-07 [1]
> Please review the draft and post any comments to the BESS working group list.
> 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, copying the BESS mailing list. The document won't progress without answers from all the authors and contributors.
> Currently, there are no IPR disclosures against this document.
> 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.
> This poll for adoption closes on 2nd September 2019.
> Regards,
> Stephane and Matthew
> [1]
> _______________________________________________
> BESS mailing list