[MMUSIC] draft-thornburgh-rtmfp-flash notice and feedback request

Michael Thornburgh <mthornbu@adobe.com> Thu, 01 May 2014 22:11 UTC

Return-Path: <mthornbu@adobe.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E40EB1A0958 for <mmusic@ietfa.amsl.com>; Thu, 1 May 2014 15:11:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
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 jDmxKaHWi1bE for <mmusic@ietfa.amsl.com>; Thu, 1 May 2014 15:11:31 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0240.outbound.protection.outlook.com [207.46.163.240]) by ietfa.amsl.com (Postfix) with ESMTP id 5E8391A066A for <mmusic@ietf.org>; Thu, 1 May 2014 15:11:31 -0700 (PDT)
Received: from BY2PR02MB364.namprd02.prod.outlook.com (10.141.140.152) by BY2PR02MB362.namprd02.prod.outlook.com (10.141.140.143) with Microsoft SMTP Server (TLS) id 15.0.934.12; Thu, 1 May 2014 22:11:28 +0000
Received: from BY2PR02MB364.namprd02.prod.outlook.com ([10.141.140.152]) by BY2PR02MB364.namprd02.prod.outlook.com ([10.141.140.152]) with mapi id 15.00.0934.000; Thu, 1 May 2014 22:11:28 +0000
From: Michael Thornburgh <mthornbu@adobe.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: draft-thornburgh-rtmfp-flash notice and feedback request
Thread-Index: Ac9lh+8qRMgfmQImQsqCwGt4lVPrxA==
Date: Thu, 01 May 2014 22:11:27 +0000
Message-ID: <62cb796a473c4972bcdf8a0e1da7d283@BY2PR02MB364.namprd02.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.150.19.4]
x-forefront-prvs: 01986AE76B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019001)(6009001)(428001)(189002)(199002)(377424004)(77096999)(54356999)(50986999)(83072002)(85852003)(81342001)(20776003)(92566001)(86362001)(80022001)(81542001)(4396001)(76482001)(74502001)(74662001)(15975445006)(33646001)(74316001)(31966008)(83322001)(19580395003)(80976001)(79102001)(76576001)(99396002)(101416001)(15202345003)(66066001)(99286001)(77982001)(87936001)(2656002)(46102001)(24736002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR02MB362; H:BY2PR02MB364.namprd02.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (: adobe.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mthornbu@adobe.com;
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: adobe.com
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/yQbowLr1j-l0gBOlA7ze5AuPVN8
Subject: [MMUSIC] draft-thornburgh-rtmfp-flash notice and feedback request
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 May 2014 22:11:40 -0000

hi MMUSIC folks.

just over a year ago, i notified this working group of the existence of an I-D describing Adobe's RTMFP, a general purpose endpoint-to-endpoint transport protocol designed for real-time and P2P communication.  it is deployed widely in the Internet as part of Flash and other software.  in particular, it is used to transport live, low-latency audio, video, and data P2P in Flash.  it has since been published as RFC 7016.

recently i submitted a new companion I-D, "Adobe's RTMFP Profile for Flash Communication", that describes how RTMFP (the generic protocol) is used to transport the video, audio, and data messages of real-time and P2P communications in Flash, including the concrete RFC 7016 "Cryptography Profile" for Flash.  this new specification illustrates a practical application of RTMFP, which can also help folks understand how to apply RTMFP's capabilities to use cases other than Flash communication.

i realize this material isn't in MMUSIC's charter.  however, this material pertains directly to live multimedia communication practiced in the Internet today, and therefore may be relevant, or of interest, to some participants of this working group.

we will eventually be submitting this specification to the Independent Submission Editorial Board for publication as an Informational RFC.  to that end i am soliciting feedback, comments, and reviews of this I-D to help us improve its quality, readability, implementability, etc.

---
Name:           draft-thornburgh-rtmfp-flash
Revision:       00
Title:          Adobe's RTMFP Profile for Flash Communication
Document date:  2014-04-14
Group:          Individual Submission
Pages:          45
URL:            http://www.ietf.org/internet-drafts/draft-thornburgh-rtmfp-flash-00.txt
Status:         https://datatracker.ietf.org/doc/draft-thornburgh-rtmfp-flash/
Htmlized:       http://tools.ietf.org/html/draft-thornburgh-rtmfp-flash-00
IPR:            https://datatracker.ietf.org/ipr/2345/

Abstract:
   This memo describes how to use Adobe's Secure Real-Time Media Flow
   Protocol (RTMFP) to transport the video, audio, and data messages of
   Adobe Flash platform communications.  Aspects of this application
   profile include cryptographic methods and data formats, flow metadata
   formats, and protocol details for client-server and peer-to-peer
   communication.
---

thank you.

-michael thornburgh