[sidr] Alexey Melnikov's No Objection on draft-ietf-sidr-publication-11: (with COMMENT)

Alexey Melnikov <aamelnikov@fastmail.fm> Sun, 26 February 2017 14:43 UTC

Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: sidr@ietf.org
Delivered-To: sidr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BD5311204D9; Sun, 26 Feb 2017 06:43:54 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148812023477.2888.8486186818190857881.idtracker@ietfa.amsl.com>
Date: Sun, 26 Feb 2017 06:43:54 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/3nlCs_jRgL5ZXYV5JyFzGxRh_nQ>
Cc: morrowc@ops-netman.net, sidr-chairs@ietf.org, draft-ietf-sidr-publication@ietf.org, sidr@ietf.org
Subject: [sidr] Alexey Melnikov's No Objection on draft-ietf-sidr-publication-11: (with COMMENT)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 14:43:54 -0000

Alexey Melnikov has entered the following ballot position for
draft-ietf-sidr-publication-11: 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:


Thank you for addressing my DISCUSS point. A couple of remaining

I still think lack of details about versionning and what requires (or
not) to bump the version number is a mistake.

RFC 2616 (HTTP) got obsoleted, please reference the latest version.

In 2.5: is the list of error reasons extensible? If yes, should you have
an IANA registry for them?

In Section 5 you should reference this document (and not just section
numbers), as IANA registrations cut & pasted to IANA website as separate