XML Encoding of SPKI Certificates
draft-paajarvi-xml-spki-cert-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Juha Paajarvi | ||
| Last updated | 2000-03-08 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This draft suggests a standard form for encoding SPKI certificates in XML as opposed to the original s-expression encoding defined in [SPKI]. The standard form is defined as an XML document type definition (DTD). The main emphasis is on the XML-encoding of an authorization certificate that is the basic SPKI certificate form. This draft provides also a brief introduction to XML and a short discussion about the benefits of choosing XML as the certificate encoding format. In addition, this draft discusses the problems of automatic processing of tags (attributes and authorizations transferred by a certificate are called tags in SPKI) when reducing certificates. An example of encoding Java permissions in an SPKI certificate is given to demonstrate the problem and, finally, a solution to this problem is suggested.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)