TLS 1.3: One Year Later
Just over a year after it was published as an RFC, TLS 1.3 adoption is growing rapidly.
Providers of voice over IP in the United States will be required to implement the IETF’s Secure Telephony Identity Revisited (STIR) protocol as a result of recently enacted legislation to address some of the root causes of illegal robocalling on the telephone network.
As part of a broader package of reforms aimed at curbing the explosive growth of robocalls, providers of Session Initiation Protocol (SIP)-based services will be required to implement STIR, the base specification of which was published as RFC 8224 together, with extensions in RFCs 8225, 8226, and 8588. A recent IETF blog post by Jon Peterson provides additional details and background about how the STIR working group approached the problem of authenticating callers using SIP-based services.
The same legislation will require providers of voice services to “take reasonable measures to implement an effective call authentication framework in the non-Internet protocol networks of the provider of voice service.” The STIR working group has been considering this issue as well. Its “STIR Out-of-Band Architecture and Use Cases” document was submitted last month to the Internet Engineering Steering Group for consideration to be published as an IETF RFC. You can find more information about the STIR working group and its work via the IETF Datatracker.
Just over a year after it was published as an RFC, TLS 1.3 adoption is growing rapidly.
At the end of November the IETF community gathered in Singapore for its 106th meeting. Across all six of the IETF’s technical areas, we saw constructive discussions of new work proposals, existing working groups progressing towards major milestones, and mature working groups wrapping up their final work items before closing. Here is a taste of what happened in each area.
The IETF Network Operations Center (NOC) team takes on the large task to build each meetings network. Monitoring the network once it is built is important. The NOC uses a number of tools and one of those tools are a number of Raspberry Pis.
Looking ahead to IETF 106 taking place 16-22 November 2019 in Singapore? Here are a few final items to consider before the meeting starts.
The IETF Administration LLC has drafted the 2020 Budget under the guidance of its first permanent board. Careful consideration has been provided to each budget request as well as the needs of the Community as a whole.
Show all