Re: editorial comments on routing document

Steve Kille <> Fri, 23 September 1994 15:41 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa04490; 23 Sep 94 11:41 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa04486; 23 Sep 94 11:41 EDT
Received: from by CNRI.Reston.VA.US id aa10409; 23 Sep 94 11:41 EDT
Received: from by; Fri, 23 Sep 94 10:39:20 -0600
Received: by; Fri, 23 Sep 94 10:40:54 -0500
X-From: Fri Sep 23 10:40 CDT 1994
Received: from by; Fri, 23 Sep 94 10:40:50 -0500
Received: from by; Fri, 23 Sep 94 10:40:37 -0500
To: Allan Cargille <>
Subject: Re: editorial comments on routing document
Phone: +44-81-332-9091
In-reply-to: Your message of Mon, 22 Aug 1994 18:59:00 -0500. <>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <>
Date: Fri, 23 Sep 1994 16:41:25 +0100
Message-ID: <>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Steve Kille <>


Thanks for these very useful comments.   I'd also like to thank Alan
Young, who has taken a full pass over the documents.   This work will
be much appreciated by others that come to the documents.  A few

 - Strong Authentication is defined
 - I don't think that it is usual or sensible for RFC authors to include
	fax numbers

 - There are a couple of places in the ASN.1 where you note
	inconsistencies of naming convention.    I decided to leave these,
	as it is quite legal and a certain sweet disorder.....

 - You suggest that SecurityError should be changed to Error.  I disagree,
	but note that I have clarified the text in that section.
	Could you review this again?

 - I have retained a number of notes in the text.  In line with the
discussions with John Klensin, it seems desirable to get this spec out
ASAP.  I think that it is better to leave notes about issues which
still need consideration, than to present this work as perfection.

I've now finished editing all four of the documents.    Three have
been submitted as I-Ds, and should immediately go formard into the RFC
process.   The big document is being reviewed by a small team
(including you), and will then be submitted.