Re: [trill] Shepherd's review Review of draft-ietf-trill-rfc6439bis-02.txt

Donald Eastlake <d3e3e3@gmail.com> Thu, 11 August 2016 04:01 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F6BF12D5B2; Wed, 10 Aug 2016 21:01:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 MAnpFS_80Etp; Wed, 10 Aug 2016 21:01:36 -0700 (PDT)
Received: from mail-ua0-x232.google.com (mail-ua0-x232.google.com [IPv6:2607:f8b0:400c:c08::232]) (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 0635612B056; Wed, 10 Aug 2016 21:01:36 -0700 (PDT)
Received: by mail-ua0-x232.google.com with SMTP id 97so101783068uav.3; Wed, 10 Aug 2016 21:01:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=azLM7atsHkM+dpRULbKsXyhM0kNcbeMD2FBVBclEARg=; b=wQardiStW33mO4tXO4pq9q+pug7pxDUFk4PqNUJOWZ8CqoHeO+nj23WjLc2W1yt7Hd UKvN0qwHjmCLMSnijRP+4sB7ZFAwYu+gCr71E8fpP99MbNZtgYrh5M70VuOC3focFqer pkR03kx8NsEP9uLZVAgkgnTFjDgD205r6SYJc4ENuDDR3cB/R7qiyWmywwiFLe6FRujB 45sumEro+slI1rwFnM5PRCXuzWrezLcE5Tio6bvRMxr5zhNcmcVbksem8XeyKj/rw8IQ kAvH8D+2cuR747HZBdOocKAb2AiLAR26KU/UCUMKL/K1Ov8++9pOkfSgqoDNo/5HRODX yhgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=azLM7atsHkM+dpRULbKsXyhM0kNcbeMD2FBVBclEARg=; b=aLx5VMi0llcNxwrj5owlNhbnrmFCVk0fx1eqi0E5A9lwcDl2qJPpmvPnrfRjhW/eEc lMRSe3J2U75BXSsSuYtDrieyw4sOrpgxSxGfv9GCTHA5WxDfKw+VD70AxgtK17N08ovi GXBX0bWEBxpTnToovkR3wUcBgBdyHXlkA01gaDYvE1s/omWO1Qu1qL0xKl4IQhUL5xr4 xjhfyT1XulT+kN4JtXuOuB8sOyX3mNFXrEqv0aElkgFkci1rnLe2yG0oUIHn8rP2rlsk bt7tr7j9ngh0Pt/oLqsy6t9bbVe8dP8kNX/4Er/DAj6NJmp7o+2HtCM7EvvQgI7ww7KX /t2Q==
X-Gm-Message-State: AEkoouuyH3y8e7tXq4GKLh+PxV5H+SeW2BuJHz+qZREv/Y1uWVJr13zfiXGY4gaeVhXnK+Fux8ikPuaIgN669w==
X-Received: by 10.31.179.209 with SMTP id c200mr3685057vkf.124.1470888095024; Wed, 10 Aug 2016 21:01:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.104.2 with HTTP; Wed, 10 Aug 2016 21:01:19 -0700 (PDT)
In-Reply-To: <0a7e01d1f33d$a4874c60$ed95e520$@ndzh.com>
References: <0a6801d1f33b$dc589d30$9509d790$@ndzh.com> <0a7e01d1f33d$a4874c60$ed95e520$@ndzh.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 11 Aug 2016 00:01:19 -0400
Message-ID: <CAF4+nEEE4Tq0dEpHefXyabKevqykyzx7BWFZxLupywxaV31_Cw@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Content-Type: multipart/mixed; boundary=001a1143ad7c6941300539c3d2e2
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/w0z1ywltjdrmFAJMazXKgWJEM4A>
Cc: Jon Hudson <jon.hudson@gmail.com>, draft-ietf-trill-rfc6439bis@ietf.org, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] Shepherd's review Review of draft-ietf-trill-rfc6439bis-02.txt
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2016 04:01:37 -0000

Hi Sue,

On Wed, Aug 10, 2016 at 3:30 PM, Susan Hares <shares@ndzh.com>; wrote:
> Trill WG:
>
> I missed one other editorial change for RFC6439bis-02.txt.
>
> RFC7180 has been obsoleted by RFC7780.  This needs to be changed.

Well, the only reference to RFC 7180 is in Appendix B where it is, in
fact, talking about RFC 7180 being obsoleted by RFC 7780. This is why
RFC 7180 was listed as an Informational reference while the many
references to RFC 7780 are mostly normative and it is listed as a
normative reference. I suggest just changing "[RFC7180]" to "RFC 7180"
in the appendix so hopefully the nits checker won't notice it :-)

See below.

> Sue
>
> From: trill [mailto:trill-bounces@ietf.org] On Behalf Of Susan Hares
> Sent: Wednesday, August 10, 2016 3:18 PM
> To: trill@ietf.org
> Cc: 'Donald Eastlake'; draft-ietf-trill-rfc6439bis@ietf.org; 'Jon Hudson'
> Subject: [trill] Shepherd's review Review of
> draft-ietf-trill-rfc6439bis-02.txt
>
> Status: Ready to publish
> Concerns: None
>
> Editorial nits:
>
> Section 2.2.1 - paragraph 6 sentence starting with /should the VLANs - it
> would help if the sentence was broken into to sentences.

I think the best think to do might be to parenthesis the "example" and
then to indent the remainder of the paragraph after the ":". See
attached for what the paragraph would then look like.

> Section 4.0 - 4th paragraph - in the 1st numbered sub-paragraph - the
> sentence starting with /This is backward/
>
> Is "backward compatible" correct English.  My understanding is that it would
> "backwardly compatible" (adverb adjective-noun).

I think "backward compatible" is a common computer term. I suppose it
is some sort of compound adjective. How about if it is hyphenated?

> This sentence would also benefit from breaking it in 2.

OK.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Sue Hares