[trill] Kathleen Moriarty's No Objection on draft-ietf-trill-ia-appsubtlv-09: (with COMMENT)

"Kathleen Moriarty" <Kathleen.Moriarty.ietf@gmail.com> Wed, 06 July 2016 16:08 UTC

Return-Path: <Kathleen.Moriarty.ietf@gmail.com>
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 26C1E12D615; Wed, 6 Jul 2016 09:08:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.25.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160706160822.26792.44487.idtracker@ietfa.amsl.com>
Date: Wed, 06 Jul 2016 09:08:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/EHCgiTcEziMy1rXlKCNBdofSLgo>
Cc: draft-ietf-trill-ia-appsubtlv@ietf.org, trill-chairs@ietf.org, shares@ndzh.com, trill@ietf.org
Subject: [trill] Kathleen Moriarty's No Objection on draft-ietf-trill-ia-appsubtlv-09: (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, 06 Jul 2016 16:08:22 -0000

Kathleen Moriarty has entered the following ballot position for
draft-ietf-trill-ia-appsubtlv-09: 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:
https://datatracker.ietf.org/doc/draft-ietf-trill-ia-appsubtlv/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

In the Security Considerations, I realize that this isn't the place for a
recommendation on what to use for transport, but a pointer for the
recommendation feels likes it's missing in the following text:

   However, this document merely describes a
   data format and does not provide any explicit mechanisms for securing
   that information, other than a few simple consistency checks that
   might detect some corrupted data. Security on the wire, or in
   storage, for this data is to be providing by the transport or storage
   used. For example, when transported with ESADI [RFC7357] or RBridge
   Channel [RFC7178], ESADI security or Channel Tunnel [ChannelTunnel]
   security mechanisms can be used, respectively.

Also, there is a nit in the second sentence:
s/providing/provided/