Re: [Sip] Process question on fixing record-route
jh@tutpro.com (Juha Heinanen) Tue, 24 April 2007 14:25 UTC
Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HgLxQ-0002c2-Fp; Tue, 24 Apr 2007 10:25:28 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1HgLxO-0002bq-RN for sip-confirm+ok@megatron.ietf.org; Tue, 24 Apr 2007 10:25:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HgLxO-0002bi-Hr for sip@ietf.org; Tue, 24 Apr 2007 10:25:26 -0400
Received: from lohi.tutpro.com ([192.98.100.2] helo=tutpro.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HgLxN-0006HE-6F for sip@ietf.org; Tue, 24 Apr 2007 10:25:26 -0400
Received: from localhost (localhost [127.0.0.1]) by tutpro.com (Postfix) with ESMTP id EBBCE1EC02E; Tue, 24 Apr 2007 17:25:14 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1]) by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lUEwspe5QmD0; Tue, 24 Apr 2007 17:25:13 +0300 (EEST)
Received: from taimen (in-vitro91.gprs.dnafinland.fi [62.78.121.91]) by tutpro.com (Postfix) with ESMTP; Tue, 24 Apr 2007 17:25:13 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000) id 5C122AC120; Tue, 24 Apr 2007 17:25:05 +0300 (EEST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <17966.4929.346525.230253@tutpro.com>
Date: Tue, 24 Apr 2007 17:25:05 +0300
To: Thomas Froment <Thomas.Froment@alcatel-lucent.fr>
Subject: Re: [Sip] Process question on fixing record-route
In-Reply-To: <462DC358.4000002@alcatel-lucent.fr>
References: <E79EA28D-BBB2-4218-A89F-65A909DAE882@softarmor.com> <462DC358.4000002@alcatel-lucent.fr>
X-Mailer: VM 7.19 under Emacs 21.4.1
From: jh@tutpro.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: IETF SIP List <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org
Thomas Froment writes: > 1) Do we want to *deprecate* record-route rewriting or just recommend > double R-R but let R-R rewriting as a valid alternative? can you clarify what you mean by r-r rewriting? if i recall correctly, according to rfc 3261 r-r headers are added during dialog initiating request and after that route set does not change, i.e., proxies only need to r-r initial request. > The URI > SHOULD NOT contain the transport parameter unless the proxy has > knowledge(such as in a private network) that the next downstream element > that will be in the path of subsequent requests supports that > transport". my proxy may be talking to a proxy of another organization using tls no matter if uri scheme in requests is sip or sips. if request comes in over udp and goes out over tls, should my proxy double r-r and add transport=tls or what? -- juha _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
- [Sip] Process question on fixing record-route Dean Willis
- Re: [Sip] Process question on fixing record-route Robert Sparks
- Re: [Sip] Process question on fixing record-route Dean Willis
- Re: [Sip] Process question on fixing record-route Robert Sparks
- Re: [Sip] Process question on fixing record-route Thomas Froment
- Re: [Sip] Process question on fixing record-route Juha Heinanen
- Re: [Sip] Process question on fixing record-route Thomas Froment
- Re: [Sip] Process question on fixing record-route Juha Heinanen
- Re: [Sip] Process question on fixing record-route Thomas Froment
- Re: [Sip] Process question on fixing record-route Juha Heinanen