IETF Logo Mail Archive

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

JP Vasseur <jvasseur@cisco.com> Sat, 05 November 2005 18:10 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 1EYSVG-0005F3-6h; Sat, 05 Nov 2005 13:10:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EYSVE-0005Ev-P0 for routing-discussion@megatron.ietf.org; Sat, 05 Nov 2005 13:10:56 -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 NAA12544 for <routing-discussion@ietf.org>; Sat, 5 Nov 2005 13:10:31 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EYSkT-00080o-6i for routing-discussion@ietf.org; Sat, 05 Nov 2005 13:26:42 -0500
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-1.cisco.com with ESMTP; 05 Nov 2005 10:10:47 -0800
X-IronPort-AV: i="3.97,294,1125903600"; d="scan'208"; a="672151200:sNHT25681924"
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id jA5IAhOx000735; Sat, 5 Nov 2005 10:10:44 -0800 (PST)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sat, 5 Nov 2005 13:10:43 -0500
Received: from [192.168.1.102] ([10.86.242.39]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sat, 5 Nov 2005 13:10:41 -0500
In-Reply-To: <00e901c5dee8$5bfcf2d0$4e919ed9@Puppy>
References: <00e901c5dee8$5bfcf2d0$4e919ed9@Puppy>
Mime-Version: 1.0 (Apple Message framework v734)
X-Priority: 3
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <B4C332C3-BABD-4103-8DC8-FC78D70BCD10@cisco.com>
Content-Transfer-Encoding: 7bit
From: JP Vasseur <jvasseur@cisco.com>
Date: Sat, 05 Nov 2005 13:09:54 -0500
To: Adrian Farrel <adrian@olddog.co.uk>
X-Mailer: Apple Mail (2.734)
X-OriginalArrivalTime: 05 Nov 2005 18:10:43.0025 (UTC) FILETIME=[3C72A410:01C5E234]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
Cc: routing-discussion@ietf.org
Subject: Re: 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

Hi Adrian,

On Nov 1, 2005, at 6:42 AM, Adrian Farrel wrote:

> 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.
>

Personally in strong support.

JP.

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

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

v2.23.0 | Report a Bug | By Email