The Daily Dose of IETF - Issue 3293

Brand Indicators for Message Identification (BIMI) (draft-blank-ietf-bimi)

By Seth Blank, Peter Goldstein, Thede Loder, Terry Zink, 2019-02-06 TXT HTML PDF

Abstract: Brand Indicators for Message Identification (BIMI) permits Domain Owners to coordinate with Mail User Agents (MUAs) to display brand- specific Indicators next to properly authenticated messages. There are two aspects of BIMI coordination: a scalable mechanism for Domain Owners to publish their desired indicators, and a mechanism for Mail Transfer Agents (MTAs) to verify the authenticity of the indicator. This document specifies how Domain Owners communicate their desired indicators through the BIMI assertion record in DNS and how that record is to be handled by MTAs and MUAs. The domain verification mechanism and extensions for other mail protocols (IMAP, etc.) are specified in separate documents. MUAs and mail-receiving organizations are free to define their own policies for indicator display that makes use or not of BIMI data as they see fit.
Receivers Guidance for Implementing Branded Indicators for Message Identification (BIMI) (draft-brotman-ietf-bimi-guidance)

By Alexander Brotman, Terry Zink, 2019-02-06 TXT HTML PDF

Abstract: This document is meant to assist receivers or other mailbox providers by providing guidance to implementing Brand Indicators for Message Identification (BIMI). This document is a companion to the main BIMI drafts which should first be consulted and reviewed.
Resource Discovery in Constrained RESTful Environments (CoRE) Using the Constrained RESTful Application Language (CoRAL) (draft-hartke-t2trg-coral-reef)

By Klaus Hartke, 2019-02-06 TXT HTML PDF

Abstract: This document explores how the Constrained RESTful Application Language (CoRAL) might be used for two use cases in Constrained RESTful Environments (CoRE): CoRE Resource Discovery, which allows a client to discover the resources of a server given a host name or IP address, and CoRE Resource Directory, which provides a directory of resources on many servers.
Loop Protection in EVPN networks (draft-snr-bess-evpn-loop-protect)

By Jorge Rabadan, Senthil Sathappan, Kiran Nagaraj, Julio Bueno, Jose Crespo, 2019-02-05 TXT HTML PDF

Abstract: Ethernet Virtual Private Networks (EVPN) is becoming the de-facto standard-based control plane solution for Data Center and layer-2 Service Provider applications. The risk of loops caused by backdoor paths accidentally created within the same broadcast domain, is a general common concern, especially among Service Providers in large Layer-2 networks. While other layer-2 Ethernet technologies use Spanning Tree based Protocols (xSTP) to provide a network-wide loop protection, EVPN has the right tools to detect and protect the network against loops in an efficient and effective way. This document describes a mechanism to provide global loop protection in EVPN networks.

Diff from 02 to 03 »
Use of Abstract NH in Scale-Out peering architecture (draft-szarecki-grow-abstract-nh-scaleout-peering)

By Rafal Szarecki, Kaliraj Vairavakkalai, Natrajan Venkataraman, 2019-02-06 TXT HTML PDF

Abstract: Many large-scale service provider networks use some form of scale-out architecture at peering sites. In such an architecture, each participating Autonomous System (AS) deploys multiple independent Autonomous System Border Routers (ASBRs) for peering, and Equal Cost Multi-Path (ECMP) load balancing is used between them. There are numerous benefits to this architecture, including but not limited to N+1 redundancy and the ability to flexibly increase capacity as needed. A cost of this architecture is an increase in the amount of state in both the control and data planes. This has negative consequences for network convergence time and scale.
Controller Based BGP Multicast Signaling (draft-zzhang-bess-bgp-multicast-controller)

By Zhaohui Zhang, Robert Raszuk, Dante Pacella, Arkadiy Gulko, 2019-02-06 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.

Diff from 00 to 01 »

Updated Drafts

ECC Brainpool Curves for Transport Layer Security (TLS) Version 1.3 (draft-bruckert-brainpool-for-tls13)

By Leonie Bruckert, Johannes Merkle, Manfred Lochter, 2019-02-06 TXT HTML PDF

