RFC 8416, "Simplified Local Internet Number Resource Management with the RPKI (SLURM)", August 2018

Errata ID: 7080
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Ben Maddison
Date Reported: 2022-08-10
Held for Document Update by: Warren Kumari (Ops AD)
Date Held: 2022-10-07

Section 3.4.2 says:

   The above is expressed as a value of the "bgpsecAssertions" member,
   as an array of zero or more objects.  Each object MUST contain one
   each of all of the following members:

   o  An "asn" member, whose value is a number.

   o  An "SKI" member, whose value is the Base64 encoding without
      trailing '=' (Section 5 of [RFC4648]) of the certificate's Subject
      Key Identifier as described in Section 4.8.2 of [RFC6487] (This is
      the value of the ASN.1 OCTET STRING without the ASN.1 tag or
      length fields.)

   o  A "routerPublicKey" member, whose value is the Base64 encoding
      without trailing '=' (Section 5 of [RFC4648]) of the equivalent to
      the subjectPublicKeyInfo value of the router certificate's public
      key, as described in [RFC8208].  This is the full ASN.1 DER
      encoding of the subjectPublicKeyInfo, including the ASN.1 tag and
      length values of the subjectPublicKeyInfo SEQUENCE.

It should say:

   The above is expressed as a value of the "bgpsecAssertions" member,
   as an array of zero or more objects.  Each object MUST contain one
   each of all of the following members:

   o  An "asn" member, whose value is a number.

   o  An "SKI" member, whose value is the Base64 encoding without
      trailing '=' (Section 5 of [RFC4648]) of the certificate's Subject
      Key Identifier as described in Section 4.8.2 of [RFC6487] (This is
      the value of the ASN.1 OCTET STRING without the ASN.1 tag or
      length fields.)

   o  A "routerPublicKey" member, whose value is the Base64 encoding
      without trailing '=' (Section 5 of [RFC4648]) of the equivalent to
      the subjectPublicKeyInfo value of the router certificate's public
      key, as described in [RFC8208].  This is the full ASN.1 DER
      encoding of the subjectPublicKeyInfo, including the ASN.1 tag and
      length values of the subjectPublicKeyInfo SEQUENCE.

   In addition, each object MAY contain one optional "comment" member,
   whose value is a string.

Notes:

The "comment" member is allowed to appear in every other structure defined by the document, and was clearly intended to be allowed here too, since it appears in the examples presented in sections 3.4.2 and 3.5

[Warren Kumari: See thread https://mailarchive.ietf.org/arch/msg/sidrops/uEc7K01ex0GJ6tE_FqfDwDTZTws/

We are not aware of any implementations which will choke on comments]

Report New Errata