Searching for source:IETF

8,337 results
Record publications over time
Ironsift results are limited for unregistered users. Register or log in to see all records.

Request for Comments RFC8475 – IETF – Oct 1, 2018

Using Conditional Router Advertisements for Enterprise Multihoming

This document discusses the most common scenarios of connecting an enterprise network to multiple ISPs using an address space assigned by an ISP and how the approach proposed in "Enterprise Multihoming using Provider-Assigned Addresses without Netw...
Full record
Register to view full records and advanced analytics.

Request for Comments RFC8407 – IETF – Oct 1, 2018

Guidelines for Authors and Reviewers of Documents Containing YANG Data Models

This memo provides guidelines for authors and reviewers of specifications containing YANG modules. Recommendations and procedures are defined, which are intended to increase interoperability and usability of Network Configuration Protocol (NETCONF)...
Full record

Request for Comments RFC8450 – IETF – Oct 1, 2018

RTP Payload Format for VC-2 High Quality (HQ) Profile

This memo describes an RTP payload format for the High Quality (HQ) profile of Society of Motion Picture and Television Engineers Standard ST 2042-1, known as VC-2. This document describes the transport of HQ Profile VC-2 in RTP packets and has app...
Full record

Request for Comments RFC8462 – IETF – Oct 1, 2018

Report from the IAB Workshop on Managing Radio Networks in an Encrypted World (MaRNEW)

The Internet Architecture Board (IAB) and GSM Association (GSMA) held a joint workshop on Managing Radio Networks in an Encrypted World (MaRNEW), on September 24-25, 2015. This workshop aimed to discuss solutions for bandwidth optimization on mobil...
Full record

Request for Comments RFC8471 – IETF – Oct 1, 2018

The Token Binding Protocol Version 1.0

This document specifies version 1.0 of the Token Binding protocol. The Token Binding protocol allows client/server applications to create long-lived, uniquely identifiable TLS bindings spanning multiple TLS sessions and connections. Applications ar...
Full record

Request for Comments RFC8486 – IETF – Oct 1, 2018

Ambisonics in an Ogg Opus Container

This document defines an extension to the Opus audio codec to encapsulate coded Ambisonics using the Ogg format. It also contains updates to RFC 7845 to reflect necessary changes in the description of channel mapping families.
Full record

Request for Comments RFC8496 – IETF – Oct 1, 2018

P-Charge-Info: A Private Header Field (P-Header) Extension to the Session Initiation Protocol (SIP)

This text documents the current usage of P-Charge-Info, an existing Session Initiation Protocol (SIP) private header field (P-Header) used to convey billing information about the party to be charged. This P-Header is currently used in production by...
Full record

Request for Comments RFC8441 – IETF – Sep 1, 2018

Bootstrapping WebSockets with HTTP/2

This document defines a mechanism for running the WebSocket Protocol (RFC 6455) over a single stream of an HTTP/2 connection.
Full record

Request for Comments RFC8454 – IETF – Sep 1, 2018

Information Model for Abstraction and Control of TE Networks (ACTN)

This document provides an information model for Abstraction and Control of TE Networks (ACTN).
Full record

Request for Comments RFC8464 – IETF – Sep 1, 2018

A URN Namespace for Device Identity and Mobile Equipment Identity (MEID)

This document defines a Uniform Resource Name (URN) namespace for the Third Generation Partnership Project 2 (3GPP2) and a Namespace Specific String (NSS) for the Mobile Equipment Identity (MEID). The structure of an MEID is 15 hexadecimal digits l...
Full record

Request for Comments RFC8474 – IETF – Sep 1, 2018

IMAP Extension for Object Identifiers

This document updates RFC 3501 (IMAP4rev1) with persistent identifiers on mailboxes and messages to allow clients to more efficiently reuse cached data when resources have changed location on the server.
Full record
Register to view full records and use our APIs.

Request for Comments RFC8481 – IETF – Sep 1, 2018

Clarifications to BGP Origin Validation Based on Resource Public Key Infrastructure (RPKI)

Deployment of BGP origin validation based on Resource Public Key Infrastructure (RPKI) is hampered by, among other things, vendor misimplementations in two critical areas: which routes are validated and whether policy is applied when not specified...
Full record

Request for Comments RFC8442 – IETF – Sep 1, 2018

ECDHE_PSK with AES-GCM and AES-CCM Cipher Suites for TLS 1.2 and DTLS 1.2

