IETF Logo Mail Archive

Re: [trill] draft-hu-trill-rbridge-esadi to TRILL WG draft

Thomas Narten <narten@us.ibm.com> Mon, 23 April 2012 12:46 UTC

Return-Path: <narten@us.ibm.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 DB64121F85F2 for <trill@ietfa.amsl.com>; Mon, 23 Apr 2012 05:46:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.229
X-Spam-Level:
X-Spam-Status: No, score=-110.229 tagged_above=-999 required=5 tests=[AWL=0.370, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 EJh1JmpCtnQm for <trill@ietfa.amsl.com>; Mon, 23 Apr 2012 05:46:12 -0700 (PDT)
Received: from e37.co.us.ibm.com (e37.co.us.ibm.com [32.97.110.158]) by ietfa.amsl.com (Postfix) with ESMTP id 3D46221F85E3 for <trill@ietf.org>; Mon, 23 Apr 2012 05:46:12 -0700 (PDT)
Received: from /spool/local by e37.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <trill@ietf.org> from <narten@us.ibm.com>; Mon, 23 Apr 2012 06:46:11 -0600
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e37.co.us.ibm.com (192.168.1.137) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Mon, 23 Apr 2012 06:45:28 -0600
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 46FEFC4000B for <trill@ietf.org>; Mon, 23 Apr 2012 06:45:26 -0600 (MDT)
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q3NCif81264826 for <trill@ietf.org>; Mon, 23 Apr 2012 06:44:51 -0600
Received: from d03av05.boulder.ibm.com (loopback [127.0.0.1]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q3NCiejo019007 for <trill@ietf.org>; Mon, 23 Apr 2012 06:44:40 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-65-216-82.mts.ibm.com [9.65.216.82]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q3NCidVj018989 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Apr 2012 06:44:40 -0600
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q3NCicwq006370; Mon, 23 Apr 2012 08:44:38 -0400
Message-Id: <201204231244.q3NCicwq006370@cichlid.raleigh.ibm.com>
To: Donald Eastlake <d3e3e3@gmail.com>
In-reply-to: <CAF4+nEFpLSZFKxosLhqXYpi_Eyo1f171QFjLHhUAz_5eBYEK6g@mail.gmail.com>
References: <CAF4+nEFpLSZFKxosLhqXYpi_Eyo1f171QFjLHhUAz_5eBYEK6g@mail.gmail.com>
Comments: In-reply-to Donald Eastlake <d3e3e3@gmail.com> message dated "Thu, 12 Apr 2012 23:13:36 -0400."
Date: Mon, 23 Apr 2012 08:44:38 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12042312-7408-0000-0000-0000046CA8EF
Cc: trill@ietf.org
Subject: Re: [trill] draft-hu-trill-rbridge-esadi to TRILL WG 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: Mon, 23 Apr 2012 12:46:13 -0000

> This message begins a two week comment period for TRILL WG assent to
> make draft-hu-trill-rbridge-esadi-04.txt a TRILL WG draft.

Question about the scope of this document. It says:

   This document updates [RFC6325], the TRILL basic specification,
   particularly the description of the ESADI protocol, and prevails over
   [RFC6325] in the case of conflicts.

To be clear, is the intention of this document to become the single,
normative description of ESADI? 

FWIW, I hope so. IMO, it would be best to put all of the ESADI
protocol specification into a single, definitive document. And have
that document obsolete/supersede all previous specifications on the
topic of ESADI.

Thomas

v2.23.0 | Report a Bug | By Email