Mailing-List: contact etch-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: etch-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of jliau@cisco.com designates
 171.68.10.86 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Etch Name Service Proposal
Date: Mon, 5 Jan 2009 11:43:29 -0800
Message-ID: 
 <4C0FAAC489C8B74F96BEAD85EAEB262507C64089@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <494FFE3B.90008@cisco.com>
Thread-Topic: Etch Name Service Proposal
Thread-Index: Aclkd2iUZook839WRtKfNeSzmWhf/AK9lwXA
References: <494FFE3B.90008@cisco.com>
From: "J.D. Liau (jliau)" <jliau@cisco.com>
To: <etch-dev@incubator.apache.org>

Looks great, should be vary helpful to large deployment.=20

-----Original Message-----
From: Scott Comer (sccomer)=20
Sent: Monday, December 22, 2008 2:53 PM
To: etch-dev@incubator.apache.org
Subject: Etch Name Service Proposal

this is a proposal for a name service for etch. there is a text document
describing the name service and rationale, and a proposed etch service
idl.

the intention is to define the service interface, implement an etch
scheme which uses it, and produce a reference implementation of the
service which can support simple deployments and also test the etch
scheme.

i will also post this to the wiki. please review and comment here.

scott out