Skip to main content
  • IETF 116 Yokohama registration now open

    Registration is now open for IETF 116 Yokohama

    • Jay DaleyIETF Executive Director
    24 Nov 2022
  • IETF 115 post-meeting survey

    IETF 115 London was held 5-11 November 2022

    • Jay DaleyIETF Executive Director
    22 Nov 2022
  • Catching up on IETF 115

    Recordings are now available for sessions held during the IETF 115 meeting and the IETF Hackathon, where more than 1500 participants gathered in London and online 5-11 November 2022.

      13 Nov 2022
    • Opportunities for university researchers and students during IETF 115

      The upcoming IETF 115 meeting in London on 5-11 November 2022 is a unique opportunity for networking researchers to learn how RFCs are written, to engage with the Internet standards community to begin to develop research impact, and to meet more than 1,000 leading technologists from around the world currently working in industry, academia, and other organizations.

        1 Nov 2022
      • Suggested IETF 115 Sessions for Getting Familiar with New Topics

        These IETF 115 meeting sessions are likely to include discussions and new proposals that are accessible to a broad range of Internet technologists whether they are new to the IETF or long-time participants.

          24 Oct 2022

        Filter by topic and date

        Filter by topic and date

        Reporting Protocol Vulnerabilities

        • Roman DanyliwSecurity Area Director

        22 Mar 2021

        The Internet Engineering Task Force recognizes that security vulnerabilities will be discovered in IETF protocols and welcomes their critical evaluation by researchers. After consulting with the community, the Internet Engineering Steering Group (IESG) recently provided guidance on how to report vulnerabilities to ensure they are addressed as effectively as possible.

        vulnerability alert

        The full set of guidance is the best source for all the information about how to report vulnerabilities in IETF protocols, but a few details are worth highlighting.

        First, the process covers vulnerabilities in protocols or other specifications in documents, such as RFCs, published by the IETF. Security issues in specific products, software, or services that implement the protocols must be addressed by the providers or maintainers of those specific products or services. The IETF does not have any formal means of contacting those parties. Vulnerabilities in any infrastructure or services that support the IETF, IRTF and IAB (such as those associated with the ietf.org, iab.org, irtf.org and rfc-editor.org domains) are the responsibility of the IETF Administration LLC, which has its own vulnerability disclosure policy.

        Second depending on the nature of the report, there may be specific steps a reporter can take to expedite its handling, as detailed in the vulnerability reporting guidance. For published RFCs or Internet-Drafts (I-Ds) currently under consideration by an active working group, the working group is the proper forum to address the issue. For individuals Internet-Drafts, contact the document author(s). For working group I-Ds or RFCs for which there is no active working group, the general reporting email address can be used.

        Finally, while the IETF values critical analysis of its work, it does not pay “bug bounties” for reported vulnerabilities. IETF processes for creating and maintaining protocol specifications are open and transparent with meeting and mailing list archives publicly available. The protocol vulnerability reporting guidance provides more detail about further considerations, including how complex or severe vulnerabilities might be addressed.

        While the preferred approach to reporting IETF protocol vulnerabilities is to contact the person or group responsible for the document, as a last resort, reports can always be  sent by email to protocol-vulnerability@ietf.org. The IETF Security Area Directors will make their best effort to triage the report. We hope this guidance helps maintain and improve the security of the protocols and specifications on which the global Internet is built.


        Share this page