Re: [trill] Forwarding table for TRILL

Donald Eastlake <> Fri, 24 August 2012 12:59 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D18F421F8581 for <>; Fri, 24 Aug 2012 05:59:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.629
X-Spam-Status: No, score=-102.629 tagged_above=-999 required=5 tests=[AWL=-0.830, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, J_CHICKENPOX_53=0.6, J_CHICKENPOX_83=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id U0g2N50tUFXb for <>; Fri, 24 Aug 2012 05:59:05 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 5827D21F8582 for <>; Fri, 24 Aug 2012 05:59:05 -0700 (PDT)
Received: by iabz21 with SMTP id z21so3738118iab.31 for <>; Fri, 24 Aug 2012 05:59:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=3nWyHRpFT78rCEOHRqwMfw4alxUQEaMcyN2C8vX894s=; b=FpT4QHB0kupdK6B/rFF4URaUhfwJC1NEstG33/Idru0gjV+u1xd1hIjn6pLTp82iD8 7Ya0KkutfB+tJNzqQRLfVaznmvzK1llhipv2LbmobJzRnxZnDeJ+bcnwg66/lGIm5BHy 7QoRovtc6vLSNDkxcymIT6Jqkb4noCWu9UC7DmIWpwx+hjzrZ9ED2va+6fFjTdsSp9m4 2FulU6MiQdvdqORpAbBS91WV6TIqtZgNHVHJ3y/mMimNJyHqmLrMMxbx/Ge5SmVw1Mu6 TFJO+t9Z/ZAAe3TuZSPmV7293hffiJxOIhYvJK3BGKXI53BqxVjPdfWUJ6xIGpZiRwia 9Hbw==
Received: by with SMTP id d10mr4318987icn.30.1345813144707; Fri, 24 Aug 2012 05:59:04 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Fri, 24 Aug 2012 05:58:44 -0700 (PDT)
In-Reply-To: <>
References: <> <>
From: Donald Eastlake <>
Date: Fri, 24 Aug 2012 08:58:44 -0400
Message-ID: <>
To: Muhammad Mohsin Sardar <>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [trill] Forwarding table for TRILL
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Developing a hybrid router/bridge." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 24 Aug 2012 12:59:05 -0000

Hi Muhammad,

On Fri, Aug 24, 2012 at 2:11 AM, Muhammad Mohsin Sardar
<> wrote:
> Hi,
> As per my understanding from RFC6325 that TRILL has two forwarding
> tables, one having the record of nicknames for RBridges and other
> haveing the MAC addresses for end stations.
> Intermediate RBridges only have nicknames table to forward encapsulated
> packets.
> Whereas ingress/egress RBridges have both nickname and MAC Address table.

An implementer can structure their tables however they want as long as
the bits on the wire and the external behavior is the same; however,
having two tables as you describe, one used by the native frame
ingress/egress function and one used by the TRILL Data forwarding
function is a reasonable way to look at it.

> Question:
> Does ingress/egress RBridges need a forwarding table having the size
> equal to number of end nodes(for MAC) + total RBridges(for
> Nickname)?

Sort of.

The ingress lookup is by VLAN+MAC to get an egress nickname (or find
that it is not in the table) while the egress lookup is by VLAN+MAC to
get a port (or find that it is not in the table). There is, of course,
no requirement that the ingress/egress table(s) be exactly "equal" to
the number of end station in the set of VLANs that the RBridge is
interested in and that is probably almost never true.

On the other hand, there is a requirement that an RBridge be able to
hold the link state which includes the nicknames of all other RBridges
(otherwise it is in overflow, see draft-ietf-trill-clear-correct) and
be able to look up the egress nickname from a TRILL Data frame to
determine which port (unicast) or ports (multi-destinaiton) to forward
the TRILL Data frame out of.

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

> Thanks!
> --
> Best Regards,
> Muhammad Mohsin Sardar