RFC 5981 on Authorization for NSIS Signaling Layer Protocols

rfc-editor@rfc-editor.org Sat, 12 February 2011 00:03 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 878AA3A6A04; Fri, 11 Feb 2011 16:03:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.22
X-Spam-Status: No, score=-102.22 tagged_above=-999 required=5 tests=[AWL=0.380, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id TMkCfw6RUjav; Fri, 11 Feb 2011 16:03:28 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id B92DF3A69FB; Fri, 11 Feb 2011 16:03:28 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 1EDCFE071F; Fri, 11 Feb 2011 16:03:45 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5981 on Authorization for NSIS Signaling Layer Protocols
From: rfc-editor@rfc-editor.org
Message-Id: <20110212000345.1EDCFE071F@rfc-editor.org>
Date: Fri, 11 Feb 2011 16:03:45 -0800 (PST)
Cc: nsis@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 12 Feb 2011 00:03:31 -0000

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

        RFC 5981

        Title:      Authorization for NSIS Signaling Layer 
        Author:     J. Manner, M. Stiemerling,
                    H. Tschofenig, R. Bless, Ed.
        Status:     Experimental
        Stream:     IETF
        Date:       February 2011
        Mailbox:    jukka.manner@tkk.fi, 
                    Hannes.Tschofenig@gmx.net,  roland.bless@kit.edu
        Pages:      37
        Characters: 82427
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nsis-nslp-auth-07.txt

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

Signaling layer protocols specified within the Next Steps in
Signaling (NSIS) framework may rely on the General Internet Signaling
Transport (GIST) protocol to handle authorization.  Still, the
signaling layer protocol above GIST itself may require separate
authorization to be performed when a node receives a request for a
certain kind of service or resources.  This document presents a
generic model and object formats for session authorization within the
NSIS signaling layer protocols.  The goal of session authorization is
to allow the exchange of information between network elements in
order to authorize the use of resources for a service and to
coordinate actions between the signaling and transport planes.
This document defines an Experimental Protocol for the Internet

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

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