This document defines several new cipher suites for version 1.2 of the Transport Layer Security (TLS) protocol and version 1.2 of the Datagram Transport Layer Security (DTLS) protocol. These cipher suites are based on the Ephemeral Elliptic Curve D...
Full record

Request for Comments RFC8459 – IETF – Sep 1, 2018

Hierarchical Service Function Chaining (hSFC)

Hierarchical Service Function Chaining (hSFC) is a network architecture allowing an organization to decompose a large-scale network into multiple domains of administration. The goals of hSFC are to make a large-scale network easier to design, simp...
Full record

Request for Comments RFC8461 – IETF – Sep 1, 2018

SMTP MTA Strict Transport Security (MTA-STS)

SMTP MTA Strict Transport Security (MTA-STS) is a mechanism enabling mail service providers (SPs) to declare their ability to receive Transport Layer Security (TLS) secure SMTP connections and to specify whether sending SMTP servers should refuse t...
Full record

Request for Comments RFC8463 – IETF – Sep 1, 2018

A New Cryptographic Signature Method for DomainKeys Identified Mail (DKIM)

This document adds a new signing algorithm, Ed25519-SHA256, to "DomainKeys Identified Mail (DKIM) Signatures" (RFC 6376). DKIM verifiers are required to implement this algorithm.
Full record

Request for Comments RFC8431 – IETF – Sep 1, 2018

A YANG Data Model for the Routing Information Base (RIB)

This document defines a YANG data model for the Routing Information Base (RIB) that aligns with the Interface to the Routing System (I2RS) RIB information model.
Full record

Request for Comments RFC8470 – IETF – Sep 1, 2018

Using Early Data in HTTP

Using TLS early data creates an exposure to the possibility of a replay attack. This document defines mechanisms that allow clients to communicate with servers about HTTP requests that are sent in early data. Techniques are described that use these...
Full record

Request for Comments RFC8479 – IETF – Sep 1, 2018

Storing Validation Parameters in PKCS#8

This memo describes a method of storing parameters needed for private-key validation in the Private-Key Information Syntax Specification as defined in PKCS#8 format (RFC 5208). It is equally applicable to the alternative implementation of the Priva...
Full record

Request for Comments RFC8465 – IETF – Sep 1, 2018

Using the Mobile Equipment Identity (MEID) URN as an Instance ID

This document specifies how the Uniform Resource Name (URN) namespace reserved for the Third Generation Partnership Project 2 (3GPP2) identities and its Namespace Specific String (NSS) for the Mobile Equipment Identity (MEID) can be used as an Inst...
Full record

Request for Comments RFC8430 – IETF – Sep 1, 2018

RIB Information Model

Routing and routing functions in enterprise and carrier networks are typically performed by network devices (routers and switches) using a Routing Information Base (RIB). Protocols and configurations push data into the RIB, and the RIB manager inst...
Full record
Register to view full records and disable ads.

Request for Comments RFC8451 – IETF – Sep 1, 2018

Considerations for Selecting RTP Control Protocol (RTCP) Extended Report (XR) Metrics for the WebRTC Statistics API

This document describes monitoring features related to media streams in Web real-time communication (WebRTC). It provides a list of RTP Control Protocol (RTCP) Sender Report (SR), Receiver Report (RR), and Extended Report (XR) metrics, which may ne...
Full record

Request for Comments RFC8457 – IETF – Sep 1, 2018

IMAP "$Important" Keyword and "\Important" Special-Use Attribute

RFC 6154 created an IMAP special-use LIST extension and defined an initial set of attributes. This document defines a new attribute, "\Important", and establishes a new IANA registry for IMAP folder attributes, which include the attributes defined...
Full record

Request for Comments RFC8460 – IETF – Sep 1, 2018

SMTP TLS Reporting

A number of protocols exist for establishing encrypted channels between SMTP Mail Transfer Agents (MTAs), including STARTTLS, DNS- Based Authentication of Named Entities (DANE) TLSA, and MTA Strict Transport Security (MTA-STS). These protocols can...
Full record

Request for Comments RFC8419 – IETF – Aug 1, 2018

Use of Edwards-Curve Digital Signature Algorithm (EdDSA) Signatures in the Cryptographic Message Syntax (CMS)

This document specifies the conventions for using the Edwards-curve Digital Signature Algorithm (EdDSA) for curve25519 and curve448 in the Cryptographic Message Syntax (CMS). For each curve, EdDSA defines the PureEdDSA and HashEdDSA modes. However,...
Full record

