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

Donald Eastlake <d3e3e3@gmail.com> Tue, 21 February 2017 19:30 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 A5A22129489; Tue, 21 Feb 2017 11:30:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 Y88U5owrpIz3; Tue, 21 Feb 2017 11:30:28 -0800 (PST)
Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (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 A9AEA128AC9; Tue, 21 Feb 2017 11:30:25 -0800 (PST)
Received: by mail-it0-x234.google.com with SMTP id 203so123367367ith.0; Tue, 21 Feb 2017 11:30:25 -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=CdhTXG0H7lD7K5dBjij6HejAWy+JR8SZs3Ef7NWlz28=; b=QRB74GIV24tKfw9gIg+snVNxj4XtB3lCzdGInEnpaJtLTFvZnkiiiowH/hOj0oFfYT Gb7g6skdd4QHxUIzaIp2EnGI/1Mqqj6Rq0NXCGIUajy4tqLrmKWa0IRitiYTluPBkE96 IS2Fse+xc/JIJ+0BNdqf5wbw6P+4QOLTXbepLv3ZRqr2zGSTFXAFs8KgjNhGAf9En6W1 WAGiFmrk8N1k9WE2lciaaTHec+e1FBPB0qom8K6JGiHR+OANA4Z8DwoxR1LT8y/zIoKB rPrfvBzPSGr7mXjgh8hFpDo9n+GcT8gkwvEzf9Mtwra/g279xKQgsyN9zxM7JGkYcxVn xYPQ==
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=CdhTXG0H7lD7K5dBjij6HejAWy+JR8SZs3Ef7NWlz28=; b=VTM+tpCCshJpx0i44xTu2OvPJx5FRViKBKAjvVEcQesWX63kPLaZbKBpmZYNCHPlcn qDhDsskFhf7BS5a1n26pHL/cD8M/haLLwchTQ2EGVItgHL71ngXwkPfoVEUcO7003a2l 6rEGYIR05FMnm8+RsSl75ePDWYDsAT+ok522UCG8KxfoHWbqtnG5Pry0MiPMuynRZOC6 NJVdfHPoNwQMKyIn0brxceP53nrinaM/Ws6Tg0hnlGQG5EAHHHwPK6aYKdE7ecXVm9nq 6sGpJ4hN+IPlScTN0urOjYfTF0/hS06sj9KfUH4NjzzODnUx43lK1/xWGrG+ExY+Ud2a qLIA==
X-Gm-Message-State: AMke39l5wQks14pvy9jaNbzvEWvw02IsKJLcBJU/XNaUFLOUhvufcd9E5YbFBgk0JVSadZMfulMPBa25jicPjA==
X-Received: by 10.36.47.213 with SMTP id j204mr28424796itj.7.1487705424839; Tue, 21 Feb 2017 11:30:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.32.148 with HTTP; Tue, 21 Feb 2017 11:30:09 -0800 (PST)
In-Reply-To: <CAKKJt-dcDhiY5hDQYPEkWAniUcGBqcP49VBHBYNHqEu1a0uGiw@mail.gmail.com>
References: <148461258839.22482.5195721834167205640.idtracker@ietfa.amsl.com> <CAF4+nEGGbbGN0xG_=bLAMVxrd5UMLKARSeo++3j_a++3dQA4-w@mail.gmail.com> <CAKKJt-dcDhiY5hDQYPEkWAniUcGBqcP49VBHBYNHqEu1a0uGiw@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 21 Feb 2017 14:30:09 -0500
Message-ID: <CAF4+nEF7BsvDxuQnu+t2wjxvZgR8m6sDS8R1pfzz_Q5BZqRTfA@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/s3eHQTLh52FWE-i2I-EQNOO7eGY>
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, 21 Feb 2017 19:30:35 -0000

Hi Spencer,

Version -05, just posted, is intended to resolve your comments.

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


On Tue, Jan 17, 2017 at 11:42 AM, Spencer Dawkins at IETF
<spencerdawkins.ietf@gmail.com>; wrote:
> 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
>
>