[trill] TRILL OAM framework review (draft-ietf-trill-oam-framework-01)

"Susan Hares" <shares@ndzh.com> Thu, 04 April 2013 21:36 UTC

Return-Path: <shares@ndzh.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 BD6A621F8F0E for <trill@ietfa.amsl.com>; Thu, 4 Apr 2013 14:36:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.705
X-Spam-Level: *
X-Spam-Status: No, score=1.705 tagged_above=-999 required=5 tests=[AWL=1.199, BAYES_00=-2.599, DOS_OUTLOOK_TO_MX=1, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
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 WOULUYEEWvpk for <trill@ietfa.amsl.com>; Thu, 4 Apr 2013 14:36:32 -0700 (PDT)
Received: from hickoryhill-consulting.com (unknown [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id E9F0A21F8FCF for <trill@ietf.org>; Thu, 4 Apr 2013 14:36:31 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=64.112.195.202;
From: "Susan Hares" <shares@ndzh.com>
To: "'Donald Eastlake'" <d3e3e3@gmail.com>, <sam.aldrin@gmail.com>, <tsenevir@cisco.com>, <ssalam@cisco.com>
Date: Thu, 4 Apr 2013 17:36:28 -0400
Message-ID: <014e01ce317c$778f7880$66ae6980$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_014F_01CE315A.F0815AF0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac4xfGWYe5JQyIDFRvKvLvCLF+llFg==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Cc: trill@ietf.org
Subject: [trill] TRILL OAM framework review (draft-ietf-trill-oam-framework-01)
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: Thu, 04 Apr 2013 21:36:33 -0000

Donald, Sam, Tissa, and Samer:

 

General comments: Nicely written and enjoyable to read after all of the
debates. 

 

Two technical issues concern me as underspecified in the document: 

 

1.       Section 2.4 has maintenance Domains which can be "nested to form a
hierarchy" (p. 12, para. 1) 

a.       The nesting of Domains seems to be underspecified in this draft and
it is unclear exactly how these domains would nest. 

b.      There are mechanism for finding the hierarchy (Domain name and
maintenance level (numeric ID), but it is not clear from the document how
this works. 

2.       Section 4.2.1.2 - Multicast prevention of reply storms from
overwhelming the initiating RBridge. 

a.       Staggering or Jittering responses  may or may not protect the
initiating RBridge

b.      Again - this may be right or wrong, but the lack of additional
details concerns me whether this solution has been written down correctly.
I suspect from Tissa's comments that it is working. 

 

Editorial comments: 

1.       Replace TRILL-OAM-REQ with RFC6905 in all document,

2.       p. 4 TRILL in para. 2 has an extra space "-     TRILL" to "-TRILL"

3.       use of "multipathing" - has this been defined elsewhere? - it
should be defined or referenced,

4.       page 6. Para. 2 beginning [RFC6371].  Please change
/protection-switching management and/protection-switching management/

5.       page 8 sentence:  "The output ports on which TRILL OAM message are
sent are determined by the TRILL routing function, which will only send on
links that are in the up state and have been incorporated into the local
view of the campus topology"  - Suggest

a.       "The output ports on which TRILL OAM messages are sent are
determined by the TRILL routing function. The TRILL Routing function will
only send on links that are in the up state and have been incorporated into
the local view of the campus topology".  

6.       Page 11 - [TRILLML] - is not listed in the references - 

7.       Page 16.  Suggest changing 1st sentence of paragraph into two
parts.  /[RFC6325] and the Link Header/[RFC6325]. The Link header" 

8.       Page 4.1.2.2 add at end of sentence 2 /section./ section (4.1.2.1).


 

Sue Hares

Reviewer