[trill] Stephen Farrell's No Objection on draft-ietf-trill-irb-13: (with COMMENT)

"Stephen Farrell" <stephen.farrell@cs.tcd.ie> Wed, 29 June 2016 12:04 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: trill@ietf.org
Delivered-To: trill@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AED212DC84; Wed, 29 Jun 2016 05:04:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160629120446.18829.90153.idtracker@ietfa.amsl.com>
Date: Wed, 29 Jun 2016 05:04:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/3de0jukuE4X0U24szcLirig2zE0>
Cc: d3e3e3@gmail.com, trill-chairs@ietf.org, draft-ietf-trill-irb@ietf.org, trill@ietf.org
Subject: [trill] Stephen Farrell's No Objection on draft-ietf-trill-irb-13: (with COMMENT)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 29 Jun 2016 12:04:46 -0000

Stephen Farrell has entered the following ballot position for
draft-ietf-trill-irb-13: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)

Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:


- section 5: The tenant ID is sometimes described as "globally
unique" and sometimes (in 5.2) as "throughout the campus." The
latter seems likely correct to me. (As an aside, is this document
the first to introduce that concept to TRILL?)

- section 8: If IS-IS security is not actually used, (is that the
current deployment reality btw?) and if I can guess a tenant ID then
what new mischief can happen? If there is some, then perhaps you
ought recommend that tenant ID's be randomly selected within the
campus? (I see you use "1" in the example, which is pretty easy to
guess:-) I think one could argue that that (and maybe more) ought be
covered in section 8, if the current deployment reality is that no
crypto is actually used to protect most IS-IS traffic. Is it?