# IETF notes

Notes

- SVCB <> IPNS as authority component
- RFC 9xxx: https://datatracker.ietf.org/doc/rfc9460/
- use-case: speed up HTTP/3 discovery
- skips many rounds for a non-CNAME lookup
- DANE ( https://datatracker.ietf.org/doc/html/rfc7671 )
- https://datatracker.ietf.org/doc/html/rfc9461
- DANE + QUIC with SVCBs draft by ben schwartz
- gap:
- IP literal in the name (old school)
- SVCB meta could include TLSA data if it fits in a URI (that allows us to drop the )
- TLSA
- NIH
- christian: underused registry, unknown adoption
- COSE chose not to use
- instead made [cose algorithms](https://www.iana.org/assignments/cose/cose.xhtml#cose-algorithms)
- ASCON also worth looking into
- Bob Moskowitz [reviewed it for NIST](https://csrc.nist.gov/csrc/media/Events/2023/lightweight-cryptography-workshop-2023/documents/accepted-papers/03-proposals-for-standardization-of-ascon-family.pdf)
- constrained contexts love it because it bundles all the crypto needs
- NIH - https://www.rfc-editor.org/rfc/rfc6920.html
- CBOR and IPv6 are STANDARDS ; PROPOSED STANDARD is almost as good, 99 of them
- other precedent: ORCHID - [RFC4843](https://datatracker.ietf.org/doc/html/rfc4843) 2007
- IANA reg has been terminated, renewed
- works in aviation, where routers are controlled and people can publish updates
- used /256 from an IP, but that was constrained
- NIH history by Dirk
- IPFS-like
- certificate-pinning
- : I tried getting it into web browser as an integrity tag
- SEARCH DATaTRACKER WHO CITES IT
- Christian: IPLD equiv as well (no RFC)
- Christian: find stakeholders with the onion-COAP thing; extensibility of non-HTTP URIs?
- key-based URIs
- Joshua Tan (DWeb) & Andrew Kaiser was presenting on DNS integrations
- Kaiser's presi: DNS addresses mapping to DHTs (via .arpa)
- Experimental RFC in ICN RG
- http header field registry - full of experimental RFC
- mikolai guetschow