RE: [EME] First cut at eme requirements

"Paul Francis" <francis@cs.cornell.edu> Mon, 04 December 2006 16:38 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrGq6-0004mQ-AR; Mon, 04 Dec 2006 11:38:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrGq5-0004mK-FM for eme@irtf.org; Mon, 04 Dec 2006 11:38:45 -0500
Received: from exchfenlb-2.cs.cornell.edu ([128.84.97.34] helo=exchfe2.cs.cornell.edu) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrGq4-0006Sz-6v for eme@irtf.org; Mon, 04 Dec 2006 11:38:45 -0500
Received: from EXCHANGE2.cs.cornell.edu ([128.84.96.44]) by exchfe2.cs.cornell.edu with Microsoft SMTPSVC(6.0.3790.1830); Mon, 4 Dec 2006 11:38:43 -0500
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
Subject: RE: [EME] First cut at eme requirements
Date: Mon, 4 Dec 2006 11:38:43 -0500
Message-ID: <E6F7A586E0A3F94D921755964F6BE00672E288@EXCHANGE2.cs.cornell.edu>
In-Reply-To: <6BF80459-3D1F-4FB2-AD1D-B90B92FCAFF6@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [EME] First cut at eme requirements
Thread-Index: AccVo5/wHTLI17TfR16cPZvC47HtGQCHZY+A
From: "Paul Francis" <francis@cs.cornell.edu>
To: "Mark Baugher" <mbaugher@cisco.com>
X-OriginalArrivalTime: 04 Dec 2006 16:38:43.0839 (UTC) FILETIME=[A98330F0:01C717C2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: eme <eme@irtf.org>
X-BeenThere: eme@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: end-middle-end research group <eme.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/eme>, <mailto:eme-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/eme>
List-Post: <mailto:eme@irtf.org>
List-Help: <mailto:eme-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/eme>, <mailto:eme-request@irtf.org?subject=subscribe>
Errors-To: eme-bounces@irtf.org

Good question.  Probably we should have a statement on scale (i.e. global).
As for the other two, I want to avoid "obvious" kinds of requirement (i.e.
"the system must be robust").  Having said that, I'm certainly aware that one
can construct quite specific robustness statements ("the system must be able
to tolerate the loss of up to three servers with zero measureable performance
degradation") that can have a major impact on system design.

But am open to discussion on this.  Do you have any thoughts on how such
requirements would be crafted?

PF

 

-----Original Message-----
From: Mark Baugher [mailto:mbaugher@cisco.com] 
Sent: Friday, December 01, 2006 6:47 PM
To: Paul Francis
Cc: eme
Subject: Re: [EME] First cut at eme requirements

What are your thoughts on robustness, scalability and fault-recovery
requirements?

Mark

On Nov 28, 2006, at 7:30 AM, Paul Francis wrote:

>
> Gang,
>
> Attached is a rough draft of a requirements document for EME.  This is 
> meant to be the union of the requirements that Handley and I presented 
> at the BOF in Montreal.  The goal here is to be ambitious but 
> realistic, and to try to limit ourselves to basic and important 
> requirements.  This really is a rough draft, and is meant to motivate 
> and focus discussion.
>
> Mark W, could you post on the wiki when you get a chance?
>
> Thanks,
>
> PF (and Saikat)
> <eme-requirements.txt>
> _______________________________________________
> EME mailing list
> EME@irtf.org
> https://www1.ietf.org/mailman/listinfo/eme

_______________________________________________
EME mailing list
EME@irtf.org
https://www1.ietf.org/mailman/listinfo/eme