The application/osp-token MIME type
draft-thomas-mime-osp-token-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | David Oran , Stephen Thomas , Butch Anton , Richard Brennan | ||
| Last updated | 1999-04-07 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-thomas-mime-osp-token-00.txt
Abstract
The Open Settlement Protocol (OSP)[1], an open standard from the European Telecommunications Standards Institute, specifies a means by which IP telephony equipment in one administrative domain may request access to IP telephony equipment (including, but not limited to: Gateways, Gatekeepers, Border Elements, etc.) in another administrative domain. OSP grants such access by returning authorization tokens, which must then be passed to the destination IP telephony gateway during call signaling. In order to support access control via OSP, IP telephony signaling protocols must be capable of carrying these authorization tokens in an interoperable way. This memo defines just such a method for protocols, such as the Session Initiation Protocol[2], that can support carriage of MIME types during call signaling. This memo conforms to the requirements for MIME type registration defined in RFC 2048[3].
Authors
David Oran
(oran@cisco.com)
Stephen Thomas
(stephen.thomas@transnexus.com)
Butch Anton
(butch@ipass.com)
Richard Brennan
(rbrennan@gric.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)