[bfcpbis] Implementation status of the drafts

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Mon, 21 January 2013 17:57 UTC

Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64E8A21F8620 for <bfcpbis@ietfa.amsl.com>; Mon, 21 Jan 2013 09:57:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.249
X-Spam-Level:
X-Spam-Status: No, score=-108.249 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 zxbB8HlkZRMe for <bfcpbis@ietfa.amsl.com>; Mon, 21 Jan 2013 09:57:58 -0800 (PST)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [62.23.212.42]) by ietfa.amsl.com (Postfix) with ESMTP id B912821F85B3 for <bfcpbis@ietf.org>; Mon, 21 Jan 2013 09:57:57 -0800 (PST)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r0LHvp55021420 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <bfcpbis@ietf.org>; Mon, 21 Jan 2013 18:57:55 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Mon, 21 Jan 2013 18:57:49 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Date: Mon, 21 Jan 2013 18:57:45 +0100
Thread-Topic: Implementation status of the drafts
Thread-Index: Ac34ANE8S0iCTAbiSmmgZzXRaygF5A==
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE20D7468B0DC@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84
Subject: [bfcpbis] Implementation status of the drafts
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bfcpbis>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jan 2013 17:57:58 -0000

(As WG cochairs)

For the publication request, we are asked to give an indication of the implementation status of the drafts, so that the IESG can identify whether the protocol as described actually works in practice.

We have been told that there have been some working implementations in the past, but it would be useful to get an update.

Could I ask people therefore to reply to the list, or if you prefer, directly to the WG chairs, identifying what if anything has been implemented from the two bfcpbis drafts (and at what version).

As this is a replacement of the original BFCP documents RFC 4582 and RFC 4583, it would also be useful to have indications of the implementation of those documents.

Regards

Keith