draft-ietf-sip-certs-10.txt   draft-ietf-sip-certs-11.txt 
Network Working Group C. Jennings Network Working Group C. Jennings
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track J. Fischl, Ed. Intended status: Standards Track J. Fischl, Ed.
Expires: September 5, 2010 Skype Expires: September 6, 2010 Skype
March 4, 2010 March 5, 2010
Certificate Management Service for The Session Initiation Protocol (SIP) Certificate Management Service for The Session Initiation Protocol (SIP)
draft-ietf-sip-certs-10 draft-ietf-sip-certs-11
Abstract Abstract
This draft defines a Credential Service that allows Session This draft defines a Credential Service that allows Session
Initiation Protocol (SIP) User Agents (UAs) to use a SIP event Initiation Protocol (SIP) User Agents (UAs) to use a SIP event
package to discover the certificates of other users. This mechanism package to discover the certificates of other users. This mechanism
allows user agents that want to contact a given Address-of-Record allows user agents that want to contact a given Address-of-Record
(AOR) to retrieve that AOR's certificate by subscribing to the (AOR) to retrieve that AOR's certificate by subscribing to the
Credential Service, which returns an authenticated response Credential Service, which returns an authenticated response
containing that certificate. The Credential Service also allows containing that certificate. The Credential Service also allows
skipping to change at page 1, line 44 skipping to change at page 1, line 44
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 5, 2010. This Internet-Draft will expire on September 6, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 7 skipping to change at page 3, line 7
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. UA Behavior with Certificates . . . . . . . . . . . . . . . . 8 4. UA Behavior with Certificates . . . . . . . . . . . . . . . . 9
5. UA Behavior with Credentials . . . . . . . . . . . . . . . . . 9 5. UA Behavior with Credentials . . . . . . . . . . . . . . . . . 10
6. Event Package Formal Definition for "certificate" . . . . . . 10 6. Event Package Formal Definition for "certificate" . . . . . . 11
6.1. Event Package Name . . . . . . . . . . . . . . . . . . . . 10 6.1. Event Package Name . . . . . . . . . . . . . . . . . . . . 11
6.2. SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . . . 10 6.2. SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . . . 11
6.3. Subscription Duration . . . . . . . . . . . . . . . . . . 10 6.3. Subscription Duration . . . . . . . . . . . . . . . . . . 11
6.4. NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . . . 10 6.4. NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . . . 11
6.5. Subscriber Generation of SUBSCRIBE Requests . . . . . . . 11 6.5. Subscriber Generation of SUBSCRIBE Requests . . . . . . . 12
6.6. Notifier Processing of SUBSCRIBE Requests . . . . . . . . 11 6.6. Notifier Processing of SUBSCRIBE Requests . . . . . . . . 12
6.7. Notifier Generation of NOTIFY Requests . . . . . . . . . . 11 6.7. Notifier Generation of NOTIFY Requests . . . . . . . . . . 12
6.8. Subscriber Processing of NOTIFY Requests . . . . . . . . . 12 6.8. Subscriber Processing of NOTIFY Requests . . . . . . . . . 13
6.9. Handling of Forked Requests . . . . . . . . . . . . . . . 12 6.9. Handling of Forked Requests . . . . . . . . . . . . . . . 13
6.10. Rate of Notifications . . . . . . . . . . . . . . . . . . 12 6.10. Rate of Notifications . . . . . . . . . . . . . . . . . . 13
6.11. State Agents and Lists . . . . . . . . . . . . . . . . . . 12 6.11. State Agents and Lists . . . . . . . . . . . . . . . . . . 13
6.12. Behavior of a Proxy Server . . . . . . . . . . . . . . . . 12 6.12. Behavior of a Proxy Server . . . . . . . . . . . . . . . . 13
7. Event Package Formal Definition for "credential" . . . . . . . 13 7. Event Package Formal Definition for "credential" . . . . . . . 14
7.1. Event Package Name . . . . . . . . . . . . . . . . . . . . 13 7.1. Event Package Name . . . . . . . . . . . . . . . . . . . . 14
7.2. SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . . . 13 7.2. SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . . . 14
7.3. Subscription Duration . . . . . . . . . . . . . . . . . . 13 7.3. Subscription Duration . . . . . . . . . . . . . . . . . . 14
7.4. NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . . . 13 7.4. NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . . . 14
7.5. Subscriber Generation of SUBSCRIBE Requests . . . . . . . 13 7.5. Subscriber Generation of SUBSCRIBE Requests . . . . . . . 15
7.6. Notifier Processing of SUBSCRIBE Requests . . . . . . . . 14 7.6. Notifier Processing of SUBSCRIBE Requests . . . . . . . . 15
7.7. Notifier Generation of NOTIFY Requests . . . . . . . . . . 14 7.7. Notifier Generation of NOTIFY Requests . . . . . . . . . . 15
7.8. Generation of PUBLISH Requests . . . . . . . . . . . . . . 15 7.8. Generation of PUBLISH Requests . . . . . . . . . . . . . . 16
7.9. Notifier Processing of PUBLISH Requests . . . . . . . . . 15 7.9. Notifier Processing of PUBLISH Requests . . . . . . . . . 16
7.10. Subscriber Processing of NOTIFY Requests . . . . . . . . . 16 7.10. Subscriber Processing of NOTIFY Requests . . . . . . . . . 17
7.11. Handling of Forked Requests . . . . . . . . . . . . . . . 16 7.11. Handling of Forked Requests . . . . . . . . . . . . . . . 17
7.12. Rate of Notifications . . . . . . . . . . . . . . . . . . 16 7.12. Rate of Notifications . . . . . . . . . . . . . . . . . . 17
7.13. State Agents and Lists . . . . . . . . . . . . . . . . . . 16 7.13. State Agents and Lists . . . . . . . . . . . . . . . . . . 17
7.14. Behavior of a Proxy Server . . . . . . . . . . . . . . . . 16 7.14. Behavior of a Proxy Server . . . . . . . . . . . . . . . . 18
8. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 8. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.1. Encrypted Page Mode IM Message . . . . . . . . . . . . . . 17 8.1. Encrypted Page Mode IM Message . . . . . . . . . . . . . . 18
8.2. Setting and Retrieving UA Credentials . . . . . . . . . . 18 8.2. Setting and Retrieving UA Credentials . . . . . . . . . . 19
9. Security Considerations . . . . . . . . . . . . . . . . . . . 18 9. Security Considerations . . . . . . . . . . . . . . . . . . . 19
9.1. Certificate Revocation . . . . . . . . . . . . . . . . . . 21 9.1. Certificate Revocation . . . . . . . . . . . . . . . . . . 22
9.2. Certificate Replacement . . . . . . . . . . . . . . . . . 21 9.2. Certificate Replacement . . . . . . . . . . . . . . . . . 22
9.3. Trusting the Identity of a Certificate . . . . . . . . . . 21 9.3. Trusting the Identity of a Certificate . . . . . . . . . . 23
9.3.1. Extra Assurance . . . . . . . . . . . . . . . . . . . 22 9.3.1. Extra Assurance . . . . . . . . . . . . . . . . . . . 24
9.4. SACRED Framework . . . . . . . . . . . . . . . . . . . . . 23 9.4. SACRED Framework . . . . . . . . . . . . . . . . . . . . . 24
9.5. Crypto Profiles . . . . . . . . . . . . . . . . . . . . . 23 9.5. Crypto Profiles . . . . . . . . . . . . . . . . . . . . . 24
9.6. User Certificate Generation . . . . . . . . . . . . . . . 24 9.6. User Certificate Generation . . . . . . . . . . . . . . . 25
9.7. Compromised Authentication Service . . . . . . . . . . . . 24 9.7. Compromised Authentication Service . . . . . . . . . . . . 25
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
10.1. Certificate Event Package . . . . . . . . . . . . . . . . 25 10.1. Certificate Event Package . . . . . . . . . . . . . . . . 26
10.2. Credential Event Package . . . . . . . . . . . . . . . . . 25 10.2. Credential Event Package . . . . . . . . . . . . . . . . . 26
10.3. PKCS#8 . . . . . . . . . . . . . . . . . . . . . . . . . . 26
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 26 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 26
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27
12.1. Normative References . . . . . . . . . . . . . . . . . . . 27 12.1. Normative References . . . . . . . . . . . . . . . . . . . 27
12.2. Informational References . . . . . . . . . . . . . . . . . 28 12.2. Informational References . . . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 28 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 28
1. Introduction 1. Introduction
[RFC3261], as ammended by [RFC3853], provides a mechanism for end-to- [RFC3261], as amended by [RFC3853], provides a mechanism for end-to-
end encryption and integrity using S/MIME [RFC3851]. Several end encryption and integrity using S/MIME [RFC3851]. Several
security properties of [RFC3261] depend on S/MIME, and yet it has not security properties of [RFC3261] depend on S/MIME, and yet it has not
been widely deployed. One reason is the complexity of providing a been widely deployed. One reason is the complexity of providing a
reasonable certificate distribution infrastructure. This reasonable certificate distribution infrastructure. This
specification proposes a way to address discovery, retrieval, and specification proposes a way to address discovery, retrieval, and
management of certificates for SIP deployments. Combined with the management of certificates for SIP deployments. Combined with the
SIP Identity [RFC4474] specification, this specification allows users SIP Identity [RFC4474] specification, this specification allows users
to have certificates that are not signed by any well known to have certificates that are not signed by any well known
certificate authority while still strongly binding the user's certificate authority while still strongly binding the user's
identity to the certificate. identity to the certificate.
skipping to change at page 14, line 34 skipping to change at page 14, line 34
The credential service SHOULD keep subscriptions active for UAs that The credential service SHOULD keep subscriptions active for UAs that
are currently registered. are currently registered.
7.4. NOTIFY Bodies 7.4. NOTIFY Bodies
An implementation compliant to this specification MUST support the An implementation compliant to this specification MUST support the
multipart/mixed type (see [RFC2046]). This allows a notification to multipart/mixed type (see [RFC2046]). This allows a notification to
contain multiple resource documents including at a minimum the contain multiple resource documents including at a minimum the
application/pkix-cert body with the certificate and an application/ application/pkix-cert body with the certificate and an application/
pkcs8 body that has the associated private key information for the pkcs8 body that has the associated private key information for the
certificate. certificate. The application/pkcs8 media type is defined in
[I-D.turner-asymmetrickeyformat].
The absence of an Accept header in the SUBSCRIBE indicates support The absence of an Accept header in the SUBSCRIBE indicates support
for multipart/mixed and the content types application/pkix-cert and for multipart/mixed and the content types application/pkix-cert and
application/pkcs8. If an Accept header is present, these types MUST application/pkcs8. If an Accept header is present, these types MUST
be included, in additional to any other types supported by the be included, in additional to any other types supported by the
client. client.
The application/pkix-cert body is a DER encoded X.509v3 certificate The application/pkix-cert body is a DER encoded X.509v3 certificate
[RFC2585]. The application/pkcs8 body contains a DER-encoded [RFC2585]. The application/pkcs8 body contains a DER-encoded
[RFC5208] object that contains the private key. The PKCS#8 objects [RFC5208] object that contains the private key. The PKCS#8 objects
skipping to change at page 15, line 33 skipping to change at page 15, line 38
an attacker. The credential service will authenticate the UA using an attacker. The credential service will authenticate the UA using
the usual SIP Digest mechanism, so the UA can expect to receive a SIP the usual SIP Digest mechanism, so the UA can expect to receive a SIP
challenge to the SUBSCRIBE or PUBLISH requests. challenge to the SUBSCRIBE or PUBLISH requests.
7.6. Notifier Processing of SUBSCRIBE Requests 7.6. Notifier Processing of SUBSCRIBE Requests
When a credential service receives a SUBSCRIBE for a credential, the When a credential service receives a SUBSCRIBE for a credential, the
credential service has to authenticate and authorize the UA and credential service has to authenticate and authorize the UA and
validate that adequate transport security is being used. Only a UA validate that adequate transport security is being used. Only a UA
that can authenticate as being able to register as the AOR is that can authenticate as being able to register as the AOR is
authorized to receive the credentials for that AOR. The credential authorized to receive the credentials for that AOR. The Credential
Service MUST digest challenge the UA to authenticate the UA and then Service MUST digest challenge the UA to authenticate the UA and then
decide if it is authorized to receive the credentials. If decide if it is authorized to receive the credentials. If
authentication is successful, the Notifier MAY limit the duration of authentication is successful, the Notifier MAY limit the duration of
the subscription to an administrator-defined period of time. The the subscription to an administrator-defined period of time. The
duration of the subscription MUST NOT be larger than the length of duration of the subscription MUST NOT be larger than the length of
time for which the certificate is still valid. The Expires header time for which the certificate is still valid. The Expires header
field SHOULD be set so that it is not longer than the notAfter date field SHOULD be set so that it is not longer than the notAfter date
in the certificate. in the certificate.
7.7. Notifier Generation of NOTIFY Requests 7.7. Notifier Generation of NOTIFY Requests
skipping to change at page 24, line 37 skipping to change at page 24, line 44
Specifically, Section 7.5, Section 7.6 and Section 7.9 follow the Specifically, Section 7.5, Section 7.6 and Section 7.9 follow the
cTLS architecture described in section 4.2.2 of [RFC3760]. The cTLS architecture described in section 4.2.2 of [RFC3760]. The
client authenticates the server using the server's TLS certificate. client authenticates the server using the server's TLS certificate.
The server authenticates the client using a SIP digest transaction The server authenticates the client using a SIP digest transaction
inside the TLS session. The TLS sessions form a strong session key inside the TLS session. The TLS sessions form a strong session key
that is used to protect the credentials being exchanged. that is used to protect the credentials being exchanged.
9.5. Crypto Profiles 9.5. Crypto Profiles
Credential services SHOULD implement the server name indication Credential Services SHOULD implement the server name indication
extensions in [RFC5246] and they MUST support a TLS profile of extensions in [RFC4366]. As specified in [RFC5246], Credential
TLS_RSA_WITH_AES_128_CBC_SHA as described in [RFC5246] as a profile Services MUST support the TLS cipher suite
of TLS_RSA_WITH_3DES_EDE_CBC_SHA. TLS_RSA_WITH_AES_128_CBC_SHA.
The PKCS#8 in the clients MUST implement PBES2 with a key derivation The PKCS#8 in the clients MUST implement PBES2 with a key derivation
algorithm of PBKDF2 using HMAC with SHA1 and an encryption algorithm algorithm of PBKDF2 using HMAC with SHA1 and an encryption algorithm
of DES-EDE2-CBC-Pad as defined in [RFC2898]. It is RECOMMENDED that of DES-EDE2-CBC-Pad as defined in [RFC2898]. It is RECOMMENDED that
this profile be used when using PKCS#8. A different passphrase this profile be used when using PKCS#8. A different passphrase
SHOULD be used for the PKCS#8 encryption than is used for server SHOULD be used for the PKCS#8 encryption than is used for server
authentication. authentication.
9.6. User Certificate Generation 9.6. User Certificate Generation
skipping to change at page 26, line 4 skipping to change at page 26, line 9
expiry date. expiry date.
The UA MAY also allow the user to see the fingerprints for the cached The UA MAY also allow the user to see the fingerprints for the cached
certificates so that they can be verified by some other out of band certificates so that they can be verified by some other out of band
means. means.
10. IANA Considerations 10. IANA Considerations
This specification defines two new event packages that IANA is This specification defines two new event packages that IANA is
requested to add the registry at: requested to add the registry at:
http://www.iana.org/assignments/sip-events http://www.iana.org/assignments/sip-events
It also defines a new mime type that IANA is requested to add to the
registry at:
http://www.iana.org/assignments/media-types/application
10.1. Certificate Event Package 10.1. Certificate Event Package
To: ietf-sip-events@iana.org To: ietf-sip-events@iana.org
Subject: Registration of new SIP event package Subject: Registration of new SIP event package
Package Name: certificate Package Name: certificate
Is this registration for a Template Package: No Is this registration for a Template Package: No
skipping to change at page 27, line 5 skipping to change at page 26, line 42
Package Name: credential Package Name: credential
Is this registration for a Template Package: No Is this registration for a Template Package: No
Published Specification(s): This document Published Specification(s): This document
Person & email address to contact for further information: Person & email address to contact for further information:
Cullen Jennings <fluffy@cisco.com> Cullen Jennings <fluffy@cisco.com>
10.3. PKCS#8
To: ietf-types@iana.org
Subject: Registration of MIME media type application/pkcs8
MIME media type name: application
MIME subtype name: pkcs8
Required parameters: None
Optional parameters: None
Encoding considerations: binary
Security considerations: Carries a cryptographic private key
Interoperability considerations:
The PKCS#8 object inside this MIME type MUST be DER-encoded
Published specification:
Kaliski, B., "Public-Key Cryptography Standards (PKCS) #8:
Private-Key Information Syntax Specification Version 1.2",
RFC 5208, May 2008.
Applications which use this media type: Any MIME-compliant transport
Additional information:
Magic number(s): None
File extension(s): .p8
Macintosh File Type Code(s): none
Person & email address to contact for further information:
Cullen Jennings <fluffy@cisco.com>
Intended usage: COMMON
Author/Change controller:
the IESG
11. Acknowledgments 11. Acknowledgments
Many thanks to Eric Rescorla, Jim Schaad, Rohan Mahy for significant Many thanks to Eric Rescorla, Jim Schaad, Rohan Mahy for significant
help and discussion. Many others provided useful comments, including help and discussion. Many others provided useful comments, including
Kumiko Ono, Peter Gutmann, Russ Housley, Yaron Pdut, Aki Niemi, Kumiko Ono, Peter Gutmann, Russ Housley, Yaron Pdut, Aki Niemi,
Magnus Nystrom, Paul Hoffman, Adina Simu, Dan Wing, Mike Hammer and Magnus Nystrom, Paul Hoffman, Adina Simu, Dan Wing, Mike Hammer, Pasi
Lyndsay Campbell. Rohan Mahy, John Elwell, and Jonathan Rosenberg Eronen, Alexey Melnikov, Tim Polk and Lyndsay Campbell. Rohan Mahy,
provided detailed review and text. John Elwell, and Jonathan Rosenberg provided detailed review and
text.
12. References 12. References
12.1. Normative References 12.1. Normative References
[RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part Two: Media Types", RFC 2046, Extensions (MIME) Part Two: Media Types", RFC 2046,
November 1996. November 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
skipping to change at page 29, line 11 skipping to change at page 28, line 8
(TLS) Protocol Version 1.2", RFC 5246, August 2008. (TLS) Protocol Version 1.2", RFC 5246, August 2008.
[RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., [RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S.,
Housley, R., and W. Polk, "Internet X.509 Public Key Housley, R., and W. Polk, "Internet X.509 Public Key
Infrastructure Certificate and Certificate Revocation List Infrastructure Certificate and Certificate Revocation List
(CRL) Profile", RFC 5280, May 2008. (CRL) Profile", RFC 5280, May 2008.
[RFC4086] Eastlake, D., Schiller, J., and S. Crocker, "Randomness [RFC4086] Eastlake, D., Schiller, J., and S. Crocker, "Randomness
Requirements for Security", BCP 106, RFC 4086, June 2005. Requirements for Security", BCP 106, RFC 4086, June 2005.
[RFC4366] Blake-Wilson, S., Nystrom, M., Hopwood, D., Mikkelsen, J.,
and T. Wright, "Transport Layer Security (TLS)
Extensions", RFC 4366, April 2006.
[I-D.turner-asymmetrickeyformat]
Turner, S., "Asymmetric Key Packages",
draft-turner-asymmetrickeyformat-03 (work in progress),
February 2010.
12.2. Informational References 12.2. Informational References
[RFC3760] Gustafson, D., Just, M., and M. Nystrom, "Securely [RFC3760] Gustafson, D., Just, M., and M. Nystrom, "Securely
Available Credentials (SACRED) - Credential Server Available Credentials (SACRED) - Credential Server
Framework", RFC 3760, April 2004. Framework", RFC 3760, April 2004.
[RFC3851] Ramsdell, B., "Secure/Multipurpose Internet Mail [RFC3851] Ramsdell, B., "Secure/Multipurpose Internet Mail
Extensions (S/MIME) Version 3.1 Message Specification", Extensions (S/MIME) Version 3.1 Message Specification",
RFC 3851, July 2004. RFC 3851, July 2004.
skipping to change at page 29, line 34 skipping to change at page 28, line 40
[RFC4662] Roach, A., Campbell, B., and J. Rosenberg, "A Session [RFC4662] Roach, A., Campbell, B., and J. Rosenberg, "A Session
Initiation Protocol (SIP) Event Notification Extension for Initiation Protocol (SIP) Event Notification Extension for
Resource Lists", RFC 4662, August 2006. Resource Lists", RFC 4662, August 2006.
Authors' Addresses Authors' Addresses
Cullen Jennings Cullen Jennings
Cisco Systems Cisco Systems
170 West Tasman Drive 170 West Tasman Drive
MS: SJC-21/2
San Jose, CA 95134 San Jose, CA 95134
USA USA
Phone: +1 408 421-9990 Phone: +1 408 421-9990
Email: fluffy@cisco.com Email: fluffy@cisco.com
Jason Fischl (editor) Jason Fischl (editor)
Skype Skype
2145 Hamilton Ave. 2145 Hamilton Ave.
San Jose, CA 95125 San Jose, CA 95125
USA USA
Phone: +1-415-202-5192 Phone: +1-415-202-5192
Email: jason.fischl@skype.net Email: jason.fischl@skype.net
 End of changes. 15 change blocks. 
109 lines changed or deleted 73 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/