Re: new version of the draft
Brian Carpenter CERN-CN <brian@dxcern.cern.ch> Wed, 16 December 1992 09:39 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01005; 16 Dec 92 4:39 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa00999; 16 Dec 92 4:39 EST
Received: from babyoil.ftp.com by CNRI.Reston.VA.US id aa03335; 16 Dec 92 4:41 EST
Received: from dxmint.cern.ch by ftp.com with SMTP id AA15769; Wed, 16 Dec 92 04:35:23 -0500
Received: by dxmint.cern.ch (5.65/DEC-Ultrix/4.3) id AA06579; Wed, 16 Dec 1992 10:35:12 +0100
Received: by dxcern.cern.ch (5.57/Ultrix3.0-C) id AA10663; Wed, 16 Dec 92 10:35:02 +0100
Message-Id: <9212160935.AA10663@dxcern.cern.ch>
Subject: Re: new version of the draft
To: kasten@ftp.com
Date: Wed, 16 Dec 1992 10:35:00 -0000
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Brian Carpenter CERN-CN <brian@dxcern.cern.ch>
Cc: criteria@ftp.com
In-Reply-To: <9212141902.AA23547@ftp.com>; from "Frank Kastenholz" at Dec 14, 92 2:02 pm
X-Mailer: ELM [version 2.3 PL11 CERN 11]
Hi, here are some *personal* comments on the December criteria draft. I hope to provide some more formal CERN comments asap. 5.1.9 Unique Naming I agree with the authors that this should not be a selection criterion. Now clearly, if for any proposal, it can be proved that the lack of unique (binary) names actually breaks the network than that proposal is no good. (Maybe we need a criterion "the protocol must not be broken" :-) For the record I raised my hand against this criterion at Washington. 5.2.1 Addressing Why isn't this section headed "multicasting"? I think the discussion should distinguish more clearly "multicasting for service location" from "multicast applications". The former is unnecessary and undesirable (e.g. see the IP over FibreChannel proposal for ARP without multicast) and the latter do not necessarily require multicast at the IP level. So (at the most) this is a SHOULD. 5.2.2 Extensibility Yes. No. My problem is that I don't understand what extensibility means, so I don't know if I need it. I raised the possible criterion of "compatibility with multiprotocol routers" and this was shot down without trace (but I still want it :-). But isn't it one form of extensibility? What are the others? This criterion needs work before I can judge whether it's a MUST, a SHOULD, or null. 5.2.7 Performance (place holder) I would express it as "not significantly slower than IPv4 on the same generation of hardware" and I think it's a MUST. Regards, Brian Carpenter CERN, brian@dxcern.cern.ch voice +41 22 767 4967, fax +41 22 767 7155 | This is a personal opinion, and not an endorsement of | | PIP/EIP, SIP/IPAE, Nimrod, or TUBA. |
- new version of the draft Frank Kastenholz
- Re: new version of the draft John Curran
- Re: new version of the draft Brian Carpenter CERN-CN
- Re: new version of the draft Frank Kastenholz
- Re: new version of the draft Frank Kastenholz
- Re: new version of the draft Brian Carpenter CERN-CN
- Re: new version of the draft Steve Deering
- Re: new version of the draft Brian Carpenter CERN-CN
- Re: new version of the draft John Curran
- Re: new version of the draft Tony Li
- Re: new version of the draft Frank Kastenholz
- Re: new version of the draft Scott_Brim
- new version of the draft Tony Li
- Re: new version of the draft Beast (Donald E. Eastlake, 3rd)