Abstract: This document specifies the use of several ECC Brainpool curves for authentication and key exchange in the Transport Layer Security (TLS) protocol version 1.3.

Diff from 01 to 02 »
Gap Analysis of Interconnecting Underlay with Cloud Overlay (draft-dm-net2cloud-gap-analysis)

By Linda Dunbar, Andrew Malis, Christian Jacquenet, 2019-02-06 TXT HTML PDF

Abstract: This document analyzes the technological gaps when using SD-WAN to interconnect workloads & apps hosted in various locations, especially cloud data centers when the network service providers do not have or have limited physical infrastructure to reach the locations [Net2Cloud-problem].

Diff from 03 to 04 »
Seamless Interconnect Underlay to Cloud Overlay Problem Statement (draft-dm-net2cloud-problem-statement)

By Linda Dunbar, Andrew Malis, Christian Jacquenet, Mehmet Toy, 2019-02-06 TXT HTML PDF

Abstract: This document describes the problems that enterprises face today when connecting their branch offices to dynamic workloads in third party data centers (a.k.a. Cloud DCs).

Diff from 06 to 07 »
Constrained Internationalized Resource Identifiers (draft-hartke-t2trg-ciri)

By Klaus Hartke, 2019-02-06 TXT HTML PDF

Abstract: Constrained Internationalized Resource Identifiers are an alternate serialization of Uniform Resource Identifiers (URIs) that encodes the URI components in Concise Binary Object Representation (CBOR) instead of a string of characters. This simplifies parsing, reference resolution, and comparison of URIs in environments with severe limitations on processing power, code size, and memory size.

Diff from 00 to 01 »
The Constrained RESTful Application Language (CoRAL) (draft-hartke-t2trg-coral)

By Klaus Hartke, 2019-02-06 TXT HTML PDF

Abstract: The Constrained RESTful Application Language (CoRAL) defines a data model and interaction model as well as two specialized serialization formats for the description of typed connections between resources on the Web ("links"), possible operations on such resources ("forms"), as well as simple resource metadata.

Diff from 06 to 07 »
EST over secure CoAP (EST-coaps) (draft-ietf-ace-coap-est)

By Peter van der Stok, Panos Kampanakis, Michael Richardson, Shahid Raza, 2019-02-06 TXT HTML PDF

Abstract: Enrollment over Secure Transport (EST) is used as a certificate provisioning protocol over HTTPS. Low-resource devices often use the lightweight Constrained Application Protocol (CoAP) for message exchanges. This document defines how to transport EST payloads over secure CoAP (EST-coaps), which allows constrained devices to use existing EST functionality for provisioning certificates.

Diff from 07 to 08 »
Document details »
ACE WG »
Babel Routing Protocol over Datagram Transport Layer Security (draft-ietf-babel-dtls)

By Antonin Decimo, David Schinazi, Juliusz Chroboczek, 2019-02-06 TXT HTML PDF

Abstract: The Babel Routing Protocol does not contain any means to authenticate neighbours or protect messages sent between them. This documents specifies a mechanism to ensure these properties, using Datagram Transport Layer Security (DTLS). This document updates RFC 6126bis.

Diff from 03 to 04 »
Document details »
BABEL WG »
FFV1 Video Coding Format Version 0, 1, and 3 (draft-ietf-cellar-ffv1)

By Michael Niedermayer, Dave Rice, Jerome Martinez, 2019-02-06 TXT HTML PDF

Abstract: This document defines FFV1, a lossless intra-frame video encoding format. FFV1 is designed to efficiently compress video data in a variety of pixel formats. Compared to uncompressed video, FFV1 offers storage compression, frame fixity, and self-description, which makes FFV1 useful as a preservation or intermediate video format.

Diff from 06 to 07 »
Document details »
CELLAR WG »
FFV1 Video Coding Format Version 4 (draft-ietf-cellar-ffv1-v4)

By Michael Niedermayer, Dave Rice, Jerome Martinez, 2019-02-06 TXT HTML PDF

