IETF-Announce List
New RFCs
New and Revived Drafts
- Client Key SASL mechanism (draft-cridland-kitten-clientkey)
By Dave Cridland, 2018-01-08 TXT HTML PDF
Abstract: This document proposes a SASL mechanism which might be used to authenticate specific clients on devices owned by a user.
- NFS version 4.0 Trunking Update (draft-ietf-nfsv4-mv0-trunking-update)
By Chuck Lever, David Noveck, 2018-01-08 TXT HTML PDF
Abstract: The location-related attribute in NFS version 4.0, fs_locations, is used to support the migration and replication of server file systems. This document describes an additional use for this attribute as a mechanism for an NFS version 4.0 client to discover an NFS version 4.0 server's trunking capabilities. The interaction of trunking with migration and replication is also clarified. This document updates RFC 7530.
- Dynamic Flooding for IS-IS (draft-li-dynamic-flooding-isis)
By Tony Li, 2018-01-07 TXT HTML PDF
Abstract: Routing with link state protocols in dense network topologies can result in sub-optimal convergence times due to the overhead associated with flooding. This can be addressed by decreasing the flooding topology so that it is less dense.
- Registry Maintenance Notifications for the Extensible Provisioning Protocol (EPP) (draft-sattler-epp-registry-maintenance)
By Tobias Sattler, 2018-01-08 TXT HTML PDF
Abstract: This document describes an Extensible Provision Protocol (EPP) mapping for the Registry Maintenance Notifications used when Domain Name Registries will conduct a maintenance, and for retrieving these informations.
- YANG data model for Flexi-Grid Optical Networks (draft-vergara-ccamp-flexigrid-yang)
By Universidad de Madrid, Daniel Perdices, Victor Lopezalvarez, Oscar de Dios, Daniel King, Young Lee, Gabriele Galimberti, 2018-01-08 TXT HTML PDF
Abstract: This document defines a YANG model for managing flexi-grid optical Networks. The model described in this document defines a flexi-grid traffic engineering database. A complementary module is referenced to detail the flexi-grid media channels.
Updated Drafts
- RIB YANG Data Model (draft-acee-rtgwg-yang-rib-extend)
By Acee Lindem, Yingzhen Qu, 2018-01-08 TXT HTML PDF
Abstract: The Routing Information Base (RIB) is a list of routes and their corresponding administrative data and operational state.
- Diameter Group Signaling (draft-ietf-dime-group-signaling)
By Mark Jones, Marco Liebsch, Lionel Morand, 2018-01-08 TXT HTML PDF
Abstract: In large network deployments, a single Diameter node can support over a million concurrent Diameter sessions. Recent use cases have revealed the need for Diameter nodes to apply the same operation to a large group of Diameter sessions concurrently. The Diameter base protocol commands operate on a single session so these use cases could result in many thousands of command exchanges to enforce the same operation on each session in the group. In order to reduce signaling, it would be desirable to enable bulk operations on all (or part of) the sessions managed by a Diameter node using a single or a few command exchanges. This document specifies the Diameter protocol extensions to achieve this signaling optimization.
- RTP Payload Format for VC-2 HQ Profile Video (draft-ietf-payload-rtp-vc2hq)
By James Weaver, 2018-01-08 TXT HTML PDF
Abstract: This memo describes an RTP Payload format for the High Quality (HQ) profile of SMPTE Standard ST 2042-1 known as VC-2. This document describes the transport of HQ Profile VC-2 in RTP packets and has applications for low-complexity, high-bandwidth streaming of both lossless and lossy compressed video.
- Negotiating Human Language in Real-Time Communications (draft-ietf-slim-negotiating-human-language)
By Randall Gellens, 2018-01-08 TXT HTML PDF
Abstract: Users have various human (natural) language needs, abilities, and preferences regarding spoken, written, and signed languages. This document adds new SDP media-level attributes so that when establishing interactive communication sessions ("calls"), it is possible to negotiate (communicate and match) the caller's language and media needs with the capabilities of the called party. This is especially important with emergency calls, where a call can be handled by a call taker capable of communicating with the user, or a translator or relay operator can be bridged into the call during setup, but this applies to non-emergency calls as well (as an example, when calling a company call center).
- Token Binding over HTTP (draft-ietf-tokbind-https)
By Andrey Popov, Magnus Nystrom, Dirk Balfanz, Adam Langley, Nick Harper, Jeff Hodges, 2018-01-07 TXT HTML PDF
Abstract: This document describes a collection of mechanisms that allow HTTP servers to cryptographically bind security tokens (such as cookies and OAuth tokens) to TLS connections.
- A Yang Data Model for WSON Tunnel (draft-lee-ccamp-wson-tunnel-model)
By Young Lee, Dhruv Dhody, Victor Lopezalvarez, Daniel King, Bin-Yeong Yoon, Ricard Vilata, 2018-01-08 TXT HTML PDF
Abstract: This document provides a YANG data model for WSON TE tunnel.
- The SM4 Blockcipher Algorithm And Its Modes Of Operations (draft-ribose-cfrg-sm4)
By Ronald Tse, Wai Wong, 2018-01-07 TXT HTML PDF
Abstract: This document describes the SM4 symmetric blockcipher algorithm published as GB/T 32907-2016 by the State Cryptography Administration of China (SCA).
- The SM3 Cryptographic Hash Function (draft-sca-cfrg-sm3)
By Sean Shen, XiaoDong Lee, Ronald Tse, Wai Wong, Paul Yang, 2018-01-07 TXT HTML PDF
Abstract: This document describes the SM3 cryptographic hash algorithm published as GB/T 32905-2016 by the State Cryptography Administration of China (SCA).
Expired Drafts
|
Drafts Sent to IESG
- WebRTC Forward Error Correction Requirements (draft-ietf-rtcweb-fec): Active » Publication Requested
By Justin Uberti, 2017-12-10 TXT HTML PDF
Abstract: This document provides information and requirements for how Forward Error Correction (FEC) should be used by WebRTC implementations.
IESG Progress
- Token Binding over HTTP (draft-ietf-tokbind-https): AD Evaluation::Revised I-D Needed » ::AD Followup
By Andrey Popov, Magnus Nystrom, Dirk Balfanz, Adam Langley, Nick Harper, Jeff Hodges, 2018-01-07 TXT HTML PDF
Abstract: This document describes a collection of mechanisms that allow HTTP servers to cryptographically bind security tokens (such as cookies and OAuth tokens) to TLS connections.
- TRILL Support of Point to Multipoint BFD (draft-ietf-trill-p2mp-bfd): In Last Call » Waiting for Writeup
By Mingui Zhang, Juniper Networks, Vengada Govindan, 2017-12-26 TXT HTML PDF
Abstract: Point to multipoint (P2MP) BFD is designed to verify multipoint connectivity. This document specifies the support of P2MP BFD in TRILL. Similar to TRILL point-to-point BFD, BFD Control packets in TRILL P2MP BFD are transmitted using RBridge Channel message. This document updates RFC 7175 and RFC 7177.
Drafts Sent to RFC Editor
Other Status Changes
- YANG Data Model for ARP (draft-ding-arp-yang-model): Active » Replaced by draft-ding-netmod-arp-yang-model
By ding xiaojian, Feng Zheng, 2017-10-26 TXT HTML PDF
Abstract: This document defines a YANG data model to describe Address Resolution Protocol (ARP) configurations. It is intended this model be used by service providers who manipulate devices from different vendors in a standard way.
- JSON response to provide Registry Maintenance Notifications within an Extensible Provisioning Protocol (EPP) poll response (draft-sattler-epp-poll-maintenance-response): Active » Replaced by draft-sattler-epp-registry-maintenance
By Tobias Sattler, 2017-12-04 TXT HTML PDF
Abstract: This document describes the JSON response which can be included in an Extensible Provisioning Protocol (EPP) <poll> response to provide Domain Name Registry Maintenance Notifications to Domain Name Registrars.
RFC Editor Status Changes
- Usage and (D)TLS Profiles for DNS-over-(D)TLS (draft-ietf-dprive-dtls-and-tls-profiles): » AUTH48
By Sara Dickinson, Daniel Gillmor, Tirumaleswar Reddy, 2017-09-11 TXT HTML PDF
Abstract: This document discusses Usage Profiles, based on one or more authentication mechanisms, which can be used for DNS over Transport Layer Security (TLS) or Datagram TLS (DTLS). These profiles can increase the privacy of DNS transactions compared to using only clear text DNS. This document also specifies new authentication mechanisms - it describes several ways a DNS client can use an authentication domain name to authenticate a (D)TLS connection to a DNS server. Additionally, it defines (D)TLS protocol profiles for DNS clients and servers implementing DNS-over-(D)TLS. This document updates RFC 7858.
- CUBIC for Fast Long-Distance Networks (draft-ietf-tcpm-cubic): » AUTH48
By Injong Rhee, Lisong Xu, Sangtae Ha, Alexander Zimmermann, Lars Eggert, Richard Scheffenegger, 2017-11-13 TXT HTML PDF
Abstract: CUBIC is an extension to the current TCP standards. It differs from the current TCP standards only in the congestion control algorithm in the sender side. In particular, it uses a cubic function instead of a linear window increase function of the current TCP standards to improve scalability and stability under fast and long distance networks. CUBIC and its predecessor algorithm have been adopted as default by Linux and have been used for many years. This document provides a specification of CUBIC to enable third party implementations and to solicit the community feedback through experimentation on the performance of CUBIC.
- Relaxing Restrictions on Explicit Congestion Notification (ECN) Experimentation (draft-ietf-tsvwg-ecn-experimentation): » AUTH48
By David Black, 2017-11-13 TXT HTML PDF
Abstract: This memo updates RFC 3168, which specifies Explicit Congestion Notification (ECN) as an alternative to packet drops for indicating network congestion to endpoints. It relaxes restrictions in RFC 3168 that hinder experimentation towards benefits beyond just removal of loss. This memo summarizes the anticipated areas of experimentation and updates RFC 3168 to enable experimentation in these areas. An Experimental RFC in the IETF document stream is required to take advantage of any of these enabling updates. In addition, this memo makes related updates to the ECN specifications for RTP in RFC 6679 and for DCCP in RFC 4341, RFC 4342 and RFC 5622. This memo also records the conclusion of the ECN nonce experiment in RFC 3540, and provides the rationale for reclassification of RFC 3540 as Historic; this reclassification enables new experimental use of the ECT(1) codepoint.
IPR Disclosures
IESG/IAB/IAOC/Trust Minutes
Liaison Statements
Classified Ads
|