< draft-channabasappa-sipping-app-profile-type-02.txt   draft-channabasappa-sipping-app-profile-type-03.txt >
SIPPING Working Group S. Channabasappa SIPPING Working Group M. Dolly
Internet-Draft CableLabs Internet-Draft AT&T
Intended status: Standards Track J. Littlefield Intended status: Standards Track S. Channabasappa
Expires: August 24, 2008 Cisco Systems, Inc. Expires: May 7, 2009 CableLabs
J. Littlefield
Cisco Systems, Inc.
S. Loreto S. Loreto
Ericsson, Inc. Ericsson
February 21, 2008 November 3, 2008
Extension to the ua-profile Event Package to Support the Application Extension to the ua-profile Event Package to Support the Application
Profile Type Profile Type
draft-channabasappa-sipping-app-profile-type-02 draft-channabasappa-sipping-app-profile-type-03
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 38 skipping to change at page 1, line 40
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 August 24, 2008. This Internet-Draft will expire on May 7, 2009.
Copyright Notice
Copyright (C) The IETF Trust (2008).
Abstract Abstract
The Framework for Session Initiation Protocol User Agent Profile The Framework for Session Initiation Protocol User Agent Profile
Delivery specifies an event package (ua-profile) that can be used by Delivery specifies an event package (ua-profile) that can be used by
user agents to retrieve profile data. The framework also allows for user agents to retrieve profile data. The framework also allows for
optional notification of changes to the retrieved profiles. Three optional notification of changes to the retrieved profiles. Three
profile types are specified: local-network, device, and user. This profile types are specified: local-network, device, and user. This
document extends that event package to support an additional profile document extends that event package to support an additional profile
type, application. This would enable User Agents to retrieve profile type, application. This would enable User Agents to retrieve profile
skipping to change at page 9, line 26 skipping to change at page 9, line 26
[RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
"Uniform Resource Names (URN) Namespace Definition "Uniform Resource Names (URN) Namespace Definition
Mechanisms", BCP 66, RFC 3406, October 2002. Mechanisms", BCP 66, RFC 3406, October 2002.
[RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and [RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and
Registration Procedures for New URI Schemes", BCP 115, Registration Procedures for New URI Schemes", BCP 115,
RFC 4395, February 2006. RFC 4395, February 2006.
Authors' Addresses Authors' Addresses
Martin Dolly
AT&T
200 Laurel Ave
Middletown, NJ,
US
Phone:
Email: mdolly@att.com
Sumanth Channabasappa Sumanth Channabasappa
CableLabs CableLabs
858 Coal Creek Circle 858 Coal Creek Circle
Louisville, Co 80027 Louisville, Co 80027
USA USA
Email: sumanth@cablelabs.com Email: sumanth@cablelabs.com
URI: http://www.cablelabs.com/ URI: http://www.cablelabs.com/
Josh Littlefield Josh Littlefield
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Avenue 1414 Massachusetts Avenue
Boxborough, MA 01719 Boxborough, MA 01719
USA USA
Email: joshl@cisco.com Email: joshl@cisco.com
URI: http://www.cisco.com/ URI: http://www.cisco.com/
Salvatore Loreto Salvatore Loreto
Ericsson, Inc. Ericsson
Hirsalantie 11 Hirsalantie 11
Jorvas, 02420 Jorvas, 02420
Finland Finland
Email: Salvatore.Loreto@ericsson.com Email: Salvatore.Loreto@ericsson.com
URI: http://www.ericsson.com/ URI: http://www.ericsson.com/
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
skipping to change at page 11, line 44 skipping to change at line 432
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 9 change blocks. 
14 lines changed or deleted 21 lines changed or added

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