1-40 of about 40 matches for site:datatracker.ietf.org reliable entry
https://datatracker.ietf.org/ipr/6290/
Patent Holder/Applicant ("Patent Holder") Previous ( #5725 ) This (#6290) Reliable Energy Analytics, LLC Holder legal name Reliable Energy Analytics, LLC II
https://datatracker.ietf.org/ipr/5725/
Disclosure ID #6290, " Reliable Energy Analytics, LLC's General License Statement " Updates IPR Disclosure ID #5683, " Reliable Energy Analytics, LLC's
https://datatracker.ietf.org/doc/html/rfc7232
of expiration times. Thus, a cache might attempt to validate an entry using a validator
draft-ietf-avtcore-rtp-scip-09 - RTP Payload Format for the Secure Communication Interoperability Pr
https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-scip/09/
Needed IANA action state RFC-Ed-Ack RFC Editor RFC Editor state EDIT Details Publication queue entry Email authors Email WG
https://datatracker.ietf.org/doc/html/draft-trammell-post-sockets
to the strong sequential dependence on a stream, streams must always be reliable and ordered
https://datatracker.ietf.org/doc/draft-mcnally-envelope/
goals in mind: to be _Structure-Ready_, allowing for the reliable and interoperable
draft-ietf-avtcore-rtp-scip-09 - RTP Payload Format for the Secure Communication Interoperability Pr
https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-scip/
Needed IANA action state RFC-Ed-Ack RFC Editor RFC Editor state EDIT Details Publication queue entry Email authors Email WG
RFC 6125 - Representation and Verification of Domain-Based Application Service Identity within Inter
https://datatracker.ietf.org/doc/rfc6125/
referred to as the "most significant" entry, and the entry farthest from the
https://datatracker.ietf.org/doc/rfc1094/
status" is NFS_OK, then it is followed by a variable number of "entry"s. Each "entry" contains
RFC 8793 - Information-Centric Networking (ICN): Content-Centric Networking (CCNx) and Named Data Ne
https://datatracker.ietf.org/doc/rfc8793/
it checks its CS and PIT to find a matching entry; if no match is
https://datatracker.ietf.org/doc/draft-mcnally-envelope/
goals in mind: to be _Structure-Ready_, allowing for the reliable and interoperable
https://datatracker.ietf.org/doc/html/rfc1700
2 [ BWB6 ] 25 LEAF-1 Leaf-1 [ BWB6 ] 26 LEAF-2 Leaf-2 [ BWB6 ] 27 RDP Reliable Data Protocol [ RFC908 , RH6
https://datatracker.ietf.org/doc/rfc1977/
the reserved code 256. Because data that would expend is sent without compression, there is no reliable way for the
https://datatracker.ietf.org/doc/html/draft-mcnally-envelope-07
goals in mind: to be Structure-Ready , allowing for the reliable and interoperable
https://datatracker.ietf.org/doc/html/rfc5626
registrar challenges this registration to authenticate Bob. When the registrar adds an entry for this
https://datatracker.ietf.org/doc/rfc5667/
elements via the XDR position value encoded in the Read chunk entry. RPC RDMA Read chunks
https://datatracker.ietf.org/doc/rfc6241/
All <name> Elements within the <users> Subtree . . . . . . . . . . . . . . . . . . . . . . . 29 6.4.5. One Specific <user> Entry . . . . . . . . . . . . . . 30 6.4.6
draft-ietf-rats-tpm-based-network-device-attest-14 - TPM-based Network Device Remote Integrity Verif
https://datatracker.ietf.org/doc/draft-ietf-rats-tpm-based-network-dev...
Needed IANA action state No IANA Actions RFC Editor RFC Editor state EDIT Details Publication queue entry Email authors Email WG
https://datatracker.ietf.org/doc/html/draft-ietf-quic-applicability
Streams 4.1 . Stream versus Flow Multiplexing 4.2 . Prioritization 4.3 . Ordered and Reliable Delivery 4.4 . Flow
draft-saintandre-tls-server-id-check-14 - Representation and Verification of Domain-Based Applicatio
https://datatracker.ietf.org/doc/draft-saintandre-tls-server-id-check/...
small percentage (less than 1%) of issued certificates. Furthermore, IP addresses are not necessarily reliable identifiers for application
RFC 6125 - Representation and Verification of Domain-Based Application Service Identity within Inter
https://datatracker.ietf.org/doc/html/rfc6125#section-6.2.1
small percentage (less than 1%) of issued certificates. Furthermore, IP addresses are not necessarily reliable identifiers for application
https://datatracker.ietf.org/doc/rfc8040/
feature is identified by an IANA-registered NETCONF Capability URI and advertised with an entry in the
https://datatracker.ietf.org/doc/rfc7322/
before the last item of a series, e.g., "TCP service is reliable, ordered, and full
https://datatracker.ietf.org/doc/rfc2616/
includes more stringent requirements than HTTP/1.0 in order to ensure reliable implementation of its
https://datatracker.ietf.org/doc/rfc1123/
21 3.3.1 Telnet End-of-Line Convention ..................... 21 3.3.2 Data Entry Terminals .............................. 23 3.3
https://datatracker.ietf.org/doc/draft-mcnally-envelope/07/
goals in mind: to be _Structure-Ready_, allowing for the reliable and interoperable
https://datatracker.ietf.org/doc/rfc7322/
before the last item of a series, e.g., "TCP service is reliable, ordered, and full
draft-ietf-rats-tpm-based-network-device-attest-14 - TPM-based Network Device Remote Integrity Verif
https://datatracker.ietf.org/doc/draft-ietf-rats-tpm-based-network-dev...
Needed IANA action state No IANA Actions RFC Editor RFC Editor state EDIT Details Publication queue entry Email authors Email WG
https://datatracker.ietf.org/doc/rfc1917/
of addresses together into blocks which can be advertised as a single routing entry. The practical
https://datatracker.ietf.org/doc/rfc6241/
All <name> Elements within the <users> Subtree . . . . . . . . . . . . . . . . . . . . . . . 29 6.4.5. One Specific <user> Entry . . . . . . . . . . . . . . 30 6.4.6
https://datatracker.ietf.org/doc/rfc1813/
Server Procedures . . . . . . . . . . . . . . . . . . . 107 5.2.0 NULL: Do nothing . . . . . . . . . . . . . . . . . . . 108 5.2.1 MNT: Add mount entry . . . . . . . . . . . . . . . . . 109 5.2.2
https://datatracker.ietf.org/doc/draft-tenoever-tao-retirement/04/
Needed IANA action state No IANA Actions RFC Editor RFC Editor state EDIT Details Publication queue entry Email authors IPR References
https://datatracker.ietf.org/doc/html/rfc2068
includes more stringent requirements than HTTP/1.0 in order to ensure reliable implementation of its
https://datatracker.ietf.org/doc/html/rfc1436
and software follow a client-server model. This protocol assumes a reliable data stream; TCP is
https://datatracker.ietf.org/doc/rfc8040/
feature is identified by an IANA-registered NETCONF Capability URI and advertised with an entry in the
https://datatracker.ietf.org/doc/rfc1036/
of the originating system. However, it is also permissible to include an extra entry on the right
https://datatracker.ietf.org/doc/rfc8974/
by the fact that both CoAP over UDP [RFC7252] and CoAP over reliable transports [RFC8323] restrict the
https://datatracker.ietf.org/doc/draft-tenoever-tao-retirement/
Needed IANA action state No IANA Actions RFC Editor RFC Editor state EDIT Details Publication queue entry Email authors IPR References
https://datatracker.ietf.org/doc/html/rfc850
of the originating system. However, it is also permissible to include an extra entry on the right
https://datatracker.ietf.org/doc/html/rfc1036
of the originating system. However, it is also permissible to include an extra entry on the right