[Sidrops] Adam Roach's Discuss on draft-ietf-sidrops-bgpsec-algs-rfc8208-bis-04: (with DISCUSS and COMMENT)

Adam Roach via Datatracker <noreply@ietf.org> Wed, 10 April 2019 21:32 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: sidrops@ietf.org
Delivered-To: sidrops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 903E71203EB; Wed, 10 Apr 2019 14:32:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Adam Roach via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-sidrops-bgpsec-algs-rfc8208-bis@ietf.org, Chris Morrow <morrowc@ops-netman.net>, sidrops-chairs@ietf.org, morrowc@ops-netman.net, sidrops@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Adam Roach <adam@nostrum.com>
Message-ID: <155493194558.22757.15388423154564497249.idtracker@ietfa.amsl.com>
Date: Wed, 10 Apr 2019 14:32:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/GnKce2O7u__94z8uOP7EA0Tu9M4>
Subject: [Sidrops] Adam Roach's Discuss on draft-ietf-sidrops-bgpsec-algs-rfc8208-bis-04: (with DISCUSS and COMMENT)
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2019 21:32:26 -0000

Adam Roach has entered the following ballot position for
draft-ietf-sidrops-bgpsec-algs-rfc8208-bis-04: Discuss

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-sidrops-bgpsec-algs-rfc8208-bis/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Thanks to everyone who worked on this document.

This issue should be trivial to fix, but it's still a blocker.

§2.1:

>     Special-Use algorithm IDs span from 0xFA (250) to 0xFE (254).

§7:

>  In addition IANA is asked to register the following address space for
>  "Special-Use":
>
>    Algorithm   Digest          Signature       Specification
>    Suite       Algorithm       Algorithm       Pointer
>    Identifier
>  +------------+---------------+--------------+-----------------------+
>  | 0xFB-0xFE  | Special-Use   | Special-Use  | This Document         |
>  +------------+---------------+--------------+-----------------------+


The ranges here do not match ([0xFA-0xFE] != [0xFB-0xFE]). Presuming that the
text in Section 2.1 is what was intended, this issue impacts all of
the tables in section 7.


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

I agree with Alexey's discuss.

---------------------------------------------------------------------------

§7:

>  To be modified to:
>
>    Algorithm   Digest          Signature       Specification
>    Suite       Algorithm       Algorithm       Pointer
>    Identifier
>  +------------+---------------+--------------+-----------------------+
>  | 0x2-0xFA   | Unassigned    | Unassigned   |                       |
>  +------------+---------------+--------------+-----------------------+

Nit: The prose has been updated to use "0x02" rather than "0x2". It would be
nice if the IANA section matched this update.