
From nobody Mon May 21 16:44:49 2018
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 3324C12DA00; Mon, 21 May 2018 16:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s-x14lmqK7BD; Mon, 21 May 2018 16:44:45 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41ABC12D94B; Mon, 21 May 2018 16:44:45 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 38C78B8283F; Mon, 21 May 2018 16:44:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, kitten@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20180521234435.38C78B8283F@rfc-editor.org>
Date: Mon, 21 May 2018 16:44:35 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/vaj-3ZkEATth0UemHYW7TzCHYCs>
Subject: [kitten] =?utf-8?q?RFC_8353_on_Generic_Security_Service_API_Versi?= =?utf-8?q?on_2=3A_Java_Bindings_Update?=
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 21 May 2018 23:44:47 -0000

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

        
        RFC 8353

        Title:      Generic Security Service API Version 2: 
                    Java Bindings Update 
        Author:     M. Upadhyay,
                    S. Malkani,
                    W. Wang
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2018
        Mailbox:    m.d.upadhyay+ietf@gmail.com, 
                    seema.malkani@gmail.com, 
                    weijun.wang@oracle.com
        Pages:      96
        Characters: 204802
        Obsoletes:  RFC 5653

        I-D Tag:    draft-ietf-kitten-rfc5653bis-07.txt

        URL:        https://www.rfc-editor.org/info/rfc8353

        DOI:        10.17487/RFC8353

The Generic Security Services Application Programming Interface
(GSS-API) offers application programmers uniform access to security
services atop a variety of underlying cryptographic mechanisms.  This
document updates the Java bindings for the GSS-API that are specified
in "Generic Security Service API Version 2: Java Bindings Update"
(RFC 5653).  This document obsoletes RFC 5653 by adding a new output
token field to the GSSException class so that when the initSecContext
or acceptSecContext methods of the GSSContext class fail, it has a
chance to emit an error token that can be sent to the peer for
debugging or informational purpose.  The stream-based GSSContext
methods are also removed in this version.

The GSS-API is described at a language-independent conceptual level
in "Generic Security Service Application Program Interface Version 2,                  
Update 1" (RFC 2743).  The GSS-API allows a caller application to
authenticate a principal identity, to delegate rights to a peer, and
to apply security services such as confidentiality and integrity on a
per-message basis.  Examples of security mechanisms defined for
GSS-API are "The Simple Public-Key GSS-API Mechanism (SPKM)"
(RFC 2025) and "The Kerberos Version 5 Generic Security Service                       
Application Program Interface (GSS-API) Mechanism: Version 2"
(RFC 4121).

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

This is now a Proposed Standard.

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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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


From nobody Thu May 31 08:45:09 2018
Return-Path: <session-request@ietf.org>
X-Original-To: kitten@ietf.org
Delivered-To: kitten@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DF7D12EAEE; Thu, 31 May 2018 08:45:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: kitten@ietf.org, kitten-chairs@ietf.org, linuxwolf+ietf@outer-planes.net,  kaduk@mit.edu
X-Test-IDTracker: no
X-IETF-IDTracker: 6.81.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152778150423.22820.15273892126915321249.idtracker@ietfa.amsl.com>
Date: Thu, 31 May 2018 08:45:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/UILUkndbOHC5Uw-Rellsn7dpzDQ>
Subject: [kitten] kitten - Not having a session at IETF 102
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 31 May 2018 15:45:04 -0000

Matthew Miller, a chair of the kitten working group, indicated that the kitten working group does not plan to hold a session at IETF 102.

This message was generated and sent by the IETF Meeting Session Request Tool.


