d by a fiber cut) is reverted upon repair without further
optimization. However, this form of TE relies... ng the traffic
information for analysis and further action.
Traffic trunk: An aggregation of tra... nted technologies such as
MPLS, routing can be further controlled by the manipulation of
relevant TE ... computed offline to allow rapid reactions without further
computation or may be derived online depending
e
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available... et" to refer to a value that is used to derive
further secret values and "key" to refer to a value that ... ch secret. From the epoch secret, members derive further shared
secrets for message encryption, group m... h
generation 0
* AR2 for derivation of further message decryption keys and nonces
* HR0 for
e
Internet Engineering Steering Group (IESG). Further information on
BCPs is available in Section 2 ... or
CFM OpCodes and one for CFM TLV Types. For further information, see
[RFC7319]. The IANA "Connect... for these code points. This
document does not further discuss these blocks of code points.
2. Etherne... ss space into four quadrants as
follows and further described below:
+=======+=======
e
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available... each inter-AS TE link.
In GMPLS networks, further information may also be required to select
the... as are other local properties
of the TE link. Further, where BGP is used to exchange IP routing
info... te ASBR is likely to be
available.
We note further that it is possible, and may be operationally
e
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available... o PCEs, enabling computation of TE LSPs. PCEP is further
extended to support GMPLS-controlled networks ... d GMPLS networks, as illustrated in [RFC8051].
Further discussion of the concept of a stateful PCE can b... ct
type, containing the LABEL-REQUEST TLV. Further note that:
* As per [RFC8779], for statel
e
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available... zero-length Application Identifier Bit Mask is
further discussed in Section 12.2.
9. Local Interface I... and processed on receipt for these applications. Further
discussion of the associated issues can be fou... LV or sub-TLV SHOULD be counted and/or logged for further
analysis. Logging of malformed TLVs and sub-T
erated sensibly.)
This specification does not further address the authentication issues
associated w... e
Internet Engineering Steering Group (IESG). Further information on
BCPs is available in Section 2 ... tating attacks (please
| see [RFC9415] for further details).
Section 3 provides an overview of c... ntifiers. Please see
| [Shostack2014] for further guidance on threat modeling.
Protocol specifi
3)
0414 File Transfer Protocol (FTP) status and further comments. A.K.
Bhushan. December 1972. (Form... (Status: UNKNOWN) (DOI: 10.17487/RFC0609)
0610 Further datalanguage design concepts. R. Winter, J. Hill,... SED STANDARD) (DOI:
10.17487/RFC6918)
6919 Further Key Words for Use in RFCs to Indicate Requirement
han, A., "File Transfer Protocol (FTP) status and further comments", RFC 414, DOI 10.17487/RFC0414, Decembe... | Winter, R., Hill, J., and W. Greiff, "Further datalanguage design concepts", RFC 610, DOI 10.17... | Barnes, R., Kent, S., and E. Rescorla, "Further Key Words for Use in RFCs to Indicate Requirement
e
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available... ation of "CounterSignature0" may be supported for further
compatibility.
1.1. Requirements Terminology... in Section 4.2 of
[RFC8949]. These rules are further narrowed in Section 9 of
[RFC9052]. The narro
knowledgment losses. All these
operations are further detailed in Section 4.
With Tetrys, a coded p... ment (if appropriate). See Section 6.1
for further details.
Several building blocks provide the ... a FEC mechanism within the transport layer is
further discussed in Section 4 of [RFC9265], where consid
examples describing
these common behaviors for further reference.
4.2.1. HTTP Request Header Identific... rmance of HTTPS traffic, a protocol that prevents further
analysis, to encourage users to switch to HTTP... f residual censorship is to provide users
with further discouragement from trying to access forbidden co
e
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available... s bits/
flags as specified in [RFC5340] and further extended by [RFC8362]
and Section 6 of this... ted and/or
logged in a rate-limited manner for further analysis.
This document describes the OSPFv3
e
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available... record is available to provide a TTL. [RFC2308] further
specified optional negative caching for two DN... e port
number and ID field. This situation is further exacerbated in the
case of timeout-based resol
e
Internet Engineering Steering Group (IESG). Further information on
BCPs is available in Section 2 ... d
quite differently by different DNS experts. Further, some terms that
are defined in early DNS RFCs... authoritative nameserver chain". [RFC2308] further says "The
forwarder typically either has be