[Sidrops] IANA early allocation for draft-ietf-sidrops-signed-tal?

[Job Snijders <[e-mail]>]

Hi all,

I was looking at draft-ietf-sidrops-signed-tal-09 and its compagnion
testbed at https://rpki-testbed.apnic.net/signed-tal.html

The internet-draft has TBD as content-type identifier:

    id-ct-signedTAL OBJECT IDENTIFIER ::= { iso(1) member-body(2) us(840)
        rsadsi(113549) pkcs(1) pkcs9(9) smime(16) ct(1) TBD }

The testbed uses 1.2.840.113549.1.9.16.1.37 (id-ct-utf8TextWithCRLF)

I can implement a validator & decoder in rpki-client's "file mode",
which could be used to display the contents of TAK files; this would aid
TA operators in the issuance & publication of TAK files, or software
package maintainers responsible for packages like "rpki-trust-anchors"
in Debian.

However - (I believe I mentioned this before) - I can't/won't implement
the ability to overwrite operating system-provided TALs with a TAL
gleaned from a TAK file, as that would mean crossing an unsurmountable
write-barrier.

I'd like to propose to use the RFC 7120 process for a code point: OIDs
are plentiful and cheap, and help us organise things.

Kind regards,

Job