IETF Logo Mail Archive

Re: draft-atlas-rtgwg-ipfrr-ip-mib-00.txt

"Adrian Farrel" <adrian@olddog.co.uk> Fri, 10 December 2004 09:02 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24958 for <rtgwg-web-archive@ietf.org>; Fri, 10 Dec 2004 04:02:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcgmT-000871-CY for rtgwg-web-archive@ietf.org; Fri, 10 Dec 2004 04:09:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CcgeF-0001w8-9D; Fri, 10 Dec 2004 04:01:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CcgZZ-0000Ux-Ht for rtgwg@megatron.ietf.org; Fri, 10 Dec 2004 03:56:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24711 for <rtgwg@ietf.org>; Fri, 10 Dec 2004 03:56:17 -0500 (EST)
Received: from ranger.systems.pipex.net ([62.241.162.32]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ccggg-00080z-0X for rtgwg@ietf.org; Fri, 10 Dec 2004 04:03:43 -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 B9669E0002F5; Fri, 10 Dec 2004 08:55:43 +0000 (GMT)
Received: from Puppy ([217.158.145.27] RDNS failed) by dnni.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 10 Dec 2004 08:55:42 +0000
Message-ID: <00a101c4de96$2657de90$4f919ed9@Puppy>
From: Adrian Farrel <adrian@olddog.co.uk>
To: Alia Atlas <aatlas@avici.com>
References: <24685528.20041109092848@psg.com> <5.1.0.14.2.20041209105543.029b1d58@pop.avici.com>
Date: Fri, 10 Dec 2004 08:08:49 -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: 10 Dec 2004 08:55:43.0355 (UTC) FILETIME=[07FABCB0:01C4DE96]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit
Cc: rtgwg@ietf.org
Subject: Re: draft-atlas-rtgwg-ipfrr-ip-mib-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit

Alia,

> >4. I agree that write access will be needed for some objects.
>
> Do you think we need write access into both the ipFrrAltTable and the
> ipFrrNoAltTable?  I primarily see this as being useful for static
routes.

Well, I don't have RFC2096-update to hand, but I suspect that you need
similar access as is provided to inetCidrRouteTable. If you're playing
with static routes then these are exactly what I would expect to see
configurable through write access. (You wouldn't want to have an
operator writing all over dynamic routes!)

Cheers,
Adrian


_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg

v2.23.0 | Report a Bug | By Email