Re: [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01
Randell Jesup <rjesup@wgate.com> Sat, 26 January 2008 17:04 UTC
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JIoRw-00022u-JV; Sat, 26 Jan 2008 12:04:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JIoRu-00022n-N2 for avt@ietf.org; Sat, 26 Jan 2008 12:04:10 -0500
Received: from pr-66-150-46-254.wgate.com ([66.150.46.254] helo=exchange1.wgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JIoRu-0001gy-73 for avt@ietf.org; Sat, 26 Jan 2008 12:04:10 -0500
Received: from jesup.eng.wgate.com ([10.32.2.26]) by exchange1.wgate.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 26 Jan 2008 12:04:06 -0500
To: Gunnar Hellström <gunnar.hellstrom@omnitor.se>
Subject: Re: [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01
References: <47679B43.3010503@db.org> <DD8B8FEBBFAF9E488F63FF0F1A69EDD10441071E@ftrdmel1> <E8308D99-774B-4B00-A5D8-72A9EFB97FDE@csperkins.org> <DD8B8FEBBFAF9E488F63FF0F1A69EDD104471489@ftrdmel1> <038901c85fef$d5e95400$0f75a7d9@GunnarH> <ybuhch0zm8y.fsf@jesup.eng.wgate.com> <03ae01c86031$627c33b0$0f75a7d9@GunnarH>
From: Randell Jesup <rjesup@wgate.com>
Date: Sat, 26 Jan 2008 12:04:04 -0500
In-Reply-To: <03ae01c86031$627c33b0$0f75a7d9@GunnarH> (Gunnar Hellström's message of "Sat, 26 Jan 2008 16:37:39 +0100")
Message-ID: <ybud4rozfgb.fsf@jesup.eng.wgate.com>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 26 Jan 2008 17:04:06.0693 (UTC) FILETIME=[75DFC550:01C8603D]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: 'MARJOU Xavier RD-CORE-LAN' <xavier.marjou@orange-ftgroup.com>, 'Colin Perkins' <csp@csperkins.org>, 'AVT WG' <avt@ietf.org>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Randell Jesup <rjesup@wgate.com>
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
Gunnar Hellström <gunnar.hellstrom@omnitor.se> writes: >Thanks for good comments. >You may be right that sending keep-alive with another SSRC may cause >unwanted effects in some receivers. But with an undefined PT as recommended >in the keepalive draft, I do not see higher risks than with sending it with >the same SSRC as another stream. I'm not sure how to parse what you said. I think you mean that the risk of using different SSRCs is no worse than the risk of using non-negotiated payload types. I'm not sure I agree, though both have some risks. >About the requirement of text/red and text/t140 to be the only payload in >the stream, RFC 4103 says in section 5.3: >----------------------------------------------------------------------- >"The text/t140 format relies on use of the sequence number in the RTP > packet header for detection of loss and, therefore, is not suitable > for applications where it needs to be alternating with other payloads > in the same RTP stream. It would be complicated and unreliable to > try to detect loss of data at the edges of the shifts between t140 > text and other stream contents. Therefore, text/t140 is RECOMMENDED > to be the only payload type in the RTP stream." >------------------------------------------------------------------ >So, it is clear that the method proposed in 4.8 of the keepalive draft is >not directly suitable for RFC 4103. Right. >It would be good to define a method for RFC 4103 keepalive in the keepalive >draft. Probably so, since for 4103 it's easy to do in a payload-specific manner and the other method won't work. This can also avoid issues with implementations that don't expect (and can't handle) multiple senders, etc. >Repetition of the latest transmitted RTP packet without modifying anything >could be another suitable method for RFC 4103 keepalive. Repeating also the >sequence number and time stamp, it will just be handled as a very late >duplicate and discarded by the receiver. Right? Yes, though I'd suggest for 4103 since it has a built-in ability to send what are basically "no-change" packets, to simply use those. >About multi-party for RFC 4103. Yes, it is not explicitly defined in RFC >4103. Generla RTP methods can be applied. >But to be clear, multi-party session handling of RFC 4103 real-time text is >now described in >http://www.ietf.org/internet-drafts/draft-hellstrom-text-conference-00.txt In practice I worry about if many/all implemetations handle "General RTP methods", though of course they should. >I think SSRC collissions and allocating SSRCs etc is described sufficiently >in RTP RFC 3550, so I do not see a need for describing that more. Agree? Your statement (if it's kept) is still too short, and also the issues with acting like you're two senders should be discussed (that's not a normal thing to do within a stream). As written, an implementer might think they should generate a new random SSRC for each keep-alive packet, and might never realize they need to send SR's or process RR's for the alternate SSRC. They also have to make sure the other side doesn't interpret this as an SSRC-collision-induced shift of SSRC. Overall, I'd lean towards a 4103-specific solution instead of adding the complexity of acting as a separate sender. -- Randell Jesup, Worldgate (developers of the Ojo videophone), ex-Amiga OS team rjesup@wgate.com "The fetters imposed on liberty at home have ever been forged out of the weapons provided for defence against real, pretended, or imaginary dangers from abroad." - James Madison, 4th US president (1751-1836) _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] draft-ietf-avt-app-rtp-keepalive-01 Alfred E. Heggestad
- [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01 SOLLAUD Aurelien RD-TECH-LAN
- Re: [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01 Colin Perkins
- RE: [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01 SOLLAUD Aurelien RD-TECH-LAN
- [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01 Gunnar Hellström
- Re: [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01 Randell Jesup
- RE: [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01 Gunnar Hellström
- Re: [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01 Colin Perkins
- Re: [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01 Randell Jesup
- Re: [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01 Colin Perkins
- RE: [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01 Gunnar Hellström
- RE: [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01 Dan Wing
- RE: [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01 Gunnar Hellström
- RE: [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01 Dan Wing
- RE: [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01 Gunnar Hellström
- RE: [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01 Dan Wing
- Re: [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01 Randell Jesup
- RE: [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01 aurelien.sollaud
- RE: [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01 Gunnar Hellström
- Re: [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01 Randell Jesup
- Re: [AVT] RE: draft-ietf-avt-app-rtp-keepalive-01 Randell Jesup