[AVT] RE: [BEHAVE] [Fwd: Last Call:draft-wing-behave-symmetric-rtprtcp(Common Local Transmit andReceive Ports (Symmetric RTP)) toInformational RFC]

"Dan Wing" <dwing@cisco.com> Tue, 13 February 2007 21:26 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HH5Ac-0005UA-DX; Tue, 13 Feb 2007 16:26:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HH5Aa-0005Tj-FQ; Tue, 13 Feb 2007 16:26:36 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HH5AU-0006gF-QD; Tue, 13 Feb 2007 16:26:36 -0500
Received: from sj-dkim-8.cisco.com ([171.68.10.93]) by sj-iport-4.cisco.com with ESMTP; 13 Feb 2007 13:26:30 -0800
X-IronPort-AV: i="4.14,164,1170662400"; d="scan'208"; a="39283429:sNHT147035007"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-8.cisco.com (8.12.11/8.12.11) with ESMTP id l1DLQUWP022987; Tue, 13 Feb 2007 13:26:30 -0800
Received: from dwingwxp ([10.32.240.194]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l1DLQNho000703; Tue, 13 Feb 2007 13:26:23 -0800 (PST)
From: Dan Wing <dwing@cisco.com>
To: 'David Barrett' <dbarrett@quinthar.com>, 'Magnus Westerlund' <magnus.westerlund@ericsson.com>
Date: Tue, 13 Feb 2007 13:26:22 -0800
Message-ID: <0a3401c74fb5$a01f9e10$c2f0200a@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: <07fa01c74fb1$2fc20a80$6b02a8c0@Quinthar>
Thread-Index: AcdPrEX0YWQ8YVSgQSOznluD8gQH6wAAUhWgAAC0ykAAASKhMA==
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7399; t=1171401990; x=1172265990; c=relaxed/simple; s=sjdkim8002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dwing@cisco.com; z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com> |Subject:=20RE=3A=20[BEHAVE]=20[Fwd=3A=20Last=20Call=3Adraft-wing-behave- symmetric-rtprtcp(Common=20Local=20Transmit=20andReceive=20Ports=20(Symmet ric=20RTP))=20toInformational=20RFC] |Sender:=20; bh=zMaMynsO7amXjWUWyjBctdM3QIryeiiK3V6jH3HU1es=; b=Yo5B1ddiyOpS6nBUkjtjkh3UUEF6fdC3RANFlgmQdP35Aja6SjB6goE0oVmSicb2ZcLdfEnC FcTjTwv7uD2A07KcKYbdnI+IibHVfuLc14t1TkE1pJUUt89Tl76ilRxh;
Authentication-Results: sj-dkim-8; header.From=dwing@cisco.com; dkim=pass (s ig from cisco.com/sjdkim8002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d008c19e97860b8641c1851f84665a75
Cc: behave@ietf.org, 'IETF AVT WG' <avt@ietf.org>
Subject: [AVT] RE: [BEHAVE] [Fwd: Last Call:draft-wing-behave-symmetric-rtprtcp(Common Local Transmit andReceive Ports (Symmetric RTP)) toInformational RFC]
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Some NATs will close down NAT bindings after some number of seconds if there
is only outside->inside traffic and no inside->outside traffic on that same
5-tuple.  If you were to encounter such a NAT with the optimization you
describe below, the RTP traffic from the TURN server would stop after
awhile.  I suppose you could work around that NAT behavior, and still do
this optimization technique, if you were to send some sort of outgoing
traffic (inside->outside) to your own TURN server.

-d
 

> -----Original Message-----
> From: David Barrett [mailto:dbarrett@quinthar.com] 
> Sent: Tuesday, February 13, 2007 12:55 PM
> To: 'Dan Wing'; 'Magnus Westerlund'
> Cc: behave@ietf.org; 'IETF AVT WG'
> Subject: RE: [BEHAVE] [Fwd: Last 
> Call:draft-wing-behave-symmetric-rtprtcp(Common Local 
> Transmit andReceive Ports (Symmetric RTP)) toInformational RFC]
> 
> Though I think it's still a good recommendation, one thing I 
> found when
> working on iGlance was the case where two users were each 
> behind a different
> TURN relay server.
> 
> With symmetric RTP (if I understand correctly), for me to 
> send a packet to
> you I need to send it up to my TURN server, which forwards it 
> to your TURN
> server, which sends it to you.  Ideally I'd send it to your 
> TURN server
> direct, and cut out one relay.
> 
> The problem with this is it means our RTP isn't strictly 
> symmetric -- I
> receive from one place (my TURN server), but send to another 
> (your TURN
> server).
> 
> Am I misunderstanding how symmetric RTP works?  Perhaps this 
> is too minor a
> point to discuss here, however.
> 
> -david
> 
> > -----Original Message-----
> > From: Dan Wing [mailto:dwing@cisco.com]
> > Sent: Tuesday, February 13, 2007 12:44 PM
> > To: 'Magnus Westerlund'
> > Cc: behave@ietf.org; 'IETF AVT WG'
> > Subject: RE: [BEHAVE] [Fwd: Last Call:draft-wing-behave-symmetric-
> > rtprtcp(Common Local Transmit andReceive Ports (Symmetric RTP))
> > toInformational RFC]
> > 
> > Per Francois's suggestion, the following new text would be 
> placed at the
> > end
> > of section 3 of draft-wing-behave-symmetric-rtprtcp:
> > 
> >   "For these reasons it is RECOMMENDED that symmetric RTP and
> >    symmetric RTCP always be used for bi-directional RTP media
> >    streams."
> > 
> > -d
> > 
> > > -----Original Message-----
> > > From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> > > Sent: Tuesday, February 13, 2007 12:17 PM
> > > To: Magnus Westerlund
> > > Cc: behave@ietf.org; IETF AVT WG
> > > Subject: Re: [BEHAVE] [Fwd: Last Call:
> > > draft-wing-behave-symmetric-rtprtcp(Common Local Transmit and
> > > Receive Ports (Symmetric RTP)) toInformational RFC]
> > >
> > > There has been raised a comment that this document should 
> contain a
> > > normative recommendation on using symmetric ports. However to
> > > make this
> > > happen the document would need to be a BCP. I am willing 
> to consider
> > > this but would like to have AVT and Behave WG 
> participant's view on
> > > doing this before progressing down that road and updating the
> > > IETF last
> > > call. So please provide comments by Tuesday 20th of Feb 
> on this issue.
> > >
> > > Best Regards
> > >
> > > Magnus
> > >
> > > Magnus Westerlund skrev:
> > > > Hi,
> > > >
> > > > This document has been raised before in both AVT and BEHAVE
> > > WG. I have
> > > > chosen to AD sponsor this document for publication as 
> informational
> > > > status because it seems to be of general interest. You have
> > > 4 weeks to
> > > > provide any comments on the document.
> > > >
> > > > Magnus Westerlund
> > > >
> > > > IETF Transport Area Director & TSVWG Chair
> > > >
> > > 
> ----------------------------------------------------------------------
> > > > Multimedia Technologies, Ericsson Research EAB/TVA/A
> > > >
> > > 
> ----------------------------------------------------------------------
> > > > Ericsson AB                | Phone +46 8 4048287
> > > > Torshamsgatan 23           | Fax   +46 8 7575550
> > > > S-164 80 Stockholm, Sweden | mailto: 
> magnus.westerlund@ericsson.com
> > > >
> > > 
> ----------------------------------------------------------------------
> > > >
> > > >
> > > --------------------------------------------------------------
> > > ----------
> > > >
> > > > Ämne:
> > > > Last Call: draft-wing-behave-symmetric-rtprtcp (Common
> > > Local Transmit
> > > > and Receive Ports (Symmetric RTP)) to Informational RFC
> > > > Från:
> > > > The IESG <iesg-secretary@ietf.org>
> > > > Datum:
> > > > Mon, 12 Feb 2007 15:44:51 -0500
> > > > Till:
> > > > IETF-Announce <ietf-announce@ietf.org>
> > > >
> > > > Till:
> > > > IETF-Announce <ietf-announce@ietf.org>
> > > >
> > > >
> > > > The IESG has received a request from an individual
> > > submitter to consider
> > > > the following document:
> > > >
> > > > - 'Common Local Transmit and Receive Ports (Symmetric RTP) '
> > > >    <draft-wing-behave-symmetric-rtprtcp-01.txt> as an
> > > Informational RFC
> > > >
> > > > The IESG plans to make a decision in the next few weeks,
> > > and solicits
> > > > final comments on this action.  Please send substantive
> > > comments to the
> > > > ietf@ietf.org mailing lists by 2007-03-12. Exceptionally,
> > > > comments may be sent to iesg@ietf.org instead. In either
> > > case, please
> > > > retain the beginning of the Subject line to allow 
> automated sorting.
> > > >
> > > > The file can be obtained via
> > > >
> > > http://www.ietf.org/internet-drafts/draft-wing-behave-symmetri
> > > c-rtprtcp-01.txt
> > > >
> > > >
> > > > IESG discussion can be tracked via
> > > >
> > > https://datatracker.ietf.org/public/pidtracker.cgi?command=vie
> > > w_id&dTag=13165&rfc_flag=0
> > > >
> > > >
> > > > _______________________________________________
> > > > IETF-Announce mailing list
> > > > IETF-Announce@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/ietf-announce
> > > >
> > > >
> > > >
> > > >
> > > --------------------------------------------------------------
> > > ----------
> > > >
> > > > _______________________________________________
> > > > Behave mailing list
> > > > Behave@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/behave
> > >
> > >
> > > --
> > >
> > > Magnus Westerlund
> > >
> > > IETF Transport Area Director & TSVWG Chair
> > > 
> ----------------------------------------------------------------------
> > > Multimedia Technologies, Ericsson Research EAB/TVA/A
> > > 
> ----------------------------------------------------------------------
> > > Ericsson AB                | Phone +46 8 4048287
> > > Torshamsgatan 23           | Fax   +46 8 7575550
> > > S-164 80 Stockholm, Sweden | mailto: 
> magnus.westerlund@ericsson.com
> > > 
> ----------------------------------------------------------------------
> > >
> > > _______________________________________________
> > > Behave mailing list
> > > Behave@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/behave
> > 
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www1.ietf.org/mailman/listinfo/behave

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt