Internet Drafts - IDs for Feb/2025

Index - Month Index of IDs

All IDs - sorted by date)

28/02/2025

	BGP Classful Transport Planes
	draft-ietf-idr-bgp-ct-39.txt   Date: 28/02/2025   Authors: Kaliraj Vairavakkalai, Natrajan Venkataraman   Working Group: Inter-Domain Routing (idr)	This document specifies a mechanism referred to as "Intent Driven Service Mapping". The mechanism uses BGP to express intent based association of overlay routes with underlay routes having specific Traffic Engineering (TE) characteristics satisfying a certain Service Level Agreement (SLA). This is achieved by defining new constructs to group underlay routes with sufficiently similar TE characteristics into identifiable classes (called "Transport Classes"), that overlay routes use as an ordered set to resolve reachability (Resolution Schemes) towards service endpoints. These constructs can be used, for example, to realize the "IETF Network Slice" defined in TEAS Network Slices framework. Additionally, this document specifies protocol procedures for BGP that enable dissemination of service mapping information in a network that may span multiple cooperating administrative domains. These domains may be administered either by the same provider or by closely coordinating providers. A new BGP address family that leverages RFC 4364 ("BGP/MPLS IP Virtual Private Networks (VPNs)") procedures and follows RFC 8277 ("Using BGP to Bind MPLS Labels to Address Prefixes") NLRI encoding is defined to enable each advertised underlay route to be identified by its class. This new address family is called "BGP Classful Transport", a.k.a., BGP CT.

27/02/2025

	Limits on Sending and Processing IPv6 Extension Headers
	draft-ietf-6man-eh-limits-19.txt   Date: 27/02/2025   Authors: Tom Herbert   Working Group: IPv6 Maintenance (6man)	This document defines various limits that may be applied to receiving, sending, and otherwise processing packets that contain IPv6 extension headers. Limits are pragmatic to facilitate interoperability amongst hosts and routers, thereby increasing the deployability of extension headers. The limits described herein establish the minimum baseline of support for use of extension headers on the Internet. If it is known that all communicating parties for a particular communication, including destination hosts and any routers in the path, are capable of supporting more than the baseline then these default limits may be freely exceeded.
	Compact Denial of Existence in DNSSEC
	draft-ietf-dnsop-compact-denial-of-existence-07.txt   Date: 27/02/2025   Authors: Shumon Huque, Christian Elmerot, Olafur Gudmundsson   Working Group: Domain Name System Operations (dnsop)	This document describes a technique to generate a signed DNS response on demand for a non-existent name by claiming that the name exists but doesn't have any data for the queried record type. Such answers require only one minimally covering NSEC or NSEC3 record, allow online signing servers to minimize signing operations and response sizes, and prevent zone content disclosure. This document updates RFC 4034 and 4035.

26/02/2025

	Path Computation Element Protocol (PCEP) Extension for Color
	draft-ietf-pce-pcep-color-12.txt   Date: 26/02/2025   Authors: Balaji Rajagopalan, Vishnu Beeram, Shaofu Peng, Mike Koldychev, Gyan Mishra   Working Group: Path Computation Element (pce)	Color is a 32-bit numerical (unsigned integer) attribute used to associate a Traffic Engineering (TE) tunnel or policy with an intent or objective. For example, a TE Tunnel constructed to deliver low latency services and whose path is optimized for delay can be tagged with a color that represents "low latency." This document specifies extensions to the Path Computation Element Protocol (PCEP) to carry the color attribute.

21/02/2025

	KangarooTwelve and TurboSHAKE
	draft-irtf-cfrg-kangarootwelve-17.txt   Date: 21/02/2025   Authors: Benoit Viguier, David Wong, Gilles Van Assche, Quynh Dang, Joan Daemen   Working Group: Crypto Forum (cfrg)	This document defines four eXtendable Output Functions (XOF), hash functions with output of arbitrary length, named TurboSHAKE128, TurboSHAKE256, KT128 and KT256. All four functions provide efficient and secure hashing primitives, and the last two are able to exploit the parallelism of the implementation in a scalable way. This document is a product of the Crypto Forum Research Group. It builds up on the definitions of the permutations and of the sponge construction in [FIPS 202], and is meant to serve as a stable reference and an implementation guide.

