Posts by rfceditor@mastodon.online
(DIR) Post #B9pvUNmb4VryPqCQ9g by rfceditor@mastodon.online
0 likes, 0 repeats
RFC 10034: RTP Payload Format for Visual Volumetric Video-Based Coding (V3C), L. Ilola, et al., https://www.rfc-editor.org/info/rfc10034 #RFC A visual volumetric video-based coding (V3C) ISO/IEC 23090-5 bitstream is composed of V3C units that contain V3C atlas sub-bitstreams, V3C video sub-bitstreams, and a V3C parameter set. This document describes an RTP payload format for V3C atlas 1/3
(DIR) Post #B9pvUerpYJ9nOzmLAm by rfceditor@mastodon.online
0 likes, 0 repeats
sub-bitstreams. The RTP payload format for V3C video sub-bitstreams is defined by relevant IETF RFCs for the applicable video codec. The V3C RTP payload format allows for the packetization of one or more V3C atlas Network Abstraction Layer (NAL) units in an RTP packet payload as well as the fragmentation of a V3C atlas NAL unit into multiple RTP packets. The document also describes the 2/3
(DIR) Post #B9pvUfgWVphrwDUpBg by rfceditor@mastodon.online
0 likes, 0 repeats
mechanisms for grouping RTP streams of V3C component sub-bitstreams, providing a complete solution for streaming V3C-encoded content. This document is a product of the Audio/Video Transport Core Maintenance Working Group of the IETF. 3/3
(DIR) Post #B9q8iP8S8fBW4KRGDo by rfceditor@mastodon.online
0 likes, 0 repeats
RFC 10038: Distributing the Segment Routing over IPv6 (SRv6) Locator Using DHCPv6, W. Cheng, Ed., et al., https://www.rfc-editor.org/info/rfc10038 #RFC In an SRv6 network, each SRv6 Segment Endpoint Node must be assigned an SRv6 Locator, and segment identifiers (SIDs) are generated within the address space of this SRv6 Locator. This document describes a method for assigning SRv6 Locators to 1/2
(DIR) Post #B9q8iPjfuGxVvlqzEu by rfceditor@mastodon.online
0 likes, 0 repeats
SRv6 Segment Endpoint Nodes through the Dynamic Host Configuration Protocol for IPv6 (DHCPv6). This document is a product of the Source Packet Routing in Networking Working Group of the IETF. 2/2
(DIR) Post #B9qLA2DE9sHyX5c69w by rfceditor@mastodon.online
0 likes, 0 repeats
RFC 10037: Registration Data Access Protocol (RDAP) Extension for DNS Time-to-Live (TTL) Values, G. Brown, https://www.rfc-editor.org/info/rfc10037 #RFC This document specifies an extension to the Registration Data Access Protocol (RDAP), which allows the Time-to-Live (TTL) values for relevant DNS record types to be included in RDAP responses. This document is a product of the Registration 1/2
(DIR) Post #B9qLAEcq0TuB1zgikC by rfceditor@mastodon.online
0 likes, 0 repeats
Protocols Extensions Working Group of the IETF. 2/2
(DIR) Post #B9wOceSd0ilM4quioq by rfceditor@mastodon.online
0 likes, 0 repeats
RFC 10042: Post-Quantum/Traditional Hybrid Key Exchange with the Module-Lattice-Based Key-Encapsulation Mechanism for Use in SSH, P. Kampanakis, et al., https://www.rfc-editor.org/info/rfc10042 #RFC This document defines Post-Quantum Traditional (PQ/T) Hybrid key exchange methods based on the quantum-resistant Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM) standard and traditional 1/2
(DIR) Post #B9wOcyTiaNWCA1ZsIK by rfceditor@mastodon.online
0 likes, 0 repeats
Elliptic-Curve Diffie-Hellman (ECDH) key exchange schemes. These methods are defined for use in the Secure Shell (SSH) transport layer protocol. This document is a product of the Secure Shell Maintenance Working Group of the IETF. 2/2
(DIR) Post #BADSUlxclFYQYolrkW by rfceditor@mastodon.online
0 likes, 0 repeats
RFC 10039: Interconnecting EVPN and IPVPN Domains, J. Rabadan, Ed., et al., https://www.rfc-editor.org/info/rfc10039 #RFC Ethernet Virtual Private Network (EVPN) provides a unified BGP control plane for both intra- and inter-subnet forwarding within tenant networks. When a tenant network spans multiple domains, including any combination of EVPN and IPVPN domains, it becomes necessary to 1/3
(DIR) Post #BADSV4chNH6aRQ7vGq by rfceditor@mastodon.online
0 likes, 0 repeats
define the interworking mechanisms among these BGP domains (EVPN and IPVPN) to ensure seamless end-to-end tenant connectivity. This document defines these interworking procedures. In addition, this document defines a new BGP Path Attribute, referred to as Domain Path (D-PATH), which provides loop prevention for gateway nodes by protecting against control plane loops. The introduction of 2/3
(DIR) Post #BADSV5R2M7N4xXg7jU by rfceditor@mastodon.online
0 likes, 0 repeats
D-PATH modifies the BGP best-path selection process for Multiprotocol BGP inter-subnet forwarding (ISF) routes of Subsequent Address Family Identifiers (SAFIs) 128 (IPVPN) and 70 (EVPN). This document is a product of the BGP Enabled ServiceS Working Group of the IETF. 3/3
(DIR) Post #BARR1z73KYri2916H2 by rfceditor@mastodon.online
0 likes, 0 repeats
RFC 10033: Hash-Based Signatures: State and Backup Management, T. Wiggers, et al., https://www.rfc-editor.org/info/rfc10033 #RFC Stateful Hash-Based Signature Schemes (Stateful HBS) such as Leighton-Micali Signature (LMS), Hierarchical Signature System (HSS), eXtended Merkle Signature Scheme (XMSS), and XMSS^MT combine Merkle trees with One-Time Signatures (OTSs) to provide signatures that 1/4
(DIR) Post #BARR2GYcTK188Z2r6O by rfceditor@mastodon.online
0 likes, 0 repeats
are resistant against attacks using large-scale quantum computers. Unlike conventional stateless digital signature schemes, Stateful HBS have a state to keep track of which OTS keys have been used, as double-signing with the same OTS key allows forgeries. This document provides guidance and catalogs security considerations for the operational and technical aspects of deploying systems that 2/4
(DIR) Post #BARR2I9sWHPn6PU7oe by rfceditor@mastodon.online
0 likes, 0 repeats
rely on Stateful HBS. Management of the state of the Stateful HBS, including any handling of redundant key material, is a sensitive topic. This document describes some approaches to handle the associated challenges. It also describes the challenges that need to be resolved before certain approaches should be considered. This document is a product of the Post-Quantum Use In Protocols Working 3/4
(DIR) Post #BARR2JI4JJYoc6KBDk by rfceditor@mastodon.online
0 likes, 0 repeats
Group of the IETF. 4/4
(DIR) Post #BARiK94ejQdTMT8oRU by rfceditor@mastodon.online
0 likes, 0 repeats
RFC 10040: Locator/ID Separation Protocol (LISP) Geo-Coordinates, D. Farinacci, https://www.rfc-editor.org/info/rfc10040 #RFC This document describes how Geo-Coordinates can be used in the Locator/ID Separation Protocol (LISP) and defines a new LISP Canonical Address Format (LCAF) encoding for such Geo-Coordinates. This document updates RFC 8060. This document is a product of the Locator/ID 1/2
(DIR) Post #BARiKA6SuBg2YMzltw by rfceditor@mastodon.online
0 likes, 0 repeats
Separation Protocol Working Group of the IETF. 2/2
(DIR) Post #BATtrWRSirzK17zF7g by rfceditor@mastodon.online
0 likes, 0 repeats
RFC 10016: System-Defined Configuration, Q. Ma, Ed., et al., https://www.rfc-editor.org/info/rfc10016 #RFC The Network Management Datastore Architecture (NMDA) in RFC 8342 defines several configuration datastores holding configuration. The contents of these configuration datastores are controlled by clients. This document introduces the concept of a system configuration datastore holding 1/2
(DIR) Post #BATtrj0I1CycycNE4e by rfceditor@mastodon.online
0 likes, 0 repeats
configuration controlled by the system on which a server is running. The system configuration can be referenced (e.g., leafref) by configuration explicitly created by clients. This document updates RFC 8342. This document is a product of the Network Modeling Working Group of the IETF. 2/2