Re: [bess] Call for adoption: draft-lin-bess-evpn-irb-mcast

Jeff Tantsura <> Thu, 11 January 2018 22:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 96F9D12AF6E; Thu, 11 Jan 2018 14:25:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 xO1alMXZz3AB; Thu, 11 Jan 2018 14:25:28 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:400e:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 77F57129C6C; Thu, 11 Jan 2018 14:25:28 -0800 (PST)
Received: by with SMTP id m20so3158687pgc.11; Thu, 11 Jan 2018 14:25:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version:content-transfer-encoding; bh=iZfMZGv9NwIV//fr6G8HgH5CHvm6BEmmOljSVvxPlFE=; b=XIvEEJ8IelwG/U0/qtxCcfIZhuTwacuL3K/h6NueqtzWEnIc7e5cTxxMrBJf0UyDYm OwbVNPoX5hGZNZe3AklLAWgXQOwPEfAgxLkIlI7IvRaJVJ+0bRzbh78YnCAGB/E8WoUO SHYqz0ViATMnwSUsM13KTJCWx4cCpXemK90b/Ju73hxEiKT7J0EVZz3I3o4ChNv9wWBb lUOPLdj1++3P/CKHiykS5kIC6058fQl3EZ2W+b9IyIemb+UToC7mnumjG0q46+/9MaJL 0XcqvlfxYYMKq2Ap0REG/I4pQYRfH5jGBN736WdWGuJSscmcARd8EPvN5TDuQFCmhq7e oC5A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version :content-transfer-encoding; bh=iZfMZGv9NwIV//fr6G8HgH5CHvm6BEmmOljSVvxPlFE=; b=EZqQov1Y9MDtS3BnufJVId99ltKmQwDRI2XEt6EU8dylNlLNPkX5OGmbl2SRKlIXXn zHd6/rTGU++bQ8vGk/P6VVjZ8QWRG7Ag+CmCk6s+AC4VHsNhaaGavsbffnHQpKrZ5/Ov w/AUw84UAFFPYO/FGZYccY2EqSdgWtjLpLXouAHR+YoQKjDIc64wvSIJT+zDpauvVQaF OoJMQvQyRHH3sZnX6i7n2zq27QSRSaMR+jfh/NvMAmV/BaBMTJu+KWP/V11xhLsIZoyM miQVpphoXHRjIuAxefeTMPjJ8MQ8E0ycUP2hmKajCnCTpyP9H1dzL0UZcoAhjPlr2Zp0 jGog==
X-Gm-Message-State: AKGB3mKRqkNXLbXF+G/ucxHSESlOwKR+9KhWoCo6yyW/ke7XJ8ohv4nI L38d8FO4IEM/jhKi8z9LY3k=
X-Google-Smtp-Source: ACJfBovv6vDQIAFFWM9TNN8FSOopb/Ir+AiacODLtQpSeXBa5PAaF7whYQq+mFHSAWvHZt9rMxdD5g==
X-Received: by with SMTP id i1mr16795571plk.323.1515709527551; Thu, 11 Jan 2018 14:25:27 -0800 (PST)
Received: from [] ([]) by with ESMTPSA id k2sm41370145pfg.53.2018. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Jan 2018 14:25:26 -0800 (PST)
User-Agent: Microsoft-MacOutlook/f.27.0.171010
Date: Thu, 11 Jan 2018 14:25:25 -0800
From: Jeff Tantsura <>
To: Martin Vigoureux <>,
Message-ID: <>
Thread-Topic: [bess] Call for adoption: draft-lin-bess-evpn-irb-mcast
References: <>
In-Reply-To: <>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <>
Subject: Re: [bess] Call for adoption: draft-lin-bess-evpn-irb-mcast
X-Mailman-Version: 2.1.22
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: Thu, 11 Jan 2018 22:25:31 -0000

Document provides very much needed clarifications wrt multicast use in EVPN.


On 1/11/18, 02:12, "BESS on behalf of Martin Vigoureux" < on behalf of> wrote:

    Hello working group,
    This email starts a two-week call for adoption on 
    draft-lin-bess-evpn-irb-mcast-04 [1] as a BESS Working Group Document.
    Please state on the list if you support the adoption or not (in both 
    cases, please also state the reasons).
    This poll runs until *the 26th of January*.
    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
    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.
    Currently no IPR has been disclosed 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.
    Thank you
    Martin & Stéphane
    bess chairs
    BESS mailing list