IETF Logo Mail Archive

RE: [Sip] B2BUA - Security

"Christian Huitema" <huitema@windows.microsoft.com> Thu, 05 December 2002 17:53 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21382 for <sip-archive@odin.ietf.org>; Thu, 5 Dec 2002 12:53:57 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gB5HuKd10023 for sip-archive@odin.ietf.org; Thu, 5 Dec 2002 12:56:20 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB5Htpv09975; Thu, 5 Dec 2002 12:55:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB5Hrov09905 for <sip@optimus.ietf.org>; Thu, 5 Dec 2002 12:53:50 -0500
Received: from mail4.microsoft.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21294 for <sip@ietf.org>; Thu, 5 Dec 2002 12:50:56 -0500 (EST)
Received: from mail6.microsoft.com ([157.54.6.196]) by mail4.microsoft.com with Microsoft SMTPSVC(5.0.2195.5600); Thu, 5 Dec 2002 09:53:45 -0800
Received: from inet-vrs-06.redmond.corp.microsoft.com ([157.54.6.181]) by mail6.microsoft.com with Microsoft SMTPSVC(5.0.2195.5600); Thu, 5 Dec 2002 09:53:40 -0800
Received: from 157.54.8.109 by inet-vrs-06.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 05 Dec 2002 09:53:41 -0800
Received: from RED-IMC-02.redmond.corp.microsoft.com ([157.54.9.107]) by INET-HUB-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3710.0); Thu, 5 Dec 2002 09:53:50 -0800
Received: from WIN-IMC-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.84]) by RED-IMC-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.5600); Thu, 5 Dec 2002 09:53:40 -0800
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.82]) by WIN-IMC-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3710.0); Thu, 5 Dec 2002 09:53:36 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: RE: [Sip] B2BUA - Security
Date: Thu, 05 Dec 2002 09:53:39 -0800
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA1D2A61@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: [Sip] B2BUA - Security
Thread-Index: AcKcgcgb36brIS1YSPaEIfsetm8rJAABH/Pg
From: Christian Huitema <huitema@windows.microsoft.com>
To: "Mahey, Sonit" <Sonit.Mahey@icn.siemens.com>, Jonathan Rosenberg <jdrosen@dynamicsoft.com>, Pete Cordell <pete@tech-know-ware.com>
Cc: sip@ietf.org
X-OriginalArrivalTime: 05 Dec 2002 17:53:36.0661 (UTC) FILETIME=[3C566C50:01C29C87]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gB5Hrov09906
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
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>
Content-Transfer-Encoding: 8bit

> From: Mahey, Sonit [mailto:Sonit.Mahey@icn.siemens.com]
> Sent: Thursday, December 05, 2002 9:14 AM
>
> I agree with Jonathan.
> 
> That brings up the question:
> Is NAT traversal for encrypted SIP traffic addressed anywhere?

There are two possibilities. If your application only uses UDP, it is
possible to use IPv4 and STUN to find out the "outside ports" for your
UDP traffic (check draft-ietf-midcom-stun-03.txt); you may need to use
the "a:rtcp" convention to encode port numbers in SDP (check
draft-ietf-mmusic-sdp4nat-03.txt). If you need to also support TCP, or
use IPSEC, or generally do away with the complications of NAT, the best
solution is to just move to IPv6; see Teredo
(draft-ietf-ngtrans-shipworm-08.txt) for one possible way to carry IPv6
across NAT, and 6to4 (RFC 3056 & 3068) for a possible way to upgrade the
NAT and make it an IPv6 router.

-- Christian Huitema
_______________________________________________
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