IETF-Announce List
![[Feed]](feedicon16.png) New RFCs
New and Revived Drafts
- MISP object template format (draft-dulaunoy-misp-object-template-format)
By Alexandre Dulaunoy, Andras Iklody, 2018-10-15 TXT HTML PDF
Abstract: This document describes the MISP object template format which describes a simple JSON format to represent the various templates used to construct MISP objects. A public directory of common vocabularies MISP object templates [MISP-O] is available and relies on the MISP object reference format.
- BIER Underlay Path Calculation Algorithm and Contraints (draft-ietf-bier-bar-ipa)
By Zhaohui Zhang, Tony Przygienda, Andrew Dolganow, Hooman Bidgoli, IJsbrand Wijnands, Arkadiy Gulko, 2018-10-16 TXT HTML PDF
Abstract: This document specifies general rules for interaction between the BAR and IPA fields defined in [RFC8401] and [I-D.ietf-bier-ospf-bier-extensions].
- BGP-LS extensions for Segment Routing BGP Egress Peer Engineering (draft-ietf-idr-bgpls-segment-routing-epe)
By Stefano Previdi, Ketan Talaulikar, Clarence Filsfils, Keyur Patel, Saikat Ray, Jie Dong, 2018-10-15 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.
- Path Aware Networking: Obstacles to Deployment (A Bestiary of Roads Not Taken) (draft-irtf-panrg-what-not-to-do)
By Spencer Dawkins, 2018-10-15 TXT HTML PDF
Abstract: At the first meeting of the Path Aware Networking Research Group, Oliver Bonaventure led a discussion of mostly-unsuccessful attempts to exploit Path Awareness to achieve a variety of goals, for a variety of reasons, over the past decade. At the end of that discussion, the research group agreed to catalog and analyze these ideas, in order to extract insights and lessons for path-aware networking researchers.
- Service Function Chaining: Subscriber and Policy Identification Variable-Length Network Service Header (NSH) Context Headers (draft-sfc-serviceid-header)
By Behcet Sarikaya, Mohamed Boucadair, Dirk Hugo, 2018-10-16 TXT HTML PDF
Abstract: This document discusses how to inform Service Functions about subscriber- and service-related information for the sake of policy enforcement and appropriate service function chaining operations.
Updated Drafts
- Configuration of Advanced Security Functions with I2NSF Security Controller (draft-dong-i2nsf-asf-config)
By Wei Pan, Liang Xia, 2018-10-15 TXT HTML PDF
Abstract: This draft defines a network security function (NSF-) facing interface of the security controller for the purpose of configuring some advanced security functions. These advanced security functions include antivirus, anti-ddos, and intrusion prevention system (IPS). The interface is presented in a YANG data model fashion and can be used to deploy a large amount of NSF blocks that all support above mentioned functions in the software defined network (SDN) based paradigm.
- LISP Geo-Coordinate Use-Cases (draft-farinacci-lisp-geo)
By Dino Farinacci, 2018-10-15 TXT HTML PDF
Abstract: This draft describes how Geo-Coordinates can be used in the LISP Architecture and Protocols.
- Flexible Session Protocol (draft-gao-flexible-session-protocol)
By Jason Gao, 2018-10-16 TXT HTML PDF
Abstract: FSP is a connection-oriented transport layer protocol that provides mobility and multihoming support by introducing the concept of 'upper layer thread ID', which is associated with some shared secret that is applied to protect authenticity of the origin of the FSP packets.
- Extensible Provisioning Protocol (EPP) Internationalized Domain Name (IDN) Table Mapping (draft-gould-idn-table)
By James Gould, Francisco Obispo, 2018-10-15 TXT HTML PDF
Abstract: This document describes an Extensible Provisioning Protocol (EPP) mapping for getting Internationalized Domain Name (IDN) Table information for the registration of IDNs, using the EPP domain name mapping, and optionally with the IDN mapping extension. An IDN Table defines the valid set of characters (code points) that can be used in a domain name. Code points may overlap across IDN Tables and the IDN Tables supported by the servers are up to server policy.
- Packet Delivery Deadline time in 6LoWPAN Routing Header (draft-ietf-6lo-deadline-time)
By Lijo Thomas, Satish Anamalamudi, S.V.R Anand, Malati Hegde, Charles Perkins, 2018-10-15 TXT HTML PDF
Abstract: This document specifies a new type for the 6LoWPAN routing header containing the delivery deadline time for data packets. The deadline time enables forwarding and scheduling decisions for time critical IoT M2M applications that need deterministic delay guarantees over constrained networks and operate within time-synchronized networks.
- Deprecating RC4 in Secure Shell (SSH) (draft-ietf-curdle-rc4-die-die-die)
By Luis Camara, Loganaden Velvindron, 2018-10-15 TXT HTML PDF
Abstract: This document deprecates RC4 in Secure Shell (SSH). Therefore, this document formally obsoletes and moves to Historic RFC4345.
- Ed25519 and Ed448 public key algorithms for the Secure Shell (SSH) protocol (draft-ietf-curdle-ssh-ed25519-ed448)
By Ben Harris, Loganaden Velvindron, 2018-10-15 TXT HTML PDF
Abstract: This document describes the use of the Ed25519 and Ed448 digital signature algorithm in the Secure Shell (SSH) protocol.
- Secret Key Transaction Authentication for DNS (TSIG) (draft-ietf-dnsop-rfc2845bis)
By Francis Dupont, Stephen Morris, Paul Vixie, Donald Eastlake, Olafur Gudmundsson, Brian Wellington, 2018-10-15 TXT HTML PDF
Abstract: This protocol allows for transaction level authentication using shared secrets and one way hashing. It can be used to authenticate dynamic updates as coming from an approved client, or to authenticate responses as coming from an approved name server.
- Device Pairing Using Short Authentication Strings (draft-ietf-dnssd-pairing)
By Christian Huitema, Daniel Kaiser, 2018-10-15 TXT HTML PDF
Abstract: This document proposes a device pairing mechanism that establishes a relation between two devices by agreeing on a secret and manually verifying the secret's authenticity using an SAS (short authentication string). Pairing has to be performed only once per pair of devices, as for a re-discovery at any later point in time, the exchanged secret can be used for mutual authentication.
- Privacy Extensions for DNS-SD (draft-ietf-dnssd-privacy)
By Christian Huitema, Daniel Kaiser, 2018-10-15 TXT HTML PDF
Abstract: DNS-SD (DNS Service Discovery) normally discloses information about both the devices offering services and the devices requesting services. This information includes host names, network parameters, and possibly a further description of the corresponding service instance. Especially when mobile devices engage in DNS Service Discovery over Multicast DNS at a public hotspot, a serious privacy problem arises.
- Route Target Constrained Distribution of Routes with no Route Targets (draft-ietf-idr-rtc-no-rt)
By Eric Rosen, Keyur Patel, Jeffrey Haas, Robert Raszuk, 2018-10-15 TXT HTML PDF
Abstract: There are a variety of BGP-enabled services in which the originator of a BGP route may attach one or more "Route Targets" to the route. By means of a procedure known as "RT Constrained Distribution" (RTC), a given BGP speaker (call it "B") can announce the set of RTs in which it has interest. The implication is that if a particular route (call it "R") carries any RTs at all, BGP speaker B wants to receive route R if and only if B has announced interest in one of the RTs carried by R. However, if route R does not carry any RTs at all, prior specifications do not make it clear whether B's use of RTC implies that it does not want to receive route R. This has caused interoperability problems in the field, as some implementations of RTC do not allow B to receive R, but some services presuppose that B will receive R. This document updates RFC 4684 by clarifying the effect of the RTC mechanism on routes that do not have any RTs.
- Simple Two-way Active Measurement Protocol (draft-ietf-ippm-stamp)
By Gregory Mirsky, Guo Jun, Henrik Nydell, Richard Foote, 2018-10-15 TXT HTML PDF
Abstract: This document describes a Simple Two-way Active Measurement Protocol which enables measurement of both one-way and round-trip performance metrics like delay, delay variation, and packet loss.
- LISP EID Anonymity (draft-ietf-lisp-eid-anonymity)
By Dino Farinacci, Padma Pillay-Esnault, Wassim Haddad, 2018-10-15 TXT HTML PDF
Abstract: This specification will describe how ephemeral LISP EIDs can be used to create source anonymity. The idea makes use of frequently changing EIDs much like how a credit-card system uses a different credit-card numbers for each transaction.
- LISP Traffic Engineering Use-Cases (draft-ietf-lisp-te)
By Dino Farinacci, Michael Kowal, Parantap Lahiri, 2018-10-15 TXT HTML PDF
Abstract: This document describes how LISP reencapsulating tunnels can be used for Traffic Engineering purposes. The mechanisms described in this document require no LISP protocol changes but do introduce a new locator (RLOC) encoding. The Traffic Engineering features provided by these LISP mechanisms can span intra-domain, inter-domain, or combination of both.
- Signaling RSVP-TE tunnels on a shared MPLS forwarding plane (draft-ietf-mpls-rsvp-shared-labels)
By Harish Sitaraman, Vishnu Beeram, Tejal Parikh, Tarek Saad, 2018-10-15 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.
- A YANG Data Model for NTP (draft-ietf-ntp-yang-data-model)
By Nan Wu, Dhruv Dhody, Ankit Sinha, N ANIL, Yi Zhao, 2018-10-15 TXT HTML PDF
Abstract: This document defines a YANG data model for Network Time Protocol (NTP) implementations. The data model includes configuration data and state data.
- OAuth 2.0 Security Best Current Practice (draft-ietf-oauth-security-topics)
By Torsten Lodderstedt, John Bradley, Andrey Labunets, Daniel Fett, 2018-10-15 TXT HTML PDF
Abstract: This document describes best current security practices for OAuth 2.0. It updates and extends the OAuth 2.0 Security Threat Model to incorporate practical experiences gathered since OAuth 2.0 was published and covers new threats relevant due to the broader application of OAuth 2.0.
- PCEP Extension for Flow Specification (draft-ietf-pce-pcep-flowspec)
By Dhruv Dhody, Adrian Farrel, Zhenbin Li, 2018-10-16 TXT HTML PDF
Abstract: The Path Computation Element (PCE) is a functional component capable of selecting the paths through a traffic engineered network. These paths may be supplied in response to requests for computation, or may be unsolicited instructions issued by the PCE to network elements. Both approaches use the PCE Communication Protocol (PCEP) to convey the details of the computed path.
- A YANG Data Model for Path Computation Element Communications Protocol (PCEP) (draft-ietf-pce-pcep-yang)
By Dhruv Dhody, Jonathan Hardwick, Vishnu Beeram, Jeff Tantsura, 2018-10-15 TXT HTML PDF
Abstract: This document defines a YANG data model for the management of Path Computation Element communications Protocol (PCEP) for communications between a Path Computation Client (PCC) and a Path Computation Element (PCE), or between two PCEs. The data model includes configuration data and state data (status information and counters for the collection of statistics).
- 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, 2018-10-16 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.
- Best Practices for Securing RTP Media Signaled with SIP (draft-ietf-sipbrandy-rtpsec)
By Jon Peterson, Richard Barnes, Russell Housley, 2018-10-15 TXT HTML PDF
Abstract: Although the Session Initiation Protocol (SIP) includes a suite of security services that has been expanded by numerous specifications over the years, there is no single place that explains how to use SIP to establish confidential media sessions. Additionally, existing mechanisms have some feature gaps that need to be identified and resolved in order for them to address the pervasive monitoring threat model. This specification describes best practices for negotiating confidential media with SIP, including both comprehensive protection solutions which bind the media to SIP-layer identities as well as opportunistic security solutions.
- BGP-Prefix Segment in large-scale data centers (draft-ietf-spring-segment-routing-msdc)
By Clarence Filsfils, Stefano Previdi, Gaurav Dawra, Ebben Aries, Petr Lapukhov, 2018-10-15 TXT HTML PDF
Abstract: This document describes the motivation and benefits for applying segment routing in BGP-based large-scale data-centers. It describes the design to deploy segment routing in those data-centers, for both the MPLS and IPv6 dataplanes.
- Session Traversal Utilities for NAT (STUN) (draft-ietf-tram-stunbis)
By Marc Petit-Huguenin, Gonzalo Salgueiro, Jonathan Rosenberg, Dan Wing, Rohan Mahy, Philip Matthews, 2018-10-15 TXT HTML PDF
Abstract: Session Traversal Utilities for NAT (STUN) is a protocol that serves as a tool for other protocols in dealing with Network Address Translator (NAT) traversal. It can be used by an endpoint to determine the IP address and port allocated to it by a NAT. It can also be used to check connectivity between two endpoints, and as a keep-alive protocol to maintain NAT bindings. STUN works with many existing NATs, and does not require any special behavior from them.
- Registration Data Access Protocol (RDAP) Reverse search capabilities (draft-loffredo-regext-rdap-reverse-search)
By Mario Loffredo, Maurizio Martinelli, 2018-10-16 TXT HTML PDF
Abstract: The Registration Data Access Protocol (RDAP) does not include query capabilities to find the list of domains related to a set of entities matching a given search pattern. Even if such capabilities, commonly referred to as reverse search, respond to some needs not yet readily fulfilled by the current Whois protocol, they have raised concern from two perspectives: server processing impact and data privacy. Anyway, the impact of the reverse queries on RDAP servers processing is the same of the standard searches and it can be reduced by implementing policies to deal with big result sets, while data privacy risks can be mitigated by RDAP access control functionalities. This document describes RDAP query extensions that allows clients to request a reverse search based on the domains- entities relationship.
- Use of TLS for Email Submission and Access (draft-lvelvindron-tls-for-email)
By Loganaden Velvindron, Stephen Farrell, 2018-10-15 TXT HTML PDF
Abstract: This specification updates current recommendation for the use of Transport Layer Security (TLS) protocol to provide confidentiality of email between a Mail User Agent (MUA) and a Mail Submission Server or Mail Access Server. This document updates RFC8314.
- Solution for Site Multihoming in a Real IP Environment (draft-shyam-site-multi)
By Shyam Bandyopadhyay, 2018-10-15 TXT HTML PDF
Abstract: This document provides a solution for Site Multihoming of stub networks in a real IP environment. Each user interface in a customer network may have as many global unicast addresses as many service providers it will be connected with. Users can establish multiple connections through different service providers simultaneously. Customer networks can maintain private address space to communicate within its users. Customer networks can provide IP mobility services as well.
- BIER MTU Discovery (draft-venaas-bier-mtud)
By Stig Venaas, IJsbrand Wijnands, Les Ginsberg, Mahesh Sivakumar, 2018-10-16 TXT HTML PDF
Abstract: This document defines an IGP based mechanism for discovering the MTU of a BIER sub-domain. This document defines extensions to OSPF and IS-IS, but other protocols could potentially be extended. MTU discovery is usually done for a given path, while this document defines it for a sub-domain. This allows the computed MTU to be independent of the set of receivers. Also, the MTU is independent of rerouting events within the sub-domain.
- The Sunset HTTP Header (draft-wilde-sunset-header)
By Erik Wilde, 2018-10-16 TXT HTML PDF
Abstract: This specification defines the Sunset HTTP response header field, which indicates that a URI is likely to become unresponsive at a specified point in the future. It also defines a sunset link relation type that allows linking to resources providing information about an upcoming resource or service sunset.
- Mobility Capability Negotiation and Protocol Selection (draft-yan-dmm-man)
By Zhiwei Yan, Guanggang Geng, Jong-Hyouk Lee, Anthony Chan, 2018-10-15 TXT HTML PDF
Abstract: Based on different requirements, multiple mobility management protocols have been developed. Different protocols have different functional requirements on the network element or the host and then a scheme should be used in order to support the negotiation and selection of adopted mobility management protocol when a host accesses to a new network. In this draft, this issue is analyzed.
- Service and Neighbor Discovery in ITS (draft-yan-ipwave-nd)
By Zhiwei Yan, Jong-Hyouk Lee, 2018-10-15 TXT HTML PDF
Abstract: For C-ACC, platooning and other typical use cases in ITS, direct IP communication between neighbor vehicles poses the following two issues: 1) how to discover the neighbor vehicle and the demanded service; and 2) how to discover the link-layer address of the neighbor vehicle and selected server. This draft presents a solution to these problems based on DNS-SD/mDNS [RFC6762][RFC6763].
Expired Drafts
- HTTP Overload Control Mechanism (draft-asveren-dispatch-http-overload-control)
By Tolga Asveren, 2018-04-14 TXT HTML PDF
Abstract: This document specifies a generic overload control mechanism for HTTP/HTTPS applications.
- draft-openpgp-iana-registry-updates
No title available; expired document? TXT HTML PDF
|
Drafts Sent to IESG
- Deprecating RC4 in Secure Shell (SSH) (draft-ietf-curdle-rc4-die-die-die): Active » Publication Requested
By Luis Camara, Loganaden Velvindron, 2018-10-15 TXT HTML PDF
Abstract: This document deprecates RC4 in Secure Shell (SSH). Therefore, this document formally obsoletes and moves to Historic RFC4345.
- Ed25519 and Ed448 public key algorithms for the Secure Shell (SSH) protocol (draft-ietf-curdle-ssh-ed25519-ed448): Active » Publication Requested
By Ben Harris, Loganaden Velvindron, 2018-10-15 TXT HTML PDF
Abstract: This document describes the use of the Ed25519 and Ed448 digital signature algorithm in the Secure Shell (SSH) protocol.
IESG Progress
- C-DNS: A DNS Packet Capture Format (draft-ietf-dnsop-dns-capture-format): Publication Requested » AD Evaluation
By John Dickinson, Jim Hague, Sara Dickinson, Terry Manderson, John Bond, 2018-08-10 TXT HTML PDF
Abstract: This document describes a data representation for collections of DNS messages. The format is designed for efficient storage and transmission of large packet captures of DNS traffic; it attempts to minimize the size of such packet capture files but retain the full DNS message contents along with the most useful transport metadata. It is intended to assist with the development of DNS traffic monitoring applications.
- IMAP REPLACE Extension (draft-ietf-extra-imap-replace): In Last Call » IESG Evaluation
By Stuart Brandt, 2018-10-12 TXT HTML PDF
Abstract: This document defines an IMAP extension which can be used to replace an existing message in a message store with a new message. Message replacement is a common operation for clients that automatically save drafts or notes as a user composes them.
- Sieve Extension: File Carbon Copy (Fcc) (draft-ietf-extra-sieve-fcc): Publication Requested » AD Evaluation::Revised I-D Needed
By Ken Murchison, Bron Gondwana, 2018-10-01 TXT HTML PDF
Abstract: The Sieve Email Filtering Language provides a number of action commands, some of which can generate additional messages on behalf of the user. This document defines an extension to such commands to allow a copy of any generated message to be filed into a target mailbox.
- DLEP Control Plane Based Pause Extension (draft-ietf-manet-dlep-pause-extension): Publication Requested » AD Evaluation
By Bow-Nan Cheng, David Wiggins, Lou Berger, 2018-06-15 TXT HTML PDF
Abstract: This document defines an extension to the DLEP protocol that enables a modem to use DLEP messages to pause and resume data traffic coming from its peer router.
- OSPFv3 Extensions for Segment Routing (draft-ietf-ospf-ospfv3-segment-routing-extensions): AD Evaluation » ::Revised I-D Needed
By Peter Psenak, Clarence Filsfils, Stefano Previdi, Hannes Gredler, Rob Shakir, Wim Henderickx, Jeff Tantsura, 2018-08-03 TXT HTML PDF
Abstract: Segment Routing (SR) allows 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).
- Signaling MSD (Maximum SID Depth) using OSPF (draft-ietf-ospf-segment-routing-msd): IESG Evaluation::AD Followup » Approved-announcement sent
By Jeff Tantsura, Uma Chunduri, Sam Aldrin, Peter Psenak, 2018-10-12 TXT HTML PDF
Abstract: This document defines a way for an Open Shortest Path First (OSPF) Router to advertise multiple types of supported Maximum SID(Segment Identifier) Depths (MSDs) at node and/or link granularity. Such advertisements allow entities (e.g., centralized controllers) to determine whether a particular SID stack can be supported in a given network. This document defines only one type of MSD, but defines an encoding that can support other MSD types. Here the term OSPF means both OSPFv2 and OSPFv3.
- PCEP extensions for GMPLS (draft-ietf-pce-gmpls-pcep-extensions): Publication Requested » In Last Call
By Cyril Margaria, Oscar de Dios, Fatai Zhang, 2018-09-27 TXT HTML PDF
Abstract: This memo provides extensions to the Path Computation Element communication Protocol (PCEP) for the support of GMPLS control plane.
- PCEP Extensions for Segment Routing (draft-ietf-pce-segment-routing): Publication Requested » In Last Call
By Siva Sivabalan, Clarence Filsfils, Jeff Tantsura, Wim Henderickx, Jonathan Hardwick, 2018-10-13 TXT HTML PDF
Abstract: Segment Routing (SR) enables any head-end node to select any path without relying on a hop-by-hop signaling technique (e.g., LDP or RSVP-TE). It depends only on "segments" that are advertised by Link- State Interior Gateway Protocols (IGPs). A Segment Routed Path can be derived from a variety of mechanisms, including an IGP Shortest Path Tree (SPT), explicit configuration, or a Path Computation Element (PCE). This document specifies extensions to the Path Computation Element Communication Protocol (PCEP) that allow a stateful PCE to compute and initiate Traffic Engineering (TE) paths, as well as a PCC to request a path subject to certain constraints and optimization criteria in SR networks.
- BGP-Prefix Segment in large-scale data centers (draft-ietf-spring-segment-routing-msdc): IESG Evaluation::Revised I-D Needed » ::AD Followup
By Clarence Filsfils, Stefano Previdi, Gaurav Dawra, Ebben Aries, Petr Lapukhov, 2018-10-15 TXT HTML PDF
Abstract: This document describes the motivation and benefits for applying segment routing in BGP-based large-scale data-centers. It describes the design to deploy segment routing in those data-centers, for both the MPLS and IPv6 dataplanes.
- The 'leaptofrogans' URI Scheme (draft-op3ft-leaptofrogans-uri-scheme): Expert Review » In Last Call
By Alexis Tamas, Benjamin Phister, Jean-Emmanuel Rodriguez, 2018-10-03 TXT HTML PDF
Abstract: This document describes the 'leaptofrogans' Uniform Resource Identifier (URI) scheme, which enables applications to launch Frogans Player on a given Frogans site. Frogans is a medium for publishing content and services on the Internet, defined as a generic software layer on the Internet. Frogans Player is software enabling end users to browse Frogans sites.
Drafts Sent to RFC Editor
Other Status Changes
- draft-dawkins-panrg-what-not-to-do: Active » Replaced by draft-irtf-panrg-what-not-to-do
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 
