f Internet Traffic Engineering
Abstract
This document describes the principles of traffic engineering (TE) in
the Internet. The document is intended to promote better
understanding of... as first published as RFC 3272 in May 2002. This document
obsoletes RFC 3272 by making a complete update... t work in the IETF.
Status of This Memo
This document is not an Internet Standards Track specification;
decades since the DNS was first defined. This document gives current
definitions for many of the terms used in the DNS in a single
document.
This document updates RFC 2308 by clarifying the definitions of
"forwarder" and "QNAME". It obsole... ments an Internet Best Current Practice.
This document is a product of the Internet Engineering Task For
t frame formats and IEEE 802
parameters. This document discusses several aspects of such
parameters a... es some values
for use in documentation. This document obsoletes RFC 7042.
Status of This Memo
This... ments an Internet Best Current Practice.
This document is a product of the Internet Engineering Task For...
Information about the current status of this document, any errata,
and how to provide feedback on it
g the advertised value for a given
link. This document introduces link attribute advertisements in
OS... that address both of these shortcomings.
This document obsoletes RFC 8920.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consen
cols such as BGP, IS-
IS, and OSPFv3.
This document defines extensions to BGP - Link State (BGP-LS) t... ess-family solution for SRv6
described in this document is similar to BGP-LS for SR for the MPLS
data ... This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consen
rity Considerations
Status of this Memo
This document specifies an Internet Best Current Practices for ... y, such sections have been relatively weak. This document
provides guidelines to RFC authors on how to w... ion. The purpose of this is both to encourage
document authors to consider security in their designs and... to RFC authors in service of both ends.
This document is structured in three parts. The first is a
t may not be online at the same
time. In this document, we specify a key establishment protocol that
... This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consen...
Information about the current status of this document, any errata,
and how to provide feedback on it
Transient Numeric Identifiers
Abstract
This document analyzes the timeline of the specification and
... e that advice in this area is warranted. This
document is a product of the Privacy Enhancements and Asse... PEARG) in the IRTF.
Status of This Memo
This document is not an Internet Standards Track specification;... published for informational purposes.
This document is a product of the Internet Research Task Force
re listed: text (TXT), PostScript (PS), Portable Document Format
(PDF), HTML, XML.
Obsoletes xxxx refers ... I, STD, or BCP number if the RFC is also in those
document sub-series. The Status field gives the document's
current status (see RFC 2026). The (DOI ddd) field give... 87/RFC0064)
0065 Comments on Host/Host Protocol document #1. D.C. Walden. August
1970. (Format: TXT,
orldwide Censorship Techniques
Abstract
This document describes technical mechanisms employed in networ... ensoring end-user access to information. This
document makes no suggestions on individual protocol consi... ely informational, intended as a reference. This document
is a product of the Privacy Enhancement and As... PEARG) in the IRTF.
Status of This Memo
This document is not an Internet Standards Track specification;
| Walden, D., "Comments on Host/Host Protocol document #1", RFC 65, DOI 10.17487/RFC0065, August 1970, <... | O'Sullivan, T., "Telnet Protocol - a proposed document", RFC 137, DOI 10.17487/RFC0137, April 1971, <htt... 95 | O'Sullivan, T., "Telnet Protocol: A Proposed Document", RFC 158, DOI 10.17487/RFC0158, May 1971, <https... rotocol - meeting announcement and a new proposed document", RFC 454, DOI 10.17487/RFC0454, February 1973, <
constrained Nodes (6lo)
Abstract
This document describes the applicability of IPv6 over constrai... FC), and Power Line Communication (PLC). This
document targets an audience who would like to understand ... ernet connectivity.
Status of This Memo
This document is not an Internet Standards Track specification;... published for informational purposes.
This document is a product of the Internet Engineering Task For
information regarding the data's existence. This document concerns
itself only with the third type.
... caching of TYPE 3
responses is optional. This document updates RFC 2308 to require
negative caching f... 5 allows DNSSEC validation failure caching. This document
updates RFC 4035 to require caching for DNSSEC... records at a failed
zone's parent zone. This document updates RFC 4697 to expand this
requirement to
t interface (FCI) as defined in RFC 8008.
This document defines two new footprint types. The first footp... This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consen...
Information about the current status of this document, any errata,
and how to provide feedback on it
(ACME) Authority Token
Abstract
This document defines a profile of the Automated Certificate
... This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consen...
Information about the current status of this document, any errata,
and how to provide feedback on it