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

"Alvaro Retana (aretana)" <> Thu, 19 January 2017 14:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DB442129415; Thu, 19 Jan 2017 06:18:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -17.72
X-Spam-Status: No, score=-17.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id IilAO3jPbEZe; Thu, 19 Jan 2017 06:18:42 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D77F51295F6; Thu, 19 Jan 2017 06:18:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=17922; q=dns/txt; s=iport; t=1484835521; x=1486045121; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=PY6LC+krHb6fmK+YSK9H8LXUAEcXx4LQvAoK+qEPnQI=; b=E0XK5LJomgrbKRVvS9rlt3wciAznKLA6u+Kxq9uyk8GfcwN1JOel0R3p /kTW9X3Qw2+MH3l4rbmVLHnOU6hZavUHMNW9q14UjdHOu3qJgNgHXmTHY l8O4eQ60Tlrfi8lW1zcTeQs7sbcB3haoYNobCXZEg4ffcixMowL0Ee6CM U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DdAQD5yYBY/51dJa1bAxoBAQEBAgEBA?= =?us-ascii?q?QEIAQEBAYJvQQ8BAQEBAR9ggQkHg0qKCJoHh32DHIIPggyGIgIagWQ/GAECAQE?= =?us-ascii?q?BAQEBAWMohGoGI1YQAgEIDjEDAgICHxEUEQIEDgWIaAMYr2yCJSuHCw2CfAEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBAR2GS4IFgmmCUYFKEQEzCgsbgj8tgjEFiH6MN4V?= =?us-ascii?q?XOAGNX4QFgXeFD4loihuIVAEfOHJUFUoBhiZzhzaBIYENAQEB?=
X-IronPort-AV: E=Sophos;i="5.33,254,1477958400"; d="scan'208,217";a="195242306"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Jan 2017 14:18:40 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id v0JEIe3q027483 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 19 Jan 2017 14:18:40 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 19 Jan 2017 08:18:40 -0600
Received: from ([]) by ([]) with mapi id 15.00.1210.000; Thu, 19 Jan 2017 08:18:40 -0600
From: "Alvaro Retana (aretana)" <>
To: Donald Eastlake <>
Thread-Topic: Alvaro Retana's Discuss on draft-ietf-trill-rfc6439bis-04: (with DISCUSS)
Thread-Index: AQHSccn8d2iuKLA/v0GoMHUkJqLJpaE/nkSAgABMx4A=
Date: Thu, 19 Jan 2017 14:18:40 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/f.1d.0.161209
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_FDF0EF47D4FE4A6296B3FB3559287AC4ciscocom_"
MIME-Version: 1.0
Archived-At: <>
Cc: "" <>, "" <>, The IESG <>, "" <>, Susan Hares <>
Subject: Re: [trill] Alvaro Retana's Discuss on draft-ietf-trill-rfc6439bis-04: (with DISCUSS)
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Developing a hybrid router/bridge." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 19 Jan 2017 14:18:54 -0000



I am not concerned about the case you described below: where the source and destination are attached to the same switch.  Nor am I concerned about transit TRILL data packets.

I am concerned about the case where the other end stations are not attached to any of the local switches, but are somewhere else in the campus (or the mixed case where some of the other end stations are attached to an overloaded switch, but others are elsewhere).  In that case, if I am not missing anything, the appointed forwarder for the local link will accept the native frame and will have to send a TRILL Data Packet across the campus – the information to do that may not be available if the switch is overloaded.



On 1/18/17, 11:43 PM, "Donald Eastlake" <<>> wrote:

Hi Alvaro,

On Wed, Jan 18, 2017 at 3:32 PM, Alvaro Retana <<>> wrote:
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.)


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?

The Appointed Forwarder function has to do with accepting frames from
end stations for ingress and egressing frames to end stations. It does
not have anything to do with TRILL Data packet transit routing.

Consider the following case: two TRILL switches (RBridges) RB1 and RB2
are connected by a link L1 that also has end stations on it. The end
stations are all in VLAN X. There are other end stations in VLAN X in
the TRILL campus not on L1 but all of these other end stations are
directly connected to RB2. RB2 is in overload.

Under these circumstances, RB2 should be the Appointed Forwarder for
VLAN X as that way traffic between all of the VLAN X end stations can
be forwarded by RB2 without any IS-IS routing at all. RB2 will just
be, in effect, forwarding native frames between RB2 ports (although,
for consistency, the TRILL specifications say that RB2 ingresses this
VLAN X traffic by encapsulating it into a TRILL Data frame, and then
notices it is destined for an end station on a local port, immediately
decapsulates it, and sends it out that port).

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.

Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
155 Beaver Street, Milford, MA 01757 USA<>