Núcleo de Informação e Coordenação do Ponto BR

Portal de Boas Práticas para a Internet no Brasil

Navegação global

Conteúdo

8137: IEEE 802.15.4 Information Element for the IETF

(13KB) IEEE Std 802.15.4 defines Information Elements (IEs) that can be used to extend 802.15.4 in an interoperable manner. The IEEE 802.15 Assigned Numbers Authority (ANA) manages the registry of the Information Elements. This document formulates a request for ANA to allocate a number from that registry for the IETF and describes how the IE is formatted to provide subtypes.

8151: Use Cases for Data Center Network Virtualization Overlay Networks

(34KB) This document describes Network Virtualization over Layer 3 (NVO3) use cases that can be deployed in various data centers and serve different data-center applications.

8116: Security Threats to the Optimized Link State Routing Protocol Version 2 (OLSRv2)

(58KB) This document analyzes common security threats to the Optimized Link State Routing Protocol version 2 (OLSRv2) and describes their potential impacts on Mobile Ad Hoc Network (MANET) operations. It also analyzes which of these security vulnerabilities can be mitigated when using the mandatory-to-implement security mechanisms for OLSRv2 and how the vulnerabilities are mitigated.

8112: Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT) Referral Internet Groper (RIG)

(23KB) A simple tool called the Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT) Referral Internet Groper (RIG), also referred to in this document as \"rig\", can be used to query the LISP- DDT hierarchy. This document describes how the \"rig\" tool works.

8111: Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT)

(96KB) This document describes the Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT), a hierarchical distributed database that embodies the delegation of authority to provide mappings from LISP Endpoint Identifiers (EIDs) to Routing Locators (RLOCs). It is a statically defined distribution of the EID namespace among a set of LISP-speaking servers called \"DDT nodes\". Each DDT node is configured as \"authoritative\" for one or more EID-prefixes, along with the set of RLOCs for Map-Servers or \"child\" DDT nodes to which more-specific EID-prefixes are delegated.

8050: Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format with BGP Additional Path Extensions

(11KB) This document extends the Multi-threaded Routing Toolkit (MRT) export format for Border Gateway Protocol (BGP) routing information by supporting the advertisement of multiple paths in BGP extensions.

8174: RFC 2119 Key Words: Clarifying the Use of Capitalization

(6KB) RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.

8170: Planning for Protocol Adoption and Subsequent Transitions

(54KB) Over the many years since the introduction of the Internet Protocol, we have seen a number of transitions throughout the protocol stack, such as deploying a new protocol, or updating or replacing an existing protocol. Many protocols and technologies were not designed to enable smooth transition to alternatives or to easily deploy extensions; thus, some transitions, such as the introduction of IPv6, have been difficult. This document attempts to summarize some basic principles to enable future transitions, and it also summarizes what makes for a good transition plan.

8134: Management Incident Lightweight Exchange (MILE) Implementation Report

(35KB) This document is a collection of implementation reports from vendors, consortiums, and researchers who have implemented one or more of the standards published from the IETF INCident Handling (INCH) and Management Incident Lightweight Exchange (MILE) working groups.

8148: Next-Generation Vehicle-Initiated Emergency Calls

(93KB) This document describes how to use IP-based emergency services mechanisms to support the next generation of emergency calls placed by vehicles (automatically in the event of a crash or serious incident, or manually invoked by a vehicle occupant) and conveying vehicle, sensor, and location data related to the crash or incident. Such calls are often referred to as \"Automatic Crash Notification\" (ACN), or \"Advanced Automatic Crash Notification\" (AACN), even in the case of manual trigger. The \"Advanced\" qualifier refers to the ability to carry a richer set of data.

8147: Next-Generation Pan-European eCall

(91KB) This document describes how to use IP-based emergency services mechanisms to support the next generation of the Pan-European in-vehicle emergency call service defined under the eSafety initiative of the European Commission (generally referred to as \"eCall\"). eCall is a standardized and mandated system for a special form of emergency calls placed by vehicles, providing real-time communications and an integrated set of related data.

8161: Benchmarking the Neighbor Discovery Protocol

(32KB) This document provides benchmarking procedures for the Neighbor Discovery Protocol (NDP). It also proposes metrics by which an NDP implementation\'s scaling capabilities can be measured.

8165: Design Considerations for Metadata Insertion

(16KB) The IAB published RFC 7624 in response to several revelations of pervasive attacks on Internet communications. This document considers the implications of protocol designs that associate metadata with encrypted flows. In particular, it asserts that designs that share metadata only by explicit actions at the host are preferable to designs in which middleboxes insert metadata.

8164: Opportunistic Security for HTTP/2

(19KB) This document describes how \"http\" URIs can be accessed using Transport Layer Security (TLS) and HTTP/2 to mitigate pervasive monitoring attacks. This mechanism not a replacement for \"https\" URIs; it is vulnerable to active attacks.

8163: Transmission of IPv6 over Master-Slave/Token-Passing (MS/TP) Networks

(55KB) Master-Slave/Token-Passing (MS/TP) is a medium access control method for the RS-485 physical layer and is used primarily in building automation networks. This specification defines the frame format for transmission of IPv6 packets and the method of forming link-local and statelessly autoconfigured IPv6 addresses on MS/TP networks.

8159: Keyed IPv6 Tunnel

(27KB) This document describes a tunnel encapsulation for Ethernet over IPv6 with a mandatory 64-bit cookie for connecting Layer 2 (L2) Ethernet attachment circuits identified by IPv6 addresses. The encapsulation is based on the Layer 2 Tunneling Protocol Version 3 (L2TPv3) over IP and does not use the L2TPv3 control plane.

8157: Huawei's GRE Tunnel Bonding Protocol

(88KB) There is an emerging demand for solutions that provide redundancy and load-sharing across wired and cellular links from a single Service Provider, so that a single subscriber is provided with bonded access to heterogeneous connections at the same time.

8154: Parallel NFS (pNFS) Small Computer System Interface (SCSI) Layout

(70KB) The Parallel Network File System (pNFS) allows a separation between the metadata (onto a metadata server) and data (onto a storage device) for a file. The Small Computer System Interface (SCSI) layout type is defined in this document as an extension to pNFS to allow the use of SCSI-based block storage devices.

8105: Transmission of IPv6 Packets over Digital Enhanced Cordless Telecommunications (DECT) Ultra Low Energy (ULE)

(48KB) Digital Enhanced Cordless Telecommunications (DECT) Ultra Low Energy (ULE) is a low-power air interface technology that is proposed by the DECT Forum and is defined and specified by ETSI.

8088: How to Write an RTP Payload Format

(161KB) This document contains information on how best to write an RTP payload format specification. It provides reading tips, design practices, and practical tips on how to produce an RTP payload format specification quickly and with good results. A template is also included with instructions.