BGPsec Algorithms, Key Formats, and Signature Formats
draft-ietf-sidr-bgpsec-algs-18

[Ballot comment]

- As Randy commented, if the goal is to smallerise the
packets, it'd have been nice to use eddsa here but I assume
that wasn't practical due to the timing and the number of
RPKI elements that'd need to be defined for that? Is that
right? Did the WG consider using 25519 instead of p256?  If
not, is it worth asking, just in case everyone loves the
idea more than this?

- Documents like this are better with test vectors included
or referenced. Couldn't you add those or some pointers to
those?

- To answer Mirja's point: Anyone who knows RFC6090 knows
that it more or less only exists because of IPR silliness.
And sadly, even though 6090 only references documents that
predate relevant IPR filings by >20 years, even 6090 still
got an (IMO also silly) IPR declaration.  [1] Sheesh, but
whaddya gonna do? :-( Anyway, I don't think there's a need
to, or benefit from, adding text here about the well-known
situation with ECC IPR that I believe stymied deployment
for at least a decade.

  [1] https://datatracker.ietf.org/ipr/search/?rfc=6090&submit=rfc

[Ballot comment]
As noted by Jouni in his OPS DIR review, and acknowledged by Sean Turner
> o Section 7 IANA Considerations says on line 192:
>  "Infrastructure (RPKI) group.  The one-octet BGPsec Algorithm Suite”
>                                    ^^^^^^^^^
>  However, in the following table and text it says nothing about
>  values 0x10-0xff. Are these unassigned or reserved? This is a bit
>  confusing since the table lists values up to 0xF (one-nibble).

Sigh - that should be:

+------------+------------+-------------+---------------------+
| 0x2-0xEF  | Unassigned | Unassigned  | This draft          |
+------------+------------+-------------+---------------------+
| 0xFF      | Reserved  | Reserved    | This draft          |
+------------+------------+-------------+---------------------+

[Ballot comment]
Just a thought: Would it be useful to add an IESG note saying something like in the sheperd write-up:
"[...] there are published references
    that preceded the filing of the patent, especially those
    mentioned in RFC6090.  RFC6090 notes that its descriptions
    "may be useful for implementing the fundamental algorithms without
    using any of the  specialized methods that were developed in
    following years.""
I know we usuall don't do things like this. But I'm wondering how someone who wants to implement this should figure this out otherwise....?

[Ballot comment]
Maybe I missed it, but I don't think the document is clear on why new algorithms are needed. Is this specified in one of referenced documents?

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Services Operator has completed its review of draft-ietf-sidr-bgpsec-algs-15. If any part of this review is inaccurate, please let us know.

The IANA Services Operator understands that, upon approval of this document, there is a single action which we must complete.

A new registry is to be created called the BGPsec Algorithm Suite Registry. This new registry is to be a subregistry of the Resource Public Key Infrastructure (RPKI) registry located in:

https://www.iana.org/assignments/rpki

The new registry is to be managed via Standards Action as defined in RFC 5226.

There are initial registrations in the new registry as follows:

Algorithm Suite Identifier  Digest Algorithm  Signature Algorithm  Reference
+------------+------------+-------------+---------------------+
| 0x0 | Reserved | Reserved | [ RFC-to-be ] |
+------------+------------+-------------+---------------------+
| 0x1 | SHA-256 | ECDSA P-256 | [FIPS 180-4][FIPS 186-4][RFC6090] |
+------------+------------+-------------+---------------------+
| 0x2-0xE | Unassigned | Unassigned |
+------------+------------+-------------+---------------------+
| 0xF | Reserved | Reserved | [ RFC-to-be ] |
+------------+------------+-------------+---------------------+

The IANA Services Operator understands that this is the only action required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed.

Thank you,

Amanda Baber
Lead IANA Services Specialist
PTI

The following Last Call announcement was sent out:

From: The IESG
To: "IETF-Announce"
CC: draft-ietf-sidr-bgpsec-algs@ietf.org, sidr@ietf.org, "Sandra L. Murphy" , sidr-chairs@ietf.org, sandy@tislabs.com, aretana@cisco.com
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (BGPsec Algorithms, Key Formats, & Signature Formats) to Proposed Standard


The IESG has received a request from the Secure Inter-Domain Routing WG
(sidr) to consider the following document:
- 'BGPsec Algorithms, Key Formats, & Signature Formats'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-11-28. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


  This document specifies the algorithms, algorithm parameters,
  asymmetric key formats, asymmetric key size and signature format used
  in BGPsec (Border Gateway Protocol Security).  This document updates
  the Profile for Algorithms and Key Sizes for Use in the Resource
  Public Key Infrastructure (ID.sidr-rfc6485bis).




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-sidr-bgpsec-algs/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-sidr-bgpsec-algs/ballot/

The following IPR Declarations may be related to this I-D:

  https://datatracker.ietf.org/ipr/1965/
  https://datatracker.ietf.org/ipr/1967/



The document contains these normative downward references.
See RFC 3967 for additional information:
    rfc6090: Fundamental Elliptic Curve Cryptography Algorithms (Informational - IETF stream)
    rfc2986: PKCS #10: Certification Request Syntax Specification Version 1.7 (Informational - Legacy stream)
Note that both of these references may already be listed in the acceptable Downref Registry.
(https://trac.tools.ietf.org/group/iesg/trac/wiki/DownrefRegistry)

Also, the document contains these non-RFC normative references:
    [DSS]    National Institute of Standards and Technology (NIST), U.S.
                    Department of Commerce, "Digital Signature Standard", FIPS
                    Publication 186-4, July 2013.

  [SHS]    National Institute of Standards and Technology (NIST), U.S.
                  Department of Commerce, "Secure Hash Standard", FIPS
                  Publication 180-4, August 2015.

== AD Review of draft-ietf-sidr-bgpsec-algs-15 ==

Thanks for working on this document.

I have some comments below, mostly minor.  I will start the IETF Last Call shortly, but I would like to see an update before the IESG Telechat.

Thanks!

Alvaro.



M. IANA Considerations:

M1. “Assignments consist of a digest algorithm name, signature algorithm name, and the algorithm suite identifier value.”  The request made to IANA in this registry would be for the Algorithm Suite Identifier, and not the Digest or Signature Algorithms, right?  IOW, a request would be made for the ID given the suite that is to be registered.  The text above gives the impression that IANA is to assign everything and not just the ID.  Please clarify.

M2. Please reorganize the registry table to list the Suite ID in the first column – this should help the readability.

M3. Clearly, the TBD value is 0x1.  Please call it out explicitly – and simply list the rest of the identifiers explicitly (0x2-0xE).  The TBD value should be then explicitly mentioned in Section 2 (“…Algorithm Suite Identifier from Section 7…”).

M4. [minor] “Future assignments are to be made using either the Standards Action process defined in [RFC5226], or the Early IANA Allocation process defined in [RFC7120].”  The use of the early allocation process is a given based on the fact that Standards Action is the overall registration policy, so there’s no need to call rfc7120 out.



Minor:
P1. rfc6485bis is now rfc7935.

As required by RFC 4858, this is the current template for the Document
Shepherd Write-Up.

Changes are expected over time. This version is dated 24 February 2012.

(1) What type of RFC is being requested (BCP, Proposed Standard,
Internet Standard, Informational, Experimental, or Historic)?  Why
is this the proper type of RFC?  Is this type of RFC indicated in the
title page header?

  The document is intended as a Standards Track RFC.

  The document adds an additional algorithm to the RPKI, updating
  RFC6485 (as recently updated). 

  The algorithm defined in this document is used in BGPsec.  At time
  of writing, there is an update to RFC6485 that has been approved
  for publication.  RFC6485 and its update define algorithms that
  are used in RPKI for origin validation, where this document defines
  algorithms that are used in path validation by BGPsec.

  The title page says "Intended status: Standards Track".

(2) The IESG approval announcement includes a Document Announcement
Write-Up. Please provide such a Document Announcement Write-Up. Recent
examples can be found in the "Action" announcements for approved
documents. The approval announcement contains the following sections:

Technical Summary

  This document specifies the algorithms, algorithm parameters,
  asymmetric key formats, asymmetric key size and signature format used
  in BGPsec (Border Gateway Protocol Security).  This document updates
  the Profile for Algorithms and Key Sizes for Use in the Resource
  Public Key Infrastructure (draft-ietf-sidr-rfc6485bis, recently
  approved for publication).

Working Group Summary

  This document has had consistent interest from the working group.
  The document passed wglc and then waited for publication until
  the BGPsec protocol was mature.  In the meantime, it absorbed some
  changes from rfc6485bis that were made during IESG consideration.

Document Quality

  There is one known implementation of the generation of certificates
  that use the algorithm and key format defined in this draft.  There are
  two known implementations of BGPsec that use the algorithms defined
  in this draft.  All are open source implementations.

Personnel

  Document Shepherd: Sandra Murphy
  Responsible Area Director: Alvaro Retana

(3) Briefly describe the review of this document that was performed by
the Document Shepherd.  If this version of the document is not ready
for publication, please explain why the document is being forwarded to
the IESG.

  The document shepherd has reviewed the current document, and many
  previous versions over the course of its progress.

(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed?

  The shepherd has no concerns about the level of reviews. 

(5) Do portions of the document need review from a particular or from
broader perspective, e.g., security, operational complexity, AAA, DNS,
DHCP, XML, or internationalization? If so, describe the review that
took place.

  There is no need for review from any particular or broader perspective.

(6) Describe any specific concerns or issues that the Document Shepherd
has with this document that the Responsible Area Director and/or the
IESG should be aware of? For example, perhaps he or she is uncomfortable
with certain parts of the document, or has concerns whether there really
is a need for it. In any event, if the WG has discussed those issues and
has indicated that it still wishes to advance the document, detail those
concerns here.

  The shepherd has no concerns or issues with this document and saw
  no unaddressed concerns in the working group discussions.

(7) Has each author confirmed that any and all appropriate IPR
disclosures required for full conformance with the provisions of BCP 78
and BCP 79 have already been filed. If not, explain why.

    All authors have confirmed.

(8) Has an IPR disclosure been filed that references this document?
If so, summarize any WG discussion and conclusion regarding the IPR
disclosures.

    Two IPR disclosures have been filed against this draft by
    Certicom Corporation (the second is an update of the first).
    The filing declares that the Patent Holder will make a license available
    on fair, reasonable and non-discriminatory terms and conditions, under
    conditions of reciprocity, etc.  See
    https://datatracker.ietf.org/ipr/1965/
    https://datatracker.ietf.org/ipr/1967/

    After the filing, the IPR was discussed at the IETF86 meeting.
    The meeting discussion mentioned that there are published references
    that preceded the filing of the patent, especially those
    mentioned in RFC6090.  RFC6090 notes that its descriptions
    "may be useful for implementing the fundamental algorithms without
    using any of the  specialized methods that were developed in
    following years."

    The working group had previously considered work that had IPR
    filings, and had concluded that this was not the desired path but
    was not forbidden.  This was mentioned in the IETF86 discussion.

(9) How solid is the WG consensus behind this document? Does it
represent the strong concurrence of a few individuals, with others
being silent, or does the WG as a whole understand and agree with it? 

    The working group support for this work is solid.

(10) Has anyone threatened an appeal or otherwise indicated extreme
discontent? If so, please summarise the areas of conflict in separate
email messages to the Responsible Area Director. (It should be in a
separate email because this questionnaire is publicly available.)

    No one has threatened an appeal or expressed extreme discontent.

(11) Identify any ID nits the Document Shepherd has found in this
document. (See https://www.ietf.org/tools/idnits/ and the Internet-Drafts
Checklist). Boilerplate checks are not enough; this check needs to be
thorough.

    Summary: 2 errors (**), 0 flaws (~~), 0 warnings (==), 4 comments (--).

    The errors are downrefs to informational RFCs.  One is RFC2986, which
    is an IETF re-publication of a document from outside the IETF. The other
    is to RFC6090, which is a list of references published outside the
    IETF.  Both are properly Informational.  Both are necessary to the
    document.

(12) Describe how the document meets any required formal review
criteria, such as the MIB Doctor, media type, and URI type reviews.

    No formal review is required for this document.

(13) Have all references within this document been identified as
either normative or informative?

    All references within this document have been identified as
    either normative or informative.

(14) Are there normative references to documents that are not ready for
advancement or are otherwise in an unclear state? If such normative
references exist, what is the plan for their completion?

    All normative references in this document are RFCs or are
    permanently published outside the IETF.

(15) Are there downward normative references references (see RFC 3967)?
If so, list these downward references to support the Area Director in
the Last Call procedure.

    See the discussion in question 11 of the two downward references to
    RFCs that are Informational:
    [RFC6090] McGrew, D., Igoe, K., and M. Salter, "Fundamental Elliptic
              Curve Cryptography Algorithms", RFC 6090, February 2011.

    [RFC2986] Nystrom, M. and B. Kaliski, "PKCS #10: Certification
              Request Syntax Specification Version 1.7", RFC 2986,
              November 2000.

  Both are RFCs that point to material published outside the IETF.

(16) Will publication of this document change the status of any
existing RFCs? Are those RFCs listed on the title page header, listed
in the abstract, and discussed in the introduction? If the RFCs are not
listed in the Abstract and Introduction, explain why, and point to the
part of the document where the relationship of this document to the
other RFCs is discussed. If this information is not in the document,
explain why the WG considers it unnecessary.

    Publication of this document updates draft-ietf-sidr-rfc6485bis,
    recently approved for publication.

    This is noted in the header, the abstract, and the introduction.

    draft-ietf-sidr-rfc6485bis updates RFC6485.

(17) Describe the Document Shepherd's review of the IANA considerations
section, especially with regard to its consistency with the body of the
document. Confirm that all protocol extensions that the document makes
are associated with the appropriate reservations in IANA registries.
Confirm that any referenced IANA registries have been clearly
identified. Confirm that newly created IANA registries include a
detailed specification of the initial contents for the registry, that
allocations procedures for future registrations are defined, and a
reasonable name for the new registry has been suggested (see RFC 5226).

    This document requests the definition of a new registry, to be
    titled "BGPsec Algorithm Suite Registry", in the RPKI group.
    Algorithms used specifically for BGPsec will be registered in that
    registry.

    This document defines the initial contents of the registry, which
    are the algorithms defined in this document.  It also defines how
    future registrations will be made - by either Standards Action or
    Early IANA process.  The document also defines what future
    registrations must include - a digest algorithm name, a signature
    algorithm name, and an algorithms suite identifier.

(18) List any new IANA registries that require Expert Review for future
allocations. Provide any public guidance that the IESG would find
useful in selecting the IANA Experts for these new registries.

    No new IANA registries are created by this document that require
    Expert Review.

(19) Describe reviews and automated checks performed by the Document
Shepherd to validate sections of the document written in a formal
language, such as XML code, BNF rules, MIB definitions, etc.

    There are no sections of this document written in a formal language.

backfilling history:
wglc was issued 16 October.  Comments supported publication.  However, this draft used the same Additional Requirements text from RFC6485 that troubled the IESG during their draft-ietf-sidr-rfc6485bis review.  Progress of this draft was held up for wg resolution of the text of that section in a new version of rfc6485bis.  The wg came to consensus on the new text for that section in draft-ietf-sidr-rfc6485bis, so this draft is directed to adopt the same text.