[RTG-DIR] RtgDir review: draft-ietf-mboned-deprecate-interdomain-asm
Loa Andersson <loa@pi.nu> Sun, 22 December 2019 09:45 UTC
Return-Path: <loa@pi.nu>
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 4833F1200B2; Sun, 22 Dec 2019 01:45:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 b2U4cukTtPSi; Sun, 22 Dec 2019 01:44:59 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F06F11200B6; Sun, 22 Dec 2019 01:44:58 -0800 (PST)
Received: from [192.168.1.6] (unknown [119.94.175.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id C78A735DF54; Sun, 22 Dec 2019 10:44:54 +0100 (CET)
To: "<rtg-ads@ietf.org>" <rtg-ads@ietf.org>
Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, draft-ietf-mboned-deprecate-interdomain-asm@ietf.org
From: Loa Andersson <loa@pi.nu>
Message-ID: <1e2a9058-93b6-4b31-c4cc-2226a7e2c4e0@pi.nu>
Date: Sun, 22 Dec 2019 17:44:51 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/kXj1Jk8GO9sZ4ZoPtf7whfDR1w8>
Subject: [RTG-DIR] RtgDir review: draft-ietf-mboned-deprecate-interdomain-asm
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 22 Dec 2019 09:45:02 -0000
Routing Directorate Last Call Review Template To: rtg-ads@… Cc: rtg-dir@…; draft-name.all@…; wg-mailing-list; Subject: RtgDir review: draft-ietf-mboned-deprecate-interdomain-asm 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-mboned-deprecate-interdomain-asm Reviewer: Loa Andersson Review Date: date IETF LC End Date: date-if-known Intended Status: BCP Summary: This document recommends deprecation of the use of Any-Source Multicast (ASM) for interdomain multicast. It recommends the use of Source-Specific Multicast (SSM) for interdomain multicast applications and that hosts and routers in these deployments fully support SSM. Major Issues: No major issues found. On the contrary I think that the document is well wriiten and comprehensive. My point below are at best minor issues, but mostly nits. Actually from a pure technical content point of view everything that needs to be there is there and the recommendations is as far as I understand correct. Minor Issues: There is a document from the RFC Editor, RFC 7322 "RFC Style guide". These guidelines should be followed, e.g. the "Requirement Language should be moved into the body of the document, normally section 1.1. Someone (AD) should think about if the requirement language is needed in this Informational document. A "MUST" is used when outlining what draft-ietf-6man-rfc6434-bis does. but it is not really a requirement from this document. I'm split about this and could go either way. Also the new template should be used for 2119 language. MLDv2 (or MLD) is not a well-know abbreviation and needs to be expanded. IGMPv3 is well-known, but IGMPv3 is not. Beats me what is required, but in such cases I always recommend expanding. " Nits: I wonder about this in section 3.1" "... has become widespread in common OSes for several years (Windows, MacOS, Linux/Android)..." Should we say: "... has become widespread in common Operating Systems for several years (Windows, MacOS, Linux/Android)..." Other style issue: Sometimes IGMPv3 / MLDv2 is used At other places IGMP/MLD or IGMPv3/MLDv2, I think we should use one or the other. Nits tool has two issues, these are addressed in the Shepherd Write-up, poimting out that updates /Loa -- Loa Andersson email: loa@pi.nu Senior MPLS Expert Bronze Dragon Consulting phone: +46 739 81 21 64
- [RTG-DIR] RtgDir review: draft-ietf-mboned-deprec… Loa Andersson
- Re: [RTG-DIR] RtgDir review: draft-ietf-mboned-de… Tim Chown
- Re: [RTG-DIR] RtgDir review: draft-ietf-mboned-de… Loa Andersson
- Re: [RTG-DIR] RtgDir review: draft-ietf-mboned-de… Tim Chown