IETF-Announce List
![[Feed]](feedicon16.png) New RFCs
New and Revived Drafts
- Eligibility for the 2020-2021 Nominating Committee (draft-iesg-nomcom-eligibility-2020)
By Barry Leiba, 2020-04-02 TXT HTML PDF
Abstract: The 2020-2021 Nominating Committee (NomCom) needs to be formed between IETF 107 and IETF 108, and the issue of eligibility of who can serve on that NomCom needs clarification. This document provides a one-time interpretation of the eligibility rules that is required for the exceptional situation of the cancellation of the in-person IETF 107 meeting. This document only affects the seating of the 2020-2021 NomCom, and does not set a precedent for the future.
- Reflexive Forwarding for CCNx and NDN Protocols (draft-oran-icnrg-reflexive-forwarding)
By David Oran, Dirk Kutscher, 2020-04-02 TXT HTML PDF
Abstract: Current Information-Centric Networking protocols such as CCNx and NDN have a wide range of useful applications in content retrieval and other scenarios that depend only on a robust two-way exchange in the form of a request and response (represented by an _Interest-Data exchange_ in the case of the two protocols noted above). A number of important applications however, require placing large amounts of data in the Interest message, and/or more than one two-way handshake. While these can be accomplished using independent Interest-Data exchanges by reversing the roles of consumer and producer, such approaches can be both clumsy for applications and problematic from a state management, congestion control, or security standpoint. This specification proposes a _Reflexive Forwarding_ extension to the CCNx and NDN protocol architectures that eliminates the problems inherent in using independent Interest-Data exchanges for such applications. It updates RFC8569 and RFC8609.
- The Universal IPv6 Configuration Option (experiment) (draft-troan-6man-universal-ra-option)
By Ole Troan, 2020-04-02 TXT HTML PDF
Abstract: One of the original intentions for the IPv6 host configuration, was to configure the network-layer parameters only with IPv6 ND, and use service discovery for other configuration information. Unfortunately that hasn't panned out quite as planned, and we are in a situation where all kinds of configuration options are added to RAs and DHCP. This document proposes a new universal option for RA and DHCP in a self-describing data format, with the list of elements maintained in an IANA registry, with greatly relaxed rules for registration.
Updated Drafts
- DNS-over-HTTPS and DNS-over-TLS Server Discovery and Deployment Considerations for Home Networks (draft-btw-add-home)
By Mohamed Boucadair, Tirumaleswar Reddy.K, Dan Wing, Neil Cook, 2020-04-02 TXT HTML PDF
Abstract: This document discusses DoT/DoH deployment considerations for home networks. It particularly sketches the required steps to use DoT/DoH capabilities provided by local networks.
- Sampled Traffic Streaming (draft-gray-sampled-streaming)
By Andrew Gray, Lawrence Wobker, 2020-04-02 TXT HTML PDF
Abstract: This document standardizes both 1) a means of requesting a stream of packet samples from any device generating, routing, or forwarding traffic, and 2) receiving metadata information from the network element about these packet samples, and the structure of said stream metadata. A main design requirement is to provide network elements with widely varying capabilities (e.g., ASICs, NPUs, NICs, vSwitches, CPUs) a mechanism to sample and export packets at high rates, by allowing communication of the specific bit formats of internal data headers applied to the packet flow, in a way that enhances interoperability between traffic sources and sinks. Historically, Netflow and similar mechanisms have been used for these use cases; however, the increasing packet rates of very high-speed devices and increasing variance in the information available to data planes lends itself to both a less-prescriptive set of packet formats as well as a decoupling of the sampling action from the collection and analysis mechanisms.
- 6TiSCH Minimal Scheduling Function (MSF) (draft-ietf-6tisch-msf)
By Tengfei Chang, Malisa Vucinic, Xavier Vilajosana, Simon Duquennoy, Diego Dujovne, 2020-04-02 TXT HTML PDF
Abstract: This specification defines the 6TiSCH Minimal Scheduling Function (MSF). This Scheduling Function describes both the behavior of a node when joining the network, and how the communication schedule is managed in a distributed fashion. MSF is built upon the 6TiSCH Operation Sublayer Protocol (6P) and the Minimal Security Framework for 6TiSCH.
- Bootstrapping Remote Secure Key Infrastructures (BRSKI) (draft-ietf-anima-bootstrapping-keyinfra)
By Max Pritikin, Michael Richardson, Toerless Eckert, Michael Behringer, Kent Watsen, 2020-04-02 TXT HTML PDF
Abstract: This document specifies automated bootstrapping of an Autonomic Control Plane. To do this a Secure Key Infrastructure is bootstrapped. This is done using manufacturer-installed X.509 certificates, in combination with a manufacturer's authorizing service, both online and offline. We call this process the Bootstrapping Remote Secure Key Infrastructure (BRSKI) protocol. Bootstrapping a new device can occur using a routable address and a cloud service, or using only link-local connectivity, or on limited/ disconnected networks. Support for deployment models with less stringent security requirements is included. Bootstrapping is complete when the cryptographic identity of the new key infrastructure is successfully deployed to the device. The established secure connection can be used to deploy a locally issued certificate to the device as well.
- Vendor Specific LISP Canonical Address Format (LCAF) (draft-ietf-lisp-vendor-lcaf)
By Alberto Rodriguez-Natal, Vina Ermagan, Anton Smirnov, Vrushali Ashtaputre, Dino Farinacci, 2020-04-02 TXT HTML PDF
Abstract: This document describes a new LISP Canonical Address Format (LCAF), the Vendor Specific LCAF. This LCAF enables organizations to have internal encodings for LCAF addresses.
- Packetization Layer Path MTU Discovery for Datagram Transports (draft-ietf-tsvwg-datagram-plpmtud)
By Gorry Fairhurst, Tom Jones, Michael Tuexen, Irene Ruengeler, Timo Voelker, 2020-04-02 TXT HTML PDF
Abstract: This document describes a robust method for Path MTU Discovery (PMTUD) for datagram Packetization Layers (PLs). It describes an extension to RFC 1191 and RFC 8201, which specifies ICMP-based Path MTU Discovery for IPv4 and IPv6. The method allows a PL, or a datagram application that uses a PL, to discover whether a network path can support the current size of datagram. This can be used to detect and reduce the message size when a sender encounters a packet black hole (where packets are discarded). The method can probe a network path with progressively larger packets to discover whether the maximum packet size can be increased. This allows a sender to determine an appropriate packet size, providing functionality for datagram transports that is equivalent to the Packetization Layer PMTUD specification for TCP, specified in RFC 4821.
- Operator Privacy for RemoteID Messages (draft-moskowitz-drip-operator-privacy)
By Robert Moskowitz, Stuart Card, Adam Wiethuechter, 2020-04-02 TXT HTML PDF
Abstract: This document describes a method of providing privacy for Operator information specified in the ASTM UAS Remote ID and Tracking messages. This is achieved by encrypting, in place, those fields containing Operator sensitive data using a hybrid ECIES.
- A YANG Model for User-Network Interface (UNI) Topologies (draft-ogondio-opsawg-uni-topology)
By Oscar de Dios, Samier Barguil, Qin WU, Mohamed Boucadair, 2020-04-02 TXT HTML PDF
Abstract: This document defines a YANG data model for representing an abstract view of the Service Provider network topology containing the points from which its services can be attached (e.g., basic connectivity, VPN, SDWAN). The data model augments the 'ietf-network' data model by adding the concept of service-attachment-points. The service- attachment-points are an abstraction of the points to which network services (such as L3 VPN or L2 VPN) can be attached.
- Reliable and Available Wireless Architecture/Framework (draft-pthubert-raw-architecture)
By Pascal Thubert, Georgios Papadopoulos, 2020-04-02 TXT HTML PDF
Abstract: Due to uncontrolled interferences, including the self-induced multipath fading, deterministic networking can only be approached on wireless links. The radio conditions may change -way- faster than a centralized routing can adapt and reprogram, in particular when the controller is distant and connectivity is slow and limited. RAW separates the routing time scale at which a complex path is recomputed from the forwarding time scale at which the forwarding decision is taken for an individual packet. RAW operates at the forwarding time scale. The RAW problem is to decide, within the redundant solutions that are proposed by the routing, which will be used for each individual packet to provide a DetNet service while minimizing the waste of resources.
- Transmission of IPv6 Packets over Overlay Multilink Network (OMNI) Interfaces (draft-templin-6man-omni-interface)
By Fred Templin, Tony Whyman, 2020-04-02 TXT HTML PDF
Abstract: Mobile nodes (e.g., aircraft of various configurations, terrestrial vehicles, seagoing vessels, mobile enterprise devices, etc.) communicate with networked correspondents over multiple access network data links and configure mobile routers to connect end user networks. A multilink interface specification is therefore needed for coordination with the network-based mobility service. This document specifies the transmission of IPv6 packets over Overlay Multilink Network (OMNI) Interfaces.
- Asymmetric Extended Route Optimization (AERO) (draft-templin-intarea-6706bis)
By Fred Templin, 2020-04-02 TXT HTML PDF
Abstract: This document specifies the operation of IP over tunnel virtual links using Asymmetric Extended Route Optimization (AERO). AERO interfaces use an IPv6 link-local address format that supports operation of the IPv6 Neighbor Discovery (ND) protocol and links ND to IP forwarding. Prefix delegation/registration services are employed for network admission and to manage the routing system. Multilink operation, mobility management, quality of service (QoS) signaling and route optimization are naturally supported through dynamic neighbor cache updates. Standard IP multicasting services are also supported. AERO is a widely-applicable mobile internetworking service especially well-suited to aviation services, mobile Virtual Private Networks (VPNs) and many other applications.
- PCEP Extension for SRv6 Unified SIDs (draft-xiong-pce-segment-routing-ipv6-complement)
By Quan Xiong, Shaofu Peng, 2020-04-02 TXT HTML PDF
Abstract: This document proposes PCEP extensions for SRv6 Path which applied to the use of SRv6 Unified SIDs.
Expired Drafts
- IGMP and MLD Proxy for EVPN (draft-ietf-bess-evpn-igmp-mld-proxy)
By Ali Sajassi, Samir Thoria, Keyur Patel, John Drake, Wen Lin, 2019-09-30 TXT HTML PDF
Abstract: Ethernet Virtual Private Network (EVPN) solution is becoming pervasive in data center (DC) applications for Network Virtualization Overlay (NVO) and DC interconnect (DCI) services, and in service provider (SP) applications for next generation virtual private LAN services.
- Publish-Subscribe Broker for the Constrained Application Protocol (CoAP) (draft-ietf-core-coap-pubsub)
By Michael Koster, Ari Keranen, Jaime Jimenez, 2019-09-30 TXT HTML PDF
Abstract: The Constrained Application Protocol (CoAP), and related extensions are intended to support machine-to-machine communication in systems where one or more nodes are resource constrained, in particular for low power wireless sensor networks. This document defines a publish- subscribe Broker for CoAP that extends the capabilities of CoAP for supporting nodes with long breaks in connectivity and/or up-time.
- DoD Common Cryptographic MIB (CCMIB) (draft-turner-ccmib)
By Jeffrey Sun, Mike Irani, Tom Nguyen, rpurvis@mitre.org, Sean Turner, 2019-09-30 TXT HTML PDF
Abstract: This document defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for key management implementations including asymmetric keys, symmetric keys, trust anchors, and cryptographic-related firmware.
- IS-IS Optimal Distributed Flooding for Dense Topologies (draft-white-distoptflood)
By Russ White, Shraddha Hegde, Shawn Zandi, 2019-09-30 TXT HTML PDF
Abstract: In dense topologies, such as data center fabrics based on the Clos and butterfly fabric topologies, flooding mechanisms designed for sparse topologies, when used in these dense topologies, can "overflood," or carry too many copies of topology and reachability to fabric devices. This results in slower convergence times and higher resource utilization. The modifications to the flooding mechanism in the Intermediate System to Intermediate System (IS-IS) link state protocol described in this document reduce resource utilization to a minimum, while increaseing convergence performance in dense topologies.
- Link Local Next Hop Handling for BGP (draft-white-linklocalnh)
By Russ White, Donald Sharp, Dinesh Dutt, Biswajit Sadhu, Jeff Tantsura, 2019-09-30 TXT HTML PDF
Abstract: BGP, described in [RFC4271], was originally designed to provide reachability between domains and between the edges of a domain. As such, BGP assumes the next hop towards any reachable destination may not reside on the advertising speaker, but rather may either be through a router connected to the same subnet as the speaker, or through a router only reachable by traversing multiple hops through the network. Because of this, BGP does not recognize the use of IPv6 link local addresses, as described in [RFC4291], as a valid next hop for forwarding purposes.
|
Drafts Sent to IESG
- Eligibility for the 2020-2021 Nominating Committee (draft-iesg-nomcom-eligibility-2020): » In Last Call
By Barry Leiba, 2020-04-02 TXT HTML PDF
Abstract: The 2020-2021 Nominating Committee (NomCom) needs to be formed between IETF 107 and IETF 108, and the issue of eligibility of who can serve on that NomCom needs clarification. This document provides a one-time interpretation of the eligibility rules that is required for the exceptional situation of the cancellation of the in-person IETF 107 meeting. This document only affects the seating of the 2020-2021 NomCom, and does not set a precedent for the future.
IESG Progress
- Extended Tokens and Stateless Clients in the Constrained Application Protocol (CoAP) (draft-ietf-core-stateless): In Last Call » Waiting for AD Go-Ahead
By Klaus Hartke, 2020-03-12 TXT HTML PDF
Abstract: This document provides considerations for alleviating CoAP clients and intermediaries of keeping per-request state. To facilitate this, this document additionally introduces a new, optional CoAP protocol extension for extended token lengths.
- Extended DNS Errors (draft-ietf-dnsop-extended-error): In Last Call » Waiting for AD Go-Ahead
By Warren Kumari, Evan Hunt, Roy Arends, Wes Hardaker, David Lawrence, 2020-01-15 TXT HTML PDF
Abstract: This document defines an extensible method to return additional information about the cause of DNS errors. Though created primarily to extend SERVFAIL to provide additional information about the cause of DNS and DNSSEC failures, the Extended DNS Errors option defined in this document allows all response types to contain extended error information. Extended DNS Error information does not change the processing of RCODEs.
- HIP Diet EXchange (DEX) (draft-ietf-hip-dex): IESG Evaluation::AD Followup » IESG Evaluation
By Robert Moskowitz, Rene Hummen, Miika Komu, 2020-03-20 TXT HTML PDF
Abstract: This document specifies the Host Identity Protocol Diet EXchange (HIP DEX), a variant of the Host Identity Protocol Version 2 (HIPv2). The HIP DEX protocol design aims at reducing the overhead of the employed cryptographic primitives by omitting public-key signatures and hash functions.
- Signaling MSD (Maximum SID Depth) using Border Gateway Protocol - Link State (draft-ietf-idr-bgp-ls-segment-routing-msd): AD Evaluation::AD Followup » In Last Call
By Jeff Tantsura, Uma Chunduri, Ketan Talaulikar, Greg Mirsky, Nikos Triantafillis, 2020-03-30 TXT HTML PDF
Abstract: This document defines a way for a Border Gateway Protocol - Link State (BGP-LS) speaker to advertise multiple types of supported Maximum SID Depths (MSDs) at node and/or link granularity.
- IS-IS TE Attributes per application (draft-ietf-isis-te-app): AD Evaluation::AD Followup » ::Point Raised - writeup needed
By Les Ginsberg, Peter Psenak, Stefano Previdi, Wim Henderickx, John Drake, 2020-03-21 TXT HTML PDF
Abstract: Existing traffic engineering related link attribute advertisements have been defined and are used in RSVP-TE deployments. Since the original RSVP-TE use case was defined, additional applications (e.g., Segment Routing Traffic Engineering, Loop Free Alternate) have been defined which also make use of the link attribute advertisements. In cases where multiple applications wish to make use of these link attributes the current advertisements do not support application specific values for a given attribute nor do they support indication of which applications are using the advertised value for a given link. This document introduces new link attribute advertisements which address both of these shortcomings.
Drafts Sent to RFC Editor
Other Status Changes
- Group Communication for the Constrained Application Protocol (CoAP) (draft-dijk-core-groupcomm-bis): Active » Replaced by draft-ietf-core-groupcomm-bis
By Esko Dijk, Chonggang Wang, Marco Tiloca, 2020-03-09 TXT HTML PDF
Abstract: This document specifies the use of the Constrained Application Protocol (CoAP) for group communication, using UDP/IP multicast as the underlying data transport. Both unsecured and secured CoAP group communication are specified. Security is achieved by use of the Group Object Security for Constrained RESTful Environments (Group OSCORE) protocol. The target application area of this specification is any group communication use cases that involve resource- constrained networks. The most common of such use cases are also discussed. This document replaces [RFC7390] and updates [RFC7252] and [RFC7641].
RFC Editor Status Changes
- DNS Reverse IP AMT (Automatic Multicast Tunneling) Discovery (draft-ietf-mboned-driad-amt-discovery): » AUTH48
By Jake Holland, 2019-12-20 TXT HTML PDF
Abstract: This document updates RFC 7450 (Automatic Multicast Tunneling, or AMT) by modifying the relay discovery process. A new DNS resource record named AMTRELAY is defined for publishing AMT relays for source-specific multicast channels. The reverse IP DNS zone for a multicast sender's IP address is configured to use AMTRELAY resource records to advertise a set of AMT relays that can receive and forward multicast traffic from that sender over an AMT tunnel. Other extensions and clarifications to the relay discovery process are also defined.
IPR Disclosures
IESG/IAB/IAOC/Trust Minutes
Liaison Statements
Classified Ads
|
WGs marked with an 
