IETF-Announce List
![[Feed]](feedicon16.png) New RFCs
New and Revived Drafts
- Source-Specific Routing in Babel (draft-boutier-babel-source-specific)
By Matthieu Boutier, Juliusz Chroboczek, 2017-06-15 TXT HTML PDF
Abstract: This document describes an extension to the Babel routing protocol to support source-specific routing.
- Remote Participation Hubs (draft-elkins-ietf-remote-participation-hubs)
By Nalini Elkins, harish@nixi.in, 2017-06-15 TXT HTML PDF
Abstract: For many reasons, remote participation in IETF meetings has increased. As the Internet grows, so does the participation by engineers worldwide. Remote participation with more than one person is considered a hub.
- Using Conditional Router Advertisements for Enterprise Multihoming (draft-linkova-v6ops-conditional-ras)
By J. Linkova, 2017-06-14 TXT HTML PDF
Abstract: This document discusses most common scenarios of connecting an enterprise network to multiple ISPs using provider aggregatable address space (PA). The problem of enterprise multihoming without address translation of any form has not been solved yet as it requires both the network to select the correct egress ISP based on the packet source address and hosts to select the correct source address based on the desired egress ISP for that traffic. [I-D.ietf-rtgwg-enterprise-pa-multihoming] proposes a solution to this problem by introducing a new routing functionality (Source Address Dependent Routing) to solve the uplink selection issue and using Router Advertisements to influence the host source address selection. While the above-mentioned document focus is on solving the general problem and to cover various complex use cases, this document describes how the solution proposed in [I-D.ietf-rtgwg-enterprise-pa-multihoming] can be adopted for limited number of common use cases. In particular the focus is on scenarios when a enterprise network has two Internet uplinks used either in primary/backup mode or simultaniously and hosts in that network might not yet properly support multihoming as described in [RFC8028].
- Requirements for Interactive Query with Dynamic Network Probes (draft-song-opsa-dnp4iq)
By Haoyu Song, Jun Gong, HongFei Chen, 2017-06-15 TXT HTML PDF
Abstract: This document discusses the motivation and requirements for supporting interactive network queries and data collection through a mechanism called Dynamic Network Probes (DNP). Network applications and OAM have various data requirements from the data plane. The unpredictable and interactive nature of the query for network data analytics asks for dynamic and on-demand data collection capabilities. As user programmable data plane is becoming a reality, it can be enhanced to support interactive query through DNPs. DNP supports node, path, and flow-based data preprocessing and collection. For example, in-situ OAM (iOAM) with user-defined flow- based data collection can be programmed and configured through DNP. DNPs serve as a building block of an integrated network data telemetry and analytics platform which involves the network data plane as an active component for user-defined data collection and preparation.
- draft-tiesel-socketintents
No title available; expired document? TXT HTML PDF
- Socket Intents (draft-tiesel-taps-socketintents)
By Philipp Tiesel, Theresa Enghardt, 2017-06-15 TXT HTML PDF
Abstract: This document outlines an API-independent concept that allows applications to share their knowledge about upcoming communication and express their performance preferences in a portable and abstract way: Socket Intents. Socket Intents express what an application knows, assumes, expects or wants to prioritize regarding its own network communication. The information provided by Socket Intents should be taken into account by the network stack in a best-effort way.
Updated Drafts
- YANG Model for QoS (draft-asechoud-rtgwg-qos-model)
By Aseem Choudhary, Mahesh Jethanandani, Norm Strahle, Ebben Aries, I. Chen, 2017-06-15 TXT HTML PDF
Abstract: This document describes a YANG model for Quality of Service (QoS) configuration and operational parameters.
- Minimal Security Framework for 6TiSCH (draft-ietf-6tisch-minimal-security)
By Malisa Vucinic, Jonathan Simon, Kris Pister, Michael Richardson, 2017-06-15 TXT HTML PDF
Abstract: This document describes the minimal mechanisms required to support secure enrollment of a pledge, a device being added to an IPv6 over the TSCH mode of IEEE 802.15.4e (6TiSCH) network. It assumes that the pledge has been provisioned with a credential that is relevant to the deployment - the "one-touch" scenario. The goal of this configuration is to set link-layer keys, and to establish a secure end-to-end session between each pledge and the join registrar who may use that to further configure the pledge. Additional security behaviors and mechanisms may be added on top of this minimal framework.
- Deprecate 3DES and RC4 in Kerberos (draft-ietf-curdle-des-des-des-die-die-die)
By Benjamin Kaduk, Michiko Short, 2017-06-15 TXT HTML PDF
Abstract: The 3DES and RC4 encryption types are steadily weakening in cryptographic strength, and the deprecation process should be begun for their use in Kerberos. Accordingly, RFC 4757 is moved to Obsolete status, as none of the encryption types it specifies should be used, and RFC 3961 is updated to note the deprecation of the triple-DES encryption types.
- GSS-API Key Exchange with SHA2 (draft-ietf-curdle-gss-keyex-sha2)
By Simo Sorce, Hubert Kario, 2017-06-15 TXT HTML PDF
Abstract: This document specifies additions and amendments to SSH GSS-API Methods [RFC4462]. It defines a new key exchange method that uses SHA-2 for integrity and deprecates weak DH groups. The purpose of this specification is to modernize the cryptographic primitives used by GSS Key Exchanges.
- Notification Message support for BGP Graceful Restart (draft-ietf-idr-bgp-gr-notification)
By Keyur Patel, Rex Fernando, John Scudder, Jeffrey Haas, 2017-06-15 TXT HTML PDF
Abstract: The BGP Graceful Restart mechanism defined in RFC 4724 limits the usage of BGP Graceful Restart to BGP protocol messages other than a BGP NOTIFICATION message. This document updates RFC 4724 by defining an extension that permits the Graceful Restart procedures to be performed when the BGP speaker receives a BGP NOTIFICATION Message or the Hold Time expires. This document also defines a new BGP NOTIFICATION Cease Error subcode whose effect is to request a full session restart instead of a Graceful Restart.
- BGP Administrative Shutdown Communication (draft-ietf-idr-shutdown)
By Job Snijders, Jakob Heitz, John Scudder, 2017-06-15 TXT HTML PDF
Abstract: This document enhances the BGP Cease NOTIFICATION message "Administrative Shutdown" and "Administrative Reset" subcodes for operators to transmit a short freeform message to describe why a BGP session was shutdown or reset. This document updates RFC 4486.
- Security Automation and Continuous Monitoring (SACM) Requirements (draft-ietf-sacm-requirements)
By Nancy Cam-Winget, Lisa Lorenzin, 2017-06-15 TXT HTML PDF
Abstract: This document defines the scope and set of requirements for the Secure Automation and Continuous Monitoring (SACM) architecture, data model and transport protocols. The requirements and scope are based on the agreed upon use cases.
- Segment Routing interworking with LDP (draft-ietf-spring-segment-routing-ldp-interop)
By Clarence Filsfils, Stefano Previdi, Ahmed Bashandy, Bruno Decraene, Stephane Litkowski, 2017-06-15 TXT HTML PDF
Abstract: A Segment Routing (SR) 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 allows to enforce a flow through any topological path and service chain while maintaining per-flow state only at the ingress node to the SR domain.
- An Architecture for Use of PCE and PCEP in a Network with Central Control (draft-ietf-teas-pce-central-control)
By Adrian Farrel, Quintin Zhao, Zhenbin Li, Chao Zhou, 2017-06-15 TXT HTML PDF
Abstract: The Path Computation Element (PCE) has become established as a core component of Software Defined Networking (SDN) systems. It can compute optimal paths for traffic across a network for any definition of "optimal" and can also monitor changes in resource availability and traffic demands to update the paths.
- Using RSA Algorithms with COSE Messages (draft-jones-cose-rsa)
By Michael Jones, 2017-06-15 TXT HTML PDF
Abstract: The CBOR Object Signing and Encryption (COSE) specification defines cryptographic message encodings using Concise Binary Object Representation (CBOR). This specification defines algorithm encodings and representations enabling RSA algorithms to be used for COSE messages. Encodings for the use of RSASSA-PSS signatures, RSAES-OAEP encryption, and RSA keys are specified.
- Certificate Transparency (CT) System Architecture (draft-kent-trans-architecture)
By Stephen Kent, David Mandelberg, Karen Seo, 2017-06-15 TXT HTML PDF
Abstract: This document describes the architecture for Certificate Transparency (CT) focusing on the Web PKI context. It defines the goals of CT and the elements that comprise the CT system. It also describes the major features of these elements. Other documents, cited in the References, establish requirements for these CT system elements and describe their operation in greater detail.
- Advertising Segment Routing Policies in BGP (draft-previdi-idr-segment-routing-te-policy)
By Stefano Previdi, Clarence Filsfils, Paul Mattes, Eric Rosen, Steven Lin, 2017-06-15 TXT HTML PDF
Abstract: This document defines a new BGP SAFI with a new NLRI in order to advertise a candidate path of a Segment Routing Policy (SR Policy). An SR Policy is a set of candidate paths consisting of one or more segment lists. The headend of an SR Policy may learn multiple candidate paths for an SR Policy. Candidate paths may be learned via a number of different mechanisms, e.g., CLI, NetConf, PCEP, or BGP. This document specifies the way in which BGP may be used to distribute candidate paths. New sub-TLVs for the Tunnel Encapsulation Attribute are defined.
- PMTUD Over Vxlan (draft-saum-nvo3-pmtud-over-vxlan)
By Saumya Dikshit, Nayak A, 2017-06-15 TXT HTML PDF
Abstract: Path MTU Discovery between hosts/VM/servers/end-points connected over a Data-Center/Service-Provider Overlay Network, is still an unattended problem. It needs a converged solution to ensure optimal usage of network and computational resources for all hooked end-point devices.
- A Mechanism Coping with Unexpected Disruption in Space Delay Tolerant Networks (draft-shi-dtn-amcud)
By Wenfeng Shi, Qi Xu, Bo-Hao Feng, Hua-chun Zhou, 2017-06-15 TXT HTML PDF
Abstract: This document proposes a coping mechanism used to deal with the unpredictable disruption problem and congestion control problem in Space Delay Tolerant Networks (DTN) [RFC4838]. Since Licklider Transmission Protocol (LTP) [RFC5326] provides retransmission-based reliability for bundles, several times of retransmissions can be seen as a failure occurred over links. The proposed mechanism is used to direct the following packets to other nodes as soon as the selected path is detected as disruption or congestion and probes the availability of the links which has disrupted unexpectedly.
Expired Drafts
- An IP option for describing the traffic flow (draft-chodorek-traffic-flow-option)
By Robert Chodorek, 2016-12-12 TXT HTML PDF
Abstract: Information about the behavior of the stream that will be transmitted in the near future will allow for better management of queues in the router and thus improve QoS and reduce the potential for a serious overload. Such information is often available in the transmitter. The proposed IP option allows for the sending of information about forthcoming traffic from the transmitter to the intermediate nodes.
- PCE auxiliary connections (draft-hu-pce-auxiliary-connections)
By fangwei hu, Ran Chen, 2016-12-12 TXT HTML PDF
Abstract: This document provides a method to establish auxiliary connections between PCE and PCC to improve the reliability of the connection of PCE and PCC. The real-time sample data and some state report flow are suggestion to transport by take use of the auxiliary connection.
- SIP Call-Info Parameters for Labeling Calls (draft-schulzrinne-sipcore-callinfo-spam)
By Henning Schulzrinne, 2016-12-12 TXT HTML PDF
Abstract: Called parties often wish to decide whether to accept, reject or redirect calls based on the likely nature of the call. For example, they may want to reject unwanted telemarketing or fraudulent calls, but accept emergency alerts from numbers not in their address book. This document describes SIP Call-Info parameters and a feature tag that allow originating, intermediate and terminating SIP entities to label calls as to their type, spam probability and references to additional information.
- Happy EarBalls: Success with Dual-Stack, Connection-Oriented SIP (draft-worley-sip-he-connection)
By Olle Johansson, Gonzalo Salgueiro, Dale Worley, 2016-12-12 TXT HTML PDF
Abstract: The Session Initiation Protocol (SIP) supports multiple transports running both over IPv4 and IPv6 protocols. In more and more cases, a SIP user agent (UA) is connected to multiple network interfaces. In these cases setting up a connection from a dual stack client to a dual stack server may suffer from the issues described in RFC 6555 [RFC6555] ("Happy Eyeballs") - significant delays in the process of setting up a working flow to a server. This negatively affects user experience.
|
Drafts Sent to IESG
- Message Encryption for Web Push (draft-ietf-webpush-encryption): Active » Publication Requested
By Martin Thomson, 2017-02-13 TXT HTML PDF
Abstract: A message encryption scheme is described for the Web Push protocol. This scheme provides confidentiality and integrity for messages sent from an Application Server to a User Agent.
IESG Progress
- The ARIA Algorithm and Its Use with the Secure Real-time Transport Protocol(SRTP) (draft-ietf-avtcore-aria-srtp): Waiting for Writeup » In Last Call
By Woo-Hwan Kim, Jungkeun Lee, Je-Hong Park, Daesung Kwon, 2015-11-25 TXT HTML PDF
Abstract: This document defines the use of the ARIA block cipher algorithm within the Secure Real-time Transport Protocol (SRTP). It details two modes of operation (CTR, GCM) and a SRTP Key Derivation Function for ARIA. Additionally, this document defines DTLS-SRTP protection profiles and MIKEY parameter sets for the use with ARIA.
- Multicast using Bit Index Explicit Replication (draft-ietf-bier-architecture): Publication Requested » In Last Call
By IJsbrand Wijnands, Eric Rosen, Andrew Dolganow, Tony Przygienda, Sam Aldrin, 2017-04-24 TXT HTML PDF
Abstract: This document specifies a new architecture for the forwarding of multicast data packets. It provides optimal forwarding of multicast packets through a "multicast domain". However, it does not require a protocol for explicitly building multicast distribution trees, nor does it require intermediate nodes to maintain any per-flow state. This architecture is known as "Bit Index Explicit Replication" (BIER). When a multicast data packet enters the domain, the ingress router determines the set of egress routers to which the packet needs to be sent. The ingress router then encapsulates the packet in a BIER header. The BIER header contains a bitstring in which each bit represents exactly one egress router in the domain; to forward the packet to a given set of egress routers, the bits corresponding to those routers are set in the BIER header. Elimination of the per- flow state and the explicit tree-building protocols results in a considerable simplification.
- Rules for Designing Protocols Using the RFC 5444 Generalized Packet/ Message Format (draft-ietf-manet-rfc5444-usage): AD Evaluation::AD Followup » In Last Call
By Thomas Clausen, Christopher Dearlove, Ulrich Herberg, Henning Rogge, 2017-05-17 TXT HTML PDF
Abstract: RFC 5444 specifies a generalized MANET packet/message format and describes an intended use for multiplexed MANET routing protocol messages that is mandated to use on the port/protocol specified by RFC 5498. This document updates RFC 5444 by providing rules and recommendations for how the multiplexer operates and how protocols can use the packet/message format. In particular, the mandatory rules prohibit a number of uses that have been suggested in various proposals, and which would have led to interoperability problems, to the impediment of protocol extension development, and to an inability to use optional generic parsers.
- Security Automation and Continuous Monitoring (SACM) Requirements (draft-ietf-sacm-requirements): Waiting for Writeup » IESG Evaluation
By Nancy Cam-Winget, Lisa Lorenzin, 2017-06-15 TXT HTML PDF
Abstract: This document defines the scope and set of requirements for the Secure Automation and Continuous Monitoring (SACM) architecture, data model and transport protocols. The requirements and scope are based on the agreed upon use cases.
- Datacenter TCP (DCTCP): TCP Congestion Control for Datacenters (draft-ietf-tcpm-dctcp): In Last Call » Waiting for Writeup
By Stephen Bensley, Dave Thaler, Praveen Balasubramanian, Lars Eggert, Glenn Judd, 2017-06-01 TXT HTML PDF
Abstract: This informational memo describes Datacenter TCP (DCTCP), a TCP congestion control scheme for datacenter traffic. DCTCP extends the Explicit Congestion Notification (ECN) processing to estimate the fraction of bytes that encounter congestion, rather than simply detecting that some congestion has occurred. DCTCP then scales the TCP congestion window based on this estimate. This method achieves high burst tolerance, low latency, and high throughput with shallow- buffered switches. This memo also discusses deployment issues related to the coexistence of DCTCP and conventional TCP, the lack of a negotiating mechanism between sender and receiver, and presents some possible mitigations. This memo documents existing DCTCP implementations ([WINDOWS], [LINUX], [FREEBSD]) and deployment experience ([MORGANSTANLEY]). DCTCP as described in this draft is applicable to deployments in controlled environments like datacenters but it must not be deployed over the public Internet without additional measures, as detailed in Section 5.
- TRILL: ARP/ND Optimization (draft-ietf-trill-arp-optimization): Publication Requested » In Last Call
By Li Yizhou, Donald Eastlake, Linda Dunbar, Radia Perlman, Mohammed Umair, 2017-04-16 TXT HTML PDF
Abstract: This document describes mechanisms to optimize the ARP (Address Resolution Protocol) and ND (Neighbor Discovery) traffic in TRILL campus. Such optimization reduces packet flooding over a TRILL campus.
- Using RSA Algorithms with COSE Messages (draft-jones-cose-rsa): In Last Call » Waiting for AD Go-Ahead
By Michael Jones, 2017-06-15 TXT HTML PDF
Abstract: The CBOR Object Signing and Encryption (COSE) specification defines cryptographic message encodings using Concise Binary Object Representation (CBOR). This specification defines algorithm encodings and representations enabling RSA algorithms to be used for COSE messages. Encodings for the use of RSASSA-PSS signatures, RSAES-OAEP encryption, and RSA keys are specified.
Drafts Sent to RFC Editor
- BGP Administrative Shutdown Communication (draft-ietf-idr-shutdown): Approved-announcement to be sent::AD Followup » RFC Ed Queue
By Job Snijders, Jakob Heitz, John Scudder, 2017-06-15 TXT HTML PDF
Abstract: This document enhances the BGP Cease NOTIFICATION message "Administrative Shutdown" and "Administrative Reset" subcodes for operators to transmit a short freeform message to describe why a BGP session was shutdown or reset. This document updates RFC 4486.
- Multipath Extension for the Optimized Link State Routing Protocol version 2 (OLSRv2) (draft-ietf-manet-olsrv2-multipath): IESG Evaluation::AD Followup » RFC Ed Queue
By Jiazi Yi, Benoit Parrein, 2017-05-24 TXT HTML PDF
Abstract: This document specifies a multipath extension for the Optimized Link State Routing Protocol version 2 (OLSRv2) to discover multiple disjoint paths for Mobile Ad Hoc Networks (MANETs). Considering the characteristics of MANETs, especially the dynamic network topology, using multiple paths can increase aggregated throughput and improve the reliability by avoiding single route failures. The interoperability with OLSRv2 is retained.
- Clarifications for when to use the name-addr production in SIP messages (draft-ietf-sipcore-name-addr-guidance): Approved-announcement sent » RFC Ed Queue
By Robert Sparks, 2017-06-01 TXT HTML PDF
Abstract: RFC3261 constrained several SIP header fields whose grammar contains the "name-addr / addr-spec" alternative to use name-addr when certain characters appear. Unfortunately it expressed the constraints with prose copied into each header field definition, and at least one header field was missed. Further, the constraint has not been copied into documents defining extension headers whose grammar contains the alternative.
Other Status Changes
- An Overview of BGPsec (draft-ietf-sidr-bgpsec-overview): AD Evaluation::External Party » Active
By Matthew Lepinski, Sean Turner, 2016-06-23 TXT HTML PDF
Abstract: This document provides an overview of a security extension to the Border Gateway Protocol (BGP) referred to as BGPsec. BGPsec improves security for BGP routing.
- draft-tiesel-socketintents: » Replaced by draft-tiesel-taps-socketintents
No title available; expired document? TXT HTML PDF
RFC Editor Status Changes
IPR Disclosures
IESG/IAB/IAOC/Trust Minutes
Liaison Statements
Classified Ads
|
WGs marked with an 
