[media-types] Registration of video/smpte291 media type
"Ali C. Begen" <acbegen@gmail.com> Tue, 09 August 2016 15:21 UTC
Return-Path: <acbegen@gmail.com>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D727E12D876 for <media-types@ietfa.amsl.com>; Tue, 9 Aug 2016 08:21:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 hc0uPZNxED9i for <media-types@ietfa.amsl.com>; Tue, 9 Aug 2016 08:21:06 -0700 (PDT)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0EE312D5FC for <media-types@ietf.org>; Tue, 9 Aug 2016 08:21:05 -0700 (PDT)
Received: by mail-oi0-x229.google.com with SMTP id 4so21891851oih.2 for <media-types@ietf.org>; Tue, 09 Aug 2016 08:21:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=7Qt4TNfLTKIpaLPIlhj/ci7N9uylGehS0B6n0ZnMPW0=; b=ApqwV+2X3sruoxg2xhI/MswDAXcdankXR3sGZdYlLLpHPw4c/RqAWGd3ZyoQ+0M6np CVfBQKNbNTAT+CKmcDgtyibtuqTFU9jcOmjOKa5f6R+7fu8r2sfXTblTvDmrFzU8YEaj KAX4K8nAda9uISgR/ojtyWLMUcygyb6xtjbFQMJAnvbGU01dk3DgvFkLv8EEOeIpU3cj ySLpBztWMPwT+Cb5mp8ptwza6E7ne8em+JT/uTjwcbN4pPn0Ln8bk+YyajwnQMkKd5Bm QE/+Ck02rxz23lVGwgflpD2y8CpnHi1hAs4PcnXDW25uTd9f7N5hs3PCc6Tl3NfS4UoV /bxw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=7Qt4TNfLTKIpaLPIlhj/ci7N9uylGehS0B6n0ZnMPW0=; b=UAd3bnUPdEaXRbtRZz/JU5Rb3sU/CyCGfShXZ7DOb/6dSstar5fW2qAy+8eXxXgp40 AjBoT8RC8vYlcq2ZTreQ/yezlewu+6AZQ+ERhwUnoK1097KnHoVWMz/XVrMJtnDh+llj LmnlSVBjz4F9leEM3+ipo9QgFflM/u2jjeuKvcbpHvVv/cOenlltxVKvKQNqNMZwE5VQ zWFDPjtybJcOAhU589QxTCJt7LGhUxg3/nVE4n0AK+S5fxB4Z1aT6AgSo3U7V5BTf+rO QGRRV1rudBPdxyIGm0YUmrfp0vVwDFXc8NiK0Fk4EEculqsBd1V9xluTaK0i+aaSPcHI IpQg==
X-Gm-Message-State: AEkoousCgXfmXls3B5wf79C5zp2GML/65rhDviIrWQl8rqmIqtoRDdozSaJMaHqys4AL8DtEq9g2/z6lzLx77Q==
X-Received: by 10.157.39.233 with SMTP id c96mr18461845otb.81.1470756065064; Tue, 09 Aug 2016 08:21:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.182.86 with HTTP; Tue, 9 Aug 2016 08:21:04 -0700 (PDT)
From: "Ali C. Begen" <acbegen@gmail.com>
Date: Tue, 09 Aug 2016 18:21:04 +0300
Message-ID: <CAG371nrTutfpqatwdj82k-8e0WSTg0ACRs6wh4=j0SE7uV51LA@mail.gmail.com>
To: media-types@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c032588cf3dd50539a51445"
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/L9d5zhkH70GwGZPDAST1O54yR8s>
Subject: [media-types] Registration of video/smpte291 media type
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 15:21:08 -0000
Hi there, https://datatracker.ietf.org/doc/draft-ietf-payload-rtp-ancillary/ completed WGLC in the Payload WG. The document registers video/smpte291. The new registration is in Section 3.1 of the document and is also given below. Comments on the registration are welcome. Thanks. Ali Begen Payload WG co-chair Type name: video Subtype name: smpte291 Required parameters: Rate: RTP timestamp clock rate. When an ANC RTP stream is to be associated with an RTP video stream, the RTP timestamp rates SHOULD be the same to ensure that ANC data packets can be associated with the appropriate frame or field. Otherwise, a 90 kHz rate SHOULD be used. Optional parameters: DID_SDID: Data identification and Secondary data identification words. The presence of the DID_SDID parameters signals that all ancillary data packets of this stream are of a particular type or types, i.e., labeled with a particular DIDs and SDIDs. DID and SDID values of SMPTE Registered ANC packet types can be found on the SMPTE Registry for Data Identification Word Assignments at: http://www.smpte-ra.org/smpte-ancillary-data-smpte-st-291 "Type 1" ANC packets (which do not have SDIDs defined) SHALL be labeled with SDID=0x00. DID and SDID values can be registered with SMPTE as per SMPTE ST 291-1 [ST291]. Encoding considerations: This media type is framed and binary; see Section 4.8 of RFC 6838 [RFC6838]. Security considerations: See Section 5 of [this RFC] Interoperability considerations: Data items in smpte291 can be very diverse. Receivers might only be capable of interpreting a subset of the possible data items. Some implementations may care about the location of the ANC data packets in the SDI raster, but other implementations may not care. Published specification: [this RFC] Applications that use this media type: Devices that stream real-time professional video, especially those that must interoperate with legacy serial digital interfaces (SDI). Additional Information: none Person & email address to contact for further information: T. Edwards <thomas.edwards@fox.com>, IETF Payload Working Group <payload@ietf.org> Intended usage: COMMON Restrictions on usage: This media type depends on RTP framing, and hence is only defined for transfer via RTP RFC 3550 [RFC3550]. Transport within other framing protocols is not defined at this time. Author: T. Edwards <thomas.edwards@fox.com> Change controller: IETF Audio/Video Transport Payloads working group delegated from the IESG.
- [media-types] Registration of video/smpte291 mediā¦ Ali C. Begen