Re: [payload] Significant Differences Between draft-ietf-payload-rtp-ancillary-08 and -09

John Fletcher <John.Fletcher@bbc.co.uk> Tue, 16 May 2017 09:19 UTC

Return-Path: <John.Fletcher@bbc.co.uk>
X-Original-To: payload@ietfa.amsl.com
Delivered-To: payload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC067129B63 for <payload@ietfa.amsl.com>; Tue, 16 May 2017 02:19:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ebZpV-eb6NY5 for <payload@ietfa.amsl.com>; Tue, 16 May 2017 02:19:33 -0700 (PDT)
Received: from mailout0.cwwtf.bbc.co.uk (mailout0.cwwtf.bbc.co.uk [132.185.160.179]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1088412945D for <payload@ietf.org>; Tue, 16 May 2017 02:16:11 -0700 (PDT)
Received: from BGB01XI1002.national.core.bbc.co.uk ([10.184.50.52]) by mailout0.cwwtf.bbc.co.uk (8.15.2/8.15.2) with ESMTP id v4G9G8m0014277; Tue, 16 May 2017 10:16:08 +0100 (BST)
Received: from BGB01XUD1011.national.core.bbc.co.uk ([10.161.14.9]) by BGB01XI1002.national.core.bbc.co.uk ([10.184.50.52]) with mapi id 14.03.0319.002; Tue, 16 May 2017 10:16:08 +0100
From: John Fletcher <John.Fletcher@bbc.co.uk>
To: Thomas Edwards <Thomas.Edwards@fox.com>, "payload@ietf.org" <payload@ietf.org>
Thread-Topic: Significant Differences Between draft-ietf-payload-rtp-ancillary-08 and -09
Thread-Index: AQHSyrZiGvSczZmxek+HC40CeN/Tn6H1hE3o//+6BgCAAW/55A==
Date: Tue, 16 May 2017 09:16:07 +0000
Message-ID: <B1D49063AD5FBD4688F3EEDEC68B2017C3835B0B@bgb01xud1011>
References: <142B2248-5244-4179-8AFD-A5BF7CCD91ED@fox.com> <B1D49063AD5FBD4688F3EEDEC68B2017C3833979@bgb01xud1011>, <90439242-F466-45B0-9AF8-5E733E42669D@fox.com>
In-Reply-To: <90439242-F466-45B0-9AF8-5E733E42669D@fox.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.19.161.211]
x-exclaimer-md-config: 1cd3ac1c-62e5-43f2-8404-6b688271c769
x-tm-as-product-ver: SMEX-11.0.0.4179-8.100.1062-23072.005
x-tm-as-result: No--14.502800-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_B1D49063AD5FBD4688F3EEDEC68B2017C3835B0Bbgb01xud1011_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/payload/QWPSgoP5ckRTBgnnU63wCLeyg0U>
Subject: Re: [payload] Significant Differences Between draft-ietf-payload-rtp-ancillary-08 and -09
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Audio/Video Transport Payloads working group discussion list <payload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/payload>, <mailto:payload-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/payload/>
List-Post: <mailto:payload@ietf.org>
List-Help: <mailto:payload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/payload>, <mailto:payload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 May 2017 09:19:37 -0000

My concern is that there are two sets of data stream numbering in ST 425-3 Figure 2.  In each link they are numbered 1 & 2.  So the language needs to make it clear that we are numbering 1 - 4.

How about adding the following text:

Numbering of data streams is across the interface as a whole.  For example in the SMPTE ST 425-3 dual-link 3 Gb/s interface, the data streams are numbered 1 - 4 with data streams 1 and 2 on link 1 and data streams 3 and 4 on link 2.

John
________________________________
From: payload [payload-bounces@ietf.org] on behalf of Thomas Edwards [Thomas.Edwards@fox.com]
Sent: 15 May 2017 18:56
To: payload@ietf.org
Subject: Re: [payload] Significant Differences Between draft-ietf-payload-rtp-ancillary-08 and -09

I don’t see the problem – In ST 425-3 there are four data streams numbered 1-4, and Figures 1 & 2 show that data streams 1 & 2 go on 3G SDI link #1, and streams 3 & 4 go on 3G SDI link #2.

If you are concerned about the fact that the 3G SDI link itself (ST 424) also has two data streams each, that also should not matter because the ST 425-3 data streams also clearly define which of those ST 424 data streams are used (i.e. ST 425-3 data stream #3 is carried on 3G-SDI Link #2, ST 424 data stream #1).   I think it should be clear that if the VPID Code refers to “1080-line Video Payloads for Level A Mapping on a Dual-link 3 Gb/s (nominal) Serial Interface” that the stream number we are describing is from that standard, and not the stream number from ST 424.  That said, I blame SMPTE for not providing an appropriate adjective (such as “image stream number” or “link stream number”), but I think that it is perilous for IETF to invent one for them.

BTW I understand why link numbers are carried in the VPID – the goal of the VPID is to describe the video format and to help you plug the coaxial cables into the proper connector.  Once the coaxes are plugged in properly, the stream numbers follow naturally based on timing, so a VPID ANC packet does not need to be in every data stream, just on at least one per link.

If I am missing something and you have alternative suggested language, please provide it.

-Thomas

From: John Fletcher <John.Fletcher@bbc.co.uk>
Date: Monday, May 15, 2017 at 9:02 AM
To: Thomas Edwards <Thomas.Edwards@fox.com>, "payload@ietf.org" <payload@ietf.org>
Subject: RE: Significant Differences Between draft-ietf-payload-rtp-ancillary-08 and -09

Section 2.1 "StreamNum" doesn't give enough information about numbering of the data streams.  For example, in dual-link 3G there are 4 data streams split across two links, see ST 425-3 Figure 2.



----------------------------

http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.

---------------------