[trill] Alvaro Retana's Discuss on draft-ietf-trill-rfc6439bis-04: (with DISCUSS)

"Alvaro Retana" <aretana@cisco.com> Wed, 18 January 2017 20:32 UTC

Return-Path: <aretana@cisco.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 7E8E1129583; Wed, 18 Jan 2017 12:32:16 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Alvaro Retana" <aretana@cisco.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148477153647.2298.16876633792182475280.idtracker@ietfa.amsl.com>
Date: Wed, 18 Jan 2017 12:32:16 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/rGo_wqr047K_541jQZjmOCkTy4Y>
Cc: trill-chairs@ietf.org, shares@ndzh.com, draft-ietf-trill-rfc6439bis@ietf.org, trill@ietf.org
Subject: [trill] Alvaro Retana's Discuss on draft-ietf-trill-rfc6439bis-04: (with DISCUSS)
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 20:32:16 -0000

Alvaro Retana has entered the following ballot position for
draft-ietf-trill-rfc6439bis-04: Discuss

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:


Section 2.4 (Overload and Appointed Forwarders) talks about potential
Appointed Forwarders which are overloaded.  In IS-IS, a node with the
overload bit set "shall not" (ISO 10589) be considered for transit. 
However, the use of "SHOULD NOT appoint an RBridge in overload" and
"SHOULD re-assign VLANs from the overloaded RBridge" leaves a potential
hole in the proper forwarding of TRILL data packers.  Why aren't MUST
NOT/MUST used?  Is there something in the specific use of IS-IS by TRILL
that I am missing?

I think this should be an easy DISCUSS to clear; either point to the
piece I'm missing, or don't use an overloaded node.