20/02/2025

	BGP Color-Aware Routing (CAR)
	draft-ietf-idr-bgp-car-16.txt   Date: 20/02/2025   Authors: Dhananjaya Rao, Swadesh Agrawal   Working Group: Inter-Domain Routing (idr)	This document describes a BGP based routing solution to establish end-to-end intent-aware paths across a multi-domain transport network. The transport network can span multiple service provider and customer network domains. The BGP intent-aware paths can be used to steer traffic flows for service routes that need a specific intent. This solution is called BGP Color-Aware Routing (BGP CAR). This document describes the routing framework and BGP extensions to enable intent-aware routing using the BGP CAR solution. The solution defines two new BGP SAFIs (BGP CAR SAFI and BGP VPN CAR SAFI) for IPv4 and IPv6. It also defines an extensible NLRI model for both SAFIs that allow multiple NLRI types to be defined for different use cases. Each type of NLRI contains key and TLV based non-key fields for efficient encoding of different per-prefix information. This specification defines two NLRI types, Color-Aware Route NLRI and IP Prefix NLRI. It defines non-key TLV types for MPLS label stack, Label Index and SRv6 SIDs. This solution also defines a new Local Color Mapping (LCM) Extended Community.
	Segment Routing Segment Types Extensions for BGP SR Policy
	draft-ietf-idr-bgp-sr-segtypes-ext-08.txt   Date: 20/02/2025   Authors: Ketan Talaulikar, Clarence Filsfils, Stefano Previdi, Paul Mattes, Dhanendra Jain   Working Group: Inter-Domain Routing (idr)	This document specifies the signaling of additional Segment Routing Segment Types for signaling of Segment Routing (SR) Policies in BGP using SR Policy Subsequent Address Family Identifier.
	Datagram PLPMTUD for UDP Options
	draft-ietf-tsvwg-udp-options-dplpmtud-15.txt   Date: 20/02/2025   Authors: Gorry Fairhurst, Tom Jones   Working Group: Transport and Services Working Group (tsvwg)	This document specifies how a UDP Options sender implements Datagram Packetization Layer Path Maximum Transmission Unit Discovery (DPLPMTUD) as a robust method for Path Maximum Transmission Unit discovery. This method uses the UDP Options packetization layer. It allows an application to discover the largest size of datagram that can be sent across a network path. It also provides a way to allow the application to periodically verify the current maximum packet size supported by a path and to update this when required.

19/02/2025

	EAP-based Authentication Service for CoAP
	draft-ietf-ace-wg-coap-eap-15.txt   Date: 19/02/2025   Authors: Rafael Marin-Lopez, Dan Garcia-Carrillo   Working Group: Authentication and Authorization for Constrained Environments (ace)	This document specifies an authentication service that uses the Extensible Authentication Protocol (EAP) transported employing Constrained Application Protocol (CoAP) messages. As such, it defines an EAP lower layer based on CoAP called CoAP-EAP. One of the main goals is to authenticate a CoAP-enabled IoT device (EAP peer) that intends to join a security domain managed by a Controller (EAP authenticator). Secondly, it allows deriving key material to protect CoAP messages exchanged between them based on Object Security for Constrained RESTful Environments (OSCORE), enabling the establishment of a security association between them.

14/02/2025

	Multicast Source Redundancy in EVPN Networks
	draft-ietf-bess-evpn-redundant-mcast-source-15.txt   Date: 14/02/2025   Authors: Jorge Rabadan, Jayant Kotalwar, Senthil Sathappan, Zhaohui Zhang, Wen Lin   Working Group: BGP Enabled ServiceS (bess)	In Ethernet Virtual Private Networks (EVPNs), IP multicast traffic replication and delivery play a crucial role in enabling efficient and scalable layer-2 and layer-3 services. A common deployment scenario involves redundant multicast sources that ensure high availability and resiliency. However, the presence of redundant sources can lead to duplicate IP multicast traffic in the network, causing inefficiencies and increased overhead. This document specifies extensions to the EVPN multicast procedures that allow for the suppression of duplicate IP multicast traffic from redundant sources. The proposed mechanisms enhance EVPN's capability to deliver multicast traffic efficiently while maintaining high availability. These extensions are applicable to various EVPN deployment scenarios and provide guidelines to ensure consistent and predictable behavior across diverse network topologies.

13/02/2025

	IGP Flexible Algorithms: Bandwidth,Delay,Metrics and Constraints
	draft-ietf-lsr-flex-algo-bw-con-22.txt   Date: 13/02/2025   Authors: Shraddha Hegde, William Britto, Rajesh Shetty, Bruno Decraene, Peter Psenak, Tony Li   Working Group: Link State Routing (lsr)	Many networks configure the IGP link metric relative to the link capacity. High bandwidth traffic gets routed as per the link capacity. Flexible algorithms [RFC9350]provide mechanisms to create constraint based paths in an IGP. This draft documents a generic metric type and set of bandwidth related constraints to be used in Flexible Algorithms.
	Shared Brotli Compressed Data Format
	draft-vandevenne-shared-brotli-format-15.txt   Date: 13/02/2025   Authors: Jyrki Alakuijala, Thai Duong, Evgenii Kliuchnikov, Zoltan Szabadka, Lode Vandevenne   Working Group: Web and Internet Transport (wit)	This specification defines a data format for shared brotli compression, which adds support for shared dictionaries, large window and a container format to brotli (RFC 7932). Shared dictionaries and large window support allow significant compression gains compared to regular brotli. This document updates RFC 7932.

