[payload] draft-ietf-payload-rtp-ancillary status
Thomas Edwards <Thomas.Edwards@fox.com> Wed, 13 December 2017 00:46 UTC
Return-Path: <Thomas.Edwards@fox.com>
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 E0685127137 for <payload@ietfa.amsl.com>; Tue, 12 Dec 2017 16:46:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=foxgroupinc.onmicrosoft.com
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 wV3LxgUKir4N for <payload@ietfa.amsl.com>; Tue, 12 Dec 2017 16:46:29 -0800 (PST)
Received: from mx0a-00195501.pphosted.com (mx0a-00195501.pphosted.com [67.231.149.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 057E812711D for <payload@ietf.org>; Tue, 12 Dec 2017 16:46:28 -0800 (PST)
Received: from pps.filterd (m0072270.ppops.net [127.0.0.1]) by mx0a-00195501.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id vBD0jsjZ020984 for <payload@ietf.org>; Tue, 12 Dec 2017 16:46:27 -0800
Received: from nam02-bl2-obe.outbound.protection.outlook.com (mail-bl2nam02lp0088.outbound.protection.outlook.com [207.46.163.88]) by mx0a-00195501.pphosted.com with ESMTP id 2etr8erf6f-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <payload@ietf.org>; Tue, 12 Dec 2017 16:46:27 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=FoxGroupInc.onmicrosoft.com; s=selector1-fox-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=EnMvxrBbFNm2Y+WJtEVyRV2jzxqxvkdfsZSTAXjBnJY=; b=B7TD6NH2HxR5lwpXJ9otpMK+BryD059nvPFYwEmtTG7lGOiBaI6+NGcH/mXJFtDiozZdJ1ulFwLiNBzow/zJ8OOzLUk6T41aguIDEGeC7SwM+PkjtIL12xblDdDefi/kKY+Alud0i65uYDcSzGqakRk8FqgJ9xZjyymXv5UjneA=
Received: from BN3PR05MB2657.namprd05.prod.outlook.com (10.166.72.21) by BN3PR05MB2659.namprd05.prod.outlook.com (10.166.72.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.323.4; Wed, 13 Dec 2017 00:46:25 +0000
Received: from BN3PR05MB2657.namprd05.prod.outlook.com ([10.166.72.21]) by BN3PR05MB2657.namprd05.prod.outlook.com ([10.166.72.21]) with mapi id 15.20.0323.011; Wed, 13 Dec 2017 00:46:24 +0000
From: Thomas Edwards <Thomas.Edwards@fox.com>
To: "payload@ietf.org" <payload@ietf.org>
Thread-Topic: draft-ietf-payload-rtp-ancillary status
Thread-Index: AQHTc6vN0fdzhVamQkyio+b+5AsqgA==
Date: Wed, 13 Dec 2017 00:46:24 +0000
Message-ID: <5A52312B-8CEA-46B4-A047-2CEB02404C52@foxeg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.25.0.170815
x-originating-ip: [76.171.122.204]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN3PR05MB2659; 20:eBBM9tkjU+Gmu9JGKJ6j6pMY7UOOVMZSuXwQw+OwzQgaSglSfiYmjyJhN66Cmcja3D6d5zIarDUhGSkjAVGxsF1cplMQrLCRIGDtd4x/970c+Vh48WjKp3KYKuqf/JIRTrvXFTcrMzzaOZILQ/3PPsaomfr33tlo7drHwmvQHbOlGhXJsPyb/wP5CEfT8iI2hblbcWGug74v9hOaCGi4jPH40ToN7+hBLbZ8NJef+ANk9qcHVWkTc1wZXOd9u0AGGQzT8Lb7+NqzafHhbyGVzm1xHM9dceIfFQ0QMNzaYCK0HJ0BX8JuaWGciMCyqT8bCPgl9FonyiwQ4lg/aWnPtA==
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 5acd5e1b-e172-419b-1763-08d541c2f00e
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(48565401081)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(5600026)(4604075)(2017052603307); SRVR:BN3PR05MB2659;
x-ms-traffictypediagnostic: BN3PR05MB2659:
x-microsoft-antispam-prvs: <BN3PR05MB2659F581784F1A0FBC77918994350@BN3PR05MB2659.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(21748063052155)(177823376758907);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(2401047)(8121501046)(5005006)(3002001)(3231023)(93006095)(93001095)(10201501046)(6055026)(6041248)(20161123562025)(20161123564025)(20161123558100)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(6072148)(201708071742011); SRVR:BN3PR05MB2659; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:BN3PR05MB2659;
x-forefront-prvs: 052017CAF1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(376002)(39860400002)(346002)(189003)(199004)(5660300001)(53936002)(1730700003)(106356001)(5640700003)(66066001)(99286004)(81166006)(105586002)(8676002)(77096006)(83506002)(81156014)(3660700001)(6486002)(2906002)(478600001)(72206003)(316002)(102836003)(6116002)(3846002)(68736007)(54896002)(86362001)(58126008)(97736004)(2501003)(36756003)(2351001)(83716003)(7736002)(6306002)(82746002)(3280700002)(14454004)(2900100001)(6916009)(8936002)(33656002)(561944003)(59450400001)(230783001)(25786009)(9686003)(6512007)(6506007)(6436002)(33896004); DIR:OUT; SFP:1101; SCL:1; SRVR:BN3PR05MB2659; H:BN3PR05MB2657.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: fox.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_5A52312B8CEA46B4A0472CEB02404C52foxegcom_"
MIME-Version: 1.0
X-OriginatorOrg: fox.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 5acd5e1b-e172-419b-1763-08d541c2f00e
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Dec 2017 00:46:24.7365 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: de99ade3-81db-4070-ae0d-3c1562041b30
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR05MB2659
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-12-12_18:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=650 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1712130009
Archived-At: <https://mailarchive.ietf.org/arch/msg/payload/lntJRYK6Q8IaMW_rltGAKSLsuhY>
Subject: [payload] draft-ietf-payload-rtp-ancillary status
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: Wed, 13 Dec 2017 00:46:32 -0000
Dear IETF Payload WG,
I have presented the new proposal for generic location codes in Line_Number and Horizontal_Offset fields to subject matter experts in SMPTE and AIMS, and there is general agreement with the proposal.
They will be:
Line_Number | ANC data packet generic vertical location
0x7FF | Without specific line location within the field or frame
0x7FE | On any line in the range from the second line after
the line specified for switching, as defined in SMPTE
RP 168, to the last line before active video, inclusive
0x7FD | On a line number larger than can be represented in 11
bits of this field (if needed for future formats)
Horizontal_Offset | ANC data packet generic horizontal location
0xFFF | Without specific horizontal location
0xFFE | Within horizontal ancillary data space (HANC) as
defined in SMPTE ST 291-1
0xFFD | Within the ancillary data space located between SAV
(Start of Active Video) and EAV (End of Active Video)
markers of the serial digital interface
0xFFC | Horizontal offset is larger than can be represented in
the 12 bits of this field (if needed for future formats, or for
certain low frame rate 720p formats)
One further item came up regarding Horizontal_Offset. In SMPTE ST 2038 (ANC Data in MPEG-TS, the data model we originally based this I-D on), Horizontal_Offset just says:
“For HD, this is in units of Y samples (e.g., the range 0 to 2199 for 1080i @ 59.94).”
When I authored draft-ietf-payload-rtp-ancillary-0, I thought I’d be more verbose and say of Horiozntal_Offset:
“For HD, this is in units of luma sample numbers as specified by the defining document of the particular image (e.g., SMPTE ST 274 [ST274] for 1920
x 1080 active images, or SMPTE ST 296 [ST296] for 1280 x 720 progressive active images).”
This appears to limit us to images carried in a single SDI stream. But now that we’ve extended this payload to be able to handle images carried over SDI multiple streams (such as UHD images), and we are specifically dealing with the location of ancillary data in SDI streams rather than images, I believe it is time to lean back towards simplicity, and have Horizontal_Offset state:
“For HD, this is in units of Y samples as defined in ITU-R BT.1120.”
If it suits the Payload WG, I can submit a -13 version of the I-D with these changes.
-Thomas
--
Thomas Edwards
FOX Networks Engineering & Operations
VP Engineering & Development
thomas.edwards@fox.com
+1-310-369-6696
10201 W Pico Blvd
Los Angeles, CA 90035
- [payload] draft-ietf-payload-rtp-ancillary status Thomas Edwards