IETF Logo Mail Archive

Re: [trill] WG Last Call: draft-ietf-trill-fine-labeling-02.txt

Radia Perlman <radiaperlman@gmail.com> Thu, 29 November 2012 00:48 UTC

Return-Path: <radiaperlman@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 3616421F88E0 for <trill@ietfa.amsl.com>; Wed, 28 Nov 2012 16:48:48 -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=[AWL=-0.000, 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 sylKvF4t5RQG for <trill@ietfa.amsl.com>; Wed, 28 Nov 2012 16:48:47 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 83CA121F88DF for <trill@ietf.org>; Wed, 28 Nov 2012 16:48:47 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so7048508vbb.31 for <trill@ietf.org>; Wed, 28 Nov 2012 16:48: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=RB8Yh/zyImxJvw8fLZsGmx2+pKy5BIWIWIHhG7zrKdk=; b=kgcbMzU/7CKRBqJkr3WFQWfGRpC0E9x2phQput2UujhL8HFGuToqssP18z3ujtFAeV iakmyoBvyC5i+VAQ8gMjaVzKhi9uEFJBK0ErBTKJ8VdeQGhqGiLihKc4Yg0q6XZrfYGk 9WsFt3KJtEUADlBmsx1l4+gsg8puu+GRdXqMzKcpmvEFW6ExnGDFBl6ezh8/MjtKJrvQ 5EFFxLa+ebdCwFMbSIjpqGIaauoN57ivgQ8C9hambaQFZWTd+jezhIS4QyFnO7NjzrZC ED7SvdgcmL5VaA/LzvKSibC080BiCdCR/neFHQkN1Wn2iy0fmhNY8H2acFa6KciXugPU Zpdg==
MIME-Version: 1.0
Received: by 10.220.225.132 with SMTP id is4mr29856909vcb.47.1354150127028; Wed, 28 Nov 2012 16:48:47 -0800 (PST)
Received: by 10.58.207.138 with HTTP; Wed, 28 Nov 2012 16:48:46 -0800 (PST)
In-Reply-To: <201211281553.qASFrAgu013237@cichlid.raleigh.ibm.com>
References: <CAF4+nEE+rT9x_MgiWLCx7xut4SgDJ7=pRK1L_PovrwBCg3OaVw@mail.gmail.com> <CCCE73BA.C6A2%ostokes@extremenetworks.com> <CAF4+nEFioN3TmDj7sGchr4atPijRNiGCwiBLe8ROB79fqA0kAg@mail.gmail.com> <A3C4E51A53661B4EBEE7C5F5E6FCDEB5026F93353CEE@USEXCHANGE.corp.extremenetworks.com> <CAF4+nEFuaJQrPXCSD0rsu_sJiSQzNNL0eU6Vp3_mwWGThXfQLg@mail.gmail.com> <A3C4E51A53661B4EBEE7C5F5E6FCDEB5026F9347058C@USEXCHANGE.corp.extremenetworks.com> <201211281553.qASFrAgu013237@cichlid.raleigh.ibm.com>
Date: Thu, 29 Nov 2012 01:48:46 +0100
Message-ID: <CAFOuuo6_BNzaGaSaOyfet=DhB3+4Yxc-Mazgp6Y4=f5E1UPD0g@mail.gmail.com>
From: Radia Perlman <radiaperlman@gmail.com>
To: Thomas Narten <narten@us.ibm.com>
Content-Type: multipart/alternative; boundary="14dae9ccd52c4b49b704cf97a52f"
Cc: Donald Eastlake <d3e3e3@gmail.com>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] WG Last Call: draft-ietf-trill-fine-labeling-02.txt
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: Thu, 29 Nov 2012 00:48:48 -0000

Even if the base spec doesn't preclude doing serial unicast, it might be
worth mentioning the possiblity here because if there is a huge campus with
so many different FGLs in use that the inner RBridges have trouble
filtering, and there's only a few edge guys participating in the FGL, it
might wind up being more optimal for the ingress switch to do serial
unicast.  So saying MAY just gives an implementer the hint that it might be
a good thing to allow.

At any rate, I don't think it hurts to have that sentence in the FGL spec.

Radia




On Wed, Nov 28, 2012 at 4:53 PM, Thomas Narten <narten@us.ibm.com> wrote:

> Olen's original comment was about the following text in the document:
>
> > "An FGL ingress RBridge MAY serially TRILL unicast a multi-destination
> > TRILL Data frame to the relevant egress TRILL switches after
> encapsulating
> > it as a TRILL known unicast data frame (M=0)".
>
> Does the base TRILL spec forbid the above behavior?
>
> Is this sentence even needed? Can we just remove it? (FWIW, it seems
> to me to be unnecessary.)
>
> Thomas
>
> _______________________________________________
> trill mailing list
> trill@ietf.org
> https://www.ietf.org/mailman/listinfo/trill
>

v2.23.0 | Report a Bug | By Email