[trill] FW: [RTG-DIR] draft-ietf-trill-rfc7180bis.all@tools.ietf.org;

"Susan Hares" <shares@ndzh.com> Wed, 06 May 2015 00:13 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CEF51B2A27 for <trill@ietfa.amsl.com>; Tue, 5 May 2015 17:13:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.055
X-Spam-Level:
X-Spam-Status: No, score=-99.055 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, USER_IN_WHITELIST=-100] autolearn=no
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 1gtHsQ-uANW9 for <trill@ietfa.amsl.com>; Tue, 5 May 2015 17:13:35 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id 516731ACE87 for <trill@ietf.org>; Tue, 5 May 2015 17:13:35 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=31.55.43.247;
From: Susan Hares <shares@ndzh.com>
To: trill@ietf.org
Date: Tue, 05 May 2015 20:13:31 -0400
Message-ID: <006901d08791$7d2838a0$7778a9e0$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdCHkN1MkS6Gy2h+RrmFUCUb/HHZ5g==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/J4meTWL2Xi1925khbO15d_NxnEI>
Cc: 'Russ White' <russ@riw.us>, 'Donald Eastlake' <d3e3e3@gmail.com>, 'Jon Hudson' <jon.hudson@gmail.com>
Subject: [trill] FW: [RTG-DIR] draft-ietf-trill-rfc7180bis.all@tools.ietf.org;
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.15
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, 06 May 2015 00:13:36 -0000

WG: 

Here's the routing directorate review of RFC7180bis.  Please let me know if this raises any additional thoughts.  The draft-trill-rfc7180bis draft has passed WG LC and will be forward to the IESG within a few days. 

Sue 

-----Original Message-----
From: rtg-dir [mailto:rtg-dir-bounces@ietf.org] On Behalf Of Russ White
Sent: Friday, April 10, 2015 7:06 PM
To: rtg-ads@tools.ietf.org
Cc: rtg-dir@ietf.org
Subject: [RTG-DIR] draft-ietf-trill-rfc7180bis.all@tools.ietf.org; trill@ietf.org

Hello,

I have been selected as the Routing Directorate reviewer for this draft. The Routing Directorate seeks to review all routing or routing-related drafts as they pass through IETF last call and IESG review, and sometimes on special request. The purpose of the review is to provide assistance to the Routing ADs. For more information about the Routing Directorate, please see ​http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir

Although these comments are primarily for the use of the Routing ADs, it would be helpful if you could consider them along with any other IETF Last Call comments that you receive, and strive to resolve them through discussion or by updating the draft.

Document: draft-ietf-trill-rfc7180bis-04
Reviewer: Russ White
Review Date: 10 April 2015
Intended Status: Proposed Standard

Summary: 

This document is basically ready for publication, but has nits that should be considered prior to publication-- (I found one very minor nit, see below). 

Comments:

This document is difficult to understand, as it modifies several other documents that must be examined in parallel to understand the modifications being made. However, given that the TRILL documents are complex on their own, and this document "sweeps up" various changes across multiple documents while replacing another document, it is readable and serves the purpose for which it is intended well. Overall, this document is complex but readable; someone who understands a TRILL implementation should find it fairly navigable. 

I did check the IANA registries, references, and modifications proposed in this document; I could find no problems with the references, modifications, or registry information as described in the document.

Major Issues:

No major issues found.

Minor Issues:

No minor issues found.

Nits:

10. TRILL Header Update (New)
The TRILL header has been updated from its original specification in [RFC6325] by [RFC7455] and [RFC7179] and is further updated by this document. The TRILL header is now as show in the figure below which is followed by references for all of the fields.

show/shown

==

Russ