idnits 2.17.1 draft-ietf-kitten-gssapi-channel-bindings-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.i or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == The 'Updates: ' line in the draft header should list only the _numbers_ of the RFCs which will be updated by this document (if approved); it should not include the word 'RFC' in the list. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (April 6, 2009) is 5470 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 KITTEN WG N. Williams 3 Internet-Draft Sun 4 Updates: rfc2743 April 6, 2009 5 (if approved) 6 Intended status: Standards Track 7 Expires: October 8, 2009 9 Clarifications and Extensions to the GSS-API for the Use of Channel 10 Bindings 11 draft-ietf-kitten-gssapi-channel-bindings-07.txt 13 Status of this Memo 15 This Internet-Draft is submitted to IETF in full conformance with the 16 provisions of BCP 78 and BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on October 8, 2009. 36 Copyright Notice 38 Copyright (c) 2009 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents in effect on the date of 43 publication of this document (http://trustee.ietf.org/license-info). 44 Please review these documents carefully, as they describe your rights 45 and restrictions with respect to this document. 47 Abstract 49 This document clarifies and generalizes the Generic Security Services 50 Application Programming Interface (GSS-API) "channel bindings" 51 facility, and imposes requirements on future GSS-API mechanisms and 52 programming language bindings of the GSS-API. 54 Table of Contents 56 1. Conventions used in this document . . . . . . . . . . . . . . 3 57 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 58 3. New Requirements for GSS-API Mechanisms . . . . . . . . . . . 5 59 4. Generic Structure for GSS-API Channel Bindings . . . . . . . . 6 60 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 61 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 62 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 63 7.1. Normative References . . . . . . . . . . . . . . . . . . . 10 64 7.2. Informative References . . . . . . . . . . . . . . . . . . 10 65 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 11 67 1. Conventions used in this document 69 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 70 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 71 document are to be interpreted as described in [RFC2119]. 73 2. Introduction 75 The base GSS-API v2, update 1 specification [RFC2743] provides a 76 facility for channel binding (see also [RFC5056]), but its treatment 77 was incomplete. The C-bindings of the GSS-API [RFC2744] expanded a 78 little on this facility in what should have been a generic way, but 79 was a C-specific way, and still, the treatment of this facility was 80 incomplete. 82 This document clarifies the GSS-API's channel binding facility and 83 generalizes the parts of it that are specified in the C-bindings 84 document but which should have been generic from the first. 86 3. New Requirements for GSS-API Mechanisms 88 Given the publication of RFC5056 we now assert that all new GSS-API 89 mechanisms that support channel binding MUST conform to [RFC5056]. 91 4. Generic Structure for GSS-API Channel Bindings 93 The base GSS-API v2, update 1 specification [RFC2743] provides a 94 facility for channel binding. It models channel bindings as an OCTET 95 STRING and leaves it to the GSS-API v2, update 1 C-Bindings 96 specification to specify the structure of the contents of the channel 97 bindings OCTET STRINGs. The C-Bindings specification [RFC2744] then 98 defines, in terms of C, what should have been a generic structure for 99 channel bindings. The Kerberos V GSS mechanism [RFC4121] also 100 defines a method for encoding GSS channel bindings in a way that is 101 independent of the C-Bindings -- otherwise the mechanism's channel 102 binding facility would not be useable with other language bindings. 104 In other words, the structure of GSS channel bindings given in 105 [RFC2744] is actually generic, rather than specific to the C 106 programming language. 108 We generalize it as shown below, using the same pseudo-ASN.1 as is 109 used in RFC2743. Although the figure below is, indeed, a valid ASN.1 110 [CCITT.X680.2002] type, we do not provide a full ASN.1 module as none 111 is needed because no standard encoding of this structure is needed -- 112 the definition below is part of an abstract API, not part of a 113 protocol defining bits on the wire. GSS-API mechanisms do need to 114 encode the contents of this structure, but that encoding will be 115 mechanism specific (see below). 117 GSS-CHANNEL-BINDINGS ::= SEQUENCE { 118 initiator-address-type INTEGER, -- See RFC2744 119 initiator-address OCTET STRING, -- See RFC2744 120 acceptor-address-type INTEGER, -- See RFC2744 121 acceptor-address OCTET STRING, -- See RFC2744 122 application-data OCTET STRING -- See RFC5056 123 } 125 Abstract GSS-API channel bindings structure 127 The values for the address fields are described in [RFC2744]. 129 New language-specific bindings of the GSS-API SHOULD specify a 130 language-specific formulation of this structure. 132 Where a language binding of the GSS-API models channel bindings as 133 OCTET STRINGs (or the language's equivalent), then the implementation 134 MUST assume that the given bindings correspond only to the 135 application-data field of GSS-CHANNEL-BINDINGS as shown above, rather 136 than some encoding of GSS-CHANNEL-BINDINGS. 138 As mentioned above, [RFC4121] describes an encoding of the above GSS- 139 CHANNEL-BINDINGS structure, and then hashes that encoding. Other 140 GSS-API mechanisms are free to use that encoding. 142 5. IANA Considerations 144 There are no IANA considerations in this document. 146 6. Security Considerations 148 For general security considerations relating to channel bindings see 149 [RFC5056]. 151 Language bindings that use OCTET STRING (or equivalent) for channel 152 bindings will not support the use of network addresses as channel 153 bindings. This should not cause any security problems, as the use of 154 network addresses as channel bindings is not generally secure. 155 However, it is important that "end-point channel bindings" not be 156 modelled as network addresses, otherwise such channel bindings may 157 not be useable with all language bindings of the GSS-API. 159 7. References 161 7.1. Normative References 163 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 164 Requirement Levels", BCP 14, RFC 2119, March 1997. 166 [RFC2743] Linn, J., "Generic Security Service Application Program 167 Interface Version 2, Update 1", RFC 2743, January 2000. 169 [RFC2744] Wray, J., "Generic Security Service API Version 2 : 170 C-bindings", RFC 2744, January 2000. 172 [RFC4121] Zhu, L., Jaganathan, K., and S. Hartman, "The Kerberos 173 Version 5 Generic Security Service Application Program 174 Interface (GSS-API) Mechanism: Version 2", RFC 4121, 175 July 2005. 177 [RFC5056] Williams, N., "On the Use of Channel Bindings to Secure 178 Channels", RFC 5056, November 2007. 180 7.2. Informative References 182 [CCITT.X680.2002] 183 International International Telephone and Telegraph 184 Consultative Committee, "Abstract Syntax Notation One 185 (ASN.1): Specification of basic notation", 186 CCITT Recommendation X.680, July 2002. 188 Author's Address 190 Nicolas Williams 191 Sun Microsystems 192 5300 Riata Trace Ct 193 Austin, TX 78727 194 US 196 Email: Nicolas.Williams@sun.com