https://tools.ietf.org/html/ New Current Internet Drafts (All Categories) en Fri, 03 Jan 2020 14:31:19 GMT 1 hourly 1970-01-01T00:40+00:00 60 henrik@levkowetz.com http://www.interglacial.com/rss/about.html https://tools.ietf.org/html/draft-geib-ippm-connectivity-monitoring-02 2020-01-02, rev -02: Within a Segment Routing domain, segment routed measurement packets can be sent along pre-determined paths. This enables new kinds of measurements. Connectivity monitoring allows to supervise the state and performance of a connection or a (sub)path from one or a few central monitoring systems. This document specifies a suitable type-P connectivity monitoring metric. https://tools.ietf.org/html/draft-google-self-published-geofeeds-07 2020-01-02, rev -07: This document records a format whereby a network operator can publish a mapping of IP address prefixes to simplified geolocation information, colloquially termed a geolocation "feed". Interested parties can poll and parse these feeds to update or merge with other geolocation data sources and procedures. This format intentionally only allows specifying coarse level location. https://tools.ietf.org/html/draft-bryant-mpls-sfl-control-05 2020-01-02, rev -05: In draft-ietf-mpls-sfl-framework the concept of MPLS synonymous flow labels (SFL) was introduced. This document describes a control protocol that runs over an associated control header to request, withdrawn and extend the lifetime of such labels. https://tools.ietf.org/html/draft-ietf-rtgwg-policy-model-08 2020-01-02, rev -08: This document defines a YANG data model for configuring and managing routing policies in a vendor-neutral way and based on actual operational practice. The model provides a generic policy framework which can be augmented with protocol-specific policy configuration. https://tools.ietf.org/html/draft-eastlake-rfc6931bis-xmlsec-uris-11 2020-01-02, rev -11: This document updates and corrects the IANA registry for the list of URIs intended for use with XML digital signatures, encryption, canonicalization, and key management. These URIs identify algorithms and types of information. This document corrrects three errata against and obsoletes RFC 6931. https://tools.ietf.org/html/draft-templin-intarea-6706bis-19 2020-01-02, rev -19: This document specifies the operation of IP over tunnel virtual links using Asymmetric Extended Route Optimization (AERO). AERO interfaces use an IPv6 link-local address format that supports operation of the IPv6 Neighbor Discovery (ND) protocol and links ND to IP forwarding. Prefix delegation/registration services are employed for network admission and to manage the routing system. Multilink operation, mobility management, quality of service (QoS) signaling and route optimization are naturally supported through dynamic neighbor cache updates. Standard IP multicasting services are also supported. AERO is a widely-applicable mobile internetworking service especially well-suited to aviation services, mobile Virtual Private Networks (VPNs) and many other applications. https://tools.ietf.org/html/draft-ietf-capport-api-04 2020-01-02, rev -04: This document describes an HTTP API that allows clients to interact with a Captive Portal system. https://tools.ietf.org/html/draft-ietf-sfc-nsh-ecn-support-02 2020-01-02, rev -02: Explicit congestion notification (ECN) allows a forwarding element to notify downstream devices of the onset of congestion without having to drop packets. Coupled with a means to feed back information about congestion to upstream nodes, this can improve network efficiency through better congestion control, frequently without packet drops. This document specifies ECN and congestion feedback support within a Service Function Chaining (SFC) domain through use of the Network Service Header (NSH, RFC 8300) and IP Flow Information Export (IPFIX, draft-ietf-tsvwg-tunnel-congestion-feedback). https://tools.ietf.org/html/draft-papadopoulos-raw-pareo-reqs-01 2020-01-02, rev -01: The Packet Replication and Elimination (PRE) mechanism duplicates data packets into several paths in the network to increase reliability and provide low jitter. PRE may be used to complement layer-2 Automatic Repeat reQuest (ARQ) and receiver-end Ordering to form the PAREO functions. Over a wireless medium, this technique can take advantage of communication Overhearing, when parallel transmissions over two adjacent paths are scheduled. This document presents the concept and details the required changes to the current specifications that will be necessary to enable the PAREO functions. https://tools.ietf.org/html/draft-gmsm-bess-evpn-bfd-04 2020-01-02, rev -04: This document specifies proactive, in-band network OAM mechanisms to detect loss of continuity and miss-connection faults that affect unicast and multi-destination paths (used by Broadcast, Unknown Unicast and Multicast traffic) in an Ethernet VPN (EVPN) network. The mechanisms specified in the draft are based on the widely adopted Bidirectional Forwarding Detection (BFD) protocol. https://tools.ietf.org/html/draft-anonymous-rtgwg-hlarp-00 2020-01-02, rev -00: This internet-draft describes a protocol with an addressing scheme where members of the internet are addressed by their physical addresses and by an implementing internet router that can contact them. The packets sent by the protocol include handshake messages, client data, and the status of the data being sent. A routing procedure is suggested according to special addresses that carry information about the region of a router. https://tools.ietf.org/html/draft-stepanek-jscontact-06 2020-01-02, rev -06: This specification defines a data model and JSON representation of contact card information that can be used for data storage and exchange in address book or directory applications. It aims to be an alternative to the vCard data format and to be unambiguous, extendable and simple to process. In contrast to the JSON-based jCard format, it is not a direct mapping from the vCard data model and expands semantics where appropriate. https://tools.ietf.org/html/draft-mglt-lurk-tls12-02 2020-01-02, rev -02: This document describes the LURK Extension 'tls12' which enables interactions between a LURK Client and a LURK Server in a context of authentication with (D)TLS 1.2. https://tools.ietf.org/html/draft-ietf-nfsv4-rpcrdma-cm-pvt-data-06 2020-01-02, rev -06: This document specifies the format of RDMA-CM Private Data exchanged between RPC-over-RDMA version 1 peers as part of establishing a connection. The addition of the private data payload specified in this document is an optional extension that does not alter the RPC- over-RDMA version 1 protocol. This document updates RFC 8166. https://tools.ietf.org/html/draft-templin-atn-aero-interface-10 2020-01-02, rev -10: Aeronautical mobile nodes (e.g., aircraft of various configurations) communicate with networked correspondents over multiple access network data links and configure mobile routers to connect their on- board networks. An Air-to-Ground (A/G) interface specification is therefore needed for coordination with the ground domain network. This document specifies the transmission of IPv6 packets over aeronautical ("aero") interfaces. https://tools.ietf.org/html/draft-ietf-rtgwg-atn-bgp-05 2020-01-01, rev -05: The International Civil Aviation Organization (ICAO) is investigating mobile routing solutions for a worldwide Aeronautical Telecommunications Network with Internet Protocol Services (ATN/IPS). The ATN/IPS will eventually replace existing communication services with an IPv6-based service supporting pervasive Air Traffic Management (ATM) for Air Traffic Controllers (ATC), Airline Operations Controllers (AOC), and all commercial aircraft worldwide. This informational document describes a simple and extensible mobile routing service based on industry-standard BGP to address the ATN/IPS requirements. https://tools.ietf.org/html/draft-templin-6man-dhcpv6-ndopt-09 2020-01-01, rev -09: IPv6 Neighbor Discovery (IPv6ND) specifies a control message set for nodes to discover neighbors, routers, prefixes and other services on the link. It also supports a manner of StateLess Address AutoConfiguration (SLAAC), while the Dynamic Host Configuration Protocol for IPv6 (DHCPv6) specifies a separate stateful service. This document presents IPv6ND extensions for providing a unified stateful/stateless configuration service. https://tools.ietf.org/html/draft-zhou-ippm-ioam-yang-05 2020-01-01, rev -05: In-situ Operations, Administration, and Maintenance (IOAM) records operational and telemetry information in user packets while the packets traverse a path between two points in the network. This document defines a YANG module for the IOAM function. https://tools.ietf.org/html/draft-ietf-bess-evpn-oam-req-frmwk-02 2020-01-01, rev -02: 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. https://tools.ietf.org/html/draft-templin-v6ops-pdhost-25 2020-01-01, rev -25: Requesting nodes typically acquire IPv6 prefixes from a prefix delegation service for the network. The requesting node can provision the prefix according to whether it acts as a router on behalf of any downstream networks and/or as a host on behalf of its local applications. In the latter case, the requesting node can use portions of the delegated prefix for its own multi-addressing purposes. This document therefore considers prefix delegation models for both the classic routing and various multi-addressing use cases. https://tools.ietf.org/html/draft-templin-ipwave-uam-its-01 2020-01-01, rev -01: Urban Air Mobility concerns the introduction of manned and unmanned aircraft within urban environments, while Intelligent Transportation Systems have traditionally considered only terrestrial vehicles operating on city streets and highways. This document considers the implications for introduction of low-altitude aircraft within urban environments operating in harmony with ground transportation. https://tools.ietf.org/html/draft-ietf-idr-flowspec-l2vpn-13 2019-12-31, rev -13: This document defines a Border Gateway Protocol (BGP) Flow-spec extension to disseminate Ethernet Layer 2 (L2) and Layer 2 Virtual Private Network (L2VPN) traffic filtering rules either by themselves or in conjunction with L3 Flow-specs. AFI/SAFI 6/133 and 25/134 are used for these purposes. New component types and an extended community also are defined. https://tools.ietf.org/html/draft-ietf-anima-bootstrapping-keyinfra-32 2019-12-31, rev -32: This document specifies automated bootstrapping of an Autonomic Control Plane. To do this a Secure Key Infrastructure is bootstrapped. This is done using manufacturer-installed X.509 certificates, in combination with a manufacturer's authorizing service, both online and offline. We call this process the Bootstrapping Remote Secure Key Infrastructure (BRSKI) protocol. Bootstrapping a new device can occur using a routable address and a cloud service, or using only link-local connectivity, or on limited/ disconnected networks. Support for deployment models with less stringent security requirements is included. Bootstrapping is complete when the cryptographic identity of the new key infrastructure is successfully deployed to the device. The established secure connection can be used to deploy a locally issued certificate to the device as well. https://tools.ietf.org/html/draft-ietf-capport-architecture-05 2019-12-31, rev -05: This document aims to document consensus on the CAPPORT architecture. DHCP or Router Advertisements, an optional signaling protocol, and an HTTP API are used to provide the solution. The role of Provisioning Domains (PvDs) is described. https://tools.ietf.org/html/draft-brockhaus-lamps-cmp-updates-02 2019-12-31, rev -02: This document contains a set of updates to the base syntax of Certificate Management Protocol (CMP) version 2. This document updates RFC 4210. https://tools.ietf.org/html/draft-tokar-pce-sid-algo-01 2019-12-31, rev -01: The Algorithm associated with a prefix Segment-ID (SID) defines the path computation Algorithm used by Interior Gateway Protocols (IGPs). This information is available to controllers such as the Path Computation Element (PCE) via topology learning. This document proposes an approach for informing headend routers regarding the Algorithm associated with each prefix SID used in PCE-computed paths, as well as signalling a specific SID algorithm as a constraint to the PCE. https://tools.ietf.org/html/draft-inadarei-api-health-check-04 2019-12-31, rev -04: This document proposes a service health check response format for HTTP APIs. https://tools.ietf.org/html/draft-song-opsawg-ifit-framework-10 2019-12-31, rev -10: As networks increase in scale and network operations become more sophisticated, traditional Operation, Administration and Maintenance (OAM) methods, which include proactive and reactive techniques, running in active and passive modes, become more susceptible to measurement accuracy and misconfiguration errors. With the advent of programmable data-plane, emerging on-path telemetry techniques provide unprecedented flow insight and realtime notification of network issues. https://tools.ietf.org/html/draft-brockhaus-lamps-lightweight-cmp-profile-02 2019-12-31, rev -02: The goal of this document is to facilitate interoperability and automation by profiling the Certificate Management Protocol (CMP) version 2 and 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 transactions are specified as mandatory. To foster interoperability also in more complex scenarios, other types of transactions are specified as recommended or optional. https://tools.ietf.org/html/draft-wilde-linkset-05 2019-12-31, rev -05: This specification defines two media types for representing sets of links and a link relation type for referring to sets of links. The media types can be used to represents links in a standalone fashion, in one case in the native format as used in the HTTP "Link" header field, and in the other case in a JSON-based format. The link relation type can be used to point at a resource that provides a set of links. https://tools.ietf.org/html/draft-hallambaker-rfctool-04 2019-12-31, rev -04: RFCTool is a documentation tool for building specifications from multiple sources and multiple source formats. Source formats currently supported are OOXML/Word, Markdown, XML2RFC and SVG. Publication formats supported are plaintext, HTML and XML2RFC. This document provides information on how to use RFCTool to generate Internet Drafts and RFCs. https://tools.ietf.org/html/draft-nakajima-crypto-asset-terminology-03 2019-12-31, rev -03: This document provides terminology used in cryptoassets. https://tools.ietf.org/html/draft-ietf-git-using-github-03 2019-12-31, rev -03: This document describes best practices for Working Groups that use GitHub for their work. https://tools.ietf.org/html/draft-pwouters-ikev1-ipsec-graveyard-04 2019-12-30, rev -04: Internet Key Exchange version 1 (IKEv1) is deprecated. Accordingly, IKEv1 has been moved to Historic status. A number of old algorithms that are associated with IKEv1, and not widely implemented for IKEv2 are deprecated as well. IANA is instructed to close all IKEv1 registries. https://tools.ietf.org/html/draft-peng-lsr-flex-algo-l2bundles-00 2019-12-30, rev -00: IGP Flex Algorithm proposes a solution that allows IGPs themselves to compute constraint based paths over the network, and it also specifies a way of using Segment Routing (SR) Prefix-SIDs and SRv6 locators to steer packets along the constraint-based paths. This document describes how to create Flex-algo plane with L2bundles scenario. https://tools.ietf.org/html/draft-pot-json-link-00 2019-12-30, rev -00: This specification defines a serialization of Web Linking [RFC8288] in the JSON [RFC8259] format. https://tools.ietf.org/html/draft-ietf-oauth-par-00 2019-12-30, rev -00: 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. https://tools.ietf.org/html/draft-sun-nmrg-hybrid-switching-00 2019-12-30, rev -00: The fast increase in traffic volumn within and outside Datacenters is placing an unprecendented challenge on the underline network, in both the capacity it can provide, and the way it delivers traffic. When a large portion of network traffic is contributed by large flows, providing high capacity and slow to change optical circuit switching along side fine-granular packet services may potentially improve network utility and reduce both CAPEX and OpEX. This gives rise to the concept of hybrid switching - a paradigm that seeks to make the best of packet and circuit switching. https://tools.ietf.org/html/draft-faibish-nfsv4-data-reduction-attributes-02 2019-12-30, rev -02: This document proposes extending NFSv4 operations to add new named attributes to be used in the protocol to provide information about the data reduction properties of files. The new data reduction attributes are proposed to allow the client application to communicate to the NFSv4 server data reduction attributes associated with files and directories using new metadata, communicated to the Block Storage data reduction engines. Corresponding new named attributes are proposed to allow clients and client applications to query the server for data reduction attributes support and allow to get and set data reduction attributes on files and directories. Such data reduction metadata is used as hints to the file server about what type of data reduction to apply. The proposed data reduction attributes include achievable ratios for compression and deduplication plus whether each data reduction technique applies to a file or directory. https://tools.ietf.org/html/draft-ietf-babel-rfc6126bis-16 2019-12-30, rev -16: Babel is a loop-avoiding distance-vector routing protocol that is robust and efficient both in ordinary wired networks and in wireless mesh networks. This document describes the Babel routing protocol, and obsoletes RFCs 6126 and 7557. https://tools.ietf.org/html/draft-ietf-netmod-yang-versioning-reqs-02 2019-12-30, rev -02: This document describes the problems that can arise because of the YANG language module update rules, that require all updates to YANG module preserve strict backwards compatibility. It also defines the requirements on any solution designed to solve the stated problems. This document does not consider possible solutions, nor endorse any particular solution. https://tools.ietf.org/html/draft-ietf-core-senml-etch-06 2019-12-27, rev -06: The Sensor Measurement Lists (SenML) media type and data model can be used to send collections of resources, such as batches of sensor data or configuration parameters. The CoAP FETCH, PATCH, and iPATCH methods enable accessing and updating parts of a resource or multiple resources with one request. This document defines new media types for the CoAP FETCH, PATCH, and iPATCH methods for resources represented with the SenML data model. https://tools.ietf.org/html/draft-richardson-opsawg-securehomegateway-mud-02 2019-12-27, rev -02: This informational document details the mechanism used by the CIRA Secure Home Gateway (SHG) to load MUD definitions for devices which have no integrated MUD (RFC8520) support. https://tools.ietf.org/html/draft-ietf-sipcore-rfc4028bis-02 2019-12-27, rev -02: This document defines an extension to the Session Initiation Protocol (SIP). This extension allows for a periodic refresh of SIP sessions through a re-INVITE or UPDATE request. The refresh allows both user agents and proxies to determine whether the SIP session is still active. The extension defines two new header fields: Session- Expires, which conveys the lifetime of the session, and Min-SE, which conveys the minimum allowed value for the session timer. https://tools.ietf.org/html/draft-klensin-rfc5321bis-02 2019-12-27, rev -02: This document is a specification of the basic protocol for Internet electronic mail transport. It consolidates, updates, and clarifies several previous documents, making all or parts of most of them obsolete. It covers the SMTP extension mechanisms and best practices for the contemporary Internet, but does not provide details about particular extensions. Although SMTP was designed as a mail transport and delivery protocol, this specification also contains information that is important to its use as a "mail submission" protocol for "split-UA" (User Agent) mail reading systems and mobile environments. https://tools.ietf.org/html/draft-ietf-emu-eap-tls13-08 2019-12-27, rev -08: This document specifies the use of EAP-TLS with TLS 1.3 while remaining backwards compatible with existing implementations of EAP- TLS. TLS 1.3 provides significantly improved security, privacy, and reduced latency when compared to earlier versions of TLS. EAP-TLS with TLS 1.3 further improves security and privacy by mandating use of privacy and revocation checking. This document updates RFC 5216. https://tools.ietf.org/html/draft-mcd-identifier-access-http-00 2019-12-26, rev -00: This document describes an Extensible Provisioning Protocol (EPP) for the provisioning and management of enterprises and identifiers between the server which is called Business Management System (BMS) and is entitled to manage the identifier top-level node and the client which is also referred to as Second Node Management System (SNMS). Specified in XML, the mapping defines EPP command syntax and semantics as applied to enterprise and identifier management. https://tools.ietf.org/html/draft-ietf-ipsecme-qr-ikev2-10 2019-12-26, rev -10: The possibility of quantum computers poses a serious challenge to cryptographic algorithms deployed widely today. IKEv2 is one example of a cryptosystem that could be broken; someone storing VPN communications today could decrypt them at a later time when a quantum computer is available. It is anticipated that IKEv2 will be extended to support quantum-secure key exchange algorithms; however that is not likely to happen in the near term. To address this problem before then, this document describes an extension of IKEv2 to allow it to be resistant to a quantum computer, by using preshared keys. https://tools.ietf.org/html/draft-wu-identifier-sln-objects-mapping-00 2019-12-25, rev -00: This document specifies the format, contents and semantics of data escrow deposits for Industrial Internet Identifier Second-level Node (SLN). SLN directly serves enterprises and provides services such as identifier registration, identifier resolution, data sharing, etc. The mapping objects in this document mainly refers to the enterprise registration information of the SLN and the Enterprise-level Node (ELN) registered in the SLN. https://tools.ietf.org/html/draft-industrial-internet-identifier-data-escrow-00 2019-12-25, rev -00: This document specifies the format and contents of data escrow deposits targeted primarily for Industrial Internet Identifier Node (IIIN) which provides identifier registration. However, this specification was designed to be independent of the underlying objects that are being escrowed, therefore it could be used for purposes other than IIIN. https://tools.ietf.org/html/draft-mcd-identifier-access-authority-00 2019-12-25, rev -00: This document specifies a method to find which Industrial Internet Identifier Data Access Protocol (IIIDAP) server is authoritative to answer queries for a request of identifier data. https://tools.ietf.org/html/draft-ma-identifier-access-http-00 2019-12-25, rev -00: This document describes an Extensible Provisioning Protocol (EPP) for the provisioning and management of enterprises and identifiers between the server which is called Business Management System (BMS) and is entitled to manage the identifier top-level node and the client which is also referred to as Second Node Management System (SNMS). Specified in XML, the mapping defines EPP command syntax and semantics as applied to enterprise and identifier management. https://tools.ietf.org/html/draft-mcd-identifier-access-query-00 2019-12-25, rev -00: This document describes uniform patterns to construct HTTP URLs that may be used to retrieve identifier information from Second-Level Nodes (SLN) using "RESTful" web access patterns. These uniform patterns define the query syntax for the Industrial Internet Identifier Data Access Protocol (IIIDAP). https://tools.ietf.org/html/draft-irtf-nmrg-ibn-concepts-definitions-00 2019-12-25, rev -00: Intent and Intent-Based Networking are taking the industry by storm. At the same time, those terms are used loosely and often inconsistently, in many cases overlapping and confused with other concepts such as "policy". This document is intended to clarify the concept of "Intent" and provide an overview of functionality that associated with it. The goal is to contribute towards a common and shared understanding of terms, concepts, and functionality which can be used as foundation to guide further definition of associated research and engineering problems and their solutions. https://tools.ietf.org/html/draft-mcd-identifier-access-responce-00 2019-12-25, rev -00: This document describes JSON data structures representing identifier information maintained by Second-Level Nodes (SLN). These data structures are used to form Industrial Internet Identifier Data Access Protocol (IIIDAP) query responses. https://tools.ietf.org/html/draft-mcd-identifier-access-security-00 2019-12-25, rev -00: The Industrial Internet Identifier Data Access Protocol (IIIDAP) provides "RESTful" web services to retrieve identifier metadata from Second-Level Node (SLN). This document describes information security services, including access control, authentication, authorization, availability, data confidentiality, and data integrity for IIIDAP. https://tools.ietf.org/html/draft-faibish-iot-ddos-usecases-01 2019-12-25, rev -01: This document specifies several usecases related to the different ways IoT devices are exploited by malicious adversaries to instantiate Distributed Denial of Services (DDoS) attacks. The attacks are generted from IoT devices that have no proper protection against generating unsolicited communication messages targeting a certain network and creating large amounts of network traffic. The attackers take advantage of breaches in the configuration data in unprotected IoT devices exploited for DDoS attacks. The attackers take advantage of the IoT devices that can send network packets that were generated by malicious code that interacts with an OS implementation that runs on the IoT devices. The prupose of this draft is to present possible IoT DDoS usecases that need to be prevented by TEE. The major enabler of such attacks is related to IoT devices that have no OS or unprotected EE OS and run code that is downloaded to them from the TA and modified by man-in-the-middle that inserts malicious code in the OS. https://tools.ietf.org/html/draft-li-lsr-isis-area-proxy-01 2019-12-24, rev -01: Link state routing protocols have hierarchical abstraction already built into them. However, when lower levels are used for transit, they must expose their internal topologies to each other, leading to scale issues. https://tools.ietf.org/html/draft-irtf-panrg-questions-04 2019-12-24, rev -04: In contrast to the present Internet architecture, a path-aware internetworking architecture has two important properties: it exposes the properties of available Internet paths to endpoints, and provides for endpoints and applications to use these properties to select paths through the Internet for their traffic. This document poses questions in path-aware networking open as of 2019, that must be answered in the design, development, and deployment of path-aware intetnetworks. It was originally written to frame discussions in the Path Aware Networking proposed Research Group (PANRG), and has been published to snapshot current thinking in this space. https://tools.ietf.org/html/draft-ietf-mile-jsoniodef-12 2019-12-24, rev -12: The Incident Object Description Exchange Format defined in RFC 7970 provides an information model and a corresponding XML data model for exchanging incident and indicator information. This draft gives implementers and operators an alternative format to exchange the same information by defining an alternative data model implementation in JSON and its encoding in CBOR.