draft-ietf-kitten-gssapi-channel-bindings-05.txt   draft-ietf-kitten-gssapi-channel-bindings-06.txt 
KITTEN WG N. Williams KITTEN WG N. Williams
Internet-Draft Sun Internet-Draft Sun
Intended status: Standards Track September 23, 2008 Intended status: Standards Track March 9, 2009
Expires: March 27, 2009 Expires: September 10, 2009
Clarifications and Extensions to the GSS-API for the Use of Channel Clarifications and Extensions to the GSS-API for the Use of Channel
Bindings Bindings
draft-ietf-kitten-gssapi-channel-bindings-05.txt draft-ietf-kitten-gssapi-channel-bindings-06.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on March 27, 2009. This Internet-Draft will expire on September 10, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (c) 2009 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 in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract Abstract
This document clarifies and generalizes the Generic Security Services This document clarifies and generalizes the Generic Security Services
Application Programming Interface (GSS-API) "channel bindings" Application Programming Interface (GSS-API) "channel bindings"
facility, and imposes requirements on future GSS-API mechanisms and facility, and imposes requirements on future GSS-API mechanisms and
programming language bindings of the GSS-API. programming language bindings of the GSS-API.
Table of Contents Table of Contents
1. Conventions used in this document . . . . . . . . . . . . . . 3 1. Conventions used in this document . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. New Requirements for GSS-API Mechanisms . . . . . . . . . . . 5 3. New Requirements for GSS-API Mechanisms . . . . . . . . . . . 5
4. Generic Structure for GSS-API Channel Bindings . . . . . . . . 6 4. Generic Structure for GSS-API Channel Bindings . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. Normative References . . . . . . . . . . . . . . . . . . . . . 9 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10 7.1. Normative References . . . . . . . . . . . . . . . . . . . 10
Intellectual Property and Copyright Statements . . . . . . . . . . 11 7.2. Informative References . . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 11
1. Conventions used in this document 1. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Introduction 2. Introduction
The base GSS-API v2, update 1 specification [RFC2743] provides a The base GSS-API v2, update 1 specification [RFC2743] provides a
skipping to change at page 6, line 22 skipping to change at page 6, line 22
defines, in terms of C, what should have been a generic structure for defines, in terms of C, what should have been a generic structure for
channel bindings. The Kerberos V GSS mechanism [RFC4121] also channel bindings. The Kerberos V GSS mechanism [RFC4121] also
defines a method for encoding GSS channel bindings in a way that is defines a method for encoding GSS channel bindings in a way that is
independent of the C-Bindings -- otherwise the mechanism's channel independent of the C-Bindings -- otherwise the mechanism's channel
binding facility would not be useable with other language bindings. binding facility would not be useable with other language bindings.
In other words, the structure of GSS channel bindings given in In other words, the structure of GSS channel bindings given in
[RFC2744] is actually generic, rather than specific to the C [RFC2744] is actually generic, rather than specific to the C
programming language. programming language.
Here, then, is a generic re-statement of this structure, in pseudo- We generalize it as shown below, using the same pseudo-ASN.1 as is
ASN.1: used in RFC2743. Although the figure below is, indeed, a valid ASN.1
[CCITT.X680.2002] type, we do not provide a full ASN.1 module as none
is needed because no standard encoding of this structure is needed --
the definition below is part of an abstract API, not part of a
protocol defining bits on the wire. GSS-API mechanisms do need to
encode the contents of this structure, but that encoding will be
mechanism specific (see below).
GSS-CHANNEL-BINDINGS ::= SEQUENCE { GSS-CHANNEL-BINDINGS ::= SEQUENCE {
initiator-address-type INTEGER, -- See RFC2744 initiator-address-type INTEGER, -- See RFC2744
initiator-address OCTET STRING, -- See RFC2744 initiator-address OCTET STRING, -- See RFC2744
acceptor-address-type INTEGER, -- See RFC2744 acceptor-address-type INTEGER, -- See RFC2744
acceptor-address OCTET STRING, -- See RFC2744 acceptor-address OCTET STRING, -- See RFC2744
application-data OCTET STRING, -- See RFC5056 application-data OCTET STRING -- See RFC5056
} }
Abstract GSS-API channel bindings structure
The values for the address fields are described in [RFC2744]. The values for the address fields are described in [RFC2744].
New language-specific bindings of the GSS-API SHOULD specify a New language-specific bindings of the GSS-API SHOULD specify a
language-specific formulation of this structure. language-specific formulation of this structure.
Where a language binding of the GSS-API models channel bindings as Where a language binding of the GSS-API models channel bindings as
OCTET STRINGs (or the language's equivalent), then the implementation OCTET STRINGs (or the language's equivalent), then the implementation
MUST assume that the given bindings correspond only to the MUST assume that the given bindings correspond only to the
application-data field of GSS-CHANNEL-BINDINGS as shown above, rather application-data field of GSS-CHANNEL-BINDINGS as shown above, rather
than some encoding of GSS-CHANNEL-BINDINGS. than some encoding of GSS-CHANNEL-BINDINGS.
skipping to change at page 9, line 5 skipping to change at page 10, line 5
[RFC5056]. [RFC5056].
Language bindings that use OCTET STRING (or equivalent) for channel Language bindings that use OCTET STRING (or equivalent) for channel
bindings will not support the use of network addresses as channel bindings will not support the use of network addresses as channel
bindings. This should not cause any security problems, as the use of bindings. This should not cause any security problems, as the use of
network addresses as channel bindings is not generally secure. network addresses as channel bindings is not generally secure.
However, it is important that "end-point channel bindings" not be However, it is important that "end-point channel bindings" not be
modelled as network addresses, otherwise such channel bindings may modelled as network addresses, otherwise such channel bindings may
not be useable with all language bindings of the GSS-API. not be useable with all language bindings of the GSS-API.
7. Normative References 7. References
7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2743] Linn, J., "Generic Security Service Application Program [RFC2743] Linn, J., "Generic Security Service Application Program
Interface Version 2, Update 1", RFC 2743, January 2000. Interface Version 2, Update 1", RFC 2743, January 2000.
[RFC2744] Wray, J., "Generic Security Service API Version 2 : [RFC2744] Wray, J., "Generic Security Service API Version 2 :
C-bindings", RFC 2744, January 2000. C-bindings", RFC 2744, January 2000.
[RFC4121] Zhu, L., Jaganathan, K., and S. Hartman, "The Kerberos [RFC4121] Zhu, L., Jaganathan, K., and S. Hartman, "The Kerberos
Version 5 Generic Security Service Application Program Version 5 Generic Security Service Application Program
Interface (GSS-API) Mechanism: Version 2", RFC 4121, Interface (GSS-API) Mechanism: Version 2", RFC 4121,
July 2005. July 2005.
[RFC5056] Williams, N., "On the Use of Channel Bindings to Secure [RFC5056] Williams, N., "On the Use of Channel Bindings to Secure
Channels", RFC 5056, November 2007. Channels", RFC 5056, November 2007.
7.2. Informative References
[CCITT.X680.2002]
International International Telephone and Telegraph
Consultative Committee, "Abstract Syntax Notation One
(ASN.1): Specification of basic notation",
CCITT Recommendation X.680, July 2002.
Author's Address Author's Address
Nicolas Williams Nicolas Williams
Sun Microsystems Sun Microsystems
5300 Riata Trace Ct 5300 Riata Trace Ct
Austin, TX 78727 Austin, TX 78727
US US
Email: Nicolas.Williams@sun.com Email: Nicolas.Williams@sun.com
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 12 change blocks. 
18 lines changed or deleted 42 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/