Re: IPv7 Selection Criteria

William Allen Simpson <bill.simpson@um.cc.umich.edu> Wed, 23 December 1992 19:41 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08487; 23 Dec 92 14:41 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa08481; 23 Dec 92 14:41 EST
Received: from babyoil.ftp.com by CNRI.Reston.VA.US id aa18981; 23 Dec 92 14:44 EST
Received: from vela.acs.oakland.edu by ftp.com with SMTP id AA08826; Wed, 23 Dec 92 14:41:26 -0500
Received: from via.ws07.merit.edu by vela.acs.oakland.edu with SMTP id AA10846 (5.65c+/IDA-1.4.4); Wed, 23 Dec 1992 14:41:00 -0500
Date: Wed, 23 Dec 1992 14:16:56 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: William Allen Simpson <bill.simpson@um.cc.umich.edu>
Message-Id: <859.bill.simpson@um.cc.umich.edu>
To: criteria@ftp.com
Reply-To: bsimpson@morningstar.com
Subject: Re: IPv7 Selection Criteria

> Hence, let me suggest explicitly distinguishing those criteria that
> have clinical benefit, but lack objective assessment, from those
> whose assessment can be made mechanical.  The clinical criteria could
> be in their own section, some sort of qualification explaining why they
> are included and how they should be used.
>
> Whatcha tink?
>

YES!

Add extensible, since the appearance of extensibility doesn't mean that
we will have any greater luck in migrating to the extended format than
we have of migrating this time.

Any claim of extensibility would have to show that there would be *NO*
negative effect when such a mechanism is added.  That is, a packet
either with or without an option would still reach the destination
eventually, just not necessarily with the guaranteed flow, for example.

Bill.Simpson@um.cc.umich.edu