[trill] Alvaro Retana's No Objection on draft-ietf-trill-centralized-replication-11: (with COMMENT)

Alvaro Retana <aretana.ietf@gmail.com> Fri, 05 January 2018 05:17 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 2858712D7EB; Thu, 4 Jan 2018 21:17:12 -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-centralized-replication@ietf.org, trill-chairs@ietf.org, d3e3e3@gmail.com, trill@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.68.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151512943212.14698.6032171824226845587.idtracker@ietfa.amsl.com>
Date: Thu, 04 Jan 2018 21:17:12 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/5cmexaGuVP9w3FJF4eSyyxMU6ug>
Subject: [trill] Alvaro Retana's No Objection on draft-ietf-trill-centralized-replication-11: (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: Fri, 05 Jan 2018 05:17:12 -0000

Alvaro Retana has entered the following ballot position for
draft-ietf-trill-centralized-replication-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:


I have some non-blocking comments.  I would like to see the ones related to
Normative Language addressed before publication.

- From the Abstract: "RPF checks on each RBridge MUST be calculated as if the
centralized node was the ingress RBridge..."  Using Normative Language in the
Abstract seems strange to me, specially since the same language is not used
later in the text.  The document does get to the same point later, but not with
the same language.

- The Introduction says that "...a centralized node, which SHOULD be a
distribution tree root", but Section 3 says otherwise: "The centralized node
MUST be a distribution tree root."  Suggestion: use Normative Language in just
one place.  IMO, the Introduction may not be the right place for it.

- BTW, what is a "distribution tree root"?  The definition is probably
intuitive since we're talking about replication, but explicitly defining it
would clear any possible confusion.

- I appreciate the background and the description of the problem and the
mechanism, but there's a lot of repetition.  Section 3 presents for the third
time an overview of the mechanism -- Abstract, Introduction, and Section
3...note that even the last paragraph repeats information about the replication
from this same section.

- Section 9: "An edge group using CMT [RFC7783] MUST NOT set the C-nickname
flag on the pseudo-nickname it is using. This is already mandatory behavior..."
If "already mandatory" then there's no need to use Normative Language here,

- Section 11.1 ("R" and "C" Flag in the Nickname Flags APPsub-TLV):  I'm not
sure if I understand correctly, but because there's a distinction between the
R-nickname and the C-nickname, both bits should not be set at the same time,
right?  What happens if they are?  It seems that the last paragraph tries to
address that question ("due to errors")...but I'm then not sure what the action
is: "it is RECOMMENDED that the nickname be treated as if the R / C flag was
set if any Nickname Flags APPsub-TLV for that nickname has the R / C flag set."
Again, what if both are set?  And "RECOMMENDED" implies that there are reasons
not to do it this way...what are those cases?