Re: [trill] DTree Questions Regarding Router Capability TLV

Ayan Banerjee <ayabaner@gmail.com> Tue, 18 December 2012 17:56 UTC

Return-Path: <ayabaner@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 9C6D621F8AAF for <trill@ietfa.amsl.com>; Tue, 18 Dec 2012 09:56:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sGI6Rzodc569 for <trill@ietfa.amsl.com>; Tue, 18 Dec 2012 09:56:53 -0800 (PST)
Received: from mail-we0-f174.google.com (mail-we0-f174.google.com [74.125.82.174]) by ietfa.amsl.com (Postfix) with ESMTP id 5BF1621F8AA4 for <trill@ietf.org>; Tue, 18 Dec 2012 09:56:48 -0800 (PST)
Received: by mail-we0-f174.google.com with SMTP id x10so445283wey.5 for <trill@ietf.org>; Tue, 18 Dec 2012 09:56:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BqEu5vql3zOyprPbo9gsKEkdjHJa2h8M5Y3G08ugx9U=; b=laII37wNSIlduyN+k23Q5H+zXxl+xR9TD1pSrxa7KksWO7sGMuCW2H78G2FuSehqR2 NSnbawU5NzkNyK/NSqnKiOBKtecpeT8P63Y0pIiC8GVXxQFTvrCRBVUe2qu89U30muo+ g0QJCl98CyFZN8fpycBhp94Ksu+ciqbLKw5J9hzzfhVsoCTD4+4tDb62nUtq0cl1BhV2 6CZsQJj2CivnqwPmpdCnfQVpHZbCdK+3OHbEv/me9TmnX7mY7l/o76kNf1NGyyLQV3hV nMi1lMmLJY9Ue/ErrHL3WZcLzoTMJEAbJLWtgonZrX8NZkxNX2+sltMxo2w90qZ1v0VW PfEQ==
MIME-Version: 1.0
Received: by 10.194.79.34 with SMTP id g2mr6304742wjx.17.1355853407387; Tue, 18 Dec 2012 09:56:47 -0800 (PST)
Received: by 10.194.154.129 with HTTP; Tue, 18 Dec 2012 09:56:47 -0800 (PST)
In-Reply-To: <201212181509.qBIF91R3012151@cichlid.raleigh.ibm.com>
References: <6738A78F51650A4FAEDCF6844B26C21401C0B3D95B4E@USEXCHANGE.corp.extremenetworks.com> <CAHD03N-tjtpwkv97p6OoBZuPuxYo8EGZ5VzjT1CcZGWeDogFTg@mail.gmail.com> <201212181509.qBIF91R3012151@cichlid.raleigh.ibm.com>
Date: Tue, 18 Dec 2012 09:56:47 -0800
Message-ID: <CAHD03N_gHdAB_7BOo2Xzkran_OC0ynyZE07vdhH=hjGfJq1K7Q@mail.gmail.com>
From: Ayan Banerjee <ayabaner@gmail.com>
To: Thomas Narten <narten@us.ibm.com>
Content-Type: multipart/alternative; boundary="047d7bb03eccb6fecb04d1243884"
Cc: Arnel Lim <ALim@extremenetworks.com>, Wenya Qi <wqi@extremenetworks.com>, Eric Garver <egarver@extremenetworks.com>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] DTree Questions Regarding Router Capability TLV
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: Tue, 18 Dec 2012 17:56:53 -0000

Please see in-line.

Thanks,
Ayan



On Tue, Dec 18, 2012 at 7:09 AM, Thomas Narten <narten@us.ibm.com> wrote:

> Ayan Banerjee <ayabaner@gmail.com> writes:
>
> > On Mon, Dec 17, 2012 at 1:50 PM, Arnel Lim <ALim@extremenetworks.com>
> wrote:
>
> > > 3) ALL Rbridges, RB2, that ingress native traffic MUST send
> > >    TREES-USE-ID sub-TLV, correct?  This is required for RPF check
> > >    used by adjacent RBridges.
>
> > > “each RBridge RB2 MUST announce which trees RB2 may choose when
> > >     RB2 ingresses a multi-destination packet.”
>
> > [Ayan] No, this is not accurate. If ingress nodes use this TLV, it
> > may help other nodes to be more strict in accepting packets from the
> > relevant multi-destination trees. If it does not send out this TLV,
> > then it implies that a node may use all multi-destination trees.
>
> So, are you saying that if RB doesn't announce the TLV, all other RBs
> must assume that RB2 can/will ingress multi-destination packets?
>
> If so, I understand the reasoning for why the RB should effectively
> announce a TLV saying "I'm not ingressing anything". But does the spec
> actually say that transit RBs SHOULD/MUST advertise a TLV with a
> (presumably) empty list in this case?
>
> [Ayan] Probably not. However, I would consider the presence of the
statement to be an optimization that would be nice to have - so even if it
is there, it will probably be a "SHOULD" and not a "MUST".


> Thomas
>
>
> _______________________________________________
> trill mailing list
> trill@ietf.org
> https://www.ietf.org/mailman/listinfo/trill
>
>