[kitten] RFC 6680 on Generic Security Service Application Programming Interface (GSS-API) Naming Extensions

rfc-editor@rfc-editor.org Thu, 30 August 2012 00:53 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A3FD21F8498; Wed, 29 Aug 2012 17:53:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.995
X-Spam-Level:
X-Spam-Status: No, score=-101.995 tagged_above=-999 required=5 tests=[AWL=0.005, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3cCVh58yV-68; Wed, 29 Aug 2012 17:53:12 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 0238821F8495; Wed, 29 Aug 2012 17:53:12 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5F8BCB1E002; Wed, 29 Aug 2012 17:50:51 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120830005051.5F8BCB1E002@rfc-editor.org>
Date: Wed, 29 Aug 2012 17:50:51 -0700
Cc: kitten@ietf.org, rfc-editor@rfc-editor.org
Subject: [kitten] RFC 6680 on Generic Security Service Application Programming Interface (GSS-API) Naming Extensions
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/kitten>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Aug 2012 00:53:12 -0000

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

        
        RFC 6680

        Title:      Generic Security Service Application Programming 
                    Interface (GSS-API) Naming Extensions 
        Author:     N. Williams, L. Johansson,
                    S. Hartman, S. Josefsson
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2012
        Mailbox:    nico@cryptonector.com, 
                    leifj@sunet.se, 
                    hartmans-ietf@mit.edu,
                    simon@josefsson.org
        Pages:      18
        Characters: 37063
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-kitten-gssapi-naming-exts-15.txt

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

The Generic Security Service Application Programming Interface (GSS-API)
provides a simple naming architecture that supports name-based
authorization.  This document introduces new APIs that extend the
GSS-API naming model to support name attribute transfer between
GSS-API peers.

This document is a product of the Common Authentication Technology Next Generation Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  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