[kitten] I-D Action: draft-ietf-kitten-channel-bound-flag-03.txt

internet-drafts@ietf.org Fri, 27 July 2018 15:58 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: kitten@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: kitten@ietf.org
Message-ID: <153270709473.32657.6439329720119757327@ietfa.amsl.com>
Date: Fri, 27 Jul 2018 08:58:14 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/poJ_xx9di91CY9Qk8QQZ9eFLuLY>
Subject: [kitten] I-D Action: draft-ietf-kitten-channel-bound-flag-03.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Common Authentication Technology Next Generation WG of the IETF.

        Title           : Channel Binding Signalling for the Generic Security Services Application Programming Interface
        Authors         : Robbie Harwood
                          Nicolas Williams
	Filename        : draft-ietf-kitten-channel-bound-flag-03.txt
	Pages           : 9
	Date            : 2018-07-27

Abstract:
   Channel binding is a technique that allows applications to use a
   secure channel at a lower layer without having to use authentication
   at that lower layer.  The concept of channel binding comes from the
   Generic Security Services Application Programming Interface (GSS-
   API).  It turns out that the semantics commonly implemented are
   different than those specified in the base GSS-API RFC (RFC2743), and
   that that specification has a serious bug.  This document addresses
   both the inconsistency as-implemented and the specification bug.

   This Internet-Draft proposes the addition of a "channel bound" return
   flag for the GSS_Init_sec_context() and GSS_Accept_sec_context()
   functions.  Two behaviors are specified: a default, safe behavior
   reflecting existing implementation deployments, and a behavior that
   is only safe when the application specifically tells the GSS-API that
   it (the application) supports the new behavior.  Additional API
   elements related to this are also added, including a new security
   context establishment API.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-kitten-channel-bound-flag/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-kitten-channel-bound-flag-03
https://datatracker.ietf.org/doc/html/draft-ietf-kitten-channel-bound-flag-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-kitten-channel-bound-flag-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

[kitten] I-D Action: draft-ietf-kitten-channel-bo… internet-drafts