Re: [payload] I-D Action: draft-ietf-payload-rtp-ancillary-13.txt

Thomas Edwards <Thomas.Edwards@fox.com> Wed, 10 January 2018 03:26 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 A9A87127601 for <payload@ietfa.amsl.com>; Tue, 9 Jan 2018 19:26:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level:
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 9nFLzeOVSOtv for <payload@ietfa.amsl.com>; Tue, 9 Jan 2018 19:26:10 -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 311EA126CD6 for <payload@ietf.org>; Tue, 9 Jan 2018 19:26:10 -0800 (PST)
Received: from pps.filterd (m0087375.ppops.net [127.0.0.1]) by mx0a-00195501.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w0A3Q5Va030850; Tue, 9 Jan 2018 19:26:05 -0800
Received: from nam01-sn1-obe.outbound.protection.outlook.com (mail-sn1nam01lp0112.outbound.protection.outlook.com [207.46.163.112]) by mx0a-00195501.pphosted.com with ESMTP id 2fd8c68c2n-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 09 Jan 2018 19:26:05 -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=aDnLnzirOQR6i7aM1h0nvBr8H+uF9nqYmirPLlejJ7k=; b=A/qm80QmSZIQna62K4lqyGtkhisH76IxmQSU9h76DNA2WxKVpvLa9Wr5Sznuhx/YXjM1a4v1LHWkirOECGp60BqWQY07gSjsYdAeqjT7FZpmTM4j1O3P6fCUuPgFce5o+e9wKKjGbG1IGtKqOy1msJhOG1FZ3hICc2oHOIS+FWY=
Received: from BN3PR05MB2657.namprd05.prod.outlook.com (10.166.72.21) by BN3PR05MB2754.namprd05.prod.outlook.com (10.167.2.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.407.1; Wed, 10 Jan 2018 03:26:01 +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.0407.004; Wed, 10 Jan 2018 03:26:01 +0000
From: Thomas Edwards <Thomas.Edwards@fox.com>
To: John Fletcher <John.Fletcher@bbc.co.uk>, "payload@ietf.org" <payload@ietf.org>
Thread-Topic: [payload] I-D Action: draft-ietf-payload-rtp-ancillary-13.txt
Thread-Index: AQHTddymwcEukxVJm0G8Lb9K6pWzMKNGBrmAgAZ9/wCAFf0RgIABP4sAgAHftoCAAwQnAIADbnYA
Date: Wed, 10 Jan 2018 03:26:00 +0000
Message-ID: <0594E33F-DD93-49BC-A827-78EB697E9E42@foxeg.com>
References: <151336685958.30439.12106998885650898556@ietfa.amsl.com> <4E1ED364-EACD-48FA-A80E-C029EFCD96C8@networked.media> <B1D49063AD5FBD4688F3EEDEC68B2017C39CF5D2@bgb01xud1011> <BBD61F65-23E2-4E26-B4B8-F86CEF456897@foxeg.com> <B1D49063AD5FBD4688F3EEDEC68B2017C39D1F54@bgb01xud1011> <4E73ADBA-259B-49F1-ADA8-20BBB87F7390@foxeg.com> <B1D49063AD5FBD4688F3EEDEC68B2017C39D5706@bgb01xud1011>
In-Reply-To: <B1D49063AD5FBD4688F3EEDEC68B2017C39D5706@bgb01xud1011>
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: [63.138.245.100]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN3PR05MB2754; 7:BWn5sZBMCLdLubQu1Fz+jk4sTsxJeenTXWFDThcqFhm9Lvg50YOCtVY9WikA6EcVu5ZPYoC5TFAse8muQvxbXc1wLhPwwayNaLDhghRupXJwAmsAErCmojKdRcM+3lXvJtzUfvNBC+RekmDfeEiZi2p5nYnwiecheu+JfyJE1U3mpq1fjyLQLSsq9jmJfY5NZHfYvAZi1JN9HyaXWzuDZq00aS1qiYdedXB4NUuB0S+NHeM7eW2a8j3//rd8Dn7O
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 841ed4fc-ff79-4642-d5d5-08d557d9df74
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(48565401081)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:BN3PR05MB2754;
x-ms-traffictypediagnostic: BN3PR05MB2754:
x-microsoft-antispam-prvs: <BN3PR05MB27549EFBA53DF512CAD9412394110@BN3PR05MB2754.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(10436049006162)(127952516941037)(177823376758907);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040470)(2401047)(5005006)(8121501046)(3231023)(944501075)(10201501046)(93006095)(93001095)(3002001)(6055026)(6041268)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123562045)(6072148)(201708071742011); SRVR:BN3PR05MB2754; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:BN3PR05MB2754;
x-forefront-prvs: 0548586081
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(396003)(366004)(39860400002)(376002)(39380400002)(189003)(199004)(24454002)(6436002)(82746002)(53936002)(9686003)(33656002)(6512007)(2900100001)(36756003)(3660700001)(14454004)(230783001)(6306002)(106356001)(105586002)(229853002)(478600001)(8936002)(81166006)(8676002)(81156014)(77096006)(6486002)(72206003)(83506002)(966005)(110136005)(102836004)(83716003)(305945005)(33896004)(7736002)(53546011)(6506007)(59450400001)(2906002)(97736004)(25786009)(6116002)(3846002)(66066001)(58126008)(68736007)(316002)(93886005)(5660300001)(2950100002)(4326008)(107886003)(2501003)(5890100001)(3280700002)(86362001)(575784001)(99286004)(76176011)(6246003); DIR:OUT; SFP:1101; SCL:1; SRVR:BN3PR05MB2754; 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)
x-microsoft-antispam-message-info: L8/86mML/rouix6L7nIOY34wTOXtyJ/GQsdULXmuU5Q7ZpJQ4XDrDJ9yiqmBLyzrgzL26LUPtTjW7hUnocuYJw==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <0A1DC02919CB8F4A9A78AE24E53A2CF7@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: fox.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 841ed4fc-ff79-4642-d5d5-08d557d9df74
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jan 2018 03:26:00.9414 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: de99ade3-81db-4070-ae0d-3c1562041b30
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR05MB2754
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-01-10_02:, , 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=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801100044
Archived-At: <https://mailarchive.ietf.org/arch/msg/payload/p3hk89iI_tevZJ9kj61AIuYJyLI>
Subject: Re: [payload] I-D Action: draft-ietf-payload-rtp-ancillary-13.txt
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, 10 Jan 2018 03:26:17 -0000

