[ESDS] Minneapolis BOF update and next steps
Ali Rezafard <arezafar@ca.afilias.info> Mon, 03 November 2008 15:25 UTC
Return-Path: <esds-bounces@ietf.org>
X-Original-To: esds-archive@optimus.ietf.org
Delivered-To: ietfarch-esds-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A341728C27E; Mon, 3 Nov 2008 07:25:53 -0800 (PST)
X-Original-To: esds@core3.amsl.com
Delivered-To: esds@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6FBB028C27D for <esds@core3.amsl.com>; Mon, 3 Nov 2008 07:25:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.265
X-Spam-Level:
X-Spam-Status: No, score=-6.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aNNg2so0Jp-J for <esds@core3.amsl.com>; Mon, 3 Nov 2008 07:25:51 -0800 (PST)
Received: from outbound.afilias.info (outbound.afilias.info [69.46.124.26]) by core3.amsl.com (Postfix) with ESMTP id D9FAC28C294 for <esds@ietf.org>; Mon, 3 Nov 2008 07:25:01 -0800 (PST)
Received: from bmp-336-ms505.wa.yyz2.afilias-ops.info ([10.50.129.111] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.69) (envelope-from <arezafar@ca.afilias.info>) id 1Kx1IU-0003YA-5V for esds@ietf.org; Mon, 03 Nov 2008 15:24:54 +0000
Message-Id: <375A1677-EDDF-490B-9D7B-6C2029D1FE8E@ca.afilias.info>
From: Ali Rezafard <arezafar@ca.afilias.info>
To: esds@ietf.org
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 03 Nov 2008 10:24:58 -0500
X-Mailer: Apple Mail (2.929.2)
X-Authenticated: True
Subject: [ESDS] Minneapolis BOF update and next steps
X-BeenThere: esds@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion of the ESDS \(Extensible Supplychain Discovery Service\)" <esds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/esds>, <mailto:esds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/esds>
List-Post: <mailto:esds@ietf.org>
List-Help: <mailto:esds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/esds>, <mailto:esds-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: esds-bounces@ietf.org
Errors-To: esds-bounces@ietf.org
Dear ESDS members, It has been recommended to us not to hold our BOF at the coming November 2008 IETF gathering. We need to demonstrate significant progress in identifying and addressing challenges in our problem domain. The IETF process gives best results when there is a constituency of participating members. So we encourage you to comment on the posts and share your thoughts, Discovery Service is still taking shape and any questions/comments would have an influence on the outcome. Our current next steps for the community are to refine the ESDS problem statement with the goal of making it more generically useful and applicable to a larger domain of applicability than only the supply chain. The second step would be to write a whitepaper on combining ESDS with documents from BRIDGE WP02 (Serial Level Lookup Service) and WP04 (Security). The whitepaper would outline a DS with integrated access control and a robust security model. Our community is constantly growing, three new members have joined us in the last month. We look forward to feedback from the ESDS community on the mailing list. Best Regards, Ali _______________________________________________ ESDS mailing list ESDS@ietf.org https://www.ietf.org/mailman/listinfo/esds
- [ESDS] Minneapolis BOF update and next steps Ali Rezafard