[trill] AD review of draft-ietf-trill-over-ip-14

Alia Atlas <akatlas@gmail.com> Tue, 20 February 2018 23:55 UTC

Return-Path: <akatlas@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 D39A012E044; Tue, 20 Feb 2018 15:55:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=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 JXho3XZ0VF0x; Tue, 20 Feb 2018 15:55:13 -0800 (PST)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (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 4766512E042; Tue, 20 Feb 2018 15:55:10 -0800 (PST)
Received: by mail-oi0-x235.google.com with SMTP id f186so3834939oig.4; Tue, 20 Feb 2018 15:55:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=N69HuPU9z0BOz/+KJcs1jXFQVMhTrNM/EJzzWatu2EA=; b=NK+QHmr7qHiZxGdHcRwR92FFqh6kns+Kb1lDcAUDle3R9Pqm1Av4U5t5X2MRU0ySc9 aCnfpgtvdBOae15ZS110cVBE4gIUYRsCLgRvKYS7lLl256wcFUNYIPNTkjj+oadPXnuY K3wZJrpRp7CxEduyI0XLbOTtgJwt/efLuwZLLkp8q/An8efXlCmSSLAwWvwe4+l3Gz0B UA3SvZKMQ13IBt7wasvsK1HqTK9c0oMy+BO+AeaxqA+vz4MWM5r1uVFVYaz2c7apWv9j PeNrGLvnA+WFTx9LL6r2j/7DLKAqI+0swkNOKzY1cstMcNjcug/wNWRebI9lHwBygqCF keHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=N69HuPU9z0BOz/+KJcs1jXFQVMhTrNM/EJzzWatu2EA=; b=ZmU8zhFhz9hSz/82yl88lI35wB0LiJg9L1pNac/Ap6hYRUzac5ISgSXm08Oxn0FXoA 6OJ/EYf4Ju4gEXrQczupiJzTqy+6JWYMyePpE++yvWjqixa3FO23sUnKnfw3Ta+aFeZ5 DShTcS2V0S38eWD0QSiLywY6uSTBZZRGg/BA0TAtSoHqQQJt2nJda+aAhKvml0koGPj4 G2PzVUiDemyGn1TUrjehz1E7VtL/tKrnxNBadaqdqdHOpH0qlG2Z7GZ8DqZfiyH13meC ovby3Snmiepx8OkmKm3u+MUR8tLE02RqNwObm1Hp3WBlIOb+FQwj5l5FnKNTRLRJvAlF Y/Bg==
X-Gm-Message-State: APf1xPBVV/gVtc+wz6PDGVb2dpxQRessWIu+PoQ4rA07tS6Q6pI/YWKg zZkQMnJsWof8iDvT4Lj7acDVNReu/yn7xk4sCv3wM88k
X-Google-Smtp-Source: AG47ELu+j7Wbm5gprkYm6RSPuetZ8HQ1va6Oh2KHQHRXK0S2ADZWKCc0bNL9E8rQbJcoEXYWBbeTc5fzKo1WKVFOkDg=
X-Received: by 10.202.94.2 with SMTP id s2mr917260oib.248.1519170909129; Tue, 20 Feb 2018 15:55:09 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.68.57 with HTTP; Tue, 20 Feb 2018 15:55:08 -0800 (PST)
From: Alia Atlas <akatlas@gmail.com>
Date: Tue, 20 Feb 2018 18:55:08 -0500
Message-ID: <CAG4d1rdiOnQg2OVBPyd7gvup4pv3yNPr2YOAkmGKjz6GEd54HQ@mail.gmail.com>
To: trill@ietf.org, draft-ietf-trill-over-ip@ietf.org
Content-Type: multipart/alternative; boundary="001a113d5384644f430565ad8a1d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/8bKDlLebiH_diVLFxU7cofAYLSA>
Subject: [trill] AD review of draft-ietf-trill-over-ip-14
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
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, 20 Feb 2018 23:55:15 -0000

As is traditional, I have done my AD review of draft-ietf-trill-over-ip-14.
First I would like to thank the authors - Donald, Margaret, Mingui, and
Dacheng, as well as the reviewers for their work on this document.

I did find one minor issue (below) and would recommend a spell-checker to
catch several minor typos.  I will send this to IETF Last Call and place it
on the IESG telechat on March 8.

Minor:

1) In Sec 5.2: " An adjacency can be formed between two TRILL over IP
transport ports if the intersection of the sets of encapsulation methods
they support is not null. If that intersection is null, then no adjacency
is formed."
Given that Sec 5.0 says that the native encapsulation MUST be supported,
how can the set be null?  Is this the set of encapsulation methods other
than the native encapsulation?  Please clarify.

Regards,
Alia