The Daily Dose of IETF - Issue 3662

BGPsec Validation State Unverified (draft-borchert-sidrops-bgpsec-state-unverified)

By Oliver Borchert, Doug Montgomery, 2020-07-09 TXT HTML PDF

Abstract: In case operators decide to delay BGPsec path validation, none of the available states do properly represent this decision. This document introduces "Unverified" as a well-defined validation state which allows to properly identify a non-evaluated BGPsec routes as not verified.

Diff from 02 to 03 »
RPKI Route Origin Validation State Unverified (draft-borchert-sidrops-rpki-state-unverified)

By Oliver Borchert, Doug Montgomery, 2020-07-09 TXT HTML PDF

Abstract: In case operators decide not to evaluate BGP route prefixes according to RPKI route origin validation (ROV), none of the available states as specified in RFC 6811 do properly represent this decision. This document introduces "Unverified" as well-defined validation state which allows to properly identify route prefixes as not evaluated according to RPKI route origin validation.

Diff from 02 to 03 »
PIM Signaling Through BIER Core (draft-ietf-bier-pim-signaling)

By Hooman Bidgoli, Fengman Xu, Jayant Kotalwar, IJsbrand Wijnands, mankamana mishra, Zhaohui Zhang, 2020-07-09 TXT HTML PDF

Abstract: Consider large networks deploying traditional PIM multicast service. Typically, each portion of these large networks have their own mandates and requirements.

Diff from 08 to 09 »
Document details »
BIER WG »
Media Operations Use Case for an Augmented Reality Application on Edge Computing Infrastructure (draft-krishna-mops-ar-use-case)

By Renan Krishna, Akbar Rahman, 2020-07-09 TXT HTML PDF

Abstract: A use case describing transmission of an application on the Internet that has several unique characteristics of Augmented Reality (AR) applications is presented for the consideration of the Media Operations (MOPS) Working Group. One key requirement identified is that the Adaptive-Bit-Rate (ABR) algorithms' current usage of policies based on heuristics and models is inadequate for AR applications running on the Edge Computing infrastructure.
OAuth 2.0 JSON Request (draft-richer-oauth-json-request)

By Justin Richer, 2020-07-09 TXT HTML PDF

Abstract: This document specifies a method for sending requests to OAuth endpoints as a JSON document instead of a form-encoded document.
Forced Redirects in SMTP (draft-sam-smtp-redirects)

By Ekow Sam, 2020-07-09 TXT HTML PDF

Abstract: This document specifies two new response codes in the SMTP protocol that relate to the redirection of emails meant for one email address to another mail server/email address.
6bed4: IPv6 Anywhere in support of Reliable Peering (draft-vanrein-6bed4)

By Rick van Rein, 2020-07-09 TXT HTML PDF

Abstract: The purpose of 6bed4 is to support IPv6-only networks, hosts and applications. It passes IPv6 frames over UDP between IPv4 sites. Peers connected over 6bed4 can switch to direct routes over UDP/IPv4 after deducing that this will be reliable.

Diff from 03 to 04 »
IS-IS Extensions to Support Transport Network Slices using Segment Routing (draft-zch-lsr-isis-network-slicing)

By Yongqing Zhu, Ran Chen, Shaofu Peng, Fengwei Qin, 2020-07-09 TXT HTML PDF

Abstract: This draft describes the IS-IS extensions required to support transport slices using Segment Routing.

Diff from 04 to 05 »

Updated Drafts

YANG Model for QoS Operational Parameters (draft-asechoud-rtgwg-qos-oper-model)

By Aseem Choudhary, Ing-Wher Chen, 2020-07-09 TXT HTML PDF

Abstract: This document describes a YANG model for Quality of Service (QoS) operational parameters.

Diff from 06 to 07 »
Operations, Administration and Maintenance (OAM) for Deterministic Networks (DetNet) with MPLS Data Plane (draft-ietf-detnet-mpls-oam)

By Greg Mirsky, Mach Chen, 2020-07-09 TXT HTML PDF