Abstract: This document defines FFV1, a lossless intra-frame video encoding format. FFV1 is designed to efficiently compress video data in a variety of pixel formats. Compared to uncompressed video, FFV1 offers storage compression, frame fixity, and self-description, which makes FFV1 useful as a preservation or intermediate video format.

Diff from 03 to 04 »
Document details »
CELLAR WG »
Deterministic Networking Architecture (draft-ietf-detnet-architecture)

By Norman Finn, Pascal Thubert, Balazs Varga, Janos Farkas, 2019-02-06 TXT HTML PDF

Abstract: This document provides the overall architecture for Deterministic Networking (DetNet), which provides a capability to carry specified unicast or multicast data flows for real-time applications with extremely low data loss rates and bounded latency within a network domain. Techniques used include: 1) reserving data plane resources for individual (or aggregated) DetNet flows in some or all of the intermediate nodes along the path of the flow; 2) providing explicit routes for DetNet flows that do not immediately change with the network topology; and 3) distributing data from DetNet flow packets over time and/or space to ensure delivery of each packet's data in spite of the loss of a path. DetNet operates at the IP layer and delivers service over sub-network technologies such as MPLS and IEEE 802.1 Time-Sensitive Networking (TSN).

Diff from 10 to 11 »
State: IESG Evaluation
ID Tracker » ATOM
Document details »
DETNET WG »
Extensions to Path Computation Element Communication Protocol (PCEP) for Hierarchical Path Computation Elements (PCE) (draft-ietf-pce-hierarchy-extensions)

By Fatai Zhang, Quintin Zhao, Oscar de Dios, R. Casellas, Daniel King, 2019-02-06 TXT HTML PDF

Abstract: The Hierarchical Path Computation Element (H-PCE) architecture is defined in RFC 6805. It provides a mechanism to derive an optimum end-to-end path in a multi-domain environment by using a hierarchical relationship between domains to select the optimum sequence of domains and optimum paths across those domains.

Diff from 08 to 09 »
State: Publication Requested
ID Tracker » ATOM
Document details »
PCE WG »
Path Computation Element (PCE) Protocol Extensions for Stateful PCE usage for Point-to-Multipoint Traffic Engineering Label Switched Paths (draft-ietf-pce-stateful-pce-p2mp)

By Udayasree Palle, Dhruv Dhody, Yosuke Tanaka, Vishnu Beeram, 2019-02-06 TXT HTML PDF

Abstract: The Path Computation Element (PCE) has been identified as an appropriate technology for the determination of the paths of point- to-multipoint (P2MP) TE Label Switched Paths (LSPs). This document provides extensions required for Path Computation Element Communication Protocol (PCEP) so as to enable the usage of a stateful PCE capability in supporting P2MP TE LSPs.

Diff from 08 to 09 »
Document details »
PCE WG »
PCEP Extension for WSON Routing and Wavelength Assignment (draft-ietf-pce-wson-rwa-ext)

By Young Lee, Ramon Casellas, 2019-02-06 TXT HTML PDF

Abstract: This document provides the Path Computation Element communication Protocol (PCEP) extensions for the support of Routing and Wavelength Assignment (RWA) in Wavelength Switched Optical Networks (WSON). Path provisioning in WSONs requires a routing and wavelength assignment (RWA) process. From a path computation perspective, wavelength assignment is the process of determining which wavelength can be used on each hop of a path and forms an additional routing constraint to optical path computation.

Diff from 11 to 12 »
State: IESG Evaluation
ID Tracker » ATOM
Document details »
PCE WG »
Retransmission Timeout Requirements (draft-ietf-tcpm-rto-consider)

By Mark Allman, 2019-02-06 TXT HTML PDF

Abstract: Ensuring reliable communication often manifests in a timeout and retry mechanism. Each implementation of a retransmission timeout mechanism represents a balance between correctness and timeliness and therefore no implementation suits all situations. This document provides high-level requirements for retransmission timeout schemes appropriate for general use in the Internet. Within the requirements, implementations have latitude to define particulars that best address each situation.

Diff from 06 to 07 »
Document details »
TCPM WG »
An Unreliable Datagram Extension to QUIC (draft-pauly-quic-datagram)

