[Idr] Joel Jaeggli's Yes on draft-ietf-idr-deprecate-30-31-129-02: (with COMMENT)

"Joel Jaeggli" <joelja@bogus.com> Mon, 02 January 2017 02:50 UTC

Return-Path: <joelja@bogus.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 E2FC1129466; Sun, 1 Jan 2017 18:50:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Jaeggli <joelja@bogus.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148332543492.25163.10499443805665312317.idtracker@ietfa.amsl.com>
Date: Sun, 01 Jan 2017 18:50:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/LON2akILvh8XXBzj55P2M1J3C9Y>
Cc: idr@ietf.org, idr-chairs@ietf.org, draft-ietf-idr-deprecate-30-31-129@ietf.org, shares@ndzh.com
Subject: [Idr] Joel Jaeggli's Yes on draft-ietf-idr-deprecate-30-31-129-02: (with COMMENT)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 02 Jan 2017 02:50:35 -0000

Joel Jaeggli has entered the following ballot position for
draft-ietf-idr-deprecate-30-31-129-02: Yes

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:


Stop them before they kill again.

Imho, while we're not doing it here, we should probably provide advice to
implementers or even revisit how we allocate them on how to do this
safely in the future cause squatting on code points is  definite
minefield here.