Re: [trill] Should we make draft-mrw-trill-over-ip-01 a WG document?

Margaret Wasserman <> Tue, 15 May 2012 10:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8DBB021F872D for <>; Tue, 15 May 2012 03:54:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.264
X-Spam-Status: No, score=-102.264 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id xm2SbmlHR9MH for <>; Tue, 15 May 2012 03:54:27 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id D5D5921F8709 for <>; Tue, 15 May 2012 03:54:26 -0700 (PDT)
Received: from [] ( []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by (Postfix) with ESMTPSA id 250A420383; Tue, 15 May 2012 06:50:07 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary="Apple-Mail-389-142294330"
From: Margaret Wasserman <>
In-Reply-To: <>
Date: Tue, 15 May 2012 06:54:23 -0400
Message-Id: <>
References: <> <> <> <>
To: Ralph Droms <>
X-Mailer: Apple Mail (2.1084)
Cc: Donald Eastlake <>,
Subject: Re: [trill] Should we make draft-mrw-trill-over-ip-01 a WG document?
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: Tue, 15 May 2012 10:54:27 -0000

Hi Ralph,

Just FYI -- I am one of the authors of draft-mrw-trill-over-ip, so obviously I have an interest in the outcome here.

On May 14, 2012, at 3:26 PM, Donald Eastlake wrote:
> None of these arguments matter as our Area Director says that we need
> to re-Charter to make TRILL over IP a WG draft. However, I will
> respond a bit below:

Could you clarify what you mean by "we need to re-Charter to make TRILL over IP a WG draft"?  I can think of two things you might mean.

(1) TRILL over Foo documents would fall into this part of the charter,

"...but also additional ways to
extend and optimize TRILL for the properties of the networks on
which it is deployed."

but we need to add a milestone for TRILL over IP which you and the chairs can easily do if the WG agrees it wants to do this work.  This makes sense to me.


(2) The above sentence would not cover TRILL over Foo documents, and we would need to do a completely new charter to cover them.  This doesn't make sense to me for two reasons:  (a) TRILL over Foo documents are pretty clearly going to be needed, and need to be done in the TRILL WG, and (b) I'm not sure what else would fall more firmly under the notion of "extend ... TRILL for the properties ... of the networks on which will be deployed".

Whatever your intent, if we _did_ somehow manage to charter a WG where the work needed to encapsulate the core protocol in IP _doesn't_ fall in the WG charter, could we please fix that?

I understand that we aren't done with the discussion of whether or not the WG wants to adopt this particular draft for that purpose, but the decisions about whether to encapsulate TRILL in IP, and if so, how do it, clearly need to be made in the TRILL WG, not through the individual or independent submission paths (which is what tends to happen when existing, nearly complete documents are declared out-of-scope for any IETF WG).