IETF Logo Mail Archive

Re: [bess] Ben Campbell's No Objection on draft-ietf-bess-evpn-vpls-seamless-integ-05: (with COMMENT)

Ben Campbell <ben@nostrum.com> Tue, 22 January 2019 16:37 UTC

Return-Path: <ben@nostrum.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 CD9F612E043; Tue, 22 Jan 2019 08:37:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.678
X-Spam-Level:
X-Spam-Status: No, score=-1.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 cEY9a0HrEHol; Tue, 22 Jan 2019 08:37:30 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 AFC67130F3C; Tue, 22 Jan 2019 08:37:30 -0800 (PST)
Received: from [10.0.1.29] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x0MGbNCf064900 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 22 Jan 2019 10:37:24 -0600 (CST) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1548175046; bh=mLgGbHL+5N6pZjmEEXhZlcuSqFOc3+nJWkxdjbhfRww=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=ozQvy95cFj10AII5gZOe728t3ok4UANZ3WM4UOLHTTqkwQ2pxymYbKn7cf0InWnzv CKj2Hl31aWnoD6NdmzlyiQBmSsFvK+ktsD2MF+/NmKkrKa9l/f8uWwxf3FwHlYma1K jlzvwMGdgNsXqqoyjgBAkAQ4J3poUmjcbjrSv8Kk=
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.29]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <7407EF02-00A4-4833-B72E-D489B41AEFDB@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_995493A3-A99D-45EA-B73D-3A237EC8ED9D"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Tue, 22 Jan 2019 10:37:21 -0600
In-Reply-To: <8A90020D-0DA8-4AA7-9C0B-60F3CBD62152@cisco.com>
Cc: The IESG <iesg@ietf.org>, "draft-ietf-bess-evpn-vpls-seamless-integ@ietf.org" <draft-ietf-bess-evpn-vpls-seamless-integ@ietf.org>, Matthew Bocci <matthew.bocci@nokia.com>, "bess-chairs@ietf.org" <bess-chairs@ietf.org>, "bess@ietf.org" <bess@ietf.org>
To: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
References: <154706930344.4846.8863021546657846056.idtracker@ietfa.amsl.com> <8A90020D-0DA8-4AA7-9C0B-60F3CBD62152@cisco.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/xTgWzkoteWDbh4C577JOZ2I09aU>
Subject: Re: [bess] Ben Campbell's No Objection on draft-ietf-bess-evpn-vpls-seamless-integ-05: (with COMMENT)
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, 22 Jan 2019 16:37:33 -0000

That all sounds good, thanks!

Ben.

> On Jan 22, 2019, at 2:59 AM, Ali Sajassi (sajassi) <sajassi@cisco.com> wrote:
> 
> Ben,
> Thanks for your review and your comments. Please refer to my replies below marked with "AS>".
> 
> On 1/9/19, 1:28 PM, "Ben Campbell" <ben@nostrum.com <mailto:ben@nostrum.com>> wrote:
> 
>    Ben Campbell has entered the following ballot position for
>    draft-ietf-bess-evpn-vpls-seamless-integ-05: 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-vpls-seamless-integ/
> 
> 
> 
>    ----------------------------------------------------------------------
>    COMMENT:
>    ----------------------------------------------------------------------
> 
>    Thanks for the work on this.
> 
>    I support Alissa's discuss.
> 
>    §2:
>    - The 2119/8174 keywords in this section are not used according to the RFC
>    2119/RFC 8174 definitions. The RFCs talk about requirements on implementations
>    to achieve interoperability. This speaks of requirements for the standards
>    process. If the working group prefers to keep the use of keywords in this
>    section, please add some additional text to the 2119/8174 boilerplate to
>    explain the usage. (My other comments on the section assume that the normative
>    keywords will remain.)
> 
>    - Req 2:  "The solution MUST require no changes..."
>    I suggest "MUST NOT require changes"
> 
> AS> Changed it to: "must not require any changes to ..."
> 
>    - Req 5: This doesn't seem to state a solution requirement; rather, it
>    describes an action that VPN instances may take. Is the solution requirement to
>    allow this behavior?
> 
> AS>   moved the 2nd part of the paragraph to the solution description under sections 3.2 and 4.2.
> 
> Regards,
> Ali

v2.14.0 | Report a Bug | By Email