]> August Cellars

ietf@augustcellars.com

Symantec Website Security

Rick_Andrews@symantec.com

Security Area Curdle When the Curdle Security Working Group was chartered, a range of object identifiers was donated by Symantec Website Security for use by that working group. This document describes the range of identifiers that were assigned in that donated range, transfers control of that range to IANA, and establishes IANA allocation policies for any future assignments within that range. The source for this draft is being maintained in GitHub. Suggested changes should be submitted as pull requests at . Instructions are on that page as well. Editorial changes can be managed in GitHub, but any substantial issues need to be discussed on the LAMPS mailing list.

When the Curdle Security Working Group was chartered, a range of object identifiers was donated by Symantec Website Security for use by that working group. These object identifiers are primarily used with Abstract Syntax Notation (ASN.1) . The ASN.1 specifications continue to evolve, but object identifiers can be used with any and all versions of ASN.1. The Curdle object identifier range is:

{ iso (1) identified-organization (3) thawte (101) 100 } to { iso (1) identified-organization (3) thawte (101) 127 }

This document describes the object identifiers that were assigned in that donated range, transfers control of the range to IANA, and establishes IANA allocation policies for any future assignments within that range.

IANA is asked to create one new registry table.

Within the SMI-numbers registry, add an "SMI Security for Curdle" table with the three columns: DecimalDescriptionReferences 100Reserved for future sub-registry 110id-X25519 111id-X448 112id-EdDSA25519 113id-EdDS448 114id-EdDSA25519-ph 115id-EdDS448=ph 120Safecurves-pkix-0 The column 'Decimal' is required to be a number between 100 and 127 inclusive. Future updates to this table require both 'Specification Required' and 'Expert Review' as defiened in .

This document populates an IANA registry, and it raises no new security considerations. The protocols that specify these values include the security considerations associated with their usage.

&RFC5226; &CURDLE;

Our thanks go out to Symantec for donating the range of OIDs covered in this document. This document stole text heavily from a previous document doing similar thing by Russ Housely. Copying always makes things easier and less error prone.