[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: I-D ACTION:draft-farrel-rtg-manageability-requirements-00.txt



[not sure if authors/and alex are on ops-area list, so I cc: them]

It is an interesting read.
I also know that various people think that we have too many "mandatory"
sections already. So how does that jive? Has the RTG community reacted 
already? In principle I think it would be good to have sections on
"Considerations for managebility".

I then wonder, why would this just apply to the docs from the RTG area?

W.r.t. sect 2.2, I am not sure I understand the differene between
the first 2 bullets.

W.r.t. sect 3.x, you may want to reference RFC3444.

Bert

> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> Sent: Tuesday, October 12, 2004 20:12
> To: Ops-Area (E-mail)
> Subject: FW: I-D
> ACTION:draft-farrel-rtg-manageability-requirements-00.txt
> 
> 
>  believe that this Internet-Draft is worth being read and 
> commented by the OPS area. 
> 
> Regards,
> 
> Dan
> 
> 
> 
> -----Original Message-----
> From: i-d-announce-bounces@ietf.org 
> [mailto:i-d-announce-bounces@ietf.org]On Behalf Of 
> Internet-Drafts@ietf.org
> Sent: 12 October, 2004 10:05 PM
> To: i-d-announce@ietf.org
> Subject: I-D ACTION:draft-farrel-rtg-manageability-requirements-00.txt
> 
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> 
> 
> 	Title		: Requirements for Manageability 
> Sections in Routing
> 			  Area Drafts
> 	Author(s)	: A. Farrel, et al.
> 	Filename	: 
> draft-farrel-rtg-manageability-requirements-00.txt
> 	Pages		: 6
> 	Date		: 2004-10-12
> 	
> It has often been the case that manageability considerations have
>    been retrofitted to protocols. This is sub-optimal.
> 
>    Similarly, new protocols or protocol extensions are frequently
>    designed without due consideration of manageability requirements.
> 
>    This document specifies the requirement for all new Routing Area
>    Internet-Drafts to include an "Manageability 
> Considerations" section,
>    and gives guidance on what that section should contain.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-farrel-rtg-manageabi
> lity-requirements-00.txt
> 
> To remove yourself from the I-D Announcement list, send a message to 
> i-d-announce-request@ietf.org with the word unsubscribe in 
> the body of the message.  
> You can also visit 
https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-farrel-rtg-manageability-requirements-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-farrel-rtg-manageability-requirements-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.