IETF Logo Mail Archive

Re: [Sip] draft-ietf-sip-sips-03.txt: Closing of Opened issues

jh@tutpro.com (Juha Heinanen) Thu, 26 April 2007 08:02 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 1Hgyvx-0002jC-Jb; Thu, 26 Apr 2007 04:02:33 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Hgyvw-0002j0-85 for sip-confirm+ok@megatron.ietf.org; Thu, 26 Apr 2007 04:02:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hgyvu-0002in-Sj for sip@ietf.org; Thu, 26 Apr 2007 04:02:31 -0400
Received: from lohi.tutpro.com ([192.98.100.2] helo=tutpro.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hgyvt-0002Tx-GN for sip@ietf.org; Thu, 26 Apr 2007 04:02:30 -0400
Received: from localhost (localhost [127.0.0.1]) by tutpro.com (Postfix) with ESMTP id C473E1EC02E; Thu, 26 Apr 2007 11:02:28 +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 sLKrGY5jlvAx; Thu, 26 Apr 2007 11:02:26 +0300 (EEST)
Received: from taimen (primer189.gprs.dnafinland.fi [62.78.125.189]) by tutpro.com (Postfix) with ESMTP; Thu, 26 Apr 2007 11:02:26 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000) id 6CC69AC122; Thu, 26 Apr 2007 11:02:20 +0300 (EEST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <17968.23692.411137.362017@tutpro.com>
Date: Thu, 26 Apr 2007 11:02:20 +0300
To: Thomas Froment <Thomas.Froment@alcatel-lucent.fr>
Subject: Re: [Sip] draft-ietf-sip-sips-03.txt: Closing of Opened issues
In-Reply-To: <46305AE8.6040405@alcatel-lucent.fr>
References: <1ECE0EB50388174790F9694F77522CCF100DE550@zrc2hxm0.corp.nortel.com> <70B32427-9693-4423-AB86-7C926A479F85@cisco.com> <1ECE0EB50388174790F9694F77522CCF1028B59B@zrc2hxm0.corp.nortel.com> <462F613C.2050502@sipstation.com> <1ECE0EB50388174790F9694F77522CCF10329CA3@zrc2hxm0.corp.nortel.com> <17968.16340.800200.535818@tutpro.com> <46305AE8.6040405@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: 7d33c50f3756db14428398e2bdedd581
Cc: "Peterson, Jon" <jon.peterson@neustar.biz>, sip@ietf.org, Francois Audet <audet@nortel.com>, Keith Drage <drage@alcatel-lucent.com>, Dean Willis <dean.willis@softarmor.com>, Alan Johnston <alan@sipstation.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:

 > Yes, actually, on my side, I did not answer your last remark because I 
 > think this is NOT related to "double RR" versus "R-R rewriting" question.
 > You can choose to either double R-R or rewrite, but the question you are 
 > raising is: are you allowed to continue to use "transport=TLS" or not,
 > this more a question related to sip/sips clarification: currently this 
 > is clearly stated in sip/sips that TLS transport parameter should not be 
 > used...

thomas,

yes, i understood that this is not a your problem.  that is why i now
posted the question explicitly to author of sips i-d.  if sips i-d tells
in the case of my example to upgrade sip: to sips: there is a BIG bug in
it.  

for some reason this issue was missing from the issues list that the
author of sips i-d just posted.

-- 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

v2.23.0 | Report a Bug | By Email