IETF Logo Mail Archive

Re: [trill] [rbridge] TRILL Multi-topology encoding draft

Anoop Ghanwani <anoop@alumni.duke.edu> Wed, 02 May 2012 16:16 UTC

Return-Path: <ghanwani@gmail.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6499521F853D for <trill@ietfa.amsl.com>; Wed, 2 May 2012 09:16:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.727
X-Spam-Level:
X-Spam-Status: No, score=-4.727 tagged_above=-999 required=5 tests=[AWL=1.250, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TuqniiCVxTx4 for <trill@ietfa.amsl.com>; Wed, 2 May 2012 09:16:44 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id BDC3C21F853B for <trill@ietf.org>; Wed, 2 May 2012 09:16:44 -0700 (PDT)
Received: from mail-pb0-f52.google.com (mail-pb0-f52.google.com [209.85.160.52]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q42GFfGP015971 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Wed, 2 May 2012 09:15:50 -0700 (PDT)
Received: by pbbro8 with SMTP id ro8so1687764pbb.39 for <rbridge@postel.org>; Wed, 02 May 2012 09:15:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=hr0kXadheSWf2Dqom3PCngpZIkfOh5d9uJjrV/VKtDU=; b=mCyb/biVTr7w8vGmjo/mJTajJrOAUWKT3hTRKj+tynCEf6n3gFlhPHeJ7bD+Og4t18 a3gW1PTHgwErekQnkl7377PVsenVVLsPJ2QKKUfmaVPde8eqaQndK6o8rKMJSoZRwfGZ gnm/D17EQ+NVopITXSPBCLyPTsQ0xxhdzKsLvluY5cNia4jdMlbkGQDwURxgpVKPJAp8 OsRvK/5+myiR37u1l249tCh1NGl5w6U7TrmMjhq/znGHM3/LZKIIR71CYmywTnXZ1To2 w54tEjSL8u33iYb3GfVQy+GVOi36mWjgiPJJkmHNARSyK9A2KK97j/yYN+CXdAOuMEAU bm6g==
MIME-Version: 1.0
Received: by 10.68.238.38 with SMTP id vh6mr727701pbc.50.1335975341241; Wed, 02 May 2012 09:15:41 -0700 (PDT)
Sender: ghanwani@gmail.com
Received: by 10.142.153.18 with HTTP; Wed, 2 May 2012 09:15:41 -0700 (PDT)
In-Reply-To: <344037D7CFEFE84E97E9CC1F56C5F4A5010A3734@xmb-sjc-214.amer.cisco.com>
References: <344037D7CFEFE84E97E9CC1F56C5F4A5D10826@xmb-sjc-214.amer.cisco.com> <CAF4+nEEiYAEgO63ZyNrNTpvXcNd-Hc7B7-+ELVkwLVXt9M_Ucw@mail.gmail.com> <344037D7CFEFE84E97E9CC1F56C5F4A5010A3734@xmb-sjc-214.amer.cisco.com>
Date: Wed, 02 May 2012 09:15:41 -0700
X-Google-Sender-Auth: _L-mesHgCbugXl3_tCTV-Wgq7SI
Message-ID: <CA+-tSzwaSwPVhAbNOLSR2KSuwW7t8yooUW-8WiBft-_enLjvdw@mail.gmail.com>
From: Anoop Ghanwani <anoop@alumni.duke.edu>
To: "Tissa Senevirathne (tsenevir)" <tsenevir@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: ghanwani@gmail.com
Cc: Donald Eastlake <d3e3e3@gmail.com>, rbridge@postel.org
Subject: Re: [trill] [rbridge] TRILL Multi-topology encoding draft
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: <http://www.ietf.org/mail-archive/web/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, 02 May 2012 16:16:45 -0000

When using the outer-VLAN, while the frame format itself would
be backwards compatible, I don't believe existing silicon would
actually be able to make use of it.

So it depends on what we mean by "backwards compatibility"?

Do we need the data plane to be backwards compatible?
If so, neither encoding mechanism works.

Or do we need just the frame format to be backwards compatible?
Then using the outer VLAN works.

Anoop

On Tue, May 1, 2012 at 4:00 PM, Tissa Senevirathne (tsenevir)
<tsenevir@cisco.com> wrote:
> Hi Donald
>
> In the ID we have specified a backward compatibility mode where one can use NH-VLAN to encode the multi topology ID on pt-pt links.
>
> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: Tuesday, May 01, 2012 12:52 PM
> To: Tissa Senevirathne (tsenevir)
> Cc: rbridge@postel.org
> Subject: Re: [rbridge] TRILL Multi-topology encoding draft
>
> While this certainly encodes topology into frames, it is not clear to me that the technique using a new tag is generally supported by existing TRILL silicon.
>
> Thanks,
> Donald
> =============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>
> On Mon, Mar 26, 2012 at 12:54 PM, Tissa Senevirathne (tsenevir) <tsenevir@cisco.com> wrote:
>> Dear All
>>
>>
>> We have posted draft-tissa-trill-mt-encode-00. This draft discuss
>> methods that can be used to encode multi topology id without
>> exhausting nickname space or adding additional control plane
>> extensions to abbreviate absolute topology. Please let us know your comments.
>>
>>
>>
>> Abstract:
>>
>>
>>
>>    Two alternative methods of encoding Multi Topology Identifier
>> within
>>
>>    the TRILL data frames are presented. Methods proposed herein do not
>>
>>    require overloading TRILL RBridge nickname to encode Multi Topology
>>
>>    Identifier.
>>
>>
>>
>> Thanks
>>
>> Tissa
>>
>>
>> _______________________________________________
>> rbridge mailing list
>> rbridge@postel.org
>> http://mailman.postel.org/mailman/listinfo/rbridge
>>
> _______________________________________________
> trill mailing list
> trill@ietf.org
> https://www.ietf.org/mailman/listinfo/trill

v2.39.1 | Report a Bug | By Email | System Status