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

Donald Eastlake <d3e3e3@gmail.com> Tue, 17 January 2017 14:22 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 919BC1294A2; Tue, 17 Jan 2017 06:22:15 -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 L3UEa_DUdks0; Tue, 17 Jan 2017 06:22:14 -0800 (PST)
Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (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 E3A12126D73; Tue, 17 Jan 2017 06:22:13 -0800 (PST)
Received: by mail-io0-x230.google.com with SMTP id v96so115489230ioi.0; Tue, 17 Jan 2017 06:22:13 -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=69EA2iYv/nlHmPBOqh4apb96GYpx8u6NQuzjxNOf3NM=; b=QPtXD3ZrmOeiFF08esAso5y9UIHlZE4zBIfaWdQnHf4xLN6wc6PamLVZqJB+BYz8/R l/B2AT4ZuZ9Ulou5NQTMFfYFRo4I9p7mYwOlX+Rfp0/vtYEsWAA/3cZMb2sWWy937g1m vaIWVdtVbuMcOlMIciLJih3rIhCYyFUkCrbvJ9wPD5qoDcbziv7NugHeKUz67RoOPnRk uTXIUVmskeqSE6AG4HBndnkMZbVvLopYu794pKtFEhxOojPg21UI3rCj7LK+kaHqbYfg DcaEaDF+6JQ/3W39NbP9UC/Z8F3O+J5mjkdoPeG7Z+CZyUN/bzXFo2oSUY/l2o8Wofbw Kb7Q==
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=69EA2iYv/nlHmPBOqh4apb96GYpx8u6NQuzjxNOf3NM=; b=Edh94eqWGP1Dmb6JM2nDcyKlR0tiK5StHNcmKZcvOAws9hxmn7s8PDuBJZZnzggL3d xC3KojeYslIRZNTK+V0vz6Qq0IgMr9loBchzoJRdqa6m+S6r8mW9VbzQvWR6EieV7Xht YqYatXSXvfA6PTOIIdctdJwvdXO1Re6mXWQ6Jvd3eB8NTifK+FWRsF3xCI8e3BtHpH41 gsVpahUgGYUZ7lDmPhKBWfzn9E2AM4R6yddlsnILSgFswQjcSAYAEHewzHmNjPaDA80w /2MGKeK64OgsLtX7Ae4eTCxkk+GfYAKApS6iYN7kQq8HLtC/ZGMy8DtaRPRT7wGSJShr euZA==
X-Gm-Message-State: AIkVDXL9alwartGW2uEaZ6Ef/iq3PTGEaU/tvPgy0WlfllD8CcVC1COkkbEyzIBp/CXEs7bLvPWx42CiVRSAIQ==
X-Received: by 10.107.141.80 with SMTP id p77mr34468141iod.97.1484662933082; Tue, 17 Jan 2017 06:22:13 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.41.72 with HTTP; Tue, 17 Jan 2017 06:21:57 -0800 (PST)
In-Reply-To: <148461258839.22482.5195721834167205640.idtracker@ietfa.amsl.com>
References: <148461258839.22482.5195721834167205640.idtracker@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 17 Jan 2017 09:21:57 -0500
Message-ID: <CAF4+nEGGbbGN0xG_=bLAMVxrd5UMLKARSeo++3j_a++3dQA4-w@mail.gmail.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/xZ3SUF4y4aM4CJzu97iYJsLNr8g>
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 14:22:16 -0000

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 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