ogy
Abstract
The Domain Name System (DNS) is defined in literally dozens of
different RFCs. The te... changed in the
decades since the DNS was first defined. This document gives current
definitions for ... y This Document
Appendix B. Definitions First Defined in This Document
Acknowledgements
Index
... he DNS".) The protocol and message format are
defined in [RFC1034] and [RFC1035]. These RFCs defined s
elated link attribute advertisements
have been defined and are used in RSVP-TE deployments. Since the
original RSVP-TE use case was defined, additional applications such
as Segment Routi... se of the link attribute advertisements have been defined.
In cases where multiple applications wish to ... d
among these use cases is SR Policy, which is defined in [RFC9256].
If both RSVP-TE and SR Policy ar
ptographic state with other clients. A client is defined by
the cryptographic keys it holds.
Gro... The PublicMessage and PrivateMessage formats are defined in
Section 6. Security notions such as forward secrecy and post-
compromise security are defined in Section 16.
As detailed in Section 13.5, M... h the CipherSuite type. The cipher
suites are defined in Section 17.1.
5.1.1. Public Keys
HPKE pu
computation. GMPLS-specific objects and TLVs are defined in
[RFC8779], which this document builds on... rthermore, the LSP Initiation function of PCEP is defined in
[RFC8281] to allow the PCE to initiate LSP ... e both data flow and technology specific
be defined. These traffic parameters are also known as "Tra... xt information for the LSP specified by GMPLS, as defined in
[RFC4872] and [RFC4873].
5. Overview o
GP-LS for SR for the MPLS
data plane, which is defined in RFC 9085.
Status of This Memo
This is an ... are advertised using the BGP-LS
Attribute TLVs defined in this section and associated with the BGP-LS
... Vs. However, no such
extensions are currently defined. Moreover, the SRv6 Capabilities
TLV defined below is not extensible. As a result, it is expected
ystems
4.3.2. Considerations for Software-Defined Networking
4.4. Local versus Global
4.... e
network.
Internet traffic engineering is defined as that aspect of Internet
network engineering... hanisms must be sufficiently
specific and well-defined to address known requirements but
simultaneous... or from another network.
Metric: A parameter defined in terms of standard units of
measurement.
Telephone Identity (STI) using
the TNAuthList defined by STI certificates.
Status of This Memo
Thi... e document using the Authority Token
mechanism defined in [RFC9447]. It is a profile that specifically
... ls such as SIP [RFC8224]. Currently, the only
defined credentials for this purpose are the certificates... of CA types of certificates for delegation, as
defined in [RFC9060].
2. Requirements Language
The
endix). In order to facilitate deployment, it is defined in
such a way that the resulting (unblinded) s... y pk by invoking
the RSASSA-PSS-VERIFY routine defined in Section 8.1.2 of [RFC8017].
The Finalize fu... an integer. RSAVP1 and EMSA-PSS-ENCODE are as defined in
Sections 5.2.2 and 9.1.1 of [RFC8017], resp... Note that this function invokes RSAVP1, which is defined to throw an
optional error for invalid inputs.
& Capabilities Advertisement interface (FCI) as defined in RFC 8008.
This document defines two new footprint types. The first footprint
type defined is an ISO 3166-2 country subdivision code. Defin... red to the ISO 3166-1 country code footprint type defined in RFC
8006. The ISO 3166-2 country subdivisi... n type in the "ALTO Entity Domain Types" registry defined
in Section 7.4 of RFC 9241. The second footpr
ded packets are built
on-the-fly by using a predefined method to choose the coefficients.
The redunda... ypes of
packets: the PKT_TYPE_SOURCE (0b00) defined in Section 5.2, the
PKT_TYPE_CODED (0b01) defined in Section 5.3 and the
PKT_TYPE_WND_UPT (0b11) for window update packets defined in
Section 5.4.
Congestion Control Info
twork-designated Resolvers (DNR).
The options defined in this document can be deployed in a variety of
... wn here.
This document makes use of the terms defined in [RFC8499]. The
following additional terms ...
Encrypted DNS options: Refers to the options defined in Sections 4,
5, and 6.
DHCP: Refers ... addresses. To
avoid such probing, the options defined in Sections 4, 5, and 6
associate an encrypted
SED STANDARD) (DOI: 10.17487/RFC5283)
5284 User-Defined Errors for RSVP. G. Swallow, A. Farrel. August 20... 10.17487/RFC6063)
6064 SDP and RTSP Extensions Defined for 3GPP Packet-Switched Streaming
Service a... Format Extensions: Representing vCard Extensions Defined by
the Open Mobile Alliance (OMA) Converged ... ARD) (DOI:
10.17487/RFC7148)
7149 Software-Defined Networking: A Perspective from within a Service
84 | | Swallow, G. and A. Farrel, "User-Defined Errors for RSVP", RFC 5284, DOI 10.17487/RFC5284,... rlund, M. and P. Frojdh, "SDP and RTSP Extensions Defined for 3GPP Packet-Switched Streaming Service and Mu... Format Extensions: Representing vCard Extensions Defined by the Open Mobile Alliance (OMA) Converged Addre... | Boucadair, M. and C. Jacquenet, "Software-Defined Networking: A Perspective from within a Service P
oT) services become more popular, the IETF
has defined adaptation layer functionality to support IPv6 ov... rs).
In its generic network topology, DECT is defined as a cellular
network technology. However, th... ld also
support the registration extensions defined in [RFC8505] and use
the mechanism as the d... RSs).
Host-to-Router Interface:
6lo has defined registration extensions for 6LoWPAN Neighbor
ss fields in the PIM Register-Stop
message are defined in Section 4.9.4 of [RFC7761]. The common header
is defined in [RFC9436].
Packing Capability bit (P-bit; ... s in the PIM Packed Null-
Register message are defined in Section 4.9.4 of [RFC7761]. The
common header is defined in [RFC9436].
Type, Subtype: PIM Packed Null