RFC 3726 on Requirements for Signaling Protocols

rfc-editor@rfc-editor.org Sun, 18 April 2004 02:31 UTC

Message-Id: <200404170007.i3H07fN15099@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3726 on Requirements for Signaling Protocols
Cc: rfc-editor@rfc-editor.org, nsis@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 16 Apr 2004 17:07:41 -0700
Sender: ietf-announce-admin@ietf.org
Errors-To: ietf-announce-admin@ietf.org
Precedence: bulk

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


        RFC 3726

        Title:      Requirements for Signaling Protocols
        Author(s):  M. Brunner, Ed.
        Status:     Informational
        Date:       April 2004
        Mailbox:    brunner@netlab.nec.de
        Pages:      42
        Characters: 98020
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-nsis-req-09.txt

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


This document defines requirements for signaling across different
network environments, such as across administrative and/or technology
domains.  Signaling is mainly considered for Quality of Service (Qos)
such as the Resource Reservation Protocol (RSVP).  However, in recent
years, several other applications of signaling have been defined.  For
example, signaling for label distribution in Multiprotocol Label
Switching (MPLS) or signaling to middleboxes.  To achieve wide
applicability of the requirements, the starting point is a diverse set
of scenarios/use cases concerning various types of networks and
application interactions.  This document presents the assumptions
before listing the requirements.  The requirements are grouped
according to areas such as architecture and design goals, signaling
flows, layering, performance, flexibility, security, and mobility.

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.echo 
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/rfc3726.txt"><ftp://ftp.isi.edu/in-notes/rfc3726.txt>

RFC 3726 on Requirements for Signaling Protocols rfc-editor