Re: [trill] Spencer Dawkins' No Objection on draft-ietf-trill-rfc6439bis-04: (with COMMENT)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Tue, 17 January 2017 16:42 UTC

Return-Path: <spencerdawkins.ietf@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 07F3C1299E6; Tue, 17 Jan 2017 08:42:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level:
X-Spam-Status: No, score=-0.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, FREEMAIL_REPLY=1, HTML_MESSAGE=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 xyQfIBo4658N; Tue, 17 Jan 2017 08:42:44 -0800 (PST)
Received: from mail-yb0-x233.google.com (mail-yb0-x233.google.com [IPv6:2607:f8b0:4002:c09::233]) (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 BA563129565; Tue, 17 Jan 2017 08:42:44 -0800 (PST)
Received: by mail-yb0-x233.google.com with SMTP id l23so45123014ybj.2; Tue, 17 Jan 2017 08:42:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=vFroCA6CbKOWlTeYrkkR+zSC5K1L+WxvaGxQFh9WYLM=; b=LN5RD+k19AtnwHi9IBHrE0v1Dj9xldtNK61Ha5oq1L/HOdMG3XfUDJrNza8EZJOOuz 6S1aqSvhM2+Q2GDj88sS1y9A8dWY69o0empT+QQTAriZggPr8g4brQ8ver5NkK/1oP1r PP5X0kQgn9gOQhc5ovmbAz7clX6PKWDkhVTBGmHRV8m3B8IF+hJT4UBjED+iwQFA9Jgd K4uXjeHt8GNKzI2wNgyvAIyxv0JNXpeHvgclBXaE4yUdQIfTDyhmR+c/v/b6vTC1SSbm qXWze12iF6xUEqqzdYLNEGljqNs8NiiEKPHVZcrjwSY31Pvld0cD/qn+uzhcmkZv0rEe 5++g==
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=vFroCA6CbKOWlTeYrkkR+zSC5K1L+WxvaGxQFh9WYLM=; b=rMCeZGWxRJaOfQmWzQP4LBkvt9WXSkRw3DKRvVGeXUpAdbH/FdIA+l738xcwqlFcZb Qqlz9FLpQOUQ73zHd/vENTK7OL1dzafz/okhud9hZ+weF0+c4egI2Lrqe47neoHykdsz I1PqqgTnGP1un+IIu6ABOL7oeMS+FRS2j75Homylqe2HRnZl+J5HvO2lSZQUDwiZniWQ BW3KHR0mb+Aiwdjn4dyFjnmYaLYWtW17vVVhXXuf7LuKBT9bjqrm7Wdq0KQdAYW0Qmfz NHpR1luemmjBEAXeY5XcqX/+LOkeH8Q0s2w6azvIYUWZJcUf/ongZKzGieNG+WVRb6m9 w9TA==
X-Gm-Message-State: AIkVDXLfz49GcOAqs9ZVejuSyqCyHbPMMU9Rkcag6TlZS5HtWwtGpr25aougaEigiq4P9Fez3OeeCn9Uy4f6QQ==
X-Received: by 10.37.92.68 with SMTP id q65mr25872327ybb.12.1484671363906; Tue, 17 Jan 2017 08:42:43 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.221.4 with HTTP; Tue, 17 Jan 2017 08:42:43 -0800 (PST)
In-Reply-To: <CAF4+nEGGbbGN0xG_=bLAMVxrd5UMLKARSeo++3j_a++3dQA4-w@mail.gmail.com>
References: <148461258839.22482.5195721834167205640.idtracker@ietfa.amsl.com> <CAF4+nEGGbbGN0xG_=bLAMVxrd5UMLKARSeo++3j_a++3dQA4-w@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 17 Jan 2017 10:42:43 -0600
Message-ID: <CAKKJt-dcDhiY5hDQYPEkWAniUcGBqcP49VBHBYNHqEu1a0uGiw@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Content-Type: multipart/alternative; boundary=001a1140f82041023005464cfd08
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/0ujIHUHaZe71hzHhHI1I_yVh6to>
Cc: "trill-chairs@ietf.org" <trill-chairs@ietf.org>, "trill@ietf.org" <trill@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-trill-rfc6439bis@ietf.org, Susan Hares <shares@ndzh.com>
Subject: Re: [trill] Spencer Dawkins' No Objection on draft-ietf-trill-rfc6439bis-04: (with COMMENT)
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: Tue, 17 Jan 2017 16:42:46 -0000

Hi, Donald,

On Tue, Jan 17, 2017 at 8:21 AM, Donald Eastlake <d3e3e3@gmail.com>; wrote:

> Hi Spencer,
>
> Thanks for the comments. See below
>
> On Mon, Jan 16, 2017 at 7:23 PM, Spencer Dawkins
> <spencerdawkins.ietf@gmail.com>; wrote:
> >
> > Spencer Dawkins has entered the following ballot position for
> > draft-ietf-trill-rfc6439bis-04: No Objection
> >
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> >
> > I had trouble parsing "output it to or queue it for" (this occurs twice
> > in the sentence).
> >
> >    However, it does not output it to or queue it for that link,
> >    although, if appropriate (for example, the frame is multi-
> >    destination), it may output it to or queue it for other links.
>
> It's kind of verbose but I believe that actual output port
> implementations typically provide for directly streaming out a packet
> even as other parts of the packet are still arriving at the switch,
> particularly in cut-through routing, or just sticking it in a queue
> for output later if the port is busy. Do you have any suggestion for
> better wording?
>

I was thinking that

    However, it does not output it to, or queue it for, that link,
    although, if appropriate (for example, the frame is multi-
   destination), it may output it to, or queue it for, other links.

might be clearer.

If the RFC Editor removes the commas, of course, you can slap me in Chicago
;-)

Spencer

>
> > I don't think the text is incorrect, just awkward. Perhaps commas would
> > help?
> >
> > In these three subsection titles,
> >
> >    3.2.1 Change Optimization One
> >
> >    3.2.2 Change Optimization Two
> >
> >    3.2.3 Settling Detection Optimization
> >
> > I found the title for 3.2.3 helpful, but not 3.2.1 or 3.2.2. Is it
> > possible to come up with more descriptive titles?
>
> That's a reasonable point. Maybe
>
>    3.2.1 Optimization for Change to Lower Priority
>
>    3.2.2 Optimization for Change to Priority Only
>
>
> > I found
> >
> >    For robustness, a TRILL switch sends a number of copies of a Port-
> >    Shutdown messages configurable from one to three, which defaults to
> >    two copies, at a configurable interval, which defaults to 20
> >    milliseconds (see Section 6.6).
> >
> > difficult to parse. Perhaps
> >
> >    For robustness, a TRILL switch sends a configurable number of copies
> >    of Port-Shutdown messages separated by a configurable interval. The
> > default
> >    number of copies is two, although this can be configured as one copy
> >    or as three copies, and the default interval is 20 milliseconds
> >    (see Section 6.6).
> >
> > ?
>
> Sure, that seems like an improvement. Might also be good to say "time
> interval" instead of just "interval".
>
> Thanks,
> Donald
> ===============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>