[trill] Alvaro Retana's No Objection on draft-ietf-trill-multi-topology-05: (with COMMENT)

Alvaro Retana <aretana.ietf@gmail.com> Mon, 05 March 2018 22:15 UTC

Return-Path: <aretana.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 E963412008A; Mon, 5 Mar 2018 14:15:36 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alvaro Retana <aretana.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-trill-multi-topology@ietf.org, 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: <152028813695.12719.14525167331803924214.idtracker@ietfa.amsl.com>
Date: Mon, 05 Mar 2018 14:15:36 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/bv_IKkB7RWbDPXdEdr_I0kIbDnU>
Subject: [trill] Alvaro Retana's No Objection on draft-ietf-trill-multi-topology-05: (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: Mon, 05 Mar 2018 22:15:37 -0000

Alvaro Retana has entered the following ballot position for
draft-ietf-trill-multi-topology-05: 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-multi-topology/



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

The extensions defined in this document are "an optional TRILL switch
capability".  To me, that indicates that the base TRILL specifications rfc6325
and rfc7177 (in this case) are not affected: an RBridge is TRILL-compliant as
long as it implements what rfc6325 specifies (without these optional
extensions).  I would then like to see the formal "Updates" tags removed.

[The publication of this document is not the place to argue about the meaning
of "Updates", so I'll defer to what the Responsible AD decides.]