[tsvwg] feedback request: draft-thornburgh-rtmfp-flash
Michael Thornburgh <mthornbu@adobe.com> Mon, 21 April 2014 21:34 UTC
Return-Path: <mthornbu@adobe.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 987491A02A0 for <tsvwg@ietfa.amsl.com>; Mon, 21 Apr 2014 14:34:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 6JHqyl1FUBjg for <tsvwg@ietfa.amsl.com>; Mon, 21 Apr 2014 14:34:12 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0184.outbound.protection.outlook.com [207.46.163.184]) by ietfa.amsl.com (Postfix) with ESMTP id 52DE11A0216 for <tsvwg@ietf.org>; Mon, 21 Apr 2014 14:34:12 -0700 (PDT)
Received: from BLUPR02MB359.namprd02.prod.outlook.com (10.141.77.148) by BLUPR02MB360.namprd02.prod.outlook.com (10.141.77.152) with Microsoft SMTP Server (TLS) id 15.0.921.12; Mon, 21 Apr 2014 21:34:06 +0000
Received: from BLUPR02MB359.namprd02.prod.outlook.com ([10.141.77.148]) by BLUPR02MB359.namprd02.prod.outlook.com ([10.141.77.148]) with mapi id 15.00.0921.000; Mon, 21 Apr 2014 21:34:06 +0000
From: Michael Thornburgh <mthornbu@adobe.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: feedback request: draft-thornburgh-rtmfp-flash
Thread-Index: Ac9dqU3+CdsveOucSe6LFY6UlsuYcg==
Date: Mon, 21 Apr 2014 21:34:05 +0000
Message-ID: <1a06e61cada14a898169c53419607ec4@BLUPR02MB359.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: 0188D66E61
x-forefront-antispam-report: SFV:NSPM; SFS:(10019001)(6009001)(428001)(377424004)(189002)(199002)(86362001)(76482001)(85852003)(83072002)(15975445006)(76576001)(81342001)(33646001)(87936001)(46102001)(81542001)(99286001)(4396001)(83322001)(66066001)(79102001)(80022001)(77982001)(99396002)(2656002)(20776003)(50986999)(15202345003)(77096999)(74316001)(92566001)(54356999)(80976001)(19580395003)(74662001)(74502001)(31966008)(24736002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR02MB360; H:BLUPR02MB359.namprd02.prod.outlook.com; FPR:AD5875FF.ACF0CD95.B5E13F47.DCEA9171.2033E; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (: adobe.com does not designate permitted sender hosts)
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/tsvwg/s2ll2gc6AsINy2xt0dzZPSTLnIw
Subject: [tsvwg] feedback request: draft-thornburgh-rtmfp-flash
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 21:34:14 -0000
hi TSV Working Group folks. i briefly presented "Adobe's Secure Real-Time Media Flow Protocol" (RTMFP) to this working group at IETF 86 in Orlando, and notified this mailing list, soliciting feedback on the specification I-D to help improve it. i received invaluable feedback from the community, and when the specification was published as RFC 7016, it was very much improved from the initial draft due in large part to the community review it received. RTMFP is 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 Adobe Flash and other software. i have 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. 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
- [tsvwg] feedback request: draft-thornburgh-rtmfp-… Michael Thornburgh