[RTG-DIR] RtgDir review: draft-ietf-mboned-driad-amt-discovery-09.txt

Henning Rogge <hrogge@gmail.com> Sat, 14 December 2019 10:34 UTC

Return-Path: <hrogge@gmail.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 CEED11200F7; Sat, 14 Dec 2019 02:34:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 DTC1No7qCURG; Sat, 14 Dec 2019 02:34:29 -0800 (PST)
Received: from mail-lf1-x144.google.com (mail-lf1-x144.google.com [IPv6:2a00:1450:4864:20::144]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A089D12006B; Sat, 14 Dec 2019 02:34:28 -0800 (PST)
Received: by mail-lf1-x144.google.com with SMTP id i23so1050348lfo.7; Sat, 14 Dec 2019 02:34:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=C71zhrGiaTBztDnN1SV0M9/JvlIvOL8Qecqfzxdbfk8=; b=We0e9NmIKm0NCeeOHTaVcIng0PB8GpHfA6AJF0VHvlhq+iP5YIwe08GxV1qrnXwoA3 1AygByecinfHOgpAQ6LyZRuXj5BjPUNhkXH/x5tytoLnlr2+oan6Ez8C5zvWyLKpFWNd h47cf3leQuHUV2wj7p38vF4JH8cpy4eBkSrb19jhRl0klVI5EpI5DotTEnzlgFJmhIaE eISiZbUhDFbHY6E70sOpyIlSKJbOEWkxE63xm7Cq/GgfOV4jA8InF2n4M9K3FYN5SJae Xo3HRzdFHiaaPRBF62l3U4ZGX6tS8RawlALtHBHlLqfWm59RZ2HZmjxAm5+0UdmaBt5r um6g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=C71zhrGiaTBztDnN1SV0M9/JvlIvOL8Qecqfzxdbfk8=; b=DUhAHqEfG1aIaYt3pnTt7+KeZGrxhGhJa0v8L5i0EFVGE0S9jKS0kLwL+SQUWBodRr /Ceq56V0DfOv3qckonKPY/tEaxnQI3PiFs9Z/dHHM/xhd5G/x7HHjBXXQdZEEGxkQNMJ FlfIKXFMjBYBQE3sts2A4iC5454xencVEhCKOQOcBREUAVpFCeW7/gTDuD3zh2PAZNn0 zjK3zCfq11u3eM+277gBTAvvJ2vASFCb65x9AFGx4Rsi6DP5k51lGE75W5D+EFP94qez Ottnn0wVJGPQTdFwm9N8RVSJFd1B7Kyx52C7QqDK9tBz0CJVB/Y3SVfT+dK5Z7Q8uZOP a/zA==
X-Gm-Message-State: APjAAAXu0oBKZLWA/OzSTngQsgOk5DFL3brrswiF7HylIzQ9ROz0Rqt1 xgF8Cpos0/LwqaR+4u9Rab9g5+t2D7Da6lCwr7JtRCOc
X-Google-Smtp-Source: APXvYqz4CQXPNSNdOGyFc6wSZXrNIQvKi0MX72KrLJYKBAv0I7mpy4tSTIstpaowsA7IOvPBXAi2zCckWGPbEPn9gqA=
X-Received: by 2002:ac2:44a2:: with SMTP id c2mr11476325lfm.105.1576319666186; Sat, 14 Dec 2019 02:34:26 -0800 (PST)
MIME-Version: 1.0
From: Henning Rogge <hrogge@gmail.com>
Date: Sat, 14 Dec 2019 11:34:00 +0100
Message-ID: <CAGnRvuqS1eS70RwK9R_U4vGOmZWXyn5TNtScbxtXBCDdYzUSVQ@mail.gmail.com>
To: "<rtg-ads@ietf.org>" <rtg-ads@ietf.org>
Cc: rtg-dir@ietf.org, draft-ietf-mboned-driad-amt-discovery.all@ietf.org, mboned@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/Np8VJQqXtpM7Vhb05kIPqIHZhOA>
Subject: [RTG-DIR] RtgDir review: draft-ietf-mboned-driad-amt-discovery-09.txt
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: Sat, 14 Dec 2019 10:34:31 -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-mboned-driad-amt-discovery-09.txt
Reviewer: Henning Rogge
Review Date: 14.12.2019
Intended Status: Standards Track

Summary:
* No issues found. This document is ready for publication.

Comments:
* I like the fact that DRIAD uses exiting DNS infrastructure for
discovery with a large pool of existing software to use both on client
and server side. DNS is ubiquitous in most networks and easy to
bootstrap (e.g. by DHCP).
* I also like the existence of the "no relay available" type for the
AMTRELAY RData. Together with DNSSEC (or other signatures) this
provides a secure way to make a gateway stop querying.

Major Issues:
* No major issues found.

Minor Issues:
* No minor issues found.

Nits:
* If an application with integrated AMT gateway does know the domain
of the multicast sender, does it make sense to do a DNS-SD query to
the sender?
* In section 4.2.1 (RData Format - Precedence) you discuss that the
Precedence field is used in the same way as the PREFERENCE field in MX
RData. In a SRV record the field Priority has the same semantics. Is
there a reason why you choose not to reuse one of the other names?

Henning Rogge