IETF-Announce List
![[Feed]](feedicon16.png) New RFCs
New and Revived Drafts
- ISIS Extensions for Broadcast Inter-AS TE Link (draft-chen-isis-ias-lk)
By Huaimo Chen, Mehmet Toy, Xufeng Liu, Lei Liu, Zhenqiang Li, Yi Yang, 2020-07-10 TXT HTML PDF
Abstract: This document presents extensions to the ISIS protocol for advertising broadcast inter-AS Traffic Engineering (TE) links.
- OSPF Extensions for Broadcast Inter-AS TE Link (draft-chen-ospf-ias-lk)
By Huaimo Chen, Mehmet Toy, Xufeng Liu, Lei Liu, Zhenqiang Li, Yi Yang, 2020-07-10 TXT HTML PDF
Abstract: This document presents extensions to the Open Shortest Path First (OSPF) for advertising broadcast inter-AS Traffic Engineering (TE) links.
- Extensions to the Path Computation Element Communication Protocol (PCEP) for Backup Egress of a Traffic Engineering Label Switched Path (draft-chen-pce-compute-backup-egress)
By Huaimo Chen, 2020-07-10 TXT HTML PDF
Abstract: This document presents extensions to the Path Computation Element Communication Protocol (PCEP) for a PCC to send a request for computing a backup egress for an MPLS TE P2MP LSP or an MPLS TE P2P LSP to a PCE and for a PCE to compute the backup egress and reply to the PCC with a computation result for the backup egress.
- Extensions to Path Computation Element Communication Protocol (PCEP) for Backup Ingress of a Traffic Engineering Label Switched Path (draft-chen-pce-compute-backup-ingress)
By Huaimo Chen, 2020-07-10 TXT HTML PDF
Abstract: This document presents extensions to the Path Computation Element Communication Protocol (PCEP) for a PCC to send a request for computing a backup ingress for an MPLS TE P2MP LSP or an MPLS TE P2P LSP to a PCE and for a PCE to compute the backup ingress and reply to the PCC with a computation result for the backup ingress.
- A Forward-Search P2MP TE LSP Inter-Domain Path Computation (draft-chen-pce-forward-search-p2mp-path)
By Huaimo Chen, 2020-07-10 TXT HTML PDF
Abstract: This document presents a forward search procedure for computing a path for a Point-to-MultiPoint (P2MP) Traffic Engineering (TE) Label Switched Path (LSP) crossing a number of domains through using multiple Path Computation Elements (PCEs). In addition, extensions to the Path Computation Element Communication Protocol (PCEP) for supporting the forward search procedure are described.
- A Forward-Search P2P TE LSP Inter-Domain Path Computation (draft-chen-pce-forward-search-p2p-path-computation)
By Huaimo Chen, 2020-07-10 TXT HTML PDF
Abstract: This document presents a forward search procedure for computing paths for Point-to-Point (P2P) Traffic Engineering (TE) Label Switched Paths (LSPs) crossing a number of domains using multiple Path Computation Elements (PCEs). In addition, extensions to the Path Computation Element Communication Protocol (PCEP) for supporting the forward search procedure are described.
- PCEP Link State Abstraction (draft-chen-pce-h-connect-access)
By Huaimo Chen, Mehmet Toy, Xufeng Liu, Lei Liu, Zhenqiang Li, 2020-07-10 TXT HTML PDF
Abstract: This document presents extensions to the Path Computation Element Communication Protocol (PCEP) for a child PCE to abstract its domain information to its parent for supporting a hierarchical PCE system.
- Hierarchical PCE Determination (draft-chen-pce-h-discovery)
By Huaimo Chen, Mehmet Toy, Xufeng Liu, Lei Liu, Zhenqiang Li, 2020-07-10 TXT HTML PDF
Abstract: This document presents extensions to the Path Computation Element Communication Protocol (PCEP) for determining parent child relations and exchanging the information between a parent and a child PCE in a hierarchical PCE system.
- Extensions to PCEP for Distributing Label Cross Domains (draft-chen-pce-label-x-domains)
By Huaimo Chen, Autumn Liu, Mehmet Toy, Vic liu, 2020-07-10 TXT HTML PDF
Abstract: This document specifies extensions to PCEP for distributing labels crossing domains for an inter-domain Point-to-Point (P2P) or Point- to-Multipoint (P2MP) Traffic Engineering (TE) Label Switched Path (LSP).
- Static PCEP Link State (draft-chen-pce-pcc-ted)
By Huaimo Chen, Mehmet Toy, Xufeng Liu, Lei Liu, Zhenqiang Li, 2020-07-10 TXT HTML PDF
Abstract: This document presents extensions to the Path Computation Element Communication Protocol (PCEP) for a PCC to advertise the information about the links without running IGP and for a PCE to build a TED based on the information received.
- SRv6 Point-to-Multipoint Path (draft-chen-pim-srv6-p2mp-path)
By Huaimo Chen, Mike McBride, Yanhe Fan, Mehmet Toy, Aijun Wang, Lei Liu, Xufeng Liu, 2020-07-12 TXT HTML PDF
Abstract: This document describes a solution for a SRv6 Point-to-Multipoint (P2MP) Path/Tree to deliver the traffic from the ingress of the path to the multiple egresses/leaves of the path in a SR domain. There is no state stored in the core of the network for a SR P2MP path like a SR Point-to-Point (P2P) path in this solution.
- BMP Extension for Path Information TLV (draft-cppy-grow-bmp-path-info-tlv)
By Camilo Cardona, Paolo Lucente, Pierre Francois, Yunan Gu, Thomas Graf, 2020-07-12 TXT HTML PDF
Abstract: The BGP Monitoring Protocol (BMP) provides an interface for obtaining BGP path information. BGP Path Information is conveyed within BMP Route Monitoring (RM) messages. This document proposes an extension to BMP to convey additional path information that is not already encapsulated in the BGP Update PDU, e.g., BPG path status. This extension makes use of the TLV mechanims described in draft-grow-bmp- tlv [I-D.grow-bmp-tlv].
- Author Header Field (draft-crocker-dmarc-author)
By Dave Crocker, 2020-07-12 TXT HTML PDF
Abstract: Internet mail defines the From: field to indicate the author of the message's content and the Sender: field to indicate who initially handled the message. The Sender: field is optional, if it has the same information as the From: field. That is, when the Sender: field is absent, the From: field has conflated semantics, with both a handling identifier and a content creator identifier. This was not a problem, until development of stringent protections on use of the From: field. It has prompted Mediators, such as mailing lists, to modify the From: field, to circumvent mail rejection caused by those protections.
- DMARC Use of the RFC5322.Sender Header Field (draft-crocker-dmarc-sender)
By Dave Crocker, 2020-07-12 TXT HTML PDF
Abstract: Internet mail defines the RFC5322.From field to indicate the author of the message's content and the RFC5322.Sender field to indicate who initially handled the message. The RFC5322.Sender field is optional, if it has the same information as the RFC5322.From field. That is, when the RFC5322.Sender field is absent, the RFC5322.From field has conflated semantics, with both a handling identifier and a content creator identifier. This was not a problem, until development of stringent protections on use of the RFC5322.From field. It has prompted Mediators, such as mailing lists, to modify the RFC5322.From field, to circumvent mail rejection caused by those protections.
- Impact of Mobility on Discovery in COIN (draft-defoy-coinrg-mobile-discovery)
By Xavier de Foy, Akbar Rahman, 2020-07-10 TXT HTML PDF
Abstract: Service, data and resource discovery is an important aspect of computing in the network. While this aspect has been studied, including in COINRG, this document looks more specifically at the influence of mobile devices on COIN discovery. Related research challenges are described and discussed.
- PCEP Extension for Stateful Inter-Domain Tunnels (draft-dugeon-pce-stateful-interdomain)
By Olivier Dugeon, Julien Meuric, Young Lee, Daniele Ceccarelli, 2020-07-10 TXT HTML PDF
Abstract: This document specifies how to combine a Backward Recursive or Hierarchical method with inter-domain paths in the context of stateful Path Computation Element (PCE). It relies on the PCInitiate message to set up independent paths per domain. Combining these different paths together enables to operate them as end-to-end inter- domain paths without the need for a signaling session between inter- domain border routers. A new Stitching Label is defined, new Path Setup Types, a new Association Type and a new PCEP communication Protocol (PCEP) Capability are considered for that purpose.
- Support of asynchronous Enrollment in BRSKI (BRSKI-AE) (draft-ietf-anima-brski-async-enroll)
By Steffen Fries, Hendrik Brockhaus, Eliot Lear, 2020-07-10 TXT HTML PDF
Abstract: This document describes enhancements of bootstrapping a remote secure key infrastructure (BRSKI) to also operate in domains featuring no or only timely limited connectivity between involved components. It addresses connectivity to backend services supporting enrollment like a Public Key Infrastructure (PKI) and also to the connectivity between pledge and registrar. For this it enhances the use of authenticated self-contained objects in BRSKI also for request and distribution of deployment domain specific device certificates. The defined approach is agnostic regarding the utilized enrollment protocol allowing the application of existing and potentially new certificate management protocols.
- Seamless Multicast Interoperability between EVPN and MVPN PEs (draft-ietf-bess-evpn-mvpn-seamless-interop)
By Ali Sajassi, Kesavan Thiruvenkatasamy, Samir Thoria, Ashutosh Gupta, Luay Jalil, 2020-07-10 TXT HTML PDF
Abstract: Ethernet Virtual Private Network (EVPN) solution is becoming pervasive for Network Virtualization Overlay (NVO) services in data center (DC) networks and as the next generation VPN services in service provider (SP) networks.
- TE Topology and Tunnel Modeling for Transport Networks (draft-ietf-teas-te-topo-and-tunnel-modeling)
By Igor Bryskin, Vishnu Beeram, Tarek Saad, Xufeng Liu, 2020-07-12 TXT HTML PDF
Abstract: This document describes how to model TE topologies and tunnels for transport networks, by using the TE topology YANG model [I-D.ietf- teas-yang-te-topo] and the TE tunnel YANG model [I-D.ietf-teas-yang- te].
- YANG Data Model for SR and SR TE Topologies on MPLS Data Plane (draft-ietf-teas-yang-sr-te-topo)
By Xufeng Liu, Igor Bryskin, Vishnu Beeram, Tarek Saad, Himanshu Shah, Stephane Litkowski, 2020-07-12 TXT HTML PDF
Abstract: This document defines a YANG data model for Segment Routing (SR) topology and Segment Routing (SR) traffic engineering (TE) topology, using MPLS data plane.
- Flowspec Indirection-id Redirect for SRv6 (draft-ietf0-idr-srv6-flowspec-path-redirect)
By Gunter Van de Velde, Keyur Patel, Zhenbin Li, Huaimo Chen, 2020-07-10 TXT HTML PDF
Abstract: This document defines extensions to "FlowSpec Redirect to indirection-id Extended Community" for SRv6. This extended community can trigger advanced redirection capabilities to flowspec clients for SRv6. When activated, this flowspec extended community is used by a flowspec client to retrieve the corresponding next-hop and encoding information within a localised indirection-id mapping table.
- Self-configuring Stub Networks: Problem Statement (draft-lemon-stub-networks-ps)
By Ted Lemon, 2020-07-09 TXT HTML PDF
Abstract: IETF currently provides protocols for automatically connecting single hosts to existing network infrastructure. This document describes a related problem: the problem of connecting a stub network (a collection of hosts behind a router) automatically to existing network infrastructure in the same manner.
- COIN Operation, Administration and Maintenance Framework (draft-li-coin-oam-framework)
By Zhiqiang Li, Yan Mu, Cheng Zhou, 2020-07-11 TXT HTML PDF
Abstract: This document provides reference framework for Operations, Administration and Maintenance (OAM) for Computing in the Network (COIN).
- Differential Computing Resource Reservation (draft-liu-coin-differential-reservation)
By Peng Liu, Huijuan Yao, Liang Geng, 2020-07-12 TXT HTML PDF
Abstract: Computing in the network may require the embedded computing capability in the network device, such as gateway, switch, etc, and there might be so much distributed computing task in the network. Some new applications like AR/VR, motion control put forward higher demand of network than before, and AI is also considered to be used in the app and network.
- Transport Network Slice YANG Data Model (draft-liu-teas-transport-network-slice-yang)
By Xufeng Liu, Jeff Tantsura, Igor Bryskin, Luis Contreras, Qin WU, Sergio Belotti, Reza Rokui, 2020-07-12 TXT HTML PDF
Abstract: This document describes a YANG data model for managing and controlling transport network slices, defined as transport slices in [I-D.nsdt-teas-transport-slice-definition].
- MPLS-based Service Function Path(SFP) Consistency Verification (draft-lm-mpls-sfc-path-verification)
By Liu Yao, Greg Mirsky, 2020-07-12 TXT HTML PDF
Abstract: This document proposes a method to verify the correlation between Service Function Chaining control and/or management plane view of the specified Service Function Path and the state of its data. It works for both SR service programming and MPLS-based NSH SFC.
- Data Discovery Problem Statement (draft-mcbride-data-discovery-problem-statement)
By Mike McBride, Dirk Kutscher, Eve Schooler, Carlos Bernardos, Diego Lopez, 2020-07-10 TXT HTML PDF
Abstract: If data is the new oil of the 21st century, then we need a standardized way of locating, capturing, classifying and transforming this raw data to generate insights and recommendations. Data, like oil, needs to be discovered and captured in order to be refined and valuable. While the topic of data discovery can be far reaching, this document focuses on the problem of actually locating data, throughout a network of data servers, in a standardized way.
- pretty Easy privacy (pEp): Email Formats and Protocols (draft-pep-email)
By Hernani Marques, 2020-07-10 TXT HTML PDF
Abstract: The proposed pretty Easy privacy (pEp) protocols for email are based upon already existing email and encryption formats (as PGP/MIME) and designed to allow for easily implementable and interoperable opportunistic encryption. The protocols range from key distribution, secret key synchronization between own devices, to mechanisms of metadata and content protection. The metadata and content protection is achieved by moving the whole message (not only the body part) into the PGP/MIME encrypted part. The proposed pEp Email Formats not only achieve simple forms of metadata protection (like subject encryption), but also allow for sending email messages through a mixnet. Such enhanced forms of metadata protection are explicitly discussed within the scope of this document.
- pretty Easy privacy (pEp): Key Synchronization Protocol (KeySync) (draft-pep-keysync)
By Volker Birk, Bernie Hoeneisen, Kelly Bristol, 2020-07-10 TXT HTML PDF
Abstract: This document describes the pEp KeySync protocol, which is designed to perform secure peer-to-peer synchronization of private keys across devices belonging to the same user.
- Private Line Emulation over Packet Switched Networks (draft-schmutzer-bess-ple)
By Steven Gringeri, Jeremy Whittaker, Christian Schmutzer, Luca Chiesa, Nagendra Nainar, Carlos Pignataro, 2020-07-12 TXT HTML PDF
Abstract: This document describes a method for encapsulating high-speed bit- streams as virtual private wire services (VPWS) over packet switched networks (PSN) providing complete signal transport transparency.
- Private Line Emulation VPWS Signalling (draft-schmutzer-bess-ple-vpws-signalling)
By Steven Gringeri, Jeremy Whittaker, Christian Schmutzer, Patrice Brissette, 2020-07-12 TXT HTML PDF
Abstract: This document specifies the mechanisms to signal Virtual Private Wire Services (VPWS) carrying bit-stream signals over Packet Switched Networks (PSN).
- Subscription to Distributed Notifications (draft-unyte-netconf-distributed-notif)
By Tianran Zhou, Guangying Zheng, Eric Voit, Thomas Graf, Pierre Francois, 2020-07-10 TXT HTML PDF
Abstract: This documents describes extensions to the YANG notifications subscription to allow metrics being published directly from processors on line cards to target receivers, while subscription is still maintained at the route processor in a distributed forwarding system.
- UDP-based Transport for Configured Subscriptions (draft-unyte-netconf-udp-notif)
By Guangying Zheng, Tianran Zhou, Thomas Graf, Pierre Francois, Paolo Lucente, 2020-07-10 TXT HTML PDF
Abstract: This document describes an UDP-based notification mechanism to collect data from networking devices. A shim header is proposed to facilitate the streaming of data directly from line cards to a collector. The objective is to rely on a lightweight approach to allow for higher frequency and better transit performance compared to already established notification mechanisms.
- Transport Layer Security (TLS) Resumption across Server Names (draft-vvv-tls-cross-sni-resumption)
By Victor Vasiliev, 2020-07-12 TXT HTML PDF
Abstract: This document specifies a way for the parties in the Transport Layer Security (TLS) protocol to indicate that an individual session ticket can be used to perform resumption even if the Server Name of the new connection does not match the Server Name of the original.
- Simple Two-way Active Measurement Protocol Extensions for Hop-by-Hop OAM Data Collection (draft-wang-ippm-stamp-hbh-extensions)
By Yali Wang, Tianran Zhou, 2020-07-10 TXT HTML PDF
Abstract: This document defines optional TLVs which are carried in Simple Two- way Active Measurement Protocol (STAMP) test packets to enhance the STAMP base functions. Such extensions to STAMP enable OAM data collection at every node that STAMP test packets traverse.
- Transport Considerations for IP and UDP Proxying in MASQUE (draft-westerlund-masque-transport-issues)
By Magnus Westerlund, Marcus Ihlar, Zaheduzzaman Sarker, Mirja Kuehlewind, 2020-07-10 TXT HTML PDF
Abstract: The HTTP Connect method uses back-to-back TCP connections to and from a proxy. Such a solution takes care of many transport aspects as well as IP Flow related concerns. With UDP and IP proxying on the other hand, there are several per-packet and per-flow aspects that need consideration to preserve the properties of end- to-end IP/UDP flows. The aim of this document is to highlight and provide solutions for these issues related to UDP and IP proxying.
- Application Oriented High Precision Delay and Jitter Measurement (draft-yang-ippm-ptp-measurement)
By Hongwei Yang, Tao Sun, Kehan Yao, 2020-07-12 TXT HTML PDF
Abstract: As 5G has arisen and it is still evolving, there become many more time sensitive services which require high precision of measurements. In addition, in order to better simulate the transmission of packets of actual services, the length and priorities of the measurement packets SHOULD be customized, especially for some network that is inclined to get congested. This document introduces a new way to measure the time delay and jitter between two devices by making adjustments based on PTP Sync message and Delay_Req message, which could, to a great extent, get close to the messages of actual services as well as achieve high precison of measured metrics, so as to meet all requirements mentioned above.
- Concepts of Digital Twin Network (draft-zhou-nmrg-digitaltwin-network-concepts)
By Cheng Zhou, Hongwei Yang, Xiaodong Duan, 2020-07-12 TXT HTML PDF
Abstract: Digital twin technology is becoming a hot technology in industry 4.0. The application of digital twin technology in network field helps to realize efficient and intelligent management and network innovation. This document presents an overview of the concepts of Digital Twin Network (DTN), provides the definition and DTN, and then describes the benefits and key challenges of DTN.
- Route Target Constrain Extension (draft-zzhang-idr-bgp-rt-constrains-extension)
By Zhaohui Zhang, Jeffrey Haas, 2020-07-12 TXT HTML PDF
Abstract: This document specifies the extensions to Route Target Constrain mechanism so that it works with various types of Route Targets of arbitrary lengths.
- Bitmask Route Target (draft-zzhang-idr-bitmask-route-target)
By Zhaohui Zhang, Srihari Ramachandra, Jeffrey Haas, 2020-07-12 TXT HTML PDF
Abstract: This document specifies a new type of Route Target called Bitmask Route Target as a BGP Community Container. The key element of a Bitmask Route Target is a Bitmask. Two Bitmask Route Targets are considered equivalent for the purpose of controlling route propagation (via Route Target Constraints) and importation if the result of logical "AND" operation of the Bitmask of the two is non- zero.
Updated Drafts
- IS-IS YANG Model Augmentations for Additional Features - Version 1 (draft-acee-lsr-isis-yang-augmentation-v1)
By Acee Lindem, Stephane Litkowski, Yingzhen Qu, 2020-07-12 TXT HTML PDF
Abstract: This document defines YANG data modules augmenting the IETF IS-IS YANG model to provide support for IS-IS Minimum Remaining Lifetime as defined in RFC 7987.
- Use of the Walnut Digital Signature Algorithm with CBOR Object Signing and Encryption (COSE) (draft-atkins-suit-cose-walnutdsa)
By Derek Atkins, 2020-07-10 TXT HTML PDF
Abstract: This document specifies the conventions for using the Walnut Digital Signature Algorithm (WalnutDSA) for digital signatures with the CBOR Object Signing and Encryption (COSE) syntax. WalnutDSA is a lightweight, quantum-resistant signature scheme based on Group Theoretic Cryptography with implementation and computational efficiency of signature verification in constrained16807 environments, even on 8- and 16-bit platforms.
- QUIC-based UDP Transport for Secure Shell (SSH) (draft-bider-ssh-quic)
By denis bider, 2020-07-12 TXT HTML PDF
Abstract: The Secure Shell protocol (SSH) [RFC4251] is widely used for purposes including secure remote administration, file transfer using SFTP and SCP, and encrypted tunneling of TCP connections. Because it is based on TCP, SSH suffers similar problems as motivate the HTTP protocol to transition to UDP-based QUIC [QUIC]. These include: unauthenticated network intermediaries can trivially disconnect SSH sessions; SSH connections are lost when mobile clients change IP addresses; performance limitations in OS-based TCP stacks; many round-trips to establish a connection; duplicate flow control on the level of the connection as well as channels. This memo specifies SSH key exchange over UDP and leverages QUIC to provide a UDP-based transport.
- A YANG Data Model for Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel (draft-boucadair-dots-rfc8782-yang-update)
By Mohamed Boucadair, Jon Shallow, 2020-07-09 TXT HTML PDF
Abstract: This document specifies an updated version of the Distributed Denial- of-Service Open Threat Signaling (DOTS) Signal Channel YANG data model. This updated version makes use of the new mechanisms for defining abstract data structures with YANG as specified in RFC8791.
- Encrypted DNS Discovery and Deployment Considerations for Home Networks (draft-btw-add-home)
By Mohamed Boucadair, Tirumaleswar Reddy.K, Dan Wing, Neil Cook, 2020-07-10 TXT HTML PDF
Abstract: This document discusses DoT/DoH deployment considerations for home networks. It particularly sketches the required steps to use DoT/DoH capabilities provided by local networks.
- Node Protection for RSVP-TE tunnels on a shared MPLS forwarding plane (draft-chandra-mpls-rsvp-shared-labels-np)
By Chandrasekar R, Vishnu Beeram, Harish Sitaraman, 2020-07-12 TXT HTML PDF
Abstract: Segment Routed RSVP-TE tunnels provide the ability to use a shared MPLS forwarding plane at every hop of the Label Switched Path (LSP). The shared forwarding plane is realized with the use of 'Traffic Engineering (TE) link labels' that get shared by LSPs traversing these TE links. This paradigm helps significantly reduce the forwarding plane state required to support a large number of LSPs on a Label Switching Router (LSR). These tunnels require the ingress Label Edge Router (LER) to impose a stack of labels. If the ingress LER cannot impose the full label stack, it can use the assistance of one or more delegation hops along the path of the LSP to impose parts of the label stack.
- IS-IS Topology-Transparent Zone (draft-chen-isis-ttz)
By Huaimo Chen, Renwei Li, Yi Yang, Yanhe Fan, Ning So, Vic liu, Mehmet Toy, Lei Liu, Kiran Makhijani, 2020-07-10 TXT HTML PDF
Abstract: This document presents a topology-transparent zone in an area. A zone is a block/piece of an area, which comprises a group of routers and a number of circuits connecting them. It is abstracted as a virtual entity such as a single virtual node or zone edges mesh. Any router outside of the zone is not aware of the zone. The information about the circuits and routers inside the zone is not distributed to any router outside of the zone.
- PCEP SR Policy Extensions to Enable IFIT (draft-chen-pce-sr-policy-ifit)
By Huanan Chen, Hang Yuan, Tianran Zhou, Weidong Li, Giuseppe Fioccola, Yali Wang, 2020-07-10 TXT HTML PDF
Abstract: Segment Routing (SR) policy is a set of candidate SR paths consisting of one or more segment lists and necessary path attributes. It enables instantiation of an ordered list of segments with a specific intent for traffic steering. In-situ Flow Information Telemetry (IFIT) refers to network OAM applications that apply dataplane on- path telemetry techniques. This document defines extensions to PCEP to distribute SR policies carrying IFIT information. So that IFIT behavior can be enabled automatically when the SR policy is applied.
- Extension for Stateful PCE to allow Optional Processing of PCEP Objects (draft-dhody-pce-stateful-pce-optional)
By Cheng Li, Haomian Zheng, Stephane Litkowski, 2020-07-09 TXT HTML PDF
Abstract: This document introduces a mechanism to mark some of the Path Computation Element (PCE) Communication Protocol (PCEP) objects as optional during PCEP messages exchange for the Stateful PCE model to allow relaxing some constraints. This document introduces this relaxation and updates the RFC 8231.
- Enhanced Performance Delay and Liveness Monitoring in Segment Routing Networks (draft-gandhi-spring-sr-enhanced-plm)
By Rakesh Gandhi, Clarence Filsfils, Navin Vaghamshi, Moses Nagarajah, Richard Foote, 2020-07-11 TXT HTML PDF
Abstract: Segment Routing (SR) leverages the source routing paradigm. SR is applicable to both Multiprotocol Label Switching (SR-MPLS) and IPv6 (SRv6) data planes. This document defines procedure for Enhanced Performance Delay and Liveness Monitoring (PDLM) in Segment Routing networks. The procedure uses the probe messages defined in RFC 5357 (Two-Way Active Measurement Protocol (TWAMP) Light) and RFC 8762 (Simple Two-Way Active Measurement Protocol (STAMP)) for end-to-end SR Paths including SR Policies with both SR-MPLS and SRv6 data planes.
- BIER BFD (draft-hu-bier-bfd)
By Quan Xiong, Greg Mirsky, fangwei hu, Chang Liu, 2020-07-10 TXT HTML PDF
Abstract: Point to multipoint (P2MP) BFD is designed to verify multipoint connectivity. This document specifies the application of P2MP BFD in BIER network.
- SR-TE Path Midpoint Protection (draft-hu-spring-segment-routing-proxy-forwarding)
By Zhibo Hu, Huaimo Chen, Junda Yao, Chris Bowers, Yongqing Zhu, 2020-07-10 TXT HTML PDF
Abstract: Segment Routing Traffic Engineering (SR-TE) supports the creation of explicit paths using segment lists containing adjacency-SIDs, node- SIDs, anycast-SIDs, and binding-SIDs. When the segment list defining an SR-TE path contains a node-SID, and the node fails, the network may no longer be able to properly forward traffic on that SR-TE path. [I-D.ietf-rtgwg-segment-routing-ti-lfa] and [I-D.hegde-spring-node-protection-for-sr-te-paths] describe a mechanism that allows local repair actions on the direct neighbors of the failed node to temporarily route traffic to the node immediately following the failed node on the SR-TE path segment list. However, once the IGP shortest paths have converged, the local repair mechanism is no longer sufficient to continue forwarding traffic using the original segment list of the SR-TE path, since the non- neighbors of the failed node will no longer have a route to reach the failed node. This document describes a mechanism that allows traffic to continue to be forwarded on an SR-TE path for an extended period of time after the failure of a node used in the path's segment list.
- Transmission of IPv6 Packets over Near Field Communication (draft-ietf-6lo-nfc)
By Younghwan Choi, Yong-Geun Hong, Joo-Sang Youn, Dongkyun Kim, JinHyeock Choi, 2020-07-09 TXT HTML PDF
Abstract: Near Field Communication (NFC) is a set of standards for smartphones and portable devices to establish radio communication with each other by touching them together or bringing them into proximity, usually no more than 10 cm apart. NFC standards cover communications protocols and data exchange formats, and are based on existing radio-frequency identification (RFID) standards including ISO/IEC 14443 and FeliCa. The standards include ISO/IEC 18092 and those defined by the NFC Forum. The NFC technology has been widely implemented and available in mobile phones, laptop computers, and many other devices. This document describes how IPv6 is transmitted over NFC using 6LoWPAN techniques.
- RTP-mixer formatting of multi-party Real-time text (draft-ietf-avtcore-multi-party-rtt-mix)
By Gunnar Hellstrom, 2020-07-12 TXT HTML PDF
Abstract: Real-time text mixers for multi-party sessions need to identify the source of each transmitted group of text so that the text can be presented by endpoints in suitable grouping with other text from the same source.
- RTP Payload Format for Versatile Video Coding (VVC) (draft-ietf-avtcore-rtp-vvc)
By Shuai Zhao, Stephan Wenger, Yago Sanchez, 2020-07-11 TXT HTML PDF
Abstract: This memo describes an RTP payload format for the video coding standard ITU-T Recommendation [H.266] and ISO/IEC International Standard [ISO23090-3], both also known as Versatile Video Coding (VVC) and developed by the Joint Video Experts Team (JVET). The RTP payload format allows for packetization of one or more Network Abstraction Layer (NAL) units in each RTP packet payload as well as fragmentation of a NAL unit into multiple RTP packets. The payload format has wide applicability in videoconferencing, Internet video streaming, and high-bitrate entertainment-quality video, among other applications.
- Controller Based BGP Multicast Signaling (draft-ietf-bess-bgp-multicast-controller)
By Zhaohui Zhang, Robert Raszuk, Dante Pacella, Arkadiy Gulko, 2020-07-12 TXT HTML PDF
Abstract: This document specifies a way that one or more centralized controllers can use BGP to set up a multicast distribution tree in a network. In the case of labeled tree, the labels are assigned by the controllers either from the controllers' local label spaces, or from a common Segment Routing Global Block (SRGB), or from each routers Segment Routing Local Block (SRLB) that the controllers learn. In case of labeled unidirectional tree and label allocation from the common SRGB or from the controllers' local spaces, a single common label can be used for all routers on the tree to send and receive traffic with. Since the controllers calculate the trees, they can use sophisticated algorithms and constraints to achieve traffic engineering.
- Weighted Multi-Path Procedures for EVPN All-Active Multi-Homing (draft-ietf-bess-evpn-unequal-lb)
By Neeraj Malhotra, Ali Sajassi, Jorge Rabadan, John Drake, Avinash Lingala, Samir Thoria, 2020-07-10 TXT HTML PDF
Abstract: In an EVPN-IRB based network overlay, EVPN all-active multi-homing enables multi-homing for a CE device connected to two or more PEs via a LAG, such that bridged and routed traffic from remote PEs can be equally load balanced (ECMPed) across the multi-homing PEs. This document defines extensions to EVPN procedures to optimally handle unequal access bandwidth distribution across a set of multi-homing PEs in order to:
- SRv6 BGP based Overlay services (draft-ietf-bess-srv6-services)
By Gaurav Dawra, Clarence Filsfils, Robert Raszuk, Bruno Decraene, Shunwan Zhuang, Jorge Rabadan, 2020-07-11 TXT HTML PDF
Abstract: This draft defines procedures and messages for SRv6-based BGP services including L3VPN, EVPN and Internet services. It builds on RFC4364 "BGP/MPLS IP Virtual Private Networks (VPNs)" and RFC7432 "BGP MPLS-Based Ethernet VPN".
- BIER IPv6 Requirements (draft-ietf-bier-ipv6-requirements)
By Mike McBride, Jingrong Xie, Senthil Dhanaraj, Rajiv Asati, Yongqing Zhu, Gyan Mishra, 2020-07-10 TXT HTML PDF
Abstract: The BIER WG charter includes work on developing "a mechanism to use BIER natively in IPv6". There have been several proposed solutions in this area. But there hasn't been a document which describes the problem and lists the requirements. The goal of this document is to describe the BIER IPv6 requirements, summarize the encapsulation modes of the proposed solutions, guide the working group in understanding the benefits and drawbacks of the various solutions, and help in the development of acceptable solutions.
- Applicability of BIER Multicast Overlay for Adaptive Streaming Services (draft-ietf-bier-multicast-http-response)
By Dirk Trossen, Akbar Rahman, Chonggang Wang, Toerless Eckert, 2020-07-10 TXT HTML PDF
Abstract: HTTP Level Multicast, using BIER, is described as a use case in the BIER Use Cases document. HTTP Level Multicast is used in today's video streaming and delivery services such as HLS, AR/VR etc., generally realized over IP Multicast as well as other use cases such as software update delivery. A realization of "HTTP Multicast" over "IP Multicast" is described for the video delivery use case. IP Multicast is commonly used for IPTV services. DVB and BBF also developes a reference architecture for IP Multicast service. A few problems with IP Multicast, such as waste of transmission bandwidth, increase in signaling when there are few users are described. Realization over BIER, through a BIER Multicast Overlay Layer, is described as an alternative. How BIER Multicast Overlay operation improves over IP Multicast, such as reduction in signaling, dynamic creation of multicast groups to reduce signaling and bandwidth wastage is described. We conclude with a few next steps.
- YANG data model for Flexi-Grid Optical Networks (draft-ietf-ccamp-flexigrid-yang)
By Universidad de Madrid, Daniel Perdices, Daniel King, Young Lee, Haomian Zheng, 2020-07-12 TXT HTML PDF
Abstract: This document defines a YANG module for managing flexi-grid optical networks. The model defined in this document specifies a flexi-grid traffic engineering database that is used to describe the topology of a flexi-grid network. It is based on and augments existing YANG models that describe network and traffic engineering topologies.
- Constrained YANG Module Library (draft-ietf-core-yang-library)
By Michel Veillette, Ivaylo Petrov, 2020-07-10 TXT HTML PDF
Abstract: This document describes a constrained version of the YANG library that provides information about the YANG modules, datastores, and datastore schemas used by a constrained network management server (e.g., a CORECONF server).
- IPv6-Only-Preferred Option for DHCPv4 (draft-ietf-dhc-v6only)
By Lorenzo Colitti, Jen Linkova, Michael Richardson, Tomek Mrugalski, 2020-07-09 TXT HTML PDF
Abstract: This document specifies a DHCPv4 option to indicate that a host supports an IPv6-only mode and willing to forgo obtaining an IPv4 address if the network provides IPv6 connectivity. It also updates RFC2563 to specify the DHCPv4 server behavior when the server receives a DHCPDISCOVER not containing the Auto-Configure option.
- Secret Key Transaction Authentication for DNS (TSIG) (draft-ietf-dnsop-rfc2845bis)
By Francis Dupont, Stephen Morris, Paul Vixie, Donald Eastlake, Olafur Gudmundsson, Brian Wellington, 2020-07-10 TXT HTML PDF
Abstract: This document describes a protocol for transaction level authentication using shared secrets and one way hashing. It can be used to authenticate dynamic updates to a DNS zone as coming from an approved client, or to authenticate responses as coming from an approved name server.
- Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry (draft-ietf-dots-telemetry)
By Mohamed Boucadair, Tirumaleswar Reddy.K, Ehud Doron, chenmeiling, Jon Shallow, 2020-07-10 TXT HTML PDF
Abstract: This document aims to enrich DOTS signal channel protocol with various telemetry attributes allowing optimal Distributed Denial-of- Service attack mitigation. It specifies the normal traffic baseline and attack traffic telemetry attributes a DOTS client can convey to its DOTS server in the mitigation request, the mitigation status telemetry attributes a DOTS server can communicate to a DOTS client, and the mitigation efficacy telemetry attributes a DOTS client can communicate to a DOTS server. The telemetry attributes can assist the mitigator to choose the DDoS mitigation techniques and perform optimal DDoS attack mitigation.
- Recommendations for DNS Privacy Service Operators (draft-ietf-dprive-bcp-op)
By Sara Dickinson, Benno Overeinder, Roland van Rijswijk-Deij, Allison Mankin, 2020-07-10 TXT HTML PDF
Abstract: This document presents operational, policy, and security considerations for DNS recursive resolver operators who choose to offer DNS Privacy services. With these recommendations, the operator can make deliberate decisions regarding which services to provide, and how the decisions and alternatives impact the privacy of users.
- Nimble out-of-band authentication for EAP (EAP-NOOB) (draft-ietf-emu-eap-noob)
By Tuomas Aura, Mohit Sethi, 2020-07-12 TXT HTML PDF
Abstract: The Extensible Authentication Protocol (EAP) provides support for multiple authentication methods. This document defines the EAP-NOOB authentication method for nimble out-of-band (OOB) authentication and key derivation. The EAP method is intended for bootstrapping all kinds of Internet-of-Things (IoT) devices that have no pre-configured authentication credentials. The method makes use of a user-assisted one-directional OOB message between the peer device and authentication server to authenticate the in-band key exchange. The device must have an input or output interface, such as a display, microphone, speakers or blinking light, which can send or receive dynamically generated messages of tens of bytes in length.
- HTTP Caching (draft-ietf-httpbis-cache)
By Roy Fielding, Mark Nottingham, Julian Reschke, 2020-07-12 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, 2020-07-12 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.
- Extensible Prioritization Scheme for HTTP (draft-ietf-httpbis-priority)
By Kazuho Oku, Lucas Pardue, 2020-07-12 TXT HTML PDF
Abstract: This document describes a scheme for prioritizing HTTP responses. This scheme expresses the priority of each HTTP response using absolute values, rather than as a relative relationship between a group of HTTP responses.
- HTTP Semantics (draft-ietf-httpbis-semantics)
By Roy Fielding, Mark Nottingham, Julian Reschke, 2020-07-12 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.
- A YANG Data Model for Layer 2 Network Topologies (draft-ietf-i2rs-yang-l2-network-topology)
By Jie Dong, Xiugang Wei, Qin WU, Mohamed Boucadair, Anders Liu, 2020-07-12 TXT HTML PDF
Abstract: This document defines a YANG data model for Layer 2 network topologies. In particular, this data model augments the generic network and network topology data models with Layer 2 specific topology attributes.
- BGP Link State Extensions for SRv6 (draft-ietf-idr-bgpls-srv6-ext)
By Gaurav Dawra, Clarence Filsfils, Ketan Talaulikar, Mach Chen, daniel.bernier@bell.ca, Bruno Decraene, 2020-07-10 TXT HTML PDF
Abstract: Segment Routing IPv6 (SRv6) allows for a flexible definition of end- to-end paths within various topologies by encoding paths as sequences of topological or functional sub-paths, called "segments". These segments are advertised by the various protocols such as BGP, ISIS and OSPFv3.
- Dissemination of Flow Specification Rules for IPv6 (draft-ietf-idr-flow-spec-v6)
By Christoph Loibl, Robert Raszuk, Susan Hares, 2020-07-10 TXT HTML PDF
Abstract: Dissemination of Flow Specification Rules I-D.ietf-idr-rfc5575bis provides a protocol extension for propagation of traffic flow information for the purpose of rate limiting or filtering. I-D.ietf- idr-rfc5575bis specifies those extensions for IPv4 protocol data packets only.
- Advanced Unidirectional Route Assessment (AURA) (draft-ietf-ippm-route)
By Jose Alvarez-Hamelin, Alfred Morton, Joachim Fabini, Carlos Pignataro, Ruediger Geib, 2020-07-10 TXT HTML PDF
Abstract: This memo introduces an advanced unidirectional route assessment (AURA) metric and associated measurement methodology, based on the IP Performance Metrics (IPPM) Framework RFC 2330. This memo updates RFC 2330 in the areas of path-related terminology and path description, primarily to include the possibility of parallel subpaths between a given Source and Destination pair, owing to the presence of multi- path technologies.
- Multiple Key Exchanges in IKEv2 (draft-ietf-ipsecme-ikev2-multiple-ke)
By C. Tjhai, M. Tomlinson, G. Bartlett, Scott Fluhrer, Daniel Van Geest, Oscar Garcia-Morchon, Valery Smyslov, 2020-07-10 TXT HTML PDF
Abstract: This document describes how to extend the Internet Key Exchange Protocol Version 2 (IKEv2) to allow multiple key exchanges to take place while computing a shared secret during a Security Association (SA) setup. The primary application of this feature in IKEv2 is the ability to perform one or more post-quantum key exchanges in conjunction with the classical (Elliptic Curve) Diffie-Hellman key exchange, so that the resulting shared key is resistant against quantum computer attacks. Another possible application is the ability to combine several key exchanges in situations when no single key exchange algorithm is trusted by both initiator and responder.
- YANG Data Model for IS-IS Segment Routing (draft-ietf-isis-sr-yang)
By Stephane Litkowski, Yingzhen Qu, Pushpasis Sarkar, Ing-Wher Chen, Jeff Tantsura, 2020-07-12 TXT HTML PDF
Abstract: This document defines a YANG data model that can be used to configure and manage IS-IS Segment Routing.
- Lightweight CMP Profile (draft-ietf-lamps-lightweight-cmp-profile)
By Hendrik Brockhaus, Steffen Fries, David von Oheimb, 2020-07-11 TXT HTML PDF
Abstract: The goal of this document is to facilitate interoperability and automation by profiling the Certificate Management Protocol (CMP) version 2, the related Certificate Request Message Format (CRMF) version 2, and the HTTP Transfer for the Certificate Management Protocol. It specifies a subset of CMP and CRMF focusing on typical uses cases relevant for managing certificates of devices in many industrial and IoT scenarios. To limit the overhead of certificate management for more constrained devices only the most crucial types of operations are specified as mandatory. To foster interoperability in more complex scenarios, other types of operations are specified as recommended or optional.
- Clarification of Enrollment over Secure Transport (EST): transfer encodings and ASN.1 (draft-ietf-lamps-rfc7030est-clarify)
By Michael Richardson, Thomas Werner, Wei Pan, 2020-07-12 TXT HTML PDF
Abstract: This document updates RFC7030: Enrollment over Secure Transport (EST) to resolve some errata that were reported, and which has proven to cause interoperability issues when RFC7030 was extended.
- Publish/Subscribe Functionality for LISP (draft-ietf-lisp-pubsub)
By Alberto Rodriguez-Natal, Vina Ermagan, Albert Cabellos-Aparicio, Sharon Barkai, Mohamed Boucadair, 2020-07-10 TXT HTML PDF
Abstract: This document specifies an extension to the use of Map-Request to enable Publish/Subscribe (PubSub) operation for LISP.
- Static Context Header Compression (SCHC) over LoRaWAN (draft-ietf-lpwan-schc-over-lorawan)
By Olivier Gimenez, Ivaylo Petrov, 2020-07-12 TXT HTML PDF
Abstract: The Static Context Header Compression (SCHC) specification describes generic header compression and fragmentation techniques for LPWAN (Low Power Wide Area Networks) technologies. SCHC is a generic mechanism designed for great flexibility so that it can be adapted for any of the LPWAN technologies.
- Data Model for Static Context Header Compression (SCHC) (draft-ietf-lpwan-schc-yang-data-model)
By Ana Minaburo, Laurent Toutain, 2020-07-10 TXT HTML PDF
Abstract: This document describes a YANG data model for the SCHC (Static Context Header Compression) compression and fragmentation rules.
- IGP Flexible Algorithm (draft-ietf-lsr-flex-algo)
By Peter Psenak, Shraddha Hegde, Clarence Filsfils, Ketan Talaulikar, Arkadiy Gulko, 2020-07-10 TXT HTML PDF
Abstract: IGP protocols traditionally compute best paths over the network based on the IGP metric assigned to the links. Many network deployments use RSVP-TE based or Segment Routing based Traffic Engineering to enforce traffic over a path that is computed using different metrics or constraints than the shortest IGP path. This document proposes a solution that allows IGPs themselves to compute constraint based paths over the network. This document also specifies a way of using Segment Routing (SR) Prefix-SIDs and SRv6 locators to steer packets along the constraint-based paths.
- OSPF YANG Model Augmentations for Additional Features - Version 1 (draft-ietf-lsr-ospf-yang-augmentation-v1)
By Acee Lindem, Yingzhen Qu, 2020-07-12 TXT HTML PDF
Abstract: This document defines YANG data modules augmenting the IETF OSPF YANG model to provide support for Traffic Engineering Extensions to OSPF Version 3 as defined in RF 5329, OSPF Two-Part Metric as defined in RFC 8042, OSPF Graceful Link Shutdown as defined in RFC 8379 and OSPF Link-Local Signaling (LLS) Extensions for Local Interface ID Advertisement as defined in RFC 8510.
- Operational Considerations for Streaming Media (draft-ietf-mops-streaming-opcons)
By Jake Holland, Ali Begen, Spencer Dawkins, 2020-07-12 TXT HTML PDF
Abstract: This document provides an overview of operational networking issues that pertain to quality of experience in delivery of video and other high-bitrate media over the internet.
- YANG Data Types and Groupings for Cryptography (draft-ietf-netconf-crypto-types)
By Kent Watsen, 2020-07-10 TXT HTML PDF
Abstract: This document presents a YANG 1.1 (RFC 7950) module defining identities, typedefs, and groupings useful to cryptographic applications.
- An HTTPS-based Transport for Configured Subscriptions (draft-ietf-netconf-https-notif)
By Mahesh Jethanandani, Kent Watsen, 2020-07-10 TXT HTML PDF
Abstract: This document defines a YANG data module for configuring HTTPS based configured subscription, as defined in RFC 8639. The use of HTTPS maximizes transport-level interoperability, while allowing for encoding selection from text, e.g. XML or JSON, to binary.
- A YANG Data Model for a Keystore (draft-ietf-netconf-keystore)
By Kent Watsen, 2020-07-10 TXT HTML PDF
Abstract: This document defines a YANG 1.1 module called "ietf-keystore" that enables centralized configuration of both symmetric and asymmetric keys. The secret value for both key types may be encrypted. Asymmetric keys may be associated with certificates. Notifications are sent when certificates are about to expire.
- YANG Groupings for SSH Clients and SSH Servers (draft-ietf-netconf-ssh-client-server)
By Kent Watsen, Gary Wu, 2020-07-10 TXT HTML PDF
Abstract: This document defines three YANG modules: the first defines groupings for a generic SSH client, the second defines groupings for a generic SSH server, and the third defines common identities and groupings used by both the client and the server. It is intended that these groupings will be used by applications using the SSH protocol.
- YANG Groupings for TLS Clients and TLS Servers (draft-ietf-netconf-tls-client-server)
By Kent Watsen, Gary Wu, 2020-07-10 TXT HTML PDF
Abstract: This document defines three YANG modules: the first defines groupings for a generic TLS client, the second defines groupings for a generic TLS server, and the third defines common identities and groupings used by both the client and the server. It is intended that these groupings will be used by applications using the TLS protocol.
- A YANG Data Model for a Truststore (draft-ietf-netconf-trust-anchors)
By Kent Watsen, 2020-07-10 TXT HTML PDF
Abstract: This document defines a YANG 1.1 data model for configuring globally- accessible bags of certificates and public keys that can be referenced by other data models for trust.
- Updated YANG Module Revision Handling (draft-ietf-netmod-yang-module-versioning)
By Robert Wilton, Reshad Rahman, Balazs Lengyel, Joe Clarke, Jason Sterne, Benoit Claise, Kevin D'Souza, 2020-07-10 TXT HTML PDF
Abstract: This document specifies a new YANG module update procedure that can document when non-backwards-compatible changes have occurred during the evolution of a YANG module. It extends the YANG import statement with an earliest revision filter to better represent inter-module dependencies. It provides help and guidelines for managing the lifecycle of YANG modules and individual schema nodes. It provides a mechanism, via the revision-label YANG extension, to specify a revision identifier for YANG modules. This document updates RFC 7950, RFC 8407 and RFC 8525.
- OAuth 2.0 Pushed Authorization Requests (draft-ietf-oauth-par)
By Torsten Lodderstedt, Brian Campbell, Nat Sakimura, Dave Tonge, Filip Skokan, 2020-07-10 TXT HTML PDF
Abstract: This document defines the pushed authorization request endpoint, which allows clients to push the payload of an OAuth 2.0 authorization request to the authorization server via a direct request and provides them with a request URI that is used as reference to the data in a subsequent authorization request.
- YANG Data Model for OSPF SR (Segment Routing) Protocol (draft-ietf-ospf-sr-yang)
By Derek Yeung, Yingzhen Qu, Zhaohui Zhang, Ing-Wher Chen, Acee Lindem, 2020-07-12 TXT HTML PDF
Abstract: This document defines a YANG data model that can be used to configure and manage OSPF Segment Routing. The model is based on YANG 1.1 as defined in RFC 7950 and conforms to the Network Management Datastore Architecture (NDMA) as described in RFC 8342.
- PCEP Extensions for LSP scheduling with stateful PCE (draft-ietf-pce-stateful-pce-lsp-scheduling)
By Huaimo Chen, Zhuangyan, Qin WU, Daniele Ceccarelli, 2020-07-12 TXT HTML PDF
Abstract: This document defines 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 and the duration of a traffic service in a centralized network environment as stated in RFC 8413.
- IGMPv3/MLDv2 Message Extension (draft-ietf-pim-igmp-mld-extension)
By Mahesh Sivakumar, Stig Venaas, Zheng Zhang, Hitoshi Asaeda, 2020-07-12 TXT HTML PDF
Abstract: IGMP and MLD protocols are extensible, but no extensions have been defined so far. This document provides a well-defined way of extending IGMP and MLD, using a list of TLVs (Type, Length and Value).
- QUIC-LB: Generating Routable QUIC Connection IDs (draft-ietf-quic-load-balancers)
By Martin Duke, Nick Banks, 2020-07-10 TXT HTML PDF
Abstract: QUIC connection IDs allow continuation of connections across address/ port 4-tuple changes, and can store routing information for stateless or low-state load balancers. They also can prevent linkability of connections across deliberate address migration through the use of protected communications between client and server. This creates issues for load-balancing intermediaries. This specification standardizes methods for encoding routing information given a small set of configuration parameters. This framework also enables offload of other QUIC functions to trusted intermediaries, given the explicit cooperation of the QUIC server.
- Remote Attestation Procedures Architecture (draft-ietf-rats-architecture)
By Henk Birkholz, Dave Thaler, Michael Richardson, Ned Smith, Wei Pan, 2020-07-10 TXT HTML PDF
Abstract: In network protocol exchanges, it is often the case that one entity (a Relying Party) requires evidence about a remote peer to assess the peer's trustworthiness, and a way to appraise such evidence. The evidence is typically a set of claims about its software and hardware platform. This document describes an architecture for such remote attestation procedures (RATS).
- TPM-based Network Device Remote Integrity Verification (draft-ietf-rats-tpm-based-network-device-attest)
By Guy Fedorkow, Eric Voit, Jessica Fitzgerald-McKay, 2020-07-12 TXT HTML PDF
Abstract: This document describes a workflow for remote attestation of the integrity of network devices.
- YANG Data Model for Segment Routing (draft-ietf-spring-sr-yang)
By Stephane Litkowski, Yingzhen Qu, Acee Lindem, Pushpasis Sarkar, Jeff Tantsura, 2020-07-09 TXT HTML PDF
Abstract: This document defines a YANG data model for segment routing configuration and operation, which is to be augmented by different segment routing data planes. The document also defines a YANG model that is intended to be used on network elements to configure or operate segment routing MPLS data plane, as well as some generic containers to be reused by IGP protocol modules to support segment routing.
- Yang model for requesting Path Computation (draft-ietf-teas-yang-path-computation)
By Italo Busi, Sergio Belotti, Victor Lopezalvarez, Anurag Sharma, Yan Shi, 2020-07-11 TXT HTML PDF
Abstract: There are scenarios, typically in a hierarchical SDN context, where the topology information provided by a TE network provider may not be sufficient for its client to perform end-to-end path computation. In these cases the client would need to request the provider to calculate some (partial) feasible paths.
- 464XLAT/NAT64 Optimization (draft-ietf-v6ops-464xlat-optimization)
By Jordi Palet, Alejandro D'Egidio, 2020-07-11 TXT HTML PDF
Abstract: IP/ICMP Translation Algorithm (SIIT) can be used to provide access for IPv4-only devices or applications to IPv4-only or dual-stack destinations over IPv6-only infrastructure. In that case, the traffic flows are translated twice: first from IPv4 to IPv6 (stateless NAT46 at the ingress point to the IPv6-only infrastructure) and then from IPv6 back to IPv4 (stateful NAT64, at the egress point). When the destination is IPv6-enabled, the second translation might be avoided. This document describes a possible optimization to 464XLAT and MAP-T to avoid translating IPv6 flows back to IPv4 if the destination is reachable over IPv6. The proposed solution would significantly reduce the NAT64 utilization in the operator's network.
- Enabling ICN in 3GPP's 5G NextGen Core Architecture (draft-irtf-icnrg-5gc-icn)
By Ravi Ravindran, Prakash suthar, Dirk Trossen, Chonggang Wang, Greg White, 2020-07-10 TXT HTML PDF
Abstract: The proposed 3GPP's 5G core nextgen architecture (5GC) allows the introduction of new user and control plane function, considering the support for network slicing functions, that offers greater flexibility to handle heterogeneous devices and applications. In this draft, we provide a short description of the proposed 5GC architecture, including recent efforts to provide cellular Local Area Network (LAN) connectivity, followed by extensions to 5GC's control and user plane to support Packet Data Unit (PDU) sessions from Information-Centric Networks (ICN). In addition, ICN over 5GLAN is also described.
- Architectural Principles for a Quantum Internet (draft-irtf-qirg-principles)
By Wojciech Kozlowski, Stephanie Wehner, Rodney Van Meter, Bruno Rijsman, Angela Cacciapuoti, Marcello Caleffi, Shota Nagayama, 2020-07-12 TXT HTML PDF
Abstract: The vision of a quantum internet is to fundamentally enhance Internet technology by enabling quantum communication between any two points on Earth. To achieve this goal, a quantum network stack should be built from the ground up as the physical nature of the communication is fundamentally different. The first realisations of quantum networks are imminent, but there is no practical proposal for how to organise, utilise, and manage such networks. In this memo, we attempt to lay down the framework and introduce some basic architectural principles for a quantum internet. This is intended for general guidance and general interest, but also to provide a foundation for discussion between physicists and network specialists.
- Applications and Use Cases for the Quantum Internet (draft-irtf-qirg-quantum-internet-use-cases)
By Chonggang Wang, Akbar Rahman, Ruidong Li, Melchior Aelmans, 2020-07-10 TXT HTML PDF
Abstract: The Quantum Internet has the potential to improve Internet application functionality by incorporating quantum information technology into the infrastructure of the overall Internet. In this document, we provide an overview of some applications expected to be used on the Quantum Internet, and then categorize them using various classification schemes. Some general requirements for the Quantum Internet are also discussed. The intent of this document is to provide a common understanding and framework of applications and use cases for the Quantum Internet.
- Inter Stateful Path Computation Element (PCE) Communication Procedures. (draft-litkowski-pce-state-sync)
By Stephane Litkowski, Siva Sivabalan, Cheng Li, Haomian Zheng, 2020-07-12 TXT HTML PDF
Abstract: The Path Computation Element Communication Protocol (PCEP) provides mechanisms for Path Computation Elements (PCEs) to perform path computations in response to Path Computation Clients (PCCs) requests. The stateful PCE extensions allow stateful control of Multi-Protocol Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE LSPs) using PCEP.
- Use cases of Application-aware Networking (APN) in Edge Computing (draft-liu-apn-edge-usecase)
By Peng Liu, Liang Geng, Shuping Peng, Zhenbin Li, 2020-07-12 TXT HTML PDF
Abstract: The ever-emerging new services are imposing more and more highly demanding requirements on the network. However, the current deployments could not fully accommodate those requirements due to limited capabilities. For example, it is difficult to utilize the traditional centralized deployment mode to meet the low-latency demand of some latency-sensitive applications. Moreover, the total amount of centralized service data is growing exponentially, which brings great pressure on the network bandwidth. There has been a clear trend that decentralized sites comprising of computing and storage resources are deployed at various locations to provide services. In particular, when the sites are deployed at the network edge, i.e. the Edge Computing, it can better handle the business needs of the users nearby, which provides the possibilities to provide differentiated network and computing services. In order to achieve the full benefits of the edge computing, it actually implies a precondition that the network should be aware of the applications' requirements in order to steer their traffic to the network paths that can satisfy their requirements. Application-aware networking (APN) fits as the missing puzzle piece to bridge the applications and the network to accommodate the edge services' needs, fully releasing the benefits of the edge computing.
- Requirement of Computing in network (draft-liu-coinrg-requirement)
By Peng Liu, Liang Geng, 2020-07-12 TXT HTML PDF
Abstract: New technology such as IOT, edge computing,etc. propose the requirement of computing in network, so the convergence of network and computing has become a trend. It will bring some new directions and areas to be considered, such as the relationship between network and computing, the influence of integrating computing to the network, and so on.
- IGP Extensions for Segment Routing Service Segment (draft-lz-lsr-igp-sr-service-segments)
By Liu Yao, Zheng Zhang, 2020-07-10 TXT HTML PDF
Abstract: This document defines extensions to the link-state routing protocols (IS-IS and OSPF) in order to carry service segment information via IGP.
- BCP72 - A Problem Statement (draft-mcfadden-smart-threat-changes)
By Mark McFadden, 2020-07-10 TXT HTML PDF
Abstract: RFC3552/BCP72 describes an Internet Threat model that has been used in Internet protocol design. More than sixteen years have passed since RFC3552 was written and the structure and topology of the Internet has changed. With those changes comes a question: has the Internet Threat Model changed? Or, is the model described in RFC3552 still largely accurate? This draft attempts to describe an non- exhaustive list of changes in the current threat environment. It finds that there are both qualitative and quantitative differences from the environment described in RFC3552 and is intended as input to the IAB program on the Internet threat model started in 2020.
- IPv4 NLRI with IPv6 Next Hop Use Cases (draft-mishra-bess-ipv4nlri-ipv6nh-use-cases)
By Gyan Mishra, 2020-07-12 TXT HTML PDF
Abstract: As Enterprises and Service Providers upgrade their brown field or green field MPLS/SR core to an IPv6 transport such as MPLS LDPv6, SR- MPLSv6 or SRv6, Multiprotocol BGP (MP-BGP)now plays an important role in the transition of the core from IPv4 to IPv6 being able to continue to support legacy IPv4, VPN-IPv4, and Multicast VPN IPv4 customers.
- Flow Classification in Information Centric Networking (draft-moiseenko-icnrg-flowclass)
By Ilya Moiseenko, David Oran, 2020-07-12 TXT HTML PDF
Abstract: For the ubiquitous and highly important Internet protocols (TCP, UDP, IP), flows are conventionally identified by the "5-tuple" of source and destination IP addresses, source and destination port, and protocol type in an IP packet. Information Centric Networking (ICN) is a new paradigm where network communications are accomplished by requesting named content, instead of sending packets to destination addresses. This document describes mechanisms allowing ICN forwarders, consumers, producers and other ICN nodes to encode, decode, and process equivalence class identifiers (flows) at any desired granularity of a routable name prefix and beyond the routable name prefix. This document is a product of the IRTF Information- Centric Networking Research Group (ICNRG).
- IETF Definition of Transport Slice (draft-nsdt-teas-transport-slice-definition)
By Reza Rokui, Shunsuke Homma, Kiran Makhijani, Luis Contreras, Jeff Tantsura, 2020-07-12 TXT HTML PDF
Abstract: This document describes the definition of a slice in the transport networks and its characteristics. The purpose here is to bring clarity and a common understanding of the transport slice concept and describe related terms and their meaning. It explains how transport slices can be used in combination with end to end network slices, or independently.
- BGP SR Policy Extensions to Enable IFIT (draft-qin-idr-sr-policy-ifit)
By Fengwei Qin, Hang Yuan, Tianran Zhou, Giuseppe Fioccola, Yali Wang, 2020-07-10 TXT HTML PDF
Abstract: Segment Routing (SR) policy is a set of candidate SR paths consisting of one or more segment lists and necessary path attributes. It enables instantiation of an ordered list of segments with a specific intent for traffic steering. In-situ Flow Information Telemetry (IFIT) refers to network OAM applications that apply dataplane on- path telemetry techniques. This document defines extensions to BGP to distribute SR policies carrying IFIT information. So that IFIT methods can be enabled automatically when the SR policy is applied.
- YANG Model for Transmission Control Protocol (TCP) Configuration (draft-scharf-tcpm-yang-tcp)
By Michael Scharf, Vishal Murgai, Mahesh Jethanandani, 2020-07-10 TXT HTML PDF
Abstract: This document specifies a YANG model for TCP on devices that are configured by network management protocols. The YANG model defines a container for all TCP connections and groupings of some of the parameters that can be imported and used in TCP implementations or by other models that need to configure TCP parameters. The model includes definitions from YANG Groupings for TCP Client and TCP Servers (I-D.ietf-netconf-tcp-client-server). The model is NMDA (RFC 8342) compliant.
- Telemetry Data Export capability (draft-tao-netconf-data-export-capabilities)
By Qin WU, Liang Geng, Peng Liu, 2020-07-12 TXT HTML PDF
Abstract: This document proposes a YANG module for telemetry data export capability which augments system Capabilities model and provides additional telemetry data export attributes associated with system capability for transport dependent capability negotiation.
- Operations, Administration and Maintenance (OAM) features for RAW (draft-theoleyre-raw-oam-support)
By Fabrice Theoleyre, Georgios Papadopoulos, Greg Mirsky, 2020-07-10 TXT HTML PDF
Abstract: Some critical applications may use a wireless infrastructure. However, wireless networks exhibit a bandwidth of several orders of magnitude lower than wired networks. Besides, wireless transmissions are lossy by nature; the probability that a packet cannot be decoded correctly by the receiver may be quite high. In these conditions, guaranteeing the network infrastructure works properly is particularly challenging, since we need to address some issues specific to wireless networks. This document lists the requirements of the Operation, Administration, and Maintenance (OAM) features recommended to construct a predictable communication infrastructure on top of a collection of wireless segments. This document describes the benefits, problems, and trade-offs for using OAM in wireless networks to achieve Service Level Objectives (SLO).
- Internet Services over ICN in 5G LAN Environments (draft-trossen-icnrg-internet-icn-5glan)
By Dirk Trossen, Chonggang Wang, Sebastian Robitzsch, Martin Reed, Mays AL-Naday, Janne Riihijarvi, 2020-07-10 TXT HTML PDF
Abstract: In this draft, we provide architecture and operations for enabling Internet services over ICN over (5G-enabled) LAN environments. Operations include ICN API to upper layers, HTTP over ICN, Service Proxy Operations, ICN Flow Management, Name Resolution, Mobility Handling, and Dual Stack Device Support.
- Identity Module for TLS Version 1.3 (draft-urien-tls-im)
By Pascal Urien, 2020-07-11 TXT HTML PDF
Abstract: TLS 1.3 will be deployed in the Internet of Things ecosystem. In many IoT frameworks, TLS or DTLS protocols, based on pre-shared key (PSK), are used for device authentication. So PSK tamper resistance, is a critical market request, in order to prevent hijacking issues. If DH exchange is used with certificate bound to DH ephemeral public key, there is also a benefit to protect its signature procedure. The TLS identity module (im) MAY be based on secure element; it realizes some HKDF operations bound to PSK, and cryptographic signature if certificates are used. Secure Element form factor could be standalone chip, or embedded in SOC like eSIM.
- Segment Routing Point-to-Multipoint Policy (draft-voyer-pim-sr-p2mp-policy)
By Daniel Voyer, Clarence Filsfils, Rishabh Parekh, Hooman Bidgoli, Zhaohui Zhang, 2020-07-10 TXT HTML PDF
Abstract: This document describes an architecture to construct a Point-to- Multipoint (P2MP) tree to deliver Multi-point services in a Segment Routing domain. A SR P2MP tree is constructed by stitching a set of Replication segments together. A SR Point-to-Multipoint (SR P2MP) Policy is used to define and instantiate a P2MP tree which is computed by a PCE.
- SR Replication Segment for Multi-point Service Delivery (draft-voyer-spring-sr-replication-segment)
By Daniel Voyer, Clarence Filsfils, Rishabh Parekh, Hooman Bidgoli, Zhaohui Zhang, 2020-07-10 TXT HTML PDF
Abstract: This document describes the SR Replication segment for Multi-point service delivery. A SR Replication segment allows a packet to be replicated from a replication node to downstream nodes.
- Adaptive Subscription to YANG Notification (draft-wang-netconf-adaptive-subscription)
By Qin WU, Wei Song, Liang Geng, Peng Liu, 2020-07-12 TXT HTML PDF
Abstract: This document defines a YANG data model and associated mechanism enabling subscriber's adaptive subscriptions to a publisher's event streams at various different period intervals with which to report updates. Applying these elements allows both subscriber and publisher to automatically adjust the volume of telemetry traffic sent from publisher to the receivers.
- DRIP Authentication Formats (draft-wiethuechter-drip-auth)
By Adam Wiethuechter, Stuart Card, Robert Moskowitz, 2020-07-10 TXT HTML PDF
Abstract: This document describes how to include trust into the ASTM Remote ID specification defined in ASTM 3411-19 under a Broadcast Remote ID (RID) scenario. It defines a few different message schemes (based on the authentication message) that can be used to assure past messages sent by a UA and also act as an assurance for UA trustworthiness in the absence of Internet connectivity at the receiving node.
- Indication of Local DNS Privacy Service During User Access (draft-yan-dprive-local-service-indication)
By Zhiwei Yan, Guanggang Geng, Yang Liu, Xinchang Zhang, 2020-07-12 TXT HTML PDF
Abstract: This document aims to support the indication of privacy service of recursive resolver during the user access.
- BIER Prefix Redistribute (draft-zwzw-bier-prefix-redistribute)
By Zheng Zhang, Wu Bo, Zhaohui Zhang, IJsbrand Wijnands, Yisong Liu, 2020-07-12 TXT HTML PDF
Abstract: This document defines a BIER proxy function to interconnect different underlay routing protocol areas in a network. And a new BIER proxy range sub-TLV is also defined to convey BIER BFR-id information across the routing areas.
Expired Drafts
- Chacha derived AEAD algorithms in JSON Object Signing and Encryption (JOSE) (draft-amringer-jose-chacha)
By Guillaume Amringer, 2020-01-09 TXT HTML PDF
Abstract: This document defines how to use the AEAD algorithms "AEAD_XCHACHA20_POLY1305" and "AEAD_CHACHA20_POLY1305" from [RFC8439] and [I-D.irtf-cfrg-xchacha] in JSON Object Signing and Encryption (JOSE).
- Study Report on a Framework for Cloud Inter-connection toward the Realization of IoT (draft-baba-iot-interconnection)
By Hiroyuki BABA, Izaya Miyake, Jun Matsumura, Yoshiki Ishida, 2020-01-09 TXT HTML PDF
Abstract: This paper describes issues for solutions through cloud inter- connection to structural problems, which are called as "silo effects" found in cloud-connected electric home appliances, housing equipment and sensors in the face of increasingly accelerated connection of them. Specifically, this paper explains an inter-connection agreement considered to be required for enhancement of cloud inter- connection, what performance guarantee as well as IoT supervising and management should be, necessity of inter-connection HUB which is able to provide inter-connection amongst the preponderance of private cloud groups, and the necessity of a mechanism to avoid threats that cause danger to users when we make the inter-connection.
- Report on Problem Solving Experiment for Realization of Web-API-based IoT (draft-baba-iot-webapi)
By Hiroyuki BABA, Yoshiki Ishida, Takayuki Amatsu, Hiroshi Masuda, Shintaro Ogura, Koichi KUNITAKE, 2020-01-09 TXT HTML PDF
Abstract: The University of Tokyo (UOT) is currently performing a demonstration experiment in COMMA House, the experimental smart-house owned by UOT and used as a connected house. The things installed in the house (Things) are operated using applications on smartphones and other devices. The various Things in the smart-house are operated online via a Web API that has been created as a prototype. This report is an overview of the experimental demonstration, which is gradually clarifying that Web API should be effective for solving issues for IoT.
- IANA Registration of Trustword Lists: Guide, Template and IANA Considerations (draft-birk-pep-trustwords)
By Bernie Hoeneisen, Hernani Marques, 2020-01-09 TXT HTML PDF
Abstract: This document specifies the IANA Registration Guidelines for Trustwords, describes corresponding registration procedures, and provides a guideline for creating Trustword list specifications.
- An Information Model for Claims used in RATS (draft-birkholz-rats-information-model)
By Henk Birkholz, Michael Eckel, 2020-01-08 TXT HTML PDF
Abstract: This document defines a standardized information model (IM) for Claims that can be used in remote attestation procedures (RATS). The information elements defined include attestation Claims which provide information about system components characteristics, as well as commonly used attributes and attribute structures that are required by protocols facilitating remote attestation.
- Guidelines for Autonomic Service Agents (draft-carpenter-anima-asa-guidelines)
By Brian Carpenter, Laurent Ciavaglia, Sheng Jiang, Peloso Pierre, 2020-01-09 TXT HTML PDF
Abstract: This document proposes guidelines for the design of Autonomic Service Agents for autonomic networks, as a contribution to describing an autonomic ecosystem. It is based on the Autonomic Network Infrastructure outlined in the ANIMA reference model, using the Autonomic Control Plane and the Generic Autonomic Signaling Protocol.
- Transferring Bulk Data over the GeneRic Autonomic Signaling Protocol (GRASP) (draft-carpenter-anima-grasp-bulk)
By Brian Carpenter, Sheng Jiang, Bing Liu, 2020-01-09 TXT HTML PDF
Abstract: This document describes how bulk data may be transferred between Autonomic Service Agents via the GeneRic Autonomic Signaling Protocol (GRASP). Although not an equivalent of a file transfer protocol, such a technique may be used for non-urgent transfer of data too large to fit into a normal GRASP message.
- BGP-LS Advertisement of Segment Routing Service Segments (draft-dawra-idr-bgp-ls-sr-service-segments)
By Gaurav Dawra, Clarence Filsfils, Ketan Talaulikar, Francois Clad, daniel.bernier@bell.ca, Jim Uttaro, Bruno Decraene, Hani Elmalky, Xiaohu Xu, Jim Guichard, Cheng Li, 2020-01-07 TXT HTML PDF
Abstract: BGP Link-State (BGP-LS) enables distribution of topology information from the network to a Path Computation Engine (PCE) or any controller/application in general so it can learn the network topology. Service functions are deployed as, physical or virtualized elements along with network elements or on servers in data centers. The advertisement of such attached service capabilities along with the network nodes that they are attached to or associated with enables their discovery and the programming of service paths that use these service functions. Segment Routing (SR) brings in the concept of segments which can be topological or service instructions. SR Policies enable the setup of paths which are a mix of topological and service segments.
- SIPv6 Headers and SDP Media Line Address Selection on Multihomed Hosts (draft-dmudric-sipcore-sipv6-addr-selection)
By Dusan Mudric, Dragan Grebovich, 2020-01-08 TXT HTML PDF
Abstract: In the networks where multihomed hosts can have ULA and GUA addresses from different ISPs, multiple SIP signaling and media connectivity issues might arise due to inappropriate address selections. Some of the problems are described in [RFC5220]. Since SIP and SDP allow IP addresses to be embedded into their headers and lines, even if proper addresses are selected initially, SIP is not equipped with the mechanisms to respond to network events, and transition transport to reachable addresses. As a result, SIP messages and media might be filtered by routers, or discarded as unreachable destinations.
- Ground-Based LISP for the Aeronautical Telecommunications Network (draft-haindl-lisp-gb-atn)
By Bernhard Haindl, Manfred Lindner, Reshad Rahman, Marc Portoles-Comeras, Victor Moreno, Fabio Maino, Balaji Venkatachalapathy, 2020-01-08 TXT HTML PDF
Abstract: This document describes the use of the LISP architecture and protocols to address the requirements of the worldwide Aeronautical Telecommunications Network with Internet Protocol Services, as articulated by the International Civil Aviation Organization.
- Group Key Management using IKEv2 (draft-ietf-ipsecme-g-ikev2)
By Brian Weis, Valery Smyslov, 2020-01-08 TXT HTML PDF
Abstract: This document presents a set of IKEv2 exchanges that comprise a group key management protocol. The protocol is in conformance with the Multicast Security (MSEC) key management architecture, which contains two components: member registration and group rekeying. Both components require a Group Controller/Key Server to download IPsec group security associations to authorized members of a group. The group members then exchange IP multicast or other group traffic as IPsec packets. This document obsoletes RFC 6407.
- Deterministic Networking Application in Ring Topologies (draft-jiang-detnet-ring)
By Yuanlong Jiang, Norman Finn, Jeong-dong Ryoo, Balazs Varga, Liang Geng, 2020-01-07 TXT HTML PDF
Abstract: Deterministic Networking (DetNet) provides a capability to carry data flows for real-time applications with extremely low data loss rates and bounded latency. This document describes how DetNet can be used in ring topologies to support Point-to-Point (P2P) and Point-to- Multipoint (P2MP) real-time services.
- pretty Easy privacy (pEp): Mapping of Privacy Rating (draft-marques-pep-rating)
By Hernani Marques, Bernie Hoeneisen, 2020-01-08 TXT HTML PDF
Abstract: In many Opportunistic Security scenarios end-to-end encryption is automatized for Internet users. In addition, it is often required to provide the users with easy means to carry out authentication.
- SRv6 Compatibility with Legacy Devices (draft-peng-spring-srv6-compatibility)
By Hui Tian, Feng Zhao, Chongfeng Xie, Tong Li, Jichun Ma, Shuping Peng, Zhenbin Li, Jim Guichard, 2020-01-08 TXT HTML PDF
Abstract: When deploying SRv6 on legacy devices, there are some compatibility challenges that must be addressed such as the support for SRH processing.
- JSON serialization for Web Linking (draft-pot-json-link)
By Evert Pot, Gabriel Sullice, 2020-01-09 TXT HTML PDF
Abstract: This specification defines a serialization of Web Linking [RFC8288] in the JSON [RFC8259] format.
- SRv6 and MPLS interworking for VPN service (draft-pzm-spring-interdomain-vpn)
By Zheng Zhang, Shaofu Peng, Greg Mirsky, 2020-01-09 TXT HTML PDF
Abstract: This document describes a method to achieve an inter-domain connection for a VPN (Virtual Private Network) service.
- YANG Model for IGP Flexible Algorithm (draft-rasool-lsr-flex-algo-yang)
By Mobashshera Rasool, Sreekanth S, Mahendra Negi, 2020-01-09 TXT HTML PDF
Abstract: This document describes a YANG data model for IGP Flexible Algorithm. The model serves as a base framework for configuring and managing Flexible Algorithms which is used by IGPs to compute constraint based paths over the network.
- DoH Preference Hints for HTTP (draft-schinazi-httpbis-doh-preference-hints)
By David Schinazi, Nick Sullivan, Jesse Kipp, 2020-01-08 TXT HTML PDF
Abstract: When using a publicly available DNS-over-HTTPS (DoH) server, some clients may suffer poor performance when the authoritative DNS server is located far from the DoH server. For example, a publicly available DoH server provided by a Content Delivery Network (CDN) should be able to resolve names hosted by that CDN with good performance but might take longer to resolve names provided by other CDNs, or might provide suboptimal results if that CDN is using DNS- based load balancing and returns different address records depending or where the DNS query originated from. This document attempts to lessen these issues by allowing the web server to indicate to the client which DoH server can best resolve its addresses. This document defines an HTTP header field that enables web host operators to inform user agents of the preferred DoH servers to use for subsequent DNS lookups for the host's domain.
- QUIC Interdomain Troubleshooting (draft-stephan-quic-interdomain-troubleshooting)
By Stephan Emile, Mathilde Cayla, Arnaud Braud, Frederic Fieau, Alexandre Ferrieux, Marcus Ihlar, 2020-01-09 TXT HTML PDF
Abstract: On-path network performance measurements methods currently deployed contribute to the ossification of the Internet because they are expensive to deploy and to maintain. This draft motivates the exposure of QUIC header fields for on-path network measurements and their specification in the QUIC core protocol as a solution to avoid on-path network performance measurements to ossify the IP stack in the future.
- Capabilities and Limitations of an Endpoint-only Security Solution (draft-taddei-smart-cless-introduction)
By Arnaud Taddei, Candid Wueest, Kevin Roundy, Dominique Lazanski, 2020-01-09 TXT HTML PDF
Abstract: In the context of existing, proposed and newly published protocols, this draft RFC is to establish the capabilities and limitations of endpoint-only security solutions and explore benefits and alternatives to mitigate those limits with the support of real case studies.
- Passive Interface Attribute (draft-wang-lsr-passive-interface-attribute)
By Aijun Wang, Zhibo Hu, 2020-01-09 TXT HTML PDF
Abstract: This document describes the mechanism that can be used to differentiate the passive interfaces from the normal interfaces within ISIS domain.
- BIER in IPv6 (BIERin6) (draft-zhang-bier-bierin6)
By Zheng Zhang, Tony Przygienda, IJsbrand Wijnands, Hooman Bidgoli, Mike McBride, 2020-01-08 TXT HTML PDF
Abstract: BIER is a new architecture for the forwarding of multicast data packets. This document defines native IPv6 encapsulation for BIER hop-by-hop forwarding or BIERin6 for short.
|
Drafts Sent to IESG
IESG Progress
- CBOR Object Signing and Encryption (COSE): Hash Algorithms (draft-ietf-cose-hash-algs): IESG Evaluation::AD Followup » ::Revised I-D Needed
By Jim Schaad, 2020-07-06 TXT HTML PDF
Abstract: The CBOR Object Signing and Encryption (COSE) syntax [I-D.ietf-cose-rfc8152bis-struct] does not define any direct methods for using hash algorithms. There are, however, circumstances where hash algorithms are used, such as indirect signatures where the hash of one or more contents are signed, and X.509 certificate or other object identification by the use of a fingerprint. This document defines a set of hash algorithms that are identified by COSE Algorithm Identifiers.
- DetNet Data Plane: IP (draft-ietf-detnet-ip): IESG Evaluation::AD Followup » Approved-announcement sent
By Balazs Varga, Janos Farkas, Lou Berger, Don Fedyk, Stewart Bryant, 2020-07-03 TXT HTML PDF
Abstract: This document specifies the DetNet data plane operation for IP hosts and routers that provide DetNet service to IP encapsulated data. No DetNet-specific encapsulation is defined to support IP flows; instead the existing IP and higher layer protocol header information is used to support flow identification and DetNet service delivery. This document builds on the DetNet Architecture and Data Plane Framework.
- IPv6-Only-Preferred Option for DHCPv4 (draft-ietf-dhc-v6only): Waiting for AD Go-Ahead::Revised I-D Needed » IESG Evaluation
By Lorenzo Colitti, Jen Linkova, Michael Richardson, Tomek Mrugalski, 2020-07-09 TXT HTML PDF
Abstract: This document specifies a DHCPv4 option to indicate that a host supports an IPv6-only mode and willing to forgo obtaining an IPv4 address if the network provides IPv6 connectivity. It also updates RFC2563 to specify the DHCPv4 server behavior when the server receives a DHCPDISCOVER not containing the Auto-Configure option.
- Recommendations for DNS Privacy Service Operators (draft-ietf-dprive-bcp-op): Approved-announcement to be sent::Revised I-D Needed » ::AD Followup
By Sara Dickinson, Benno Overeinder, Roland van Rijswijk-Deij, Allison Mankin, 2020-07-10 TXT HTML PDF
Abstract: This document presents operational, policy, and security considerations for DNS recursive resolver operators who choose to offer DNS Privacy services. With these recommendations, the operator can make deliberate decisions regarding which services to provide, and how the decisions and alternatives impact the privacy of users.
- A YANG Data Model for Layer 2 Network Topologies (draft-ietf-i2rs-yang-l2-network-topology): IESG Evaluation::Revised I-D Needed » ::AD Followup
By Jie Dong, Xiugang Wei, Qin WU, Mohamed Boucadair, Anders Liu, 2020-07-12 TXT HTML PDF
Abstract: This document defines a YANG data model for Layer 2 network topologies. In particular, this data model augments the generic network and network topology data models with Layer 2 specific topology attributes.
- Advanced Unidirectional Route Assessment (AURA) (draft-ietf-ippm-route): Waiting for AD Go-Ahead::Revised I-D Needed » IESG Evaluation
By Jose Alvarez-Hamelin, Alfred Morton, Joachim Fabini, Carlos Pignataro, Ruediger Geib, 2020-07-10 TXT HTML PDF
Abstract: This memo introduces an advanced unidirectional route assessment (AURA) metric and associated measurement methodology, based on the IP Performance Metrics (IPPM) Framework RFC 2330. This memo updates RFC 2330 in the areas of path-related terminology and path description, primarily to include the possibility of parallel subpaths between a given Source and Destination pair, owing to the presence of multi- path technologies.
- Invalid TLV Handling in IS-IS (draft-ietf-lsr-isis-invalid-tlv): Waiting for Writeup » IESG Evaluation
By Les Ginsberg, Paul Wells, Tony Li, Tony Przygienda, Shraddha Hegde, 2020-06-22 TXT HTML PDF
Abstract: Key to the extensibility of the Intermediate System to Intermediate System (IS-IS) protocol has been the handling of unsupported and/or invalid Type/Length/Value (TLV) tuples. Although there are explicit statements in existing specifications, deployment experience has shown that there are inconsistencies in the behavior when a TLV which is disallowed in a particular Protocol Data Unit (PDU) is received.
- PCEP Extensions for LSP scheduling with stateful PCE (draft-ietf-pce-stateful-pce-lsp-scheduling): IESG Evaluation::Revised I-D Needed » ::AD Followup
By Huaimo Chen, Zhuangyan, Qin WU, Daniele Ceccarelli, 2020-07-12 TXT HTML PDF
Abstract: This document defines 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 and the duration of a traffic service in a centralized network environment as stated in RFC 8413.
Drafts Sent to RFC Editor
- The LoST-Validation S-NAPTR Application Service Tag (draft-gellens-lost-validation): Approved-announcement to be sent::AD Followup » RFC Ed Queue
By Randall Gellens, Brian Rosen, 2020-07-01 TXT HTML PDF
Abstract: This document adds the "LoST-Validation" service tag to the Straightforward Naming Authority PoinTeR (S-NAPTR) Application Service Tag IANA registry. This tag can appear in a Naming Authority Pointer (NAPTR) Domain Name System (DNS) record to assist clients of the Location-to-Service Translation Protocol (LoST) in identifying LoST servers explicitly willing to perform location validation. This tag and the information on its use is an update to RFC5222 that enables the explicit discovery of a server that supports location validation.
- Secret Key Transaction Authentication for DNS (TSIG) (draft-ietf-dnsop-rfc2845bis): Approved-announcement to be sent::AD Followup » RFC Ed Queue
By Francis Dupont, Stephen Morris, Paul Vixie, Donald Eastlake, Olafur Gudmundsson, Brian Wellington, 2020-07-10 TXT HTML PDF
Abstract: This document describes a protocol for transaction level authentication using shared secrets and one way hashing. It can be used to authenticate dynamic updates to a DNS zone as coming from an approved client, or to authenticate responses as coming from an approved name server.
- HTTP Client Hints (draft-ietf-httpbis-client-hints): Approved-announcement to be sent::AD Followup » RFC Ed Queue
By Ilya Grigorik, Yoav Weiss, 2020-07-03 TXT HTML PDF
Abstract: HTTP defines proactive content negotiation to allow servers to select the appropriate response for a given request, based upon the user agent's characteristics, as expressed in request headers. In practice, user agents are often unwilling to send those request headers, because it is not clear whether they will be used, and sending them impacts both performance and privacy.
- Structured Field Values for HTTP (draft-ietf-httpbis-header-structure): IESG Evaluation::AD Followup » RFC Ed Queue
By Mark Nottingham, Poul-Henning Kamp, 2020-06-03 TXT HTML PDF
Abstract: This document describes a set of data types and associated algorithms that are intended to make it easier and safer to define and handle HTTP header and trailer fields, known as "Structured Fields", "Structured Headers", or "Structured Trailers". It is intended for use by specifications of new HTTP fields that wish to use a common syntax that is more restrictive than traditional HTTP field values.
Other Status Changes
- TPM-based Network Device Remote Integrity Verification (draft-fedorkow-rats-network-device-attestation): Active » Replaced by draft-ietf-rats-tpm-based-network-device-attest
By Guy Fedorkow, Eric Voit, Jessica Fitzgerald-McKay, 2020-04-16 TXT HTML PDF
Abstract: This document describes a workflow for remote attestation of integrity of network devices.
- Support of asynchronous Enrollment in BRSKI (draft-fries-anima-brski-async-enroll): Active » Replaced by draft-ietf-anima-brski-async-enroll
By Steffen Fries, Hendrik Brockhaus, Eliot Lear, 2020-03-06 TXT HTML PDF
Abstract: This document discusses enhancements of bootstrapping of a remote secure key infrastructure (BRSKI) to also operate in domains featuring no or only timely limited connectivity to backend services offering enrollment functionality, specifically a Public Key Infrastructure (PKI). The enhancements proposed to enable this are also applied to further set of use cases in which a pledge may not have a direct connection to the registrar and is served by for instance by a commissioning tool as an agent providing registrar connectivity. In the context of deploying new devices the design of BRSKI allows for online (synchronous object exchange) and offline interactions (asynchronous object exchange) with a manufacturer's authorization service. For this it utilizes an authenticated self- contained voucher to transport the domain credentials as a signed object to establish an initial trust between a pledge and the target deployment domain. The currently supported enrollment protocol for request and distribution of deployment domain specific device certificates provides only limited support for asynchronous PKI interactions. This memo motivates the enhancement of supporting authenticated self-contained objects for certificate management by using an abstract notation. The enhancement allows on one hand off- site operation of PKI services outside the deployment domain of the pledge. This addresses specifically scenarios, in which the final authorization of a certification request of a pledge cannot be made in the deployment domain and is therefore delegated to a operator backend. On the other hand, this enhancement also facilitates the exchange of certificate management information via a pledge agent. The goal is to enable the usage of existing and potentially new PKI protocols supporting authenticated self-containment for certificate management exchanges.
- draft-marques-pep-email: Expired » Replaced by draft-pep-email
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 
