API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Preference is stored in this browser only.

IETF RFC 3935
[ACTIVE]

A Mission Statement for the IETF

Metadata

Publisher
IETF
Doc Type
Best Practice
Pages
7
Abstract
This memo gives a mission statement for the IETF, tries to define the terms used in the statement sufficiently to make the mission statement understandable and useful, argues why the IETF needs a mission statement, and tries to capture some of the debate that led to this point. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Publication Date
2004-10-01
Status Note
Best Current Practice
DOI
10.17487/RFC3935
Link
https://doi.org/10.17487/RFC3935
Author(s)
Harald T. Alvestrand
Keyword(s)
Mission Statement
Latest version of IETF RFC 3935

Document Versions — IETF RFC 3935

  • ▶ IETF RFC 3935 (2004-10-01)
    THIS DOC [ACTIVE] [LATEST VERSION]
Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC3935.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 3935, A Mission Statement for the IETF. Available at https://doi.org/10.17487/RFC3935
Snippet:
IETF RFC 3935, A Mission Statement for the IETF. Available at https://doi.org/10.17487/RFC3935

HTML (ISO 690 compliant)

Preview:
IETF RFC 3935, A Mission Statement for the IETF. Available at https://doi.org/10.17487/RFC3935
Snippet:
<span class="citation"><cite>IETF RFC 3935</cite>, A Mission Statement for the IETF. Available at <a href="https://doi.org/10.17487/RFC3935" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3935</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 3935, A Mission Statement for the IETF
doi: 10.17487/RFC3935
url: https://doi.org/10.17487/RFC3935
Snippet:
<li>
<cite id="bib-rfc3935">IETF RFC 3935</cite>, A Mission Statement for the IETF
<span class="doi">10.17487/RFC3935</span>
</li>

Referenced By