IETF Logo Mail Archive

Re: Another twist on my proposal

Joel Halpern <jhalpern@newbridge.com> Fri, 05 May 1995 14:37 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03971; 5 May 95 10:37 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa03967; 5 May 95 10:37 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa07322; 5 May 95 10:37 EDT
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03960; 5 May 95 10:37 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa03956; 5 May 95 10:37 EDT
Received: from Newbridge.COM by CNRI.Reston.VA.US id aa07314; 5 May 95 10:37 EDT
Received: from thor.Newbridge.com by nbkanata.newbridge.com (4.1/SMI-4.1) id AA10850; Fri, 5 May 95 10:37:21 EDT
Received: from mako.newbridge.com by thor.Newbridge.com (4.1/SMI-4.0) id AA04318; Fri, 5 May 95 10:37:42 EDT
Received: from lobster.Newbridge.COM by mako.newbridge.com (4.1/SMI-4.1) id AA16218; Fri, 5 May 95 10:36:34 EDT
Received: by lobster.Newbridge.COM (5.0/SMI-SVR4) id AA25861; Fri, 5 May 1995 10:37:01 +0500
Date: Fri, 05 May 1995 10:37:01 +0500
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Joel Halpern <jhalpern@newbridge.com>
Message-Id: <9505051437.AA25861@lobster.Newbridge.COM>
To: iesg@CNRI.Reston.VA.US
Subject: Re: Another twist on my proposal
X-Sun-Charset: US-ASCII
Content-Length: 504

Actually, even under Mike's proposed setup, I would have allowed DLSw as an
Informational RFC. (RFC1795, the one referred to in the article Mike quoted.)
This suggests in fact that in the particular instance in question the
proposed change would not help.

(For context, my reasoning on this document is that it is a good definition
of a way to run an important protocol family over the internet.  Customers
actively need this.)

Yours,
Joel M. Halpern				jhalpern@newbridge.com
Newbridge Networks Inc.

v2.23.0 | Report a Bug | By Email