draft-farrel-rtg-manageability-requirements-01.txt

"Adrian Farrel" <adrian@olddog.co.uk> Tue, 01 November 2005 13:35 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EWwIm-0005X1-Gz; Tue, 01 Nov 2005 08:35:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EWwIk-0005WY-7B for routing-discussion@megatron.ietf.org; Tue, 01 Nov 2005 08:35:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20623 for <routing-discussion@ietf.org>; Tue, 1 Nov 2005 08:35:26 -0500 (EST)
Received: from ranger.systems.pipex.net ([62.241.162.32]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EWwX7-0004Mq-Py for routing-discussion@ietf.org; Tue, 01 Nov 2005 08:50:39 -0500
Received: from dnni.com (81-178-2-190.dsl.pipex.com [81.178.2.190]) by ranger.systems.pipex.net (Postfix) with ESMTP id 6D306E000139 for <routing-discussion@ietf.org>; Tue, 1 Nov 2005 13:35:18 +0000 (GMT)
Received: from Puppy ([217.158.132.194] RDNS failed) by dnni.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 1 Nov 2005 13:27:01 +0000
Message-ID: <00e901c5dee8$5bfcf2d0$4e919ed9@Puppy>
From: Adrian Farrel <adrian@olddog.co.uk>
To: routing-discussion@ietf.org
Date: Tue, 01 Nov 2005 11:42:45 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-OriginalArrivalTime: 01 Nov 2005 13:27:01.0980 (UTC) FILETIME=[F17649C0:01C5DEE7]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
Subject: draft-farrel-rtg-manageability-requirements-01.txt
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org

Hi,

Following some mild interest two IETF's ago, we have updated this I-D.

The chief change is some fleshing out of the guidance for the content of
mandatory manageability sections, and the inclusion of an example from a
current I-D.

It seems to me that the Routing Area (under guidance of its ADs) now needs
to decide whether this is something we pursue and turn into a rule
(completing all of the details), or whether we should abandon the idea.

Thanks,
Adrian


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion