IETF-Announce List
![[Feed]](feedicon16.png) New RFCs
New and Revived Drafts
- Fast Reroute for Node Protection in LDP-based LSPs (draft-esale-mpls-ldp-node-frr)
By Santosh Esale, Raveendra Torvi, Luyuan Fang, Luay Jalil, 2016-05-19 TXT HTML PDF
Abstract: This document describes procedures to support node protection for unicast Label Switched Paths (LSPs) established by Label Distribution Protocol (LDP). In order to protect a node N, the Point of Local Repair (PLR) of N must discover the Merge Points (MPs) of node N such that traffic can be redirected to them in case of node N failure. Redirecting the traffic around the failed node N depends on existing point-to-point LSPs originated from the PLR to the MPs while bypassing the protected node N. The procedures described in this document are topology independent in a sense that they provide node protection in any topology.
- Transport layer protocols over UDP (draft-herbert-transports-over-udp)
By Tom Herbert, 2016-05-19 TXT HTML PDF
Abstract: This specification defines a mechanism to encapsulate layer four transport protocols over UDP. Such encapsulation facilitates deployment of alternate transport protocols or transport protocol features on the Internet. DTLS can be employed to encrypt the encapsulated transport header in a packet thus minimizing the exposure of transport layer information to the network and so promoting the end-to-end networking principle.
- Applying BGP flowspec rules on a specific interface set (draft-ietf-idr-flowspec-interfaceset)
By Stephane Litkowski, Adam Simpson, Keyur Patel, Jeffrey Haas, 2016-05-19 TXT HTML PDF
Abstract: BGP Flow-spec is an extension to BGP that allows for the dissemination of traffic flow specification rules. The primary application of this extension is DDoS mitigation where the flowspec rules are applied in most cases to all peering routers of the network.
- Coordinating Attack Response at Internet Scale (CARIS) Workshop Report (draft-moriarty-carisreport)
By Kathleen Moriarty, Mat Ford, 2016-05-19 TXT HTML PDF
Abstract: The Internet Architecture Board (IAB) and the Internet Society (ISOC) hosted a day-long Coordinating Attack Response at Internet Scale (CARIS) workshop on 18 June 2015 in coordination with the Forum for Incident Response and Security Teams (FIRST) Conference in Berlin. The workshop included members of the FIRST community, attack response working group representatives, network and security operators, Regional Internet Registry (RIR) representatives, researchers, vendors, and representatives from standardisation communities. Key goals of the workshop were to improve mutual awareness, understanding, and coordination among the diverse participating organizations and their representatives. The workshop also aimed to provide the attendees with greater awareness of existing efforts to mitigate specific types of attacks, and greater understanding of the options available to collaborate and engage with these efforts.
Updated Drafts
- An MPTCP Option for Network-Assisted MPTCP Deployments: Plain Transport Mode (draft-boucadair-mptcp-plain-mode)
By Mohamed Boucadair, Christian Jacquenet, Denis Behaghel, stesecci, Wim Henderickx, Robert Skog, Olivier Bonaventure, Suresh Vinapamula, SungHoon Seo, 2016-05-19 TXT HTML PDF
Abstract: One of the promising deployment scenarios for Multipath TCP (MPTCP) is to enable a Customer Premises Equipment (CPE) that is connected to multiple networks (e.g., DSL, LTE, WLAN) to optimize the usage of its network attachments. Because of the lack of MPTCP support at the server side, some service providers now consider a network-assisted model that relies upon the activation of a dedicated function called MPTCP concentrator. This document focuses on a deployment scheme where the identity of the MPTCP concentrator(s) is explicitly configured on connected hosts.
- Special Use Domain Name 'ipv4only.arpa' (draft-cheshire-sudn-ipv4only-dot-arpa)
By Stuart Cheshire, David Schinazi, 2016-05-19 TXT HTML PDF
Abstract: The document "Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis" [RFC7050] specifies the Special Use Domain Name 'ipv4only.arpa', with certain precise special properties, but, perversely, the Domain Name Reservation Considerations section [RFC6761] in that document then goes on to deny the specialness of that name, and (as of May 2016) the name 'ipv4only.arpa' does not appear in the Special-Use Domain Names registry.
- CDNI Control Interface / Triggers (draft-ietf-cdni-control-triggers)
By Rob Murray, Ben Niven-Jenkins, 2016-05-19 TXT HTML PDF
Abstract: This document describes the part of the CDN Interconnection Control Interface that allows a CDN to trigger activity in an interconnected CDN that is configured to deliver content on its behalf. The upstream CDN can use this mechanism to request that the downstream CDN pre-positions metadata or content, or that it invalidates or purges metadata or content. The upstream CDN can monitor the status of activity that it has triggered in the downstream CDN.
- Diameter Agent Overload and the Peer Overload Report (draft-ietf-dime-agent-overload)
By Steve Donovan, 2016-05-19 TXT HTML PDF
Abstract: This specification documents an extension to the Diameter Overload Indication Conveyance (DOIC) [RFC7683] base solution. The extension defines the Peer overload report type. The initial use case for the Peer report is the handling of occurrences of overload of a Diameter agent.
- MPLS Transport Profile Linear Protection MIB (draft-ietf-mpls-tp-linear-protection-mib)
By Kingston Smiler, Venkatesan Mahalingam, Vishwas Manral, Daniel King, Sam Aldrin, Jeong-dong Ryoo, 2016-05-19 TXT HTML PDF
Abstract: This memo defines a portion of the Management Information Base (MIB) for use with network management protocols. In particular it defines objects for managing MPLS Transport Profile (MPLS-TP) Linear Protection.
- Securing RPSL Objects with RPKI Signatures (draft-ietf-sidr-rpsl-sig)
By kistel, Brian Haberman, 2016-05-19 TXT HTML PDF
Abstract: This document describes a method to allow parties to electronically sign Routing Policy Specification Language objects and validate such electronic signatures. This allows relying parties to detect accidental or malicious modifications on such objects. It also allows parties who run Internet Routing Registries or similar databases, but do not yet have Routing Policy System Security-based authentication of the maintainers of certain objects, to verify that the additions or modifications of such database objects are done by the legitimate holder(s) of the Internet resources mentioned in those objects. This document updates RFC 2622 and RFC 4012 to add the signature attribute to supported RPSL objects.
- RFC 4960 Errata and Issues (draft-tuexen-tsvwg-rfc4960-errata)
By Randall Stewart, Michael Tuexen, Maksim Proshin, 2016-05-19 TXT HTML PDF
Abstract: This document is a compilation of issues found since the publication of RFC4960 in September 2007 based on experience with implementing, testing, and using SCTP along with the suggested fixes. This document provides deltas to RFC4960 and is organized in a time based way. The issues are listed in the order they were brought up. Because some text is changed several times the last delta in the text is the one which should be applied. In addition to the delta a description of the problem and the details of the solution are also provided.
Expired Drafts
- ISIS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering (draft-chen-isis-rfc5316bis)
By Mach Chen, Les Ginsberg, Stefano Previdi, Xiaodong Duan, 2015-11-16 TXT HTML PDF
Abstract: This document describes extensions to the ISIS (ISIS) protocol to support Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering (TE) for multiple Autonomous Systems (ASes). It defines ISIS-TE extensions for the flooding of TE information about inter-AS links, which can be used to perform inter- AS TE path computation.
|
Drafts Sent to IESG
IESG Progress
- AQM Characterization Guidelines (draft-ietf-aqm-eval-guidelines): IESG Evaluation » ::Revised I-D Needed
By N. Kuhn, Preethi Natarajan, Naeem Khademi, David Ros, 2016-02-15 TXT HTML PDF
Abstract: Unmanaged large buffers in today's networks have given rise to a slew of performance issues. These performance issues can be addressed by some form of Active Queue Management (AQM) mechanism, optionally in combination with a packet scheduling scheme such as fair queuing. This document describes various criteria for performing precautionary characterizations of AQM schemes.
- PIE: A Lightweight Control Scheme To Address the Bufferbloat Problem (draft-ietf-aqm-pie): IESG Evaluation » Approved-announcement to be sent::Revised I-D Needed
By Rong Pan, Preethi Natarajan, Fred Baker, 2016-04-19 TXT HTML PDF
Abstract: Bufferbloat is a phenomenon where excess buffers in the network cause high latency and jitter. As more and more interactive applications (e.g. voice over IP, real time video streaming and financial transactions) run in the Internet, high latency and jitter degrade application performance. There is a pressing need to design intelligent queue management schemes that can control latency and jitter; and hence provide desirable quality of service to users.
- CDNI Request Routing: Footprint and Capabilities Semantics (draft-ietf-cdni-footprint-capabilities-semantics): IESG Evaluation » Approved-announcement to be sent::Point Raised - writeup needed
By Jan Seedorf, Jon Peterson, Stefano Previdi, Ray van Brandenburg, Kevin Ma, 2016-05-14 TXT HTML PDF
Abstract: This document captures the semantics of the "Footprint and Capabilities Advertisement" part of the CDNI Request Routing interface, i.e., the desired meaning of "Footprint" and "Capabilities" in the CDNI context, and what the "Footprint and Capabilities Advertisement Interface (FCI)" offers within CDNI. The document also provides guidelines for the CDNI FCI protocol. It further defines a Base Advertisement Object, the necessary registries for capabilities and footprints, and guidelines on how these registries can be extended in the future.
- CDNI Logging Interface (draft-ietf-cdni-logging): IESG Evaluation » ::Revised I-D Needed
By Francois Le Faucheur, Gilles Bertrand, Iuniana Oprescu, Roy Peterkofsky, 2016-04-07 TXT HTML PDF
Abstract: This memo specifies the Logging interface between a downstream CDN (dCDN) and an upstream CDN (uCDN) that are interconnected as per the CDN Interconnection (CDNI) framework. First, it describes a reference model for CDNI logging. Then, it specifies the CDNI Logging File format and the actual protocol for exchange of CDNI Logging Files.
- The YANG 1.1 Data Modeling Language (draft-ietf-netmod-rfc6020bis): Waiting for Writeup » Approved-announcement to be sent::Point Raised - writeup needed
By Martin Bjorklund, 2016-04-28 TXT HTML PDF
Abstract: YANG is a data modeling language used to model configuration data, state data, remote procedure calls, and notifications for network management protocols. This document also specifies the YANG mappings to the Network Configuration Protocol (NETCONF).
- The Profile for Algorithms and Key Sizes for use in the Resource Public Key Infrastructure (draft-ietf-sidr-rfc6485bis): Publication Requested » In Last Call
By Geoff Huston, George Michaelson, 2016-03-08 TXT HTML PDF
Abstract: This document specifies the algorithms, algorithms' parameters, asymmetric key formats, asymmetric key size, and signature format for the Resource Public Key Infrastructure (RPKI) subscribers that generate digital signatures on certificates, Certificate Revocation Lists (CRLs), Cryptographic Message Syntax (CMS) signed objects and certification requests as well as for the relying parties (RPs) that verify these digital signatures.
- Securing RPSL Objects with RPKI Signatures (draft-ietf-sidr-rpsl-sig): IESG Evaluation » Approved-announcement to be sent
By kistel, Brian Haberman, 2016-05-19 TXT HTML PDF
Abstract: This document describes a method to allow parties to electronically sign Routing Policy Specification Language objects and validate such electronic signatures. This allows relying parties to detect accidental or malicious modifications on such objects. It also allows parties who run Internet Routing Registries or similar databases, but do not yet have Routing Policy System Security-based authentication of the maintainers of certain objects, to verify that the additions or modifications of such database objects are done by the legitimate holder(s) of the Internet resources mentioned in those objects. This document updates RFC 2622 and RFC 4012 to add the signature attribute to supported RPSL objects.
- Problem Statement and Architecture for Information Exchange Between Interconnected Traffic Engineered Networks (draft-ietf-teas-interconnected-te-info-exchange): IESG Evaluation » ::AD Followup
By Adrian Farrel, John Drake, Nabil Bitar, George Swallow, Daniele Ceccarelli, Xian Zhang, 2016-05-10 TXT HTML PDF
Abstract: In Traffic Engineered (TE) systems, it is sometimes desirable to establish an end-to-end TE path with a set of constraints (such as bandwidth) across one or more network from a source to a destination. TE information is the data relating to nodes and TE links that is used in the process of selecting a TE path. TE information is usually only available within a network. We call such a zone of visibility of TE information a domain. An example of a domain may be an IGP area or an Autonomous System.
- Transport Layer Security (TLS) False Start (draft-ietf-tls-falsestart): IESG Evaluation » Approved-announcement to be sent
By Adam Langley, Nagendra Modadugu, Bodo Moeller, 2016-05-11 TXT HTML PDF
Abstract: This document specifies an optional behavior of TLS client implementations, dubbed False Start. It affects only protocol timing, not on-the-wire protocol data, and can be implemented unilaterally. A TLS False Start reduces handshake latency to one round trip.
- DSCP Packet Markings for WebRTC QoS (draft-ietf-tsvwg-rtcweb-qos): IESG Evaluation » Approved-announcement to be sent::Point Raised - writeup needed
By Paul Jones, Subha Dhesikan, Cullen Jennings, Dan Druta, 2016-05-11 TXT HTML PDF
Abstract: Many networks, such as service provider and enterprise networks, can provide different forwarding treatments for individual packets based on Differentiated Services Code Point (DSCP) values on a per-hop basis. This document provides the recommended DSCP values for web browsers to use for various classes of WebRTC traffic.
- Guidelines for Writing an IANA Considerations Section in RFCs (draft-leiba-cotton-iana-5226bis): Waiting for AD Go-Ahead » IESG Evaluation
By Michelle Cotton, Barry Leiba, Thomas Narten, 2016-04-05 TXT HTML PDF
Abstract: Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values used in these fields do not have conflicting uses, and to promote interoperability, their allocation is often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).
Drafts Sent to RFC Editor
- Requirements for Subscription to YANG Datastores (draft-ietf-i2rs-pub-sub-requirements): Approved-announcement sent » RFC Ed Queue
By Eric Voit, Alex Clemm, Alberto Prieto, 2016-05-17 TXT HTML PDF
Abstract: This document provides requirements for a service that allows client applications to subscribe to updates of a YANG datastore. Based on criteria negotiated as part of a subscription, updates will be pushed to targeted recipients. Such a capability eliminates the need for periodic polling of YANG datastores by applications and fills a functional gap in existing YANG transports (i.e., Netconf and Restconf). Such a service can be summarized as a "pub/sub" service for YANG datastore updates. Beyond a set of basic requirements for the service, various refinements are addressed. These refinements include: periodicity of object updates, filtering out of objects underneath a requested a subtree, and delivery QoS guarantees.
- Interface to the Routing System (I2RS) Traceability: Framework and Information Model (draft-ietf-i2rs-traceability): Approved-announcement sent » RFC Ed Queue
By Joe Clarke, Gonzalo Salgueiro, Carlos Pignataro, 2016-05-18 TXT HTML PDF
Abstract: This document describes a framework for traceability in the Interface to the Routing System (I2RS) and information model for that framework. It specifies the motivation, requirements, use cases, and defines an information model for recording interactions between elements implementing the I2RS protocol. This framework provides a consistent tracing interface for components implementing the I2RS architecture to record what was done, by which component, and when. It aims to improve the management of I2RS implementations, and can be used for troubleshooting, auditing, forensics, and accounting purposes.
Other Status Changes
RFC Editor Status Changes
- RFC6374 UDP Return Path (draft-ietf-mpls-rfc6374-udp-return-path): » AUTH48
By Stewart Bryant, Siva Sivabalan, Sagar Soni, 2016-04-07 TXT HTML PDF
Abstract: RFC6374 defines a protocol for Packet Loss and Delay Measurement for MPLS networks (MPLS-PLDM). This document specifies the procedures to be used when sending and processing out-of-band MPLS performance management responses over an IP/UDP return path.
IPR Disclosures
IESG/IAB/IAOC/Trust Minutes
Liaison Statements
Classified Ads
|
WGs marked with an 
