RE: Progressing: draft-farrel-rtg-manageability-requirements-01.txt

"Ash, Gerald R \(Jerry\), ALABS" <gash@att.com> Thu, 10 November 2005 19:33 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 1EaIB6-0008FK-3j; Thu, 10 Nov 2005 14:33:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EaIB3-0008Cm-F0 for routing-discussion@megatron.ietf.org; Thu, 10 Nov 2005 14:33:41 -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 OAA28422 for <routing-discussion@ietf.org>; Thu, 10 Nov 2005 14:33:11 -0500 (EST)
Received: from mail121.messagelabs.com ([216.82.241.195]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1EaIFI-0004wL-A2 for routing-discussion@ietf.org; Thu, 10 Nov 2005 14:38:09 -0500
X-VirusChecked: Checked
X-Env-Sender: gash@att.com
X-Msg-Ref: server-13.tower-121.messagelabs.com!1131650431!6822538!12
X-StarScan-Version: 5.5.9.1; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 2097 invoked from network); 10 Nov 2005 19:21:04 -0000
Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4) by server-13.tower-121.messagelabs.com with SMTP; 10 Nov 2005 19:21:04 -0000
Received: from kcclust06evs1.ugd.att.com (135.38.164.89) by attrh3i.attrh.att.com (7.2.052) id 435BB4FA00388B53; Thu, 10 Nov 2005 14:21:03 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 10 Nov 2005 13:20:32 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA09FA9657@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Progressing: draft-farrel-rtg-manageability-requirements-01.txt
Thread-Index: AcXmKTImi+gYCba+SQ2S8L9dXtwiLwAAfOsg
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: Adrian Farrel <adrian@olddog.co.uk>, routing-discussion@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: quoted-printable
Cc: Loa Andersson <loa@pi.se>, "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, Avri Doria <avri@acm.org>
Subject: RE: Progressing: draft-farrel-rtg-manageability-requirements-01.txt
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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

> Should we advance this work as a suggestion or BCP, or should
> we throw it out?

IMO we should advance to BCP, and require a manageability section.
Requiring the section will force the authors to give thoughtful
consideration to what the manageability requirements are for the
feature.

Thanks,
Jerry

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