Updates AGENTS.md to reflect usage of the <rfc>

tag that was added earlier this year.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1935474 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/AGENTS.md b/docs/manual/AGENTS.md
index b8b6c0775a02d9eaf0efb68c7c02080f69ba5996..9e6e9d4f7ea05e50d3e6f2bd113534ca94abbd23 100644 (file)
--- a/docs/manual/AGENTS.md
+++ b/docs/manual/AGENTS.md
@@ -27,14 +27,33 @@ This is the documentation source for the [Apache HTTP Server](https://httpd.apac
 
 ## External Link Conventions
 
+### `<rfc>` — RFC References
 
-Always link to the IETF Datatracker for RFC references:
+Use the `<rfc>` tag for all RFC references. The element content is the
+RFC number (digits only). The rendered output is "RFC NNNN" linked to
+the canonical URL.
+
+```xml
+<rfc>7230</rfc>
+<rfc>9110</rfc>
+```
+
+To link to a numbered section, use the `section` attribute:
+```xml
+<rfc section="14.24">2616</rfc>
 ```
-https://datatracker.ietf.org/doc/html/rfcNNNN
+
+To link to a named anchor (appendix, named heading, etc.), use `anchor`:
+```xml
+<rfc anchor="appendix-B">7231</rfc>
+<rfc anchor="name-upgrade">9110</rfc>
 ```
-For section-specific links, use fragment anchors: `#section-N.N`
 
-Do NOT use `tools.ietf.org`, `www.rfc-editor.org`, `www.ietf.org/rfc/`, `www.w3.org/Protocols/`, `www.faqs.org/rfcs/`, or any other RFC mirror. These are legacy patterns — `datatracker.ietf.org` is the canonical standard for this documentation.
+Do **not** use both `section` and `anchor` on the same element.
+
+Do **not** use `<a href="...">` with RFC URLs when the `<rfc>` tag can
+express the link. Use `<a>` only for non-RFC resources, IETF drafts, or
+cases where the display text must differ from "RFC NNNN".
 
 ## Directive Syntax Definitions