[trill] Fwd: Publication requested: draft-ietf-trill-rbridge-channel-06

Erik Nordmark <nordmark@acm.org> Wed, 16 May 2012 15:23 UTC

Return-Path: <nordmark@acm.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 3C34321F863B for <trill@ietfa.amsl.com>; Wed, 16 May 2012 08:23:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 JGcF+S6kIxfa for <trill@ietfa.amsl.com>; Wed, 16 May 2012 08:23:29 -0700 (PDT)
Received: from a.mail.sonic.net (a.mail.sonic.net []) by ietfa.amsl.com (Postfix) with ESMTP id 335D321F862B for <trill@ietf.org>; Wed, 16 May 2012 08:23:29 -0700 (PDT)
Received: from [] (96-24-77-210.sfo.clearwire-wmx.net [] (may be forged)) (authenticated bits=0) by a.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id q4GFNPQb011878 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 May 2012 08:23:27 -0700
Message-ID: <4FB3C66B.7010005@acm.org>
Date: Wed, 16 May 2012 08:23:23 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "trill@ietf.org" <trill@ietf.org>
References: <4FB3C528.3000708@acm.org>
In-Reply-To: <4FB3C528.3000708@acm.org>
X-Forwarded-Message-Id: <4FB3C528.3000708@acm.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [trill] Fwd: Publication requested: draft-ietf-trill-rbridge-channel-06
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: Wed, 16 May 2012 15:23:30 -0000

-------- Original Message --------
Subject: Publication requested: draft-ietf-trill-rbridge-channel-06
Date: Wed, 16 May 2012 08:18:00 -0700
From: Erik Nordmark <nordmark@acm.org>
To: iesg-secretary@ietf.org, "rdroms >> Ralph Droms" <rdroms.ietf@gmail.com>
CC: Trill Chairs <trill-chairs@tools.ietf.org>

		    TRILL: RBridge Channel Support

(1) What type of RFC is being requested (BCP, Proposed Standard,
Internet Standard, Informational, Experimental, or Historic)?  Why
is this the proper type of RFC?  Is this type of RFC indicated in the
title page header?

   Proposed Standard as indicated in the title page header. This
   document specifies how a channel (with associated code points) for
   carrying things like BFD and error reports for TRILL.

(2) The IESG approval announcement includes a Document Announcement
Write-Up. Please provide such a Document Announcement Write-Up. Recent
examples can be found in the "Action" announcements for approved
documents. The approval announcement contains the following sections:

Technical Summary

    The TRILL base protocol standard [RFC6325] provides for TRILL Data
    messages and TRILL IS-IS messages.

    This document specifies a general channel mechanism for the
    transmission of other messages within an RBridge campus, such as BFD
    (Bidirectional Forwarding Detection, [RFC5880]) and error messages,
    RBridges and end stations that are directly connected on the same
    link and between RBridges. This mechanism supports a requirement to
    be able to operate with minimal configuration.

Working Group Summary

   There was consensus in the working group in favor of the document.

Document Quality

   The document has been carefully reviewed in the WG and by the document
   shepherd. There are currently no known implementations of the channel
   mechanism, but BFD and error reporting will drive their implementation.


   Who is the Document Shepherd?

      Erik Nordmark

   Who is the Responsible Area Director?

      Ralph Droms

(3) Briefly describe the review of this document that was performed by
the Document Shepherd.  If this version of the document is not ready
for publication, please explain why the document is being forwarded to
the IESG.

   Careful review of the whole document, including looking at
   dependencies to and from rbridge-bfd and rbridge-extension.

(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed?


(5) Do portions of the document need review from a particular or from
broader perspective, e.g., security, operational complexity, AAA, DNS,
DHCP, XML, or internationalization? If so, describe the review that
took place.


(6) Describe any specific concerns or issues that the Document Shepherd
has with this document that the Responsible Area Director and/or the
IESG should be aware of?


(7) Has each author confirmed that any and all appropriate IPR
disclosures required for full conformance with the provisions of BCP 78
and BCP 79 have already been filed. If not, explain why.


(8) Has an IPR disclosure been filed that references this document?
If so, summarize any WG discussion and conclusion regarding the IPR

   No IPR disclosures on this document.

(9) How solid is the WG consensus behind this document? Does it
represent the strong concurrence of a few individuals, with others
being silent, or does the WG as a whole understand and agree with it?

   The consensus is reasonably broad.

(10) Has anyone threatened an appeal or otherwise indicated extreme


(11) Identify any ID nits the Document Shepherd has found in this
document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts
Checklist). Boilerplate checks are not enough; this check needs to be

   No issues.

(12) Describe how the document meets any required formal review
criteria, such as the MIB Doctor, media type, and URI type reviews.

   No formal review criteria apply.

(13) Have all references within this document been identified as
either normative or informative?


(14) Are there normative references to documents that are not ready for
advancement or are otherwise in an unclear state? If such normative
references exist, what is the plan for their completion?

   There are normative references to draft-ietf-trill-rbridge-extension
   which is being advanced simultaneously and to
   draft-eastlake-isis-rfc6326bis whose move to an ISIS WG draft has
   been requested.

(15) Are there downward normative references references (see RFC 3967)?
If so, list these downward references to support the Area Director in the
Last Call procedure.


(16) Will publication of this document change the status of any
existing RFCs?


(17) Describe the Document Shepherd's review of the IANA considerations
section, especially with regard to its consistency with the body of the

   The IANA considerations section lists the additional code points
   and multicast addresses, and also the three new sub-registries.
   The description of the sub-registries and their initial content is
   consistent with the rest of the docuument.

(18) List any new IANA registries that require Expert Review for future
allocations. Provide any public guidance that the IESG would find
useful in selecting the IANA Experts for these new registries.

   The new subregistries do not require Expert Review.

(19) Describe reviews and automated checks performed by the Document
Shepherd to validate sections of the document written in a formal
language, such as XML code, BNF rules, MIB definitions, etc.

   None. No part of this draft is in a formal language.