IETF Logo Mail Archive

[trill] Comments on draft-ietf-trill-transport-over-mpls-06

Donald Eastlake <d3e3e3@gmail.com> Tue, 16 January 2018 23:05 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 2397C12EB83; Tue, 16 Jan 2018 15:05:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 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, 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 Pf0VMz4IULUf; Tue, 16 Jan 2018 15:05:22 -0800 (PST)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::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 7CB0A12EB7C; Tue, 16 Jan 2018 15:05:22 -0800 (PST)
Received: by mail-wm0-x234.google.com with SMTP id r78so11943437wme.0; Tue, 16 Jan 2018 15:05:22 -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:cc; bh=Thc3PqSQDS021oRS2BxwQDVCcr23gcyUbakSEo9TA7M=; b=rMjsHZ5UxhOeFj2IU+hdK2W8snredgEtDE8UAanF4aMKTWnp+XEyXSRafj/ib3LCmW Ov2shFHfLPS5QPBonP8mdnSHefRM1lISlYc3bQrBSuefSP5KAO605gl9qrFkLmLKS6mp 8bpiSclmX++lda2kagldVMwujREEiFBbSLkbltBLPM4F1JnK/hnYCvicVlJJnz13H+SI AUeqOQVsFHI3zdgY35+4afeI3J4XFKwLpPA1BHom5qzNzXJHGqQfoozd4NpLYVZFgItX Hna7p8dQ6sjoTZOyu4lBhot4rVsNOqCXHmr1bCXenaVs+S1632QS7lratnlbSFeJ/wAn NgSQ==
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:cc; bh=Thc3PqSQDS021oRS2BxwQDVCcr23gcyUbakSEo9TA7M=; b=EdBFAlwcJjsKeTDmYMH/GCbUe6r8bLOwiO/LXEGichPdSLRUWXx5fLmUFKaguJIhf1 0JfIm4MtHlp21D8hm1URLUcOlg1k7CKNINa2LPQ2V4M13JDVPUhif6xAs8fQw0BsB1s4 +FZURNJvfqUvhqlXHdbgbSD23Iu4ZxMSzgLlURTQUvT31ALeAfIjOAy6L6MdRFPeko5D 4BWy3/fnvnWcNe0VAUBhRJvC8E+ERZS+frVCgBjQLzKcVKiie0NrseRO465b7igWHF2C 4h2bU5njAo858JAgHJZrFcOty3wj8yHb/keDfD/Sb3Wg5xUHZjyw/8LHutWSSML9eOjx SnWw==
X-Gm-Message-State: AKwxytdqU4g7Tn6Y25bYnJ3GcbswdKkqzXUZT7DZBQch/TrieBk7rRD8 2D3+DPjA00agiLpO9Vk00UPFTMT3lXKUldCX5RO90w==
X-Google-Smtp-Source: ACJfBou4fQmhnqtgrNxtW6CzoRk6BFQXfOoEdT0I0O5bXkM3W9fSBA9SYRoLMHzLelg41zzY/qwgLrFZFgItGGD5wCo=
X-Received: by 10.80.137.178 with SMTP id g47mr32472edg.100.1516143920769; Tue, 16 Jan 2018 15:05:20 -0800 (PST)
MIME-Version: 1.0
Received: by 10.80.154.69 with HTTP; Tue, 16 Jan 2018 15:05:05 -0800 (PST)
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 16 Jan 2018 18:05:05 -0500
Message-ID: <CAF4+nEG+pPq7X=w2xvJNN4hC3BpObevw5YXwu1TjuOzKJpAY8Q@mail.gmail.com>
To: trill@ietf.org
Cc: trill-chairs@ietf.org
Content-Type: multipart/alternative; boundary="f403045c29fed36d840562ecc357"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/UbXOMU1oi5WvoIE-Kvp2eAqpWxw>
Subject: [trill] Comments on draft-ietf-trill-transport-over-mpls-06
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, 16 Jan 2018 23:05:24 -0000

Hi,

There are a bunch of RFCs referenced in this draft but not listed in the
References section. They need to be added to the References.

I think the Security Considerations section, while it provides a good set
of references, needs one added sentence: something about how the document
does not change the security considerations because it uses existing
standards without change.

Section 5 is very short and seems like it could be moved up and merged with
the Introduction. (The section number of the following sections would be
reduced by one.)

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

v2.23.0 | Report a Bug | By Email