Re: [bess] Mirja Kühlewind's No Objection on draft-ietf-bess-evpn-usage-08: (with COMMENT)
"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Mon, 19 February 2018 19:56 UTC
Return-Path: <ietf@kuehlewind.net>
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 F0631126C19 for <bess@ietfa.amsl.com>; Mon, 19 Feb 2018 11:56:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level:
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
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 kNdthIUhT5hV for <bess@ietfa.amsl.com>; Mon, 19 Feb 2018 11:56:09 -0800 (PST)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F1B2126DCA for <bess@ietf.org>; Mon, 19 Feb 2018 11:56:09 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net; b=Q8ieTGo+x6gqcwxaYIh3G+GpxsR6B0LHWrTHJL9Q+Acptf4zFlxDMPeXZdkh5AhsHR6iVshfSTu1dKZw5ixX20WisK3DMCDOuaNCSYhC4mC7+Z/TRvcAIG0aCVyqD9y/bFNhMHYogWk0htI5FIxu/YNJieWA84bfvkD0jASUlzY=; h=Received:Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 29186 invoked from network); 19 Feb 2018 20:49:25 +0100
Received: from i577bce31.versanet.de (HELO ?192.168.178.33?) (87.123.206.49) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 19 Feb 2018 20:49:25 +0100
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <136089E3-27FA-4570-8151-3730BF2035B9@nokia.com>
Date: Mon, 19 Feb 2018 20:49:23 +0100
Cc: The IESG <iesg@ietf.org>, "draft-ietf-bess-evpn-usage@ietf.org" <draft-ietf-bess-evpn-usage@ietf.org>, "Vigoureux, Martin (Nokia - FR/Paris-Saclay)" <martin.vigoureux@nokia.com>, "bess-chairs@ietf.org" <bess-chairs@ietf.org>, "bess@ietf.org" <bess@ietf.org>, "aretana.ietf@gmail.com" <aretana.ietf@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <8340F031-0409-4B57-9316-A025AB7D9EB5@kuehlewind.net>
References: <151904794146.18699.5332623354542357293.idtracker@ietfa.amsl.com> <136089E3-27FA-4570-8151-3730BF2035B9@nokia.com>
To: "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com>
X-Mailer: Apple Mail (2.3445.5.20)
X-PPP-Message-ID: <20180219194925.29176.22596@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/tzFXWQl7-1A26jgDoigJ-qf4-Vk>
Subject: Re: [bess] Mirja Kühlewind's No Objection on draft-ietf-bess-evpn-usage-08: (with COMMENT)
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 19 Feb 2018 19:56:11 -0000
Ah, thanks. That’s much more clear to me! > Am 19.02.2018 um 20:47 schrieb Rabadan, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com>: > > Hi Mirja, > > It should be "must be enable". However you are right that the sentence may be worded a bit better. > We can change it as follows: > > It is worth noting that unknown unicast flooding must not be > suppressed, unless (at least) one of the following two statements are > given: a) control or management plane learning is performed > throughout the entire EVI for all the MACs or b) all the EVI-attached > devices signal their presence when they come up (GARPs or similar). > > Thanks. > Jorge > > > -----Original Message----- > From: Mirja Kühlewind <ietf@kuehlewind.net> > Date: Monday, February 19, 2018 at 2:45 PM > To: The IESG <iesg@ietf.org> > Cc: "draft-ietf-bess-evpn-usage@ietf.org" <draft-ietf-bess-evpn-usage@ietf.org>, "aretana.ietf@gmail.com" <aretana.ietf@gmail.com>, "bess-chairs@ietf.org" <bess-chairs@ietf.org>, "Vigoureux, Martin (Nokia - FR/Paris-Saclay)" <martin.vigoureux@nokia.com>, "bess@ietf.org" <bess@ietf.org> > Subject: Mirja Kühlewind's No Objection on draft-ietf-bess-evpn-usage-08: (with COMMENT) > Resent-From: <alias-bounces@ietf.org> > Resent-To: <jorge.rabadan@nokia.com>, <senad.palislamovic@nokia.com>, <wim.henderickx@nokia.com>, <sajassi@cisco.com>, <uttaro@att.com> > Resent-Date: Monday, February 19, 2018 at 2:45 PM > > Mirja Kühlewind has entered the following ballot position for > draft-ietf-bess-evpn-usage-08: No Objection > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html > for more information about IESG DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-usage/ > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Possible nit: > sec 9.1.3: "It is worth noting that unless: a) control or management plane > learning is performed through the entire EVI or b) all the EVI- > attached devices signal their presence when they come up (GARPs or > similar), unknown unicast flooding must be enabled." > Is this "must be enabled" or "must not be enabled"? > > > >
- [bess] Mirja Kühlewind's No Objection on draft-ie… Mirja Kühlewind
- Re: [bess] Mirja Kühlewind's No Objection on draf… Rabadan, Jorge (Nokia - US/Mountain View)
- Re: [bess] Mirja Kühlewind's No Objection on draf… Mirja Kuehlewind (IETF)