RFC 6545 on Real-time Inter-network Defense (RID)

rfc-editor@rfc-editor.org Fri, 20 April 2012 23:19 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id ADB4F21E8086; Fri, 20 Apr 2012 16:19:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.197
X-Spam-Status: No, score=-104.197 tagged_above=-999 required=5 tests=[AWL=0.880, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id aTlyzDFJJ7wi; Fri, 20 Apr 2012 16:19:10 -0700 (PDT)
Received: from rfc-editor.org (rfcpa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 1B93221E8049; Fri, 20 Apr 2012 16:19:10 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 810C6B1E003; Fri, 20 Apr 2012 16:18:00 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6545 on Real-time Inter-network Defense (RID)
From: rfc-editor@rfc-editor.org
Message-Id: <20120420231800.810C6B1E003@rfc-editor.org>
Date: Fri, 20 Apr 2012 16:18:00 -0700
Cc: mile@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2012 23:19:10 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 6545

        Title:      Real-time Inter-network Defense (RID) 
        Author:     K. Moriarty
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2012
        Mailbox:    Kathleen.Moriarty@emc.com
        Pages:      84
        Characters: 203100
        Obsoletes:  RFC6045

        I-D Tag:    draft-ietf-mile-rfc6045-bis-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6545.txt

Security incidents, such as system compromises, worms, viruses,
phishing incidents, and denial of service, typically result in the
loss of service, data, and resources both human and system.  Service
providers and Computer Security Incident Response Teams need to be
equipped and ready to assist in communicating and tracing security
incidents with tools and procedures in place before the occurrence of
an attack.  Real-time Inter-network Defense (RID) outlines a
proactive inter-network communication method to facilitate sharing
incident-handling data while integrating existing detection, tracing,
source identification, and mitigation mechanisms for a complete
incident-handling solution.  Combining these capabilities in a
communication system provides a way to achieve higher security levels
on networks.  Policy guidelines for handling incidents are
recommended and can be agreed upon by a consortium using the security
recommendations and considerations.  This document obsoletes RFC

This document is a product of the Managed Incident Lightweight Exchange Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC