[Sidrops] feedback on draft-michaelson-rpki-rta

[Job Snijders <[e-mail]>]

Dear group,

Reading draft-michaelson-rpki-rta-02 while writing some work-in-progress
code, I have some suggestions that hopefully improve the ease of use
of RTAs. WIP: http://sobornost.net/~job/rpki-client-rta.patch.txt

While it is useful property of RTAs they can be exchanged via email or
webforms (aka 'private B2B'), I also envision use cases where RTA
objects are best distributed through a publication protocol (public INR
holder statements). I forsee increased interoperability if the document
specifies some constraints on how to publish RTAs via RSYNC/RRDP, if the
Resource Holder chooses to use that path. Some suggestions for text are
included below.

Of course, from a cryptographic validation and 'permissionless
innovation' point-of-view the 'standalone' use of RTAs (without IANA
actions) is perfectly valid and applicable, however from an
interopability point-of-view I would encourage the group to also go
through the motions on describing how to publicly publish RTAs, and thus
target Standards Track.

Kind regards,

Job

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

OLD:
    Intended status: Experimental
NEW:
    Intended status: Standards Track

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

Section 8
OLD:
   An RTA and its associated EE certificates MAY appear on an RPKI
   Manifest and MAY be published in a repository.

NEW:
   An RTA and its associated EE certificates MAY appear on an RPKI
   Manifest and MAY be published in a repository. If an RTA appears
   on an RPKI Manifest, the RTA's file extension MUST be '.rta'.

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

OLD:
    Section 9
    IANA is entirely off the hook on this one.

NEW:
    Section 9.1 OID
    The IANA is requested to reference the '1.2.840.113549.1.9.16.1.36'
    OID as Resource Tagged Attestations in the RPKI Signed Objects
    registry created by [RFC6488].

    Section 9.2 File Extension
    IANA is requested to an item for the Ghostbusters Record file
    extension to the "RPKI Repository Name Scheme" created by [RFC6481]
    as follows: '.rta', 'Resource Tagged Attestation', ref: [draft-michaelson-rpki-rta]

    Section 9.3 Media Type
    The IANA is requested to register the media type application/rpki-rta as follows:

    Type name: application
    Subtype name: rpki-resourcetaggedattestations
    Required parameters: None
    Optional parameters: None
    Encoding considerations: binary
    Security considerations: Carries an Resource Tagged Attestation [draft-michaelson-rpki-rta]
    Applications that use this media type: RPKI users.
    Additional information:
     Content: This media type is a signed object, as defined
         in [draft-michaelson-rpki-rta], which contains an arbitary
         canonicalized payload as defined above in this document.
     Magic number(s): None
     File extension(s): .rta
    Person & email address to contact for further information:
     George Michaelson <[e-mail]>
    Intended usage: COMMON
    Restrictions on usage: None
    Author: George Michaelson <[e-mail]>
    Change controller: George Michaelson <[e-mail]>
--------------------------