draft-ietf-kitten-gssapi-naming-exts-03.txt   draft-ietf-kitten-gssapi-naming-exts-04.txt 
KITTEN WORKING GROUP N. Williams KITTEN WORKING GROUP N. Williams
Internet-Draft Sun Internet-Draft Sun
Intended status: Standards Track L. Johansson Intended status: Standards Track L. Johansson
Expires: January 14, 2009 Stockholm university Expires: September 9, 2009 Stockholm university
July 13, 2008 March 8, 2009
GSS-API Naming Extensions GSS-API Naming Extensions
draft-ietf-kitten-gssapi-naming-exts-03.txt draft-ietf-kitten-gssapi-naming-exts-04.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 January 14, 2009. This Internet-Draft will expire on September 9, 2009.
Copyright Notice
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
The Generic Security Services API (GSS-API) provides a simple naming The Generic Security Services API (GSS-API) provides a simple naming
architecture that supports name-based authorization. This document architecture that supports name-based authorization. This document
introduces new APIs that extend the GSS-API naming model to support introduces new APIs that extend the GSS-API naming model to support
name attribute transfer between GSS-API peers. name attribute transfer between GSS-API peers.
Table of Contents Table of Contents
skipping to change at page 2, line 38 skipping to change at page 3, line 4
11. GSS_Export_name_composite() . . . . . . . . . . . . . . . 12 11. GSS_Export_name_composite() . . . . . . . . . . . . . . . 12
11.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 13 11.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 13
12. GSS_Map_name_to_any() . . . . . . . . . . . . . . . . . . 13 12. GSS_Map_name_to_any() . . . . . . . . . . . . . . . . . . 13
12.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 13 12.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 13
13. GSS_Release_any_name_mapping() . . . . . . . . . . . . . . 14 13. GSS_Release_any_name_mapping() . . . . . . . . . . . . . . 14
13.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 15 13.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 15
14. IANA Considerations . . . . . . . . . . . . . . . . . . . 15 14. IANA Considerations . . . . . . . . . . . . . . . . . . . 15
15. Security Considerations . . . . . . . . . . . . . . . . . 15 15. Security Considerations . . . . . . . . . . . . . . . . . 15
16. Normative References . . . . . . . . . . . . . . . . . . . 16 16. Normative References . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . 19
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
As described in [I-D.GSS-NAMING] the GSS-API's naming architecture As described in [I-D.GSS-NAMING] the GSS-API's naming architecture
skipping to change at page 16, line 24 skipping to change at page 16, line 24
It is important to understand the meaning of 'authenticated' in this It is important to understand the meaning of 'authenticated' in this
setting. It does not mean that any semantic of the attribute is setting. It does not mean that any semantic of the attribute is
claimed to be true. The only implication is that a trusted third claimed to be true. The only implication is that a trusted third
party has asserted the attribute as opposed to the attribute being party has asserted the attribute as opposed to the attribute being
asserte by the peer itself. Any additional semantics is always the asserte by the peer itself. Any additional semantics is always the
result of applying policy. For instance in a given deployment the result of applying policy. For instance in a given deployment the
mail attribute of the subject may be authenticated and sourced from mail attribute of the subject may be authenticated and sourced from
an email system where 'correct' values are kept. In another setting an email system where 'correct' values are kept. In another setting
users may be allowed to modify their mail addresses freely. In both users may be allowed to modify their mail addresses freely. In both
cases the 'mail' attribute may be authenticated by virtue of being cases the 'mail' attribute may be authenticated by virtue of being
included in signed SAML attribute assertions or by other means included in signed SAML attribute assertions lor by other means
authenticated by the underlying mechanism. authenticated by the underlying mechanism.
When the underlying security mechanism does not provide a permanent When the underlying security mechanism does not provide a permanent
unique identity (eg anonymous kerberos) the GSS-API naming extensions unique identity (eg anonymous kerberos) the GSS-API naming extensions
may be used to provide a replacement permanent unique identity may be used to provide a replacement permanent unique identity
attribute which in this case may be unique for each relying party. attribute which in this case may be unique for each relying party.
This is analogous to the Liberty Alliance targetedID attribute and This is analogous to the Liberty Alliance targetedID attribute and
has similar security implications. has similar security implications.
16. Normative References 16. Normative References
skipping to change at page 19, line 4 skipping to change at line 781
Email: Nicolas.Williams@sun.com Email: Nicolas.Williams@sun.com
Leif Johansson Leif Johansson
Stockholm university Stockholm university
Avdelningen foer IT och Media Avdelningen foer IT och Media
Stockholm SE-106 91 Stockholm SE-106 91
Email: leifj@it.su.se Email: leifj@it.su.se
URI: http://people.su.se/~leifj/ URI: http://people.su.se/~leifj/
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.
 End of changes. 7 change blocks. 
10 lines changed or deleted 18 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/