IETF Logo Mail Archive

Re: [OPSEC] minutes part 2

"Glen Kent" <glen.kent@gmail.com> Thu, 18 December 2008 01:18 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 AAA4B3A6B4F; Wed, 17 Dec 2008 17:18:04 -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 6C4803A694E for <opsec@core3.amsl.com>; Wed, 17 Dec 2008 17:18:03 -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 EBltE6Ko5qoi for <opsec@core3.amsl.com>; Wed, 17 Dec 2008 17:18:02 -0800 (PST)
Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.190]) by core3.amsl.com (Postfix) with ESMTP id 6E71A3A66B4 for <opsec@ietf.org>; Wed, 17 Dec 2008 17:18:02 -0800 (PST)
Received: by mu-out-0910.google.com with SMTP id w1so115281mue.9 for <opsec@ietf.org>; Wed, 17 Dec 2008 17:17:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=XDKoRGywCfyOBD5V3N/wuSZPww+aunNpVuJmfJRI5DA=; b=QnxtBPqlQVFR2109fIzak13a3Um3PcFro45PT46gHO+Ygrm3JQCZDVpUbnThU7RbKR 3F/4YTXTDJHXZLNejSw5kY/WKb/KFldYVVkDhTDLZQhtVDar3M69A64M0fbd5hUfK9oV Rp8K+40vyNXk7VnDvaeC9oIRWrANDQpvbrwzU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=vsguO0T2ds/eUWaJsiAz6lc+VX6QZauFEidUsRNE85TgYyehJAIx7GoLJznNMA1DTT zuRlyZBMDp+I1jTTDUFLXxbgrqyw2Lk3ScA6+zTXhz+BCfiqZwtp+0DMHip5h9w/XaFs +F/3zu85CsVHZXGVnqUBewQ21nLbwCDKcobzQ=
Received: by 10.103.24.11 with SMTP id b11mr531787muj.76.1229563073644; Wed, 17 Dec 2008 17:17:53 -0800 (PST)
Received: by 10.103.160.12 with HTTP; Wed, 17 Dec 2008 17:17:53 -0800 (PST)
Message-ID: <92c950310812171717s437509a4p4d56cf4c697529a@mail.gmail.com>
Date: Thu, 18 Dec 2008 06:47:53 +0530
From: Glen Kent <glen.kent@gmail.com>
To: R Atkinson <ran.atkinson@gmail.com>
In-Reply-To: <69BA9195-6869-45F1-832F-9040901F0C9F@gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <14198D76-AA32-4E02-9425-0700ED57B07B@gmail.com> <77ead0ec0812161759g4900bd98h6ad6c07bb0d81fe3@mail.gmail.com> <69BA9195-6869-45F1-832F-9040901F0C9F@gmail.com>
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

>>
>> No, it is not discussed in the document. The RFC you mention is an
>> Experimental RFC. The draft talks about "Issues with Existing
>> Cryptographic Mechanisms with Routing Protocols". We can discuss the
>> same however (though I would feel it may not exactly fit the draft).
>
> It would be helpful to discuss also, as that is an IGP authentication
> mechanism that we have today and that could be used.  I'm told that
> there is at least one implementation, although I'm unclear on how
> available that implementation might be.

Is there anyone in this list who is aware of 2154 being deployed. Is
there any interest in this WG to include 2154? If none, then this can
be safely ignored.

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

v2.23.0 | Report a Bug | By Email