Skip to content

About

Internet-Drafts and specification text by Anivar Aravind

Resources

Stars

1 star

Watchers

0 watching

Forks

Latest commit

 

History

7 Commits

Folders and files

Repository files navigation

IETF contributions

Internet-Drafts and specification text by Anivar Aravind.

This repository is the canonical source for the drafts listed below. The datatracker holds the submitted revisions; the markdown here is what they are built from.

Drafts

Draft Claim Revision
draft-aravind-oauth-decision-subject dsub -00, 19 July 2026
draft-aravind-oauth-operator-of-record opr -00, 19 July 2026

Agent-authorization records model who acts and who delegated. Neither of the two parties these claims name is currently expressible: dsub names the party a decision is about, and opr marks who operated when a presentation or decision was produced, in the case where key binding cannot distinguish a human from an agent acting for one.

Both are descriptive. Neither grants authority, and neither is an input to an authorization decision. They are intended for the IANA JWT Claims registry under RFC 7519 Section 10.1.

They are separate documents by design. dsub stands alone and carries no dependency; opr is motivated by the wallet substrate and would drag that motivation into dsub if the two were merged. Recombining them would make the smaller claim harder to adopt, not easier.

Contributions to other documents

Specification text written for drafts authored by others.

Document Author Contribution Status
draft-ranjbar-dane-did Kaveh Ranjbar Section 10.2 Continuity of Holding; Section 4 alias signer check posted in -01, 1 Aug 2026, as co-author

Section 10.2 was merged in full into draft-ranjbar-dane-did-01, which carries Anivar as co-author rather than in the acknowledgments, and the alias paragraph of Section 4 was adopted from the pre-posting review verbatim. The text under contributions/dane-did/ is the source both were merged from, and reference/posted/ holds both submitted revisions, -00 and -01, so the effect of the contribution is diffable rather than asserted.

Building

Requires kramdown-rfc and xml2rfc on PATH.

make          build every draft to text and html under build/
make check    validate the XML and run the pre-submission gate
make verify   diff the built text against the submitted revision
make tools    report toolchain versions

make check enforces three things that must hold before a revision is uploaded: no editor notes survive into the output, no national infrastructure product names appear in a draft body, and dsub and opr have not been recombined.

make verify rebuilds and compares against reference/posted/, which holds the exact text of each submitted revision. It exists so a toolchain change cannot quietly alter a draft that is already public.

Known benign difference

Against xml2rfc 3.34.0, make verify reports a two-line difference in the BCP 14 boilerplate of both -00 drafts. Current xml2rfc keeps BCP 14 unbroken across a line where the version used for the original submission split it. The difference is line-wrapping in generated boilerplate only. All other content matches byte for byte.

Licence

Contributions are made under the IETF Trust's Note Well and the BSD licence set out in RFC 8174 and the TLP.

About

Internet-Drafts and specification text by Anivar Aravind

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages