One document matched: draft-saintandre-header-pres-01.txt
Differences from draft-saintandre-header-pres-00.txt
Network Working Group P. Saint-Andre
Internet-Draft XMPP Standards Foundation
Intended status: Informational November 7, 2007
Expires: May 10, 2008
The Presence-ID Header Field
draft-saintandre-header-pres-01
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 May 10, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract
This document defines a header field that enables the author of an
email or netnews message to include a Presence URI in the message
header block for the purpose of associating the author with an
address that provides information about network availability, also
known as "presence".
Saint-Andre Expires May 10, 2008 [Page 1]
Internet-Draft Presence-ID November 2007
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Implementation . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Inclusion . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Generation . . . . . . . . . . . . . . . . . . . . . . . . 3
3.3. Processing . . . . . . . . . . . . . . . . . . . . . . . . 4
3.4. Disposition . . . . . . . . . . . . . . . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6
Intellectual Property and Copyright Statements . . . . . . . . . . 7
Saint-Andre Expires May 10, 2008 [Page 2]
Internet-Draft Presence-ID November 2007
1. Introduction
Several technologies enable entities to share information about their
network availability, also known as "presence" [IMP-REQS]. Such
technologies include the Extensible Messaging and Presence Protocol
[XMPP-IM] and the Session Initiation Protocol [SIP-PRES]. To
facilitate the exchange of presence information, a URI scheme for
presence is defined in [CPP].
Because almost all human users of presence systems also use email
systems and because many such users also use netnews systems, it can
be helpful for such users to specify their presence URIs in the
messages they author. The Presence-ID header field provides a
standard location for such information. This document documents the
syntax and implementation of the Presence-ID header field, including
the information necessary to register it in the Permanent Message
Header Field Registry maintained by the IANA.
2. Syntax
The syntax of the Presence-ID header field is defined below using
Augmented Backus-Naur Form (as specified by [ABNF]), where the "PRES-
URI" rule is defined in [CPP] and the remaining rules are defined in
[MESSAGE]:
"Presence-ID:" [FWS] PRES-URI *WSP CRLF
3. Implementation
3.1. Inclusion
The Presence-ID header field is associated with the author of the
message; see [MESSAGE]. If the "From:" header field contains more
than one mailbox, the Presence-ID header field should not be added to
the message. There should be no more than one instance of the
Presence-ID header field.
3.2. Generation
For a user whose presence URI is "pres:juliet@example.com", the
corresponding Presence-ID header field would be:
Presence-ID: pres:juliet@example.com
Saint-Andre Expires May 10, 2008 [Page 3]
Internet-Draft Presence-ID November 2007
3.3. Processing
Upon receiving a message containing a Presence-ID header field, a
user agent that supports the field should process the field by
resolving the presence URI in accordance with the procedures
specified in [CPP].
3.4. Disposition
A user agent that has processed a Presence-ID header field may
provide appropriate interface elements if it has independent
information linking the author of the message with the specified
presence URI (e.g., via a user-controlled address book or automated
directory lookup). If the user is subscribed to the presence of the
author, such interface elements might include an indicator that the
author is online and available for communication over a network.
4. IANA Considerations
In accordance with [REG], the IANA registers the "Presence-ID" header
field in the Permanent Message Header Field Registry. The
registration template is as follows:
Header field name: Presence-ID
Applicable protocol: mail, netnews
Status: permanent
Author/Change controller: Peter Saint-Andre
<mailto:stpeter@jabber.org>
Specification document(s): draft-saintandre-header-pres-00 [Note to
IANA and RFC Editor: Replace I-D name with RFC XXXX, where "XXXX"
is the number of the RFC that results from this specification, if
any]
Related information: For detail information regarding presence URIs,
refer to RFC 3859.
5. Security Considerations
Message headers are an existing standard and are designed to easily
accommodate new types. Although the Presence-ID header field may be
forged, this problem is inherent in Internet email; however, because
a forged Presence-ID header field may break automated processing,
applications should not depend on the Presence-ID header field to
indicate the authenticity of an email message or the identity of its
author or sender. Including the Presence-ID header field among the
signer header fields in DomainKeys Identified Mail (DKIM) can help to
mitigate against forging of the header (see [DKIMSIG]).
Saint-Andre Expires May 10, 2008 [Page 4]
Internet-Draft Presence-ID November 2007
Advertising presence URIs in message headers may make it easier for
malicious users to harvest such URIs and therefore to send
unsolicited bulk communications to the users or applications
represented by those URIs. Care should be taken in balancing the
benefits of open information exchange against the potential costs of
unwanted communication. An email user agent that is capable of
including the Presence-ID header field in outgoing email messages
should provide an option for its user to disable inclusion of the
Presence-ID header field generally, on a per-recipient basis, and on
a per-message basis.
The security considerations discussed in [URI] and [CPP] may also
apply to the Presence-ID message header.
6. References
6.1. Normative References
[ABNF] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 4234, October 2005.
[CPP] Peterson, J., "Common Profile for Presence (CPP)",
RFC 3859, August 2004.
[MESSAGE] Resnick, P., "Internet Message Format", RFC 2822,
April 2001.
6.2. Informative References
[DKIMSIG] Allman, E., Callas, J., Delany, M., Libbey, M., Fenton,
J., and M. Thomas, "DomainKeys Identified Mail (DKIM)
Signatures", RFC 4871, May 2007.
[IMP-REQS]
Day, M., Aggarwal, S., and J. Vincent, "Instant Messaging
/ Presence Protocol Requirements", RFC 2779,
February 2000.
[REG] Klyne, G., Nottingham, M., and J. Mogul, "Registration
Procedures for Message Header Fields", BCP 90, RFC 3864,
September 2004.
[SIP-PRES]
Rosenberg, J., "A Presence Event Package for the Session
Initiation Protocol (SIP)", RFC 3856, August 2004.
[URI] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Saint-Andre Expires May 10, 2008 [Page 5]
Internet-Draft Presence-ID November 2007
Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, January 2005.
[XMPP-IM] Saint-Andre, P., "Extensible Messaging and Presence
Protocol (XMPP): Instant Messaging and Presence",
RFC 3921, October 2004.
Author's Address
Peter Saint-Andre
XMPP Standards Foundation
Email: stpeter@jabber.org
URI: https://stpeter.im/
Saint-Andre Expires May 10, 2008 [Page 6]
Internet-Draft Presence-ID November 2007
Full Copyright Statement
Copyright (C) The IETF Trust (2007).
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.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Saint-Andre Expires May 10, 2008 [Page 7]
| PAFTECH AB 2003-2026 | 2026-04-24 01:09:11 |