OK, I’d be glad to issue a new I-D with this language if it pleases the Payload WG.  I have passed it by some key SMPTE SMEs who also feel it is OK wording.

-Thomas

On 1/7/18, 7:02 AM, "John Fletcher" <John.Fletcher@bbc.co.uk> wrote:

    Looks good to me.
    John
    ________________________________________
    From: Thomas Edwards [Thomas.Edwards@fox.com]
    Sent: 06 January 2018 00:58
    To: John Fletcher; payload@ietf.org
    Cc: Ali C. Begen
    Subject: Re: [payload] I-D Action: draft-ietf-payload-rtp-ancillary-13.txt
    
    OK, I am fine with this:
    
    Horizontal_Offset: 12 bits
               This field defines the location of the ANC data packet in an
               SDI raster relative to the start of active video (SAV, a
               digital synchronizing signal present in SDI interfaces) as an
               unsigned integer in network byte order.  A value of 0 means
               that the Ancillary Data Flag (ADF) of the ANC data packet
               begins immediately following SAV.  The horizontal offset
               from SAV is measured in terms of 10-bit words of the
               indicated data stream and data channel.
    
    For line number, I see your point.  Really no point in referencing anything even for SD, how about just:
    
    Line_Number: 11 bits
               This field contains the digital interface line number
               that corresponds to the location of the ANC data
               packet as an unsigned integer in network
               byte order.
    
    -Thomas
    
    
    On 1/4/18, 4:21 AM, "John Fletcher" <John.Fletcher@bbc.co.uk> wrote:
    
        That is better but there is still the issue that no definition is given for UHD.  I don't think there is any need for make a distinction for SD/HD/UHD, so the last sentence could be as below (deleting the "For SD..." sentence):
    
        "The horizontal offset from SAV is measured in terms of 10-bit words of the indicated data stream/data channel."
    
        I also have a slight issue with the Line_Number definition because it says line number for HD is defined in ITU-R BT.1120 but that does not cover 3G Level A or HFR.  So I would suggest changing the first paragraph to:
    
        "This field contains the line number (as defined in ITU-R BT.1700 [BT1700] for SD video or the appropriate interface mapping specification for HD or UHD video) that corresponds to the location of the ANC data packet in an SDI raster as an unsigned integer in network byte order."
    
        I would also move the paragraph beginning "In multi-stream interfaces ..." so that it follows the first paragraph.
    
        And finally, in the "Note ..." paragraph, I would change "sample structure specification" to "interface mapping specification".
    
        John
        ________________________________________
        From: Thomas Edwards [Thomas.Edwards@fox.com]
        Sent: 04 January 2018 01:17
        To: John Fletcher; payload@ietf.org
        Cc: Ali C. Begen
        Subject: Re: [payload] I-D Action: draft-ietf-payload-rtp-ancillary-13.txt
    
        draft-ietf-payload-rtp-ancillary-13 currently says for Horizontal_Offset:
    
        “This field defines the location of the ANC data packet in an SDI raster relative to the start of active video (SAV, a digital synchronizing signal present in SDI interfaces) as an unsigned integer in network byte order.  A value of 0 means that the Ancillary Data Flag (ADF) of the ANC data packet begins immediately following SAV.  For HD, this is in units of Y samples as defined in ITU-R BT.1120 [BT1120]…”
    
        How about we change the last sentence to:
    
        “For HD, the horizontal offset from SAV is measured in terms of 10-bit words of the particular channel indicated by the ‘C’ bit.”
    
        -Thomas
    
    
        On 12/20/17, 9:30 AM, "payload on behalf of John Fletcher" <payload-bounces@ietf.org on behalf of John.Fletcher@bbc.co.uk> wrote:
    
            I think there may still be an issue with the definition of Horizontal_Offset.  No definition is given for UHD and I'm not sure that the HD definition in terms of Y samples is always applicable.
    
            The ANC data consists of 10-bit words in a 10-bit data stream (or a data channel of a data stream).  The position should be measured in terms of  10-bit words relative to the SAV sequence in the data stream.  A definition along those lines works regardless of the image format (YCbCr, RGB, 10-bit, 12-bit) or the mapping from source image to interface.
    
            John Fletcher
            ________________________________________
            From: payload [payload-bounces@ietf.org] on behalf of Ali C. Begen [ali.begen@networked.media]
            Sent: 16 December 2017 14:21
            To: payload@ietf.org
            Subject: Re: [payload] I-D Action: draft-ietf-payload-rtp-ancillary-13.txt
    
            Payload WG,
    
            Is there any objection to the latest revision that addresses the issues Thomas pointed out earlier? The draft was in the RFC editor queue and if there are no objections, we will soon ship it back there. But to give people a chance to read and officially comment on the revision, I think we should start a new IETF LC for a week.
    
            @Ben, could we do that?
    
            -acbegen
    
    
    
    
    
    
    
    -----------------------------
    https://urldefense.proofpoint.com/v2/url?u=http-3A__www.bbc.co.uk&d=DwIF-g&c=uw6TLu4hwhHdiGJOgwcWD4AjKQx6zvFcGEsbfiY9-EI&r=lekNOOM5noV61zrPH3rwPyhtNnLLWoLEHgd0quQxly8&m=V2EAlSlkG_oZade6gVi4ztzBsIIms5rqHMx_ps519Kk&s=EZGTs6H5N1HOkhnHnvZc0EdR573b8IkIaiMCZFad3B0&e=
    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.
    -----------------------------