RFC 8953: Coordinating Attack Response at Internet Scale 2 (CARIS2) Workshop Report
In plain English — editorial summary, not part of the RFC
The Coordinating Attack Response at Internet Scale (CARIS) 2 workshop, sponsored by the Internet Society, took place on 28 February and 1 March 2019 in Cambridge, Massachusetts, USA. Participants spanned regional, national, international, and enterprise Computer Security Incident Response Teams (CSIRTs), operators, service providers, network and security operators, transport operators and researchers, incident response researchers, vendors, and participants from standards communities. This workshop continued the work started at the first CARIS workshop, with a focus on scaling incident prevention and detection as the Internet industry moves to a stronger and a more ubiquitous deployment of session encryption.
Document record
- Document ID
- RFC8953
- Published
- December 2020
- Authors
- K. Moriarty
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9128YANG Data Model for Protocol Independent Multicast (PIM)Current
October 2022
- RFC 9166A YANG Data Model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) SnoopingCurrent
February 2022
- RFC 8695A YANG Data Model for the Routing Information Protocol (RIP)Current
February 2020
- RFC 8652A YANG Data Model for the Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD)Current
November 2019
- RFC 9312Manageability of the QUIC Transport ProtocolCurrent
September 2022
- RFC 9315Intent-Based Networking - Concepts and DefinitionsCurrent
October 2022
- RFC 9316Intent ClassificationCurrent
October 2022
- RFC 9490Report from the IAB Workshop on Management Techniques in Encrypted Networks (M-TEN)Current
January 2024
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?