Carsten Bormann
This was a one-shot contribution to provide travel support for participation to the Internet Engineering Task Force (IETF), and specifically participation at the July 2025 plenary meeting in Madrid. I attended this meeting as an Internet Transport expert contributing work and progressing standards to support the evolution of the Internet and its support for enhanced resilience, authentication and privacy. An in-person attendance at the technical sessions also allowed me to progress the work for which I am an editor: Qlog draft-ietf-tsvwg-careful-resume-qlog, a transport specification based on the “qlog” specification being developed by the IETF QUIC; and a recent work item in the IETF Congestion Control working group, “Increase of the Congestion Window when the Sender Is Rate-Limited” (draft-ietf-ccwg-ratelimited-increase). In-person participation at this meeting is particularly important in my current role as an Area Director of the WIT Area, where I will help organise and oversee the meeting as a whole and specifically support the WIT area WG chairs in organising WG sessions and supporting cross area review of emerging specifications.
The document describes the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on IEEE 802.15.4 networks. Additional specifications include a simple header compression scheme using shared context and provisions for packet delivery in IEEE 802.15.4 meshes.
The document defines a portion of the Management Information Base (MIB) for use with network management protocols. In particular it defines objects for managing IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) [RFC4944].
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
The low- power variant of Bluetooth has been standardized since revision 4.0 of the Bluetooth specifications, although version 4.1 or newer is required for IPv6. This document describes how IPv6 is transported over Bluetooth low energy using IPv6 over Low-power Wireless Personal Area Network (6LoWPAN) techniques.
LoWPAN encapsulation as defined in RFC 4944 has been updated by [RFC6282], and may be extended and modified by future IETF Standards. The intended Layer 2 technology for IPv6 datagrams using LoWPAN encapsulation as originally defined is [IEEE.802.15.4_2011], which does not provide for a protocol switch in its Layer 2 headers.
As more and more protocols need to be compressed, the encoding capabilities of the original dispatch defined in the 6LowPAN adaptation-layer framework ([RFC4944] and [RFC6282]) becomes saturated. This specification introduces a new context switch mechanism for 6LoWPAN compression, expressed in terms of Pages and signaled by a new Paging Dispatch mechanism.
Master-Slave/Token-Passing (MS/TP) is a medium access control method for the RS-485 physical layer and is used primarily in building automation networks. This specification defines the frame format for transmission of IPv6 packets and the method of forming link-local and statelessly autoconfigured IPv6 addresses on MS/TP networks.
Service providers are starting to deploy and interconnect computing capabilities across the network for hosting network functions and applications. In distributed computing environments, both computing and topological information are necessary in order to determine the more convenient infrastructure where to deploy such a service or application. This document proposes an initial approach towards the use of ALTO to provide such information and assist the selection of appropriate deployment locations for services and applications.
OAuth 2.0 is the industry-standard protocol for authorization.