Protocol Action: 'Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS' to Proposed Standard (draft-ietf-isis-rfc6326bis-03.txt)
The IESG <iesg-secretary@ietf.org> Mon, 03 February 2014 14:34 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 434291A00F4; Mon, 3 Feb 2014 06:34:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fPdcAEHorCJJ; Mon, 3 Feb 2014 06:34:16 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 06DD01A010A; Mon, 3 Feb 2014 06:34:15 -0800 (PST)
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>
Subject: Protocol Action: 'Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS' to Proposed Standard (draft-ietf-isis-rfc6326bis-03.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140203143415.5208.99636.idtracker@ietfa.amsl.com>
Date: Mon, 03 Feb 2014 06:34:15 -0800
Cc: isis chair <isis-chairs@tools.ietf.org>, isis mailing list <isis-wg@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Feb 2014 14:34:18 -0000
The IESG has approved the following document: - 'Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS' (draft-ietf-isis-rfc6326bis-03.txt) as Proposed Standard This document is the product of the IS-IS for IP Internets Working Group. The IESG contact persons are Adrian Farrel and Stewart Bryant. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-isis-rfc6326bis/ Technical Summary The IETF TRILL (Transparent Interconnection of Lots of Links) protocol provides optimal pair-wise data frame forwarding without configuration in multi-hop networks with arbitrary topology and link technology, and support for multipathing of both unicast and multicast traffic. This document, in conjunction with RFC 6165, specifies the data formats and code points for the IS-IS [ISO-10589] extensions to support TRILL. It obsoletes RFC 6326, which corresponded to the base TRILL protocol as the TRILL Working Group passed it up to the IESG in 2009. There has been substantial development of TRILL since them. The changes from RFC 6326 are briefly summarized in the Introduction and a full list is given in Section 7. Working Group Summary: The need for an IPR disclosure was found after the first Working Group Last Call resulting in a second Working Group Last Call. As a non-controversial update extending a previous RFC, there was relatively little discussion. Owing to some fumbles by the ISIS chairs (honeymoon, NomCom, hospitalisation) the publication request for this document got delayed for a long time. This has nothing to do with the quality of the document and we are trying to play catch-up now. Document Quality: The document is of good quality. The vast majority of the code points and code points specified in this document are in use in shipping TRILL or similar control plane code from multiple equipment manufacturers. The predecessor document RFC 6326 was thoroughly review by Mike Shand and this revision is based on RFC 6326 incorporating the results of that review. The document is on the telechat agenda on the day after the last call ends. A very minor revision is expected to fix a few nits, but currently no issues of substance have been raised. If a more significant revision is needed, the document will be moved to a later telechat. Personnel: Document Shepherd: Adrian Farrel Responsible Area Director: Adrian Farrel