IETF-Announce List
![[Feed]](feedicon16.png) New RFCs
New and Revived Drafts
- Anchorless mobility management through hICN (hICN-AMM): Deployment options (draft-auge-dmm-hicn-mobility-deployment-options)
By Jordan Auge, Giovanna Carofiglio, Luca Muscariello, Michele Papalini, 2018-06-19 TXT HTML PDF
Abstract: A novel mobility management approach is described in [I-D.auge-dmm-hicn-mobility], that leverages routable location- independent identifiers (IDs) and an Information-Centric Networking (ICN) communication model integrated in IPv6, (also referred to as Hybrid ICN, hICN, [I-D.muscariello-intarea-hicn].
- PCEP extension to support Segment Routing Policy Candidate Paths (draft-barth-pce-segment-routing-policy-cp)
By Colby Barth, Mike Koldychev, Dhruv Dhody, Siva Sivabalan, 2018-06-18 TXT HTML PDF
Abstract: This document introduces a mechanism to specify an SR policy, as a collection of SR candidate paths. An SR policy is identified by <headend, color, destination end-point> tuple. An SR policy can be associated with one or more candidate paths where each candidate path is represented in PCEP by an LSP. This document proposes extension to PCEP to support association among candidate paths of a given SR policy. The mechanism proposed in this document is applicable to both MPLS and IPv6 data plane.
- Preferred Path Routing (PPR) in IS-IS (draft-chunduri-isis-preferred-path-routing)
By Uma Chunduri, Richard Li, Russ White, Jeff Tantsura, Luis Contreras, Yingzhen Qu, 2018-06-18 TXT HTML PDF
Abstract: This document specifies a Preferred Path Routing (PPR) mechanism to simplify the path description of data plane traffic in Segment Routing (SR) deployments. PPR aims to mitigate the MTU and data plane processing issues that may result from SR packet overheads; and also supports traffic measurement, accounting statistics and further attribute extensions along the paths. Preferred Path Routing is achieved through the addition of descriptions to IS-IS advertised prefixes, and mapping those to a PPR data-plane identifier.
- Preferred Path Routing (PPR) in IS-IS (draft-chunduri-lsr-isis-preferred-path-routing)
By Uma Chunduri, Richard Li, Russ White, Jeff Tantsura, Luis Contreras, Yingzhen Qu, 2018-06-18 TXT HTML PDF
Abstract: This document specifies a Preferred Path Routing (PPR) mechanism to simplify the path description of data plane traffic in Segment Routing (SR) deployments. PPR aims to mitigate the MTU and data plane processing issues that may result from SR packet overheads; and also supports traffic measurement, accounting statistics and further attribute extensions along the paths. Preferred Path Routing is achieved through the addition of descriptions to IS-IS advertised prefixes, and mapping those to a PPR data-plane identifier.
- Preferred Path Routing (PPR) in OSPF (draft-chunduri-lsr-ospf-preferred-path-routing)
By Uma Chunduri, Yingzhen Qu, Russ White, Jeff Tantsura, Luis Contreras, 2018-06-19 TXT HTML PDF
Abstract: This document specifies a Preferred Path Routing (PPR) mechanism to simplify the path description of data plane traffic in Segment Routing (SR) deployments with OSPFv2 and OSPFv3 protocols. PPR aims to mitigate the MTU and data plane processing issues that may result from SR packet overheads; and also supports traffic measurement, accounting statistics and further attribute extensions along the paths. Preferred Path Routing is achieved through the addition of descriptions to OSPF advertised prefixes, and mapping those to a PPR data-plane identifier.
- Preferred Path Routing (PPR) in OSPF (draft-chunduri-ospf-lsr-preferred-path-routing)
By Uma Chunduri, Yingzhen Qu, Russ White, Jeff Tantsura, Luis Contreras, 2018-06-18 TXT HTML PDF
Abstract: This document specifies a Preferred Path Routing (PPR) mechanism to simplify the path description of data plane traffic in Segment Routing (SR) deployments with OSPFv2 and OSPFv3 protocols. PPR aims to mitigate the MTU and data plane processing issues that may result from SR packet overheads; and also supports traffic measurement, accounting statistics and further attribute extensions along the paths. Preferred Path Routing is achieved through the addition of descriptions to OSPF advertised prefixes, and mapping those to a PPR data-plane identifier.
- IDNA2008 and Unicode 11.0.0 (draft-faltstrom-unicode11)
By Patrik Faltstrom, 2018-06-18 TXT HTML PDF
Abstract: This document describes changes between Unicode 6.3.0 and Unicode 11.0.0 in the context of IDNA2008. It further suggests for the IETF a path forward regarding ensuring IDNA2008 follows the evolution of the Unicode Standard.
- EVPN Virtual Ethernet Segment (draft-ietf-bess-evpn-virtual-eth-segment)
By Ali Sajassi, Patrice Brissette, Rick Schell, John Drake, Jorge Rabadan, 2018-06-19 TXT HTML PDF
Abstract: EVPN and PBB-EVPN introduce a family of solutions for multipoint Ethernet services over MPLS/IP network with many advanced capabilities among which their multi-homing capabilities. These solutions define two types of multi-homing for an Ethernet Segment (ES): 1) Single-Active and 2) All-Active, where an Ethernet Segment is defined as a set of links between the multi-homed device/network and the set of PE devices that they are connected to.
- Performance Measurement (PM) with Marking Method in Bit Index Explicit Replication (BIER) Layer (draft-ietf-bier-pmmm-oam)
By Gregory Mirsky, Lianshu Zheng, Mach Chen, Giuseppe Fioccola, 2018-06-19 TXT HTML PDF
Abstract: This document describes a hybrid performance measurement method for multicast service over Bit Index Explicit Replication (BIER) domain.
- OTN Tunnel YANG Model (draft-ietf-ccamp-otn-tunnel-model)
By zhenghaomian@huawei.com, Aihua Guo, Italo Busi, Anurag Sharma, Rajan Rao, Sergio Belotti, Victor Lopezalvarez, Yunbo Li, Yunbin Xu, 2018-06-19 TXT HTML PDF
Abstract: This document describes the YANG data model for OTN Tunnels.
- RSVP Extensions for RMR (draft-ietf-teas-rsvp-rmr-extension)
By Abhishek Deshmukh, Kireeti Kompella, 2018-06-19 TXT HTML PDF
Abstract: Rings are the most common topology in access and aggregation networks. However, the use of MPLS as the transport protocol for rings is very limited today. draft-ietf-mpls-rmr-02 describes a mechanism to handle rings efficiently using MPLS. This document describes the extensions to the RSVP protocol for signaling MPLS label switched paths in rings.
- Enterprise Profile for the Precision Time Protocol With Mixed Multicast and Unicast Messages (draft-ietf-tictoc-ptp-enterprise-profile)
By Doug Arnold, Heiko Gerstung, 2018-06-19 TXT HTML PDF
Abstract: This document describes a profile for the use of the Precision Time Protocol in an IPV4 or IPv6 Enterprise information system environment. The profile uses the End to End Delay Measurement Mechanism, allows both multicast and unicast Delay Request and Delay Response Messages.
- Internet Assigned Numbers Authority (IANA) Registration of the Session Initiation Protocol (SIP) Feature-Capability indicators (draft-jesske-sipcore-sip-tree-cap-indicators)
By Roland Jesske, 2018-06-18 TXT HTML PDF
Abstract: This document registers with IANA SIP Feature-Capability indicators in the "SIP Feature-Capability Indicator Registration Tree" of the IANA "Proxy-Feature Feature-Capability Indicator Trees" registry for use with the SIP Feature-Caps header field and defines their usage and interpretation.
- BGP FlowSpec Payload Matching (draft-khare-idr-bgp-flowspec-payload-match)
By Anurag Khare, John Scudder, 2018-06-18 TXT HTML PDF
Abstract: The rise in frequency, volume, and pernicious effects of DDoS attacks has elevated them from fare for the specialist to generalist press. Numerous reports detail the taxonomy of DDoS types, the varying motivations of their attackers, as well as the resulting business and reputation loss of their targets.
- MPLS Encapsulation for SFC NSH (draft-malis-mpls-sfc-encapsulation)
By Andrew Malis, Stewart Bryant, Joel Halpern, 2018-06-19 TXT HTML PDF
Abstract: This document describes how to use a Service Function Forwarder (SFF) Label (similar to a pseudowire label or VPN label) to indicate the presence of a Service Function Chaining (SFC) Network Service Header (NSH) between an MPLS label stack and the packet payload. This allows SFC packets using the NSH to be forwarded between SFFs over an MPLS network, and the selection between multiple SFFs in the destination node.
- BFD in Demand Mode over Point-to-Point MPLS LSP (draft-mirsky-bfd-mpls-demand)
By Gregory Mirsky, 2018-06-19 TXT HTML PDF
Abstract: This document describes procedures for using Bidirectional Forwarding Detection (BFD) in Demand mode to detect data plane failures in Multiprotocol Label Switching (MPLS) point-to-point Label Switched Paths.
- NTP Correction Field (draft-mlichvar-ntp-correction-field)
By Miroslav Lichvar, 2018-06-18 TXT HTML PDF
Abstract: This document specifies an extension field for the Network Time Protocol (NTP) which improves resolution of specific fields in the NTP header and allows network devices such as switches and routers to modify NTP packets with corrections to improve accuracy of the synchronization in the network.
- Deprecating TLSv1.0 and TLSv1.1 (draft-moriarty-tls-oldversions-diediedie)
By Kathleen Moriarty, Stephen Farrell, 2018-06-18 TXT HTML PDF
Abstract: This document [if approved] formally deprecates Transport Layer Security (TLS) versions 1.0 [RFC2246] and 1.1 [RFC4346] and moves these documents to the historic state. These versions lack support for current and recommended cipher suites, and various government and industry profiiles of applications using TLS now mandate avoiding these old TLS versions. TLSv1.2 has been the recommended version for IETF protocols since 2008, providing sufficient time to transition away from older versions. Products having to support older versions increase the attack surface unnecessarily and increase opportunities for misconfigurations. Supporting these older versions also requires additional effort for library and product maintenance.
- 5G-Core System Split Bearer's FILTER for Dual Access (draft-sfc-sinha-5g-bearer-filter-dual-access)
By Sunil Sinha, Amardeep Sinha, Harsh Chauhan, Manish Srivastava, 2018-06-18 TXT HTML PDF
Abstract: This document attempts the case for new work that need to be developed for 5G user to improve faster download and upload of user's data via FILTER mechanism to be implemented at UPF user plane data for dual-access outlining the poor radio coverage issue. FILTER template governs the user data split at UPF with maintaining agreed PCC rules to achieve required throughput.
- 5G IMS system supporting dual-Registration for Dual-Access (draft-sfc-sinha-5g-ims-dual-reg)
By Sunil Sinha, Amardeep Sinha, Amit Mishra, Manish Srivastava, 2018-06-18 TXT HTML PDF
Abstract: This document attempts the case for new work that need to be developed for 5G user to improve user reachability outlining the poor radio coverage issue with respect to voice and video services by IMS network. This document also outlines dual access capabilities of 5G user device and user is reachable on each access-type leading to faster user reachability.
Updated Drafts
- LISP Based FlowMapping for Scaling NFV (draft-barkai-lisp-nfv)
By Sharon Barkai, Dino Farinacci, David Meyer, Fabio Maino, Vina Ermagan, Alberto Rodriguez-Natal, Albert Cabellos-Aparicio, 2018-06-18 TXT HTML PDF
Abstract: This draft describes an RFC 6830 Locator ID Separation Protocol (LISP) based distributed flow-mapping-fabric for dynamic scaling of virtualized network functions (NFV). Network functions such as subscriber-management, content-optimization, security and quality of service, are typically delivered using proprietary hardware appliances embedded into the network as turn-key service-nodes or service-blades within routers. Next generation network functions are being implemented as pure software instances running on standard servers - unbundled virtualized components of capacity and functionality. LISP-SDN based flow-mapping, dynamically assembles these components to whole solutions by steering the right traffic in the right sequence to the right virtual function instance.
- Diameter Policy Groups and Sets (draft-bertz-dime-policygroups)
By Lyle Bertz, Mark Bales, 2018-06-18 TXT HTML PDF
Abstract: This document defines optional Diameter attributes for efficient policy provisioning.
- Diameter Predicted Units (draft-bertz-dime-predictunits)
By Lyle Bertz, 2018-06-18 TXT HTML PDF
Abstract: This document specifies the conveyance of predicted usage information for proper dimensioning of network services that use Diameter based authorization.
- Path Aware Networking: A Bestiary of Roads Not Taken (draft-dawkins-panrg-what-not-to-do)
By Spencer Dawkins, 2018-06-18 TXT HTML PDF
Abstract: At the first meeting of the proposed Path Aware Networking Research Group, Oliver Bonaventure led a discussion of our mostly-unsuccessful attempts to exploit Path Awareness to achieve a variety of goals, over the past decade. At the end of that discussion, the research group agreed to catalog and analyze these ideas, to extract insights and lessons for path-aware networking researchers.
- Segment routing for SD-WAN paths over hybrid networks (draft-dunbar-sr-sdwan-over-hybrid-networks)
By Linda Dunbar, Mehmet Toy, 2018-06-19 TXT HTML PDF
Abstract: This document describes a method for end-to-end (E2E) SD-WAN paths (most likely encrypted) to traverse specific list of network segments, some of which are SR enabled and others may be legacy networks that do not support SR, to achieve the desired optimal E2E quality.
- NSH and Segment Routing Integration for Service Function Chaining (SFC) (draft-guichard-sfc-nsh-sr)
By Jim Guichard, Haoyu Song, Jeff Tantsura, Joel Halpern, Wim Henderickx, Mohamed Boucadair, 2018-06-18 TXT HTML PDF
Abstract: This document describes two application scenarios where Network Service Header (NSH) and Segment Routing (SR) techniques can be deployed together to support Service Function Chaining (SFC) in an efficient manner while maintaining separation of the service and transport planes as originally intended by the SFC architecture.
- Registration Extensions for 6LoWPAN Neighbor Discovery (draft-ietf-6lo-rfc6775-update)
By Pascal Thubert, Erik Nordmark, Samita Chakrabarti, Charles Perkins, 2018-06-19 TXT HTML PDF
Abstract: This specification updates RFC 6775 - 6LoWPAN Neighbor Discovery, to clarify the role of the protocol as a registration technique, simplify the registration operation in 6LoWPAN routers, as well as to provide enhancements to the registration capabilities and mobility detection for different network topologies including the Routing Registrars performing routing for host routes and/or proxy Neighbor Discovery in a low power network.
- Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams (draft-ietf-bfcpbis-rfc4583bis)
By Gonzalo Camarillo, Tom Kristensen, Christer Holmberg, 2018-06-19 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.
- BFD for Multipoint Networks (draft-ietf-bfd-multipoint)
By Dave Katz, David Ward, Juniper Networks, Gregory Mirsky, 2018-06-18 TXT HTML PDF
Abstract: This document describes extensions to the Bidirectional Forwarding Detection (BFD) protocol for its use in multipoint and multicast networks.
- BFD Multipoint Active Tails. (draft-ietf-bfd-multipoint-active-tail)
By Dave Katz, David Ward, Juniper Networks, Gregory Mirsky, 2018-06-18 TXT HTML PDF
Abstract: This document describes active tail extensions to and updates the Bidirectional Forwarding Detection (BFD) protocol for multipoint networks.
- YANG Data Model for Bidirectional Forwarding Detection (BFD) (draft-ietf-bfd-yang)
By Reshad Rahman, Lianshu Zheng, Mahesh Jethanandani, Juniper Networks, Gregory Mirsky, 2018-06-18 TXT HTML PDF
Abstract: This document defines a YANG data model that can be used to configure and manage Bidirectional Forwarding Detection (BFD).
- Path Maximum Transmission Unit Discovery (PMTUD) for Bit Index Explicit Replication (BIER) Layer (draft-ietf-bier-path-mtu-discovery)
By Gregory Mirsky, Tony Przygienda, Andrew Dolganow, 2018-06-19 TXT HTML PDF
Abstract: This document describes Path Maximum Transmission Unit Discovery (PMTUD) in Bit Indexed Explicit Replication (BIER) layer.
- Ambisonics in an Ogg Opus Container (draft-ietf-codec-ambisonics)
By Jan Skoglund, Michael Graczyk, 2018-06-19 TXT HTML PDF
Abstract: This document defines an extension to the Opus audio codec to encapsulate coded ambisonics using the Ogg format. It also contains updates to RFC 7845 to reflect necessary changes in the description of channel mapping families.
- Protocol for Forwarding Policy Configuration (FPC) in DMM (draft-ietf-dmm-fpc-cpdp)
By Satoru Matsushima, Lyle Bertz, Marco Liebsch, Sri Gundavelli, Danny Moses, Charles Perkins, 2018-06-18 TXT HTML PDF
Abstract: This document describes a way, called Forwarding Policy Configuration (FPC) to manage the separation of data-plane and control-plane. FPC defines a flexible mobility management system using FPC agent and FPC client functions. A FPC agent provides an abstract interface to the data-plane. The FPC client configures data-plane nodes by using the functions and abstractions provided by the FPC agent for the data- plane nodes. The data-plane abstractions presented in this document are extensible in order to support many different types of mobility management systems and data-plane functions.
- Bootstrapping WebSockets with HTTP/2 (draft-ietf-httpbis-h2-websockets)
By Patrick McManus, 2018-06-18 TXT HTML PDF
Abstract: This document defines a mechanism for running the WebSocket Protocol (RFC 6455) over a single stream of an HTTP/2 connection.
- Postquantum Preshared Keys for IKEv2 (draft-ietf-ipsecme-qr-ikev2)
By Scott Fluhrer, David McGrew, Panos Kampanakis, Valery Smyslov, 2018-06-18 TXT HTML PDF
Abstract: The possibility of Quantum Computers pose a serious challenge to cryptography algorithms deployed widely today. IKEv2 is one example of a cryptosystem that could be broken; someone storing VPN communications today could decrypt them at a later time when a Quantum Computer is available. It is anticipated that IKEv2 will be extended to support quantum secure key exchange algorithms; however that is not likely to happen in the near term. To address this problem before then, this document describes an extension of IKEv2 to allow it to be resistant to a Quantum Computer, by using preshared keys.
- Split DNS Configuration for IKEv2 (draft-ietf-ipsecme-split-dns)
By Tommy Pauly, Paul Wouters, 2018-06-18 TXT HTML PDF
Abstract: This document defines two Configuration Payload Attribute Types for the IKEv2 protocol that add support for private DNS domains. These domains are intended to be resolved using DNS servers reachable through an IPsec connection, while leaving all other DNS resolution unchanged. This approach of resolving a subset of domains using non- public DNS servers is referred to as "Split DNS".
- Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Message Specification (draft-ietf-lamps-rfc5751-bis)
By Jim Schaad, Blake Ramsdell, Sean Turner, 2018-06-19 TXT HTML PDF
Abstract: This document defines Secure/Multipurpose Internet Mail Extensions (S/MIME) version 4.0. S/MIME provides a consistent way to send and receive secure MIME data. Digital signatures provide authentication, message integrity, and non-repudiation with proof of origin. Encryption provides data confidentiality. Compression can be used to reduce data size. This document obsoletes RFC 5751.
- Synonymous Flow Label Framework (draft-ietf-mpls-sfl-framework)
By Stewart Bryant, Mach Chen, Zhenbin Li, George Swallow, Siva Sivabalan, Gregory Mirsky, 2018-06-18 TXT HTML PDF
Abstract: RFC 8372 describes the requirement for introducing flow identities within the MPLS architecture. This document describes a method of accomplishing this by using a technique called Synonymous Flow Labels in which labels which mimic the behaviour of other labels provide the identification service. These identifiers can be used to trigger per-flow operations on the on the packet at the receiving label switching router.
- RESTCONF and HTTP Transport for Event Notifications (draft-ietf-netconf-restconf-notif)
By Eric Voit, Reshad Rahman, Einar Nilsen-Nygaard, Alexander Clemm, Andy Bierman, 2018-06-18 TXT HTML PDF
Abstract: This document defines RESTCONF, HTTP2, and HTTP1.1 bindings for the transport of subscription requests and corresponding push updates. Being subscribed may be either publisher defined event streams or nodes/subtrees of YANG Datastores.
- Customized Subscriptions to a Publisher's Event Streams (draft-ietf-netconf-subscribed-notifications)
By Eric Voit, Alexander Clemm, Alberto Prieto, Einar Nilsen-Nygaard, Ambika Tripathy, 2018-06-18 TXT HTML PDF
Abstract: This document defines a YANG data model and associated mechanisms enabling subscriber-specific subscriptions to a publisher's event streams. Applying these elements allows a subscriber to request for and receive a continuous, custom feed of publisher generated information.
- OSPF LLS Extensions for Local Interface ID Advertisement (draft-ietf-ospf-lls-interface-id)
By Peter Psenak, Ketan Talaulikar, Wim Henderickx, Padma Pillay-Esnault, 2018-06-19 TXT HTML PDF
Abstract: This draft describes the extensions to OSPF link-local signaling to advertise the Local Interface Identifier.
- PCEP Extensions for Establishing Relationships Between Sets of LSPs (draft-ietf-pce-association-group)
By Ina Minei, Edward Crabbe, Siva Sivabalan, Hariharan Ananthakrishnan, Dhruv Dhody, Yosuke Tanaka, 2018-06-18 TXT HTML PDF
Abstract: This document introduces a generic mechanism to create a grouping of LSPs in the context of a Path Computation Element (PCE). This grouping can then be used to define associations between sets of LSPs or between a set of LSPs and a set of attributes (such as configuration parameters or behaviors), and is equally applicable to the stateful PCE (active and passive modes) and the stateless PCE.
- Path Computation Element communication Protocol extension for associating Policies and LSPs (draft-ietf-pce-association-policy)
By Dhruv Dhody, Siva Sivabalan, Stephane Litkowski, Jeff Tantsura, Jonathan Hardwick, 2018-06-19 TXT HTML PDF
Abstract: This document introduces a simple mechanism to associate policies to a group of Label Switched Paths (LSPs) via an extension to the Path Computation Element (PCE) Communication Protocol (PCEP).
- Ability for a stateful PCE to request and obtain control of a LSP (draft-ietf-pce-lsp-control-request)
By Aswatnarayan Raghuram, Al Goddard, Chaitanya Yadlapalli, Jay Karthik, Siva Sivabalan, Jon Parker, Dhruv Dhody, 2018-06-18 TXT HTML PDF
Abstract: The stateful Path Computation Element (PCE) communication Protocol (PCEP) extensions provide stateful control of Multiprotocol Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE LSP) via PCEP, for a model where a Path Computation Client (PCC) delegates control over one or more locally configured LSPs to a stateful PCE. There are use-cases in which a stateful PCE may wish to request and obtain control of one or more LSPs from a PCC. This document describes a simple extension to stateful PCEP to achieve such an objective.
- Hierarchical Stateful Path Computation Element (PCE). (draft-ietf-pce-stateful-hpce)
By Dhruv Dhody, Young Lee, Daniele Ceccarelli, Jongyoon Shin, Daniel King, Oscar de Dios, 2018-06-18 TXT HTML PDF
Abstract: A Stateful Path Computation Element (PCE) maintains information on the current network state, including: computed Label Switched Path (LSPs), reserved resources within the network, and pending path computation requests. This information may then be considered when computing new traffic engineered LSPs, and for associated and dependent LSPs, received from Path Computation Clients (PCCs).
- PCEP Extensions for Associating Working and Protection LSPs with Stateful PCE (draft-ietf-pce-stateful-path-protection)
By Hariharan Ananthakrishnan, Siva Sivabalan, Colby Barth, Raveendra Torvi, Ina Minei, Edward Crabbe, Dhruv Dhody, 2018-06-19 TXT HTML PDF
Abstract: A stateful Path Computation Element (PCE) is capable of computing as well as controlling via Path Computation Element Protocol (PCEP) Multiprotocol Label Switching Traffic Engineering Label Switched Paths (MPLS LSP). Furthermore, it is also possible for a stateful PCE to create, maintain, and delete LSPs. This document describes PCEP extension to associate two or more LSPs to provide end-to-end path protection.
- PCEP Extensions for LSP scheduling with stateful PCE (draft-ietf-pce-stateful-pce-lsp-scheduling)
By Huaimo Chen, Zhuangyan, Qin Wu, Dhruv Dhody, Daniele Ceccarelli, 2018-06-18 TXT HTML PDF
Abstract: This document proposes a set of extensions needed to the stateful Path Computation Element (PCE) communication Protocol (PCEP), so as to enable Labeled Switched Path (LSP) scheduling for path computation and LSP setup/deletion based on the actual network resource usage duration of a traffic service in a centralized network environment as stated in [I-D.ietf-teas-scheduled-resources].
- Root initiated routing state in RPL (draft-ietf-roll-dao-projection)
By Pascal Thubert, Rahul Jadhav, James Pylakutty, 2018-06-19 TXT HTML PDF
Abstract: This document proposes a protocol extension to RPL that enables to install a limited amount of centrally-computed routes in a RPL graph, enabling loose source routing down a non-storing mode DODAG, or transversal routes inside the DODAG. As opposed to the classical route injection in RPL that are injected by the end devices, this draft enables the root of the DODAG to projects the routes that are needed on the nodes where they should be installed.
- NSH Context Header Allocation for Broadband (draft-ietf-sfc-nsh-broadband-allocation)
By Jeffrey Napper, Surendra Kumar, Praveen Muley, Wim Henderickx, Mohamed Boucadair, 2018-06-19 TXT HTML PDF
Abstract: This document provides a recommended allocation of Network Service Header (NSH) context headers within the broadband service provider network context. Both fixed and mobile deployments are considered.
- IPv4 Multicast over an IPv6 Multicast in Softwire Mesh Network (draft-ietf-softwire-mesh-multicast)
By Mingwei Xu, Yong Cui, Jianping Wu, Shu Yang, Chris Metz, 2018-06-18 TXT HTML PDF
Abstract: During the transition to IPv6, there will be scenarios where a backbone network internally running one IP address family (referred to as the internal IP or I-IP family), connects client networks running another IP address family (referred to as the external IP or E-IP family). In such cases, the I-IP backbone needs to offer both unicast and multicast transit services to the client E-IP networks.
- Using Conditional Router Advertisements for Enterprise Multihoming (draft-ietf-v6ops-conditional-ras)
By Jen Linkova, mstucchi@ripe.net, 2018-06-18 TXT HTML PDF
Abstract: This document discusses the most common scenarios of connecting an enterprise network to multiple ISPs using an address space assigned by an ISP. 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. The "ietf-rtgwg- enterprise-pa-multihoming" document 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 focuses on solving the general problem and on covering various complex use cases, this document adopts the approach proposed in the "ietf-rtgwg-enterprise-pa- multihoming" draft to provide a solution for a limited number of common use cases. In particular, the focus is on scenarios where an enterprise network has two Internet uplinks used either in primary/ backup mode or simultaneously and hosts in that network might not yet properly support multihoming as described in RFC8028.
- Handling Long Lines in Artwork in Drafts (draft-kwatsen-netmod-artwork-folding)
By Kent Watsen, Qin Wu, 2018-06-18 TXT HTML PDF
Abstract: This document introduces a simple and yet time-proven strategy for handling long lines in artwork in drafts using a backslash ('\') character where line-folding has occurred. The strategy works on any text based artwork, producing consistent results regardless the artwork content. Using a per-artwork header, the strategy is both self-documenting and enables automated reconstitution of the original artwork.
- Registration Data Access Protocol (RDAP) Query Parameters for Result Sorting and Paging (draft-loffredo-regext-rdap-sorting-and-paging)
By Mario Loffredo, Maurizio Martinelli, Scott Hollenbeck, 2018-06-18 TXT HTML PDF
Abstract: The Registration Data Access Protocol (RDAP) does not include core functionality for clients to provide sorting and paging parameters for control of large result sets. This omission can lead to unpredictable server processing of queries and client processing of responses. This unpredictability can be greatly reduced if clients can provide servers with their preferences for managing response values. This document describes RDAP query extensions that allow clients to specify their preferences for sorting and paging result sets.
- The Time Zone Information Format (TZif) (draft-murchison-tzdist-tzif)
By Arthur Olson, Paul Eggert, Ken Murchison, 2018-06-19 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. A MIME media type for this format is also defined.
- IPoE Client Health Checking (draft-patterson-intarea-ipoe-health)
By Richard Patterson, Mikael Abrahamsson, 2018-06-19 TXT HTML PDF
Abstract: PPP over Ethernet clients have the functionality to detect path unavailability by using PPP Keepalives. IP over Ethernet does not have this functionality, and it's not specified when an IP over Ethernet client should consider its WAN connectivity down, unless there is a physical layer link down event.
- LISP-OAM (Operations, Administration and Management): Use cases and requirements (draft-rodrigueznatal-lisp-oam)
By Alberto Rodriguez-Natal, Albert Cabellos-Aparicio, Marc Portoles-Comeras, Michael Kowal, Darrel Lewis, Fabio Maino, 2018-06-18 TXT HTML PDF
Abstract: This document describes Operations Administration and Management (OAM) use-cases and the requirements that they have towards the LISP architecture.
- IS-IS Routing for Spine-Leaf Topology (draft-shen-isis-spine-leaf-ext)
By Naiming Shen, Les Ginsberg, Sanjay Thyamagundalu, 2018-06-18 TXT HTML PDF
Abstract: This document describes a mechanism for routers and switches in a Spine-Leaf type topology to have non-reciprocal Intermediate System to Intermediate System (IS-IS) routing relationships between the leafs and spines. The leaf nodes do not need to have the topology information of other nodes and exact prefixes in the network. This extension also has application in the Internet of Things (IoT).
- On the Politics of Standards (draft-tenoever-hrpc-political)
By Niels ten Oever, Amelia Andersdotter, 2018-06-18 TXT HTML PDF
Abstract: The IETF cannot ordain which standards or protocols are to be used on network, but the standards developing process in the IETF has a normative effect. Among other things the standardisation work at the IETF has implications on what is perceived as technologically possible and useful where networking technologies are being deployed, and its standards output reflect was is considered by the technical community as feasible and good practice. Because mediates many aspects of modern life, and therefore contributes to the ordering of societies and communities, the consideration of the politics and (potential) impact of protocols should be part of the standardization and development process.
- Global Time Distribution in 6TiSCH Networks (draft-vilajosana-6tisch-globaltime)
By Xavier Vilajosana, Pere Tuset, Borja Martinez, Jonathan Munoz, 2018-03-01 TXT HTML PDF
Abstract: This specification defines an optional extension to the Join Response message defined by the Minimal Security Framework for 6TiSCH. The extension aims at providing global time distribution support so nodes in the 6TiSCH network can exploit global time information instead of relying only in relative network time based on the Absolute Sequence Number (ASN). The specification also defines a mechanism for resynchronization, to handle leap seconds or to enable periodic global time updates relying on a CoAP service.
- Base Notifications for NMDA (draft-wu-netconf-base-notification-nmda)
By Qin Wu, Rohit Ranade, 2018-06-19 TXT HTML PDF
Abstract: The Network Configuration Protocol (NETCONF) provides mechanisms to manipulate configuration datastores. NMDA introduces additional datastores for systems that support more advanced processing chains converting configuration to operational state. However, client applications are not able to be aware of common events pertaining to additional datstores, such as a data validation state change in NETCONF server, that may impact management applications. This document updates [RFC6470] to allow a NETCONF client to receive additional notifications for some common system events pertaining to the Network Management Datastore Architecture (NMDA) defined in [RFC8342].
- PCEP Procedures and Protocol Extensions for Using PCE as a Central Controller (PCECC) of LSPs (draft-zhao-pce-pcep-extension-for-pce-controller)
By Quintin Zhao, Zhenbin Li, Dhruv Dhody, Satish Karunanithi, Adrian Farrel, Chao Zhou, 2018-06-18 TXT HTML PDF
Abstract: The Path Computation Element (PCE) is a core component of Software- Defined Networking (SDN) systems. It can compute optimal paths for traffic across a network and can also update the paths to reflect changes in the network or traffic demands.
- PCEP Procedures and Protocol Extensions for Using PCE as a Central Controller (PCECC) of SR-LSPs (draft-zhao-pce-pcep-extension-pce-controller-sr)
By Quintin Zhao, Zhenbin Li, Dhruv Dhody, Satish Karunanithi, Adrian Farrel, Chao Zhou, 2018-06-18 TXT HTML PDF
Abstract: The Path Computation Element (PCE) is a core component of Software- Defined Networking (SDN) systems. It can compute optimal paths for traffic across a network and can also update the paths to reflect changes in the network or traffic demands.
Expired Drafts
- draft-boucadair-connectivity-provisioning-protocol
No title available; expired document? TXT HTML PDF
|
Drafts Sent to IESG
IESG Progress
- Framework for EVPN Designated Forwarder Election Extensibility (draft-ietf-bess-evpn-df-election-framework): Publication Requested » AD Evaluation
By Jorge Rabadan, satyamoh@cisco.com, Ali Sajassi, John Drake, Kiran Nagaraj, Senthil Sathappan, 2018-05-24 TXT HTML PDF
Abstract: The Designated Forwarder (DF) in EVPN networks is the PE responsible for sending broadcast, unknown unicast and multicast (BUM) traffic to a multi-homed CE, on a given VLAN on a particular Ethernet Segment (ES). The DF is selected out of a list of candidate PEs that advertise the same Ethernet Segment Identifier (ESI) to the EVPN network. By default, EVPN uses a DF Election algorithm referred to as "Service Carving" and it is based on a modulus function (V mod N) that takes the number of PEs in the ES (N) and the VLAN value (V) as input. This default DF Election algorithm has some inefficiencies that this document addresses by defining a new DF Election algorithm and a capability to influence the DF Election result for a VLAN, depending on the state of the associated Attachment Circuit (AC). In addition, this document creates a registry with IANA, for future DF Election Algorithms and Capabilities. It also presents a formal definition and clarification of the DF Election Finite State Machine.
- (PBB-)EVPN Seamless Integration with (PBB-)VPLS (draft-ietf-bess-evpn-vpls-seamless-integ): Publication Requested » AD Evaluation
By Ali Sajassi, Samer Salam, Nick Regno, Jorge Rabadan, 2018-04-25 TXT HTML PDF
Abstract: This draft specifies procedures for backward compatibility of the (PBB-)EVPN solution with (PBB-)VPLS and provides mechanisms for seamless integration of the two technologies in the same MPLS/IP network on a per-VPN-instance basis. Implementation of this draft enables service providers to introduce (PBB-)EVPN PEs in their brown- field deployments of (PBB-)VPLS networks.
- Explicit Tracking with Wild Card Routes in Multicast VPN (draft-ietf-bess-mvpn-expl-track): Publication Requested » AD Evaluation
By Andrew Dolganow, Jayant Kotalwar, Eric Rosen, Zhaohui Zhang, 2018-04-19 TXT HTML PDF
Abstract: The MVPN specifications provide procedures to allow a multicast ingress node to invoke "explicit tracking" for a multicast flow or set of flows, thus learning the egress nodes for that flow or set of flows. However, the specifications are not completely clear about how the explicit tracking procedures work in certain scenarios. This document provides the necessary clarifications. It also specifies a new, optimized explicit tracking procedure. This new procedure allows an ingress node, by sending a single message, to request explicit tracking of each of a set of flows, where the set of flows is specified using a wildcard mechanism. This document updates RFCs 6514, 6625, and 7524.
- BFD for Multipoint Networks (draft-ietf-bfd-multipoint): Waiting for Writeup » IESG Evaluation
By Dave Katz, David Ward, Juniper Networks, Gregory Mirsky, 2018-06-18 TXT HTML PDF
Abstract: This document describes extensions to the Bidirectional Forwarding Detection (BFD) protocol for its use in multipoint and multicast networks.
- BFD Multipoint Active Tails. (draft-ietf-bfd-multipoint-active-tail): In Last Call » IESG Evaluation
By Dave Katz, David Ward, Juniper Networks, Gregory Mirsky, 2018-06-18 TXT HTML PDF
Abstract: This document describes active tail extensions to and updates the Bidirectional Forwarding Detection (BFD) protocol for multipoint networks.
- YANG Data Model for Bidirectional Forwarding Detection (BFD) (draft-ietf-bfd-yang): Waiting for Writeup » IESG Evaluation
By Reshad Rahman, Lianshu Zheng, Mahesh Jethanandani, Juniper Networks, Gregory Mirsky, 2018-06-18 TXT HTML PDF
Abstract: This document defines a YANG data model that can be used to configure and manage Bidirectional Forwarding Detection (BFD).
- Ambisonics in an Ogg Opus Container (draft-ietf-codec-ambisonics): AD Evaluation::Revised I-D Needed » ::AD Followup
By Jan Skoglund, Michael Graczyk, 2018-06-19 TXT HTML PDF
Abstract: This document defines an extension to the Opus audio codec to encapsulate coded ambisonics using the Ogg format. It also contains updates to RFC 7845 to reflect necessary changes in the description of channel mapping families.
- A new cryptographic signature method for DKIM (draft-ietf-dcrup-dkim-crypto): Waiting for AD Go-Ahead » IESG Evaluation
By John Levine, 2018-06-15 TXT HTML PDF
Abstract: This document adds a new signing algorithm to DKIM, ed25519-sha256. DKIM verifiers are required to implement this algorithm.
- Split DNS Configuration for IKEv2 (draft-ietf-ipsecme-split-dns): AD Evaluation::Revised I-D Needed » ::AD Followup
By Tommy Pauly, Paul Wouters, 2018-06-18 TXT HTML PDF
Abstract: This document defines two Configuration Payload Attribute Types for the IKEv2 protocol that add support for private DNS domains. These domains are intended to be resolved using DNS servers reachable through an IPsec connection, while leaving all other DNS resolution unchanged. This approach of resolving a subset of domains using non- public DNS servers is referred to as "Split DNS".
- Entropy label for SPRING tunnels (draft-ietf-mpls-spring-entropy-label): In Last Call » Waiting for Writeup
By Sriganesh Kini, Kireeti Kompella, Siva Sivabalan, Stephane Litkowski, Rob Shakir, Jeff Tantsura, 2018-05-23 TXT HTML PDF
Abstract: Segment Routing (SR) leverages the source routing paradigm. A node steers a packet through an ordered list of instructions, called segments. Segment Routing can be applied to the Multi Protocol Label Switching (MPLS) data plane. Entropy label (EL) is a technique used in MPLS to improve load-balancing. This document examines and describes how ELs are to be applied to Segment Routing MPLS.
- Registration Data Access Protocol (RDAP) Object Tagging (draft-ietf-regext-rdap-object-tag): In Last Call » Waiting for Writeup
By Scott Hollenbeck, Andrew Newton, 2018-05-21 TXT HTML PDF
Abstract: The Registration Data Access Protocol (RDAP) includes a method that can be used to identify the authoritative server for processing domain name, IP address, and autonomous system number queries. The method does not describe how to identify the authoritative server for processing other RDAP query types, such as entity queries. This limitation exists because the identifiers associated with these query types are typically unstructured. This document updates RFC 7484 by describing an operational practice that can be used to add structure to RDAP identifiers that makes it possible to identify the authoritative server for additional RDAP queries.
Drafts Sent to RFC Editor
- A Uniform Resource Name Namespace for the Device Identity and the Mobile Equipment Identity (MEID) (draft-atarius-dispatch-meid-urn): Approved-announcement to be sent::Point Raised - writeup needed » RFC Ed Queue
By Roozbeh Atarius, 2018-06-10 TXT HTML PDF
Abstract: This document defines a Uniform Resource Name (URN) namespace for the Third Generation Partnership Project 2 (3GPP2) and a Namespace Specific String (NSS) for the Mobile Equipment Identity (MEID). The structure of an MEID is 15 hexadecimal digits long and is defined in the Third Generation Partnership Project 2 (3GPP2) (see [S.R0048-A]) to uniquely identify each individual mobile equipment (e.g., a handset or mobile phone). The 3GPP2 has a requirement to be able to use an MEID as a URN. This document fulfills that requirement.
- Using the Mobile Equipment Identity (MEID) Uniform Resource Name (URN) as an Instance ID (draft-atarius-dispatch-meid-urn-as-instanceid): Approved-announcement to be sent::AD Followup » RFC Ed Queue
By Roozbeh Atarius, 2018-06-10 TXT HTML PDF
Abstract: This specification specifies how the Uniform Resource Name (URN) namespace reserved for the Third Generation Partnership Project 2 (3GPP2) identities and its Namespace Specific String (NSS) for the Mobile Equipment Identity (MEID) can be used as an instance-id. Its purpose is to fulfill the requirements for defining how a specific URN needs to be constructed and used in the "+sip.instance" Contact header field parameter for outbound behavior.
- Bootstrapping WebSockets with HTTP/2 (draft-ietf-httpbis-h2-websockets): Approved-announcement to be sent::Point Raised - writeup needed » RFC Ed Queue
By Patrick McManus, 2018-06-18 TXT HTML PDF
Abstract: This document defines a mechanism for running the WebSocket Protocol (RFC 6455) over a single stream of an HTTP/2 connection.
- Negotiating Media Multiplexing Using the Session Description Protocol (SDP) (draft-ietf-mmusic-sdp-bundle-negotiation): IESG Evaluation::AD Followup » RFC Ed Queue
By Christer Holmberg, Harald Alvestrand, Cullen Jennings, 2018-05-24 TXT HTML PDF
Abstract: This specification defines a new Session Description Protocol (SDP) Grouping Framework extension, 'BUNDLE'. The extension can be used with the SDP Offer/Answer mechanism to negotiate the usage of a single transport (5-tuple) for sending and receiving media described by multiple SDP media descriptions ("m=" sections). Such transport is referred to as a BUNDLE transport, and the media is referred to as bundled media. The "m=" sections that use the BUNDLE transport form a BUNDLE group.
- SMTP MTA Strict Transport Security (MTA-STS) (draft-ietf-uta-mta-sts): Approved-announcement sent » RFC Ed Queue
By Daniel Margolis, Mark Risher, Binu Ramakrishnan, Alexander Brotman, Janet Jones, 2018-06-15 TXT HTML PDF
Abstract: SMTP Mail Transfer Agent Strict Transport Security (MTA-STS) is a mechanism enabling mail service providers to declare their ability to receive Transport Layer Security (TLS) secure SMTP connections, and to specify whether sending SMTP servers should refuse to deliver to MX hosts that do not offer TLS with a trusted server certificate.
- Considerations for Selecting RTCP Extended Report (XR) Metrics for the WebRTC Statistics API (draft-ietf-xrblock-rtcweb-rtcp-xr-metrics): Approved-announcement to be sent::AD Followup » RFC Ed Queue
By Varun Singh, Rachel Huang, Roni Even, Dan Romascanu, Deng Lingli, 2018-05-25 TXT HTML PDF
Abstract: This document describes monitoring features related to media streams in Web real-time communication (WebRTC). It provides a list of RTCP Sender Report, Receiver Report and Extended Report metrics, which may need to be supported by RTP implementations in some diverse environments. It lists a set of identifiers for the WebRTC's statistics API. These identifiers are a set of RTCP SR, RR, and XR metrics related to the transport of multimedia flows.
Other Status Changes
- RSVP Extensions for RMR (draft-deshmukh-teas-rsvp-rmr-extension): Active » Replaced by draft-ietf-teas-rsvp-rmr-extension
By Abhishek Deshmukh, Kireeti Kompella, 2018-02-13 TXT HTML PDF
Abstract: Rings are the most common topology in access and aggregation networks. However, the use of MPLS as the transport protocol for rings is very limited today. draft-ietf-mpls-rmr-02 describes a mechanism to handle rings efficiently using MPLS. This document describes the extensions to the RSVP protocol for signaling MPLS label switched paths in rings.
- draft-leebelotti-teas-actn-info: Expired » Replaced by draft-ietf-teas-actn-info-model
No title available; expired document? TXT HTML PDF
- ChaCha20 and Poly1305 for IETF Protocols (draft-nir-cfrg-rfc7539bis): Active » RFC 8439
rfc8439.txt
By Yoav Nir, Adam Langley, 2018-03-29 TXT HTML PDF
Abstract: This document defines the ChaCha20 stream cipher as well as the use of the Poly1305 authenticator, both as stand-alone algorithms and as a "combined mode", or Authenticated Encryption with Associated Data (AEAD) algorithm.
RFC Editor Status Changes
- Conveying path setup type in PCEP messages (draft-ietf-pce-lsp-setup-type): » AUTH48
By Siva Sivabalan, Jeff Tantsura, Ina Minei, Robert Varga, Jonathan Hardwick, 2018-05-04 TXT HTML PDF
Abstract: A Path Computation Element (PCE) can compute Traffic Engineering (TE) paths through a network that are subject to various constraints. Currently, TE paths are Label Switched Paths (LSPs) which are set up using the RSVP-TE signaling protocol. However, other TE path setup methods are possible within the PCE architecture. This document proposes an extension to the PCE communication protocol (PCEP) to allow support for different path setup methods over a given PCEP session.
- Shared Bottleneck Detection for Coupled Congestion Control for RTP Media. (draft-ietf-rmcat-sbd): » AUTH48
By David Hayes, Simone Ferlin, Michael Welzl, Kristian Hiorth, 2018-03-29 TXT HTML PDF
Abstract: This document describes a mechanism to detect whether end-to-end data flows share a common bottleneck. It relies on summary statistics that are calculated based on continuous measurements and used as input to a grouping algorithm that runs wherever the knowledge is needed.
IPR Disclosures
IESG/IAB/IAOC/Trust Minutes
Liaison Statements
Classified Ads
|
WGs marked with an 
