IETF-Announce List
![[Feed]](feedicon16.png) New RFCs
New and Revived Drafts
- Human Rights Considerations of Internet Filtering (draft-elkins-hrpc-ifilter)
By Nalini Elkins, Barry Shein, Vittorio Bertola, 2018-10-17 TXT HTML PDF
Abstract: This document is a survey of the filtering of content. The focus is on the human rights involved as cited in the Universal Declaration of Human Rights" which is one of the foundational documents for HRPC. The recent years have seen an increase in content filtering for a variety of reasons including to further the aims of governments who wish to maintain their rule and suppress dissent but also to enforce cultural norms, human rights and compliance with the law. Filters also exist for security (botnets, malware etc.), user-defined policies (parental control, corporate blocking of social networks during work time, etc.), spam control, upload of copyrighted material and other reasons. This document is based on several real world considerations: the existence of national and regional sovereignty, Internet Service Providers (ISPs) and Content Distribution Networks (CDNs) that provide connectivity and content hosting services, Over- the-top (OTTs) and Content Delivery Platforms (CDPs) that play a disproportionate role in capturing the attention and "eyeballs" of many of the users of the Internet.
- A Vocabulary of Path Properties (draft-enghardt-panrg-path-properties)
By Theresa Enghardt, Cyrill Krahenbuhl, 2018-10-18 TXT HTML PDF
Abstract: This document defines and categorizes information about Internet paths that an endpoint might have or want to have. This information is expressed as properties of paths between two endpoints.
- Motivations and Design Choices of the Flexible Session Protocol (draft-gao-fsp-motivations)
By Jason Gao, 2018-10-17 TXT HTML PDF
Abstract: This document introduces the motivation to design the Flexible Session Protocol which supports mobility and multihoming at the transport layer. FSP is to avoid, if not to extirpate, the routing scalability problem in the IPv6 internetwork.
- Traffic Accounting for MPLS Segment Routing Paths (draft-hegde-spring-traffic-accounting-for-sr-paths)
By Shraddha Hegde, 2018-10-17 TXT HTML PDF
Abstract: Traffic statistics form an important part of operations and maintenance data that are used to create demand matrices and for capacity planning in networks. Segment Routing (SR) is a source routing paradigm that uses stack of labels to represent a path. The SR path specific state is not stored in any other node in the network except the head-end node of the SR path. Traffic statistics specific to each SR path are an important component of the data which helps the controllers to lay out the SR paths in a way that optimizes the use of network resources. SR paths are inherently ECMP aware.
- The "xml2rfc" version 3 Vocabulary (draft-iab-rfc7991bis)
By Paul Hoffman, 2018-10-17 TXT HTML PDF
Abstract: This document defines the "xml2rfc" version 3 vocabulary: an XML- based language used for writing RFCs and Internet-Drafts. It is heavily derived from the version 2 vocabulary that is also under discussion. This document obsoletes the earlier v3 grammar described in RFC 7991, which in turn obsoleted the v2 grammar in RFC 7749.
- CDNI Request Routing Extensions (draft-ietf-cdni-request-routing-extensions)
By Ori Finkelman, Sanjay Mishra, 2018-10-17 TXT HTML PDF
Abstract: The Open Caching working group of the Streaming Video Alliance is focused on the delegation of video delivery requests from commercial CDNs to a caching layer at the ISP. In that aspect, Open Caching is a specific use case of CDNI, where the commercial CDN is the upstream CDN (uCDN) and the ISP caching layer is the downstream CDN (dCDN). The extensions specified in this document to the CDNI Metadata and FCI interfaces are derived from requirements raised by Open Caching but are applicable to CDNI use cases in general.
- Promoting Compliance with Intellectual Property Rights (IPR) Disclosure Rules (draft-ietf-iasa2-rfc6702-bis)
By Russell Housley, Tim Polk, Peter Saint-Andre, 2018-10-17 TXT HTML PDF
Abstract: The disclosure process for intellectual property rights (IPR) in documents produced within the IETF stream is essential to the accurate development of community consensus. However, this process is not always followed by IETF participants. Regardless of the cause or motivation, noncompliance with IPR disclosure rules can delay or even derail completion of IETF specifications. This document describes some strategies for promoting compliance with the IPR disclosure rules. These strategies are primarily intended for use by area directors, working group chairs, and working group secretaries.
- DLEP Latency Range Extension (draft-ietf-manet-dlep-latency-extension)
By Bow-Nan Cheng, Lou Berger, 2018-10-17 TXT HTML PDF
Abstract: This document defines an extension to the DLEP protocol to provide the range of latency that may be experienced on a link.
- Requirements for Name Resolution Service in ICN (draft-irtf-icnrg-nrs-requirements)
By Jungha Hong, Taewan You, Yong-Geun Hong, Cedric Westphal, Ved Kafle, 2018-10-17 TXT HTML PDF
Abstract: This document discusses the motivation and requirements for Name Resolution Service (NRS) in ICN. The NRS in ICN is to translate an object name into some other information such as locator and another name which is used for forwarding the object request.
- Architectural Considerations of ICN using Name Resolution Service (draft-irtf-icnrg-nrsarch-considerations)
By Jungha Hong, Taewan You, Yong-Geun Hong, 2018-10-17 TXT HTML PDF
Abstract: This document discusses architectural considerations and implications of Information-Centric Networking (ICN) related to the usage of the Name Resolution Service (NRS). It describes how ICN architecture changes and what implications are in the routing system when NRS is utilized in ICN.
- Open Questions in Path Aware Networking (draft-irtf-panrg-questions)
By Brian Trammell, 2018-10-17 TXT HTML PDF
Abstract: This document poses open questions in path-aware networking, as a background for framing discussions in the Path Aware Networking proposed Research Group (PANRG). These are split into making properties of Internet paths available to endpoints, and allowing endpoints to select paths through the Internet for their traffic.
- Multicast Traceroute for MVPNs (draft-kebler-kurapati-l3vpn-mvpn-mtrace)
By Robert Kebler, Pavan Kurapati, Saud Asif, mankamana mishra, Stig Venaas, 2018-10-17 TXT HTML PDF
Abstract: Mtrace is a tool used to troubleshoot issues in a network deploying Multicast service. When multicast is used within a VPN service offering, the base Mtrace specification does not detect the failures. This document specifies a method of using multicast traceroute in a network offering Multicast in VPN service.
- Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Call Home (draft-reddy-dots-home-network)
By Reddy K, Joshi Harsha, Mohamed Boucadair, Jon Shallow, 2018-10-16 TXT HTML PDF
Abstract: This document presents 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.
- Constrained Join Proxy for Bootstrapping Protocols (draft-vanderstok-anima-constrained-join-proxy)
By Michael Richardson, Peter van der Stok, Panos Kampanakis, 2018-10-18 TXT HTML PDF
Abstract: This document defines a protocol to securely assign a pledge to an owner, using an intermediary node between pledge and owner. This intermediary node is known as a "constrained-join-proxy".
Updated Drafts
- IS-IS Extensions to Support Routing over IPv6 Dataplane (draft-bashandy-isis-srv6-extensions)
By Peter Psenak, Clarence Filsfils, Ahmed Bashandy, Bruno Decraene, Zhibo Hu, 2018-10-18 TXT HTML PDF
Abstract: Segment Routing (SR) allows for a flexible definition of end-to-end paths by encoding paths as sequences of topological sub-paths, called "segments". Segment routing architecture can be implemented over an MPLS data plane as well as an IPv6 data plane. This draft describes the IS-IS extensions required to support Segment Routing over an IPv6 data plane.
- Transport Network aware Mobility for 5G (draft-clt-dmm-tn-aware-mobility)
By Uma Chunduri, Renwei Li, Jeff Tantsura, Luis Contreras, Xavier de Foy, 2018-10-16 TXT HTML PDF
Abstract: This document specifies a framework and a mapping function for 5G mobile user plane with transport network slicing, integrated with Mobile Radio Access and a Virtualized Core Network. The integrated approach specified in a way to address all the mobility scenarios defined in [TS23.501] and to be backward compatible with LTE [TS.23.401-3GPP] network deployments.
- A Framework for Enhanced Virtual Private Networks (VPN+) (draft-dong-teas-enhanced-vpn)
By Jie Dong, Stewart Bryant, Zhenqiang Li, Takuya Miyasaka, 2018-10-18 TXT HTML PDF
Abstract: This document specifies a framework for using existing, modified and potential new networking technologies as components to provide an enhanced VPN (VPN+) service. The purpose is to enable virtual private networks (VPNs) to support the needs of new applications, particularly applications that are associated with 5G services. A network enhanced with these properties can form the underpinning of network slicing, but will also be of use in its own right.
- Extensions to WHois service to allow query on email identities (draft-emailwhois-pradeepkumarxplorer)
By pradeep xplorer, 2018-10-18 TXT HTML PDF
Abstract: This document describes the need for a WHois email address service similar to the internet domainname WHois service. Theres a need for a registered email address as opposed to non-registered email address to fight internet SPAM, as well as encouraging email use for personal, commercial and legal and all kinds of purposes.An internet user can have multiple email identities.
- Node Protection for SR-TE Paths (draft-hegde-spring-node-protection-for-sr-te-paths)
By Shraddha Hegde, Chris Bowers, Stephane Litkowski, Xiaohu Xu, Feng Xu, 2018-10-17 TXT HTML PDF
Abstract: Segment routing supports the creation of explicit paths using adjacency-sids, node-sids, and binding-sids. It is important to provide fast reroute (FRR) mechanisms to respond to failures of links and nodes in the Segment-Routed Traffic-Engineered(SR-TE) path. A point of local repair (PLR) can provide FRR protection against the failure of a link in an SR-TE path by examining only the first (top) label in the SR label stack. In order to protect against the failure of a node, a PLR may need to examine the second label in the stack as well in order to determine SR-TE path beyond the failed node. This document specifies how a PLR can use the first and second label in the label stack describing an SR-TE path to provide protection against node failures.
- An Architecture for IPv6 over the TSCH mode of IEEE 802.15.4 (draft-ietf-6tisch-architecture)
By Pascal Thubert, 2018-10-18 TXT HTML PDF
Abstract: This document describes a network architecture that provides low- latency, low-jitter and high-reliability packet delivery. It combines a high speed powered backbone and subnetworks using IEEE 802.15.4 time-slotted channel hopping (TSCH) to meet the requirements of LowPower wireless deterministic applications.
- An Optional Encoding of the BIFT-id Field in the non-MPLS BIER Encapsulation (draft-ietf-bier-non-mpls-bift-encoding)
By IJsbrand Wijnands, Xiaohu Xu, Hooman Bidgoli, 2018-10-18 TXT HTML PDF
Abstract: Bit Index Explicit Replication (BIER) is an architecture that provides optimal multicast forwarding through a "multicast domain", without requiring intermediate routers to maintain any per-flow state or to engage in an explicit tree-building protocol. The Multicast packet is encapsulated using a BIER Header and transported through an MPLS or non-MPLS network. When MPLS is used as the transport, the Bit Indexed Forwarding Table (BIFT) is identified by a MPLS Label. When non-MPLS transport is used, the BIFT is identified by a 20bit value. This document describes one way of encoding the 20bit value.
- PIM Signaling Through BIER Core (draft-ietf-bier-pim-signaling)
By Hooman Bidgoli, Andrew Dolganow, Jayant Kotalwar, Fengman Xu, mankamana mishra, Zhaohui Zhang, 2018-10-17 TXT HTML PDF
Abstract: Bit Index Explicit Replication (BIER) is an architecture that provides multicast forwarding through a "BIER domain" without requiring intermediate routers to maintain multicast related per-flow state. Neither does BIER require an explicit tree-building protocol for its operation. A multicast data packet enters a BIER domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs). The BFIR router adds a BIER header to the packet. Such header contains a bit-string in which each bit represents exactly one BFER to forward the packet to. The set of BFERs to which the multicast packet needs to be forwarded is expressed by the according set of bits switched on in BIER packet header.
- FFV1 Video Coding Format Version 0, 1, and 3 (draft-ietf-cellar-ffv1)
By Michael Niedermayer, Dave Rice, Jerome Martinez, 2018-10-18 TXT HTML PDF
Abstract: This document defines FFV1, a lossless intra-frame video encoding format. FFV1 is designed to efficiently compress video data in a variety of pixel formats. Compared to uncompressed video, FFV1 offers storage compression, frame fixity, and self-description, which makes FFV1 useful as a preservation or intermediate video format.
- FFV1 Video Coding Format Version 4 (draft-ietf-cellar-ffv1-v4)
By Michael Niedermayer, Dave Rice, Jerome Martinez, 2018-10-18 TXT HTML PDF
Abstract: This document defines FFV1, a lossless intra-frame video encoding format. FFV1 is designed to efficiently compress video data in a variety of pixel formats. Compared to uncompressed video, FFV1 offers storage compression, frame fixity, and self-description, which makes FFV1 useful as a preservation or intermediate video format.
- HTTP Caching (draft-ietf-httpbis-cache)
By Roy Fielding, Mark Nottingham, Julian Reschke, 2018-10-18 TXT HTML PDF
Abstract: The Hypertext Transfer Protocol (HTTP) is a stateless application- level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.
- HTTP/1.1 Messaging (draft-ietf-httpbis-messaging)
By Roy Fielding, Mark Nottingham, Julian Reschke, 2018-10-18 TXT HTML PDF
Abstract: The Hypertext Transfer Protocol (HTTP) is a stateless application- level protocol for distributed, collaborative, hypertext information systems. This document specifies the HTTP/1.1 message syntax, message parsing, connection management, and related security concerns.
- HTTP Semantics (draft-ietf-httpbis-semantics)
By Roy Fielding, Mark Nottingham, Julian Reschke, 2018-10-18 TXT HTML PDF
Abstract: The Hypertext Transfer Protocol (HTTP) is a stateless application- level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP: its architecture, terminology, the "http" and "https" Uniform Resource Identifier (URI) schemes, core request methods, request header fields, response status codes, response header fields, and content negotiation.
- Defining the Role and Function of IETF Protocol Parameter Registry Operators (draft-ietf-iasa2-rfc6220bis)
By Danny McPherson, Olaf Kolkman, John Klensin, Geoff Huston, IAB, 2018-10-18 TXT HTML PDF
Abstract: Many Internet Engineering Task Force (IETF) protocols make use of commonly defined values that are passed in messages or packets. To ensure consistent interpretation of these values between independent implementations, there is a need to ensure that the values and associated semantic intent are uniquely defined. The IETF uses registry functions to record assigned protocol parameter values and their associated semantic intentions. For each IETF protocol parameter, it is current practice for the IETF to delegate the role of Protocol Parameter Registry Operator to a nominated entity. This document provides a description of, and the requirements for, these delegated functions.
- Dissemination of Flow Specification Rules (draft-ietf-idr-rfc5575bis)
By Susan Hares, Christoph Loibl, Robert Raszuk, Danny McPherson, Martin Bacher, 2018-10-17 TXT HTML PDF
Abstract: This document defines a Border Gateway Protocol Network Layer Reachability Information (BGP NLRI) encoding format that can be used to distribute traffic Flow Specifications. This allows the routing system to propagate information regarding more specific components of the traffic aggregate defined by an IP destination prefix.
- IS-IS TE Attributes per application (draft-ietf-isis-te-app)
By Les Ginsberg, Peter Psenak, Stefano Previdi, Wim Henderickx, John Drake, 2018-10-17 TXT HTML PDF
Abstract: Existing traffic engineering related link attribute advertisements have been defined and are used in RSVP-TE deployments. 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.
- Use of the HSS/LMS Hash-based Signature Algorithm in the Cryptographic Message Syntax (CMS) (draft-ietf-lamps-cms-hash-sig)
By Russell Housley, 2018-10-17 TXT HTML PDF
Abstract: This document specifies the conventions for using the the HSS/LMS hash-based signature algorithm with the Cryptographic Message Syntax (CMS). The HSS/LMS algorithm is one form of hash-based digital signature; it is described in [HASHSIG].
- SDP-based Data Channel Negotiation (draft-ietf-mmusic-data-channel-sdpneg)
By Keith Drage, Maridi Makaraju, Juergen Stoetzer-Bradler, Richard Ejzak, Jerome Marcon, Roni Even, 2018-10-17 TXT HTML PDF
Abstract: The Real-Time Communication in WEB-browsers (RTCWeb) working group is charged to provide protocols to support direct interactive rich communications using audio, video, and data between two peers' web- browsers. For the support of data communication, the RTCWeb working group has in particular defined the concept of bi-directional data channels over SCTP (Stream Control Transmission Protocol), where each data channel might be used to transport other protocols, called subprotocols. Data channel setup can be done using either the in- band Data Channel Establishment Protocol (DCEP) or using some out-of- band non-DCEP protocol. This document specifies how the SDP (Session Description Protocol) offer/answer exchange can be used to achieve such an out-of-band non-DCEP negotiation. Even though data channels are designed for RTCWeb use initially, they may be used by other protocols like, but not limited to, the CLUE protocol (which is defined by the IETF "ControLling mUltiple streams for tElepresence" working group). This document is intended to be used wherever data channels are used.
- A YANG Data Model for MPLS Base (draft-ietf-mpls-base-yang)
By Tarek Saad, Kamran Raza, Rakesh Gandhi, Xufeng Liu, Vishnu Beeram, 2018-10-16 TXT HTML PDF
Abstract: This document contains a specification of the the MPLS base YANG model. The MPLS base YANG model serves as a base framework for configuring and managing an MPLS switching subsystem on an MPLS- enabled router. It is expected that other MPLS YANG models (e.g. MPLS LSP Static, LDP or RSVP-TE YANG models) will augment the MPLS base YANG model.
- NETCONF Extensions to Support the Network Management Datastore Architecture (draft-ietf-netconf-nmda-netconf)
By Martin Bjorklund, Juergen Schoenwaelder, Philip Shafer, Kent Watsen, Robert Wilton, 2018-10-17 TXT HTML PDF
Abstract: This document extends the NETCONF protocol defined in RFC 6241 in order to support the Network Management Datastore Architecture defined in RFC 8342.
- YANG Library (draft-ietf-netconf-rfc7895bis)
By Andy Bierman, Martin Bjorklund, Juergen Schoenwaelder, Kent Watsen, Robert Wilton, 2018-10-17 TXT HTML PDF
Abstract: This document describes a YANG library that provides information about the YANG modules, datastores, and datastore schemas used by a network management server. Simple caching mechanisms are provided to allow clients to minimize retrieval of this information. This version of the YANG library supports the Network Management Datastore Architecture by listing all datastores supported by a network management server and the schema that is used by each of these datastores.
- YANG Module Tags (draft-ietf-netmod-module-tags)
By Christian Hopps, Lou Berger, Dean Bogdanovic, 2018-10-17 TXT HTML PDF
Abstract: This document provides for the association of tags with YANG modules. The expectation is for such tags to be used to help classify and organize modules. A method for defining, reading and writing a modules tags is provided. Tags may be standardized and assigned during module definition; assigned by implementations; or dynamically defined and set by users. This document provides guidance to future model writers and, as such, this document updates [I-D.ietf-netmod-rfc6087bis].
- YANG Schema Mount (draft-ietf-netmod-schema-mount)
By Martin Bjorklund, Ladislav Lhotka, 2018-10-17 TXT HTML PDF
Abstract: This document defines a mechanism to add the schema trees defined by a set of YANG modules onto a mount point defined in the schema tree in some YANG module.
- Signaling MSD (Maximum SID Depth) using OSPF (draft-ietf-ospf-segment-routing-msd)
By Jeff Tantsura, Uma Chunduri, Sam Aldrin, Peter Psenak, 2018-10-18 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.
- OSPF Link Traffic Engineering (TE) Attribute Reuse (draft-ietf-ospf-te-link-attr-reuse)
By Peter Psenak, Acee Lindem, Les Ginsberg, Wim Henderickx, Jeff Tantsura, Hannes Gredler, John Drake, 2018-10-18 TXT HTML PDF
Abstract: Various link attributes have been defined in OSPF in the context of the MPLS Traffic Engineering (TE) and GMPLS. Many of these link attributes can be used for applications other than MPLS Traffic Engineering or GMPLS. This document defines how to distribute such attributes in OSPFv2 and OSPFv3 for applications other than MPLS Traffic Engineering or GMPLS.
- SRTP Double Encryption Procedures (draft-ietf-perc-double)
By Cullen Jennings, Paul Jones, Richard Barnes, Adam Roach, 2018-10-17 TXT HTML PDF
Abstract: In some conferencing scenarios, it is desirable for an intermediary to be able to manipulate some parameters in Real Time Protocol (RTP) packets, while still providing strong end-to-end security guarantees. This document defines a cryptographic transform for the Secure Real Time Protocol (SRTP) that uses two separate but related cryptographic operations to provide hop-by-hop and end-to-end security guarantees. Both the end-to-end and hop-by-hop cryptographic algorithms can utilize an authenticated encryption with associated data scheme or take advantage of future SRTP transforms with different properties.
- Encrypted Key Transport for DTLS and Secure RTP (draft-ietf-perc-srtp-ekt-diet)
By Cullen Jennings, John Mattsson, David McGrew, Dan Wing, Flemming Andreasen, 2018-10-17 TXT HTML PDF
Abstract: Encrypted Key Transport (EKT) is an extension to DTLS (Datagram Transport Layer Security) and Secure Real-time Transport Protocol (SRTP) that provides for the secure transport of SRTP master keys, rollover counters, and other information within SRTP. This facility enables SRTP for decentralized conferences by distributing a common key to all of the conference endpoints.
- PASSporT SHAKEN Extension (SHAKEN) (draft-ietf-stir-passport-shaken)
By Chris Wendt, Mary Barnes, 2018-10-17 TXT HTML PDF
Abstract: This document extends PASSporT, which is a token object that conveys cryptographically-signed information about the participants involved in communications, to include information defined as part of the SHAKEN specification from ATIS (Alliance for Telecommunications Industry Solutions) and the SIP Forum IP-NNI Joint Task Force. These extensions provide a level of confidence in the correctness of the originating identity for a telephone network that has communications coming from both STIR participating originating communications as well as communications that does not include STIR information.
- Requirements for IPv6 Customer Edge Routers to Support IPv4 Connectivity as-a-Service (draft-ietf-v6ops-transition-ipv4aas)
By Jordi Palet, Hans Liu, Masanobu Kawashima, 2018-10-16 TXT HTML PDF
Abstract: This document specifies the IPv4 service continuity requirements for an IPv6 Customer Edge (CE) router, either provided by the service provider or through the retail market.
- Roadmap to a Networkless World (draft-liu-nmrg-networkless-roadmap)
By Bing Liu, Brian Carpenter, 2018-10-17 TXT HTML PDF
Abstract: This document aims to illustrate possible approaches to make network management and operations more autonomic in several aspects. The ultimate goal is that the network could run all by itself, so that users and administrators may feel that there is no network to take care of at all (a.k.a. "Networkless"). The approaches are described in a form of different levels (inspired by the Self-Driven Car levels). The higher the level is, the more autonomic management capabilities the network would have.
- Hybrid Two-Step Performance Measurement Method (draft-mirsky-ippm-hybrid-two-step)
By Gregory Mirsky, Wang Lingqiang, Guo Zhui, 2018-10-17 TXT HTML PDF
Abstract: Development of, and advancements in, automation of network operations brought new requirements for measurement methodology. Among them is the ability to collect instant network state as the packet being processed by the networking elements along its path through the domain. This document introduces a new hybrid measurement method, referred to as hybrid two-step, as it separates the act of measuring and/or calculating the performance metric from the act of collecting and transporting network state.
- The Time Zone Information Format (TZif) (draft-murchison-tzdist-tzif)
By Arthur Olson, Paul Eggert, Ken Murchison, 2018-10-18 TXT HTML PDF
Abstract: This document defines the Time Zone Information Format (TZif) for representing and exchanging time zone information, independent of any particular service or protocol. Two MIME media types for this format are also defined.
- HTTP-initiated Network Tunnelling (HiNT) (draft-pardue-httpbis-http-network-tunnelling)
By Lucas Pardue, 2018-10-18 TXT HTML PDF
Abstract: The HTTP CONNECT method allows an HTTP client to initiate, via a proxy, a TCP-based tunnel to a single destination origin. This memo explores options for expanding HTTP-initiated Network Tunnelling (HiNT) to cater for diverse UDP and IP associations.
- GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.2 (draft-smyshlyaev-tls12-gost-suites)
By Stanislav Smyshlyaev, Dmitry Belyavsky, Markku-Juhani Saarinen, 2018-10-17 TXT HTML PDF
Abstract: This document specifies a set of cipher suites for the Transport Layer Security (TLS) protocol Version 1.2 to support the Russian cryptographic standard algorithms.
- Name-Based Service Function Forwarder (nSFF) component within SFC framework (draft-trossen-sfc-name-based-sff)
By Dirk Trossen, Debashish Purkayastha, Akbar Rahman, 2018-10-17 TXT HTML PDF
Abstract: Many stringent requirements are imposed on today's network, such as low latency, high availability and reliability in order to support several use cases such as IoT, Gaming, Content distribution, Robotics etc. Adoption of cloud and fog technology at the edge of the network allows operator to deploy a single "Service Function" to multiple "Execution locations". The decision to steer traffic to a specific location may change frequently based on load, proximity etc. Under the current SFC framework, steering traffic dynamically to the different execution end points require a specific 're-chaining', i.e., a change in the service function path reflecting the different IP endpoints to be used for the new execution points. In order to address this, we discuss separating the logical Service Function Path from the specific execution end points. This can be done by identifying the Service Functions using a name rather than a routable IP endpoint (or Layer 2 address). This draft describes the necessary extensions, additional functions and protocol details in SFF to handle name based relationships.
- Subscription to Multiple Stream Originators (draft-zhou-netconf-multi-stream-originators)
By Tianran Zhou, Guangying Zheng, Eric Voit, Alexander Clemm, Andy Bierman, 2018-10-18 TXT HTML PDF
Abstract: This document describes the distributed data collection mechanism that allows multiple data streams to be managed using a single subscription. Specifically, multiple data streams are pushed directly to the collector without passing through a broker for internal consolidation.
Expired Drafts
- draft-camelot-holy-grenade
No title available; expired document? TXT HTML PDF
- SimpleMetadata: An interoperable format for sharing metadata (draft-dorfner-core-simplemetadata)
By Ralf Dorfner, 2018-04-16 TXT HTML PDF
Abstract: This document describes a container format for storing serializable metadata. It shall provide the possibility to store and share any kind of metadata, including encryption support. The idea is to create an open, universal and interoperable standard for storing and distributing every kind of metadata independent from media type or file format.
- Poll-Based SET Token Delivery Using HTTP (draft-ietf-secevent-http-poll)
By Annabelle Backman, Michael Jones, Phil Hunt, Marius Scurtescu, Morteza Ansari, Anthony Nadalin, 2018-04-16 TXT HTML PDF
Abstract: This specification defines how a series of security event tokens (SETs) may be delivered to a previously registered receiver using HTTP POST over TLS initiated as a poll by the receiver. The specification also defines how delivery can be assured subject to the SET Token Receiver's need for assurance.
- OpenID Connect DNS-based Discovery (draft-sanz-openid-dns-discovery)
By Vittorio Bertola, Marcos Sanz, 2018-04-16 TXT HTML PDF
Abstract: The following document describes a DNS-based mechanism for a client to discover an OpenID Identity Provider given an Identifier of the End-User, as a complementary alternative to the existing WebFinger- based mechanism.
- In-situ OAM Data Type Extension (draft-song-ippm-ioam-data-extension)
By Haoyu Song, Tianran Zhou, 2018-04-16 TXT HTML PDF
Abstract: This document describes a proposal which extends in-situ OAM to support potential future standard tracing data in addition to those currently defined. We provide use cases to motivate our proposal and base the modifications on the latest in-situ OAM header format specification.
- In-situ OAM Data Validation Option (draft-song-ippm-ioam-data-validation-option)
By Haoyu Song, Tianran Zhou, 2018-04-16 TXT HTML PDF
Abstract: This document describes several potential performance scalability and capability issues when implementing in-situ OAM on heterogenous target network elements. The document proposes the corresponding solutions and modifications to the current in-situ OAM specification to mitigate the issues. Specifically, in-situ OAM is extended with data validation fields to cope with the node processing capability. We provide use cases to motivate our proposal and base the modifications on the current in-situ OAM header format specification.
|
Drafts Sent to IESG
IESG Progress
- Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams (draft-ietf-bfcpbis-rfc4583bis): In Last Call » IESG Evaluation
By Gonzalo Camarillo, Tom Kristensen, Christer Holmberg, 2018-10-01 TXT HTML PDF
Abstract: This document defines the Session Description Protocol (SDP) offer/ answer procedures for negotiating and establishing Binary Floor Control Protocol (BFCP) streams.
- Protocol for Controlling Multiple Streams for Telepresence (CLUE) (draft-ietf-clue-protocol): In Last Call » IESG Evaluation
By Roberta Presta, Simon Romano, 2018-09-21 TXT HTML PDF
Abstract: The CLUE protocol is an application protocol conceived for the description and negotiation of a telepresence session. The design of the CLUE protocol takes into account the requirements and the framework defined within the IETF CLUE working group. A companion document delves into CLUE signaling details, as well as on the SIP/ SDP session establishment phase. CLUE messages flow over the CLUE data channel, based on reliable and ordered SCTP over DTLS transport. Message details, together with the behavior of CLUE Participants acting as Media Providers and/or Media Consumers, are herein discussed.
- Session Signaling for Controlling Multiple Streams for Telepresence (CLUE) (draft-ietf-clue-signaling): In Last Call » IESG Evaluation
By Robert Hansen, Paul Kyzivat, Lennard Xiao, Christian Groves, 2017-11-20 TXT HTML PDF
Abstract: This document specifies how CLUE-specific signaling such as the CLUE protocol and the CLUE data channel are used in conjunction with each other and with existing signaling mechanisms such as SIP and SDP to produce a telepresence call.
- IS-IS Routing with Reverse Metric (draft-ietf-isis-reverse-metric): In Last Call » IESG Evaluation
By Naiming Shen, Shane Amante, Mikael Abrahamsson, 2018-10-16 TXT HTML PDF
Abstract: This document describes a mechanism to allow IS-IS routing to quickly and accurately shift traffic away from either a point-to-point or multi-access LAN interface during network maintenance or other operational events. This is accomplished by signaling adjacent IS-IS neighbors with a higher reverse metric, i.e., the metric towards the signaling IS-IS router.
- SDP-based Data Channel Negotiation (draft-ietf-mmusic-data-channel-sdpneg): AD Evaluation::Revised I-D Needed » ::AD Followup
By Keith Drage, Maridi Makaraju, Juergen Stoetzer-Bradler, Richard Ejzak, Jerome Marcon, Roni Even, 2018-10-17 TXT HTML PDF
Abstract: The Real-Time Communication in WEB-browsers (RTCWeb) working group is charged to provide protocols to support direct interactive rich communications using audio, video, and data between two peers' web- browsers. For the support of data communication, the RTCWeb working group has in particular defined the concept of bi-directional data channels over SCTP (Stream Control Transmission Protocol), where each data channel might be used to transport other protocols, called subprotocols. Data channel setup can be done using either the in- band Data Channel Establishment Protocol (DCEP) or using some out-of- band non-DCEP protocol. This document specifies how the SDP (Session Description Protocol) offer/answer exchange can be used to achieve such an out-of-band non-DCEP negotiation. Even though data channels are designed for RTCWeb use initially, they may be used by other protocols like, but not limited to, the CLUE protocol (which is defined by the IETF "ControLling mUltiple streams for tElepresence" working group). This document is intended to be used wherever data channels are used.
- YANG Schema Mount (draft-ietf-netmod-schema-mount): IESG Evaluation::Revised I-D Needed » ::AD Followup
By Martin Bjorklund, Ladislav Lhotka, 2018-10-17 TXT HTML PDF
Abstract: This document defines a mechanism to add the schema trees defined by a set of YANG modules onto a mount point defined in the schema tree in some YANG module.
- SRTP Double Encryption Procedures (draft-ietf-perc-double): AD Evaluation::Revised I-D Needed » Last Call Requested
By Cullen Jennings, Paul Jones, Richard Barnes, Adam Roach, 2018-10-17 TXT HTML PDF
Abstract: In some conferencing scenarios, it is desirable for an intermediary to be able to manipulate some parameters in Real Time Protocol (RTP) packets, while still providing strong end-to-end security guarantees. This document defines a cryptographic transform for the Secure Real Time Protocol (SRTP) that uses two separate but related cryptographic operations to provide hop-by-hop and end-to-end security guarantees. Both the end-to-end and hop-by-hop cryptographic algorithms can utilize an authenticated encryption with associated data scheme or take advantage of future SRTP transforms with different properties.
- Encrypted Key Transport for DTLS and Secure RTP (draft-ietf-perc-srtp-ekt-diet): AD Evaluation::Revised I-D Needed » Last Call Requested
By Cullen Jennings, John Mattsson, David McGrew, Dan Wing, Flemming Andreasen, 2018-10-17 TXT HTML PDF
Abstract: Encrypted Key Transport (EKT) is an extension to DTLS (Datagram Transport Layer Security) and Secure Real-time Transport Protocol (SRTP) that provides for the secure transport of SRTP master keys, rollover counters, and other information within SRTP. This facility enables SRTP for decentralized conferences by distributing a common key to all of the conference endpoints.
- Link Relation Types for Web Services (draft-wilde-service-link-rel): Publication Requested::External Party » AD Evaluation
By Erik Wilde, 2018-08-01 TXT HTML PDF
Abstract: Many resources provided on the Web are part of sets of resources that are provided in a context that is managed by one particular service provider. Often, these sets of resources are referred to as "Web Services" or "Web APIs". This specification defines link relations for representing relationships from those resources to ones that provide documentation, descriptions, or metadata for these Web services. Documentation is primarily intended for human consumers, whereas descriptions are primarily intended for automated consumers; metadata is supposed to be information about a service's context. It also defines a link relation to identify status resources that are used to represent operational information about service status.
- The Sunset HTTP Header (draft-wilde-sunset-header): Publication Requested::External Party » AD Evaluation
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.
Drafts Sent to RFC Editor
Other Status Changes
- draft-dong-icnrg-nrs-requirement: Expired » Replaced by draft-irtf-icnrg-nrs-requirements
No title available; expired document? TXT HTML PDF
- draft-finkelman-cdni-rr-sva-extensions: Active » Replaced by draft-ietf-cdni-request-routing-extensions
No title available; expired document? TXT HTML PDF
- draft-hong-icnrg-nrs-requirements: Expired » Replaced by draft-irtf-icnrg-nrsarch-considerations
No title available; expired document? TXT HTML PDF
- draft-iab-xml2rfc-v3-bis: Active » Replaced by draft-iab-rfc7991bis
No title available; expired document? TXT HTML PDF
- Network coding and satellites (draft-kuhn-nwcrg-network-coding-satellites): Active » Replaced by draft-irtf-nwcrg-network-coding-satellites
By Nicolas Kuhn, Emmanuel Lochin, 2018-07-02 TXT HTML PDF
Abstract: This memo presents the current deployment of network coding in some satellite telecommunications systems along with a discussion on the multiple opportunities to introduce these techniques at a wider scale.
RFC Editor Status Changes
IPR Disclosures
IESG/IAB/IAOC/Trust Minutes
Liaison Statements
Classified Ads
|
WGs marked with an 