By Tommy Pauly, Eric Kinnear, David Schinazi, 2019-02-06 TXT HTML PDF

Abstract: This document defines an extension to the QUIC transport protocol to add support for sending and receiving unreliable datagrams over a QUIC connection.

Diff from 01 to 02 »
Enabling secure network enrollment in RPL networks (draft-richardson-6tisch-roll-enrollment-priority)

By Michael Richardson, 2019-02-06 TXT HTML PDF

Diff from 01 to 02 »

Expired Drafts

Right to Life Issues in Internet Content and Protocols (draft-elris-hrpc-righttolife)

By Nalini Elkins, William Jouris, 2018-08-05 TXT HTML PDF

Abstract: This document proposes a new IANA registry of Guidance for Blocked Content. Blocked Content is content which has no significant valid use and conflicts with the "Universal Declaration of Human Rights" . The format of the proposed registry is provided, and some initial categories; for example, human trafficking and 3d printed guns.

State: Expired
Security for 5G (draft-naresh-mptcp-security-for-5g)

By Naresh Kumar, Karan Verma, 2018-08-05 TXT HTML PDF

Abstract: This document proposes a new method which provides the capability to resolve issue of attack over Mobile Communication System. This document assumes that the reader is familiar with some concepts and details regarding Authentication and Encryption in generations of Mobile Telephony.

State: Expired

Drafts Sent to IESG

Consolidated IASA 2.0 Updates of IETF Administrative Terminology (draft-ietf-iasa2-consolidated-upd): Active » Publication Requested

By John Klensin, 2019-01-31 TXT HTML PDF

Abstract: In 2018, the IETF began the transition to a new administrative structure and updated its IETF Administrative Support Activity (IASA) to a new "IASA 2.0" structure. In addition to more substantive changes that are described in other documents, the transition to the 2018 IETF Administrative Support structure changes several position titles and organizational relationships that are referenced elsewhere. Rather than reissue those referencing documents individually, this specification provides updates to them and deprecates some now-obsolete documents to ensure that there is no confusion due to these changes.

State: Publication Requested
ID Tracker » ATOM
Document details »
IASA2 WG »
Structure of the IETF Administrative Support Activity, Version 2.0 (draft-ietf-iasa2-rfc4071bis): Active » Publication Requested

By Brian Haberman, Joseph Hall, Jason Livingood, 2019-01-10 TXT HTML PDF

Abstract: The IETF Administrative Support Activity (IASA) was originally established in 2005. In the years since then, the needs of the IETF evolved in ways that required changes to its administrative structure. The purpose of this document is to document and describe the IASA 2.0 structure.

State: Publication Requested
ID Tracker » ATOM
Document details »
IASA2 WG »
Extensions to Path Computation Element Communication Protocol (PCEP) for Hierarchical Path Computation Elements (PCE) (draft-ietf-pce-hierarchy-extensions): Active » Publication Requested

By Fatai Zhang, Quintin Zhao, Oscar de Dios, R. Casellas, Daniel King, 2019-02-06 TXT HTML PDF

Abstract: The Hierarchical Path Computation Element (H-PCE) architecture is defined in RFC 6805. It provides a mechanism to derive an optimum end-to-end path in a multi-domain environment by using a hierarchical relationship between domains to select the optimum sequence of domains and optimum paths across those domains.

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

IESG Progress

Best Practices for Securing RTP Media Signaled with SIP (draft-ietf-sipbrandy-rtpsec): AD Evaluation::AD Followup » Last Call Requested

By Jon Peterson, Richard Barnes, Russ Housley, 2019-02-01 TXT HTML PDF

Abstract: Although the Session Initiation Protocol (SIP) includes a suite of security services that has been expanded by numerous specifications over the years, there is no single place that explains how to use SIP to establish confidential media sessions. Additionally, existing mechanisms have some feature gaps that need to be identified and resolved in order for them to address the pervasive monitoring threat model. This specification describes best practices for negotiating confidential media with SIP, including both comprehensive protection solutions which bind the media to SIP-layer identities as well as opportunistic security solutions.

State: Last Call Requested
ID Tracker » ATOM
Document details »
SIPBRANDY WG »