[RTG-DIR] [RTG-DIR} RtgDir last call review: draft-ietf-lisp-signal-free-multicast-07.txt

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Fri, 12 January 2018 06:48 UTC

Return-Path: <ginsberg@cisco.com>
X-Original-To: rtg-dir@ietfa.amsl.com
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B67E81289B0; Thu, 11 Jan 2018 22:48:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level:
X-Spam-Status: No, score=-14.531 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 xzFtpml5if8X; Thu, 11 Jan 2018 22:48:18 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78E3B126CD6; Thu, 11 Jan 2018 22:48:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2103; q=dns/txt; s=iport; t=1515739698; x=1516949298; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=GkLdi4UaBgYnAfbOd5v2f0bag7F+EhA+gWqM0QjCnLs=; b=YiYtWn8RpEExLtueqAn8BoQSYR85Z0zwOp0+myDGi/pXV6R7s7nNXqe/ FYw0XSqGAp15glnFOD/ljAIRQ0flmnPP6fdDnjyIwZ/oe4T6svY1kP0O2 ih0uNRpI4+9U32DewVyuvbLxR7DZCrIj1bknLWt7gdPipStLAWr1BAkXr A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B/BADQWVha/5ldJa1dGQEBAQEBAQEBAQEBAQcBAQEBAYNBZnQnAQaOJI5hmTIUggIKI4UYhEE/GAEBAQEBAQEBAWsdC4VkMQ4SARwiQiYBBA4NiisQshqKPAEBAQEBBQEBAQEkhDyCFYFXgWmGUgsCgT4BEgGGGwWKW48XiXICiAmNNYIiZ4EbhBuEFYdFjT6JOgIRGQGBOwEfOWBwbxWCaAiETnmJG4ElgRcBAQE
X-IronPort-AV: E=Sophos;i="5.46,348,1511827200"; d="scan'208";a="55638340"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Jan 2018 06:48:17 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id w0C6mGZr008454 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 12 Jan 2018 06:48:17 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 12 Jan 2018 00:48:16 -0600
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1320.000; Fri, 12 Jan 2018 00:48:16 -0600
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "rtg-ads@ietf.org" <rtg-ads@ietf.org>
CC: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "draft-ietf-lisp-signal-free-multicast.all@ietf.org" <draft-ietf-lisp-signal-free-multicast.all@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>
Thread-Topic: [RTG-DIR} RtgDir last call review: draft-ietf-lisp-signal-free-multicast-07.txt
Thread-Index: AdOLcLxCyIYYx6rFQ5mJ4GHzb7Xvog==
Date: Fri, 12 Jan 2018 06:48:16 +0000
Message-ID: <67a4814cf3aa408c8794d9b937cb8fcf@XCH-ALN-001.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.57.31]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/pUVMM8MQAt67VXkTgxf4ysK1Uac>
Subject: [RTG-DIR] [RTG-DIR} RtgDir last call review: draft-ietf-lisp-signal-free-multicast-07.txt
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir/>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jan 2018 06:48:21 -0000

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-lisp-signal-free-multicast-07.txt
Reviewer: Les Ginsberg
Review Date: 11 January 2018
IETF LC End Date: Unknown
Intended Status: Experimental

Summary:
    This document is basically ready for publication, but has nits that should be considered prior to publication.

Comments:

This draft is very well written. Ideas are presented in a logical and coherent manner and I find it easy to understand the concepts even
without necessarily being an expert in the specific technology.

Major Issues:

No major issues found.

Minor Issues:

No minor issues found.

Nits:

The first use of LCAF (Section 2) should be expanded.

I find the acronym "RTR" a bit unfortunate for the obvious reason that it intuitively represents "just a router". I wonder if the authors could
consider something like "ReTR". I am sensitive to the fact that this document has been around since 2014 and has undergone significant WG review. I have
not attempted to track all of the email history regarding this document. Perhaps this point has been considered and consensus has been that the
RTR acronym is the best choice. If so, feel free to disregard my suggestion, but as someone who read this document for the first time I found myself 
looking back for the definition of "RTR" multiple times as I read through the text.

   Les