Abstract: This document lists functional requirements for Operations, Administration, and Maintenance (OAM) toolset in Deterministic Networks (DetNet) and, using these requirements; defines format and use principals of the DetNet service Associated Channel over a DetNet network with the MPLS data plane..

Diff from 00 to 01 »
Document details »
DETNET WG »
YANG Model for QoS (draft-ietf-rtgwg-qos-model)

By Aseem Choudhary, Mahesh Jethanandani, Norm Strahle, Ebben Aries, Ing-Wher Chen, 2020-07-09 TXT HTML PDF

Abstract: This document describes a YANG model for Quality of Service (QoS) configuration and operational parameters.

Diff from 01 to 02 »
Document details »
RTGWG WG »
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 ([RFC6020], [RFC7950]) for segment routing ([RFC8402]) configuration and operation. This YANG model is intended to be used on network elements to configure or operate segment routing MPLS data plane [RFC8660]. This document defines also generic containers that SHOULD be reused by IGP protocol modules to support segment routing.

Diff from 15 to 16 »
Document details »
SPRING WG »
Transparent Interconnection of Lots of Links (TRILL) Single Area Border RBridge Nickname for Multilevel (draft-ietf-trill-multilevel-single-nickname)

By Mingui Zhang, Donald Eastlake, Radia Perlman, Margaret Cullen, Hongjun Zhai, 2020-07-09 TXT HTML PDF

Abstract: A major issue in multilevel TRILL is how to manage RBridge nicknames. In this document, area border RBridges use a single nickname in both Level 1 and Level 2. RBridges in Level 2 must obtain unique nicknames but RBridges in different Level 1 areas may have the same nicknames.

Diff from 11 to 12 »
State: Waiting for Writeup
ID Tracker » ATOM
Document details »
TRILL WG »
The memory-hard Argon2 password hash and proof-of-work function (draft-irtf-cfrg-argon2)

By Alex Biryukov, Daniel Dinu, Dmitry Khovratovich, Simon Josefsson, 2020-07-09 TXT HTML PDF

Abstract: This document describes the Argon2 memory-hard function for password hashing and proof-of-work applications. We provide an implementer- oriented description with test vectors. The purpose is to simplify adoption of Argon2 for Internet protocols. This document is a product of the Crypto Forum Research Group (CFRG) in the IRTF.

Diff from 10 to 11 »
Coding and congestion control in transport (draft-irtf-nwcrg-coding-and-congestion)

By Nicolas Kuhn, Emmanuel Lochin, Francois Michel, Michael Welzl, 2020-07-09 TXT HTML PDF

Abstract: FEC coding is a reliability mechanism that is distinct and separate from the loss detection of congestion controls. Using FEC coding can be a useful way to deal with transfer tail losses or with networks having non-congestion losses. However, FEC coding mechanisms should not hide congestion signals. This memo offers a discussion of how FEC coding and congestion control can coexist. Another objective is to encourage the research community to also consider congestion control aspects when proposing and comparing FEC coding solutions in communication systems.

Diff from 02 to 03 »
Approaches on Supporting IOAM in IPv6 (draft-song-ippm-ioam-ipv6-support)

By Haoyu Song, Zhenbin Li, Shuping Peng, Jim Guichard, 2020-07-09 TXT HTML PDF

Abstract: It has been proposed to encapsulate IOAM tracing option data fields in IPv6 HbH options header. However, due to size of the trace data and the extension header location in the IPv6 packets, the proposal creates practical challenges for implementation, especially when other extension headers, such as routing header, also exist and require in-network processing. We propose several alternative approaches to address this challenge, including separating the IOAM trace data to a different extension header, using the postcard-based telemetry (e.g., IOAM DEX) instead, and applying the segment IOAM trace export scheme, based on the network scenario and application requirements. We discuss the pros and cons of each approach and hope to foster standard convergence and industry adoption.

Diff from 00 to 01 »
BFD for Geneve (draft-xiao-nvo3-bfd-geneve)

By Xiao Min, Greg Mirsky, Juniper Networks, Jeff Tantsura, 2020-07-09 TXT HTML PDF

