IETF-Announce List
![[Feed]](feedicon16.png) New RFCs
New and Revived Drafts
- Delay-based Metric Extension for the Babel Routing Protocol (draft-ietf-babel-rtt-extension)
By Baptiste Jonglez, Juliusz Chroboczek, 2019-04-26 TXT HTML PDF
Abstract: This document defines an extension to the Babel routing protocol that uses symmetric delay in metric computation and therefore makes it possible to prefer lower latency links to higher latency ones.
- Cookies: HTTP State Management Mechanism (draft-ietf-httpbis-rfc6265bis)
By Adam Barth, Mike West, 2019-04-27 TXT HTML PDF
Abstract: This document defines the HTTP Cookie and Set-Cookie header fields. These header fields can be used by HTTP servers to store state (called cookies) at HTTP user agents, letting the servers maintain a stateful session over the mostly stateless HTTP protocol. Although cookies have many historical infelicities that degrade their security and privacy, the Cookie and Set-Cookie header fields are widely used on the Internet. This document obsoletes RFC 6265.
- SCHC over Sigfox LPWAN (draft-ietf-lpwan-schc-over-sigfox)
By Juan Zuniga, Carles Gomez, Laurent Toutain, 2019-04-26 TXT HTML PDF
Abstract: The Static Context Header Compression (SCHC) specification describes a header compression scheme and a fragmentation functionality for Low Power Wide Area Network (LPWAN) technologies. SCHC offers a great level of flexibility that can be tailored for different LPWAN technologies.
- YANG Geo Location (draft-ietf-netmod-geo-location)
By Christian Hopps, 2019-04-26 TXT HTML PDF
Abstract: This document defines a generic geographical location object YANG grouping. The geographical location grouping is intended to be used in YANG models for specifying a location on or in reference to the Earth or any other astronomical object.
- RACK: a time-based fast loss detection algorithm for TCP (draft-ietf-tcpm-rack)
By Yuchung Cheng, Neal Cardwell, Nandita Dukkipati, Priyaranjan Jha, 2019-04-26 TXT HTML PDF
Abstract: This document presents a new TCP loss detection algorithm called RACK ("Recent ACKnowledgment"). RACK uses the notion of time, instead of packet or sequence counts, to detect losses, for modern TCP implementations that can support per-packet timestamps and the selective acknowledgment (SACK) option. It is intended to replace the conventional DUPACK threshold approach and its variants, as well as other nonstandard approaches.
- DNS over Transport Layer Security announcements using DHCP or Router Advertisements (draft-peterson-dot-dhcp)
By Thomas Peterson, 2019-04-27 TXT HTML PDF
Abstract: This specification describes a DHCP option and Router Advertisement (RA) extension to inform clients of the presence of DNS resolvers with Transport Layer Security (TLS).
- The checksum in DIASER/UDP/IP is a XOR without STX (draft-petrescu-ipwave-diaser-checksum)
By Alexandre Petrescu, Mariama Sarr, 2019-04-26 TXT HTML PDF
Abstract: This document defines the manner in which to calculate the checksum for the protocol DIASER. DIASER is a protocol for communication with traffic lights controllers used in France. DIASER is specified at AFNOR. The specification misses an instruction on how to compute the 'BCC' checksum ('Byte Character Control').
- IPv6 Neighbor Discovery on Wireless Networks (draft-thubert-6man-ipv6-over-wireless)
By Pascal Thubert, 2019-04-26 TXT HTML PDF
Abstract: This document describes how the original IPv6 Neighbor Discovery and Wireless ND (WiND) can be applied on various abstractions of wireless media.
- L3DL Upper Layer Protocol Configuration (draft-ymbk-lsvr-l3dl-ulpc)
By Randy Bush, Keyur Patel, 2019-04-27 TXT HTML PDF
Abstract: This document users the Layer 3 Liveness and Discovery protocol to communicate the parameters needed to exchange inter-device Upper Layer Protocol Configuration for upper layer protocols such as the BGP family.
Updated Drafts
- Applicability of the Babel routing protocol (draft-ietf-babel-applicability)
By Juliusz Chroboczek, 2019-04-26 TXT HTML PDF
Abstract: Babel is a routing protocol based on the distance-vector algorithm augmented with mechanisms for loop avoidance and starvation avoidance. In this document, we argue that there exist niches where Babel is useful and that are not adequately served by more mature protocols.
- BGP Control Plane for NSH SFC (draft-ietf-bess-nsh-bgp-control-plane)
By Adrian Farrel, John Drake, Eric Rosen, Jim Uttaro, Luay Jalil, 2019-04-26 TXT HTML PDF
Abstract: This document describes the use of BGP as a control plane for networks that support Service Function Chaining (SFC). The document introduces a new BGP address family called the SFC AFI/SAFI with two route types. One route type is originated by a node to advertise that it hosts a particular instance of a specified service function. This route type also provides "instructions" on how to send a packet to the hosting node in a way that indicates that the service function has to be applied to the packet. The other route type is used by a Controller to advertise the paths of "chains" of service functions, and to give a unique designator to each such path so that they can be used in conjunction with the Network Service Header defined in RFC 8300.
- Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Call Home (draft-ietf-dots-signal-call-home)
By Reddy K, Mohamed Boucadair, Jon Shallow, 2019-04-26 TXT HTML PDF
Abstract: This document specifies the DOTS signal channel Call Home service, which enables a DOTS server to initiate a secure connection to a DOTS client, and to receive the attack traffic information from the DOTS client. The DOTS server in turn uses the attack traffic information to identify the compromised devices launching the outgoing DDoS attack and takes appropriate mitigation action(s).
- Validation of Locations Around a Planned Change (draft-ietf-ecrit-lost-planned-changes)
By Brian Rosen, 2019-04-26 TXT HTML PDF
Abstract: This document defines an extension to LoST (RFC5222) that allows a planned change to the data in the LoST server to occur. Records that previously were valid will become invalid at a date in the future, and new locations will become valid after the date. The extension adds two elements to the <findservice> request: A URI to be used to inform the LIS that previously valid locations will be invalid after the planned change date, and add a date which requests the server to perform validation as of the date specified. It also adds an optional Time-To-Live element to the response, which informs clients about the current expected lifetime of the validation. This document also provides a conventional XML schema for LoST, as backwards compatible alternative to the RelaxNG schema in RFC5222
- A YANG data model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) (draft-ietf-pim-igmp-mld-yang)
By Xufeng Liu, Feng Guo, Mahesh Sivakumar, Pete McAllister, Anish Peter, 2019-04-27 TXT HTML PDF
Abstract: This document defines a YANG data model that can be used to configure and manage Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) devices.
- Efficient Route Invalidation (draft-ietf-roll-efficient-npdao)
By Rahul Jadhav, Pascal Thubert, Rabi Sahoo, Zhen Cao, 2019-04-27 TXT HTML PDF
Abstract: This document describes the problems associated with No-Path Destination Advertisement Object (NPDAO) messaging used in Routing Protocol for Low power and lossy networks (RPL) for route invalidation and signaling changes to improve route invalidation efficiency.
- Asymmetric Manifest Based Integrity (draft-jholland-mboned-ambi)
By Jake Holland, Kyle Rose, 2019-04-26 TXT HTML PDF
Abstract: This document defines Asymmetric Manifest-Based Integrity (AMBI). AMBI allows each receiver of a stream of multicast packets to check the integrity of the contents of each packet in the data stream. AMBI operates by passing cryptographically verifiable manifests for the data packets, over out-of-band communication channels.
- Publishing Organization Boundaries in the DNS (draft-levine-dbound-dns)
By John Levine, 2019-04-27 TXT HTML PDF
Abstract: The organization that manages a subtree in the DNS is often different from the one that manages the tree above it. We describe an architecture to publish in the DNS the boundaries between organizations that can be adapted to various policy models and can be queried with a small number of DNS lookups.
- The length of the prefix of an IPv6 link-local address ranges from 10 to 127 (draft-petrescu-6man-ll-prefix-len)
By Alexandre Petrescu, Loganaden Velvindron, Naveen Kottapalli, Gyan Mishra, 2019-04-27 TXT HTML PDF
Abstract: A rejected Erratum to RFC4291 "IPv6 Addr Archi" on the topic of link- local addresses 'would need' a draft. This is an answer to that need.
Expired Drafts
- Session Initiation Protocol (SIP) Call Flow Examples with PASSporT Diversion and History-Info (draft-barnes-stir-passport-div-hi-callflows)
By Mary Barnes, 2018-10-23 TXT HTML PDF
Abstract: This document focuses on use cases and call flows which include the History-Info header field and a SIP Identity header field with a PASSport with a "div" claim in cases of retargeting. These use cases are derived from those provided in the SIP History-Info call flows document. The objective is to describe the optimal way to correlate the History-Info header fields with a PASSporT with diversion information to increase the level of confidence in the History-Info header field by the terminating entity making use of the information.
- Software Inventory YANG module based on Software Identifiers (draft-birkholz-yang-swid)
By Henk Birkholz, 2018-10-23 TXT HTML PDF
Abstract: This document provides a YANG module definition that enables a computing context to provide detailed information about installed software components. The structure of the module is based on the Concise Software Identifier draft and therefore also strongly related to the ISO 19770-2:2015 Software Identifiers standard. Both standards provide no interface to transport the SWID tag information between system entities and this document leverages the wide adoption of YANG based management interfaces.
- Constrained Application Protocol (CoAP): Corrections and Clarifications (draft-bormann-core-corr-clar)
By Carsten Bormann, 2018-10-23 TXT HTML PDF
Abstract: RFC 7252 defines the Constrained Application Protocol (CoAP), along with a number of additional specifications, including RFC 7641, RFC 7959, RFC 8132, and RFC 8323. RFC 6690 defines the link format that is used in CoAP self-description documents.
- Preferred Path Route Graph Structure (draft-ce-lsr-ppr-graph)
By Uma Chunduri, Toerless Eckert, 2018-10-23 TXT HTML PDF
Abstract: This document defines a graph structure for the Preferred Path Route (PPR) for IS-IS, OSPFv2 and OSPFv3 protocols. This structure helps further scale of the PPR and reduce domain level global entries needed in some data planes.
- Service Discovery Road Map (draft-cheshire-dnssd-roadmap)
By Stuart Cheshire, 2018-10-23 TXT HTML PDF
Abstract: Over the course of several years, a rich collection of technologies has developed around DNS-Based Service Discovery, described across multiple documents. This "Road Map" document gives an overview of how these related but separate technologies (and their documents) fit together, to facilitate service discovery in various environments.
- Performance Measurement (PM) with Alternate Marking in Network Virtualization Overlays (NVO3) (draft-fmm-nvo3-pm-alt-mark)
By Giuseppe Fioccola, Gregory Mirsky, Tal Mizrahi, 2018-10-23 TXT HTML PDF
Abstract: This document describes how the alternate marking method can be used for performance measurement method in a Network Virtualization Overlays (NVO3) Domain. The description aims to be general for NVO3 encapsulations, but is focused to Geneve, recommended by the NVO3 design team [I-D.ietf-nvo3-encap].
- C3DC -- Constrained Client/Cross-Domain Capable Authorization Profile for Authentication and Authorization for Constrained Environments (ACE) (draft-gerdes-ace-c3dc)
By Stefanie Gerdes, Olaf Bergmann, Carsten Bormann, 2018-10-23 TXT HTML PDF
Abstract: Resource-constrained nodes come in various sizes and shapes and often have constraints on code size, state memory, processing capabilities, user interface, power and communication bandwidth (RFC 7228).
- Traffic Engineering for Bit Index Explicit Replication (BIER-TE) (draft-ietf-bier-te-arch)
By Toerless Eckert, Gregory Cauchie, Wolfgang Braun, Michael Menth, 2018-10-23 TXT HTML PDF
Abstract: This document proposes an architecture for BIER-TE: Traffic Engineering for Bit Index Explicit Replication (BIER).
- Device Pairing Design Issues (draft-ietf-dnssd-pairing-info)
By Daniel Kaiser, Christian Huitema, 2018-10-23 TXT HTML PDF
Abstract: This document discusses issues and problems occuring in the design of device pairing mechanism. It presents experience with existing pairing systems and general user interaction requirements to make the case for "short authentication strings". It then reviews the design of cryptographic algorithms designed to maximise the robustness of the short authentication string mechanisms, as well as implementation considerations such as integration with TLS.
- Homenet Naming and Service Discovery Architecture (draft-ietf-homenet-simple-naming)
By Ted Lemon, Daniel Migault, Stuart Cheshire, 2018-10-23 TXT HTML PDF
Abstract: This document describes how names are published and resolved on homenets, and how hosts are configured to use these names to discover services on homenets. It presents the complete architecture, and describes a simple subset of that architecture that can be used in low-cost homenet routers.
- Distribution of MPLS-TE Extended admin Group Using BGP (draft-ietf-idr-eag-distribution)
By Zitao Wang, Qin Wu, Jeff Tantsura, 2018-10-23 TXT HTML PDF
Abstract: As MPLS-TE network grows, administrative Groups advertised as a fixed-length 32-bit Bitmask is quite constraining. "Extended Administrative Group" IGP TE extensions sub-TLV is introduced to provide for additional administrative groups (link colors) beyond the current limit of 32. This document describes extensions to BGP protocol, that can be used to distribute extended administrative groups in MPLS-TE.
- The Open Trust Protocol (OTrP) (draft-ietf-teep-opentrustprotocol)
By Mingliang Pei, Andrew Atyeo, Nick Cook, Minho Yoo, Hannes Tschofenig, 2018-10-23 TXT HTML PDF
Abstract: This document specifies the Open Trust Protocol (OTrP), a protocol that follows the Trust Execution Environment Provisioning (TEEP) architecture and provides a message protocol that provisions and manages Trusted Applications into a device with a Trusted Execution Environment (TEE).
- LSP Ping/Traceroute for Prefix SID in Presence of Multi-Algorithm/Multi-Topology Networks (draft-iqbal-spring-mpls-ping-algo)
By faiqbal@cisco.com, Nagendra Kumar, Zafar Ali, Carlos Pignataro, 2018-10-23 TXT HTML PDF
Abstract: This document updates [RFC8287] by modifying IPv4 and IPv6 IGP-Prefix Segment ID FEC sub-TLVs to also include algorithm identification while maintaining backwards compatibility. This document also introduces new Target FEC Stack sub-TLVs for Prefix SID validation in multi-topology networks.
- Multipath ChaMeLeon (M-CML): A multipath hybrid routing protocol for MANETs (draft-ladas-manet-m-cml)
By Alexandros Ladas, Deepak C, Nuwan Weerasinghe, Christos Politis, 2018-10-23 TXT HTML PDF
Abstract: This document describes the multipath ChaMeLeon (M-CML) routing protocol designed for Mobile Ad hoc Networks (MANETs). M-CML is a multi-path, hybrid routing protocol operating within a defined area denoted as the Critical Area (CA) in which the MANET is temporarily deployed during the post-disaster phase. The main concept behind M- CML is the adaptability of its routing mechanisms towards changes in the physical and logical state of a MANET. For autonomous communications in MANET, it is likely that the network size varies whenever additional devices join or subset of them leave the network. In addition, battery depletion of lightweight mobile communication devices will stipulate another reason for changes in the network size. As a result, the M-CML approach adapts its routing mechanism according to changes in the network scenario within a predefined CA. For small networks, M-CML routes data proactively using the Optimized Link State Routing version v2 (OLSRv2) protocol whereas for larger networks it utilizes the reactive Ad hoc On- Demand Distance Vector Version 2 (AODVv2) Routing protocol. The oscillation phase is the intermediate phase in which the transition of routing protocol occurs. M-CML creates multi-path routes for nodes with disjoint paths which increases the network reliability.
- pretty Easy privacy (pEp): Email Formats and Protocols (draft-marques-pep-email)
By Hernani Marques, 2018-10-23 TXT HTML PDF
Abstract: The pretty Easy privacy (pEp) propositions for email are based upon already existing email and encryption formats (i.e., PGP/MIME) and designed to allow for easy implementable and interoperable opportunistic encryption: this ranging from key distribution to mechanisms of subject encryption.
- Special-Use Labels (draft-moonesamy-dnsop-special-use-label-registry)
By Moonesamy S, Jiankang Yao, 2018-10-23 TXT HTML PDF
Abstract: This document describes what it means to say that a label is reserved for special use, when reserving such a label is appropriate, and the procedure for doing so. It establishes an IANA registry for such special-use labels, and seeds it with entries for some of the already established special labels.
- Label Switched Path (LSP) Ping/Traceroute for Segment Routing SIDs with MPLS Data-plane (draft-nainar-mpls-spring-lsp-ping-sids)
By Nagendra Kumar, Carlos Pignataro, faiqbal@cisco.com, Zafar Ali, 2018-10-23 TXT HTML PDF
Abstract: RFC8402 introduces Segment Routing architecture that leverages source routing and tunneling paradigms and can be directly applied to the Multi Protocol Label Switching (MPLS) data plane. A node steers a packet through a controlled set of instructions called segments, by prepending the packet with Segment Routing header. SR architecture defines different types of segments with different forwarding semantics associated.
- An Information Model for the Monitoring of Network Security Functions (NSF) (draft-zhang-i2nsf-info-model-monitoring)
By Liang Xia, Dacheng Zhang, Yi Wu, Rakesh Kumar, Anil Lohiya, Henk Birkholz, 2018-10-23 TXT HTML PDF
Abstract: The Network Security Functions (NSF) NSF-facing interface exists between the Service Provider's management system (or Security Controller) and the NSF to enforce security policy provisioning and network security status monitoring. This document focuses on the monitoring part and defines the corresponding information model for it.
|
Drafts Sent to IESG
IESG Progress
- Applicability of the Babel routing protocol (draft-ietf-babel-applicability): AD Evaluation::Revised I-D Needed » ::AD Followup
By Juliusz Chroboczek, 2019-04-26 TXT HTML PDF
Abstract: Babel is a routing protocol based on the distance-vector algorithm augmented with mechanisms for loop avoidance and starvation avoidance. In this document, we argue that there exist niches where Babel is useful and that are not adequately served by more mature protocols.
- BGP-LS extensions for Segment Routing BGP Egress Peer Engineering (draft-ietf-idr-bgpls-segment-routing-epe): Waiting for Writeup » IESG Evaluation
By Stefano Previdi, Ketan Talaulikar, Clarence Filsfils, Keyur Patel, Saikat Ray, Jie Dong, 2019-03-24 TXT HTML PDF
Abstract: Segment Routing (SR) leverages source routing. A node steers a packet through a controlled set of instructions, called segments, by prepending the packet with an SR header. A segment can represent any instruction, topological or service-based. SR segments allow steering a flow through any topological path and service chain while maintaining per-flow state only at the ingress node of the SR domain.
- IS-IS Extensions for Segment Routing (draft-ietf-isis-segment-routing-extensions): Waiting for Writeup » IESG Evaluation
By Stefano Previdi, Les Ginsberg, Clarence Filsfils, Ahmed Bashandy, Hannes Gredler, Bruno Decraene, 2019-04-17 TXT HTML PDF
Abstract: Segment Routing (SR) allows for a flexible definition of end-to-end paths within IGP topologies by encoding paths as sequences of topological sub-paths, called "segments". These segments are advertised by the link-state routing protocols (IS-IS and OSPF).
- TCP Extensions for Multipath Operation with Multiple Addresses (draft-ietf-mptcp-rfc6824bis): In Last Call » Waiting for Writeup
By Alan Ford, Costin Raiciu, Mark Handley, Olivier Bonaventure, Christoph Paasch, 2019-02-17 TXT HTML PDF
Abstract: TCP/IP communication is currently restricted to a single path per connection, yet multiple paths often exist between peers. The simultaneous use of these multiple paths for a TCP/IP session would improve resource usage within the network and, thus, improve user experience through higher throughput and improved resilience to network failure.
- A YANG data model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) (draft-ietf-pim-igmp-mld-yang): Waiting for AD Go-Ahead::Revised I-D Needed » ::AD Followup
By Xufeng Liu, Feng Guo, Mahesh Sivakumar, Pete McAllister, Anish Peter, 2019-04-27 TXT HTML PDF
Abstract: This document defines a YANG data model that can be used to configure and manage Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) devices.
- Efficient Route Invalidation (draft-ietf-roll-efficient-npdao): AD Evaluation::Revised I-D Needed » ::AD Followup
By Rahul Jadhav, Pascal Thubert, Rabi Sahoo, Zhen Cao, 2019-04-27 TXT HTML PDF
Abstract: This document describes the problems associated with No-Path Destination Advertisement Object (NPDAO) messaging used in Routing Protocol for Low power and lossy networks (RPL) for route invalidation and signaling changes to improve route invalidation efficiency.
Drafts Sent to RFC Editor
Other Status Changes
- YANG Geo Location (draft-chopps-netmod-geo-location): Active » Replaced by draft-ietf-netmod-geo-location
By Christian Hopps, 2019-03-02 TXT HTML PDF
Abstract: This document defines a generic geographical location object YANG grouping. The geographical location grouping is intended to be used in YANG models for specifying a location on or in reference to the Earth or any other astronomical object.
- State-of-the-Art and Challenges for the Internet of Things Security (draft-irtf-t2trg-iot-seccons): Active » RFC 8576
rfc8576.txt
By Oscar Garcia-Morchon, Sandeep Kumar, Mohit Sethi, 2018-12-13 TXT HTML PDF
Abstract: The Internet of Things (IoT) concept refers to the usage of standard Internet protocols to allow for human-to-thing and thing-to-thing communication. The security needs for IoT systems are well- recognized and many standardization steps to provide security have been taken, for example, the specification of Constrained Application Protocol (CoAP) secured with Datagram Transport Layer Security (DTLS). However, security challenges still exist, not only because there are some use cases that lack a suitable solution, but also because many IoT devices and systems have been designed and deployed with very limited security capabilities. In this document, we first discuss the various stages in the lifecycle of a thing. Next, we document the security threats to a thing and the challenges that one might face to protect against these threats. Lastly, we discuss the next steps needed to facilitate the deployment of secure IoT systems. This document can be used by implementors and authors of IoT specifications as a reference for details about security considerations while documenting their specific security challenges, threat models, and mitigations.
- Delay-based Metric Extension for the Babel Routing Protocol (draft-jonglez-babel-rtt-extension): Active » Replaced by draft-ietf-babel-rtt-extension
By Baptiste Jonglez, Juliusz Chroboczek, 2019-03-11 TXT HTML PDF
Abstract: This document defines an extension to the Babel routing protocol that uses symmetric delay in metric computation and therefore makes it possible to prefer lower latency links to higher latency ones.
RFC Editor Status Changes
IPR Disclosures
IESG/IAB/IAOC/Trust Minutes
Liaison Statements
Classified Ads
|
WGs marked with an 
