[trill] Kathleen Moriarty's No Objection on draft-ietf-trill-vendor-channel-00: (with COMMENT)

Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com> Wed, 07 March 2018 15:57 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 4F189129C56; Wed, 7 Mar 2018 07:57:38 -0800 (PST)
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>
Cc: draft-ietf-trill-vendor-channel@ietf.org, Susan Hares <shares@ndzh.com>, trill-chairs@ietf.org, shares@ndzh.com, trill@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.74.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152043825827.17721.6520945623840542211.idtracker@ietfa.amsl.com>
Date: Wed, 07 Mar 2018 07:57:38 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/ELoLgTPp0anw8JfryhcDnlOEvjQ>
Subject: [trill] Kathleen Moriarty's No Objection on draft-ietf-trill-vendor-channel-00: (with COMMENT)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
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, 07 Mar 2018 15:57:38 -0000

Kathleen Moriarty has entered the following ballot position for
draft-ietf-trill-vendor-channel-00: 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-vendor-channel/



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

Could you please expand the text in the security considerations section as to
why security properties (integrity, authentication, and encryption since they
are not part of RBridge Channel messages except when explicitly added on in the
extension draft) were not built in?  I'm assuming it is the limited scope of
use for the protocol.  I am glad that options exist to add it in, but wish the
text were a bit more encouraging so that would actually happen.  Vendors need
to be motivated to provide these options for customers who may want to use
them, without that motivation, the features won't be provided.