Abstract: This document describes the use of the Bidirectional Forwarding Detection (BFD) protocol in point-to-point Generic Network Virtualization Encapsulation (Geneve) tunnels used to make up an overlay network.

Diff from 02 to 03 »

Expired 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-01-06 TXT HTML PDF

Abstract: This document presents extensions to the ISIS protocol for advertising broadcast inter-AS Traffic Engineering (TE) links.

State: Expired
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-01-06 TXT HTML PDF

Abstract: This document presents extensions to the Open Shortest Path First (OSPF) for advertising broadcast inter-AS Traffic Engineering (TE) links.

State: Expired
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-01-06 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.

State: Expired
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-01-06 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.

State: Expired
A Forward-Search P2MP TE LSP Inter-Domain Path Computation (draft-chen-pce-forward-search-p2mp-path)

By Huaimo Chen, 2020-01-06 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.

State: Expired
A Forward-Search P2P TE LSP Inter-Domain Path Computation (draft-chen-pce-forward-search-p2p-path-computation)

By Huaimo Chen, 2020-01-06 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.

State: Expired
PCEP Link State Abstraction (draft-chen-pce-h-connect-access)

By Huaimo Chen, Mehmet Toy, Xufeng Liu, Lei Liu, Zhenqiang Li, 2020-01-06 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.

State: Expired
Hierarchical PCE Determination (draft-chen-pce-h-discovery)

By Huaimo Chen, Mehmet Toy, Xufeng Liu, Lei Liu, Zhenqiang Li, 2020-01-06 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.

State: Expired
Extensions to PCEP for Distributing Label Cross Domains (draft-chen-pce-label-x-domains)

By Huaimo Chen, Autumn Liu, Mehmet Toy, Vic liu, 2020-01-06 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).

State: Expired
Static PCEP Link State (draft-chen-pce-pcc-ted)

By Huaimo Chen, Mehmet Toy, Xufeng Liu, Lei Liu, Zhenqiang Li, 2020-01-06 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.

State: Expired
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-01-06 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.

State: Expired
BGP-LS Extensions for Advertising Path MTU (draft-zhu-idr-bgp-ls-path-mtu)

By Yongqing Zhu, Zhibo Hu, Gang Yan, Junda Yao, 2020-01-06 TXT HTML PDF

Abstract: BGP Link State (BGP-LS) describes a mechanism by which link-state and TE information can be collected from networks and shared with external components using the BGP routing protocol. The centralized controller (PCE/SDN) completes the service path calculation based on the information transmitted by the BGP-LS and delivers the result to the Path Computation Client (PCC) through the PCEP or BGP protocol.

State: Expired

Drafts Sent to IESG

EVPN Operations, Administration and Maintenance Requirements and Framework (draft-ietf-bess-evpn-oam-req-frmwk): Active » Publication Requested

By Samer Salam, Ali Sajassi, Sam Aldrin, John Drake, Donald Eastlake, 2020-07-08 TXT HTML PDF

Abstract: This document specifies the requirements and reference framework for Ethernet VPN (EVPN) Operations, Administration and Maintenance (OAM). The requirements cover the OAM aspects of EVPN and PBB-EVPN. The framework defines the layered OAM model encompassing the EVPN service layer, network layer and underlying Packet Switched Network (PSN) transport layer.

State: Publication Requested
ID Tracker » ATOM
Document details »
BESS WG »

IESG Progress

Extensions to Automatic Certificate Management Environment for end user S/MIME certificates (draft-ietf-acme-email-smime): In Last Call » Waiting for Writeup

By Alexey Melnikov, 2020-06-16 TXT HTML PDF

Abstract: This document specifies identifiers and challenges required to enable the Automated Certificate Management Environment (ACME) to issue certificates for use by email users that want to use S/MIME.

State: Waiting for Writeup
ID Tracker » ATOM
Document details »
ACME WG »
IPv6-Only-Preferred Option for DHCPv4 (draft-ietf-dhc-v6only): Waiting for Writeup » Waiting for AD Go-Ahead::Revised I-D Needed

