Re: [trill] Eric Rescorla's No Objection on draft-ietf-trill-directory-assisted-encap-10: (with COMMENT)

Donald Eastlake <d3e3e3@gmail.com> Thu, 08 March 2018 05:03 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 2A71D126CC7; Wed, 7 Mar 2018 21:03:08 -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 p9hDN82kI4YD; Wed, 7 Mar 2018 21:03:06 -0800 (PST)
Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (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 C74981201FA; Wed, 7 Mar 2018 21:03:06 -0800 (PST)
Received: by mail-it0-x233.google.com with SMTP id j7so6344239ita.3; Wed, 07 Mar 2018 21:03:06 -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=PVygi8WC9mEhnV0PKng4iOTcF3pDYR88fwBQ0l3yyAU=; b=DdRBrPAtsEnCXrBRjnKdG9zqqs3QymkiiGvjU8F1PgENXkmiGbNyxV87u5SdCIhEU/ NPftVV7AEu8hapSno46greDrmLTf2ecFkVJGKtUJimKCg0rd5X58cQbVxF5s5EwVPOJf JjuUx6y2B/xagrfwmyw4oNl+Rhss8KvLhFDlFH1ijbV3ZfH0pRmd8sJu8VS1j60qwB1V jk1M3WWXBDdNSD99bn6gOw7vdIWQFbQf9LaMql1sCM2eafLqgNT6ag3kUuNJsQAqAcj/ 24hoAKo5XWRCg2T1v6yffDhSurgl1FRFn8sGHxhwFvmfzoHeC5AA7CD0xMEd2xF3/fmQ YB0Q==
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=PVygi8WC9mEhnV0PKng4iOTcF3pDYR88fwBQ0l3yyAU=; b=BpkPo+Ee+KBCo8m9ndsAGjRJ5OWdHb+Xu+NjCUpE+TRFlqzjsawz4pdcK5o4aNmRDJ cR+byGc0LvX1IkRpNRM7OqIXKXm9nD1xVN23bsIDbz4/NQexDhg+YO4B3P954whDKkp6 jnU3/RDLB/Dln7BQt84RXC51omNWs96Pnyoh75nT3FeUQFaKRWToMC/zCi/M9M/m5GwI Z3IK7YHbuTgoi5iuutYagnr+iMjh+EvaIKR5cUds1ijEsd9t18Ldfg/o9sPAeH28cGCH 3MbQO0rted9GCwlLIpnMmQ6UQ+RSK5eLHWqYuJN2HnfQW9uC5DJ8KHVdU6YvuK3N/woi HJKA==
X-Gm-Message-State: AElRT7E0BkHl4uN72wC+QR0dvigXDKpYMDmAGISp86CcuOJFmXB72yh5 i17p3KqCIwf1DkXK+IXBBapS1eZSgafq9r20Rt6v5yAi
X-Google-Smtp-Source: AG47ELsV47Q9S/PfVKfmIxGBy1J4XJkv/ESRmrPaDESVtocHvuvUXYT9JNqedsI7STvgj/ZJcgp98XR+XB3ke/tmPVU=
X-Received: by 10.36.25.202 with SMTP id b193mr26413767itb.105.1520485385994; Wed, 07 Mar 2018 21:03:05 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.58.193 with HTTP; Wed, 7 Mar 2018 21:02:50 -0800 (PST)
In-Reply-To: <152048411881.21355.2781874496381601721.idtracker@ietfa.amsl.com>
References: <152048411881.21355.2781874496381601721.idtracker@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 8 Mar 2018 00:02:50 -0500
Message-ID: <CAF4+nEFjnw6_ROAt1J0K6ir+jg21a=41T8sJH2m_wpws9QhEAA@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-trill-directory-assisted-encap@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/Ica1k0m__r-ZLp0e7aT57D7Fqcs>
Subject: Re: [trill] Eric Rescorla's No Objection on draft-ietf-trill-directory-assisted-encap-10: (with COMMENT)
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: Thu, 08 Mar 2018 05:03:08 -0000

Hi Eric,

On Wed, Mar 7, 2018 at 11:41 PM, Eric Rescorla <ekr@rtfm.com> wrote:
>
> Eric Rescorla has entered the following ballot position for
> draft-ietf-trill-directory-assisted-encap-10: No Objection
>
> ...
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> I support Alvaro's DISCUSS and Kathleen's comment
>
> I also think it would be useful to emphasize the need for some security on the
> links between the egress and ingress nodes, although presumably that's a
> standard TRILL consideration.

Sure. The links between TRILL nodes can be a variety of technologies.
So security on on the links depends on the link technology and is
discussed in the RFC covering TRILL over that link technology.

> Finally
>       nodes. Such spoofing cannot cause looping traffic because TRILL has a
>      hop count in the TRILL header [RFC6325] so that, should there be a
>       loop, a TRILL packet caught in that loop (i.e., an encapsulated
>       frame) will be discarded.
>
> Is it in fact the case that it cannot cause looping or merely that the loop is
> contained by the hop count? Perhaps this is just a terminology issue and in
> routing loop just means infinite loop?

Should probably say "...persistently looping traffic...".

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