References from draft-ietf-mtgvenue-iaoc-venue-selection-process
This is an experimental product. These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| BCP 101 |
BCP 101 Update for IPR Trust Refs Ref'd by |
Best Current Practice | normatively references | |
| BCP 14 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| BCP 95 |
A Mission Statement for the IETF Refs Ref'd by |
Best Current Practice | informatively references | |
| draft-ietf-mtgvenue-meeting-policy |
High level guidance for the meeting policy of the IETF Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 3935 |
A Mission Statement for the IETF Refs Ref'd by |
Best Current Practice | informatively references | |
| RFC 4071 |
Structure of the IETF Administrative Support Activity (IASA) Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 6771 |
Considerations for Having a Successful "Bar BOF" Side Meeting Refs Ref'd by |
Informational | informatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words Refs Ref'd by |
Best Current Practice | normatively references |