[secdir] Secdir last call review of draft-ietf-dnssd-mdns-dns-interop-04

Sean Turner <sean@sn3rd.com> Tue, 11 April 2017 15:15 UTC

Return-Path: <sean@sn3rd.com>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6356812EAB0; Tue, 11 Apr 2017 08:15:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Sean Turner <sean@sn3rd.com>
To: secdir@ietf.org
Cc: dnssd@ietf.org, ietf@ietf.org, draft-ietf-dnssd-mdns-dns-interop.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149192374936.15734.41201323624268863@ietfa.amsl.com>
Date: Tue, 11 Apr 2017 08:15:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/liTXJlCs1Nt3Ae_JraZ7qQLFrA0>
Subject: [secdir] Secdir last call review of draft-ietf-dnssd-mdns-dns-interop-04
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 15:15:49 -0000

Reviewer: Sean Turner
Review result: Ready

The draft is short and well written.  The security considerations is
also brief, but I agree with its basic point "This memo presents some
requirements for future development, but does not specify anything." 
The persistent "visual confusability" consideration wrt
internationalized domain names is duly noted as a consideration.  In
my opinion, the security considerations as written is appropriate and
sufficient; other DNSSD WG protocol-focused drafts have more extensive
security considerations and it is better to grind the security axe
against those documents rather than here.