RFC 3924 Cisco Architecture for Lawful Intercept in IP Networks

rfc-editor@rfc-editor.org Mon, 01 November 2004 18:15 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13453; Mon, 1 Nov 2004 13:15:52 -0500 (EST)
Received: from megatron.ietf.org ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COgxc-00071J-AP; Mon, 01 Nov 2004 13:31:21 -0500
Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COg6V-0001oG-Vu; Mon, 01 Nov 2004 12:36:28 -0500
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COfre-0008DR-01 for ietf-announce@megatron.ietf.org; Mon, 01 Nov 2004 12:21:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05711 for <ietf-announce@ietf.org>; Mon, 1 Nov 2004 12:21:04 -0500 (EST)
Received: from boreas.isi.edu ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COg6a-0004oO-HS for ietf-announce@ietf.org; Mon, 01 Nov 2004 12:36:32 -0500
Received: from ISI.EDU (adma.isi.edu []) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id iA1HIii15277; Mon, 1 Nov 2004 09:18:44 -0800 (PST)
Message-Id: <200411011718.iA1HIii15277@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 01 Nov 2004 09:18:44 -0800
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Cc: rfc-editor@rfc-editor.org
Subject: RFC 3924 Cisco Architecture for Lawful Intercept in IP Networks
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813

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

        RFC 3924

        Title:      Cisco Architecture for Lawful Intercept in IP
        Author(s):  F. Baker, B. Foster, C. Sharp
        Status:     Informational
        Date:       October 2004
        Mailbox:    fred@cisco.com, bfoster@cisco.com,
        Pages:      18
        Characters: 40826
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-baker-slem-architecture-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3924.txt

For the purposes of this document, lawful intercept is the lawfully
authorized interception and monitoring of communications.  Service
providers are being asked to meet legal and regulatory requirements
for the interception of voice as well as data communications in IP
networks in a variety of countries worldwide.  Although requirements
vary from country to country, some requirements remain common even
though details such as delivery formats may differ.  This document
describes Cisco's Architecture for supporting lawful intercept in IP
networks.  It provides a general solution that has a minimum set of
common interfaces.  This document does not attempt to address any of
the specific legal requirements or obligations that may exist in a
particular country.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
IETF-Announce mailing list