Transport of Real-time Inter-network Defense (RID) Messages over HTTP/TLS
RFC 6546

Document Type RFC - Proposed Standard (April 2012; Errata)
Obsoletes RFC 6046
Last updated 2015-10-14
Replaces draft-trammell-mile-rfc6046-bis
Stream IETF
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Kathleen Moriarty
IESG IESG state RFC 6546 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Sean Turner
IESG note Kathleen Moriarty ( is the document shepherd.
Send notices to (None)
Internet Engineering Task Force (IETF)                       B. Trammell
Request for Comments: 6546                                    ETH Zurich
Obsoletes: 6046                                               April 2012
Category: Standards Track
ISSN: 2070-1721

      Transport of Real-time Inter-network Defense (RID) Messages
                             over HTTP/TLS


   The Incident Object Description Exchange Format (IODEF) defines a
   common XML format for document exchange, and Real-time Inter-network
   Defense (RID) defines extensions to IODEF intended for the
   cooperative handling of security incidents within consortia of
   network operators and enterprises.  This document specifies an
   application-layer protocol for RID based upon the passing of RID
   messages over HTTP/TLS.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   ( in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Trammell                     Standards Track                    [Page 1]
RFC 6546                      RID Transport                   April 2012

1.  Introduction

   The Incident Object Description Exchange Format (IODEF) [RFC5070]
   describes an XML document format for the purpose of exchanging data
   between Computer Security Incident Response Teams (CSIRTs) or those
   responsible for security incident handling for service providers
   (SPs).  The defined document format provides a simple way for CSIRTs
   to exchange data in a way which can be easily parsed.

   IODEF defines a message format, not a protocol, as the sharing of
   messages is assumed to be out of scope in order to allow CSIRTs to
   exchange and store messages in a way most suited to their established
   incident-handling processes.  However, Real-time Inter-network
   Defense (RID) [RFC6545] does require a specification of a protocol to
   ensure interoperability among members in a RID consortium.  This
   document specifies the transport of RID messages within HTTP
   [RFC2616] Request and Response messages over TLS [RFC5246] (herein,
   HTTP/TLS).  Note that any IODEF message may also be transported using
   this mechanism, by sending it as a RID Report message.

1.1.  Changes from RFC 6046

   This document contains the following changes with respect to its
   predecessor [RFC6046]:

   o  The status of the document is Standards Track.

   o  The document is updated to refer to the updated RID specification,
      [RFC6545], where appropriate.

   o  Language regarding the use of HTTP/1.1 and TCP ports for RID
      transport is clarified.

   o  The RID-Callback-Token entity header field is added to allow
      matching of RID replies during callback, independent of the
      content of the underlying RID message.

   o  The minimum required version of TLS is upgraded to 1.1, and the
      minimum recommended version to 1.2.

   o  Language regarding PKI for RID over HTTPS is clarified, and
      updated to refer to [RFC6125].

   This document obsoletes [RFC6046] and moves it to Historic status.

Trammell                     Standards Track                    [Page 2]
RFC 6546                      RID Transport                   April 2012

2.  Terminology and Normative Sections

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   document are to be interpreted as described in [RFC2119].

   RID systems participating in a consortium are required to fully
Show full document text