FW: (s22-list) FW: [AVT] Carrying SMPTE TimeCode in RTP

"Miller, William C" <William.C.Miller@abc.com> Fri, 03 March 2006 00:25 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEy6Z-0001cj-S1; Thu, 02 Mar 2006 19:25:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEtvO-0003I6-KA for avt@ietf.org; Thu, 02 Mar 2006 14:57:22 -0500
Received: from mail11.disney.com ([192.195.66.20]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEtvM-00059J-Kt for avt@ietf.org; Thu, 02 Mar 2006 14:57:22 -0500
Received: from imr12.disney.pvt (imr12.disney.pvt [153.6.60.115]) by mail11.disney.com with ESMTP; Thu, 2 Mar 2006 14:57:18 -0500
Received: from sm-flor-xc04.wdw.disney.com (sm-flor-xc04.wdw.disney.com [172.16.177.31]) by imr12.disney.pvt with ESMTP; Thu, 2 Mar 2006 14:57:17 -0500
Received: from SM-FLOR-XC02.wdw.disney.com ([172.16.177.19]) by sm-flor-xc04.wdw.disney.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 2 Mar 2006 14:57:16 -0500
Received: from sm-nyny-xc04.nena.wdpr.disney.com ([167.13.137.86]) by SM-FLOR-XC02.wdw.disney.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 2 Mar 2006 14:57:16 -0500
Received: from sm-nyny-xm06.nena.wdpr.disney.com ([167.13.137.81]) by sm-nyny-xc04.nena.wdpr.disney.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 2 Mar 2006 14:57:15 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: FW: (s22-list) FW: [AVT] Carrying SMPTE TimeCode in RTP
Date: Thu, 02 Mar 2006 14:57:14 -0500
Message-Id: <AA56D4A269A7284D9C0CE661AC23C463084A6B7C@sm-nyny-xm06.nena.wdpr.disney.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: (s22-list) FW: [AVT] Carrying SMPTE TimeCode in RTP
Thread-Index: AcY+HhqA48VLgOWuRGi9rQzUaidU2gABROuOAALdvyAAARiHoQ==
References: <8CD6499B205A994F9B6EA414EE591C653CB908@aspen.noc.iptv.org>
From: "Miller, William C" <William.C.Miller@abc.com>
To: avt@ietf.org
X-OriginalArrivalTime: 02 Mar 2006 19:57:15.0181 (UTC) FILETIME=[80CCFDD0:01C63E33]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: a6594207bdf0e066acd2cadeb5960bf2
X-Mailman-Approved-At: Thu, 02 Mar 2006 19:25:08 -0500
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>
Content-Type: multipart/mixed; boundary="===============0869753865=="
Errors-To: avt-bounces@ietf.org

Forwarded for Bill Hayes.  As an aside, note that iptv has a meaning other than video over IP.
 
Bill

	-----Original Message----- 
	From: Bill Hayes [mailto:Hayes@iptv.org] 
	Sent: Thu 3/2/2006 2:26 PM 
	To: Miller, William C 
	Cc: 
	Subject: RE: (s22-list) FW: [AVT] Carrying SMPTE TimeCode in RTP
	
	
	In life there are few certainties. Death, taxes and SMPTE timecode. If the proposed modification fixes the first two than I am in favor of it. But if I still have to pay taxes and die...than I'd like to see all of the SMPTE timecode carried.
	 
	Bill 
	 
	William T. Hayes
	Director of Engineering and Technology
	Iowa Public Television
	P.O. Box 6450
	Johnston, IA 50131-6450
	515-242-3116 (v)
	515-242-3109 (f)
	 
	<http://www.iptv.org/dtv/2006> 
	 

  _____  

	From: owner-s22-list@eng.smpte.org [mailto:owner-s22-list@eng.smpte.org] On Behalf Of Miller, William C
	Sent: Thursday, March 02, 2006 12:02 PM
	To: s22-list@eng.smpte.org
	Subject: (s22-list) FW: [AVT] Carrying SMPTE TimeCode in RTP
	
	
	Anyone want to comment?
	 
	Bill

		-----Original Message----- 
		From: avt-bounces@ietf.org on behalf of Colin Perkins 
		Sent: Thu 3/2/2006 12:23 PM 
		To: Dave Singer 
		Cc: avt@ietf.org 
		Subject: Re: [AVT] Carrying SMPTE TimeCode in RTP
		
		

		On 2 Mar 2006, at 00:42, Dave Singer wrote:
		> Answering my own email here, I'm assuming that the answer is yes to 
		> the 2nd question.
		>
		> The extra bits in an 8-byte SMPTE time-code can be used to
		> a) maintain the polarity of the code (numbers of 1s and 0s)
		> b) indicate the relationship of the codes to color fields
		> c) indicate whether it's drop-frame coding
		> d) and then do one of
		>    i) carry 4 characters more
		>    ii) carry a date and time-zone indication (SMPTE 309M)
		>    iii) carry some general SMPTE 262M data (control codes, text, 
		> production info etc.)
		>
		> I don't believe we need color and polarity handling in RTP.
		> We have drop-frame in the signalling.
		>
		> If we want to carry something as slowly-changing as a date or as 
		> unchanging as a time-zone, I on't believe that embedding it here is 
		> right.  Certainly thought should be applied before blindly applying 
		> it.  If a date is needed, it's not needed inline;  at most it would 
		> be in RTCP, and then I would argue for a new RTCP packet type to 
		> carry it.
		>
		> The other two possibilities are 'general meta-data' and should not 
		> be sub-embedded in a time-code, in RTP, but elevated and properly 
		> labelled at the stream level.
		>
		> So, my answer is no, we do not need the full 8-byte SMPTE time-code.
		
		Seems reasonable.
		
		Colin
		
		_______________________________________________
		Audio/Video Transport Working Group
		avt@ietf.org
		https://www1.ietf.org/mailman/listinfo/avt
		

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