Skip to main content
  • IETF 118 post-meeting survey

    IETF 118 Prague was held 4-10 November 2023 and the results of the post-meeting survey are now available on a web-based interactive dashboard.

    • Jay DaleyIETF Executive Director
    30 Nov 2023
  • Net zero update for 2023

    An update on the IETF’s carbon footprint over the past year and efforts going forward to increase the sustainability of how the IETF operates.

    • Greg WoodIETF LLC Director of Communications and Operations
    • Stephanie McCammonDirector of Meetings and Sponsorships, IETF Secretariat
    29 Nov 2023
  • IETF 118 Highlights

    The IETF 118 meeting was held in Prague in early November. In general, the meeting was productive and full of lively discussions fueled by 1067 onsite participants, and 1806 participants altogether.

    • Christopher A. WoodIAB Member
    28 Nov 2023
  • Cisco to host IETF 121 Dublin meeting

    I am pleased to announce that Cisco will be the Host for IETF 121 Dublin, 2-8 November 2024.

    • Jay DaleyIETF Executive Director
    6 Nov 2023
  • Suggested IETF 118 Sessions for Getting Familiar with New Topics

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

      4 Nov 2023

    Filter by topic and date

    Filter by topic and date

    IETF LLC Statement on OFAC Compliance Questions

    • Jason LivingoodIETF Administration LLC Board Chair

    24 Mar 2021

    IETF contributors recently asked the IETF LLC about the implications of complying with the US Treasury Department’s Office of Financial Asset Controls (OFAC).

    See:

    The sanctions rules managed by the US Treasury Department’s Office of Financial Asset Controls (OFAC) are nuanced and complex; broad statements about them are inevitably oversimplifications. That said, we think it unlikely that OFAC rules would meaningfully inhibit participation in IETF activities by individuals from sanctioned countries, or ever have in the past, as a general matter. OFAC rules focus on transactions and trade. Most IETF activity is fundamentally speech, excepted out from OFAC regulation either explicitly in the OFAC rules themselves or implicitly via U.S. constitutional safeguards.

    We are not aware of any instance where OFAC rules have inhibited an individual from participating in the IETF. If such a situation were to arise in the future, we would work the affected individual to seek an appropriate accommodation to enable participation—for example, we could avoid problematic transactions while still engaging in communications, or seek a license from OFAC, or even escalate the issue as a legal matter if we thought that an individual’s right “to seek, receive and impart information and ideas through any media and regardless of frontiers” was being infringed (quoting the U.N. Declaration of Human Rights).

    Properly complying with the OFAC regulations—as well as all other applicable laws and regulations—remains a critical task for IETF LLC. Our OFAC policy is designed to ensure our compliance. We do not anticipate that compliance will cause negative impacts on the IETF or its current or potential future new participants.

    Recommendation of the IETF LLC to the General Area Dispatch working group and the Internet-Draft authors that asked the initial question.

    We have no data to suggest OFAC rules have ever prevented any individual from participating in and contributing to the technical work of the IETF. We predict this will remain true in the future. OFAC rules thus do not appear to be a factor that will lead to a negative impact on the diversity and inclusiveness of the IETF. Further, OFAC regulations are a complex, nuanced topic that is difficult for non-experts to assess, and that defy simple summary treatment. Misstatements about compliance can have consequences. 

    Accordingly, we recommend that any IETF groups or individuals focusing on issues of diversity and inclusiveness leave OFAC issues out of scope, given that (a) they are unlikely to negatively impact participation, (b) there is no evidence suggesting it has had an impact in the past, and (c) statements about IETF OFAC compliance are best managed by legal counsel.


    Share this page