.ds RF FORMFEED[Page %]
.ds CF
.ds LH Internet Draft
-.ds RH XXXXX
+.ds RH 15 January 2007
.ds CH
.na
.hy 0
.nf
Network Working Group P. Riikonen
Internet-Draft
-draft-riikonen-presence-attrs-03.txt XXXx
-Expires: XXX
+draft-riikonen-presence-attrs-04.txt 15 January 2007
+Expires: 15 July 2007
.in 3
<draft-riikonen-presence-attrs-04.txt>
.ti 0
-Status of this Memo
+Status of this Draft
-This document is an Internet-Draft and is in full conformance with
-all provisions of Section 10 of RFC 2026. 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.
+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 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."
+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 current Internet-Drafts can be accessed at
+http://www.ietf.org/1id-abstracts.html
+The list of Internet-Draft Shadow Directories can be accessed at
+http://www.ietf.org/shadow.html.
-The list of Internet-Draft Shadow Directories can be accessed at
-http://www.ietf.org/shadow.html
-
-The distribution of this memo is unlimited.
.ti 0
2.3 Attribute Data Types ...................................... 4
2.4 Attribute Payload ......................................... 4
2.5 Attributes ................................................ 5
-3 Security Considerations ....................................... 11
+3 Security Considerations ....................................... 12
4 References .................................................... 12
5 Author's Address .............................................. 13
6 Full Copyright Statement ...................................... 13
.ti 0
1.1 Requirements Terminology
-The keywords MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, RECOMMENDED,
+The keywords MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, RECOMMENDED,
MAY, and OPTIONAL, when they appear in this document, are to be
interpreted as described in [RFC2119].
information, or with the required precision that may be desired in
some applications. It is therefore RECOMMENDED that this attribute
would be used to provide only basic and constant user information,
- such as name and contact information, but not online status
+ such as name and contact information, but not online status
information.
Length Type Value
Note that these public keys are intended for signing. Some
certificates may have a key usage restrictions and same key cannot
be used for both encryption and signing. Therefore, the name
- of the certificate type indicates if they are intended for
+ of the certificate type indicates if they are intended for
signing only.
This attribute includes a third party server or authority public
key or CA certificate and MUST be present if the attribute
ATTRIBUTE_SERVER_DIGITAL_SIGNATURE is also present. The format
- for this attribute is identical to the ATTRIBUTE_USER_PUBLIC_KEY
+ for this attribute is identical to the ATTRIBUTE_USER_PUBLIC_KEY
attribute. If there are more than one ATTRIBUTE_SERVER_PUBLIC_KEY
attributes set and ATTRIBUTE_SERVER_DIGITAL_SIGNATURE is also set,
the digital signature SHOULD be verifiable with the first set public
This attribute value includes digital signature of all Attribute
Payloads except this attribute. This signature can be provided by
- the user. This attribute SHOULD be last attribute provided in the
- reply so that it is easier for the receiver to compute the signature
+ the user. This attribute SHOULD be last attribute provided in the
+ reply so that it is easier for the receiver to compute the signature
data to be verified. The format and encoding of this attribute
depends on the public key or certificate used to produce the
signature. See the ATTRIBUTE_USER_PUBLIC_KEY for all public keys
information provided by the user. How it verifies this information
is out of scope of this document, however it may base its
information to a previous registration information and current
- online status of the user in a service. This attribute SHOULD be
+ online status of the user in a service. This attribute SHOULD be
last when provided, so that it is easier for the receiver to
compute the signature data to be verified. The format for this
attribute is identical to the ATTRIBUTE_USER_DIGITAL_SIGNATURE
.ti 0
-4 References
+4 References
[RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
RFC 2426, September 1998.
[SILC1] Riikonen, P., "Secure Internet Live Conferencing (SILC),
- Protocol Specification", Internet Draft, May 2002.
+ Protocol Specification", Internet Draft, January 2007.
[RFC2440] Callas, J., et al, "OpenPGP Message Format", RFC 2440,
November 1998.
-[RFC2459] Housley, R., et al, "Internet X.509 Public Key
+[RFC2459] Housley, R., et al, "Internet X.509 Public Key
Infrastructure, Certificate and CRL Profile", RFC 2459,
January 1999.
-[SSH-TRANS] Ylonen, T., et al, "SSH Transport Layer Protocol",
+[SSH-TRANS] Ylonen, T., et al, "SSH Transport Layer Protocol",
Internet Draft.
[PKCS7] Kalinski, B., "PKCS #7: Cryptographic Message Syntax,
5 Author's Address
Pekka Riikonen
-Snellmaninkatu 34 A 15
-70100 Kuopio
+Helsinki
Finland
EMail: priikone@iki.fi
.ti 0
6 Full Copyright Statement
-Copyright (C) The Internet Society (2003). All Rights Reserved.
-
-This document and translations of it may be copied and furnished to
-others, and derivative works that comment on or otherwise explain it
-or assist in its implementation may be prepared, copied, published
-and distributed, in whole or in part, without restriction of any
-kind, provided that the above copyright notice and this paragraph are
-included on all such copies and derivative works. However, this
-document itself may not be modified in any way, such as by removing
-the copyright notice or references to the Internet Society or other
-Internet organizations, except as needed for the purpose of
-developing Internet standards in which case the procedures for
-copyrights defined in the Internet Standards process must be
-followed, or as required to translate it into languages other than
-English.
-
-The limited permissions granted above are perpetual and will not be
-revoked by the Internet Society or its successors or assigns.
-
-This document and the information contained herein is provided on an
-"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
-TASK FORCE DISCLAIMS 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.
+Copyright (C) The Internet Society (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 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.
projects / runtime.git / blobdiff