CARVIEW |
Select Language
HTTP/2 302
date: Wed, 16 Jul 2025 07:15:47 GMT
content-type: text/html; charset=utf-8
location: https://www.rfc-editor.org/info/bcp188
content-security-policy: default-src 'self' 'unsafe-inline' data: https://datatracker.ietf.org/ https://www.ietf.org/ https://ietf.org/ https://analytics.ietf.org https://static.ietf.org; frame-ancestors 'self' ietf.org *.ietf.org meetecho.com *.meetecho.com
cross-origin-opener-policy: unsafe-none
referrer-policy: strict-origin-when-cross-origin
strict-transport-security: max-age=3600; includeSubDomains
vary: Cookie, Accept-Encoding
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
cf-cache-status: EXPIRED
expires: Wed, 16 Jul 2025 11:15:47 GMT
cache-control: public, max-age=14400
server: cloudflare
cf-ray: 95ffb5ddfb7ac197-BLR
alt-svc: h3=":443"; ma=86400
HTTP/2 200
date: Wed, 16 Jul 2025 07:15:49 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 95ffb5e0e8823c3c-BOM
alt-svc: h3=":443"; ma=86400
Information on BCP 188 » RFC Editor
Search RFCs
- File formats:
- Status:
- BEST CURRENT PRACTICE
- Authors:
- S. Farrell
H. Tschofenig - Stream:
- IETF
- Source:
- NON WORKING GROUP
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC
Abstract
Pervasive monitoring is a technical attack that should be mitigated in the design of IETF protocols, where possible.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us