[sipcore] #2: Editorial: section 2 is really confusing
"sipcore issue tracker" <trac@tools.ietf.org> Wed, 25 August 2010 23:03 UTC
Return-Path: <trac@tools.ietf.org>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 20F8A3A6A77 for <sipcore@core3.amsl.com>; Wed, 25 Aug 2010 16:03:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level:
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DOe+xmFLt+16 for <sipcore@core3.amsl.com>; Wed, 25 Aug 2010 16:03:07 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 417F83A6A64 for <sipcore@ietf.org>; Wed, 25 Aug 2010 16:03:07 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OoP0N-0004kJ-P2; Wed, 25 Aug 2010 16:03:39 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: sipcore issue tracker <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: hkaplan@acmepacket.com
X-Trac-Project: sipcore
Date: Wed, 25 Aug 2010 23:03:39 -0000
X-URL: http://tools.ietf.org/sipcore/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/sipcore/trac/ticket/2
Message-ID: <064.50eebc47edad8fd946968d68bac122e0@tools.ietf.org>
X-Trac-Ticket-ID: 2
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: hkaplan@acmepacket.com, sipcore@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: sipcore@ietf.org
Subject: [sipcore] #2: Editorial: section 2 is really confusing
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Aug 2010 23:03:08 -0000
#2: Editorial: section 2 is really confusing ------------------------------------+--------------------------------------- Reporter: hkaplan@… | Owner: Type: defect | Status: new Priority: minor | Milestone: milestone1 Component: rfc4244bis | Version: 2.0 Severity: In WG Last Call | Keywords: ------------------------------------+--------------------------------------- Section 2 "Conventions and terminology" defines two terms: "retarget" and "forward". I can't make heads or tales about what they mean from this text, or how they're different. I went back and read the original RFC 4424, and in there it was somewhat clearer (section 1.3 and 3 of rfc4424). Currently 4424bis says this: The term "retarget" is used in this document to refer both to the process of a Proxy Server/User Agent Client (UAC) changing a Uniform Resource Identifier (URI) in a request based on the rules for determining request targets as described in Section 16.5 of [RFC3261] and the subsequent forwarding of that request as described in section 16.6 of [RFC3261]. I *think* what you mean is this: The term "retarget" is used in this document to refer to the process of a Proxy Server/User Agent Client (UAC) changing the Request-URI of a request, based on the rules for determining request targets as described in Section 16.5 of [RFC3261] and step-2 of the subsequent forwarding of that request as described in section 16.6 of [RFC3261]. This includes changing the Request-URI due to a location service lookup and 3xx redirect processing, 4424bis then says this about forwarding: The term "forward" is used consistent with the terminology in [RFC3261]. Noting that [RFC3261] uses the term "forwarding" to describe a proxy's handling of requests for domains for which is not responsible, as well as to describe the basic "forwarding" of a request (in section 16.6) once a target has been determined. However, the context of the usage is sufficient to differentiate the slightly different meanings. This is super-confusing, and not what you meant I think. At least not the "describe a proxy's handling of requests for domains for which is not responsible" piece. The real ambiguity of the term "forward" in 3261 is that it's used both for request routing procedures and for "call forwarding" to a new user/identity. Is that what you mean? What this 4424bis draft does not have a term for is for when the request gets retargeted to a new identity - *that* has been described in previous drafts and emails as "retargeting", whereas "rerouting" or "contact routing" was changing the req-URI but not the identity. I suggest you use the word "divert" for changing the identity, since "retarget" and "redirect" are ambiguous. -- Ticket URL: <http://trac.tools.ietf.org/wg/sipcore/trac/ticket/2> sipcore <http://tools.ietf.org/sipcore/>
- [sipcore] #2: Editorial: section 2 is really conf… sipcore issue tracker
- Re: [sipcore] #2: Editorial: section 2 is really … Mary Barnes
- Re: [sipcore] #2: Editorial: section 2 is really … Hadriel Kaplan
- Re: [sipcore] #2: Editorial: section 2 is really … Mary Barnes
- Re: [sipcore] #2: Editorial: section 2 is really … Worley, Dale R (Dale)
- Re: [sipcore] #2: Editorial: section 2 is really … Mary Barnes
- Re: [sipcore] #2: Editorial: section 2 is really … Worley, Dale R (Dale)
- Re: [sipcore] #2: Editorial: section 2 is really … Mary Barnes
- Re: [sipcore] #2: Editorial: section 2 is really … Hadriel Kaplan
- Re: [sipcore] #2: Editorial: section 2 is really … DRAGE, Keith (Keith)
- Re: [sipcore] #2: Editorial: section 2 is really … Hadriel Kaplan
- Re: [sipcore] #2: Editorial: section 2 is really … Mary Barnes
- Re: [sipcore] #2: Editorial: section 2 is really … Worley, Dale R (Dale)
- Re: [sipcore] #2: Editorial: section 2 is really … Hadriel Kaplan
- Re: [sipcore] #2: Editorial: section 2 is really … Worley, Dale R (Dale)
- Re: [sipcore] #2: Editorial: section 2 is really … Hadriel Kaplan
- Re: [sipcore] #2: Editorial: section 2 is really … Worley, Dale R (Dale)
- Re: [sipcore] #2: Editorial: section 2 is really … Hadriel Kaplan
- Re: [sipcore] #2: Editorial: section 2 is really … DRAGE, Keith (Keith)
- Re: [sipcore] #2: Editorial: section 2 is really … marianne.mohali