< draft-rosenberg-sipping-gruu-reqs-00.txt   draft-rosenberg-sipping-gruu-reqs-01.txt >
SIP J. Rosenberg SIPPING J. Rosenberg
Internet-Draft dynamicsoft Internet-Draft dynamicsoft
Expires: January 27, 2004 July 29, 2003 Expires: April 19, 2004 October 20, 2003
Requirements for Construction and Usage of Globally Routable User Requirements for Construction and Usage of Globally Routable User
Agent (UA) URIs for the Session Initiation Protocol (SIP) Agent (UA) URIs for the Session Initiation Protocol (SIP)
draft-rosenberg-sipping-gruu-reqs-00 draft-rosenberg-sipping-gruu-reqs-01
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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 other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 1, line 31 skipping to change at page 1, line 31
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 http:// The list of current Internet-Drafts can be accessed at http://
www.ietf.org/ietf/1id-abstracts.txt. 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 January 27, 2004. This Internet-Draft will expire on April 19, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
Several applications of the Session Initiation Protocol (SIP) require Several applications of the Session Initiation Protocol (SIP) require
a user agent (UA) to construct and distribute a URI which can be used a user agent (UA) to construct and distribute a URI which can be used
by anyone on the Internet to route a call to that specific UA by anyone on the Internet to route a call to that specific UA
skipping to change at page 2, line 12 skipping to change at page 2, line 12
motivating use cases for GRUUs, and presents some requirements for motivating use cases for GRUUs, and presents some requirements for
their construction and usage. their construction and usage.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Defining a GRUU . . . . . . . . . . . . . . . . . . . . . . . 3 2. Defining a GRUU . . . . . . . . . . . . . . . . . . . . . . . 3
3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1 REFER . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1 REFER . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.2 Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.2 Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.3 Presence . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.3 Presence . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.4 An Alternative to Dialog Reuse . . . . . . . . . . . . . . . . 5 3.4 An Alternative to Dialog Reuse . . . . . . . . . . . . . . . . 5
4. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. Security Requirements . . . . . . . . . . . . . . . . . . . . 7 5. Security Requirements . . . . . . . . . . . . . . . . . . . . 7
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7
Informative References . . . . . . . . . . . . . . . . . . . . 7 Informative References . . . . . . . . . . . . . . . . . . . . 7
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 8
Intellectual Property and Copyright Statements . . . . . . . . 9 Intellectual Property and Copyright Statements . . . . . . . . 9
1. Introduction 1. Introduction
Several applications of the Session Initiation Protocol (SIP) [1] Several applications of the Session Initiation Protocol (SIP) [1]
require a user agent (UA) to construct and distribute a URI which can require a user agent (UA) to construct and distribute a URI which can
skipping to change at page 3, line 50 skipping to change at page 3, line 50
Instance Routing: It routes to a specific UA instance, and never Instance Routing: It routes to a specific UA instance, and never
forks. In that regard, it is unlike an address-of-record. When a forks. In that regard, it is unlike an address-of-record. When a
call is made to a normal AOR which represents a user, routing call is made to a normal AOR which represents a user, routing
logic is applied in proxies to deliver the call to one or more logic is applied in proxies to deliver the call to one or more
UAs. That logic can result in a different routing decision based UAs. That logic can result in a different routing decision based
on the time-of-day, or the identity of the caller. However, when a on the time-of-day, or the identity of the caller. However, when a
call is made to a GRUU, the routing logic is much more static. It call is made to a GRUU, the routing logic is much more static. It
has to cause the call to be delivered to a very specific UA has to cause the call to be delivered to a very specific UA
instance. That UA instance has to be the same UA instance instance. That UA instance has to be the same UA instance
throughout the lifetime of the GRUU. throughout the lifetime of the GRUU. This does not mean that a
GRUU represents a fundamentally different type of URI; it only
means that the logic a proxy applies to a GRUU is going to
generally be simpler than that it applies to a normal AOR.
3. Use Cases 3. Use Cases
We have encountered several use cases for a GRUU. We have encountered several use cases for a GRUU.
3.1 REFER 3.1 REFER
Consider a blind transfer application [6]. User A is talking to user Consider a blind transfer application [6]. User A is talking to user
B. A wants to transfer the call to user C. So, it sends a REFER to B. A wants to transfer the call to user C. So, it sends a REFER to
user C. That REFER looks like, in part: user C. That REFER looks like, in part:
 End of changes. 7 change blocks. 
7 lines changed or deleted 10 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/