RE: [AVT] Re: RTP/RTCP Port Sharing -> SCTP

"Christian Huitema" <huitema@windows.microsoft.com> Mon, 23 July 2001 16:43 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA05268; Mon, 23 Jul 2001 12:43:54 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA05270; Mon, 23 Jul 2001 12:42:08 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA05231 for <avt@ns.ietf.org>; Mon, 23 Jul 2001 12:41:55 -0400 (EDT)
Received: from mail2.microsoft.com (mail2.microsoft.com [131.107.3.124]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA05067 for <avt@ietf.org>; Mon, 23 Jul 2001 12:40:57 -0400 (EDT)
Received: from 157.54.9.100 by mail2.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 23 Jul 2001 09:37:10 -0700 (Pacific Daylight Time)
Received: from red-imc-01.redmond.corp.microsoft.com ([157.54.9.102]) by inet-imc-03.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966); Mon, 23 Jul 2001 09:36:51 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.82]) by red-imc-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966); Mon, 23 Jul 2001 09:36:51 -0700
Received: from win-msg-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.134]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966); Mon, 23 Jul 2001 09:35:43 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.5683.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: RE: [AVT] Re: RTP/RTCP Port Sharing -> SCTP
Date: Mon, 23 Jul 2001 09:35:43 -0700
Message-ID: <F66A04C29AD9034A8205949AD0C90104A3E602@win-msg-02.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: [AVT] Re: RTP/RTCP Port Sharing -> SCTP
Thread-Index: AcESB2Z1wR3wl/ZYQECfpBseOBu2EwBjfX5A
From: Christian Huitema <huitema@windows.microsoft.com>
To: "Henning G. Schulzrinne" <hgs@cs.columbia.edu>, Michael Thomas <mat@cisco.com>
Cc: Jonathan Rosenberg <jdrosen@dynamicsoft.com>, "Fairlie-Cuninghame, Robert" <rfairlie@nuera.com>, Leonid Rosenboim <Leonid@BitBand.COM>, Ross Finlayson <finlayson@live.com>, avt@ietf.org
X-OriginalArrivalTime: 23 Jul 2001 16:35:43.0638 (UTC) FILETIME=[8474B360:01C11395]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id MAA05239
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
X-BeenThere: avt@ietf.org
Content-Transfer-Encoding: 8bit

Henning,

The NGTRANS group is working on the issue of IPv6 behind NAT. I recently
submitted a draft (draft-huitema-shipworm-00.txt) that proposes a
solution for getting IPv6 addresses from behind a NAT. This is a rough
first draft, that will be discussed in the NGTRANS group, and that will
certainly have to be perfected. However, it provides a credible solution
for making IPv6 available everywhere.

-- Christian Huitema

> -----Original Message-----
> From: Henning G. Schulzrinne [mailto:hgs@cs.columbia.edu]
> Sent: Saturday, July 21, 2001 9:53 AM
> To: Michael Thomas
> Cc: Jonathan Rosenberg; Fairlie-Cuninghame, Robert; 'Leonid
> Rosenboim'; Ross Finlayson; avt@ietf.org
> Subject: Re: [AVT] Re: RTP/RTCP Port Sharing -> SCTP
> 
> Michael Thomas wrote:
> >
> > Jonathan Rosenberg writes:
> >  > Then you read draft-rosenberg-sip-entfw-02.txt, due out this
> week, which
> >  > explains how to handle this case.... :) The mechanism in there
> uses
> >  > bidirectional streams (which we call symmetric) whenever only one
> side its
> >  > natted, and otherwise uses a network intermediary outside of the
> firewall
> >  > when both are behind nats that don't support Christian's
> >  > http://search.ietf.org/internet-drafts/draft-huitema-natreq4udp-
> 00.txt. When
> >  > contacting this network intermediary, its still useful to use
> symmetric RTP.
> >
> >    Sigh. If the end result of most media sessions is a rendezvous
> >    to a intermediary, then our bragging rights over the IN will
> >    be nullified. I know that this is the implication of NAT's, but
> >    it still depresses me.
> 
> It would be nice if all the effort expended on fixing the NAT stuff
> would be matched by people deploying IPv6 applications (enabling IPv6
> on
> recent Solaris and Linux boxes, as well as routers, seems pretty
> trivial, from our experience) or dispelling the notion that you can't
> get addresses, which seems to often be perpetuated by people who have
> other agendas (such as making it difficult to use more than one
> computer
> on a home DSL/cable modem).
> 
> That said, I wonder if it wouldn't be easier to just have the client
> set
> up one secure tunnel to this outside entity with a real IP address,
> for
> all applications that are stymied by NATs, rather than inventing a new
> mechanism for each application. This does mean two relaying points,
> but
> avoids all the negotiation and myriad special cases. Can this be done
> with the typical VPN setups in some of the more recent OSs?
> 
> --
> Henning Schulzrinne   http://www.cs.columbia.edu/~hgs
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> http://www.ietf.org/mailman/listinfo/avt

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
http://www.ietf.org/mailman/listinfo/avt