Re: [sipcore] #2: Editorial: section 2 is really confusing

I prefer not to use the term "diversion" because there is a well defined set of ISDN diversion services, and while the use of History-Info does encompass equivalents of such services, it encompasses much more. 

Changing the target to a new Request-URI may encompass diversion (in the ISDN sense), but it could also encompass a number of other cases, including freephone and number portability.

regards

Keith

> -----Original Message-----
> From: sipcore-bounces@ietf.org 
> [mailto:sipcore-bounces@ietf.org] On Behalf Of Worley, Dale R (Dale)
> Sent: Tuesday, August 31, 2010 4:34 PM
> To: Hadriel Kaplan; Mary Barnes
> Cc: sipcore@ietf.org
> Subject: Re: [sipcore] #2: Editorial: section 2 is really confusing
> 
> ________________________________________
> From: sipcore-bounces@ietf.org [sipcore-bounces@ietf.org] On 
> Behalf Of Hadriel Kaplan [HKaplan@acmepacket.com]
> 
> Do you not want to use the term "Divert" because of the 
> Diversion header?
> 
> I think it's the only term left that isn't ambiguous... 
> "retarget" is being used for any/all cases of changing the 
> request-uri, and "forward" is used for generic message 
> routing procedures, and "redirect" is used for 3xx cases.  So 
> there isn't a term left I can think of that means "changing 
> the target to a new user/identity" (i.e., "call forwarding" 
> in the PSTN).
> 
> And really the draft would be clearer if there was a unique 
> term for that, because a lot of use-cses depend on it: 
> finding the previous or current diverted-to party.
> ______________________________________________
> 
> People use these various terms freely, but in reality, none 
> of them are well-defined and people don't use the same 
> definition for each term.  The current doc carries forward 
> this confusion by deferring the meanings to previous 
> documents.  The only useful way to deal with the situation is 
> to define the terms we want to use ab initio in this document.
> 
> Dale
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
> 