[trill] draft-ietf-trill-channel-tunnel-01.txt proposed change

Donald Eastlake <d3e3e3@gmail.com> Mon, 01 December 2014 19:14 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6097F1A8970 for <trill@ietfa.amsl.com>; Mon, 1 Dec 2014 11:14:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 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, SPF_PASS=-0.001] autolearn=no
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 i66auKbK2UmJ for <trill@ietfa.amsl.com>; Mon, 1 Dec 2014 11:14:38 -0800 (PST)
Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A78141A8982 for <trill@ietf.org>; Mon, 1 Dec 2014 11:13:50 -0800 (PST)
Received: by mail-oi0-f44.google.com with SMTP id e131so8003828oig.31 for <trill@ietf.org>; Mon, 01 Dec 2014 11:13:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=jBgT1srK8yW5NEuKK2nAmoA0F6UVhfb1zIPOKGIX0Jc=; b=nd+U0hSqOniXOy+z7Cj0oUoMx4p03ogoHy8yla75HB6OL0yybs2X0pGL6RlCgr26zw Hh1fKuABO4Pg/FZDs3aYiNKPJDyiJM+MK8RzhJZahD6Xa+yCuZhLdteDZnpJmlrNIXTr nOQshqo8BpPRMOZg8O1PtsPk2J0KrXg3pek+o5BAkNh7zXf8pN19ZRMjoVzojcJRvdy3 lwfTuLCJg/E6u/Njkd1QJ31zfS6d2XMSxGlpTE9Ca602JmBWnFGXBDy4GtqOKt+AKUBu /MrDIJNKOA596aCX9J1t6qIhp1AB7YeubJUMDCXgmp50qmQ/yR0fYxkZrClCjmt6cmFy PWVA==
X-Received: by 10.182.60.162 with SMTP id i2mr37668927obr.20.1417461230044; Mon, 01 Dec 2014 11:13:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.145.4 with HTTP; Mon, 1 Dec 2014 11:13:28 -0800 (PST)
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 1 Dec 2014 14:13:28 -0500
Message-ID: <CAF4+nEHXDzWAi=+JYQq=qc7a0BH6UX+nj5f68biy9dRky_A5Zg@mail.gmail.com>
To: "trill@ietf.org" <trill@ietf.org>
Content-Type: multipart/alternative; boundary=089e01681e7a198d5405092c69ce
Archived-At: http://mailarchive.ietf.org/arch/msg/trill/uv2sozO3yK_SJdQ6ctv1fytUrYE
Subject: [trill] draft-ietf-trill-channel-tunnel-01.txt proposed change
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 01 Dec 2014 19:14:39 -0000

Hi,

As I mentioned at the TRILL WG meeting in
November, draft-ietf-trill-channel-tunnel currently covers three separately
optional extensions to the RBridge Channel facility [RFC7178]. These three
are: (1) a general set of payload types, (2) security, and (3) "scope". As
the draft is written, you could implement any one, two. or all three of
these although there is one default payload type (a nested RBridge Channel
message) that is mandatory. Of course you could also implement none of
this, since it is all optional. (Scope has to do with things like providing
a default way to send RBridge channel messages between end stations and
TRILL switches that are not on the same link.)

The security extension and the default payload type are needed to provide
security for pull directories
[draft-ietf-trill-directory-assist-mechanisms] but there is no current
requirement for the "scope" feature. I think including scope in this draft
unduly complicates it and will make it less likely to be implemented. So,
as the primary author of this draft, I plan to remove the "scope" feature.
It could always be added later through another document.

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