[ietf-types] Registration of application/smpte336m

"Ali C. Begen (abegen)" <abegen@cisco.com> Wed, 11 January 2012 19:22 UTC

Return-Path: <abegen@cisco.com>
X-Original-To: ietf-types@ietfa.amsl.com
Delivered-To: ietf-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD65221F874A for <ietf-types@ietfa.amsl.com>; Wed, 11 Jan 2012 11:22:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.274
X-Spam-Level:
X-Spam-Status: No, score=-7.274 tagged_above=-999 required=5 tests=[AWL=-0.675, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LHL3jecYRtc9 for <ietf-types@ietfa.amsl.com>; Wed, 11 Jan 2012 11:22:39 -0800 (PST)
Received: from pechora3.lax.icann.org (unknown [IPv6:2620:0:2d0:201::1:73]) by ietfa.amsl.com (Postfix) with ESMTP id 4C3B311E8094 for <ietf-types@ietf.org>; Wed, 11 Jan 2012 11:22:35 -0800 (PST)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by pechora3.lax.icann.org (8.13.8/8.13.8) with ESMTP id q0BJME1c004260 for <ietf-types@iana.org>; Wed, 11 Jan 2012 19:22:35 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=abegen@cisco.com; l=2153; q=dns/txt; s=iport; t=1326309755; x=1327519355; h=mime-version:content-transfer-encoding:subject:date: message-id:from:to:cc; bh=rTlqZIZbUHPTWO5xDrh6McBgHhQMteuHkFCQ4Z8jn8I=; b=mJNmIZBFblV4Cxodj+fNOblUHB0PVAKvgwEL/Wqu7KYGlwPg1OeWzBXJ kVMH9NnlpL8tUFwmfDciK910eO9Rmn+yGFrp0rXvlxqke07sntzIMih0c BH8XeyvnyOmInyZZBYmzdZ33NDZDywL3hKhxrfuVHtsjOKyfDzmEjw5yI 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAA3hDU+rRDoI/2dsb2JhbABDrQaBBYF0AQQSAR1JEgEqBhgHIDcBBAoJCBqHYJkFAZ5NiQGCOWMEiAczl0iHZw
X-IronPort-AV: E=Sophos;i="4.71,494,1320624000"; d="scan'208";a="24913694"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 11 Jan 2012 19:21:57 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q0BJLvEv017689; Wed, 11 Jan 2012 19:21:57 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 11 Jan 2012 11:21:56 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 11 Jan 2012 11:21:50 -0800
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D5410B0A017@xmb-sjc-215.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Registration of application/smpte336m
Thread-Index: AczQlkSJJSeJKPUKTyiakz3lL6NNNg==
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: ietf-types@iana.org
X-OriginalArrivalTime: 11 Jan 2012 19:21:56.0923 (UTC) FILETIME=[48A338B0:01CCD096]
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora3.lax.icann.org [192.0.33.73]); Wed, 11 Jan 2012 19:22:35 +0000 (UTC)
X-Mailman-Approved-At: Fri, 13 Jan 2012 07:29:28 -0800
Cc: payload@ietf.org
Subject: [ietf-types] Registration of application/smpte336m
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jan 2012 19:22:42 -0000

Hello,

draft-ietf-payload-rtp-klv-02 has finished WGLC in the PAYLOAD WG. There is one new registration in Section 6.1 of http://datatracker.ietf.org/doc/draft-ietf-payload-rtp-klv/?include_text=1 

The relevant text is copied below as well.

Your comments are appreciated.

Thanks. 
-acbegen (PAYLOAD WG Co-chair)



6.1.  Media Type Definition

      Type name: application

      Subtype name: smpte336m

      Required parameters:

         rate: RTP timestamp clock rate.  Typically chosen based on
         sampling rate of metadata being transmitted, but other rates
         can be specified.

      Optional parameters: None

      Encoding considerations: This media type is framed and binary; see
      Section 4.8 of [RFC4288].

      Security considerations: See Section 8 of RFCXXXX (note to RFC
      editor: please replace XXXX with the number assigned to this RFC).

      Interoperability considerations: Data items in smpte336m can be
      very diverse.  Receivers might only be capable of interpreting a
      subset of the possible data items; unrecognized items are skipped.
      Agreement on data items to be used out of band, via application
      profile or similar, is typical.

      Published specification: RFCXXXX

      Applications that use this media type: Streaming of metadata
      associated with simultaneously streamed video and transmission of
      [SMPTE336M] based media formats (e.g.  MXF [SMPTE377M]).

      Additional Information: none

      Person & email address to contact for further information: J.
      Downs <jeff_downs@partech.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 ([RFC3550]).  Transport
      within other framing protocols is not defined at this time.

      Author:

         J. Downs <jeff_downs@partech.com>

         J. Arbeiter <jimsgti@gmail.com>

      Change controller: IETF Payload working group delegated from the
      IESG.