By Lorenzo Colitti, Jen Linkova, Michael Richardson, Tomek Mrugalski, 2020-06-17 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.

State: Waiting for AD Go-Ahead::Revised I-D Needed
ID Tracker » ATOM
Document details »
DHC WG »
Use cases for DDoS Open Threat Signaling (draft-ietf-dots-use-cases): IESG Evaluation » Approved-announcement to be sent

By Roland Dobbins, Daniel Migault, Robert Moskowitz, Nik Teague, Liang Xia, Kaname Nishizuka, 2020-07-05 TXT HTML PDF

Abstract: The DDoS Open Threat Signaling (DOTS) effort is intended to provide protocols to facilitate interoperability across disparate DDoS mitigation solutions. This document presents sample use cases which describe the interactions expected between the DOTS components as well as DOTS messaging exchanges. These use cases are meant to identify the interacting DOTS components, how they collaborate, and what are the typical information to be exchanged.

State: Approved-announcement to be sent
ID Tracker » ATOM
Document details »
DOTS WG »
Recommendations for DNS Privacy Service Operators (draft-ietf-dprive-bcp-op): IESG Evaluation » Approved-announcement to be sent::Revised I-D Needed

By Sara Dickinson, Benno Overeinder, Roland van Rijswijk-Deij, Allison Mankin, 2020-07-06 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.

State: Approved-announcement to be sent::Revised I-D Needed
ID Tracker » ATOM
Document details »
DPRIVE WG »
HIP Diet EXchange (DEX) (draft-ietf-hip-dex): IESG Evaluation::AD Followup » IESG Evaluation

By Robert Moskowitz, Rene Hummen, Miika Komu, 2020-07-08 TXT HTML PDF

Abstract: This document specifies the Host Identity Protocol Diet EXchange (HIP DEX), a variant of the Host Identity Protocol Version 2 (HIPv2). The HIP DEX protocol design aims at reducing the overhead of the employed cryptographic primitives by omitting public-key signatures and hash functions.

State: IESG Evaluation
ID Tracker » ATOM
Document details »
HIP WG »
A YANG Data Model for Layer 2 Network Topologies (draft-ietf-i2rs-yang-l2-network-topology): IESG Evaluation » ::Revised I-D Needed

By Jie Dong, Xiugang Wei, Qin WU, Mohamed Boucadair, Anders Liu, 2020-06-29 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.

State: IESG Evaluation::Revised I-D Needed
ID Tracker » ATOM
Document details »
I2RS WG »
Simple Two-way Active Measurement Protocol Optional Extensions (draft-ietf-ippm-stamp-option-tlv): Waiting for Writeup » IESG Evaluation

By Greg Mirsky, Xiao Min, Henrik Nydell, Richard Foote, Adi Masputra, Ernesto Ruffini, 2020-07-08 TXT HTML PDF

Abstract: This document describes optional extensions to Simple Two-way Active Measurement Protocol (STAMP) that enable measurement of performance metrics, in addition to ones supported by the STAMP base specification. The document also defines a STAMP Test Session Identifier and thus updates RFC 8762.

State: IESG Evaluation
ID Tracker » ATOM
Document details »
IPPM WG »
Clarification of Enrollment over Secure Transport (EST): transfer encodings and ASN.1 (draft-ietf-lamps-rfc7030est-clarify): In Last Call » Waiting for Writeup

By Michael Richardson, Thomas Werner, Wei Pan, 2020-07-06 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.

State: Waiting for Writeup
ID Tracker » ATOM
Document details »
LAMPS WG »
LISP Generic Protocol Extension (draft-ietf-lisp-gpe): IESG Evaluation » Approved-announcement to be sent::Revised I-D Needed

By Fabio Maino, Jennifer Lemon, Puneet Agarwal, Darrel Lewis, Michael Smith, 2020-07-07 TXT HTML PDF

Abstract: This document describes extensions to the Locator/ID Separation Protocol (LISP) Data-Plane, via changes to the LISP header, to support multi-protocol encapsulation.

