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
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... object classes allowed for search. Through
a further step of generalization, the meaning of reverse se... s to
a dedicated backend server and leveraging further security services
offered by other protocol la
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
nnectivity and
Data Center Interconnect
Further analysis of the needs of IETF Network Slice Servi... ustomer requests. These would
be specified in further documents.
If the IETF Network Slice Service ... as a
quantifiable metric.
Please see further discussion on security in Section 10.
Geograp... composition: An IETF Network Slice
can be further sliced into other network slices. Recursive
e
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available... of the JSON value the query is
applied to. No further errors relating to the well-formedness and
the... | | | further |
| | | ... (see Section 2.4) and the ability to register
further functions provided by the "Function Extensions" s
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
fies the agency within that
top-level domain. Further optional subdomains can follow. The top-
leve... possible
solutions can be found in [RFC3833]. Further information on security
considerations regardi
chine-learning analysis. [WU] also
recommends further research investment in Artificial Intelligence
... ncrypted traffic, as well as the opportunities to further enhance
user privacy.
2.1.3. Users and Priva
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