Add RFC/document metadata to point to implementation status

[tfpauly]

Implementation status is removed before RFC publication. Could we instead link to something like in #13 ?

[tfpauly]

This could be similar to the IPR button on RFCs (metadata on RFCs, etc)

[tfpauly]

At out last call, we discussed adding a single tag that WG chairs and document authors could use to point to a resource for implementation status/info/guidance/code or interop testing.

The question is what the tag name should be! This is a bike shed, but we should decide on something before IETF 113 so we can add it for people working on the hackathon and in working groups.

For reference, the existing tags are: faq, github_org, github_repo, github_username, gitlab_username, jabber_log, jabber_room, mailing_list, mailing_list_archive, repo, slack, tracker, webpage, wiki, yc_entry, yc_impact

Some options to start us off:

• implementations (display as “Implementations”)
• impl_status (display as “Implementation Status”)
• related_code (display as “Related Code”)

Please reply with other options, or which option you prefer.

[martinthomson]

implementations is longish, but fine. While the patient is open, maybe add test_suite or similar.

[tfpauly]

Based on list discussion, too, David and I are leaning towards going with related_implementations -> Related Implementations

[eckelcu]

https://trac.ietf.org/trac/ietfdb/ticket/3560