[trill] Alissa Cooper's No Objection on draft-ietf-trill-directory-assist-mechanisms-11: (with COMMENT)

"Alissa Cooper" <alissa@cooperw.in> Wed, 18 January 2017 15:58 UTC

Return-Path: <alissa@cooperw.in>
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 8BA09129409; Wed, 18 Jan 2017 07:58:56 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Alissa Cooper" <alissa@cooperw.in>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148475513653.2001.17665625207200773811.idtracker@ietfa.amsl.com>
Date: Wed, 18 Jan 2017 07:58:56 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/6QduT0Qok048T2BzN6RcME8-o0E>
Cc: trill-chairs@ietf.org, draft-ietf-trill-directory-assist-mechanisms@ietf.org, shares@ndzh.com, trill@ietf.org
Subject: [trill] Alissa Cooper's No Objection on draft-ietf-trill-directory-assist-mechanisms-11: (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, 18 Jan 2017 15:58:56 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-trill-directory-assist-mechanisms-11: 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:


Since this document implies the creation of centralized databases of
addressing information, I think it would help to call out in Section 6
the need to secure the directory contents themselves, not just against
abuses of the push or pull services but in general against unauthorized

Also, I recall in prior evaluations of TRILL documents some discussion
about how TRILL deals with ephemeral MAC addresses and my recollection is
that they are likely prohibited by policy on TRILL networks. But if there
is some interaction between ephemeral MAC addresses and the services
described in this document that would be good for implementors to be
aware of, those are probably worth mentioning.