1-100 of about 284 matches for site:datatracker.ietf.org site:datatracker.ietf.org explicit
https://datatracker.ietf.org/group/enamews/about/
IAB Workshop on Explicit Internet Naming Systems (enamews) Skip to main content Datatracker Groups By area/parent Apps
https://datatracker.ietf.org/wg/bier/about/
Bit Indexed Explicit Replication (bier) Skip to main content Datatracker Groups By area/parent Apps & Realtime
https://datatracker.ietf.org/group/enamews/materials/
IAB Workshop on Explicit Internet Naming Systems (enamews) Skip to main content Datatracker Groups By area/parent Apps
https://datatracker.ietf.org/group/enamews/photos/
IAB Workshop on Explicit Internet Naming Systems (enamews) photos Skip to main content Datatracker Groups By area/parent
https://datatracker.ietf.org/group/enamews/history/
IAB Workshop on Explicit Internet Naming Systems (enamews) Skip to main content Datatracker Groups By area/parent Apps
https://datatracker.ietf.org/group/enamews/email/
IAB Workshop on Explicit Internet Naming Systems (enamews) Skip to main content Datatracker Groups By area/parent Apps
RFC 7560 - Problem Statement and Requirements for Increased Accuracy in Explicit Congestion Notifica
https://datatracker.ietf.org/doc/html/rfc7560
RFC 7560 - Problem Statement and Requirements for Increased Accuracy in Explicit Congestion Notification (ECN) Feedback
https://datatracker.ietf.org/person/Sally%20Floyd
Initial Window 13 RFCs RFC 2481 Jan 1999 A Proposal to add Explicit Congestion Notification (ECN) to
https://datatracker.ietf.org/wg/tsvwg/about/
ports, maximum transmission unit discovery, reordering, congestion control, loss detection and recovery, queue management, explicit congestion notification, multihoming, stream
https://datatracker.ietf.org/doc/html/rfc7234#section-4.2.3
not store a response that has neither a cache validator nor an explicit expiration time, as such
https://datatracker.ietf.org/doc/html/rfc7234#section-3.2
not store a response that has neither a cache validator nor an explicit expiration time, as such
https://datatracker.ietf.org/doc/html/rfc7234#section-3.3
not store a response that has neither a cache validator nor an explicit expiration time, as such
https://datatracker.ietf.org/doc/html/rfc7234#section-1.2.1
not store a response that has neither a cache validator nor an explicit expiration time, as such
https://datatracker.ietf.org/doc/html/rfc7234#section-2
not store a response that has neither a cache validator nor an explicit expiration time, as such
https://datatracker.ietf.org/doc/html/rfc7234#page-19
not store a response that has neither a cache validator nor an explicit expiration time, as such
https://datatracker.ietf.org/doc/draft-ietf-bier-evpn/writeup/
Proposed Standard This document is the product of the Bit Indexed Explicit Replication Working Group. The
https://datatracker.ietf.org/doc/rfc9111/
not store a response that has neither a cache validator nor an explicit expiration time, as such
https://datatracker.ietf.org/doc/html/rfc7234#page-13
not store a response that has neither a cache validator nor an explicit expiration time, as such
https://datatracker.ietf.org/doc/html/rfc7234#page-21
not store a response that has neither a cache validator nor an explicit expiration time, as such
https://datatracker.ietf.org/doc/html/rfc7234#section-4
not store a response that has neither a cache validator nor an explicit expiration time, as such
https://datatracker.ietf.org/doc/html/rfc8725
Use and Validate Audience ¶ 3.10 . Do Not Trust Received Claims ¶ 3.11 . Use Explicit Typing ¶ 3.12 . Use
https://datatracker.ietf.org/wg/ohai/about/
defined. Broad applicability is limited by multiple factors, including the need for explicit server support of
https://datatracker.ietf.org/person/Mirja%20Kuehlewind
Aug 2015 Problem Statement and Requirements for Increased Accuracy in Explicit Congestion Notification (ECN) Feedback
https://datatracker.ietf.org/doc/rfc7234/
not store a response that has neither a cache validator nor an explicit expiration time, as such
draft-ietf-tsvwg-ecn-encap-guidelines-22 - Guidelines for Adding Congestion Notification to Protocol
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-ecn-encap-guidelines...
lower layer or tunnelling protocol that encapsulates IP. The aim is for explicit congestion signals to
https://datatracker.ietf.org/doc/html/rfc7234#page-5
not store a response that has neither a cache validator nor an explicit expiration time, as such
https://datatracker.ietf.org/doc/html/rfc7234#section-4.2.1
not store a response that has neither a cache validator nor an explicit expiration time, as such
https://datatracker.ietf.org/wg/avt/charter/
in these tasks must not be accepted by the working group without an explicit re-chartering. In
Appeal - Appeal re Protocol Action: 'URI Design and Ownership' to Best Current Practice (draft-notti
https://datatracker.ietf.org/group/iesg/appeals/artifact/48
updates or changes the technical content or applicability of another be very explicit about what is being
https://datatracker.ietf.org/doc/html/draft-ietf-oauth-jwt-bcp
and Validate Audience . . . . . . . . . . . . . . . . 9 3.10 . Do Not Trust Received Claims . . . . . . . . . . . . . . 10 3.11 . Use Explicit Typing . . . . . . . . . . . . . . . . . . . 10 3.12
https://datatracker.ietf.org/doc/html/rfc7234#page-15
not store a response that has neither a cache validator nor an explicit expiration time, as such
https://datatracker.ietf.org/doc/html/rfc7234#section-3.1
not store a response that has neither a cache validator nor an explicit expiration time, as such
https://datatracker.ietf.org/doc/html/rfc7234#section-5.2
not store a response that has neither a cache validator nor an explicit expiration time, as such
https://datatracker.ietf.org/doc/draft-ietf-bier-evpn/14/
unicast, and multicast (BUM) traffic of Ethernet VPNs (EVPN) using Bit Index Explicit Replication (BIER). Requirements Language
https://datatracker.ietf.org/doc/html/rfc2854
DOCTYPE declaration "<!DOCTYPE html". 6 . Charset default rules The use of an explicit charset parameter is strongly
https://datatracker.ietf.org/team/
Internet Applications and Systems Jari Arkko , Lars Eggert , Colin Perkins enamews IAB Workshop on Explicit Internet Naming Systems smartobjectsws
draft-ietf-lamps-cms-kemri-08 - Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptograp
https://datatracker.ietf.org/doc/draft-ietf-lamps-cms-kemri/08/
0 rid RecipientIdentifier, kem KEMAlgorithmIdentifier, kemct OCTET STRING, kdf KeyDerivationAlgorithmIdentifier, kekLength INTEGER (1..65535), ukm [0] EXPLICIT UserKeyingMaterial OPTIONAL, wrap KeyEncryptionAlgorithmIdentifier
https://datatracker.ietf.org/person/Matthew%20Bocci
Point-to-Multipoint Pseudowires over MPLS Packet Switched Networks 3 RFCs RFC 7392 Dec 2014 Explicit Path Routing for
https://datatracker.ietf.org/wg/tcpm/about/
a Proposed Standard RFC draft-ietf-tcpm-tcp-edo Jan 2023 Submit document on adding Explicit Congestion Notification (ECN) to
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-ecn-encap-guidelines...
lower layer or tunnelling protocol that encapsulates IP. The aim is for explicit congestion signals to
https://datatracker.ietf.org/group/enamews/meetings/
IETF Datatracker relies on Javascript. Please enable Javascript for full functionality. IAB Workshop on Explicit Internet Naming Systems (enamews
draft-briscoe-tsvwg-ecn-encap-guidelines-04 - Guidelines for Adding Congestion Notification to Proto
https://datatracker.ietf.org/doc/draft-briscoe-tsvwg-ecn-encap-guideli...
lower layer or tunnelling protocol that encapsulates IP. The aim is for explicit congestion signals to
https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-ecn-encap-guide...
lower layer or tunnelling protocol that encapsulates IP. The aim is for explicit congestion signals to
draft-ietf-tsvwg-ecn-encap-guidelines-00 - Guidelines for Adding Congestion Notification to Protocol
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-ecn-encap-guidelines...
lower layer or tunnelling protocol that encapsulates IP. The aim is for explicit congestion signals to
https://datatracker.ietf.org/group/iab/about/
Workshop: Design Expectations vs Deployment Reality in Protocol Development Team enamews IAB Workshop on Explicit Internet Naming Systems Team
https://datatracker.ietf.org/doc/draft-ietf-bier-evpn/00/
unicast and multicast (BUM) traffic of Ethernet VPNs (EVPN) using Bit Index Explicit Replication (BIER). Authors Zhaohui
https://datatracker.ietf.org/list/nonwg
such as QUIC over satellite. event-streaming Event-streaming evolving-documents Evolving Documents (nee Living Documents) explicit-meas This mailing list
draft-ietf-lamps-cms-kemri-00 - Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptograp
https://datatracker.ietf.org/doc/draft-ietf-lamps-cms-kemri/00/
0 rid RecipientIdentifier, kem KEMAlgorithmIdentifier, kemct OCTET STRING, kdf KeyDerivationAlgorithmIdentifier, kekLength INTEGER (1..MAX), ukm [0] EXPLICIT UserKeyingMaterial OPTIONAL, wrap KeyEncryptionAlgorithmIdentifier
https://datatracker.ietf.org/doc/draft-ietf-bier-evpn/
unicast, and multicast (BUM) traffic of Ethernet VPNs (EVPN) using Bit Index Explicit Replication (BIER). Requirements Language
https://datatracker.ietf.org/doc/draft-ietf-httpbis-p6-cache/26/
not store a response that has neither a cache validator nor an explicit expiration time, as such
https://datatracker.ietf.org/doc/rfc9217/
Transport Layer Security (TLS) [RFC8446], can authenticate the remote endpoint. However, little, if any, explicit information about the
https://datatracker.ietf.org/doc/html/rfc2145
HTTP/1.1 specification [2]: It is, and has always been, the explicit intent of the
https://datatracker.ietf.org/doc/draft-ietf-detnet-yang/20/
functions in the DetNet service layer, so there is no need for explicit indication). The corresponding
Response - Appeal re Protocol Action: 'URI Design and Ownership' to Best Current Practice (draft-not
https://datatracker.ietf.org/group/iesg/appeals/artifact/49
updates or changes the technical content or applicability of another be very explicit about what is being
https://datatracker.ietf.org/doc/draft-ietf-bier-evpn/ballot/
SMET routes are not used to reduce the burden of explicit tracking", what you mean
https://datatracker.ietf.org/person/Colin%20Perkins
Use of Variable Bit Rate Audio with Secure RTP 13 RFCs RFC 6679 Aug 2012 Explicit Congestion Notification (ECN) for
draft-ietf-tsvwg-ecn-encap-guidelines-22 - Guidelines for Adding Congestion Notification to Protocol
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-ecn-encap-guidelines...
lower layer or tunnelling protocol that encapsulates IP. The aim is for explicit congestion signals to
https://datatracker.ietf.org/doc/review-ietf-dtn-dtnma-08-tsvart-lc-to...
presented. Sec 1.2 - The definition of Reference Model might be more explicit that it does not
https://datatracker.ietf.org/doc/html/rfc2195
MD5 ] for precomputation of intermediate results make it possible to avoid explicit cleartext storage of
https://datatracker.ietf.org/doc/statement-iab-statement-on-the-risks-...
authentication. In contrast, attestation of client software and hardware places explicit restrictions on the
https://datatracker.ietf.org/doc/draft-carpenter-rswg-format-details/
RFCs, and overall management of the RFC Series." This definition is not explicit about the level
https://datatracker.ietf.org/doc/charter-irtf-ufmrg/
conferences and workshops (e.g., Security Standardization Research (SSR), Computer-Aided Verification (CAV), etc.). An explicit non-goal is to
https://datatracker.ietf.org/wg/clue/about/
part of the receiver telling the sender what it wants dynamically, explicit receiver notification to
https://datatracker.ietf.org/doc/draft-ietf-websec-origin/ballot/
probability of collision and it'd be better to be explicit about that so that
https://datatracker.ietf.org/rg/ufmrg/about/
conferences and workshops (e.g., Security Standardization Research (SSR), Computer-Aided Verification (CAV), etc.). An explicit non-goal is to
https://datatracker.ietf.org/doc/rfc8789/
for publishing some documents that the community cannot agree on. However, we have an explicit path for such
https://datatracker.ietf.org/doc/rfc3849/
environment causes address and routing conflicts with existing services. In making an explicit allocation of a
https://datatracker.ietf.org/group/spring/about/
need for per-path state information to be held at transit nodes. Full explicit control (through loose or
https://datatracker.ietf.org/doc/rfc7030/
POP Information ......................22 3.6. Server Authorization ......................................23 3.6.1. Client Use of Explicit TA Database .................24 3
RFC 7295 - Report from the IAB/IRTF Workshop on Congestion Control for Interactive Real-Time Communi
https://datatracker.ietf.org/doc/rfc7295/
of a software download happening in another application into account. 8. There are explicit congestion signals (such as
https://datatracker.ietf.org/doc/rfc9490/
Many existing network management techniques are passive in nature: they don't rely on explicit signals from end hosts
RFC 7295 - Report from the IAB/IRTF Workshop on Congestion Control for Interactive Real-Time Communi
https://datatracker.ietf.org/doc/html/rfc7295
of a software download happening in another application into account. 8. There are explicit congestion signals (such as
https://datatracker.ietf.org/doc/html/rfc1874
the recipient's SGML system. Those entities may contain and such systems may permit explicit system level commands to
https://datatracker.ietf.org/doc/draft-ietf-httpbis-http2-encryption/1...
identifier that uses TLS, such as "h2" [RFC7540]. Such a protocol MUST include an explicit indication of the
https://datatracker.ietf.org/doc/html/rfc8164
identifier that uses TLS, such as "h2" [ RFC7540 ]. Such a protocol MUST include an explicit indication of the
https://datatracker.ietf.org/doc/html/rfc1122
guidance for an implementor. For each protocol, this document also contains an explicit set of requirements
draft-ietf-lamps-cms-kemri-08 - Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptograp
https://datatracker.ietf.org/doc/draft-ietf-lamps-cms-kemri/
0 rid RecipientIdentifier, kem KEMAlgorithmIdentifier, kemct OCTET STRING, kdf KeyDerivationAlgorithmIdentifier, kekLength INTEGER (1..65535), ukm [0] EXPLICIT UserKeyingMaterial OPTIONAL, wrap KeyEncryptionAlgorithmIdentifier
https://datatracker.ietf.org/doc/html/rfc7538
response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls (see [RFC7234
https://datatracker.ietf.org/doc/review-bichot-msync-08-artart-early-a...
encoded in Network Byte Order (also called big-endian), some readers might appreciate this being explicit. * 3.2 "object CRC
https://datatracker.ietf.org/doc/minutes-118-rswg-202311091045/
If we are allowing RPC to use discretion we need to be explicit about that in
https://datatracker.ietf.org/doc/draft-ietf-detnet-yang/ballot/
DetNet Forwarding Sub-layer YANG Attributes * Since this model programs the data plane existing explicit route mechanisms can be
https://datatracker.ietf.org/doc/html/rfc1779
case, the types for attributes in the RDN must be explicit. The name
https://datatracker.ietf.org/doc/rfc2914/
of communications between the end nodes and routers about congestion information (e.g., Explicit Congestion Notification [RFC2481]) or
https://datatracker.ietf.org/doc/rfc1126/
limited in the extent of their effect. Routing firewalls may be explicit, or may be inherent
https://datatracker.ietf.org/meeting/119/materials/minutes-119-icnrg-2...
attach" a local namespace to a more global namespace via an explicit graft operation. The
https://datatracker.ietf.org/doc/html/rfc3377
of RFCs comprising LDAPv3, and formally address the IESG Note through explicit inclusion of RFC
https://datatracker.ietf.org/doc/rfc2310/
in the history buffer. If the POST request is unsafe, HTTP requires explicit user confirmation is before
http://datatracker.ietf.org/list/wg/
Floor Control Protocol Bis bfd Bidirectional Forwarding Detection bgmp Border Gateway Multicast Protocol bier Bit Indexed Explicit Replication bliss Basic Level
https://datatracker.ietf.org/doc/rfc9298/
connection containing a UDP Proxying request stream disables congestion control, it MUST NOT signal Explicit Congestion Notification (ECN) [ECN
https://datatracker.ietf.org/doc/draft-ietf-detnet-yang/
functions in the DetNet service layer, so there is no need for explicit indication). The corresponding
draft-iab-marnew-report-02 - Report from the IAB Workshop on Managing Radio Networks in an Encrypted
https://datatracker.ietf.org/doc/draft-iab-marnew-report/02/
opt-out. Some users will always automatically click through consent requests, so any model relying on explicit consent is flawed for
https://datatracker.ietf.org/doc/draft-ietf-quic-multipath/
abort the handshake with a TRANSPORT_PARAMETER error. 4. Path Identifier The explicit Path Identifier is an
https://datatracker.ietf.org/doc/rfc2616/
75 13.1.2 Warnings .................................................76 13.1.3 Cache-control Mechanisms .................................77 13.1.4 Explicit User Agent Warnings .............................78
https://datatracker.ietf.org/doc/html/draft-ietf-oauth-jwt-introspecti...
way to establish the legal basis for releasing PII is by explicit user consent gathered from
https://datatracker.ietf.org/doc/draft-ietf-pkix-est/09/
PoP information . . . . . . . . . . 20 3.6. Server Authorization . . . . . . . . . . . . . . . . . . 21 3.6.1. Client use of Explicit TA Database . . . . . . . . . 22 3
https://datatracker.ietf.org/doc/draft-ietf-http-v11-spec-rev/06/
69 13.1.2 Warnings ..................................................70 13.1.3 Cache-control Mechanisms ..................................71 13.1.4 Explicit User Agent Warnings ..............................72
https://datatracker.ietf.org/doc/rfc8085/
other topics, including message sizes, reliability, checksums, middlebox traversal, the use of Explicit Congestion Notification (ECN), Differentiated
https://datatracker.ietf.org/doc/html/rfc2068
72 13.1.2 Warnings ........................................ 73 13.1.3 Cache-control Mechanisms ........................ 74 13.1.4 Explicit User Agent Warnings .................... 74
https://datatracker.ietf.org/doc/html/draft-kuehlewind-masque-quic-sub...
proxy and explicitly coordinate with it. This allows client hosts to make explicit decisions about the
https://datatracker.ietf.org/doc/html/draft-kuehlewind-spud-use-cases
SPUD) draft-kuehlewind-spud-use-cases-01 Abstract This document identifies use cases for explicit cooperation between endpoints and