[NSIS] RFC 5974 on NSIS Signaling Layer Protocol (NSLP) for Quality-of-Service Signaling

rfc-editor@rfc-editor.org Wed, 06 October 2010 19:15 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B39663A71AA; Wed, 6 Oct 2010 12:15:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7NwFA0t1oSF9; Wed, 6 Oct 2010 12:15:26 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 2C7383A71D0; Wed, 6 Oct 2010 12:15:14 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1F604E06FE; Wed, 6 Oct 2010 12:16:15 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20101006191615.1F604E06FE@rfc-editor.org>
Date: Wed, 06 Oct 2010 12:16:15 -0700
Cc: nsis@ietf.org, rfc-editor@rfc-editor.org
Subject: [NSIS] RFC 5974 on NSIS Signaling Layer Protocol (NSLP) for Quality-of-Service Signaling
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nsis>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 19:15:29 -0000

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

        
        RFC 5974

        Title:      NSIS Signaling Layer Protocol (NSLP) 
                    for Quality-of-Service Signaling 
        Author:     J. Manner, G. Karagiannis,
                    A. McDonald
        Status:     Experimental
        Stream:     IETF
        Date:       October 2010
        Mailbox:    jukka.manner@tkk.fi, 
                    karagian@cs.utwente.nl, 
                    andrew.mcdonald@roke.co.uk
        Pages:      102
        Characters: 233309
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nsis-qos-nslp-18.txt

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

This specification describes the NSIS Signaling Layer Protocol (NSLP)
for signaling Quality of Service (QoS) reservations in the Internet.
It is in accordance with the framework and requirements developed in
NSIS.  Together with General Internet Signaling Transport (GIST), it
provides functionality similar to RSVP and extends it.  The QoS NSLP
is independent of the underlying QoS specification or architecture
and provides support for different reservation models.  It is
simplified by the elimination of support for multicast flows.  This
specification explains the overall protocol approach, describes the
design decisions made, and provides examples.  It specifies object,
message formats, and processing rules.  This document defines an 
Experimental Protocol for the Internet community.

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


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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