Request for Comments RFC8424 – IETF – Aug 1, 2018

Extensions to RSVP-TE for Label Switched Path (LSP) Ingress Fast Reroute (FRR) Protection

This document describes extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for locally protecting the ingress node of a Point-to-Point (P2P) or Point-to-Multipoint (P2MP) Traffic Engineered (TE) Label Switched Path (LSP). I...
Full record

Request for Comments RFC8433 – IETF – Aug 1, 2018

A Simpler Method for Resolving Alert-Info URNs

The "alert" namespace of Uniform Resource Names (URNs) can be used in the Alert-Info header field of Session Initiation Protocol (SIP) requests and responses to inform a voice over IP (VoIP) telephone (user agent) of the characteristics of the call...
Full record

Request for Comments RFC8434 – IETF – Aug 1, 2018

Requirements for Parallel NFS (pNFS) Layout Types

This document defines the requirements that individual Parallel NFS (pNFS) layout types need to meet in order to work within the pNFS framework as defined in RFC 5661. In so doing, this document aims to clearly distinguish between requirements for...
Full record

Request for Comments RFC8435 – IETF – Aug 1, 2018

Parallel NFS (pNFS) Flexible File Layout

Parallel NFS (pNFS) allows a separation between the metadata (onto a metadata server) and data (onto a storage device) for a file. The flexible file layout type is defined in this document as an extension to pNFS that allows the use of storage devi...
Full record

Request for Comments RFC8437 – IETF – Aug 1, 2018

IMAP UNAUTHENTICATE Extension for Connection Reuse

This specification extends the Internet Message Access Protocol (IMAP) to allow an administrative client to reuse the same IMAP connection on behalf of multiple IMAP user identities.
Full record

Request for Comments RFC8440 – IETF – Aug 1, 2018

IMAP4 Extension for Returning MYRIGHTS Information in Extended LIST

This document defines an extension to the Internet Message Access Protocol (IMAP) LIST command that allows the client to request the set of rights that the logged-in user has been granted on mailboxes, along with other information typically returne...
Full record
Register to view full records and receive email notifications.

Request for Comments RFC8438 – IETF – Aug 1, 2018

IMAP Extension for STATUS=SIZE

This document adds a new capability called "STATUS=SIZE" to the Internet Message Access Protocol (IMAP). It allows retrieving the total storage size of a mailbox with a single STATUS command rather than retrieving and summing the sizes of all indiv...
Full record

Request for Comments RFC8449 – IETF – Aug 1, 2018

Record Size Limit Extension for TLS

An extension to Transport Layer Security (TLS) is defined that allows endpoints to negotiate the maximum size of protected records that each will send the other. This replaces the maximum fragment length extension defined in RFC 6066.
Full record

Request for Comments RFC8410 – IETF – Aug 1, 2018

Algorithm Identifiers for Ed25519, Ed448, X25519, and X448 for Use in the Internet X.509 Public Key Infrastructure

This document specifies algorithm identifiers and ASN.1 encoding formats for elliptic curve constructs using the curve25519 and curve448 curves. The signature algorithms covered are Ed25519 and Ed448. The key agreement algorithms covered are X25519...
Full record

Request for Comments RFC8418 – IETF – Aug 1, 2018

Use of the Elliptic Curve Diffie-Hellman Key Agreement Algorithm with X25519 and X448 in the Cryptographic Message Syntax (CMS)

This document describes the conventions for using the Elliptic Curve Diffie-Hellman (ECDH) key agreement algorithm with curve25519 and curve448 in the Cryptographic Message Syntax (CMS).
Full record

Request for Comments RFC8422 – IETF – Aug 1, 2018

Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS) Versions 1.2 and Earlier

This document describes key exchange algorithms based on Elliptic Curve Cryptography (ECC) for the Transport Layer Security (TLS) protocol. In particular, it specifies the use of Ephemeral Elliptic Curve Diffie-Hellman (ECDHE) key agreement in a TL...
Full record

Request for Comments RFC8443 – IETF – Aug 1, 2018

Personal Assertion Token (PASSporT) Extension for Resource Priority Authorization

This document extends the Personal Assertion Token (PASSporT) specification defined in RFC 8225 to allow the inclusion of cryptographically signed assertions of authorization for the values populated in the Session Initiation Protocol (SIP) 'Resour...
Full record

Request for Comments RFC8409 – IETF – Aug 1, 2018

The Entity Category Security Assertion Markup Language (SAML) Attribute Types

This document describes two SAML entity attributes: one that can be used to assign category membership semantics to an entity and another for use in claiming interoperation with or support for entities in such categories. This document is a produc...
Full record

Request for Comments RFC8416 – IETF – Aug 1, 2018

Simplified Local Internet Number Resource Management with the RPKI (SLURM)

The Resource Public Key Infrastructure (RPKI) is a global authorization infrastructure that allows the holder of Internet Number Resources (INRs) to make verifiable statements about those resources. Network operators, e.g., Internet Service Provide...
Full record

Request for Comments RFC8428 – IETF – Aug 1, 2018

Sensor Measurement Lists (SenML)

This specification defines a format for representing simple sensor measurements and device parameters in Sensor Measurement Lists (SenML). Representations are defined in JavaScript Object Notation (JSON), Concise Binary Object Representation (CBOR)...
Full record

Request for Comments RFC8436 – IETF – Aug 1, 2018

Update to IANA Registration Procedures for Pool 3 Values in the Differentiated Services Field Codepoints (DSCP) Registry

The Differentiated Services (Diffserv) architecture specifies use of the DS field in the IPv4 and IPv6 packet headers to carry one of 64 distinct differentiated services field codepoint (DSCP) values. The Internet Assigned Numbers Authority (IANA)...
Full record
Register to view full records and use our APIs.

Request for Comments RFC8411 – IETF – Aug 1, 2018

IANA Registration for the Cryptographic Algorithm Object Identifier Range

When the Curdle Security Working Group was chartered, a range of object identifiers was donated by DigiCert, Inc. for the purpose of registering the Edwards Elliptic Curve key agreement and signature algorithms. This donated set of OIDs allowed for...
Full record

Request for Comments RFC8420 – IETF – Aug 1, 2018

Using the Edwards-Curve Digital Signature Algorithm (EdDSA) in the Internet Key Exchange Protocol Version 2 (IKEv2)

This document describes the use of the Edwards-curve Digital Signature Algorithm (EdDSA) in the Internet Key Exchange Protocol Version 2 (IKEv2).
Full record

Request for Comments RFC8446 – IETF – Aug 1, 2018

The Transport Layer Security (TLS) Protocol Version 1.3

This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery. This doc...
Full record

Request for Comments RFC8447 – IETF – Aug 1, 2018

IANA Registry Updates for TLS and DTLS

This document describes a number of changes to TLS and DTLS IANA registries that range from adding notes to the registry all the way to changing the registration policy. These changes were mostly motivated by WG review of the TLS- and DTLS-related...
Full record

Request for Comments RFC8453 – IETF – Aug 1, 2018

Framework for Abstraction and Control of TE Networks (ACTN)

Traffic Engineered (TE) networks have a variety of mechanisms to facilitate the separation of the data plane and control plane. They also have a range of management and provisioning protocols to configure and activate network resources. These mecha...
Full record

Request for Comments RFC8371 – IETF – Jul 1, 2018

Mobile Node Identifier Types for MIPv6

This document defines additional identifier type numbers for use with the mobile node identifier option for Mobile IPv6 (MIPv6) as defined by RFC 4283.
Full record

Request for Comments RFC8390 – IETF – Jul 1, 2018

RSVP-TE Path Diversity Using Exclude Route

RSVP-TE provides support for the communication of exclusion information during Label Switched Path (LSP) setup. A typical LSP diversity use case is for protection, where two LSPs should follow different paths through the network in order to avoid s...
Full record

Request for Comments RFC8396 – IETF – Jul 1, 2018

Managing, Ordering, Distributing, Exposing, and Registering Telephone Numbers (MODERN): Problem Statement, Use Cases, and Framework

The functions of the Public Switched Telephone Network (PSTN) are rapidly migrating to the Internet. This is generating new requirements for many traditional elements of the PSTN, including Telephone Numbers (TNs). TNs no longer serve simply as tel...
Full record

Request for Comments RFC8402 – IETF – Jul 1, 2018

Segment Routing Architecture

Segment Routing (SR) leverages the source routing paradigm. A node steers a packet through an ordered list of instructions, called "segments". A segment can represent any instruction, topological or service based. A segment can have a semantic loca...
Full record