New Registration request for /.well-known/faf

[Wolfe-Jam]

Hello,

Please confirm that:

• You have read and understood the requirements for registration (RFC 8615, Section 3.1).
• You have checked the registry and found no current value that meets your needs. (No faf suffix is currently registered.)
• Your specification reference URL is stable. — The reference is an IETF Internet-Draft on the Datatracker.

If so, please enter the details of the well-known URI below:

URI suffix: faf

Change controller: FAF Foundation (team@faf.one)

Specification document(s):
draft-wolfe-faf-format-02, Section 6 ("The faf Well-Known URI") — https://datatracker.ietf.org/doc/draft-wolfe-faf-format/

Any additional information:

• The specification defines /.well-known/faf as a discovery anchor. A GET request returns the origin's context document with media type application/vnd.faf+yaml. The document may also reference associated resources (.fafm memory and .fafa agent documents).
• As an Individual Submission Internet-Draft (not yet published as an RFC), this registration would be provisional. It can be updated to permanent status if/when the document is published as an RFC.
• The name faf is tied to the existing IANA-registered media type application/vnd.faf+yaml (registered 2025-10-30) and is not a generic term.
• Current deployment includes integrations with Model Context Protocol (MCP) servers for Claude, Grok, and Gemini, with packages distributed via npm, PyPI, and crates.io. The FAF family currently holds three IANA-registered media types.

Thank you,
James Wolfe
FAF Foundation
team@faf.one

[mnot]

Parking until the draft is adopted on a stream.