[Idr] Adam Roach's No Objection on draft-ietf-idr-shutdown-08: (with COMMENT)

Adam Roach <adam@nostrum.com> Wed, 24 May 2017 02:39 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F873126B7F; Tue, 23 May 2017 19:39:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Adam Roach <adam@nostrum.com>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-idr-shutdown@ietf.org, Susan Hares <skh@ndzh.com>, aretana@cisco.com, idr-chairs@ietf.org, skh@ndzh.com, idr@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149559358944.28506.18362121959782542849.idtracker@ietfa.amsl.com>
Date: Tue, 23 May 2017 19:39:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/oXyqFjoEO11BdEy95UCBtKGYt7E>
Subject: [Idr] Adam Roach's No Objection on draft-ietf-idr-shutdown-08: (with COMMENT)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 May 2017 02:39:50 -0000

Adam Roach has entered the following ballot position for
draft-ietf-idr-shutdown-08: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-idr-shutdown/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

The portion of Section 6 (Security Considerations) that discusses
confusable characters is describing a problem that isn't obvious on first
reading. As these strings are human-produced and human-consumed, it's not
clear what harm would arise through the use of spoofing. If there is a
real risk here that the authors are aware of, it should be described in
more detail to allow implemetors to more adeptly steer around it. If not,
the statement around spoofing should probably be removed so as to avoid
implementors scratching their heads regarding what mitigating actions
they might take.