No, I think we'd need to allow for configuration to be a valid use case for addition of the target parameter as well. Shida makes a fine point and there is no reason to exclude it.

-Jonathan R.

DRAGE, Keith (Keith) wrote:
I believe the 800 use case is still a valid problem that has to be
solved.

Do we have another way of using History-Info that would cover this
specific case. For example, do we just need an extension to the
Voicemail URI RFC?

regards

Keith
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Rosenberg
Sent: Friday, November 14, 2008 10:27 PM
To: Shida Schubert
Cc: [email protected] List
Subject: Re: [Sip] I-D Action:draft-rosenberg-sip-target-uri-delivery-00.txt

Actually I removed the 800 use case because it doesn't work so well with the proposed mechanism. The reason is that, this draft is very crisp about how you determine if a URI is a 'target' or not - based on a REGISTRATION. However, for 8xx numbers, my assumption is that they would typically be translated to a non-8xx number by some other configured translation on the server, not via a registration.

For example, a server might have a config like this:

1-800-555-1212:
   replace with: [EMAIL PROTECTED]

and then individual UAs register as 'directory'.

In reality this was a problem in the UA loose route draft too; its really hard to programatically determine that something is a target vs. not a target.

-Jonathan R.


Shida Schubert wrote:
Jonathan;

 Thanks for writing up the draft.

There was a use-case for freephone number mentioned in
section 2.7 of
loose-route draft which no longer exists in this draft.

I do recall that in section 2.7 of loose-route you expressed that freephone number is just another form of alias, so I am
assuming that
is the reason you removed the text OR was there any
technical reason
why you removed the use-case?

If there is no technical reason behind removing the text,
could you
add its use for freephone number as a use-case either as a separate sub-section or as part of alias use-case..

 Thanks & Regards
  Shida

On 27-Oct-08, at 1:30 PM, [EMAIL PROTECTED] wrote:

A New Internet-Draft is available from the on-line Internet-Drafts directories.

Title : Delivery of Request-URI Targets to
User Agents
    Author(s)       : J. Rosenberg
Filename :
draft-rosenberg-sip-target-uri-delivery-00.txt
    Pages           : 12
    Date            : 2008-10-26

When a Session Initiation Protocol (SIP) proxy receives a request targeted at a URI identifying a user or resource it is responsible for, the proxy translates the URI to a registered contact
URI of an
agent representing that user or resource. In the process, the original URI is removed from the request. Numerous use cases have arisen which require this information to be delivered to the user agent. This document describes these use cases and defines an extension to the History-Info header field which allows it
to be used
to support those cases.

A URL for this Internet-Draft is:

http://www.ietf.org/internet-drafts/draft-rosenberg-sip-target-uri-de
livery-00.txt


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.
<mime-attachment>_______________________________________________
I-D-Announce mailing list
[EMAIL PROTECTED]
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

--
Jonathan D. Rosenberg, Ph.D.                   111 Wood Avenue South
Cisco Fellow                                   Iselin, NJ 08830
Cisco, Voice Technology Group
[EMAIL PROTECTED]
http://www.jdrosen.net                         PHONE: (408) 902-3084
http://www.cisco.com
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip



--
Jonathan D. Rosenberg, Ph.D.                   111 Wood Avenue South
Cisco Fellow                                   Iselin, NJ 08830
Cisco, Voice Technology Group
[EMAIL PROTECTED]
http://www.jdrosen.net                         PHONE: (408) 902-3084
http://www.cisco.com
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip

Reply via email to