rfc9592v2.txt | rfc9592.txt | |||
---|---|---|---|---|
Internet Engineering Task Force (IETF) N. ten Oever | Internet Engineering Task Force (IETF) N. ten Oever | |||
Request for Comments: 9592 University of Amsterdam | Request for Comments: 9592 University of Amsterdam | |||
Obsoletes: 6722 G. Wood | Obsoletes: 6722 G. Wood | |||
Category: Informational IETF Administration LLC | Category: Informational IETF Administration LLC | |||
ISSN: 2070-1721 May 2024 | ISSN: 2070-1721 June 2024 | |||
Retiring the Tao of the IETF | Retiring the Tao of the IETF | |||
Abstract | Abstract | |||
This document retires and obsoletes the Tao of the IETF as an IETF- | This document retires and obsoletes the Tao of the IETF as an IETF- | |||
maintained document. This document also obsoletes RFC 6722, which | maintained document. This document also obsoletes RFC 6722, which | |||
describes the publication process of the Tao. Furthermore, this | describes the publication process of the Tao. Furthermore, this | |||
document describes the rationale for the retirement of the Tao. For | document describes the rationale for the retirement of the Tao. For | |||
archival purposes, the last version of the Tao is included in the | archival purposes, the last version of the Tao is included in the | |||
skipping to change at line 67 ¶ | skipping to change at line 67 ¶ | |||
2.2. Unwieldy Format | 2.2. Unwieldy Format | |||
2.3. Changing Participation Modes | 2.3. Changing Participation Modes | |||
3. Going Forward | 3. Going Forward | |||
3.1. New Communications Opportunities | 3.1. New Communications Opportunities | |||
4. Conclusion | 4. Conclusion | |||
5. Security Considerations | 5. Security Considerations | |||
6. IANA Considerations | 6. IANA Considerations | |||
7. Informative References | 7. Informative References | |||
Appendix A. Last Edition of the Tao | Appendix A. Last Edition of the Tao | |||
Abstract | Abstract | |||
1 Introduction | 1. Introduction | |||
1.1 Acronyms and Abbreviations Used in the Tao | 1.1. Acronyms and Abbreviations Used in the Tao | |||
2 What is the IETF? | 2. What is the IETF? | |||
2.1 Humble Beginnings | 2.1. Humble Beginnings | |||
2.2 The Hierarchy | 2.2. The Hierarchy | |||
2.3 IETF Mailing Lists | 2.3. IETF Mailing Lists | |||
3 IETF Meetings | 3. IETF Meetings | |||
3.1 Registration | 3.1. Registration | |||
3.2 Take the Plunge and Stay All Week! | 3.2. Take the Plunge and Stay All Week! | |||
3.3 Newcomer Training | 3.3. Newcomer Training | |||
3.4 Dress Code | 3.4. Dress Code | |||
3.5 Working Group Meetings | 3.5. Working Group Meetings | |||
3.6 Seeing Spots Before Your Eyes | 3.6. Seeing Spots Before Your Eyes | |||
3.7 Terminal Room | 3.7. Terminal Room | |||
3.8 Meals and Snacks | 3.8. Meals and Snacks | |||
3.9 Social Event | 3.9. Social Event | |||
3.10 Agenda | 3.10. Agenda | |||
3.11 EMODIR to the Rescue | 3.11. EMODIR to the Rescue | |||
3.12 Where Do I Fit In? | 3.12. Where Do I Fit In? | |||
3.13 Proceedings | 3.13. Proceedings | |||
3.14 Other General Things | 3.14. Other General Things | |||
3.15 Remote Participation | 3.15. Remote Participation | |||
4 Working Groups | 4. Working Groups | |||
4.1 Working Group Chairs | 4.1. Working Group Chairs | |||
4.2 Getting Things Done in a Working Group | 4.2. Getting Things Done in a Working Group | |||
4.3 Working Group Documents | 4.3. Working Group Documents | |||
4.4 Preparing for Working Group Meetings | 4.4. Preparing for Working Group Meetings | |||
4.5 Working Group Mailing Lists | 4.5. Working Group Mailing Lists | |||
4.6 Interim Working Group Meetings | 4.6. Interim Working Group Meetings | |||
5 BOFs and Dispatching | 5. BOFs and Dispatching | |||
6 RFCs and Internet-Drafts | 6. RFCs and Internet-Drafts | |||
6.1 The Overall Process | 6.1. The Overall Process | |||
6.2 Common Issues | 6.2. Common Issues | |||
6.3 Writing an Internet-Draft | 6.3. Writing an Internet-Draft | |||
6.4 Standards-Track RFCs | 6.4. Standards-Track RFCs | |||
6.5 RFCs Other than Standards-Track | 6.5. RFCs Other than Standards-Track | |||
7 How to Contribute to the IETF | 7. How to Contribute to the IETF | |||
7.1 What You Can Do | 7.1. What You Can Do | |||
7.2 What Your Company Can Do | 7.2. What Your Company Can Do | |||
8 IETF and the Outside World | 8. IETF and the Outside World | |||
8.1 IETF and Other SDOs | 8.1. IETF and Other SDOs | |||
8.2 Press Coverage of the IETF | 8.2. Press Coverage of the IETF | |||
Acknowledgements | Acknowledgements | |||
Authors' Addresses | Authors' Addresses | |||
1. Introduction | 1. Introduction | |||
Since its publication as [RFC1391] in 1993, The "Tao of the IETF" | Since its publication as [RFC1391] in 1993, The "Tao of the IETF" | |||
("Tao") has described the inner workings of IETF meetings and Working | ("Tao") has described the inner workings of IETF meetings and Working | |||
Groups, discussed organizations related to the IETF, and introduced | Groups, discussed organizations related to the IETF, and introduced | |||
the working processes to new participants. The Tao never was a | the working processes to new participants. The Tao never was a | |||
formal IETF process document, but rather a community-developed and | formal IETF process document, but rather a community-developed and | |||
skipping to change at line 270 ¶ | skipping to change at line 270 ¶ | |||
Abstract | Abstract | |||
This document introduces you to the "ways of the IETF": it will | This document introduces you to the "ways of the IETF": it will | |||
convey the might and magic of networking people and packets in the | convey the might and magic of networking people and packets in the | |||
Internet's most prominent standards body. In this document we | Internet's most prominent standards body. In this document we | |||
describe the inner workings of IETF meetings and Working Groups, | describe the inner workings of IETF meetings and Working Groups, | |||
discuss organizations related to the IETF, and introduce the | discuss organizations related to the IETF, and introduce the | |||
standards process. This is not a formal IETF process document but an | standards process. This is not a formal IETF process document but an | |||
informal and informational overview. | informal and informational overview. | |||
1 Introduction | 1. Introduction | |||
The Internet Engineering Task Force (IETF) is the largest standard | The Internet Engineering Task Force (IETF) is the largest standard | |||
development organization (SDO) for the Internet. Since its early | development organization (SDO) for the Internet. Since its early | |||
years, participation in the IETF has grown phenomenally. In-person | years, participation in the IETF has grown phenomenally. In-person | |||
attendance at face-to-face meetings now averages between 1000 and | attendance at face-to-face meetings now averages between 1000 and | |||
1500 participants (https://datatracker.ietf.org/stats/meeting/ | 1500 participants (https://datatracker.ietf.org/stats/meeting/ | |||
overview/). At any given meeting, around 200 attendees are | overview/). At any given meeting, around 200 attendees are | |||
_newcomers_ (defined by the IETF as someone who has attended five or | _newcomers_ (defined by the IETF as someone who has attended five or | |||
fewer meetings), and many of those go on to become regular | fewer meetings), and many of those go on to become regular | |||
participants. When the IETF was smaller, it was relatively easy for | participants. When the IETF was smaller, it was relatively easy for | |||
skipping to change at line 313 ¶ | skipping to change at line 313 ¶ | |||
Many types of IETF documentation are mentioned here. The IETF | Many types of IETF documentation are mentioned here. The IETF | |||
publishes its technical documentation as RFCs, still known by their | publishes its technical documentation as RFCs, still known by their | |||
historical term _Requests for Comments_. (Sometimes people joke that | historical term _Requests for Comments_. (Sometimes people joke that | |||
it stands for _Request for Compliance_.) STDs are RFCs identified as | it stands for _Request for Compliance_.) STDs are RFCs identified as | |||
"standards", and BCPs are RFCs that represent thoughts on Best | "standards", and BCPs are RFCs that represent thoughts on Best | |||
Current Practices in the Internet. Both STDs and BCPs are also RFCs. | Current Practices in the Internet. Both STDs and BCPs are also RFCs. | |||
For example, BCP 9 (https://www.rfc-editor.org/info/bcp9) points to a | For example, BCP 9 (https://www.rfc-editor.org/info/bcp9) points to a | |||
collection of RFCs that describe the IETF's standardization | collection of RFCs that describe the IETF's standardization | |||
processes. See RFCs and Internet-Drafts for more details. | processes. See RFCs and Internet-Drafts for more details. | |||
1.1 Acronyms and Abbreviations Used in the Tao | 1.1. Acronyms and Abbreviations Used in the Tao | |||
Some of the acronyms and abbreviations from this document are listed | Some of the acronyms and abbreviations from this document are listed | |||
below. | below. | |||
+=======+=====================================================+ | +=======+=====================================================+ | |||
| Term | Meaning | | | Term | Meaning | | |||
+=======+=====================================================+ | +=======+=====================================================+ | |||
| AD | Area Director | | | AD | Area Director | | |||
+-------+-----------------------------------------------------+ | +-------+-----------------------------------------------------+ | |||
| BCP | Best Current Practice (a type of RFC) | | | BCP | Best Current Practice (a type of RFC) | | |||
skipping to change at line 356 ¶ | skipping to change at line 356 ¶ | |||
+-------+-----------------------------------------------------+ | +-------+-----------------------------------------------------+ | |||
| RFC | Request for Comments | | | RFC | Request for Comments | | |||
+-------+-----------------------------------------------------+ | +-------+-----------------------------------------------------+ | |||
| STD | Standard (a type of RFC) | | | STD | Standard (a type of RFC) | | |||
+-------+-----------------------------------------------------+ | +-------+-----------------------------------------------------+ | |||
| WG | Working Group | | | WG | Working Group | | |||
+-------+-----------------------------------------------------+ | +-------+-----------------------------------------------------+ | |||
Table 1 | Table 1 | |||
2 What is the IETF? | 2. What is the IETF? | |||
The IETF has no members and no dues; it is a loosely self-organized | The IETF has no members and no dues; it is a loosely self-organized | |||
group of people who contribute to the engineering and evolution of | group of people who contribute to the engineering and evolution of | |||
Internet technologies. It is the principal body engaged in the | Internet technologies. It is the principal body engaged in the | |||
development of new Internet standard specifications. The IETF is | development of new Internet standard specifications. The IETF is | |||
unusual in that it exists as a collection of meetings (both in-person | unusual in that it exists as a collection of meetings (both in-person | |||
and virtual) and online activities (such as email and pull request | and virtual) and online activities (such as email and pull request | |||
discussions), in which individuals voluntarily participate. | discussions), in which individuals voluntarily participate. | |||
The IETF welcomes all interested individuals: IETF participants come | The IETF welcomes all interested individuals: IETF participants come | |||
skipping to change at line 445 ¶ | skipping to change at line 445 ¶ | |||
One more thing that is important for newcomers: the IETF in no way | One more thing that is important for newcomers: the IETF in no way | |||
"runs the Internet," despite what some people mistakenly might say. | "runs the Internet," despite what some people mistakenly might say. | |||
The IETF makes voluntary standards that are often adopted by Internet | The IETF makes voluntary standards that are often adopted by Internet | |||
users, network operators, and equipment vendors, and it thus helps | users, network operators, and equipment vendors, and it thus helps | |||
shape the trajectory of the development of the Internet. But in no | shape the trajectory of the development of the Internet. But in no | |||
way does the IETF control, or even patrol, the Internet. If your | way does the IETF control, or even patrol, the Internet. If your | |||
interest in the IETF is because you want to be part of the overseers, | interest in the IETF is because you want to be part of the overseers, | |||
you may be badly disappointed by the IETF. A saying you will | you may be badly disappointed by the IETF. A saying you will | |||
sometimes hear is, "we are not the protocol police." | sometimes hear is, "we are not the protocol police." | |||
2.1 Humble Beginnings | 2.1. Humble Beginnings | |||
The first IETF meeting was held in January 1986 at Linkabit in San | The first IETF meeting was held in January 1986 at Linkabit in San | |||
Diego, with 21 attendees. The 4th IETF, held at SRI in Menlo Park in | Diego, with 21 attendees. The 4th IETF, held at SRI in Menlo Park in | |||
October 1986, was the first that equipment vendors attended. The | October 1986, was the first that equipment vendors attended. The | |||
concept of Working Groups was introduced at the 5th IETF meeting at | concept of Working Groups was introduced at the 5th IETF meeting at | |||
the NASA Ames Research Center in California in February 1987. The | the NASA Ames Research Center in California in February 1987. The | |||
7th IETF, held at MITRE in McLean, Virginia, in July 1987, was the | 7th IETF, held at MITRE in McLean, Virginia, in July 1987, was the | |||
first meeting with more than 100 attendees. | first meeting with more than 100 attendees. | |||
After the Internet Society (https://www.internetsociety.org) (ISOC) | After the Internet Society (https://www.internetsociety.org) (ISOC) | |||
skipping to change at line 486 ¶ | skipping to change at line 486 ¶ | |||
policy can be found in RFC 8718: IETF Plenary Meeting Venue Selection | policy can be found in RFC 8718: IETF Plenary Meeting Venue Selection | |||
Process (https://www.rfc-editor.org/info/rfc8718) and RFC 8719: High- | Process (https://www.rfc-editor.org/info/rfc8718) and RFC 8719: High- | |||
Level Guidance for the Meeting Policy of the IETF (https://www.rfc- | Level Guidance for the Meeting Policy of the IETF (https://www.rfc- | |||
editor.org/info/rfc8719). | editor.org/info/rfc8719). | |||
Remote participation in IETF meetings has been growing significantly | Remote participation in IETF meetings has been growing significantly | |||
in the past few years, thanks in part to the ongoing effort to | in the past few years, thanks in part to the ongoing effort to | |||
improve the tools and processes used to facilitate this mode of | improve the tools and processes used to facilitate this mode of | |||
participation. | participation. | |||
2.2 The Hierarchy | 2.2. The Hierarchy | |||
2.2.1 The Internet Society (ISOC) and the IETF Administration LLC (IETF | 2.2.1. The Internet Society (ISOC) and the IETF Administration LLC | |||
LLC) | (IETF LLC) | |||
The Internet Society (ISOC) is an international, non-profit, | The Internet Society (ISOC) is an international, non-profit, | |||
membership organization that supports and promotes the development of | membership organization that supports and promotes the development of | |||
the Internet as a global technical infrastructure. The mission of | the Internet as a global technical infrastructure. The mission of | |||
ISOC is "to promote the open development, evolution, and use of the | ISOC is "to promote the open development, evolution, and use of the | |||
Internet for the benefit of all people throughout the world." One of | Internet for the benefit of all people throughout the world." One of | |||
the ways that ISOC does this is through financial support of the | the ways that ISOC does this is through financial support of the | |||
IETF. | IETF. | |||
The IETF Administration LLC (https://www.ietf.org/about/ | The IETF Administration LLC (https://www.ietf.org/about/ | |||
skipping to change at line 527 ¶ | skipping to change at line 527 ¶ | |||
* Raising money on behalf of the IETF. | * Raising money on behalf of the IETF. | |||
* Establishing and enforcing policies to ensure compliance with | * Establishing and enforcing policies to ensure compliance with | |||
applicable laws, regulations, and rules. | applicable laws, regulations, and rules. | |||
The IETF and ISOC continue to be strongly aligned on key principles. | The IETF and ISOC continue to be strongly aligned on key principles. | |||
ISOC initiatives related to the IETF continue to support | ISOC initiatives related to the IETF continue to support | |||
participation in, and deployment of, the standards created by the | participation in, and deployment of, the standards created by the | |||
IETF. | IETF. | |||
2.2.2 Internet Engineering Steering Group (IESG) | 2.2.2. Internet Engineering Steering Group (IESG) | |||
The IESG is responsible for technical management of IETF activities | The IESG is responsible for technical management of IETF activities | |||
and the Internet standards process. However, the IESG doesn't | and the Internet standards process. However, the IESG doesn't | |||
exercise much direct leadership, such as the kind you will find in | exercise much direct leadership, such as the kind you will find in | |||
many other standards organizations. As its name suggests, its role | many other standards organizations. As its name suggests, its role | |||
is to set directions rather than to give orders. The IESG gets WGs | is to set directions rather than to give orders. The IESG gets WGs | |||
started and finished, ratifies or steers the output from the IETF's | started and finished, ratifies or steers the output from the IETF's | |||
Working Groups (WGs), and makes sure that non-WG I-Ds that are about | Working Groups (WGs), and makes sure that non-WG I-Ds that are about | |||
to become RFCs are correct. | to become RFCs are correct. | |||
skipping to change at line 618 ¶ | skipping to change at line 618 ¶ | |||
the WGs to help prevent IETF protocols that are at odds with each | the WGs to help prevent IETF protocols that are at odds with each | |||
other. This is why ADs are supposed to review the I-Ds coming out of | other. This is why ADs are supposed to review the I-Ds coming out of | |||
Areas other than their own, and each Area has a _directorate_, a set | Areas other than their own, and each Area has a _directorate_, a set | |||
of experienced volunteers who review I-Ds with a focus on potential | of experienced volunteers who review I-Ds with a focus on potential | |||
issues for their area. | issues for their area. | |||
The quality of the IETF standards comes both from the review they get | The quality of the IETF standards comes both from the review they get | |||
in the Working Groups and the scrutiny that the WG review gets from | in the Working Groups and the scrutiny that the WG review gets from | |||
the ADs. | the ADs. | |||
2.2.3 Internet Architecture Board (IAB) | 2.2.3. Internet Architecture Board (IAB) | |||
The IAB (https://www.iab.org) is responsible for keeping an eye on | The IAB (https://www.iab.org) is responsible for keeping an eye on | |||
the "big picture" of the Internet, and it focuses on long-range | the "big picture" of the Internet, and it focuses on long-range | |||
planning and coordination among the various areas of IETF activity. | planning and coordination among the various areas of IETF activity. | |||
The IAB stays informed about important long-term issues in the | The IAB stays informed about important long-term issues in the | |||
Internet, and it brings these topics to the attention of people it | Internet, and it brings these topics to the attention of people it | |||
thinks should know about them. | thinks should know about them. | |||
IAB members pay special attention to emerging activities in the IETF. | IAB members pay special attention to emerging activities in the IETF. | |||
When a new IETF Working Group is proposed, the IAB reviews its | When a new IETF Working Group is proposed, the IAB reviews its | |||
skipping to change at line 655 ¶ | skipping to change at line 655 ¶ | |||
* Oversees the RFC series policy and procedures | * Oversees the RFC series policy and procedures | |||
* Acts as an advisory body to ISOC | * Acts as an advisory body to ISOC | |||
* Oversees IETF liaisons with other standards bodies | * Oversees IETF liaisons with other standards bodies | |||
Like the IESG, the IAB members are selected for two-year positions by | Like the IESG, the IAB members are selected for two-year positions by | |||
the NomCom and are approved by the ISOC Board of Trustees. | the NomCom and are approved by the ISOC Board of Trustees. | |||
2.2.4 Internet Assigned Numbers Authority (IANA) | 2.2.4. Internet Assigned Numbers Authority (IANA) | |||
The core registrar for the IETF's activities is the IANA | The core registrar for the IETF's activities is the IANA | |||
(https://www.iana.org). Many Internet protocols require that someone | (https://www.iana.org). Many Internet protocols require that someone | |||
keep track of protocol items that were added after the protocol came | keep track of protocol items that were added after the protocol came | |||
out. Typical examples of the kinds of registries needed are for TCP | out. Typical examples of the kinds of registries needed are for TCP | |||
port numbers and MIME types. IANA's work on behalf of the IETF is | port numbers and MIME types. IANA's work on behalf of the IETF is | |||
overseen by the IAB. There is a joint group | overseen by the IAB. There is a joint group | |||
(https://datatracker.ietf.org/group/ietfiana/about/) that advises | (https://datatracker.ietf.org/group/ietfiana/about/) that advises | |||
IANA. IANA is funded by ICANN (https://www.icann.org). | IANA. IANA is funded by ICANN (https://www.icann.org). | |||
Even though being a registry may not sound interesting, many IETF | Even though being a registry may not sound interesting, many IETF | |||
participants will testify to how important IANA has been for the | participants will testify to how important IANA has been for the | |||
Internet. Having a stable, long-term repository run by careful and | Internet. Having a stable, long-term repository run by careful and | |||
conservative operators makes it much easier for people to experiment | conservative operators makes it much easier for people to experiment | |||
without worrying about messing things up. | without worrying about messing things up. | |||
2.2.5 RFC Editor and RFC Production Center (RPC) | 2.2.5. RFC Editor and RFC Production Center (RPC) | |||
The RPC edits, formats, and publishes RFC's. This used to be done by | The RPC edits, formats, and publishes RFC's. This used to be done by | |||
one person, which is why you will still see the term _RFC Editor_; | one person, which is why you will still see the term _RFC Editor_; | |||
IETFers are fond of their history. Also, if you are a document | IETFers are fond of their history. Also, if you are a document | |||
author, you will most commonly come in contact with people | author, you will most commonly come in contact with people | |||
responsible for editing your draft. Another important role is to | responsible for editing your draft. Another important role is to | |||
provide one definitive repository (https://www.rfc-editor.org) for | provide one definitive repository (https://www.rfc-editor.org) for | |||
all RFCs. | all RFCs. | |||
A common misconception is that all RFCs are the work of the IETF. In | A common misconception is that all RFCs are the work of the IETF. In | |||
skipping to change at line 707 ¶ | skipping to change at line 707 ¶ | |||
At the time of this writing, the model for the RFC Editor and the RPC | At the time of this writing, the model for the RFC Editor and the RPC | |||
is being revised under an IAB Program | is being revised under an IAB Program | |||
(https://datatracker.ietf.org/group/rfcefdp/about/). In this | (https://datatracker.ietf.org/group/rfcefdp/about/). In this | |||
revision, there is a position hired by the IETF LLC known as the RFC | revision, there is a position hired by the IETF LLC known as the RFC | |||
Series Editor, who is advised by a couple of groups. As a newcomer, | Series Editor, who is advised by a couple of groups. As a newcomer, | |||
and potential author, the details shouldn't matter much to you right | and potential author, the details shouldn't matter much to you right | |||
now. | now. | |||
The RPC is contracted by the IETF LLC. | The RPC is contracted by the IETF LLC. | |||
2.2.6 IETF Secretariat | 2.2.6. IETF Secretariat | |||
There are a few people who are paid to support the IETF. The IETF | There are a few people who are paid to support the IETF. The IETF | |||
Secretariat provides day-to-day logistical support, which mainly | Secretariat provides day-to-day logistical support, which mainly | |||
means coordinating face-to-face meetings and running the IETF | means coordinating face-to-face meetings and running the IETF | |||
presence on the web, including the IETF web site | presence on the web, including the IETF web site | |||
(https://www.ietf.org), mailing lists, the repository for Internet- | (https://www.ietf.org), mailing lists, the repository for Internet- | |||
Drafts, and so on. The Secretariat also provides administrative | Drafts, and so on. The Secretariat also provides administrative | |||
assistance to the IESG and others. | assistance to the IESG and others. | |||
The Secretariat is contracted by the IETF LLC. | The Secretariat is contracted by the IETF LLC. | |||
2.2.7 IETF Trust | 2.2.7. IETF Trust | |||
The IETF Trust (https://trustee.ietf.org) was set up to hold and | The IETF Trust (https://trustee.ietf.org) was set up to hold and | |||
license the intellectual property of the IETF, such as trademarks | license the intellectual property of the IETF, such as trademarks | |||
(the IETF logo, etc.) and copyrights. The trust is a stable, | (the IETF logo, etc.) and copyrights. The trust is a stable, | |||
legally-identifiable entity. Most participants never interact with | legally-identifiable entity. Most participants never interact with | |||
the IETF Trust, beyond seeing it mentioned in RFC boilerplate. This | the IETF Trust, beyond seeing it mentioned in RFC boilerplate. This | |||
is a good sign, and indicates that they are quietly doing their job. | is a good sign, and indicates that they are quietly doing their job. | |||
2.3 IETF Mailing Lists | 2.3. IETF Mailing Lists | |||
The IETF does most of its communication, and all of its official | The IETF does most of its communication, and all of its official | |||
work, via email. | work, via email. | |||
Anyone who plans to participate in the IETF should join the IETF | Anyone who plans to participate in the IETF should join the IETF | |||
announcement mailing list (https://www.ietf.org/mailman/listinfo/ | announcement mailing list (https://www.ietf.org/mailman/listinfo/ | |||
ietf-announce). This is where all of the meeting information, RFC | ietf-announce). This is where all of the meeting information, RFC | |||
announcements, and IESG Protocol Actions and Last Calls are posted. | announcements, and IESG Protocol Actions and Last Calls are posted. | |||
This list is strongly moderated, and only the Secretariat and a small | This list is strongly moderated, and only the Secretariat and a small | |||
number of IETF leaders can approve messages sent to the announcement | number of IETF leaders can approve messages sent to the announcement | |||
skipping to change at line 775 ¶ | skipping to change at line 775 ¶ | |||
Every IETF mailing list is archived. (Unfortunately, the archives | Every IETF mailing list is archived. (Unfortunately, the archives | |||
for some lists from many years ago, when the IETF did not have its | for some lists from many years ago, when the IETF did not have its | |||
own servers, have been lost.) | own servers, have been lost.) | |||
Even though the IETF mailing lists "represent" the IETF participants | Even though the IETF mailing lists "represent" the IETF participants | |||
at large, it is important to note that attending an IETF meeting does | at large, it is important to note that attending an IETF meeting does | |||
not mean you'll be automatically added to any list; you'll have to | not mean you'll be automatically added to any list; you'll have to | |||
"opt in" directly. | "opt in" directly. | |||
3 IETF Meetings | 3. IETF Meetings | |||
The computer industry is rife with conferences, seminars, | The computer industry is rife with conferences, seminars, | |||
expositions, and all manner of other kinds of meetings. IETF face- | expositions, and all manner of other kinds of meetings. IETF face- | |||
to-face meetings are not like these. The meetings, held three times | to-face meetings are not like these. The meetings, held three times | |||
a year, are week-long gatherings with the primary goals of helping | a year, are week-long gatherings with the primary goals of helping | |||
Working Groups get their tasks done, and promoting a fair amount of | Working Groups get their tasks done, and promoting a fair amount of | |||
mixing among the WGs and the Areas. IETF meetings are of little | mixing among the WGs and the Areas. IETF meetings are of little | |||
interest to sales and marketing folks, but of high interest to | interest to sales and marketing folks, but of high interest to | |||
engineers and developers. | engineers and developers. | |||
skipping to change at line 831 ¶ | skipping to change at line 831 ¶ | |||
There have been more than 110 IETF meetings so far. The list of | There have been more than 110 IETF meetings so far. The list of | |||
future meetings is available online | future meetings is available online | |||
(https://www.ietf.org/how/meetings/upcoming/), and they are also | (https://www.ietf.org/how/meetings/upcoming/), and they are also | |||
announced on the _ietf-announce_ mailing list mentioned above. | announced on the _ietf-announce_ mailing list mentioned above. | |||
Note that COVID-19 disrupted the in-person meetings. After several | Note that COVID-19 disrupted the in-person meetings. After several | |||
virtual or online meetings, the IETF tried its first hybrid meeting, | virtual or online meetings, the IETF tried its first hybrid meeting, | |||
in Vienna, in March 2022. | in Vienna, in March 2022. | |||
3.1 Registration | 3.1. Registration | |||
To attend an IETF meeting, either online or in person, you have to | To attend an IETF meeting, either online or in person, you have to | |||
register and pay a registration fee. If you cannot afford the online | register and pay a registration fee. If you cannot afford the online | |||
registration fee, you can apply for a fee waiver during the | registration fee, you can apply for a fee waiver during the | |||
registration process. The meeting site (if the meeting is not purely | registration process. The meeting site (if the meeting is not purely | |||
online) is generally announced at several months ahead of the meeting | online) is generally announced at several months ahead of the meeting | |||
-- earlier if possible. An announcement goes out via email to the | -- earlier if possible. An announcement goes out via email to the | |||
_ietf-announce_ mailing list, and information is posted on the IETF | _ietf-announce_ mailing list, and information is posted on the IETF | |||
web site (https://www.ietf.org), that same day. Upcoming meeting | web site (https://www.ietf.org), that same day. Upcoming meeting | |||
locations are also mentioned at the plenary, and the host for the | locations are also mentioned at the plenary, and the host for the | |||
skipping to change at line 896 ¶ | skipping to change at line 896 ¶ | |||
You can also turn in lost-and-found items to the registration desk. | You can also turn in lost-and-found items to the registration desk. | |||
At the end of the meeting, anything left over from the lost-and-found | At the end of the meeting, anything left over from the lost-and-found | |||
will usually be turned over to the hotel or brought back to the | will usually be turned over to the hotel or brought back to the | |||
Secretariat's office. Incidentally, the IETF registration desk is | Secretariat's office. Incidentally, the IETF registration desk is | |||
often a convenient place to arrange to meet people. If someone says | often a convenient place to arrange to meet people. If someone says | |||
"meet me at registration," you should clarify if they mean the IETF | "meet me at registration," you should clarify if they mean the IETF | |||
registration desk, or the hotel registration desk: This has been a | registration desk, or the hotel registration desk: This has been a | |||
common cause of missed connections. | common cause of missed connections. | |||
3.2 Take the Plunge and Stay All Week! | 3.2. Take the Plunge and Stay All Week! | |||
IETF WG meetings are scheduled from Monday morning through Friday | IETF WG meetings are scheduled from Monday morning through Friday | |||
afternoon. Associated non-WG meetings often take place on the | afternoon. Associated non-WG meetings often take place on the | |||
preceding or following weekends, and unofficial "side meetings" can | preceding or following weekends, and unofficial "side meetings" can | |||
also be scheduled during the week. It is best to plan to be present | also be scheduled during the week. It is best to plan to be present | |||
the whole week, to benefit from cross-fertilization between WGs and | the whole week, to benefit from cross-fertilization between WGs and | |||
from hallway discussions (both offline as well as in online | from hallway discussions (both offline as well as in online | |||
environments such as the _gather.town_ website). As noted below, the | environments such as the _gather.town_ website). As noted below, the | |||
agenda is fluid, and there have been instances of participants | agenda is fluid, and there have been instances of participants | |||
missing important sessions due to last-minute scheduling changes | missing important sessions due to last-minute scheduling changes | |||
skipping to change at line 926 ¶ | skipping to change at line 926 ¶ | |||
charge to use the "IETF wifi." This usually covers many places of | charge to use the "IETF wifi." This usually covers many places of | |||
the meeting venue (restaurants, coffee shops, and so on), so catching | the meeting venue (restaurants, coffee shops, and so on), so catching | |||
up on email when not in meetings is a fairly common task for IETFers. | up on email when not in meetings is a fairly common task for IETFers. | |||
Note that many people use their laptops actively during meeting | Note that many people use their laptops actively during meeting | |||
sessions for practical purposes such as consulting drafts. Power | sessions for practical purposes such as consulting drafts. Power | |||
strips in all meeting rooms and hotel rooms will provide only the | strips in all meeting rooms and hotel rooms will provide only the | |||
sockets permitted by local regulations, so ensure in advance that you | sockets permitted by local regulations, so ensure in advance that you | |||
have an appropriate travel adapter. | have an appropriate travel adapter. | |||
3.3 Newcomer Training | 3.3. Newcomer Training | |||
Newcomers should attend the Newcomer's Tutorial on Sunday, which is | Newcomers should attend the Newcomer's Tutorial on Sunday, which is | |||
especially designed for them. The tutorial is organized and | especially designed for them. The tutorial is organized and | |||
conducted by the IETF Education, Mentoring, and Outreach Directorate | conducted by the IETF Education, Mentoring, and Outreach Directorate | |||
(_EMODIR_) team and is intended to provide useful introductory | (_EMODIR_) team and is intended to provide useful introductory | |||
information. The session covers the structure of the IETF, how to | information. The session covers the structure of the IETF, how to | |||
get the most out of the meeting, and many other essential and | get the most out of the meeting, and many other essential and | |||
enlightening topics for new IETFers. The IETF has a YouTube channel | enlightening topics for new IETFers. The IETF has a YouTube channel | |||
(https://www.youtube.com/user/ietf) which has the previous tutorials. | (https://www.youtube.com/user/ietf) which has the previous tutorials. | |||
This has recently been broken down into four 15-minute segments | This has recently been broken down into four 15-minute segments | |||
(https://www.youtube.com/watch?v=MW1cDLmr91c&list=PLC86T- | (https://www.youtube.com/watch?v=MW1cDLmr91c&list=PLC86T- | |||
6ZTP5imxIwnF0mYxWVp0sbqDR0J&pp=iAQB) which might be easier to view. | 6ZTP5imxIwnF0mYxWVp0sbqDR0J&pp=iAQB) which might be easier to view. | |||
_Quick Connections_ is a session limited to newcomers and experienced | _Quick Connections_ is a session limited to newcomers and experienced | |||
IETF participants. It is a great chance to meet people, and | IETF participants. It is a great chance to meet people, and | |||
establish contacts that can be useful during the rest of the week. | establish contacts that can be useful during the rest of the week. | |||
Registration is required as space is limited. It is held right | Registration is required as space is limited. It is held right | |||
before the welcome reception. | before the welcome reception. | |||
3.4 Dress Code | 3.4. Dress Code | |||
At meetings people generally dress informally, and newcomers could | At meetings people generally dress informally, and newcomers could | |||
feel out of place if they show up Monday morning in suits. The | feel out of place if they show up Monday morning in suits. The | |||
general rule is "dress for casual comfort." Note that the hotel air | general rule is "dress for casual comfort." Note that the hotel air | |||
conditioning might mean bringing a sweater or other covering as well. | conditioning might mean bringing a sweater or other covering as well. | |||
3.5 Working Group Meetings | 3.5. Working Group Meetings | |||
The heart of an IETF meeting is the WG meetings themselves. | The heart of an IETF meeting is the WG meetings themselves. | |||
Different WGs chairs have very different styles, so it is impossible | Different WGs chairs have very different styles, so it is impossible | |||
to generalize how a WG meeting will feel. All WGs have agendas, | to generalize how a WG meeting will feel. All WGs have agendas, | |||
however, and most will follow the following approach. | however, and most will follow the following approach. | |||
At the beginning of the meeting, the chair will pass around the _blue | At the beginning of the meeting, the chair will pass around the _blue | |||
sheets_, which are paper forms on which everyone writes their name | sheets_, which are paper forms on which everyone writes their name | |||
and their affiliation. These are archived and used for planning | and their affiliation. These are archived and used for planning | |||
capacity needs for the next time the WG meets. In very rare cases, | capacity needs for the next time the WG meets. In very rare cases, | |||
skipping to change at line 994 ¶ | skipping to change at line 994 ¶ | |||
at the mic, but do not hesitate to be the first person at the line if | at the mic, but do not hesitate to be the first person at the line if | |||
you have a question or a contribution to the discussion. The WG | you have a question or a contribution to the discussion. The WG | |||
chair or presenter will indicate when you can speak. Although it | chair or presenter will indicate when you can speak. Although it | |||
would be easier to just raise your hand from where you are sitting, | would be easier to just raise your hand from where you are sitting, | |||
the mics perform a very useful task: they let the people listening | the mics perform a very useful task: they let the people listening | |||
remotely and in the room hear your question or comment. When you | remotely and in the room hear your question or comment. When you | |||
first speak, say your name and affiliation for identification | first speak, say your name and affiliation for identification | |||
purposes. If you miss this, folks will often say "name!" to remind | purposes. If you miss this, folks will often say "name!" to remind | |||
you. Don't be embarrassed if this happens, it's not uncommon. | you. Don't be embarrassed if this happens, it's not uncommon. | |||
3.6 Seeing Spots Before Your Eyes | 3.6. Seeing Spots Before Your Eyes | |||
Some attendees will have a little colored dot on their name tag, and | Some attendees will have a little colored dot on their name tag, and | |||
a few people have more than one. These dots identify people who have | a few people have more than one. These dots identify people who have | |||
volunteered to do extra work, such as being a WG chair, an IESG | volunteered to do extra work, such as being a WG chair, an IESG | |||
member, and so on. The colors have the meanings shown here. | member, and so on. The colors have the meanings shown here. | |||
+========+=============================+ | +========+=============================+ | |||
| Color | Meaning | | | Color | Meaning | | |||
+========+=============================+ | +========+=============================+ | |||
| Blue | Working Group/BOF Chair | | | Blue | Working Group/BOF Chair | | |||
skipping to change at line 1040 ¶ | skipping to change at line 1040 ¶ | |||
send email after the meeting ends. Also, when you start a hallway | send email after the meeting ends. Also, when you start a hallway | |||
conversation with an Area Director (or even a WG chair, for that | conversation with an Area Director (or even a WG chair, for that | |||
matter), it is often good to give them about 30 seconds of context | matter), it is often good to give them about 30 seconds of context | |||
for the discussion. | for the discussion. | |||
Near the registration area there are usually ribbons and markers so | Near the registration area there are usually ribbons and markers so | |||
that people can label their specific interests, history, and so on. | that people can label their specific interests, history, and so on. | |||
Many people use them to make (inside) jokes, which are sometimes | Many people use them to make (inside) jokes, which are sometimes | |||
amusing. | amusing. | |||
3.7 Terminal Room | 3.7. Terminal Room | |||
The IETF wifi is provided by volunteers who run the Network | The IETF wifi is provided by volunteers who run the Network | |||
Operations Center (NOC). The terminal room is where you can get | Operations Center (NOC). The terminal room is where you can get | |||
wired connectivity and limited access to a printer. The people and | wired connectivity and limited access to a printer. The people and | |||
companies that donate their equipment, services, and time are to be | companies that donate their equipment, services, and time are to be | |||
heartily congratulated and thanked. | heartily congratulated and thanked. | |||
You must be wearing your badge in order to get into the terminal | You must be wearing your badge in order to get into the terminal | |||
room. The terminal room provides power strips, Ethernet ports, and | room. The terminal room provides power strips, Ethernet ports, and | |||
wifi (for the people who don't need Ethernet but want power). What | wifi (for the people who don't need Ethernet but want power). What | |||
it doesn't provide are terminals; the name is historical. The help | it doesn't provide are terminals; the name is historical. The help | |||
desk in the terminal room is also a good place to ask questions about | desk in the terminal room is also a good place to ask questions about | |||
network failures, although they might point you off to different | network failures, although they might point you off to different | |||
networking staff. | networking staff. | |||
3.8 Meals and Snacks | 3.8. Meals and Snacks | |||
Although it is true that some people eat very well at the IETF, they | Although it is true that some people eat very well at the IETF, they | |||
find the food on their own since lunches and dinners are not included | find the food on their own since lunches and dinners are not included | |||
in the registration fee. In addition to socializing, dinner meetings | in the registration fee. In addition to socializing, dinner meetings | |||
can be a good way to get additional work done. | can be a good way to get additional work done. | |||
If sponsorship for it is secured, the welcome reception provides | If sponsorship for it is secured, the welcome reception provides | |||
drinks and appetizers but is not meant to be a full replacement for | drinks and appetizers but is not meant to be a full replacement for | |||
dinner. Sometimes a continental breakfast can be included with the | dinner. Sometimes a continental breakfast can be included with the | |||
hotel registration. There IETF meeting also includes a morning | hotel registration. There IETF meeting also includes a morning | |||
coffee and snack break, and a similar one in the afternoon. | coffee and snack break, and a similar one in the afternoon. | |||
If you prefer to get out of the hotel for meals, the local host | If you prefer to get out of the hotel for meals, the local host | |||
usually provides a list of places to eat within easy reach of the | usually provides a list of places to eat within easy reach of the | |||
meeting site, and the meeting-specific email list is also a useful | meeting site, and the meeting-specific email list is also a useful | |||
source. | source. | |||
3.9 Social Event | 3.9. Social Event | |||
Another of the most important things organized and managed by the | Another of the most important things organized and managed by the | |||
host is the IETF social event. The social event is sometimes high- | host is the IETF social event. The social event is sometimes high- | |||
tech-related event, or it might be in an art museum or a reception | tech-related event, or it might be in an art museum or a reception | |||
hall. Note, however, that not all IETF meetings have social events. | hall. Note, however, that not all IETF meetings have social events. | |||
Newcomers to the IETF are encouraged to attend the social event. | Newcomers to the IETF are encouraged to attend the social event. | |||
Wear your name tag and leave your laptop behind. The social event is | Wear your name tag and leave your laptop behind. The social event is | |||
designed to give people a chance to meet on a social, rather than | designed to give people a chance to meet on a social, rather than | |||
technical, level. The social ticket costs extra, is reserved at | technical, level. The social ticket costs extra, is reserved at | |||
registration time, and has limited capacity. People looking to buy | registration time, and has limited capacity. People looking to buy | |||
or sell a social ticket often post to the email list, or on the | or sell a social ticket often post to the email list, or on the | |||
corkboards mentioned above. | corkboards mentioned above. | |||
3.10 Agenda | 3.10. Agenda | |||
The agenda for the IETF meetings is a very fluid thing. It is | The agenda for the IETF meetings is a very fluid thing. It is | |||
available on the web and through the IETF mobile apps starting a few | available on the web and through the IETF mobile apps starting a few | |||
weeks before the meeting. Of course, "final" in the IETF doesn't | weeks before the meeting. Of course, "final" in the IETF doesn't | |||
mean the same thing as it does elsewhere in the world. The final | mean the same thing as it does elsewhere in the world. The final | |||
agenda is simply the last version posted before the meeting. The | agenda is simply the last version posted before the meeting. The | |||
Secretariat will post agenda changes on the bulletin board near the | Secretariat will post agenda changes on the bulletin board near the | |||
IETF registration desk (reminder, not the hotel registration desk!). | IETF registration desk (reminder, not the hotel registration desk!). | |||
These late changes are not capricious: they are made "just in time" | These late changes are not capricious: they are made "just in time" | |||
as session chairs and speakers become aware of unanticipated | as session chairs and speakers become aware of unanticipated | |||
conflicts. The IETF is too dynamic for agendas to be tied down weeks | conflicts. The IETF is too dynamic for agendas to be tied down weeks | |||
in advance. | in advance. | |||
A map showing the hotel layout and, specifically the meeting rooms, | A map showing the hotel layout and, specifically the meeting rooms, | |||
is also available with the agenda. Room assignments can change as | is also available with the agenda. Room assignments can change as | |||
the agenda changes. Some Working Groups meet multiple times during a | the agenda changes. Some Working Groups meet multiple times during a | |||
meeting, and every attempt is made to have a Working Group meet in | meeting, and every attempt is made to have a Working Group meet in | |||
the same room for each session. | the same room for each session. | |||
3.11 EMODIR to the Rescue | 3.11. EMODIR to the Rescue | |||
If, after you finish reading this document, certain aspects of the | If, after you finish reading this document, certain aspects of the | |||
IETF still mystify you, you'll want to drop in on the on-site | IETF still mystify you, you'll want to drop in on the on-site | |||
training offered by the Education, Mentoring, and Outreach (EMODIR) | training offered by the Education, Mentoring, and Outreach (EMODIR) | |||
team. In addition to the Newcomer training mentioned above, EMODIR | team. In addition to the Newcomer training mentioned above, EMODIR | |||
also hosts informal newcomer gatherings during the coffee break | also hosts informal newcomer gatherings during the coffee break | |||
sessions. Details vary for each meeting, so watch the agenda and the | sessions. Details vary for each meeting, so watch the agenda and the | |||
newcomer-specific email list. | newcomer-specific email list. | |||
EMODIR also organized in-depth technical tutorials, useful for | EMODIR also organized in-depth technical tutorials, useful for | |||
skipping to change at line 1135 ¶ | skipping to change at line 1135 ¶ | |||
effective quickly. This has not worked out very well during the all- | effective quickly. This has not worked out very well during the all- | |||
virtual meetings, frankly. If you are interested, watch for the | virtual meetings, frankly. If you are interested, watch for the | |||
announcement. Ideally you have a call with your mentor before the | announcement. Ideally you have a call with your mentor before the | |||
meeting, a meeting during the beginning of the meeting, and check in | meeting, a meeting during the beginning of the meeting, and check in | |||
some time during the meeting, so they can help you with any questions | some time during the meeting, so they can help you with any questions | |||
you might have. | you might have. | |||
Details on EMODIR membership and charter are available online | Details on EMODIR membership and charter are available online | |||
(https://datatracker.ietf.org/group/emodir/about/). | (https://datatracker.ietf.org/group/emodir/about/). | |||
3.12 Where Do I Fit In? | 3.12. Where Do I Fit In? | |||
The IETF is different things to different people. There are many | The IETF is different things to different people. There are many | |||
people who have been very active in the IETF who have never attended | people who have been very active in the IETF who have never attended | |||
an IETF meeting, and you should not feel obligated to come to an IETF | an IETF meeting, and you should not feel obligated to come to an IETF | |||
meeting just to get a feel for the IETF. If, however, you decide to | meeting just to get a feel for the IETF. If, however, you decide to | |||
come, this document and RFC 4144: How to Gain Prominence and | come, this document and RFC 4144: How to Gain Prominence and | |||
Influence in Standards Organizations (https://www.rfc- | Influence in Standards Organizations (https://www.rfc- | |||
editor.org/info/rfc4144) provides some pointers on how to make your | editor.org/info/rfc4144) provides some pointers on how to make your | |||
meeting a success. The following guidelines (based on stereotypes of | meeting a success. The following guidelines (based on stereotypes of | |||
people in various industries) might help you decide whether you | people in various industries) might help you decide whether you | |||
actually want to come and, if so, what might be the best use of your | actually want to come and, if so, what might be the best use of your | |||
time at your first meeting. | time at your first meeting. | |||
3.12.1 IT Managers | 3.12.1. IT Managers | |||
As discussed throughout this document, an IETF meeting is nothing | As discussed throughout this document, an IETF meeting is nothing | |||
like any trade show you have attended. IETF meetings are singularly | like any trade show you have attended. IETF meetings are singularly | |||
bad places to go if your intention is to find out what will be hot in | bad places to go if your intention is to find out what will be hot in | |||
the Internet industry next year. You can safely assume that going to | the Internet industry next year. You can safely assume that going to | |||
Working Group meetings will confuse you more than it will help you | Working Group meetings will confuse you more than it will help you | |||
understand what is happening, or will be happening, in the industry. | understand what is happening, or will be happening, in the industry. | |||
This is not to say that no one from the industry should go to IETF | This is not to say that no one from the industry should go to IETF | |||
meetings. As an IT manager, you might want to consider sending | meetings. As an IT manager, you might want to consider sending | |||
specific people who are responsible for technologies that are under | specific people who are responsible for technologies that are under | |||
development in the IETF. As these people read the current Internet- | development in the IETF. As these people read the current Internet- | |||
Drafts and email traffic on the relevant Working Group lists, they | Drafts and email traffic on the relevant Working Group lists, they | |||
will get a sense of whether or not their presence would be worthwhile | will get a sense of whether or not their presence would be worthwhile | |||
for your company or for the Working Groups. | for your company or for the Working Groups. | |||
3.12.2 Network Operators and ISPs | 3.12.2. Network Operators and ISPs | |||
Knowledge of how networks are run is indispensable for the | Knowledge of how networks are run is indispensable for the | |||
development of new (versions of) protocols. Especially if you work | development of new (versions of) protocols. Especially if you work | |||
for the type of network that is always using the very latest hardware | for the type of network that is always using the very latest hardware | |||
and software, and you are already following the relevant Working | and software, and you are already following the relevant Working | |||
Groups, you could certainly find participating in the IETF valuable. | Groups, you could certainly find participating in the IETF valuable. | |||
Note that the IETF has several WGs focused on operations, that might | Note that the IETF has several WGs focused on operations, that might | |||
be particularly relevant. | be particularly relevant. | |||
Finally, note that the IETF is increasingly focused on encrypting | Finally, note that the IETF is increasingly focused on encrypting | |||
network traffic, and that this has implications for operators. A | network traffic, and that this has implications for operators. A | |||
fair amount of IETF work also covers many other parts of operations | fair amount of IETF work also covers many other parts of operations | |||
of ISPs and large enterprises, and the input of operators from each | of ISPs and large enterprises, and the input of operators from each | |||
of these types of organizations is quite valuable to keep this work | of these types of organizations is quite valuable to keep this work | |||
vibrant and relevant. Many of the best operations documents from the | vibrant and relevant. Many of the best operations documents from the | |||
IETF come from real-world operators, not vendors and academics. | IETF come from real-world operators, not vendors and academics. | |||
3.12.3 Networking Hardware and Software Vendors | 3.12.3. Networking Hardware and Software Vendors | |||
The image of the IETF being mostly network researchers may have been | The image of the IETF being mostly network researchers may have been | |||
true in the distant past, but the jobs of today's attendees are | true in the distant past, but the jobs of today's attendees are | |||
typically in industry. In most areas of the IETF, employees of | typically in industry. In most areas of the IETF, employees of | |||
vendors are the ones writing the protocols and leading the Working | vendors are the ones writing the protocols and leading the Working | |||
Groups, so it's completely appropriate for vendors to attend. If you | Groups, so it's completely appropriate for vendors to attend. If you | |||
create Internet hardware or software, or run a service available on | create Internet hardware or software, or run a service available on | |||
the Internet, and no one from your company has ever attended an IETF | the Internet, and no one from your company has ever attended an IETF | |||
meeting, it behooves you to come to a meeting if for no other reason | meeting, it behooves you to come to a meeting if for no other reason | |||
than to tell the others how relevant the meeting was or was not to | than to tell the others how relevant the meeting was or was not to | |||
skipping to change at line 1212 ¶ | skipping to change at line 1212 ¶ | |||
useful, for everyone from a technical department to go, especially if | useful, for everyone from a technical department to go, especially if | |||
they are not all reading the Internet-Drafts and following the | they are not all reading the Internet-Drafts and following the | |||
Working Group mailing lists. Many companies have just a few | Working Group mailing lists. Many companies have just a few | |||
designated meeting attendees who are chosen for their ability to do | designated meeting attendees who are chosen for their ability to do | |||
complete and useful trip reports. In addition, many companies have | complete and useful trip reports. In addition, many companies have | |||
internal coordination efforts and a standards strategy. If a company | internal coordination efforts and a standards strategy. If a company | |||
depends on the Internet for some or all of its business, the strategy | depends on the Internet for some or all of its business, the strategy | |||
should probably cover the IETF, but note that IETF participation is | should probably cover the IETF, but note that IETF participation is | |||
as an _individual_ not a formal representative of their employer. | as an _individual_ not a formal representative of their employer. | |||
3.12.4 Academics | 3.12.4. Academics | |||
IETF meetings are often excellent places for all kinds of researchers | IETF meetings are often excellent places for all kinds of researchers | |||
to find out what is happening in the way of soon-to-be-deployed | to find out what is happening in the way of soon-to-be-deployed | |||
protocols, and networking architecture and infrastructure. | protocols, and networking architecture and infrastructure. | |||
Professors and grad students (and sometimes overachieving undergrads) | Professors and grad students (and sometimes overachieving undergrads) | |||
who are doing research in networking or communications can get a | who are doing research in networking or communications can get a | |||
wealth of information by following Working Groups in their specific | wealth of information by following Working Groups in their specific | |||
fields of interest. Wandering into different Working Group meetings | fields of interest. Wandering into different Working Group meetings | |||
can have the same effect as going to symposia and seminars in your | can have the same effect as going to symposia and seminars in your | |||
department. Researchers are also, of course, likely to be interested | department. Researchers are also, of course, likely to be interested | |||
in IRTF activities. | in IRTF activities. | |||
In addition, the IRTF and ACM co-host the annual Applied Networking | In addition, the IRTF and ACM co-host the annual Applied Networking | |||
Research Workshop (https://irtf.org/anrw/), normally scheduled during | Research Workshop (https://irtf.org/anrw/), normally scheduled during | |||
the July IETF meeting Registration is required, IETF attendees can | the July IETF meeting Registration is required, IETF attendees can | |||
attend for free. The IRTF also hosts the Applied Networking Research | attend for free. The IRTF also hosts the Applied Networking Research | |||
Prize (https://irtf.org/anrp/), which includes a cash prize, a travel | Prize (https://irtf.org/anrp/), which includes a cash prize, a travel | |||
grant to attend, and a chance to present. See the web page for | grant to attend, and a chance to present. See the web page for | |||
requirements. | requirements. | |||
3.12.5 Computer Trade Press | 3.12.5. Computer Trade Press | |||
If you're a member of the press and are considering attending IETF, | If you're a member of the press and are considering attending IETF, | |||
please see the special section below. | please see the special section below. | |||
3.13 Proceedings | 3.13. Proceedings | |||
IETF proceedings are compiled in the weeks and months after each | IETF proceedings are compiled in the weeks and months after each | |||
meeting and are available online (https://www.ietf.org/how/meetings/ | meeting and are available online (https://www.ietf.org/how/meetings/ | |||
proceedings/). Be sure to look through a copy at least once; the | proceedings/). Be sure to look through a copy at least once; the | |||
proceedings are filled with information about IETF that you're not | proceedings are filled with information about IETF that you're not | |||
likely to find anywhere else. For example, you'll copies of every | likely to find anywhere else. For example, you'll copies of every | |||
session's slides, links to the video recording, copies of the blue | session's slides, links to the video recording, copies of the blue | |||
sheets (attendance), and so on. | sheets (attendance), and so on. | |||
3.14 Other General Things | 3.14. Other General Things | |||
IETFers in general are very approachable. Never be afraid to | IETFers in general are very approachable. Never be afraid to | |||
approach someone and introduce yourself. Also, don't be afraid to | approach someone and introduce yourself. Also, don't be afraid to | |||
ask questions, especially when it comes to jargon and acronyms. If | ask questions, especially when it comes to jargon and acronyms. If | |||
someone is presenting an update to their draft, feel free to step up | someone is presenting an update to their draft, feel free to step up | |||
to the mic and ask a clarifying question. Before you do, however, | to the mic and ask a clarifying question. Before you do, however, | |||
make sure to have read the draft first. Working Group meetings are | make sure to have read the draft first. Working Group meetings are | |||
not a time for general tutorials. | not a time for general tutorials. | |||
Hallway conversations are very important. A lot of very good work | Hallway conversations are very important. A lot of very good work | |||
skipping to change at line 1284 ¶ | skipping to change at line 1284 ¶ | |||
mind that the IETF is not a trade show. | mind that the IETF is not a trade show. | |||
There is always a "materials distribution table" near the | There is always a "materials distribution table" near the | |||
registration desk. This desk is used to make appropriate information | registration desk. This desk is used to make appropriate information | |||
available to the attendees (e.g., copies of something discussed in a | available to the attendees (e.g., copies of something discussed in a | |||
Working Group session, descriptions of online IETF-related | Working Group session, descriptions of online IETF-related | |||
information). Please check with the Secretariat before placing | information). Please check with the Secretariat before placing | |||
materials on the desk; the Secretariat has the right to remove | materials on the desk; the Secretariat has the right to remove | |||
material that they feel is not appropriate. | material that they feel is not appropriate. | |||
3.15 Remote Participation | 3.15. Remote Participation | |||
People have joined IETF meetings remotely for a long time, but the | People have joined IETF meetings remotely for a long time, but the | |||
tools for this have changed a lot over the years. Currently the IETF | tools for this have changed a lot over the years. Currently the IETF | |||
uses a browser- based tool known as _MeetEcho_. There is also a text- | uses a browser- based tool known as _MeetEcho_. There is also a text- | |||
based discussion forum called _Jabber_. This is integrated into | based discussion forum called _Jabber_. This is integrated into | |||
MeetEcho, but there are also stand-alone clients available. Planned | MeetEcho, but there are also stand-alone clients available. Planned | |||
for 2022, the _Zulip_ text will be available. Each WG will have its | for 2022, the _Zulip_ text will be available. Each WG will have its | |||
own stream. | own stream. | |||
The links for the Meetecho rooms, the Jabber chats, and meeting | The links for the Meetecho rooms, the Jabber chats, and meeting | |||
materials, can always be found in the right-hand side of the agenda, | materials, can always be found in the right-hand side of the agenda, | |||
under the different icons. All sessions are recorded and can be | under the different icons. All sessions are recorded and can be | |||
viewed after the meeting, along with chat logs and meeting minutes. | viewed after the meeting, along with chat logs and meeting minutes. | |||
This can be useful to refresh your memory while writing a trip | This can be useful to refresh your memory while writing a trip | |||
report, or for catching up on what happened when you wanted to be in | report, or for catching up on what happened when you wanted to be in | |||
two WG meetings at once. It happens; scheduling conflicts are | two WG meetings at once. It happens; scheduling conflicts are | |||
unavoidable. | unavoidable. | |||
4 Working Groups | 4. Working Groups | |||
The vast majority of the IETF's work is done in its many Working | The vast majority of the IETF's work is done in its many Working | |||
Groups; at the time of this writing, there are well over one hundred | Groups; at the time of this writing, there are well over one hundred | |||
different WGs. BCP 25 (https://www.rfc-editor.org/info/bcp25), "IETF | different WGs. BCP 25 (https://www.rfc-editor.org/info/bcp25), "IETF | |||
Working Group Guidelines and Procedures," is an excellent resource | Working Group Guidelines and Procedures," is an excellent resource | |||
for anyone participating in WG discussions. The full list of working | for anyone participating in WG discussions. The full list of working | |||
groups can be found on the datatracker (https://datatracker.ietf.org/ | groups can be found on the datatracker (https://datatracker.ietf.org/ | |||
wg/). | wg/). | |||
A WG is really just a mailing list with a bit of supervision and | A WG is really just a mailing list with a bit of supervision and | |||
skipping to change at line 1333 ¶ | skipping to change at line 1333 ¶ | |||
wander off on other "interesting" topics. Of course, looking a bit | wander off on other "interesting" topics. Of course, looking a bit | |||
outside the scope of the WG is occasionally useful, but the large | outside the scope of the WG is occasionally useful, but the large | |||
majority of the discussion should be on the topics listed in the | majority of the discussion should be on the topics listed in the | |||
charter. In fact, some WG charters actually specify what the WG will | charter. In fact, some WG charters actually specify what the WG will | |||
not do, particularly if there were some attractive but nebulous | not do, particularly if there were some attractive but nebulous | |||
topics brought up during the drafting of the charter. The list of | topics brought up during the drafting of the charter. The list of | |||
all WG charters makes interesting reading for folks who want to know | all WG charters makes interesting reading for folks who want to know | |||
what the different Working Groups are supposed to be doing. Each WG | what the different Working Groups are supposed to be doing. Each WG | |||
has its own page on the datatracker. | has its own page on the datatracker. | |||
4.1 Working Group Chairs | 4.1. Working Group Chairs | |||
Each Working Group has one or two (or, rarely, three) chairs. The | Each Working Group has one or two (or, rarely, three) chairs. The | |||
role of the WG chairs is described in both BCP 11 (https://www.rfc- | role of the WG chairs is described in both BCP 11 (https://www.rfc- | |||
editor.org/info/bcp11) and BCP 25 (https://www.rfc-editor.org/info/ | editor.org/info/bcp11) and BCP 25 (https://www.rfc-editor.org/info/ | |||
bcp25). | bcp25). | |||
Chairs have responsibility for the technical and non-technical | Chairs have responsibility for the technical and non-technical | |||
quality of WG output. The chair must keep the WG productive, and | quality of WG output. The chair must keep the WG productive, and | |||
making progress on its drafts. Sometimes there is a WG Secretary to | making progress on its drafts. Sometimes there is a WG Secretary to | |||
help. Document editors, too, are usually incentivized to make | help. Document editors, too, are usually incentivized to make | |||
skipping to change at line 1355 ¶ | skipping to change at line 1355 ¶ | |||
on the list and by scheduling meetings when appropriate. Sometimes | on the list and by scheduling meetings when appropriate. Sometimes | |||
discussions get stuck on contentious points and the chair may need to | discussions get stuck on contentious points and the chair may need to | |||
steer people toward productive interaction and then declare when | steer people toward productive interaction and then declare when | |||
rough consensus has been met and the discussion is over. Sometimes | rough consensus has been met and the discussion is over. Sometimes | |||
chairs also manage interactions with non-WG participants or the IESG, | chairs also manage interactions with non-WG participants or the IESG, | |||
especially when a WG document approaches publication. As you can | especially when a WG document approaches publication. As you can | |||
imagine given the mix of secretarial, interpersonal, and technical | imagine given the mix of secretarial, interpersonal, and technical | |||
demands, some Working Group chairs are much better at their jobs than | demands, some Working Group chairs are much better at their jobs than | |||
others. | others. | |||
4.2 Getting Things Done in a Working Group | 4.2. Getting Things Done in a Working Group | |||
One fact that confuses many newcomers is that the face-to-face WG | One fact that confuses many newcomers is that the face-to-face WG | |||
meetings are much less important in the IETF than they are in most | meetings are much less important in the IETF than they are in most | |||
other organizations. Any decision made at a face-to-face meeting | other organizations. Any decision made at a face-to-face meeting | |||
must also gain consensus on the WG mailing list. This is sometimes | must also gain consensus on the WG mailing list. This is sometimes | |||
phrased as "at the last WG meeting, we decided XXX; if you disagree | phrased as "at the last WG meeting, we decided XXX; if you disagree | |||
please speak up by the end of the week" and you'll therefore often | please speak up by the end of the week" and you'll therefore often | |||
hear the phrase "to be confirmed on the list." There are numerous | hear the phrase "to be confirmed on the list." There are numerous | |||
examples of important decisions made in WG meetings that are later | examples of important decisions made in WG meetings that are later | |||
overturned on the mailing list, often because someone who couldn't | overturned on the mailing list, often because someone who couldn't | |||
skipping to change at line 1409 ¶ | skipping to change at line 1409 ¶ | |||
bring their concerns to the responsible AD. | bring their concerns to the responsible AD. | |||
When a WG has fulfilled its charter, it is supposed to cease | When a WG has fulfilled its charter, it is supposed to cease | |||
operations. (Most WG mailing lists continue on after a WG is closed, | operations. (Most WG mailing lists continue on after a WG is closed, | |||
still discussing the same topics as the Working Group did.) In the | still discussing the same topics as the Working Group did.) In the | |||
IETF, it is a mark of success that the WG closes up because it | IETF, it is a mark of success that the WG closes up because it | |||
fulfilled its charter. This is one of the aspects of the IETF that | fulfilled its charter. This is one of the aspects of the IETF that | |||
newcomers who have experience with other standards bodies have a hard | newcomers who have experience with other standards bodies have a hard | |||
time understanding. | time understanding. | |||
4.3 Working Group Documents | 4.3. Working Group Documents | |||
There is an official distinction between WG I-Ds and individual I-Ds. | There is an official distinction between WG I-Ds and individual I-Ds. | |||
A WG will have to review an individual draft before deciding if it | A WG will have to review an individual draft before deciding if it | |||
should be adopted by the WG. The WG chairs appoint who will be the | should be adopted by the WG. The WG chairs appoint who will be the | |||
authors or editors of the I-Ds; often those who wrote the initial | authors or editors of the I-Ds; often those who wrote the initial | |||
draft continue work on behalf of the WG. Procedures for Internet- | draft continue work on behalf of the WG. Procedures for Internet- | |||
Drafts are covered in much more detail later in this document. | Drafts are covered in much more detail later in this document. | |||
For Working Group documents, the document editor serves at the | For Working Group documents, the document editor serves at the | |||
pleasure of the WG Chair. There is often more than one editor for | pleasure of the WG Chair. There is often more than one editor for | |||
skipping to change at line 1445 ¶ | skipping to change at line 1445 ¶ | |||
determines who will be listed as authors on the title page and who | determines who will be listed as authors on the title page and who | |||
will be acknowledged as contributors in the body of the document. | will be acknowledged as contributors in the body of the document. | |||
When a WG document is ready to progress beyond the WG, the WG Chairs | When a WG document is ready to progress beyond the WG, the WG Chairs | |||
will assign a "shepherd" to take over the final process. The role of | will assign a "shepherd" to take over the final process. The role of | |||
the document shepherd is described in RFC 4858: Document Shepherding | the document shepherd is described in RFC 4858: Document Shepherding | |||
from Working Group Last Call to Publication (https://www.rfc- | from Working Group Last Call to Publication (https://www.rfc- | |||
editor.org/info/rfc4858). The chair, who knows the history of the | editor.org/info/rfc4858). The chair, who knows the history of the | |||
draft within the WG, often does the shepherd write-up. | draft within the WG, often does the shepherd write-up. | |||
4.4 Preparing for Working Group Meetings | 4.4. Preparing for Working Group Meetings | |||
The most important thing that *everyone* should do before coming to a | The most important thing that *everyone* should do before coming to a | |||
face-to-face meeting is to read the Internet-Drafts and RFCs ahead of | face-to-face meeting is to read the Internet-Drafts and RFCs ahead of | |||
time. WG meetings are explicitly not for education: they are for | time. WG meetings are explicitly not for education: they are for | |||
developing the group's documents and often the document is presented | developing the group's documents and often the document is presented | |||
as a set of slides saying "here's what changed since last meeting." | as a set of slides saying "here's what changed since last meeting." | |||
Even if you do not plan to say anything in the meeting, you should | Even if you do not plan to say anything in the meeting, you should | |||
read, or at least skim, the group's documents before attending so you | read, or at least skim, the group's documents before attending so you | |||
can understand what is being said. | can understand what is being said. | |||
skipping to change at line 1503 ¶ | skipping to change at line 1503 ¶ | |||
during Working Group sessions is to follow the running commentary on | during Working Group sessions is to follow the running commentary on | |||
the Jabber room associated with that Working Group. Jabber is a | the Jabber room associated with that Working Group. Jabber is a | |||
free, streaming XML technology mainly used for instant messaging. | free, streaming XML technology mainly used for instant messaging. | |||
You can find pointers to Jabber clients for many platforms at | You can find pointers to Jabber clients for many platforms at | |||
(https://xmpp.org/xmpp-software/clients). The Jabber chatrooms have | (https://xmpp.org/xmpp-software/clients). The Jabber chatrooms have | |||
the name of the Working Group followed by "@jabber.ietf.org". Those | the name of the Working Group followed by "@jabber.ietf.org". Those | |||
rooms are, in fact, available year-round, not just during IETF | rooms are, in fact, available year-round, not just during IETF | |||
meetings, and some are used by active Working Group participants | meetings, and some are used by active Working Group participants | |||
during protocol development. | during protocol development. | |||
4.5 Working Group Mailing Lists | 4.5. Working Group Mailing Lists | |||
As we mentioned earlier, the IETF announcement and discussion mailing | As we mentioned earlier, the IETF announcement and discussion mailing | |||
lists are the central mailing lists for IETF activities. However, | lists are the central mailing lists for IETF activities. However, | |||
there are many other mailing lists related to IETF work. For | there are many other mailing lists related to IETF work. For | |||
example, every Working Group has its own discussion list. In | example, every Working Group has its own discussion list. In | |||
addition, there are some long-term technical debates that have been | addition, there are some long-term technical debates that have been | |||
moved off of the IETF list onto lists created specifically for those | moved off of the IETF list onto lists created specifically for those | |||
topics. It is highly recommended that you follow the discussions on | topics. It is highly recommended that you follow the discussions on | |||
the mailing lists of the Working Groups that you wish to attend. The | the mailing lists of the Working Groups that you wish to attend. The | |||
more work that is done on the mailing lists, the less work that will | more work that is done on the mailing lists, the less work that will | |||
skipping to change at line 1527 ¶ | skipping to change at line 1527 ¶ | |||
The mailing lists also provide a forum for those who wish to follow, | The mailing lists also provide a forum for those who wish to follow, | |||
or contribute to, the Working Groups' efforts, but can't attend the | or contribute to, the Working Groups' efforts, but can't attend the | |||
IETF meetings. That's why IETF procedures require all decisions to | IETF meetings. That's why IETF procedures require all decisions to | |||
be confirmed "on the list" and you will often hear a WG chair say, | be confirmed "on the list" and you will often hear a WG chair say, | |||
"Let's take it to the list" to close a discussion. | "Let's take it to the list" to close a discussion. | |||
Every WG has a dedicated page on the datatracker site, and the | Every WG has a dedicated page on the datatracker site, and the | |||
"About" tab will point to mailing list subscription and archives. | "About" tab will point to mailing list subscription and archives. | |||
4.6 Interim Working Group Meetings | 4.6. Interim Working Group Meetings | |||
Working Groups sometimes hold interim meetings between IETFs. | Working Groups sometimes hold interim meetings between IETFs. | |||
Interim meetings aren't a substitute for IETF meetings, however -- a | Interim meetings aren't a substitute for IETF meetings, however -- a | |||
group can't decide to skip a meeting in a location they're not fond | group can't decide to skip a meeting in a location they're not fond | |||
of and meet in Cancun (or even someplace mundane) three weeks later, | of and meet in Cancun (or even someplace mundane) three weeks later, | |||
for example. Interim meetings need to be announced at least one | for example. Interim meetings need to be announced at least one | |||
month in advance. Location and timing need to allow fair access for | month in advance. Location and timing need to allow fair access for | |||
all participants. Like regular IETF meetings, someone needs to take | all participants. Like regular IETF meetings, someone needs to take | |||
notes and the group needs to take attendance. Decisions tentatively | notes and the group needs to take attendance. Decisions tentatively | |||
made during an interim WG meeting must still be confirmed on the | made during an interim WG meeting must still be confirmed on the | |||
mailing list. Interim meetings are subject to the IETF Note Well. | mailing list. Interim meetings are subject to the IETF Note Well. | |||
Most interim meetings are virtual these days and have the same | Most interim meetings are virtual these days and have the same | |||
reporting requirements as face-to-face virtual meetings. | reporting requirements as face-to-face virtual meetings. | |||
The IESG has rules for advance notice on time and place of interim | The IESG has rules for advance notice on time and place of interim | |||
Working Group meetings, as well as reporting the results of the | Working Group meetings, as well as reporting the results of the | |||
meetings. The purpose of these rules is to make interim meetings | meetings. The purpose of these rules is to make interim meetings | |||
accessible to as many Working Group members as possible and to | accessible to as many Working Group members as possible and to | |||
maintain the transparency of the Working Group process. | maintain the transparency of the Working Group process. | |||
5 BOFs and Dispatching | 5. BOFs and Dispatching | |||
In order to form a Working Group, you need a charter and someone who | In order to form a Working Group, you need a charter and someone who | |||
is able to be chair. In order to get those things, you need to get | is able to be chair. In order to get those things, you need to get | |||
people interested so that they can help focus the charter and | people interested so that they can help focus the charter and | |||
convince an Area Director that the project is worthwhile. A face-to- | convince an Area Director that the project is worthwhile. A face-to- | |||
face meeting is useful for this. In fact, very few WGs get started | face meeting is useful for this. In fact, very few WGs get started | |||
without an initial meeting. | without an initial meeting. | |||
A _Birds of a Feather_ (BOF) meeting has to be approved by the Area | A _Birds of a Feather_ (BOF) meeting has to be approved by the Area | |||
Director in the relevant area, in consultation with the IESG and the | Director in the relevant area, in consultation with the IESG and the | |||
skipping to change at line 1589 ¶ | skipping to change at line 1589 ¶ | |||
steps: possibilities include create a new WG, send to an existing WG, | steps: possibilities include create a new WG, send to an existing WG, | |||
hold a BOF, and so on. | hold a BOF, and so on. | |||
An advantage of using the dispatch WG compared to a BOF is that the | An advantage of using the dispatch WG compared to a BOF is that the | |||
discussion is more limited and focused. On the other hand, a draft | discussion is more limited and focused. On the other hand, a draft | |||
might tend to limit what the other folks in the BOF want to do in the | might tend to limit what the other folks in the BOF want to do in the | |||
charter. Remember that most BOFs are held in order to get support | charter. Remember that most BOFs are held in order to get support | |||
for an eventual Working Group, not to get support for a particular | for an eventual Working Group, not to get support for a particular | |||
document. | document. | |||
6 RFCs and Internet-Drafts | 6. RFCs and Internet-Drafts | |||
This section discusses Internet-Drafts and RFCs in the IETF stream, | This section discusses Internet-Drafts and RFCs in the IETF stream, | |||
that is, it describes how documents are produced and advanced within | that is, it describes how documents are produced and advanced within | |||
the IETF. For a brief note on other RFC streams, see above. | the IETF. For a brief note on other RFC streams, see above. | |||
If you're a new IETF participant and are looking for a particular RFC | If you're a new IETF participant and are looking for a particular RFC | |||
or Internet-Draft, you can use the IETF _Datatracker_. This website, | or Internet-Draft, you can use the IETF _Datatracker_. This website, | |||
https://datatracker.ietf.org/ (https://datatracker.ietf.org/), has a | https://datatracker.ietf.org/ (https://datatracker.ietf.org/), has a | |||
text search capability (including content, keywords, author, and so | text search capability (including content, keywords, author, and so | |||
on), and the search results point to the document status, page count, | on), and the search results point to the document status, page count, | |||
skipping to change at line 1618 ¶ | skipping to change at line 1618 ¶ | |||
started/#officialdocuments), particularly if it is not intended for | started/#officialdocuments), particularly if it is not intended for | |||
the standards track. For the sake of brevity, we will not mention | the standards track. For the sake of brevity, we will not mention | |||
those here. After all, this document is about "the Way of the IETF" | those here. After all, this document is about "the Way of the IETF" | |||
and the main Way is "developing standards." | and the main Way is "developing standards." | |||
If you are interested in learning more about how to author an | If you are interested in learning more about how to author an | |||
Internet-Draft yourself, the I-D Authors website | Internet-Draft yourself, the I-D Authors website | |||
(https://authors.ietf.org) has a lot of information and resources, | (https://authors.ietf.org) has a lot of information and resources, | |||
including pointers to online tools that can help. | including pointers to online tools that can help. | |||
6.1 The Overall Process | 6.1. The Overall Process | |||
The very first step is to have a draft document. Internet-Drafts | The very first step is to have a draft document. Internet-Drafts | |||
should follow a specific format, and are required to have particular | should follow a specific format, and are required to have particular | |||
sections. This will be discussed more below. | sections. This will be discussed more below. | |||
RFCs are generally written by a Working Group. If an appropriate WG | RFCs are generally written by a Working Group. If an appropriate WG | |||
doesn't seem to exist, then the BOF or Dispatch process mentioned | doesn't seem to exist, then the BOF or Dispatch process mentioned | |||
above can be used to learn which one is appropriate, or start the | above can be used to learn which one is appropriate, or start the | |||
process to create one. | process to create one. | |||
skipping to change at line 1692 ¶ | skipping to change at line 1692 ¶ | |||
The publication process can take weeks, but be patient, and you'll | The publication process can take weeks, but be patient, and you'll | |||
eventually see an email announcement saying that your brand-new RFC | eventually see an email announcement saying that your brand-new RFC | |||
has been published. Congratulations! | has been published. Congratulations! | |||
A much more complete explanation of these steps is contained in BCP 9 | A much more complete explanation of these steps is contained in BCP 9 | |||
(https://www.rfc-editor.org/info/bcp9). This set of documents goes | (https://www.rfc-editor.org/info/bcp9). This set of documents goes | |||
into great detail on a topic that is very often misunderstood, even | into great detail on a topic that is very often misunderstood, even | |||
by seasoned IETF participants: different types of RFCs go through | by seasoned IETF participants: different types of RFCs go through | |||
different processes and have different rankings. | different processes and have different rankings. | |||
6.2 Common Issues | 6.2. Common Issues | |||
There are two major issues that often come up while preparing I-Ds: | There are two major issues that often come up while preparing I-Ds: | |||
copyright and patents. | copyright and patents. | |||
We discussed copyright above, but expand on it here. When the IETF | We discussed copyright above, but expand on it here. When the IETF | |||
adopts a Internet-Draft, it is required that the _boilerplate_, the | adopts an Internet-Draft, it is required that the _boilerplate_, the | |||
common text that appears in every draft, has a notice that says the | common text that appears in every draft, has a notice that says the | |||
IETF, _and the document authors_ own the copyright. This means that | IETF, _and the document authors_ own the copyright. This means that | |||
while the IETF can do what it wants with the document, within | while the IETF can do what it wants with the document, within | |||
limitations so can you. You cannot, for example, claim this is an | limitations so can you. You cannot, for example, claim this is an | |||
IETF standard, nor use the IETF trademarks. | IETF standard, nor use the IETF trademarks. | |||
Incidentally, the change control on Internet standards doesn't end | Incidentally, the change control on Internet standards doesn't end | |||
when the RFC is published. Things can be changed later for a number | when the RFC is published. Things can be changed later for a number | |||
of reasons, such as to solve a newly-discovered problem or address | of reasons, such as to solve a newly-discovered problem or address | |||
new use-cases. These later changes are also under the control of the | new use-cases. These later changes are also under the control of the | |||
skipping to change at line 1748 ¶ | skipping to change at line 1748 ¶ | |||
in the document. Instead, consult the IPR disclosures | in the document. Instead, consult the IPR disclosures | |||
(https://datatracker.ietf.org/ipr/about/) page. If you still have | (https://datatracker.ietf.org/ipr/about/) page. If you still have | |||
issues, consult with the WG Chair or the responsible AD. | issues, consult with the WG Chair or the responsible AD. | |||
Intellectual property rights aren't mentioned in RFCs because RFCs | Intellectual property rights aren't mentioned in RFCs because RFCs | |||
never change after they are published, while knowledge of IPR can | never change after they are published, while knowledge of IPR can | |||
change at any time. Therefore, an IPR list in an RFC could be | change at any time. Therefore, an IPR list in an RFC could be | |||
incomplete and mislead the reader. BCP 79 (https://www.rfc- | incomplete and mislead the reader. BCP 79 (https://www.rfc- | |||
editor.org/info/bcp79) provides specific text that should be added to | editor.org/info/bcp79) provides specific text that should be added to | |||
RFCs where the author knows of IPR issues. | RFCs where the author knows of IPR issues. | |||
6.3 Writing an Internet-Draft | 6.3. Writing an Internet-Draft | |||
Every RFC starts its life as an I-D. Internet-Drafts have the same | Every RFC starts its life as an I-D. Internet-Drafts have the same | |||
format as an RFC, and are required to have all the content that | format as an RFC, and are required to have all the content that | |||
should appear in the RFC. This includes a couple of sections | should appear in the RFC. This includes a couple of sections | |||
detailed below. A draft may also have more information, such as an | detailed below. A draft may also have more information, such as an | |||
incremental list of changes from previous versions of the draft, or | incremental list of changes from previous versions of the draft, or | |||
pointers to online locations for raising issues and suggesting | pointers to online locations for raising issues and suggesting | |||
changes. | changes. | |||
For the past several years, the official canonical source of RFCs as | For the past several years, the official canonical source of RFCs as | |||
skipping to change at line 1781 ¶ | skipping to change at line 1781 ¶ | |||
help both new and experienced authors. As of this writing, it's | help both new and experienced authors. As of this writing, it's | |||
still a draft but it does contain a great deal of useful content. | still a draft but it does contain a great deal of useful content. | |||
You should feel free to use the site, and offer feedback. | You should feel free to use the site, and offer feedback. | |||
Outside of the formatting decision, the most important document you | Outside of the formatting decision, the most important document you | |||
can read is Guidelines to Authors of Internet-Drafts | can read is Guidelines to Authors of Internet-Drafts | |||
(https://www.ietf.org/how/ids/guidelines). That document explains | (https://www.ietf.org/how/ids/guidelines). That document explains | |||
the naming conventions, formatting requirements, required content, | the naming conventions, formatting requirements, required content, | |||
and details of how to submit (also called _post_) your draft. | and details of how to submit (also called _post_) your draft. | |||
6.3.1 Internet-Draft Language | 6.3.1. Internet-Draft Language | |||
It is common for Internet-Drafts that revise existing RFCs to have | It is common for Internet-Drafts that revise existing RFCs to have | |||
draft names with "bis" in them, meaning "again" or "twice." For | draft names with "bis" in them, meaning "again" or "twice." For | |||
example, a draft might be called "draft-ietf-uta-rfc6125bis" meaning | example, a draft might be called "draft-ietf-uta-rfc6125bis" meaning | |||
that this is intended to be a revision of, and eventual replacement | that this is intended to be a revision of, and eventual replacement | |||
for, RFC6125. | for, RFC6125. | |||
Writing clear specifications can be a bit of an art, particularly for | Writing clear specifications can be a bit of an art, particularly for | |||
people who don't have English as their native language. You can keep | people who don't have English as their native language. You can keep | |||
the specification very short, with just a list of requirements, but | the specification very short, with just a list of requirements, but | |||
skipping to change at line 1813 ¶ | skipping to change at line 1813 ¶ | |||
about a dozen keywords that can be used to clarify what are | about a dozen keywords that can be used to clarify what are | |||
requirements, as compared to what is purely informative. It defines | requirements, as compared to what is purely informative. It defines | |||
the meaning of words like _MUST_ and points out that it has to appear | the meaning of words like _MUST_ and points out that it has to appear | |||
in all uppercase to its special meaning. | in all uppercase to its special meaning. | |||
It is not uncommon for feedback on standards-track I-Ds to question | It is not uncommon for feedback on standards-track I-Ds to question | |||
the particular uses of what is called "2119 language." For example, | the particular uses of what is called "2119 language." For example, | |||
"The document says MAY but doesn't explain why not; should it be a | "The document says MAY but doesn't explain why not; should it be a | |||
MUST?" | MUST?" | |||
6.3.2 About References | 6.3.2. About References | |||
One aspect of writing IETF standards that trips up many newcomers is | One aspect of writing IETF standards that trips up many newcomers is | |||
the rule about how to make _normative references_ to non-IETF | the rule about how to make _normative references_ to non-IETF | |||
documents or to other RFCs in a standard. A normative reference is a | documents or to other RFCs in a standard. A normative reference is a | |||
reference to a document that must be followed in order to implement | reference to a document that must be followed in order to implement | |||
the standard. A non-normative reference (sometimes called an | the standard. A non-normative reference (sometimes called an | |||
_informative reference_) is one that is helpful to an implementor but | _informative reference_) is one that is helpful to an implementor but | |||
not strictly needed to implement it. | not strictly needed to implement it. | |||
An IETF standard may make a normative reference to any other | An IETF standard may make a normative reference to any other | |||
standards-track RFC that is at the same standards level or higher, or | standards-track RFC that is at the same standards level or higher, or | |||
to any "open standard" that has been developed outside the IETF. The | to any "open standard" that has been developed outside the IETF. The | |||
"same level or higher" rule means that before a standard can move | "same level or higher" rule means that before a standard can move | |||
from Proposed to Internet Standard, all of the RFCs that appear as a | from Proposed to Internet Standard, all of the RFCs that appear as a | |||
normative reference must also be an Internet Standard. This rule | normative reference must also be an Internet Standard. This rule | |||
gives implementors assurance that everything in a Internet standard | gives implementors assurance that everything in an Internet standard | |||
is quite stable, even the things referenced outside the standard. | is quite stable, even the things referenced outside the standard. | |||
This rule, and its exceptions, is described in BCP 97 | This rule, and its exceptions, is described in BCP 97 | |||
(https://www.rfc-editor.org/info/bcp97). | (https://www.rfc-editor.org/info/bcp97). | |||
There is no hard-and-fast rule about what is an "open standard", but | There is no hard-and-fast rule about what is an "open standard", but | |||
generally this means a stable standard that was made by a generally- | generally this means a stable standard that was made by a generally- | |||
recognized SDO, and that anyone can get a copy of, although not | recognized SDO, and that anyone can get a copy of, although not | |||
necessarily for free. If the external standard changes, you have to | necessarily for free. If the external standard changes, you have to | |||
reference the particular instantiation of that standard in your | reference the particular instantiation of that standard in your | |||
specification, as with a designation of the date of the standard. | specification, as with a designation of the date of the standard. | |||
Some external standards bodies don't make old standards available, | Some external standards bodies don't make old standards available, | |||
which is a problem for IETF standards that need to be used in the | which is a problem for IETF standards that need to be used in the | |||
future. When in doubt, ask the WG chair or AD if a particular | future. When in doubt, ask the WG chair or AD if a particular | |||
external standard can be used in an IETF standard. | external standard can be used in an IETF standard. | |||
6.3.3 About Required Content | 6.3.3. About Required Content | |||
Every draft is required to have some content. Some of this is | Every draft is required to have some content. Some of this is | |||
boilerplate text about copyright, "2119 keyword," and so on. The | boilerplate text about copyright, "2119 keyword," and so on. The | |||
document formatting tools will generate this for you automatically if | document formatting tools will generate this for you automatically if | |||
you use the right keyword. In addition, there are special sections | you use the right keyword. In addition, there are special sections | |||
that might be required for your draft, and you (and the WG) will have | that might be required for your draft, and you (and the WG) will have | |||
to write them. | to write them. | |||
Many IETF standards have extension points, such as unassigned fields | Many IETF standards have extension points, such as unassigned fields | |||
in a message header, or for something like email or HTTP, an actual | in a message header, or for something like email or HTTP, an actual | |||
skipping to change at line 1898 ¶ | skipping to change at line 1898 ¶ | |||
explicit privacy section. | explicit privacy section. | |||
Some drafts benefit from having an "Implementation Status" section, | Some drafts benefit from having an "Implementation Status" section, | |||
as explained by BCP 205: Improving Awareness of Running Code: The | as explained by BCP 205: Improving Awareness of Running Code: The | |||
Implementation Status Section (https://www.rfc-editor.org/info/ | Implementation Status Section (https://www.rfc-editor.org/info/ | |||
rfc7942). | rfc7942). | |||
More detail on the required content can be found online | More detail on the required content can be found online | |||
(https://authors.ietf.org/en/required-content). | (https://authors.ietf.org/en/required-content). | |||
6.4 Standards-Track RFCs | 6.4. Standards-Track RFCs | |||
If the IESG approves the draft to become a standards-track RFC, they | If the IESG approves the draft to become a standards-track RFC, they | |||
ask the RPC to publish it as a _Proposed Standard_. | ask the RPC to publish it as a _Proposed Standard_. | |||
Don't be surprised if a particular standard doesn't progress from | Don't be surprised if a particular standard doesn't progress from | |||
Proposed Standard to Internet Standard. To become an Internet | Proposed Standard to Internet Standard. To become an Internet | |||
Standard, an RFC must have multiple interoperable implementations and | Standard, an RFC must have multiple interoperable implementations and | |||
the unused features in the Proposed Standard must be removed; there | the unused features in the Proposed Standard must be removed; there | |||
are additional requirements listed in BCP 9 (https://www.rfc- | are additional requirements listed in BCP 9 (https://www.rfc- | |||
editor.org/info/bcp9). Most of the protocols in common use are | editor.org/info/bcp9). Most of the protocols in common use are | |||
Proposed standards and never move forward. This may be because no | Proposed standards and never move forward. This may be because no | |||
one took the time to try to get them to Internet Standard, or some of | one took the time to try to get them to Internet Standard, or some of | |||
the normative references in the standard are still at Proposed | the normative references in the standard are still at Proposed | |||
standard, or it may be that everyone found more important things to | standard, or it may be that everyone found more important things to | |||
do. | do. | |||
6.5 RFCs Other than Standards-Track | 6.5. RFCs Other than Standards-Track | |||
As mentioned earlier, not all RFCs are standards. In fact, many | As mentioned earlier, not all RFCs are standards. In fact, many | |||
important RFCs are not on the standards track at all. At the time of | important RFCs are not on the standards track at all. At the time of | |||
writing, there are also categories for Informational, Experimental, | writing, there are also categories for Informational, Experimental, | |||
Best Current Practice, and Historical for standards that are no | Best Current Practice, and Historical for standards that are no | |||
longer recommended for use. The role of Informational RFCs can be | longer recommended for use. The role of Informational RFCs can be | |||
confusing, and people sometimes refer to them as "standards," when | confusing, and people sometimes refer to them as "standards," when | |||
they are not. | they are not. | |||
Experimental RFCs are for specifications that are interesting, but | Experimental RFCs are for specifications that are interesting, but | |||
skipping to change at line 1954 ¶ | skipping to change at line 1954 ¶ | |||
document the many parts of the IETF process. The STD sub-series was | document the many parts of the IETF process. The STD sub-series was | |||
created to identify RFCs that do in fact specify Internet standards. | created to identify RFCs that do in fact specify Internet standards. | |||
These are an example of the aphorism that everything in computer | These are an example of the aphorism that everything in computer | |||
science can be solved by a layer of indirection. For example, a | science can be solved by a layer of indirection. For example, a | |||
single BCP can refer to one or more RFCs, and the specific RFCs can | single BCP can refer to one or more RFCs, and the specific RFCs can | |||
change such as when a new version of a protocol is published. | change such as when a new version of a protocol is published. | |||
Likewise, some STDs are actually sets of more than one RFC, and the | Likewise, some STDs are actually sets of more than one RFC, and the | |||
"standard" designation applies to the whole set of documents. | "standard" designation applies to the whole set of documents. | |||
7 How to Contribute to the IETF | 7. How to Contribute to the IETF | |||
7.1 What You Can Do | 7.1. What You Can Do | |||
*Read:* Review the Internet-Drafts in your area of expertise and | *Read:* Review the Internet-Drafts in your area of expertise and | |||
comment on them in the Working Groups. Participate in the discussion | comment on them in the Working Groups. Participate in the discussion | |||
in a friendly, helpful fashion, with the goal being the best Internet | in a friendly, helpful fashion, with the goal being the best Internet | |||
standards possible. Listen much more than you speak. If you | standards possible. Listen much more than you speak. If you | |||
disagree, debate the technical issues: never attack the people. | disagree, debate the technical issues: never attack the people. | |||
*Implement:* Write programs that use the current Internet standards. | *Implement:* Write programs that use the current Internet standards. | |||
The standards aren't worth much unless they are available to Internet | The standards aren't worth much unless they are available to Internet | |||
users. Implement even the "minor" standards, since they will become | users. Implement even the "minor" standards, since they will become | |||
skipping to change at line 1987 ¶ | skipping to change at line 1987 ¶ | |||
in the Hackathons. | in the Hackathons. | |||
*Write:* Edit or co-author Internet-Drafts in your area of expertise. | *Write:* Edit or co-author Internet-Drafts in your area of expertise. | |||
Do this for the benefit of the Internet community, not to get your | Do this for the benefit of the Internet community, not to get your | |||
name (or, even worse, your company's name) on a document. Draft | name (or, even worse, your company's name) on a document. Draft | |||
authors receive kinds of technical (and, sadly, sometimes personal) | authors receive kinds of technical (and, sadly, sometimes personal) | |||
criticism. Take the technical comments with equanimity and use it to | criticism. Take the technical comments with equanimity and use it to | |||
improve your draft in order to produce the best and most | improve your draft in order to produce the best and most | |||
interoperable standard, and ignore the personal ones. | interoperable standard, and ignore the personal ones. | |||
7.2 What Your Company Can Do | 7.2. What Your Company Can Do | |||
*Share:* Avoid proprietary standards. If you are an implementor, | *Share:* Avoid proprietary standards. If you are an implementor, | |||
exhibit a strong preference for IETF standards. If the IETF | exhibit a strong preference for IETF standards. If the IETF | |||
standards aren't as good as the proprietary standards, work to make | standards aren't as good as the proprietary standards, work to make | |||
the IETF standards better. If you're a purchaser, avoid products | the IETF standards better. If you're a purchaser, avoid products | |||
that use proprietary standards that compete with the open standards | that use proprietary standards that compete with the open standards | |||
of the IETF and tell the vendors that you are doing so. | of the IETF and tell the vendors that you are doing so. | |||
*Open Up:* If your company owns a patent that is used in an IETF | *Open Up:* If your company owns a patent that is used in an IETF | |||
standard, convince the company to make the patent available at no | standard, convince the company to make the patent available at no | |||
skipping to change at line 2015 ¶ | skipping to change at line 2015 ¶ | |||
sighted as other patent-holders. | sighted as other patent-holders. | |||
*Support:* The IETF has sponsorship opportunities | *Support:* The IETF has sponsorship opportunities | |||
(https://ietf.org/about/donors/) and an endowment | (https://ietf.org/about/donors/) and an endowment | |||
(https://www.ietf.org/endowment/donate-ietf-endowment/) which can | (https://www.ietf.org/endowment/donate-ietf-endowment/) which can | |||
also take individual-sized donations. Become a member of ISOC. Urge | also take individual-sized donations. Become a member of ISOC. Urge | |||
any company that has benefited from the Internet to contribute, since | any company that has benefited from the Internet to contribute, since | |||
this has the greatest financial benefit for the group. It will, of | this has the greatest financial benefit for the group. It will, of | |||
course, also benefit the Internet as a whole. | course, also benefit the Internet as a whole. | |||
8 IETF and the Outside World | 8. IETF and the Outside World | |||
While some IETF participants would like to think otherwise, the IETF | While some IETF participants would like to think otherwise, the IETF | |||
does not exist in a standards vacuum. This section discusses two | does not exist in a standards vacuum. This section discusses two | |||
important groups. | important groups. | |||
8.1 IETF and Other SDOs | 8.1. IETF and Other SDOs | |||
There are many other standards organizations whose decisions affect | There are many other standards organizations whose decisions affect | |||
the Internet. Some of them ignored the Internet for a long time and | the Internet. Some of them ignored the Internet for a long time and | |||
now want to get a piece of the action. In general, the IETF tries to | now want to get a piece of the action. In general, the IETF tries to | |||
have cordial relationships with other SDOs. This isn't always easy, | have cordial relationships with other SDOs. This isn't always easy, | |||
since they usually have different structures and processes than the | since they usually have different structures and processes than the | |||
IETF does, and the IETF is mostly run by volunteers who would | IETF does, and the IETF is mostly run by volunteers who would | |||
probably prefer to write standards rather than meet with | probably prefer to write standards rather than meet with | |||
representatives from other bodies. Even so, many SDOs make a great | representatives from other bodies. Even so, many SDOs make a great | |||
effort to interact well with the IETF despite the obvious cultural | effort to interact well with the IETF despite the obvious cultural | |||
skipping to change at line 2049 ¶ | skipping to change at line 2049 ¶ | |||
role. The best place to check to see whether the IETF has any formal | role. The best place to check to see whether the IETF has any formal | |||
liaison at all is the list of IETF liaisons | liaison at all is the list of IETF liaisons | |||
(https://www.ietf.org/about/liaisons). | (https://www.ietf.org/about/liaisons). | |||
At the time of this writing, the IETF has around two dozen liaisons. | At the time of this writing, the IETF has around two dozen liaisons. | |||
Some of these liaison tasks fall to the IESG, whereas others fall to | Some of these liaison tasks fall to the IESG, whereas others fall to | |||
the IAB. Full details about the processes for dealing with other | the IAB. Full details about the processes for dealing with other | |||
SDOs can be found in BCP 102 (https://www.rfc-editor.org/info/bcp102) | SDOs can be found in BCP 102 (https://www.rfc-editor.org/info/bcp102) | |||
and BCP 103 (https://www.rfc-editor.org/info/bcp103). | and BCP 103 (https://www.rfc-editor.org/info/bcp103). | |||
8.2 Press Coverage of the IETF | 8.2. Press Coverage of the IETF | |||
Given that the IETF is one of the best-known bodies that is helping | Given that the IETF is one of the best-known bodies that is helping | |||
move the Internet forward, it's natural for the media to cover its | move the Internet forward, it's natural for the media to cover its | |||
actions. But it can be hard to cover the IETF; a common mistake is | actions. But it can be hard to cover the IETF; a common mistake is | |||
reporting an individual's Internet-Draft as something the IETF is | reporting an individual's Internet-Draft as something the IETF is | |||
working on, or that the IETF has approved a new standard when it was | working on, or that the IETF has approved a new standard when it was | |||
an Informational or Individual RFC. Often, the press is not really | an Informational or Individual RFC. Often, the press is not really | |||
to blame for the problem, as they might have been alerted to the | to blame for the problem, as they might have been alerted to the | |||
story by a company trying to get publicity for a protocol, or they | story by a company trying to get publicity for a protocol, or they | |||
see the latest "controversy" on social media. | see the latest "controversy" on social media. | |||
End of changes. 61 change blocks. | ||||
103 lines changed or deleted | 103 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |