loading
NSF INSTALLATION MANUAL - Installation Manual for Food Service Equipment
July 1, 1968 - NSF
A description is not available for this item.
IETF RFC 8476 - Signaling Maximum SID Depth (MSD) Using OSPF
December 1, 2018 - IETF
A description is not available for this item.
IETF RFC 8503 - BGP/MPLS Layer 3 VPN Multicast Management Information Base
December 1, 2018 - IETF
A description is not available for this item.
IETF RFC 8389 - Definitions of Managed Objects for Mapping of Address and Port with Encapsulation (MAP-E)
December 1, 2018 - IETF
A description is not available for this item.
IETF RFC 8502 - L2L3 VPN Multicast MIB
December 1, 2018 - IETF
A description is not available for this item.
IETF RFC 8509 - A Root Key Trust Anchor Sentinel for DNSSEC
December 1, 2018 - IETF
A description is not available for this item.
IETF RFC 8505 - Registration Extensions for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Neighbor Discovery
November 1, 2018 - IETF

This specification updates RFC 6775 - the Low-Power Wireless Personal Area Network (6LoWPAN) Neighbor Discovery specification - to clarify the role of the protocol as a registration technique and simplify the registration operation in 6LoWPAN routers, as well as to provide enhancements to the...

IETF RFC 8497 - Marking SIP Messages to Be Logged
November 1, 2018 - IETF

SIP networks use signaling monitoring tools to diagnose user-reported problems and to perform regression testing if network or user agent (UA) software is upgraded. As networks grow and become interconnected, including connection via transit networks, it becomes impractical to predict the path that...

IETF RFC 8495 - Allocation Token Extension for the Extensible Provisioning Protocol (EPP)
November 1, 2018 - IETF

This document describes an Extensible Provisioning Protocol (EPP) extension for including an Allocation Token in "query" and "transform" commands. The Allocation Token is used as a credential that authorizes a client to request the allocation of a specific object from the server using one of the...

IETF RFC 8469 - Recommendation to Use the Ethernet Control Word
November 1, 2018 - IETF

The pseudowire (PW) encapsulation of Ethernet, as defined in RFC 4448, specifies that the use of the control word (CW) is optional. In the absence of the CW, an Ethernet PW packet can be misidentified as an IP packet by a label switching router (LSR). This may lead to the selection of the wrong...

IETF RFC 8415 - Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
November 1, 2018 - IETF

This document describes the Dynamic Host Configuration Protocol for IPv6 (DHCPv6): an extensible mechanism for configuring nodes with network configuration parameters, IP addresses, and prefixes. Parameters can be provided statelessly, or in combination with stateful assignment of one or more IPv6...

IETF RFC 8480 - 6TiSCH Operation Sublayer (6top) Protocol (6P)
November 1, 2018 - IETF

This document defines the "IPv6 over the TSCH mode of IEEE 802.15.4e" (6TiSCH) Operation Sublayer (6top) Protocol (6P), which enables distributed scheduling in 6TiSCH networks. 6P allows neighbor nodes to add/delete Time-Slotted Channel Hopping (TSCH) cells to/on one another. 6P is part of the...

IETF RFC 8491 - Signaling Maximum SID Depth (MSD) Using IS-IS
November 1, 2018 - IETF

This document defines a way for an Intermediate System to Intermediate System (IS-IS) router to advertise multiple types of supported Maximum SID Depths (MSDs) at node and/or link granularity. Such advertisements allow entities (e.g., centralized controllers) to determine whether a particular...

IETF RFC 8444 - OSPFv2 Extensions for Bit Index Explicit Replication (BIER)
November 1, 2018 - IETF

Bit Index Explicit Replication (BIER) is an architecture that provides optimal multicast forwarding through a "BIER domain" without requiring intermediate routers to maintain multicast-related, per- flow state. BIER also does not require an explicit tree-building protocol for its operation. A...

IETF RFC 8466 - A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery
October 1, 2018 - IETF

This document defines a YANG data model that can be used to configure a Layer 2 provider-provisioned VPN service. It is up to a management system to take this as an input and generate specific configuration models to configure the different network elements to deliver the service. How this...

IETF RFC 8473 - Token Binding over HTTP
October 1, 2018 - IETF

This document describes a collection of mechanisms that allow HTTP servers to cryptographically bind security tokens (such as cookies and OAuth tokens) to TLS connections. We describe both first-party and federated scenarios. In a firstparty scenario, an HTTP server is able to cryptographically...

IETF RFC 8471 - The Token Binding Protocol Version 1.0
October 1, 2018 - IETF

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 are then enabled to cryptographically bind security...

IETF RFC 8487 - Mtrace Version 2: Traceroute Facility for IP Multicast
October 1, 2018 - IETF

This document describes the IP multicast traceroute facility, named Mtrace version 2 (Mtrace2). Unlike unicast traceroute, Mtrace2 requires special implementations on the part of routers. This specification describes the required functionality in multicast routers, as well as how an Mtrace2 client...

IETF RFC 8450 - RTP Payload Format for VC-2 High Quality (HQ) Profile
October 1, 2018 - IETF

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 applications for low-complexity, high-bandwidth...

IETF RFC 8484 - DNS Queries over HTTPS (DoH)
October 1, 2018 - IETF

This document defines a protocol for sending DNS queries and getting DNS responses over HTTPS. Each DNS query-response pair is mapped into an HTTP exchange.

Advertisement