Re: [trill] Alvaro Retana's Discuss on draft-ietf-trill-smart-endnodes-10: (with DISCUSS)

Donald Eastlake <d3e3e3@gmail.com> Tue, 13 March 2018 20:47 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 BC036126D0C; Tue, 13 Mar 2018 13:47:23 -0700 (PDT)
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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=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 60NS9PWHnD3A; Tue, 13 Mar 2018 13:47:22 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (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 AEC91126C89; Tue, 13 Mar 2018 13:47:21 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id i194so413084wmg.1; Tue, 13 Mar 2018 13:47:21 -0700 (PDT)
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=x/CGRmmkXI/V36ZL5SumTylP3Kf3eEcqMhHThCesbQU=; b=GnZZ0J3IT1QuUkFQTaMPqlD+r67PGC84HZMdX87i7iFoPyS1ZczBnlmqoxr/GJiB3n MF76AByyEXilJ/+dr86LnopmiVuDMrdtS+F23ir1ucw1Ecr1s6VZjIsacSgtK1gZ6NnO fK3Wz7TuAAqAUbqA8xjlXvq89p9hjLTDAvLpw4NAqrVOReypeEzIIjyTgMSeVftJBIlC iUOSz/Yt1ENRSEY8379ibeTpmGXRHlPP1wu3xPVcmEU7Z+h0xHs/I024Cr75deNja4bZ EIlUbxDOXO/21X6sJhYm+e4ubYUYNH/lD1SMuT8vDjUaba5ITDq4DZve0o8TzgT7Th6j eQug==
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=x/CGRmmkXI/V36ZL5SumTylP3Kf3eEcqMhHThCesbQU=; b=Xhh/IWJjeSnlZIdm/3IDsosoCktZgQ3HLYFjhd830X+WggBdwu30Qmc75/2MxDlPqW xxaQx59WsLOdL+bel+DWTHIGfx9WT12eR5oCrDbaB1aW64M7iqecrjL5u8gVa53FJwEm n2eKVCDn8bZWFrEygj4rp1/uKLMF52UQR5H5AxiB74s5EYbSFfxns7M1sAe+gPbE5PuE 4EBg2/Uzjuyo/kaIIDqUwL+YC510pXlDCIn+MagV4J5/9xDuspHxLDKlbhyAw83d3ZjU IgUSvR4Xwc2hcFdx6aCL0R9b1vu0KlVdKHbCAacg3+y3oClUOSGdEb4CdF0P4ZCzXa+A OpTA==
X-Gm-Message-State: AElRT7Gde56GQ4y6uOO4SvNGW5yeEIAnUv1Pqm9riiNhw67hVhT2DA5y +XMVL4MlTciDpROSZFpjkThhMb15Jvd6bZmo0CA=
X-Google-Smtp-Source: AG47ELtqoirJtWxWGHPaCKg+9F84vk2NhRuLqbjEh9Ki8r/dzT1c0K4BsKuE4fAKwcbvFqUjagmbD91D7rdBDzWQZ98=
X-Received: by 10.80.150.2 with SMTP id y2mr2216168eda.114.1520974040063; Tue, 13 Mar 2018 13:47:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.170.11 with HTTP; Tue, 13 Mar 2018 13:47:03 -0700 (PDT)
In-Reply-To: <CAF4+nEGbGebfdDZ4Ktk62VeE7YC+Jktd1fpEckO6jrV_Deo6Jw@mail.gmail.com>
References: <152028566673.31723.3025539385493024777.idtracker@ietfa.amsl.com> <CAF4+nEGbGebfdDZ4Ktk62VeE7YC+Jktd1fpEckO6jrV_Deo6Jw@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 13 Mar 2018 16:47:03 -0400
Message-ID: <CAF4+nEHu+Wi7-O+qwKtUePayEL-C6nESZPatLxXMps0emoh4OA@mail.gmail.com>
To: Alvaro Retana <aretana.ietf@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-trill-smart-endnodes@ietf.org, trill-chairs@ietf.org, Susan Hares <shares@ndzh.com>, trill IETF mailing list <trill@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/b7EKzrR8NLlDFVZVrjseXNgiEX8>
Subject: Re: [trill] Alvaro Retana's Discuss on draft-ietf-trill-smart-endnodes-10: (with DISCUSS)
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, 13 Mar 2018 20:47:24 -0000

Hi Alvaro,

A -11 version of the draft-ietf-trill-smart-endnodes draft has been
posted. Could you look at it to see if it resolves your Discuss?

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


On Wed, Mar 7, 2018 at 2:56 PM, Donald Eastlake <d3e3e3@gmail.com>; wrote:
> Hi Alvaro,
>
> On Mon, Mar 5, 2018 at 4:34 PM, Alvaro Retana <aretana.ietf@gmail.com>; wrote:
>> Alvaro Retana has entered the following ballot position for
>> draft-ietf-trill-smart-endnodes-10: Discuss
>>
>> ...
>>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>> This document feels tightly coupled with
>> draft-ietf-trill-directory-assisted-encap, even though there are no
>> cross-references.  If I understand the mechanisms correctly, a Smart Endnode
>> (discussed in this draft) can then do directory assisted encapsulation
>> (described in draft-ietf-trill-directory-assisted-encap).  In fact, the
>> encapsulation/decapsulation seems to be the main motivation in defining a Smart
>> Endnode.
>
> There are similarities, but I'm not sure I would say that
> draft-ietf-trill-directory-assisted-encap and
> draft-ietf-trill-smart-endnodes are "tightly coupled".
>
> trill-directory-assisted-encap is the best you can do with no changes
> to RBridges as specified in the TRILL Base Protocol [RFC6325]. Special
> end stations can do the encapsulation but edge RBridges always do the
> decapsuation.
>
> trill-smart-endnodes requires additional mechanisms in the edge
> RBridges to shake hands with the smart endnode, recognize when a
> destination MAC is being handled by the smart endnode and just forward
> it without decapslation, etc. As a result, this also support smart
> endnodes that are fine grained label aware.
>
>> I think then that this document also falls short in the exploration of
>> potential issues, so I am also balloting DISCUSS.  The same cases that I
>> pointed at for draft-ietf-trill-directory-assisted-encap [1] are applicable
>> here -- with the added caveat that the Smart Endnode, in general, has other
>> sources of information (learning, etc.), which means that there are potentially
>> more doors to close.
>
> OK, similar security consideration text improvements can presumably be
> made to this draft.
>
>> The Multi-homing Scenario (Section 6) adds some complexity to the ability to
>> check whether the Ingress RBridge is set correctly in the encapsulation.  It
>> would be nice to explore this case a little further and highlight the issues as
>> the topologies get more complex.
>>
>> As I wrote in [1], I don't think that there are easy mitigations for these
>> issues, but at least mentioning them so that operators are aware of the risk
>> would be enough to clear this DISCUSS.  Given that the authors partially
>> overlap, it may be a good idea to solve the issue in this document (which is
>> the general case) and then just have the other one point this way.
>>
>> [1]
>> https://mailarchive.ietf.org/arch/msg/trill/xZvEj_9FtSgHSp4DnKCVxr670gc/?qid=1e5a9496ac80237a3f7cc6aeea09d24d
>
> Thanks,
> Donald
> ===============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com