Re: [OPSEC] minutes part 2

Joel Jaeggli <joelja@bogus.com> Tue, 23 December 2008 23:41 UTC

Return-Path: <opsec-bounces@ietf.org>
X-Original-To: opsec-archive@optimus.ietf.org
Delivered-To: ietfarch-opsec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC9DE3A67F2; Tue, 23 Dec 2008 15:41:49 -0800 (PST)
X-Original-To: opsec@core3.amsl.com
Delivered-To: opsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CE783A67A5 for <opsec@core3.amsl.com>; Tue, 23 Dec 2008 15:41:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X4bucE5js5Lr for <opsec@core3.amsl.com>; Tue, 23 Dec 2008 15:41:47 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 12B3E3A67F2 for <opsec@ietf.org>; Tue, 23 Dec 2008 15:41:46 -0800 (PST)
Received: from [192.168.11.143] (c-67-171-158-173.hsd1.wa.comcast.net [67.171.158.173]) (authenticated bits=0) by nagasaki.bogus.com (8.14.3/8.14.3) with ESMTP id mBNNfXig035837 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 23 Dec 2008 23:41:34 GMT (envelope-from joelja@bogus.com)
Message-ID: <4951772C.303@bogus.com>
Date: Tue, 23 Dec 2008 15:41:32 -0800
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Thunderbird 2.0.0.18 (X11/20081119)
MIME-Version: 1.0
To: R Atkinson <ran.atkinson@gmail.com>
References: <EC3F7E1D-F7C8-484A-A0C0-1A25E79AD86E@extremenetworks.com> <92c950310812161620j7d8aaa16m553940edadbe6d8f@mail.gmail.com> <12201E12-8A0B-4FBE-95A9-5C8B23DA46EC@gmail.com> <92c950310812171704x76e374bbv1bd74d74f5ca755b@mail.gmail.com> <C2E84336-3E35-4D68-BD81-3E222CD681F2@gmail.com> <92c950310812180801i10ac5f07l4ed58c87778ca9ba@mail.gmail.com> <49513A5B.7030307@bogus.com> <81B44188-AB93-40D9-B335-09A0CC466CEF@gmail.com>
In-Reply-To: <81B44188-AB93-40D9-B335-09A0CC466CEF@gmail.com>
X-Enigmail-Version: 0.95.7
X-Virus-Scanned: ClamAV 0.93.3/8795/Tue Dec 23 17:58:21 2008 on nagasaki.bogus.com
X-Virus-Status: Clean
Cc: opsec@ietf.org
Subject: Re: [OPSEC] minutes part 2
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/opsec>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: opsec-bounces@ietf.org
Errors-To: opsec-bounces@ietf.org

R Atkinson wrote:
> 
> On  23 Dec 2008, at 14:22, Joel Jaeggli wrote:
>> Just to be clear here... since the context disappeared some messages
>> back...
>>
>> RFC 2154 is what is being referred to here?
>>
>> Do we have deployments or operational experience to draw on?
> 
> Joel,
> 
> I am told there is limited use of RFC-2154 within US DoD.
> 
> I gather (from the URL provided earlier) that at least one
> commercial router vendor supports it.
> 
> Note that I have not and do not propose that this WG recommend
> RFC-2154 for general use at this time.

I agree...

>  It would be unusual
> to recommend an experimental status RFC for widespread use.
> I suspect many folks would agree with that.

As a foil for a thought experiment it's  fine.

We continue to demonstrate that the problem space has not been fully
exhausted.

> I have proposed, and continue to believe, that a document talking
> about issues with IGP authentication mechanisms (and there are
> lots of potential issues with IGP authentication at present)
> ought also include analysis and discussion of RFC-2154.

noted

>  If
> RFC-2154 has issues, those would be useful to know in detail,
> and such a document would be an appropriate place for such
> information.
> 
> Cheers,
> 
> Ran
> 
> _______________________________________________
> OPSEC mailing list
> OPSEC@ietf.org
> https://www.ietf.org/mailman/listinfo/opsec
> 

_______________________________________________
OPSEC mailing list
OPSEC@ietf.org
https://www.ietf.org/mailman/listinfo/opsec