Responses below [MB]. ________________________________
From: Christer Holmberg [mailto:[email protected]] Sent: Thursday, March 12, 2009 1:18 PM To: Barnes, Mary (RICH2:AR00); Hans Erik van Elburg Cc: [email protected]; Elwell, John Subject: RE: [Sip] Terminology (was RE: Fwd:I-DACTION:draft-rosenberg-sip-target-uri-delivery-01.txt Hi Mary, A couple of question: 1. Does the 4244bis definition of "retarget" cover the freephone case, when the R-URI is replaced with the AoR of B - not with the contact of B - no matter whether it's done based on location service, configuration or whatever? [MB] That was the intention, however, the current text needs to be made more general (i.e., I was using location service to mean more than registration based contacts - another thing that's not quite so clear in 3261). [/MB] 2. Related to the first question, when you say "...and thus chaning the target of the request", what is the defintion of "target"? [MB] The definition of target matches that used in section 16.5 of 3261. A target is an entry in the target list, which is populated using information from a location service, configuration, etc. I can clarify that as well and as you previously suggested make a more comprehensive glossary in the more conventional format - e.g., "Target: definition text, blah, blah, blah...] So, I believe it is the same use of target as in the target-uri draft. [/MB] Regards, Christer ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Mary Barnes Sent: Thursday, March 12, 2009 5:20 PM To: Hans Erik van Elburg Cc: [email protected]; Elwell, John Subject: Re: [Sip] Terminology (was RE: Fwd:I-DACTION:draft-rosenberg-sip-target-uri-delivery-01.txt When I use "retarget" I am using the definition that I put into 4244bis. So, if you could ignore the tag or change it to 'iscontact' or whatever, what would you change in that definition? Also, consider that if you were to change everyplace that I use "retarget"/"retargeted"/"retargeting" in 4244bis with 'iscontact' the text would not make sense. So, even if we change the name of the tag, we still need to understand the concept or define another term that means that the request-uri in the incoming request (which should be the same as the last hi-entry in the request) is being chnaged due to service lookup, configuration, blah, blah, blah and that to meet the requirements in the target-uri document, we want to tag this entry so that this request-uri is not "lost" - i.e., this is the one the services identified in the target-uri document care about. So, right now, here's what's in 4244bis: The term "retarget" is used in this document to refer to the process of a Proxy Server/User Agent Client (UAC) changing a Uniform Resource Identifier (URI) in a request based on a lookup in a location service and thus changing the target of the request. We have previously discussed that we do need to expand the "based on a lookup in a location service" to include configuration, etc., so let's not debate that. But, what explicitly is the concern with that definition? Mary. ________________________________ From: Hans Erik van Elburg [mailto:[email protected]] Sent: Thursday, March 12, 2009 9:55 AM To: Barnes, Mary (RICH2:AR00) Cc: Elwell, John; [email protected] Subject: Re: [Sip] Terminology (was RE: Fwd: I-DACTION:draft-rosenberg-sip-target-uri-delivery-01.txt I'm fine with discussing implementation if everyone is meaning the same if they use the same words. As to the "retarget" term such does not seem to be the case. /Hans Erik van Elburg _______________________________________________ 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
