Network Working Group S. Schubert
Internet-Draft sip101
Intended status: Standards Track October 15, 2006
Expires: April 18, 2007
Advertising S/MIME Capabilities with Presence
draft-schubert-simple-pidf-cert-00.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
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
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 April 18, 2007.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
This document specifies a means to integrate Certificate Management
Service for The Session Initiation Protocol(SIP) with presence.
Presentities employing the Presence Information Data Format (PIDF)
can use the extensions in this draft to advertise their ability to
exchange signalling using S/MIME, and thus allow secure signalling
between the two peers. In a presence application, the presence of
this information could be displayed to watchers as the padlock
"secure signalling available" of the presentity.
Schubert Expires April 18, 2007 [Page 1]
Internet-Draft Advertising S/MIME Capabilities October 2006
Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. The 'certs' Presence Capability . . . . . . . . . . . . . . . . 3
4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
7.1. Normative Reference . . . . . . . . . . . . . . . . . . . . 4
7.2. Informative Reference . . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5
Intellectual Property and Copyright Statements . . . . . . . . . . 6
Schubert Expires April 18, 2007 [Page 2]
Internet-Draft Advertising S/MIME Capabilities October 2006
1. Requirements notation
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 RFC 2119[1].
2. Introduction
Certificate Management Service for The Session Initiation
Protocol(SIP) [6] [4] is a mechanism that provides a way to address
discovery, retrieval, and management of certificates for SIP
deployments and provide a way for SIP entities to exchange signalling
using S/MIME [5] a reality.
Presence [2] information depicts the status and disposition of a
presentity towards a particular watcher. It encompasses availability
on the network, attitude towards communication, and to some degree
application capability.
Accordingly, this specification provides a means for presence to
communicate a presentity's capability to signal using S/MIME prior to
any session establishment. This mechanism communicates a
presentity's ability to receive signalling using S/MIME by extending
the Presence Information Data Format (PIDF) , a document format for
transmitting presence information.
3. The 'certs' Presence Capability
This specification extends the Presence Capabilities (or 'prescaps')
framework [3] for PIDF with a new element called 'certs'.Transmission
of the 'certs' stanza in a PIDF presence notification communicate the
presentity's ability to signal using S/MIME.
Below, we describe the 'certs' element in detail. The optional
attribute of 'src' indicates the location of the certificate, the
value of this attribute MUST be URI starting with the schema used.
Schema MUST be one of "sips:", "sip:", "http:" or "https:".
If the schema in 'src' is either "sips:" or "sip:" wathcer MUST
follow section 6 of Certificate Management Service for The Session
Initiation Protocol(SIP) to obtain the certificate with an exception
to use the URI presented in the 'src' attribute instead of the
AoR.(URI may be of GRUU etc.)
The absence of 'src' attributes indicates that a watcher interested
in obtaining the certificate MUST follow the section 6 of Certificate
Schubert Expires April 18, 2007 [Page 3]
Internet-Draft Advertising S/MIME Capabilities October 2006
Management Service for The Session Initiation Protocol(SIP) with AoR
as the UR.
4. XML Schema
TBD.
5. Security Considerations
TBD.
6. IANA Considerations
This document registers a new XML namespaces for the 'certs' stanza
of the prescaps extension to PIDF.
7. References
7.1. Normative Reference
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
[2] Sugano, H., Fujimoto, S., Klyne, G., Bateman, A., Carr, W., and
J. Peterson, "CPIM Presence Information Data Format", RFC 3863,
Aug 2004.
[3] Lonnfors, M. and K. Kiss, "User Agent Capability Extension to
Presence Information Data Format (PIDF)",
Draft draft-ietf-simple-prescaps-ext-01 (work in progress),
Jul 2006.
[4] Jennings, C., Peterson, J., and J. Fischl, "Certificate
Management Service for The Session Initiation Protocol (SIP)",
Draft draft-ietf-sip-certs-01 (work in progress), Jun 2006.
7.2. Informative Reference
[5] Ramsdell, B., "Secure/Multipurpose Internet Mail Extensions
(S/MIME) Version 3.1 Message Specification", RFC 3851,
July 2004.
[6] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
Peterson, J., Peterson, R., Handley, M., and E. Schooler, "SIP:
Schubert Expires April 18, 2007 [Page 4]
Internet-Draft Advertising S/MIME Capabilities October 2006
Session Initiation Protocol", RFC 3261, June 2002.
Author's Address
Shida Schubert
SIP101
1094 15 Ave W
Vancouver, BC V6H 1R6
Canada
Phone: +1 604 762 5606
Email: shida@sip101.net
URI: http://www.sip101.net/
Schubert Expires April 18, 2007 [Page 5]
Internet-Draft Advertising S/MIME Capabilities October 2006
Full Copyright Statement
Copyright (C) The Internet Society (2006).
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 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.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Schubert Expires April 18, 2007 [Page 6]