[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
CVS gss/doc/specification
|
From: |
gss-commit |
|
Subject: |
CVS gss/doc/specification |
|
Date: |
Mon, 06 Dec 2004 14:57:33 +0100 |
Update of /home/cvs/gss/doc/specification
In directory dopio:/tmp/cvs-serv19294
Added Files:
draft-ietf-kitten-gssapi-domain-based-names-00.txt
draft-ietf-kitten-gssapi-prf-00.txt
draft-ietf-kitten-krb5-gssapi-domain-based-names-00.txt
draft-ietf-kitten-krb5-gssapi-prf-00.txt
Log Message:
Add.
---
/home/cvs/gss/doc/specification/draft-ietf-kitten-gssapi-domain-based-names-00.txt
2004/12/06 13:57:32 NONE
+++
/home/cvs/gss/doc/specification/draft-ietf-kitten-gssapi-domain-based-names-00.txt
2004/12/06 13:57:32 1.1
NETWORK WORKING GROUP N. Williams
Internet-Draft Sun
Expires: December 30, 2004 July 2004
GSS-API Domain-Based Service Names and Name Type
draft-ietf-kitten-gssapi-domain-based-names-00.txt
Status of this Memo
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 30, 2004.
Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract
This document describes domainname-based service principal names and
the corresponding name type for the Generic Security Service
Application Programming Interface (GSS-API).
Domain-based service names are similar to host-based service names,
but using a domain name (not necessarily and Internat domain name)
instead of or in addition to a hostname. The primary purpose of
domain-based service names is to provide a way to name clustered
services after the domain which they service, thereby allowing their
clients to authorize the service's servers based on authentication of
Williams Expires December 30, 2004 [Page 1]
Internet-Draft GSS Domain Based Names July 2004
their names.
Table of Contents
1. Conventions used in this document . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Name Type OID and Symbolic Name . . . . . . . . . . . . . . . 5
4. Query and Display Syntaxes . . . . . . . . . . . . . . . . . . 6
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1 Normative . . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.2 Informative . . . . . . . . . . . . . . . . . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 9
Intellectual Property and Copyright Statements . . . . . . . . 10
Williams Expires December 30, 2004 [Page 2]
Internet-Draft GSS Domain Based Names July 2004
1. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
Williams Expires December 30, 2004 [Page 3]
Internet-Draft GSS Domain Based Names July 2004
2. Introduction
The use of hostbased principal names for domain-wide services
presents the problem of how to distinguish between an instance of a
hostbased service that is authorized to respond for a domain and one
that isn't.
Consider LDAP. LDAP [RFC3377] with SASL [RFC2222] and the Kerberos V
mechanism [RFC1964] for the GSS-API [RFC2743] uses a hostbased
principal with a service name of "ldap", a reasonable approach,
provided there is only one logical LDAP directory in a Kerberos
realm's domain, and that all ldap servers in that realm serve that
one LDAP directory. If there were other LDAP directories, then
clients could not tell which service is authorized to serve which
directory, not without assuming a secure method for finding LDAP
servers (e.g., DNSSEC). This is a significant, and oft-unstated
restriction on users of LDAP.
Domain based names can eliminate this problem by allowing LDAP
service names to indicate which LDAP directory they are authorized to
serve.
A domain-based name consists of three required elements:
o a service name
o a domain name
o a hostname
Williams Expires December 30, 2004 [Page 4]
Internet-Draft GSS Domain Based Names July 2004
3. Name Type OID and Symbolic Name
The new name type has an OID of
[NOTE: OID assignment to be made with IANA.]
{iso(1) org(3) dod(6) internet(1) security(5) nametypes(6)
gss-domain-based(5)}
The recommended symbolic name for this GSS-API name type is
"GSS_C_NT_DOMAINBASED_SERVICE".
Williams Expires December 30, 2004 [Page 5]
Internet-Draft GSS Domain Based Names July 2004
4. Query and Display Syntaxes
There is a single name syntax for domain-based names.
The syntax is:
domain-based-name :=
| <service> '@' <domain> '@' <hostname>
Note that for Internet domain names the trailing '.' is not and MUST
NOT be included in the domain name (or hostname) parts of the display
form GSS-API domain-based MNs.
Williams Expires December 30, 2004 [Page 6]
Internet-Draft GSS Domain Based Names July 2004
5. Examples
o address@hidden@ds1.example.tld
o address@hidden@kdc1.example.tld
Williams Expires December 30, 2004 [Page 7]
Internet-Draft GSS Domain Based Names July 2004
6. Security Considerations
Use of GSS-API domain-based names may not be negotiable by some
GSS-API mechanisms, and some acceptors may not support GSS-API
domain-based names. In such cases initiators are left to fallback on
the use of hostbased names, in which case the initiators MUST also
verify that the acceptor's hostbased name is authorized to provide
[159 lines skipped]
--- /home/cvs/gss/doc/specification/draft-ietf-kitten-gssapi-prf-00.txt
2004/12/06 13:57:33 NONE
+++ /home/cvs/gss/doc/specification/draft-ietf-kitten-gssapi-prf-00.txt
2004/12/06 13:57:33 1.1
[606 lines skipped]
---
/home/cvs/gss/doc/specification/draft-ietf-kitten-krb5-gssapi-domain-based-names-00.txt
2004/12/06 13:57:33 NONE
+++
/home/cvs/gss/doc/specification/draft-ietf-kitten-krb5-gssapi-domain-based-names-00.txt
2004/12/06 13:57:33 1.1
[997 lines skipped]
--- /home/cvs/gss/doc/specification/draft-ietf-kitten-krb5-gssapi-prf-00.txt
2004/12/06 13:57:33 NONE
+++ /home/cvs/gss/doc/specification/draft-ietf-kitten-krb5-gssapi-prf-00.txt
2004/12/06 13:57:33 1.1
[1332 lines skipped]