IETF-Announce List
![[Feed]](feedicon16.png) New RFCs
New and Revived Drafts
Updated Drafts
- Scalability Considerations for Network Resource Partition (draft-dong-teas-nrp-scalability)
By Jie Dong, Zhenbin Li, Liyan Gong, Guangming Yang, Jim Guichard, Gyan Mishra, Fengwei Qin, Tarek Saad, Vishnu Beeram, 2022-05-16 TXT HTML PDF
Abstract: The IETF Network Slice service aims to meet the connectivity demands of a network slice customer with specific Service Level Objectives (SLOs) and Service Level Expectations (SLEs) over a common underlay network. A Network Resource Partition (NRP) is a set of network resources that are allocated from the underlay network to carry a specific set of network traffic and meet the required SLOs and SLEs. One or multiple IETF Network Slice services can be mapped to one NRP.
- DRIP Entity Tag (DET) for Unmanned Aircraft System Remote ID (UAS RID) (draft-ietf-drip-rid)
By Robert Moskowitz, Stuart Card, Adam Wiethuechter, Andrei Gurtov, 2022-05-16 TXT HTML PDF
Abstract: This document describes the use of Hierarchical Host Identity Tags (HHITs) as self-asserting IPv6 addresses and thereby a trustable identifier for use as the Unmanned Aircraft System Remote Identification and tracking (UAS RID).
- Data Model for Static Context Header Compression (SCHC) (draft-ietf-lpwan-schc-yang-data-model)
By Ana Minaburo, Laurent Toutain, 2022-05-16 TXT HTML PDF
Abstract: This document describes a YANG data model for the SCHC (Static Context Header Compression) compression and fragmentation rules.
- IGP Flexible Algorithms (Flex-Algorithm) In IP Networks (draft-ietf-lsr-ip-flexalgo)
By William Britto, Shraddha Hegde, Parag Kaneriya, Rejesh Shetty, Ron Bonica, Peter Psenak, 2022-05-16 TXT HTML PDF
Abstract: An IGP Flexible Algorithm (Flex-Algorithm) allows IGPs to compute constraint-based paths. The base IGP Flex-Algorithm specification describes how it is used with Segment Routing (SR) data planes - SR MPLS and SRv6.
- Area Proxy for IS-IS (draft-ietf-lsr-isis-area-proxy)
By Tony Li, Sarah Chen, Vivek Ilangovan, Gyan Mishra, 2022-05-16 TXT HTML PDF
Abstract: Link state routing protocols have hierarchical abstraction already built into them. However, when lower levels are used for transit, they must expose their internal topologies to each other, leading to scale issues.
- JWK Thumbprint URI (draft-ietf-oauth-jwk-thumbprint-uri)
By Michael Jones, Kristina Yasuda, 2022-05-16 TXT HTML PDF
Abstract: This specification registers a kind of URI that represents a JSON Web Key (JWK) Thumbprint value. JWK Thumbprints are defined in RFC 7638. This enables JWK Thumbprints to be used, for instance, as key identifiers in contexts requiring URIs.
- A Network YANG Model for Service Attachment Points (SAPs) (draft-ietf-opsawg-sap)
By Mohamed Boucadair, Oscar de Dios, samier barguil, Qin WU, Victor Lopez, 2022-05-15 TXT HTML PDF
Abstract: This document defines a YANG data model for representing an abstract view of the provider network topology that contains the points from which its services can be attached (e.g., basic connectivity, VPN, network slices). Also, the model can be used to retrieve the points where the services are actually being delivered to customers (including peer networks).
- Updates to the TLS Transport Model for SNMP (draft-ietf-opsawg-tlstm-update)
By Kenneth Vaughn, 2022-05-16 TXT HTML PDF
Abstract: This document updates the TLS Transport Model (TLSTM), as defined in RFC 6353, to reflect changes necessary to support Transport Layer Security Version 1.3 (TLS 1.3) and Datagram Transport Layer Security Version 1.3 (DTLS 1.3), which are jointly known as "(D)TLS 1.3". This document is compatible with (D)TLS 1.2 and is intended to be compatible with future versions of SNMP and (D)TLS.
- Intent Classification (draft-irtf-nmrg-ibn-intent-classification)
By Chen Li, Olga Havel, Adriana Olariu, Pedro Martinez-Julia, Jeferson Nobre, Diego Lopez, 2022-05-16 TXT HTML PDF
Abstract: Intent is an abstract, high-level policy used to operate the network. Intent-based management system includes an interface for users to input requests and an engine to translate the intents into the network configuration and manage their life-cycle.
- Signature Validation Token (draft-santesson-svt)
By Stefan Santesson, Russ Housley, 2022-05-16 TXT HTML PDF
Abstract: Electronic signatures have a limited lifespan with respect to the time period that they can be validated and determined to be authentic. The Signature Validation Token (SVT) defined in this specification provides evidence that asserts the validity of an electronic signature. The SVT is provided by a trusted authority, which asserts that a particular signature was successfully validated according to defined procedures at a certain time. Any future validation of that electronic signature can be satisfied by validating the SVT without any need to also validate the original electronic signature or the associated digital certificates. SVT supports electronic signatures in CMS, XML, PDF and JSON documents.
- Unicast Use of the Lowest Address in an IPv4 Subnet (draft-schoen-intarea-unicast-lowest-address)
By Seth Schoen, John Gilmore, David Taht, Michael Karels, 2022-05-16 TXT HTML PDF
Abstract: With ever-increasing pressure to conserve IP address space on the Internet, it makes sense to consider where relatively minor changes can be made to fielded practice to improve numbering efficiency. One such change, proposed by this document, is to increase the number of unicast addresses in each existing subnet, by redefining the use of the lowest-numbered (zeroth) host address in each IPv4 subnet as an ordinary unicast host identifier, instead of as a duplicate segment- directed broadcast address.
- Authentic Chained Data Containers (ACDC) (draft-ssmith-acdc)
By Samuel Smith, 2022-05-16 TXT HTML PDF
Abstract: An authentic chained data container (ACDC) [ACDC_ID][ACDC_WP][VCEnh] is an IETF [IETF] internet draft focused specification being incubated at the ToIP (Trust over IP) foundation [TOIP][ACDC_TF]. An ACDC is a variant of the W3C Verifiable Credential (VC) specification [W3C_VC]. The W3C VC specification depends on the W3C DID (Decentralized IDentifier) specification [W3C_DID]. A major use case for the ACDC specification is to provide GLEIF vLEIs (verifiable Legal Entity Identifiers) [vLEI][GLEIF_vLEI][GLEIF_KERI]. GLEIF is the Global Legal Entity Identifier Foundation [GLEIF]. ACDCs are dependent on a suite of related IETF focused standards associated with the KERI (Key Event Receipt Infrastructure) [KERI_ID][KERI] specification. These include CESR [CESR_ID], SAID [SAID_ID], PTEL [PTEL_ID], CESR-Proof [Proof_ID], IPEX [IPEX_ID], did:keri [DIDK_ID], and OOBI [OOBI_ID]. Some of the major distinguishing features of ACDCs include normative support for chaining, use of composable JSON Schema [JSch][JSchCp], multiple serialization formats, namely, JSON [JSON][RFC4627], CBOR [CBOR][RFC8949], MGPK [MGPK], and CESR [CESR_ID], support for Ricardian contracts [RC], support for chain- link confidentiality [CLC], a well defined security model derived from KERI [KERI][KERI_ID], _compact_ formats for resource constrained applications, simple _partial disclosure_ mechanisms and simple _selective disclosure_ mechanisms. ACDCs provision data using a synergy of provenance, protection, and performance.
- YANG Data Model for FlexE Management (draft-wang-ccamp-flexe-yang-cm)
By Minxue Wang, Liuyan Han, Fan Yang, Xiaobing NIU, Luis Contreras, Xufeng Liu, 2022-05-16 TXT HTML PDF
Abstract: This document defines a service provider targeted YANG data model for the configuration and management of a Flex Ethernet (FlexE) network, including FlexE groups. It also supports the configuration of each FlexE client as an interface. The YANG module in this document conforms to the Network Management Datastore Architecture (NMDA).
- Advertisement of Stub Link Attributes (draft-wang-lsr-stub-link-attributes)
By Aijun Wang, Zhibo Hu, Acee Lindem, Gyan Mishra, Jinsong Sun, 2022-05-16 TXT HTML PDF
Abstract: This document describes the mechanism that can be used to advertise the stub link attributes within the ISIS or OSPF domain.
Expired Drafts
- Preferred Path Routing (PPR) in IS-IS (draft-chunduri-lsr-isis-preferred-path-routing)
By Uma Chunduri, Richard Li, Russ White, Luis Contreras, Jeff Tantsura, Yingzhen Qu, 2021-11-12 TXT HTML PDF
Abstract: This document specifies a Preferred Path Routing (PPR), a routing protocol mechanism to simplify the path description using IS-IS protocol. PPR builds on existing encapsulation to add the path identity to the packet and supports further extensions along the preferred paths. PPR aims to provide path steering, services and support further extensions along the paths. Preferred path routing is achieved through the addition of path descriptions to the IS-IS advertised prefixes, and mapping those to a PPR data-plane identifier.
- PIM Light (draft-hb-pim-light)
By Hooman Bidgoli, Stig Venaas, Mankamana Mishra, Zhaohui Zhang, Mike McBride, 2021-11-12 TXT HTML PDF
Abstract: This document specifies a new Protocol Independent Multicast interface which does not need PIM Hello to accept PIM Join/Prunes or PIM Asserts.
- M-LDP Signaling Through BIER Core (draft-ietf-bier-mldp-signaling-over-bier)
By Hooman Bidgoli, Jayant Kotalwar, IJsbrand Wijnands, Mankamana Mishra, Zhaohui Zhang, Eddie Leyton, 2021-11-12 TXT HTML PDF
Abstract: Consider an end to end Multipoint LDP (mLDP) network, where it is desirable to deploy BIER in portion of this network. It might be desirable to deploy BIER with minimum disruption to the mLDP network or redesign of the network.
- Use of GOST 2012 Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC (draft-ietf-dnsop-rfc5933-bis)
By Dmitry Belyavsky, Vasily Dolmatov, 2021-11-12 TXT HTML PDF
Abstract: This document describes how to produce digital signatures and hash functions using the GOST R 34.10-2012 and GOST R 34.11-2012 algorithms for DNSKEY, RRSIG, and DS resource records, for use in the Domain Name System Security Extensions (DNSSEC).
- Multiple SIP Reason Header Field Values (draft-sparks-sipcore-multiple-reasons)
By Robert Sparks, 2021-11-12 TXT HTML PDF
Abstract: The SIP Reason Header Field as defined in RFC 3326 allows only one Reason value per protocol value. Practice shows it is useful to allow multiple values with the same protocol value. This update to RFC 3326 allows multiple values for an indicated registered protocol when that protocol defines what the presence of multiple values means.
|
Drafts Sent to IESG
- Segment Routing IPv6 for Mobile User Plane (draft-ietf-dmm-srv6-mobile-uplane): Active » Publication Requested
By Satoru Matsushima, Clarence Filsfils, Miya Kohno, Pablo Camarillo, Dan Voyer, Charles Perkins, 2022-05-09 TXT HTML PDF
Abstract: This document specifies the applicability of SRv6 (Segment Routing IPv6) to the user-plane of mobile networks. The network programming nature of SRv6 accomplishes mobile user-plane functions in a simple manner. The statelessness of SRv6 and its ability to control both service layer path and underlying transport can be beneficial to the mobile user-plane, providing flexibility, end-to-end network slicing, and SLA control for various applications.
- IGP Flexible Algorithms (Flex-Algorithm) In IP Networks (draft-ietf-lsr-ip-flexalgo): Active » Publication Requested
By William Britto, Shraddha Hegde, Parag Kaneriya, Rejesh Shetty, Ron Bonica, Peter Psenak, 2022-05-16 TXT HTML PDF
Abstract: An IGP Flexible Algorithm (Flex-Algorithm) allows IGPs to compute constraint-based paths. The base IGP Flex-Algorithm specification describes how it is used with Segment Routing (SR) data planes - SR MPLS and SRv6.
- Use of Internationalized Email Addresses in the Extensible Provisioning Protocol (EPP) (draft-ietf-regext-epp-eai): Active » Publication Requested
By Dmitry Belyavsky, James Gould, 2022-04-04 TXT HTML PDF
Abstract: This document describes an EPP extension that permits usage of Internationalized Email Addresses in the EPP protocol and specifies the terms when it can be used by EPP clients and servers. The Extensible Provisioning Protocol (EPP), being developed before appearing the standards for Internationalized Email Addresses (EAI), does not support such email addresses.
IESG Progress
- Binary Representation of HTTP Messages (draft-ietf-httpbis-binary-message): Publication Requested » AD Evaluation
By Martin Thomson, Christopher Wood, 2022-05-09 TXT HTML PDF
Abstract: This document defines a binary format for representing HTTP messages.
- JWK Thumbprint URI (draft-ietf-oauth-jwk-thumbprint-uri): Waiting for Writeup::Revised I-D Needed » IESG Evaluation
By Michael Jones, Kristina Yasuda, 2022-05-16 TXT HTML PDF
Abstract: This specification registers a kind of URI that represents a JSON Web Key (JWK) Thumbprint value. JWK Thumbprints are defined in RFC 7638. This enables JWK Thumbprints to be used, for instance, as key identifiers in contexts requiring URIs.
- Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) (draft-ietf-uta-rfc7525bis): AD Evaluation » In Last Call
By Yaron Sheffer, Peter Saint-Andre, Thomas Fossati, 2022-03-24 TXT HTML PDF
Abstract: Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) are widely used to protect data exchanged over application protocols such as HTTP, SMTP, IMAP, POP, SIP, and XMPP. Over the years, the industry has witnessed several serious attacks on TLS and DTLS, including attacks on the most commonly used cipher suites and their modes of operation. This document provides recommendations for improving the security of deployed services that use TLS and DTLS. The recommendations are applicable to the majority of use cases.
Drafts Sent to RFC Editor
- I2NSF Capability YANG Data Model (draft-ietf-i2nsf-capability-data-model): Approved-announcement to be sent::AD Followup » RFC Ed Queue
By Susan Hares, Jaehoon Jeong, Jinyong Kim, Robert Moskowitz, Qiushi Lin, 2022-05-14 TXT HTML PDF
Abstract: This document defines an information model and the corresponding YANG data model for the capabilities of various Network Security Functions (NSFs) in the Interface to Network Security Functions (I2NSF) framework to centrally manage the capabilities of the various NSFs.
- I2NSF Network Security Function-Facing Interface YANG Data Model (draft-ietf-i2nsf-nsf-facing-interface-dm): Approved-announcement to be sent::AD Followup » RFC Ed Queue
By Jinyong Kim, Jaehoon Jeong, J., PARK, Susan Hares, Qiushi Lin, 2022-05-14 TXT HTML PDF
Abstract: This document defines a YANG data model for configuring security policy rules on Network Security Functions (NSF) in the Interface to Network Security Functions (I2NSF) framework. The YANG data model in this document is for the NSF-Facing Interface between a Security Controller and NSFs in the I2NSF framework. It is built on the basis of the YANG data model in the I2NSF Capability YANG Data Model document for the I2NSF framework.
Other Status Changes
RFC Editor Status Changes
IPR Disclosures
IESG/IAB/IAOC/Trust Minutes
Liaison Statements
Classified Ads
|
WGs marked with an 