State: Approved-announcement to be sent::Revised I-D Needed
ID Tracker » ATOM
Document details »
LISP WG »
The Locator/ID Separation Protocol (LISP) (draft-ietf-lisp-rfc6830bis): IESG Evaluation » ::Revised I-D Needed

By Dino Farinacci, Vince Fuller, David Meyer, Darrel Lewis, Albert Cabellos-Aparicio, 2020-03-05 TXT HTML PDF

Abstract: This document describes the Data-Plane protocol for the Locator/ID Separation Protocol (LISP). LISP defines two namespaces, End-point Identifiers (EIDs) that identify end-hosts and Routing Locators (RLOCs) that identify network attachment points. With this, LISP effectively separates control from data, and allows routers to create overlay networks. LISP-capable routers exchange encapsulated packets according to EID-to-RLOC mappings stored in a local Map-Cache.

State: IESG Evaluation::Revised I-D Needed
ID Tracker » ATOM
Document details »
LISP WG »
Locator/ID Separation Protocol (LISP) Control-Plane (draft-ietf-lisp-rfc6833bis): IESG Evaluation » ::Revised I-D Needed

By Dino Farinacci, Fabio Maino, Vince Fuller, Albert Cabellos-Aparicio, 2020-01-09 TXT HTML PDF

Abstract: This document describes the Control-Plane and Mapping Service for the Locator/ID Separation Protocol (LISP), implemented by two types of LISP-speaking devices -- the LISP Map-Resolver and LISP Map-Server -- that provides a simplified "front end" for one or more Endpoint ID to Routing Locator mapping databases.

State: IESG Evaluation::Revised I-D Needed
ID Tracker » ATOM
Document details »
LISP WG »
Towards Remote Procedure Call Encryption By Default (draft-ietf-nfsv4-rpc-tls): IESG Evaluation » ::Revised I-D Needed

By Trond Myklebust, Chuck Lever, 2020-06-19 TXT HTML PDF

Abstract: This document describes a mechanism that, through the use of opportunistic Transport Layer Security (TLS), enables encryption of in-transit Remote Procedure Call (RPC) transactions while interoperating with ONC RPC implementations that do not support this mechanism. This document updates RFC 5531.

State: IESG Evaluation::Revised I-D Needed
ID Tracker » ATOM
Document details »
NFSV4 WG »
PCEP Extensions for LSP scheduling with stateful PCE (draft-ietf-pce-stateful-pce-lsp-scheduling): IESG Evaluation » ::Revised I-D Needed

By Huaimo Chen, Zhuangyan, Qin WU, Daniele Ceccarelli, 2020-07-06 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.

State: IESG Evaluation::Revised I-D Needed
ID Tracker » ATOM
Document details »
PCE WG »
A Yang Data Model for IGMP and MLD Snooping (draft-ietf-pim-igmp-mld-snooping-yang): IESG Evaluation » ::AD Followup

By Hongji Zhao, Xufeng Liu, Yisong Liu, Mahesh Sivakumar, Anish Peter, 2020-07-08 TXT HTML PDF

Abstract: This document defines a YANG data model that can be used to configure and manage Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping devices. The YANG module in this document conforms to Network Management Datastore Architecture (NMDA).

State: IESG Evaluation::AD Followup
ID Tracker » ATOM
Document details »
PIM WG »
Requirements for Time-Based Loss Detection (draft-ietf-tcpm-rto-consider): IESG Evaluation » ::Revised I-D Needed

By Mark Allman, 2020-06-19 TXT HTML PDF

Abstract: Many protocols must detect packet loss for various reasons (e.g., to ensure reliability using retransmissions or to understand the level of congestion along a network path). While many mechanisms have been designed to detect loss, protocols ultimately can only count on the passage of time without delivery confirmation to declare a packet "lost". Each implementation of a time-based loss detection mechanism represents a balance between correctness and timeliness and therefore no implementation suits all situations. This document provides high-level requirements for time-based loss detectors appropriate for general use in the Internet. Within the requirements, implementations have latitude to define particulars that best address each situation.

State: IESG Evaluation::Revised I-D Needed
ID Tracker » ATOM
Document details »
TCPM WG »