BCP
Click on the red underlined text to get to the source
... without having some sort of structure. In the IETF's case, that
structure is provided by other organizations, as described in BCP 11 (RFC-2028),
"The Organizations Involved in the IETF Standards ...
... IETF Standards Process." If you
participate in the IETF and only read one BCP, this is the one you
should read.
...
... appointed for two years. The process for choosing the members of the
IESG is detailed in BCP 10(RFC-2727(-> 3777)), "IAB and IESG ...
... WGs. (The term "Working Group" is often seen capitalized, but
probably not for a very good reason.) BCP 25(RFC-2418), "IETF Working Group
...
... WG chairs is described in both BCP 11(RFC-2028) and BCP 25(RFC-2418).
Basically, their job is to keep the discussion ...
...
A much more complete explanation of these steps is contained in BCP
9(RFC-2026), "The Internet Standards Process ...
... Internet Standards Process." Anyone who writes a draft that
they hope will become an IETF standard must read BCP 9(RFC-2026) so that they
can follow the path of their document through the process. BCP ...
... BCP 9(RFC-2026) so that they
can follow the path of their document through the process. BCP 9(RFC-2026)
goes into great detail on a topic that is very often misunderstood,
...
...
There are also three sub-series of RFCs, known as FYIs, BCPs, and
STDs. The For Your Information RFC sub-series was created ...
... removed from the
online directories after six months. They are most definitely not
standards or even specifications. As BCP 9(RFC-2026) says:
...
...
The procedure for creating and advancing a standard is described in
BCP 9(RFC-2026). After an Internet Draft has been sufficiently discussed and
...
... last call. If the draft is an individual submission, the draft's
author or editor submits it to the appropriate Area Director. BCP 9(RFC-2026)
also describes the appeals process for people who feel that a Working
Group ...
... Support," written way back in 1989, had a short list of words that
had appeared to be useful, namely "must", "should", and "may". These
definitions were updated and further refined in BCP 14(RFC-2119), "Key words
for use in RFCs to Indicate Requirement Levels ...
... Requirement Levels," which is widely
referenced in current Internet standards. BCP 14(RFC-2119) also specifically
defines "must not" and "should not", and lists a few synonyms for the
...
...
In a standard, in order to make it clear that you're using the
definitions from BCP 14(RFC-2119), you should do two things. First, refer to
BCP ...
... BCP 14(RFC-2119), you should do two things. First, refer to
BCP 14 (although most people refer to it as RFC 2119, because that's
what BCP ...
... BCP 14 (although most people refer to it as RFC 2119, because that's
what BCP 14 tells you to do), so that the reader knows how you're
defining your words. Second, you should point out which instances of
the words you are using come from BCP ...
... BCP 14 tells you to do), so that the reader knows how you're
defining your words. Second, you should point out which instances of
the words you are using come from BCP 14. The accepted practice for
this is to capitalize the words. That is why you see "MUST" and
"SHOULD" capitalized in IETF standards ...
...
BCP 14 is a short document, and should be read by everyone who is
reading or writing IETF standards. Although the definitions of
...
... Internet standard that may need an IANA registry
needs to read BCP 26 (RFC-2434), "Guidelines for Writing an IANA Considerations
...
... methods for dealing with patents in standards are a
subject of much debate. You can read about the official rules in BCP
9(RFC-2026), but you should assume that the application of those rules is
...
... IPR can change at any time. Therefore, an IPR list
in a RFC could be incomplete and mislead the reader. BCP 9(RFC-2026) provides
specific text that should be added to RFCs where the author knows of
...
... 2727(-> 3777)) Operation of the Nominating and Recall Committees"
BCP 11 "The Organizations Involved in the IETF Standards Process"
(RFC-2028 ...