Skip to main content
  • JSONPath: from blog post to RFC in 17 years

    Today the JSONPath RFC (RFC 9535) proposed standard was published, precisely 17 years after Stefan Gössner wrote his influential blog post JSONPath – XPath for JSON that resulted in some 50 implementations in various languages.

    • Glyn NormingtonRFC 9535 Editor
    21 Feb 2024
  • Stepping towards a Sustainable Internet

    The IAB’s new Environmental Impacts of Internet Technology (E-Impact) program will hold its first virtual interim meeting over two slots on 15 and 16 February 2024. These interim meetings are open to participation, and we invite all interested community members to join, participate, and contribute.

    • Jari ArkkoE-Impact Program Lead
    • Suresh KrishnanE-Impact Program Lead
    7 Feb 2024
  • What’s the deal with Media Over QUIC?

    In 2022, the IETF formed a working group for Media Over QUIC (MoQ)—a media delivery solution that has the potential to transform how we send and receive media during live streaming, real-time collaboration, gaming, and more.

    • Brett BralleyThought Leadership Content Writer, Cisco
    25 Jan 2024
  • IETF Administration LLC 2024 Budget

    The IETF Administration LLC has finalised its budget for 2024.

    • Jay DaleyIETF Executive Director
    18 Jan 2024
  • Update on the IT Infrastructure Transition Project

    Begun in the last quarter of 2023, work is underway to define and deploy a new, cloud-based infrastructure approach for services that support the work of the IETF, and to move those services onto the new infrastructure.

    • Robert SparksIETF Tools Project Manager
    12 Jan 2024

Filter by topic and date

Filter by topic and date

Privacy and Trustworthiness for Web Notifications

  • Martin ThomsonIETF Participant

18 Oct 2017

RFC 8188 builds on existing protocols to provide a new option for delivering trustworthy messages containing confidential information over the Internet.

Mailboxes with flags

HTTPS (HTTP over TLS) is possibly the mostwidely used security protocol in existence. HTTPS is a two-party protocol; it involves a single client and a single server. This aspect of the protocol limits the ways in which it can be used.

The recently published RFC 8188 provides protocol designers a new option for building multi-party protocols with HTTPS by defining a standardized format for encrypting HTTP message bodies. While this tool is less capable than other encryption formats, like CMS (RFC 5652) or JOSE (RFC 7516), it is designed for simplicity and ease-of-integration with existing HTTP semantics.

The WebPush protocol (RFC 8030) provides an example of the how the encrypted HTTP content coding could be used.

In WebPush, there are three parties: a user agent (in most cases this is a Web browser), an application server, and a push service. The push service is an HTTP server that has a special relationship with the user agent. The push service can wake a user agent from sleep and contact it even though it might be behind a firewall or NAT.

The application server uses the push service to send a push message to a user agent. The push service receives a message from the application server, and then forwards the contents of the push message to the user agent at the next opportunity. It is important here to recognize that the push service only forwards messages. It has no need to see or modify push messages. Both the user agent and the application server only communicate via the push service, but they both want some assurance that the push service cannot read or modify push messages. Nor do they want the push service to be able to create false push messages.

For example, an alerting service might use WebPush to deliver alerts to mobile devices without increased battery drain. Push message encryption ensures that these messages are trustworthy and allows the messages to contain confidential information.

The document draft-ietf-webpush-encryption, which was recently approved for publication as an RFC, describes how push messages can be encrypted using RFC 8188. The encrypted content coding ensures that the push service has access to the information it needs, such as URLs and HTTP header fields, but that the content of push messages is protected.

WebPush is available in some web browsers through the W3C Push API, which requires push message encryption.


Share this page