[dispatch] Proposal to provide update to draft-sandbakken-dispatch-bfcp-udp

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Mon, 23 May 2011 23:51 UTC

Return-Path: <eckelcu@cisco.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 091CBE07C2 for <dispatch@ietfa.amsl.com>; Mon, 23 May 2011 16:51:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.476
X-Spam-Level:
X-Spam-Status: No, score=-10.476 tagged_above=-999 required=5 tests=[AWL=0.123, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CTIXtXy91u0m for <dispatch@ietfa.amsl.com>; Mon, 23 May 2011 16:51:48 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfa.amsl.com (Postfix) with ESMTP id 769A7E0869 for <dispatch@ietf.org>; Mon, 23 May 2011 16:48:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=1730; q=dns/txt; s=iport; t=1306194482; x=1307404082; h=mime-version:content-transfer-encoding:subject:date: message-id:from:to; bh=eGbKs5nEuiNU/u3NmtdLqW794TvmSSgqq/Fqk9/pFUA=; b=OqWsqCUyMfwjXwL25+tf0PpXLykvuERuTHxdpWLsjuFw7MeNv2LhYCTt pftu6I29fjYk9aKPoJ/ZOTYh0Lx+5sh9BI3mVGyyEYmeq9+PTJSp+N43v dLgPKlprpU6Sfa0cOmG78H9MCAPqLJIZduwvrVBBYzi+4Wj2dL3p4vXwG M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnIIAFXx2k2rRDoI/2dsb2JhbACYII4Cd6gCgR2dcIYZBIZVjgKKYA
X-IronPort-AV: E=Sophos;i="4.65,258,1304294400"; d="scan'208";a="702107769"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-6.cisco.com with ESMTP; 23 May 2011 23:47:48 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p4NNlmBc007124 for <dispatch@ietf.org>; Mon, 23 May 2011 23:47:48 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 23 May 2011 16:47:48 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 23 May 2011 16:47:47 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C045A9E0D@xmb-sjc-234.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Proposal to provide update to draft-sandbakken-dispatch-bfcp-udp
Thread-Index: AcwZo9HtZKSlpVBASvW5ec0INqTXPw==
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: dispatch@ietf.org
X-OriginalArrivalTime: 23 May 2011 23:47:48.0774 (UTC) FILETIME=[D26EC460:01CC19A3]
Subject: [dispatch] Proposal to provide update to draft-sandbakken-dispatch-bfcp-udp
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2011 23:51:49 -0000

Problem Statement
-----------------
"Revision of the Binary Floor Control Protocol (BFCP) for use over an
unreliable transport", draft-sandbakken-dispatch-bfcp-udp, extends the
Binary Floor Control Protocol (BFCP) for use over an unreliable
transport.  It details a set of revisions to the protocol definition
document and the specification of Session Description Protocol (SDP)
format for BFCP streams.
The latest update to this draft, draft-sandbakken-dispatch-bfcp-udp-01,
has expired.
It is currently available at
http://tools.ietf.org/html/draft-sandbakken-dispatch-bfcp-udp-01.

Charter Proposal
----------------
I am not prosing a new working group for this. Rather, I would like make
an official proposal to update the draft to address the concerns raised
previously on the mailing list as well as when the draft was presented
at IETF 79. Provided this is done within the timeframe outlined for the
DISPATCH working group, I would like to ask to present the updated draft
within DISPATCH at IEFT 81. Next steps can be discussed at or following
IETF 81.

The motivation for using an unreliable transport for BFCP [RFC4582]
messages is fuelled by network deployments where RTP proxies or media
relays are present for NAT and firewall traversal.  In these
deployments, the previous draft claimed TCP may neither be applicable
nor appropriate. This claim needs to be better explained and researched
as part of the aforementioned update.

Goals and Milestones
--------------------
July 2011    Update to draft-sandbakken-dispatch-bfcp-udp addressing
concerns 
             raised previously
July 2011    Present update to draft-sandbakken-dispatch-bfcp-udp at
IETF 81

Cheers,
Charles