[trill] Last Call: <draft-ietf-trill-clear-correct-03.txt> (TRILL: Clarifications, Corrections, and Updates) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Wed, 06 June 2012 18:14 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 44EAD21F8800; Wed, 6 Jun 2012 11:14:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.933
X-Spam-Status: No, score=-101.933 tagged_above=-999 required=5 tests=[AWL=0.666, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 08ZvUif0Yk7D; Wed, 6 Jun 2012 11:13:59 -0700 (PDT)
Received: from ietfa.amsl.com (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id BD86921F87FE; Wed, 6 Jun 2012 11:13:59 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120606181359.29043.12432.idtracker@ietfa.amsl.com>
Date: Wed, 06 Jun 2012 11:13:59 -0700
Cc: trill@ietf.org
Subject: [trill] Last Call: <draft-ietf-trill-clear-correct-03.txt> (TRILL: Clarifications, Corrections, and Updates) to Proposed Standard
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
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, 06 Jun 2012 18:14:00 -0000

The IESG has received a request from the Transparent Interconnection of
Lots of Links WG (trill) to consider the following document:
- 'TRILL: Clarifications, Corrections, and Updates'
  <draft-ietf-trill-clear-correct-03.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2012-06-20. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   The IETF TRILL (TRansparent Interconnection of Lots of Links)
   protocol provides least cost pair-wise data forwarding without
   configuration in multi-hop networks with arbitrary topology, safe
   forwarding even during periods of temporary loops, and support for
   multipathing of both unicast and multicast traffic. TRILL
   accomplishes this by using IS-IS (Intermediate System to Intermediate
   System) link state routing and by encapsulating traffic using a
   header that includes a hop count. Since the TRILL base protocol was
   approved in March 2010, active development of TRILL has revealed a
   few errata in the original RFC 6325 and some cases that could use
   clarifications or updates.

   RFC 6327 and RFC 6439 provide clarifications and updates with respect
   to Adjacency and Appointed Forwarders. This document provide other
   known clarifications, corrections, and updates to RFC 6325, RFC 6327,
   and RFC 6439.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.