IETF-Announce List
![[Feed]](feedicon16.png) New RFCs
New and Revived Drafts
- TLS-based EAP types and TLS 1.3 (draft-dekok-emu-tls-eap-types)
By Alan DeKok, 2019-02-11 TXT HTML PDF
Abstract: EAP-TLS [RFC5216] is being updated for TLS 1.3 in [EAPTLS]. Many other EAP [RFC3748] and [RFC5247] types also depend on TLS, such as FAST [RFC4851], TTLS [RFC5281], TEAP [RFC7170], and possibly many vendor specific EAP methods. This document updates those methods in order to use the new key derivation methods available in TLS 1.3. Additional changes necessitated by TLS 1.3 are also discussed.
- IPRAN Grid-Ring IGP convergence problems (draft-hares-lsr-grid-ring-convergence)
By Susan Hares, 2019-02-11 TXT HTML PDF
Abstract: This draft describes problems with IGP convergence time in some IPRAN networks that use a physical topology of grid backbones that connect rings of routers. Part of these IPRAN network topologies exist in data centers with sufficient power and interconnections, but some network equipment sits in remote sites impacted by power loss. In some geographic areas these remote sites may be subject to rolling blackouts. These rolling power blackouts could cause multiple simultaneous node and link failures. In these remote networks with blackouts, it is often critical that the IPRAN phone network re- converge quickly.
- Random Linear Network Coding (RLNC): Background and Practical Considerations (draft-heide-nwcrg-rlnc-background)
By Janus Heide, Shirley Shi, Kerim Fouli, Muriel Medard, Vince Chook, 2019-02-11 TXT HTML PDF
Abstract: This document describes the use of Random Linear Network Coding (RLNC) schemes for reliable data transport. Both block and sliding window RLNC code implementations are described. By providing erasure correction using randomly generated repair symbols, such RLNC-based schemes offer advantages in accommodating varying frame sizes and dynamically changing connections, reducing the need for feedback, and lowering the amount of state information needed at the sender and receiver. The practical considerations' section identifies RLNC- encoded symbol representation as a valuable target for standardization.
- SenML Data Value Content-Format Indication (draft-keranen-core-senml-data-ct)
By Ari Keranen, Carsten Bormann, 2019-02-11 TXT HTML PDF
Abstract: The Sensor Measurement Lists (SenML) media type supports multiple types of values, from numbers to text strings and arbitrary binary data values. In order to simplify processing of the data values this document proposes to specify a new SenML field for indicating the Content-Format of the data.
- Dynamic MultiPath Routing Protocol (draft-pfeifer-rtgwg-dmpr)
By Hagen Pfeifer, Sebastian Widmann, 2019-02-11 TXT HTML PDF
Abstract: Dynamic MultiPath Routing (DMPR) is a loop free path vector routing protocol with built-in support for policy based multipath routing. It has been designed from scratch to work at both low and high bandwidth networks - even with high packet loss. The objective was to keep routing overhead low and ensure a deterministic upper limit. DMPR can be used to manage huge networks with a similar feature set as BGPv4 except for the concept of autonomous systems.
- RPL Mode of Operation extension (draft-rahul-roll-mop-ext)
By Rahul Jadhav, Pascal Thubert, 2019-02-11 TXT HTML PDF
Abstract: RPL allows different mode of operations which allows nodes to have a consensus on the basic primitives that must be supported to join the network. The MOP field in RFC6550 is of 3 bits and is fast depleting. This document extends the MOP field specification and adds a notion of capabilities using which the nodes can further advertise their support for, possibly optional, capabilities.
- TinyMT32 Pseudo Random Number Generator (PRNG) (draft-roca-tsvwg-tinymt32)
By Mutsuo Saito, Makoto Matsumoto, Vincent Roca, Emmanuel Baccelli, 2019-02-11 TXT HTML PDF
Abstract: This document describes the TinyMT32 Pseudo Random Number Generator (PRNG) that produces 32-bit pseudo-random unsigned integers and aims at having a simple-to-use and deterministic solution. This PRNG is a small-sized variant of Mersenne Twister (MT) PRNG, also designed by M. Saito and M. Matsumoto. The main advantage of TinyMT32 over MT is the use of a small internal state, compatible with most target platforms including embedded devices, while keeping a reasonably good randomness.
Updated Drafts
- Remote Procedure Call Encryption By Default (draft-cel-nfsv4-rpc-tls)
By Trond Myklebust, Chuck Lever, 2019-02-11 TXT HTML PDF
Abstract: This document describes a mechanism that enables encryption of in- transit Remote Procedure Call (RPC) transactions with minimal administrative overhead and full interoperation with RPC implementations that do not support this mechanism. This document updates RFC 5531.
- Authentication and Authorization for Constrained Environments (ACE) using the OAuth 2.0 Framework (ACE-OAuth) (draft-ietf-ace-oauth-authz)
By Ludwig Seitz, Goeran Selander, Erik Wahlstroem, Samuel Erdtman, Hannes Tschofenig, 2019-02-11 TXT HTML PDF
Abstract: This specification defines a framework for authentication and authorization in Internet of Things (IoT) environments called ACE- OAuth. The framework is based on a set of building blocks including OAuth 2.0 and CoAP, thus making a well-known and widely used authorization solution suitable for IoT devices. Existing specifications are used where possible, but where the constraints of IoT devices require it, extensions are added and profiles are defined.
- Additional OAuth Parameters for Authorization in Constrained Environments (ACE) (draft-ietf-ace-oauth-params)
By Ludwig Seitz, 2019-02-11 TXT HTML PDF
Abstract: This specification defines new parameters for the OAuth 2.0 token and introspection endpoints when used with the framework for authentication and authorization for constrained environments (ACE). These are used to express the proof-of-possession key the client whishes to use, the proof-of-possession key that the AS has selected, and the key the RS should use to authenticate to the client.
- Integrated Routing and Bridging in EVPN (draft-ietf-bess-evpn-inter-subnet-forwarding)
By Ali Sajassi, Samer Salam, Samir Thoria, John Drake, Jorge Rabadan, 2019-02-11 TXT HTML PDF
Abstract: EVPN provides an extensible and flexible multi-homing VPN solution over an MPLS/IP network for intra-subnet connectivity among Tenant Systems and End Devices that can be physical or virtual. However, there are scenarios for which there is a need for a dynamic and efficient inter-subnet connectivity among these Tenant Systems and End Devices while maintaining the multi-homing capabilities of EVPN. This document describes an Integrated Routing and Bridging (IRB) solution based on EVPN to address such requirements.
- Diameter Overload Rate Control (draft-ietf-dime-doic-rate-control)
By Steve Donovan, Eric Noel, 2019-02-11 TXT HTML PDF
Abstract: This specification documents an extension to the Diameter Overload Indication Conveyance (DOIC) [RFC7683] base solution. This extension adds a new overload control abatement algorithm. This abatement algorithm allows for a DOIC reporting node to specify a maximum rate at which a DOIC reacting node sends Diameter requests to the DOIC reporting node.
- Deprecating ASM for Interdomain Multicast (draft-ietf-mboned-deprecate-interdomain-asm)
By Mikael Abrahamsson, Tim Chown, Leonard Giuliano, Toerless Eckert, 2019-02-11 TXT HTML PDF
Abstract: This document recommends deprecation of the use of Any-Source Multicast (ASM) for interdomain multicast. It recommends the use of Source-Specific Multicast (SSM) for interdomain multicast applications and that hosts and routers in these deployments fully support SSM. The recommendations in this document do not preclude the continued use of ASM within a single organisation or domain and are especially easy to adopt in existing intradomain ASM/PIM-SM deployments.
- RADIUS Attributes for Address plus Port (A+P) based Softwire Mechanisms (draft-ietf-softwire-map-radius)
By Sheng Jiang, Yu Fu, Bing Liu, Peter Deacon, Chongfeng Xie, Tianxiang Li, Mohamed Boucadair, 2019-02-11 TXT HTML PDF
Abstract: IPv4-over-IPv6 transition mechanisms provide IPv4 connectivity services over IPv6 native networks during the IPv4/IPv6 co-existence period. DHCPv6 options have been defined for configuring clients for Lightweight 4over6, Mapping of Address and Port with Encapsulation, and Mapping of Address and Port using Translation unicast softwire mechanisms, and also multicast softwires. However, in many networks, configuration information is stored in an Authentication, Authorization, and Accounting server which utilizes the RADIUS protocol to provide centralized management for users. When a new transition mechanism is developed, new RADIUS attributes need to be defined correspondingly.
- YANG Data Model for Traffic Engineering (TE) Topologies (draft-ietf-teas-yang-te-topo)
By Xufeng Liu, Igor Bryskin, Vishnu Beeram, Tarek Saad, Himanshu Shah, Oscar de Dios, 2019-02-11 TXT HTML PDF
Abstract: This document defines a YANG data model for representing, retrieving and manipulating Traffic Engineering (TE) Topologies. The model serves as a base model that other technology specific TE Topology models can augment.
- Sliding Window Random Linear Code (RLC) Forward Erasure Correction (FEC) Schemes for FECFRAME (draft-ietf-tsvwg-rlc-fec-scheme)
By Vincent Roca, Belkacem Teibi, 2019-02-11 TXT HTML PDF
Abstract: This document describes two fully-specified Forward Erasure Correction (FEC) Schemes for Sliding Window Random Linear Codes (RLC), one for RLC over the Galois Field (A.K.A. Finite Field) GF(2), a second one for RLC over the Galois Field GF(2^^8), each time with the possibility of controlling the code density. They can protect arbitrary media streams along the lines defined by FECFRAME extended to sliding window FEC codes, as defined in [fecframe-ext]. These sliding window FEC codes rely on an encoding window that slides over the source symbols, generating new repair symbols whenever needed. Compared to block FEC codes, these sliding window FEC codes offer key advantages with real-time flows in terms of reduced FEC- related latency while often providing improved packet erasure recovery capabilities.
- Remote Attestation Procedures for Network Security Functions (NSFs) through the I2NSF Security Controller (draft-pastor-i2nsf-nsf-remote-attestation)
By Antonio Pastor, Diego Lopez, Adrian Shaw, 2019-02-11 TXT HTML PDF
Abstract: This document describes the procedures a client can follow to assess the trust on an external NSF platform and its client-defined configuration through the I2NSF Security Controller. The procedure to assess trustworthiness is based on a remote attestation of the platform and the NSFs running on it performed through a Trusted Platform Module (TPM) invoked by the Security Controller.
- A Yang Data Model for IGMP/MLD Proxy (draft-zhao-pim-igmp-mld-proxy-yang)
By Hongji Zhao, Xufeng Liu, Yisong Liu, 2019-02-11 TXT HTML PDF
Abstract: This document defines a YANG data model that can be used to configure and manage Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD) proxy devices. The YANG module in this document conforms to Network Management Datastore Architecture (NMDA).
Expired Drafts
- A Yang Data Model for SAVI Management (draft-an-savi-yang)
By Changqing An, Jiahai Yang, Jianping Wu, Jun Bi, 2018-08-10 TXT HTML PDF
Abstract: This document contains a specification of YANG modules for the management of SAVI (Source Address Validation Improvements) protocol.
- Problem Statement of RoCEv2 Congestion Management (draft-chen-nfsv4-rocev2-cm-problem-statement)
By Fei Chen, Wenhao Sun, 2018-08-10 TXT HTML PDF
Abstract: On IP-routed datacenter networks, RDMA is deployed using RoCEv2 protocol. RoCEv2 specification does not define the congestion management and load balancing methods. RoCEv2 relies on the existing Link-Layer Flow-Control IEEE 802.1Qbb(Priority-based Flow Control, PFC)to provide a lossless network. RoCEv2 Congestion Management(RCM) use ECN(Explicit Congestion Notification, defined in RFC3168) to signal the congestion to the destination and use the congestion notification to reduce the rate of injection and increase the injection rate when the extent of congestion decreases. More and more practice of congestion management for RoCEv2 appear in the industry, such as DCQCN(Data Center Quantized Congestion Notification). There is a demanding for the new RoCE protocol(temporary alias RoCEv3) to provide stronger congestion management and load balancing mechanisms for RDMA deployment in modern datacenter.
- DLEP Traffic Classification Data Item (draft-ietf-manet-dlep-traffic-classification)
By Bow-Nan Cheng, David Wiggins, Lou Berger, 2018-08-10 TXT HTML PDF
Abstract: This document defines a new DLEP protocol Data Item that is used to support traffic classification. Traffic classification information is used to identify traffic flows based on frame/packet content such as destination address. The Data Item is defined in an extensible and reusable fashion. It's use will be mandated in other documents defining specific DLEP extensions. This document aloas introduces DLEP sub data items, and sub data items are defined to support DiffServ and Ethernet traffic classification.
- MPLS Payload Protocol Identifier (draft-xu-mpls-payload-protocol-identifier)
By Xiaohu Xu, Hamid Assarpour, Shaowen Ma, Francois Clad, 2018-08-10 TXT HTML PDF
Abstract: The MPLS label stack has no explicit protocol identifier field to indicate the protocol type of the MPLS payload. This document proposes a mechanism for containing a protocol identifier field within the MPLS packet, which is useful for any new encapsulation header which may need to be encapsulated with an MPLS header.
|
Drafts Sent to IESG
- IP Fragmentation Considered Fragile (draft-ietf-intarea-frag-fragile): Active » Publication Requested
By Ron Bonica, Fred Baker, Geoff Huston, Robert Hinden, Ole Troan, Fernando Gont, 2019-01-30 TXT HTML PDF
Abstract: This document describes IP fragmentation and explains how it reduces the reliability of Internet communication.
IESG Progress
- An Architecture for IPv6 over the TSCH mode of IEEE 802.15.4 (draft-ietf-6tisch-architecture): Publication Requested » AD Evaluation
By Pascal Thubert, 2018-12-17 TXT HTML PDF
Abstract: This document describes a network architecture that provides low- latency, low-jitter and high-reliability packet delivery. It combines a high speed powered backbone and subnetworks using IEEE 802.15.4 time-slotted channel hopping (TSCH) to meet the requirements of LowPower wireless deterministic applications.
- Diameter Overload Rate Control (draft-ietf-dime-doic-rate-control): Approved-announcement to be sent::Revised I-D Needed » ::AD Followup
By Steve Donovan, Eric Noel, 2019-02-11 TXT HTML PDF
Abstract: This specification documents an extension to the Diameter Overload Indication Conveyance (DOIC) [RFC7683] base solution. This extension adds a new overload control abatement algorithm. This abatement algorithm allows for a DOIC reporting node to specify a maximum rate at which a DOIC reacting node sends Diameter requests to the DOIC reporting node.
- On Demand Mobility Management (draft-ietf-dmm-ondemand-mobility): Waiting for Writeup » IESG Evaluation
By Alper Yegin, Danny Moses, Kisuk Kweon, Jinsung Lee, Jungshin Park, Seil Jeon, 2019-02-08 TXT HTML PDF
Abstract: Applications differ with respect to whether they need session continuity and/or IP address reachability. The network providing the same type of service to any mobile host and any application running on the host yields inefficiencies, as described in section 4 of [RFC7333]. This document defines a new concep of enabling applications to influence the network's mobility services (session continuity and/or IP address reachability) on a per-Socket basis, and suggests extensions to the networking stack's API to accomodate this concept.
- Algorithm Implementation Requirements and Usage Guidance for DNSSEC (draft-ietf-dnsop-algorithm-update): Publication Requested » AD Evaluation
By Paul Wouters, Ondrej Sury, 2018-10-23 TXT HTML PDF
Abstract: The DNSSEC protocol makes use of various cryptographic algorithms in order to provide authentication of DNS data and proof of non- existence. To ensure interoperability between DNS resolvers and DNS authoritative servers, it is necessary to specify a set of algorithm implementation requirements and usage guidelines to ensure that there is at least one algorithm that all implementations support. This document defines the current algorithm implementation requirements and usage guidance for DNSSEC. This document obsoletes [RFC6944].
- IMAP4 Extension: Message Preview Generation (draft-ietf-extra-imap-fetch-preview): In Last Call » Waiting for Writeup
By Michael Slusarz, 2019-01-22 TXT HTML PDF
Abstract: This document specifies an IMAP protocol extension which allows a client to request that a server provide an abbreviated representation of a message that can be used by a client to provide a useful contextual preview of the message contents.
- Generic UDP Encapsulation (draft-ietf-intarea-gue): Publication Requested » AD Evaluation
By Tom Herbert, Lucy Yong, Osama Zia, 2018-08-31 TXT HTML PDF
Abstract: This specification describes Generic UDP Encapsulation (GUE), which is a scheme for using UDP to encapsulate packets of different IP protocols for transport across layer 3 networks. By encapsulating packets in UDP, specialized capabilities in networking hardware for efficient handling of UDP packets can be leveraged. GUE specifies basic encapsulation methods upon which higher level constructs, such as tunnels and overlay networks for network virtualization, can be constructed. GUE is extensible by allowing optional data fields as part of the encapsulation, and is generic in that it can encapsulate packets of various IP protocols.
- Transmission of IPv6 Packets over IEEE 802.11 Networks operating in mode Outside the Context of a Basic Service Set (IPv6-over-80211-OCB) (draft-ietf-ipwave-ipv6-over-80211ocb): Publication Requested » AD Evaluation
By Alexandre Petrescu, Nabil Benamar, Jerome Haerri, Jong-Hyouk Lee, Thierry Ernst, Thierry Ernst, 2018-12-18 TXT HTML PDF
Abstract: In order to transmit IPv6 packets on IEEE 802.11 networks running outside the context of a basic service set (OCB, earlier "802.11p") there is a need to define a few parameters such as the supported Maximum Transmission Unit size on the 802.11-OCB link, the header format preceding the IPv6 header, the Type value within it, and others. This document describes these parameters for IPv6 and IEEE 802.11-OCB networks; it portrays the layering of IPv6 on 802.11-OCB similarly to other known 802.11 and Ethernet layers - by using an Ethernet Adaptation Layer.
- SDP: Session Description Protocol (draft-ietf-mmusic-rfc4566bis): AD Evaluation » ::Revised I-D Needed
By Ali Begen, Paul Kyzivat, Colin Perkins, Mark Handley, 2018-12-18 TXT HTML PDF
Abstract: This memo defines the Session Description Protocol (SDP). SDP is intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. This document obsoletes RFC 4566.
- Test Cases for Evaluating RMCAT Proposals (draft-ietf-rmcat-eval-test): In Last Call » Waiting for Writeup
By Zaheduzzaman Sarker, Varun Singh, Xiaoqing Zhu, Michael Ramalho, 2019-02-08 TXT HTML PDF
Abstract: The Real-time Transport Protocol (RTP) is used to transmit media in multimedia telephony applications. These applications are typically required to implement congestion control. This document describes the test cases to be used in the performance evaluation of such congestion control algorithms in a controlled environment.
Drafts Sent to RFC Editor
- Signaling RSVP-TE tunnels on a shared MPLS forwarding plane (draft-ietf-mpls-rsvp-shared-labels): IESG Evaluation::AD Followup » RFC Ed Queue
By Harish Sitaraman, Vishnu Beeram, Tejal Parikh, Tarek Saad, 2019-01-31 TXT HTML PDF
Abstract: As the scale of MPLS RSVP-TE networks has grown, so the number of Label Switched Paths (LSPs) supported by individual network elements has increased. Various implementation recommendations have been proposed to manage the resulting increase in control plane state.
- Message Authentication Code for the Network Time Protocol (draft-ietf-ntp-mac): Approved-announcement to be sent::Point Raised - writeup needed » RFC Ed Queue
By Aanchal Malhotra, Sharon Goldberg, 2019-01-04 TXT HTML PDF
Abstract: RFC 5905 states that Network Time Protocol (NTP) packets should be authenticated by appending the NTP data to a 128-bit key, and hashing the result with MD5 to obtain a 128-bit tag. This document deprecates MD5-based authentication, which is considered to be too weak, and recommends the use of AES-CMAC as in RFC 4493 as a replacement.
- Requirements for IPv6 Customer Edge Routers to Support IPv4 Connectivity as-a-Service (draft-ietf-v6ops-transition-ipv4aas): IESG Evaluation::AD Followup » RFC Ed Queue
By Jordi Palet, Hans Liu, Masanobu Kawashima, 2019-01-28 TXT HTML PDF
Abstract: This document specifies the IPv4 service continuity requirements for an IPv6 Customer Edge (CE) router, either provided by the service provider or by vendors who sell through the retail market.
Other Status Changes
- draft-gredler-idr-bgp-ls-segment-routing-extension: Expired » Replaced by draft-gredler-idr-bgp-ls-segment-routing-ext
No title available; expired document? TXT HTML PDF
- RPL Mode of Operation extension (draft-rahul-mop-ext): Active » Replaced by draft-rahul-roll-mop-ext
By Rahul Jadhav, Pascal Thubert, 2019-02-07 TXT HTML PDF
Abstract: RPL allows different mode of operations which allows nodes to have a consensus on the basic primitives that must be supported to join the network. The MOP field in RFC6550 is of 3 bits and is fast depleting. This document extends the MOP field specification and adds a notion of capabilities using which the nodes can further advertise their support for, possibly optional, capabilities.
RFC Editor Status Changes
- Update to the Process for Selection of Trustees for the IETF Trust (draft-ietf-iasa2-trust-update): » AUTH48
By Jari Arkko, Ted Hardie, 2019-02-04 TXT HTML PDF
Abstract: This memo updates the process for selection of trustees for the IETF Trust. Previously, the Internet Administrative Oversight Committee (IAOC) members also acted as trustees, but the IAOC has been eliminated as part of an update of the structure of the Internet Administrative Support Activity (IASA). This memo specifies that the trustees shall be selected separately.
- Generic YANG Data Model for Connection Oriented Operations, Administration, and Maintenance(OAM) protocols (draft-ietf-lime-yang-connection-oriented-oam-model): » AUTH48
By Deepak Kumar, Qin Wu, Zitao Wang, 2018-02-25 TXT HTML PDF
Abstract: This document presents a base YANG Data model for connection-oriented Operations, Administration, and Maintenance(OAM) protocols. It provides a technology-independent abstraction of key OAM constructs for such protocols. The model presented here can be extended to include technology specific details. This guarantees uniformity in the management of OAM protocols and provides support for nested OAM workflows (i.e., performing OAM functions at different levels through a unified interface).
- Retrieval Methods YANG Data Model for the Management of Operations, Administration, and Maintenance (OAM) Protocols that use Connectionless Communications (draft-ietf-lime-yang-connectionless-oam-methods): » AUTH48
By Deepak Kumar, Zitao Wang, Qin Wu, Reshad Rahman, Srihari Raghavan, 2017-11-12 TXT HTML PDF
Abstract: This document presents a retrieval method YANG Data model for connectionless OAM protocols. It provides technology-independent RPC operations for OAM protocols that use connectionless communication. The retrieval methods model herein presented can be extended to include technology specific details. There are two key benefits of this approach: First, it leads to uniformity between OAM protocols. And second, it support both nested OAM workflows (i.e., performing OAM functions at different or same levels through a unified interface) as well as interactive OAM workflows (i.e., performing OAM functions at same levels through a unified interface).
IPR Disclosures
IESG/IAB/IAOC/Trust Minutes
Liaison Statements
Classified Ads
|
WGs marked with an 
