IETF Logo Mail Archive

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

"Francois Audet" <audet@nortel.com> Thu, 26 April 2007 21:29 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 1HhBWU-0001l8-1h; Thu, 26 Apr 2007 17:29:06 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1HhBWS-0001jZ-Jq for sip-confirm+ok@megatron.ietf.org; Thu, 26 Apr 2007 17:29:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HhBWS-0001jR-AL for sip@ietf.org; Thu, 26 Apr 2007 17:29:04 -0400
Received: from zrtps0kn.nortel.com ([47.140.192.55]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HhBWR-0001uv-2Z for sip@ietf.org; Thu, 26 Apr 2007 17:29:04 -0400
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id l3QLT0Q00359; Thu, 26 Apr 2007 21:29:00 GMT
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] draft-ietf-sip-sips-03.txt: Closing of Opened issues
Date: Thu, 26 Apr 2007 16:28:49 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF1032AAEF@zrc2hxm0.corp.nortel.com>
In-Reply-To: <05650EF6-4740-4F00-97AF-AA180402AC1E@softarmor.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] draft-ietf-sip-sips-03.txt: Closing of Opened issues
Thread-Index: AceIRzqoq2B7P2L0SuCNVDIPe6M6VgAAJr0g
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> <1ECE0EB50388174790F9694F77522CCF1032A3C9@zrc2hxm0.corp.nortel.com> <17968.58739.220882.733487@tutpro.com> <1ECE0EB50388174790F9694F77522CCF1032A6D8@zrc2hxm0.corp.nortel.com> <17968.61648.893419.784702@tutpro.com> <05650EF6-4740-4F00-97AF-AA180402AC1E@softarmor.com>
From: Francois Audet <audet@nortel.com>
To: Dean Willis <dean.willis@softarmor.com>, Juha Heinanen <jh@tutpro.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: sip@ietf.org
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

 
> > tell me, why is tls (instead of tcp) needed in via when uri 
> scheme is 
> > sips?  cannot tls/tcp be concluded if transport is tcp and 
> uri scheme 
> > is sips.
> 
> I've always wondered about this one myself. What about 
> TLS/SCTP and DTLS, which might serve as transports for SIPS?

VIA already supports SCTP, TLS-SCTP. And the draft provides the 
references to RFC 4168 that defines it.

DTLS is defined in
http://tools.ietf.org/wg/sip/draft-jennings-sip-dtls-03.txt.

On the question of "why we are using VIA in the first place?" instead or
replying to where the request came from, well, I don't know. It wasn't
me
who wrote RFC 3261. This is a widely known characteristic described
in RFC 3581.

It's completely out of scope of this draft. 






_______________________________________________
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