RFC 4081 on Security Threats for Next Steps in Signaling (NSIS)

rfc-editor@rfc-editor.org Fri, 10 June 2005 17:04 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dgmw9-00039t-Az; Fri, 10 Jun 2005 13:04:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dgmw7-00038k-8M; Fri, 10 Jun 2005 13:04:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08826; Fri, 10 Jun 2005 13:04:47 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DgnHp-0007es-0w; Fri, 10 Jun 2005 13:27:17 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j5AH37L19226; Fri, 10 Jun 2005 10:03:07 -0700 (PDT)
Message-Id: <200506101703.j5AH37L19226@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: Fri, 10 Jun 2005 10:03:07 -0700
X-ISI-4-39-6-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: nsis@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4081 on Security Threats for Next Steps in Signaling (NSIS)
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

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


        RFC 4081

        Title:      Security Threats for Next Steps in Signaling
                    (NSIS)
        Author(s):  H. Tschofenig, D. Kroeselberg
        Status:     Informational
        Date:       June 2005
        Mailbox:    Hannes.Tschofenig@siemens.com,
                    Dirk.Kroeselberg@siemens.com
        Pages:      28
        Characters: 67786
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-nsis-threats-06.txt

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


This threats document provides a detailed analysis of the security
threats relevant to the Next Steps in Signaling (NSIS) protocol suite.
It calls attention to, and helps with the understanding of, various
security considerations in the NSIS Requirements, Framework, and
Protocol proposals.  This document does not describe vulnerabilities
of specific parts of the NSIS protocol suite.

This document is a product of the Next Steps in Signaling Working
Group of the IETF.

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
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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.
ftp://ftp.isi.edu/in-notes/rfc4081.txt"><ftp://ftp.isi.edu/in-notes/rfc4081.txt>
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce