Channel Binding Signalling for the Generic Security Services Application Programming Interface
draft-ietf-kitten-channel-bound-flag-01

Document Type Active Internet-Draft (kitten WG)
Last updated 2017-03-30
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
KITTEN                                                       N. Williams
Internet-Draft                                              Cryptonector
Updates: 2743, 2744 (if approved)                         March 30, 2017
Intended status: Standards Track
Expires: October 1, 2017

Channel Binding Signalling for the Generic Security Services Application
                         Programming Interface
                draft-ietf-kitten-channel-bound-flag-01

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 that 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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 1, 2017.

Williams                 Expires October 1, 2017                [Page 1]
Internet-Draft           GSS Channel Bound Flag               March 2017

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   1.1.  Error in RFC2743  . . . . . . . . . . . . . . . . . . . . .   3
   1.2.  Design  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   1.3.  Alternative Design  . . . . . . . . . . . . . . . . . . . .   4
   1.4.  Future Directions . . . . . . . . . . . . . . . . . . . . .   4
   1.5.  Conventions used in this document . . . . . . . . . . . . .   4
   2.  Channel Binding State Extension . . . . . . . . . . . . . . .   5
   2.1.  GSS_Create_sec_context()  . . . . . . . . . . . . . . . . .   5
   2.1.1.  C-Bindings  . . . . . . . . . . . . . . . . . . . . . . .   5
   2.2.  GSS_Set_context_flags() . . . . . . . . . . . . . . . . . .   6
   2.2.1.  C-Bindings  . . . . . . . . . . . . . . . . . . . . . . .   6
   2.3.  Return Flag for Channel Binding State Signalling  . . . . .   7
   2.3.1.  C-Bindings  . . . . . . . . . . . . . . . . . . . . . . .   7
   2.4.  New Mechanism Attributes  . . . . . . . . . . . . . . . . .   7
   2.5.  Request Flag for Acceptor Confirmation of Channel Binding .   7
   2.5.1.  C-Bindings  . . . . . . . . . . . . . . . . . . . . . . .   8
   2.6.  GSS_Delete_sec_context() Behavior When Applied to Empty
         Security Contexts . . . . . . . . . . . . . . . . . . . . .   8
   3.  Modified Channel Binding Semantics  . . . . . . . . . . . . .   8
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
   6.1.  Normative References  . . . . . . . . . . . . . . . . . . .   9
   6.2.  Informative References  . . . . . . . . . . . . . . . . . .  10
Show full document text