12/02/2025

	Additional Parameter sets for HSS/LMS Hash-Based Signatures
	draft-fluhrer-lms-more-parm-sets-19.txt   Date: 12/02/2025   Authors: Scott Fluhrer, Quynh Dang   Working Group: Crypto Forum (cfrg)	This note extends HSS/LMS (RFC 8554) by defining parameter sets by including additional hash functions. These include hash functions that result in signatures with significantly smaller size than the signatures using the current parameter sets, and should have sufficient security. This document is a product of the Crypto Forum Research Group (CFRG) in the IRTF.
	System-defined Configuration
	draft-ietf-netmod-system-config-12.txt   Date: 12/02/2025   Authors: Qiufang Ma, Qin WU, Chong Feng   Working Group: Network Modeling (netmod)	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 system configuration datastore holding 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.
	Topology Independent Fast Reroute using Segment Routing
	draft-ietf-rtgwg-segment-routing-ti-lfa-21.txt   Date: 12/02/2025   Authors: Ahmed Bashandy, Stephane Litkowski, Clarence Filsfils, Pierre Francois, Bruno Decraene, Dan Voyer   Working Group: Routing Area Working Group (rtgwg)	This document presents Topology Independent Loop-free Alternate Fast Reroute (TI-LFA), aimed at providing protection of node and adjacency segments within the Segment Routing (SR) framework. This Fast Reroute (FRR) behavior builds on proven IP Fast Reroute concepts being LFAs, remote LFAs (RLFA), and remote LFAs with directed forwarding (DLFA). It extends these concepts to provide guaranteed coverage in any two-connected networks using a link-state IGP. An important aspect of TI-LFA is the FRR path selection approach establishing protection over the expected post-convergence paths from the point of local repair, reducing the operational need to control the tie-breaks among various FRR options.

06/02/2025

	Internationalized Domain Names in Applications (IDNA): Registry Restrictions and Recommendations
	draft-klensin-idna-rfc5891bis-10.txt   Date: 06/02/2025   Authors: John Klensin, Asmus Freytag   Working Group: Applications and Real-Time Area (art)	The IDNA specifications for internationalized domain names combine rules that determine the labels that are allowed in the DNS without violating the protocol itself and an assignment of responsibility, consistent with earlier specifications, for determining the labels that are allowed in particular zones. Conformance to IDNA by registries and other implementations requires both parts. Experience strongly suggests that the language describing those responsibilities was insufficiently clear to promote safe and interoperable use of the specifications and that more details and discussion of circumstances would have been helpful. Without making any substantive changes to IDNA, this specification updates two of the core IDNA documents (RFCs 5890 and 5891) and the IDNA explanatory document (RFC 5894) to provide that guidance and to correct some technical errors in the descriptions.
	Bootstrapped TLS Authentication with Proof of Knowledge (TLS-POK)
	draft-ietf-emu-bootstrapped-tls-08.txt   Date: 06/02/2025   Authors: Owen Friel, Dan Harkins   Working Group: EAP Method Update (emu)	This document defines a mechanism that enables a bootstrapping device to establish trust and mutually authenticate against a network. Bootstrapping devices have a public private key pair, and this mechanism enables a network server to prove to the device that it knows the public key, and the device to prove to the server that it knows the private key. The mechanism leverages existing DPP and TLS standards and can be used in an EAP exchange.
	Advertising Segment Routing Policies in BGP
	draft-ietf-idr-sr-policy-safi-13.txt   Date: 06/02/2025   Authors: Stefano Previdi, Clarence Filsfils, Ketan Talaulikar, Paul Mattes, Dhanendra Jain   Working Group: Inter-Domain Routing (idr)	A Segment Routing (SR) Policy is an ordered list of segments (also referred to as instructions) that define a source-routed policy. An SR Policy consists of one or more candidate paths, each comprising one or more segment lists. A headend can be provisioned with these candidate paths using various mechanisms, such as CLI, NETCONF, PCEP, or BGP. This document specifies how BGP can be used to distribute SR Policy candidate paths. It introduces a BGP SAFI for advertising a candidate path of an SR Policy and defines sub-TLVs for the Tunnel Encapsulation Attribute to signal information related to these candidate paths. Furthermore, this document updates RFC9012 by extending the Color Extended Community to support additional steering modes over SR Policy.
	Updated YANG Module Revision Handling
	draft-ietf-netmod-yang-module-versioning-13.txt   Date: 06/02/2025   Authors: Robert Wilton, Reshad Rahman, Balazs Lengyel, Joe Clarke, Jason Sterne   Working Group: Network Modeling (netmod)	This document refines the RFC 7950 module update rules. It specifies a new YANG module update procedure that can document when non- backwards-compatible changes have occurred during the evolution of a YANG module. It extends the YANG import statement with a minimum revision suggestion to help document inter-module dependencies. It provides guidelines for managing the lifecycle of YANG modules and individual schema nodes. This document updates RFC 7950, RFC 6020, RFC 8407 and RFC 8525.

03/02/2025

	rLEDBAT: receiver-driven Low Extra Delay Background Transport for TCP
	draft-irtf-iccrg-rledbat-10.txt   Date: 03/02/2025   Authors: Marcelo Bagnulo, Alberto Garcia-Martinez, Gabriel Montenegro, Praveen Balasubramanian   Working Group: Internet Congestion Control (iccrg)	This document specifies rLEDBAT, a set of mechanisms that enable the execution of a less-than-best-effort congestion control algorithm for TCP at the receiver end. This document is a product of the Internet Congestion Control Research Group (ICCRG) of the Internet Research Task Force (IRTF).

---