IETF Logo Mail Archive

Re: [bess] Warren Kumari's No Objection on draft-ietf-bess-evpn-vpws-13: (with COMMENT)

Eric Rescorla <ekr@rtfm.com> Sun, 07 May 2017 20:54 UTC

Return-Path: <ekr@rtfm.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 75A971279E5 for <bess@ietfa.amsl.com>; Sun, 7 May 2017 13:54:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 FwlFu8fiL6Ys for <bess@ietfa.amsl.com>; Sun, 7 May 2017 13:54:08 -0700 (PDT)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (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 A513A128D19 for <bess@ietf.org>; Sun, 7 May 2017 13:54:05 -0700 (PDT)
Received: by mail-yw0-x22c.google.com with SMTP id 203so21660110ywe.0 for <bess@ietf.org>; Sun, 07 May 2017 13:54:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=CHUEkeGgqqX+6SxG02d0NQEF6wENEy+DKxEk4Lj2TaM=; b=TlOgKmKmxtAE8KO4NqolEkqEq6Oaun4ajHNCbp8nPuX1uXrtudL11QZRD4AHAqXeYL R7EPq53IBj7fjFySJY3n1ZhRsP/LqjL5N+HLw0iF67pVrGoS96rUC43FaAVQZcHedIuj 5LdXdCYW1M+E46IAy3ObbFbTHx6ICweC7iyrj6wR/n9Y9uS0h9/Av1mm9GD9A5SyFb7t hF6g/hxpaPjhBEIcdYD/yMQvjXVDMUBRF1ZWiC2BogmRkuqZWrog9Fd+J322CAt6551D n0k8WwZBG1Q23X7kNoVUxPNUHQ6A+mthvQBxhWSNaYYTg1w4PQin/dcWzCvIuhCrEGFQ na1Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=CHUEkeGgqqX+6SxG02d0NQEF6wENEy+DKxEk4Lj2TaM=; b=bsqmd47+Q2FQQTnHxxWET6ceGN67UIGXJ2v2eE1Tyb3z1Ad4kQCQTQeSRre5K75pB0 zNmocdXBLcduTxxsNFBmqk6pl7LiWbNGu/TUZMtBmFGLNGMGRtf0I4p6++uiZQX51oyA bNohhm+wAD3Oco9m1mzHOy1BWSnhyiEKVlk7tGILBFJlQf54XQeLt+Z7YG1RxzLdYDDk pflTNna+lgv90xnJ7oYmJGqRqdRkgbsZazBGMfB2y8ZovdiVj06r94jXS/nqPZN6weDE zuV0O0mU9+Cfly49EPox9Ut2aWg5bWFgcyuPsXvOLFcdZ/VNESX7X8Qo5d6VRbNLpPSa ZeLQ==
X-Gm-Message-State: AODbwcAPWbHmvRqBS6UPVBxCAsW22vil/WyeD5+FhqWfPawkBi6pOQk4 cGYJv3R6OfKPhr7Q7VDi54CVtWVEBA==
X-Received: by 10.129.146.210 with SMTP id j201mr5611665ywg.3.1494190444897; Sun, 07 May 2017 13:54:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.131.150 with HTTP; Sun, 7 May 2017 13:53:24 -0700 (PDT)
In-Reply-To: <CA+b+ERk6kjqNAm=9ACHutAUBGRJ0DGLxHeyUo2btGRfJYGh4Sw@mail.gmail.com>
References: <149417673555.23196.14417727329971821809.idtracker@ietfa.amsl.com> <CA+b+ERmHn-08F5pAFrZ7zwg-cPgiES5WX5i1FXTXCOHEsNBrnA@mail.gmail.com> <CAHw9_iJVi1v24j77hHE2LK7UCQZYPheXfSYMS03kOazkcgPzCA@mail.gmail.com> <CA+b+ERk6kjqNAm=9ACHutAUBGRJ0DGLxHeyUo2btGRfJYGh4Sw@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sun, 07 May 2017 13:53:24 -0700
Message-ID: <CABcZeBPyy7G+A9tSrZTo=3SkFoEsxZ8s24ZNsF=C88Q7rP1dJA@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
Cc: Warren Kumari <warren@kumari.net>, draft-ietf-bess-evpn-vpws@ietf.org, "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>, The IESG <iesg@ietf.org>, "Alvaro Retana (aretana)" <aretana@cisco.com>, bess-chairs@ietf.org, "bess@ietf.org" <bess@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c092a40b1f202054ef55210"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/pVkuf6pXi8NxaryhqVkzlfvq6c4>
Subject: Re: [bess] Warren Kumari's No Objection on draft-ietf-bess-evpn-vpws-13: (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: Sun, 07 May 2017 20:54:09 -0000

On Sun, May 7, 2017 at 1:05 PM, Robert Raszuk <robert@raszuk.net> wrote:

>
>
>> is there any reason for the authirs *not* to make things easier for your
>> readers by saying: "
>> This document describes how EVPN [RFC7432] can be ..."?
>>
>
> ​That clearly is a good edit suggestion for all alone occurrences of
> [RFC7432] in the draft. ​
>
>
> That sounds like a fine idea - perhaps the authors should add something
>> like "Readers of this document are expected to be familiar with RFC7209 and
>> RFC7432."
>> Mainly I don't understand why we wouldn't want to make it easier for
>> someone new to the technology...
>>
>
>
> ​I think in number of IETF drafts extending existing specifications there
> is an implicit assumption that the reader is ​familiar with the base spec
> or specs around it related to new work.
>

I'm sure this is true, but as someone who reads a lot of specs, this one is
unusually
reader-unfriendly to someone who is being asked to pick it up and review
it. It's
not unreasonable to expect that:

1. Acronyms be expanded on first use.
2. Terms of art come with citations to where they are defined.

-Ekr

v2.23.0 | Report a Bug | By Email