From msec-bounces@ietf.org  Fri Sep 19 16:57:49 2008
Return-Path: <msec-bounces@ietf.org>
X-Original-To: msec-archive@optimus.ietf.org
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1781A3A68B1;
	Fri, 19 Sep 2008 16:57:49 -0700 (PDT)
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 903AB3A68B1
	for <msec@core3.amsl.com>; Fri, 19 Sep 2008 16:57:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 dSs8CFaawwoK for <msec@core3.amsl.com>;
	Fri, 19 Sep 2008 16:57:46 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id D81013A6868
	for <msec@ietf.org>; Fri, 19 Sep 2008 16:57:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,433,1217808000"; d="scan'208";a="80226202"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 19 Sep 2008 23:57:58 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m8JNvwJ8007759
	for <msec@ietf.org>; Fri, 19 Sep 2008 16:57:58 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m8JNvwcq003888
	for <msec@ietf.org>; Fri, 19 Sep 2008 23:57:58 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 Sep 2008 16:57:57 -0700
Received: from [128.107.163.243] ([128.107.163.243]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 Sep 2008 16:57:57 -0700
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <CCE8A2F5-D341-4C71-8358-FAE264B3CC59@cisco.com>
To: msec@ietf.org
From: Brian Weis <bew@cisco.com>
Date: Fri, 19 Sep 2008 16:59:28 -0700
X-Mailer: Apple Mail (2.753.1)
X-OriginalArrivalTime: 19 Sep 2008 23:57:57.0776 (UTC)
	FILETIME=[8A411900:01C91AB3]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=356; t=1221868678; x=1222732678;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=bew@cisco.com;
	z=From:=20Brian=20Weis=20<bew@cisco.com>
	|Subject:=20WGLC=20on=20draft-ietf-msec-tesla-for-alc-norm-
	05.txt |Sender:=20;
	bh=cmFZlsqRd7ytLawmI2qn+StDdHI5m9583g1CLmL52d0=;
	b=IYqBisXkNtoVn4qtdqIJAeIcER3dNd0m4CeXnowo1e55Ia3IgkSmqjZG4R
	cyXI8V7wgtEzrRVel0aoO80XES8kudL9zC1zYWA5NQeiYXNzuFZj6Flq72sH
	/4ZTDy/ySi;
Authentication-Results: sj-dkim-2; header.From=bew@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Subject: [MSEC] WGLC on draft-ietf-msec-tesla-for-alc-norm-05.txt
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org

Folks,

At the last MSEC WG meeting, the consensus was to take draft-ietf- 
msec-tesla-for-alc-norm-05.txt to Working Group last call. Please  
review and send your comments to the MSEC WG (msec@ietf.org) list  
before Oct 3, 2008. Please feel free to send any private concerns to  
the chairs or the shepherding AD.

Thanks,
Brian & Lakshminath

_____From msec-bounces@ietf.org  Fri Sep 19 16:57:49 2008
Return-Path: <msec-bounces@ietf.org>
X-Original-To: msec-archive@lists.ietf.org
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1781A3A68B1;
	Fri, 19 Sep 2008 16:57:49 -0700 (PDT)
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 903AB3A68B1
	for <msec@core3.amsl.com>; Fri, 19 Sep 2008 16:57:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 dSs8CFaawwoK for <msec@core3.amsl.com>;
	Fri, 19 Sep 2008 16:57:46 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id D81013A6868
	for <msec@ietf.org>; Fri, 19 Sep 2008 16:57:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,433,1217808000"; d="scan'208";a="80226202"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 19 Sep 2008 23:57:58 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m8JNvwJ8007759
	for <msec@ietf.org>; Fri, 19 Sep 2008 16:57:58 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m8JNvwcq003888
	for <msec@ietf.org>; Fri, 19 Sep 2008 23:57:58 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 Sep 2008 16:57:57 -0700
Received: from [128.107.163.243] ([128.107.163.243]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 Sep 2008 16:57:57 -0700
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <CCE8A2F5-D341-4C71-8358-FAE264B3CC59@cisco.com>
To: msec@ietf.org
From: Brian Weis <bew@cisco.com>
Date: Fri, 19 Sep 2008 16:59:28 -0700
X-Mailer: Apple Mail (2.753.1)
X-OriginalArrivalTime: 19 Sep 2008 23:57:57.0776 (UTC)
	FILETIME=[8A411900:01C91AB3]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=356; t=1221868678; x=1222732678;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=bew@cisco.com;
	z=From:=20Brian=20Weis=20<bew@cisco.com>
	|Subject:=20WGLC=20on=20draft-ietf-msec-tesla-for-alc-norm-
	05.txt |Sender:=20;
	bh=cmFZlsqRd7ytLawmI2qn+StDdHI5m9583g1CLmL52d0=;
	b=IYqBisXkNtoVn4qtdqIJAeIcER3dNd0m4CeXnowo1e55Ia3IgkSmqjZG4R
	cyXI8V7wgtEzrRVel0aoO80XES8kudL9zC1zYWA5NQeiYXNzuFZj6Flq72sH
	/4ZTDy/ySi;
Authentication-Results: sj-dkim-2; header.From=bew@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Subject: [MSEC] WGLC on draft-ietf-msec-tesla-for-alc-norm-05.txt
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org

Folks,

At the last MSEC WG meeting, the consensus was to take draft-ietf- 
msec-tesla-for-alc-norm-05.txt to Working Group last call. Please  
review and send your comments to the MSEC WG (msec@ietf.org) list  
before Oct 3, 2008. Please feel free to send any private concerns to  
the chairs or the shepherding AD.

Thanks,
Brian & Lakshminath

_______________________________________________
MSEC mailing list
MSEC@ietf.org
https://www.ietf.org/mailman/listinfo/msec


__________________________________________
MSEC mailing list
MSEC@ietf.org
https://www.ietf.org/mailman/listinfo/msec


From msec-bounces@ietf.org  Mon Sep 22 17:51:28 2008
Return-Path: <msec-bounces@ietf.org>
X-Original-To: msec-archive@lists.ietf.org
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D10A93A68EF;
	Mon, 22 Sep 2008 17:51:28 -0700 (PDT)
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BE48A3A68EF
	for <msec@core3.amsl.com>; Mon, 22 Sep 2008 17:51:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 f28phjW-dj7Z for <msec@core3.amsl.com>;
	Mon, 22 Sep 2008 17:51:27 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 249EB3A6826
	for <msec@ietf.org>; Mon, 22 Sep 2008 17:51:27 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,449,1217808000"; d="scan'208";a="160596662"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 23 Sep 2008 00:51:29 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m8N0pTnW012572
	for <msec@ietf.org>; Mon, 22 Sep 2008 17:51:29 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m8N0pTJp018931
	for <msec@ietf.org>; Tue, 23 Sep 2008 00:51:29 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 22 Sep 2008 17:51:28 -0700
Received: from [128.107.163.243] ([128.107.163.243]) by
	xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 22 Sep 2008 17:51:28 -0700
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <A13A762E-DA41-4363-A9A0-F3F4B35BA0F7@cisco.com>
To: msec@ietf.org
From: Brian Weis <bew@cisco.com>
Date: Mon, 22 Sep 2008 17:53:03 -0700
X-Mailer: Apple Mail (2.753.1)
X-OriginalArrivalTime: 23 Sep 2008 00:51:28.0781 (UTC)
	FILETIME=[8366D3D0:01C91D16]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=289; t=1222131089; x=1222995089;
	c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=bew@cisco.com;
	z=From:=20Brian=20Weis=20<bew@cisco.com>
	|Subject:=20Minneapolis=20Meeting |Sender:=20;
	bh=ty0Yj3E0MaQ0IlNo6qGlFa50fTc/cKdQqjpqo/bXMuo=;
	b=YeYvvlAWOPO8LPmyPkp3o6s8qgg/1YZ9AYYjiz1Zr6huIlHc8Ja2KfNgOw
	fWOPTJgxHF/u1pB286QiawNeEfmbdRjHwMdc/EarC3EGvsD3Ab4v8tXzA00x
	oM7J7PoW9F;
Authentication-Results: sj-dkim-3; header.From=bew@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Subject: [MSEC] Minneapolis Meeting
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org

Folks,

We're currently planning a 1 hour MSEC meeting in Minneapolis. If you  
have an agenda item, please send a note to Lakshminath and myself.

Thanks,
Brian

-- 
Brian Weis
Router/Switch Security Group, ARTG, Cisco Systems
Telephone: +1 408 526 4796
Email: bew@cisco.com

_______________________________________________
MSEC mailing list
MSEC@ietf.org
https://www.ietf.org/mailman/From msec-bounces@ietf.org  Mon Sep 22 17:51:28 2008
Return-Path: <msec-bounces@ietf.org>
X-Original-To: msec-archive@optimus.ietf.org
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D10A93A68EF;
	Mon, 22 Sep 2008 17:51:28 -0700 (PDT)
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BE48A3A68EF
	for <msec@core3.amsl.com>; Mon, 22 Sep 2008 17:51:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 f28phjW-dj7Z for <msec@core3.amsl.com>;
	Mon, 22 Sep 2008 17:51:27 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 249EB3A6826
	for <msec@ietf.org>; Mon, 22 Sep 2008 17:51:27 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,449,1217808000"; d="scan'208";a="160596662"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 23 Sep 2008 00:51:29 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m8N0pTnW012572
	for <msec@ietf.org>; Mon, 22 Sep 2008 17:51:29 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m8N0pTJp018931
	for <msec@ietf.org>; Tue, 23 Sep 2008 00:51:29 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 22 Sep 2008 17:51:28 -0700
Received: from [128.107.163.243] ([128.107.163.243]) by
	xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 22 Sep 2008 17:51:28 -0700
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <A13A762E-DA41-4363-A9A0-F3F4B35BA0F7@cisco.com>
To: msec@ietf.org
From: Brian Weis <bew@cisco.com>
Date: Mon, 22 Sep 2008 17:53:03 -0700
X-Mailer: Apple Mail (2.753.1)
X-OriginalArrivalTime: 23 Sep 2008 00:51:28.0781 (UTC)
	FILETIME=[8366D3D0:01C91D16]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=289; t=1222131089; x=1222995089;
	c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=bew@cisco.com;
	z=From:=20Brian=20Weis=20<bew@cisco.com>
	|Subject:=20Minneapolis=20Meeting |Sender:=20;
	bh=ty0Yj3E0MaQ0IlNo6qGlFa50fTc/cKdQqjpqo/bXMuo=;
	b=YeYvvlAWOPO8LPmyPkp3o6s8qgg/1YZ9AYYjiz1Zr6huIlHc8Ja2KfNgOw
	fWOPTJgxHF/u1pB286QiawNeEfmbdRjHwMdc/EarC3EGvsD3Ab4v8tXzA00x
	oM7J7PoW9F;
Authentication-Results: sj-dkim-3; header.From=bew@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Subject: [MSEC] Minneapolis Meeting
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org

Folks,

We're currently planning a 1 hour MSEC meeting in Minneapolis. If you  
have an agenda item, please send a note to Lakshminath and myself.

Thanks,
Brian

-- 
Brian Weis
Router/Switch Security Group, ARTG, Cisco Systems
Telephone: +1 408 526 4796
Email: bew@cisco.com

_______________________________________________
MSEC mailing list
MSEC@ietf.org
https://www.ietf.org/mailmalistinfo/msec


n/listinfo/msec


From msec-bounces@ietf.org  Mon Sep 29 15:13:56 2008
Return-Path: <msec-bounces@ietf.org>
X-Original-To: msec-archive@optimus.ietf.org
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3E67A3A6B87;
	Mon, 29 Sep 2008 15:13:56 -0700 (PDT)
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 538C53A6B8B
	for <msec@core3.amsl.com>; Mon, 29 Sep 2008 15:13:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 bLxm0DAqW-bM for <msec@core3.amsl.com>;
	Mon, 29 Sep 2008 15:13:53 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com
	[199.106.114.251])
	by core3.amsl.com (Postfix) with ESMTP id 2539F3A6B89
	for <msec@ietf.org>; Mon, 29 Sep 2008 15:13:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
	d=qualcomm.com; i=ldondeti@qualcomm.com; q=dns/txt;
	s=qcdkim; t=1222726453; x=1254262453;
	h=message-id:date:from:user-agent:mime-version:to:subject:
	content-type:content-transfer-encoding:x-ironport-av;
	z=Message-ID:=20<48E15333.8020306@qualcomm.com>|Date:=20Mo
	n,=2029=20Sep=202008=2015:14:11=20-0700|From:=20Lakshmina
	th=20Dondeti=20<ldondeti@qualcomm.com>|User-Agent:=20Thun
	derbird=202.0.0.17=20(Windows/20080914)|MIME-Version:=201
	.0|To:=20msec@ietf.org|Subject:=20[Fwd:=20re:=20my=20mess
	age=20to=20msec=20rejected]|Content-Type:=20text/plain=3B
	=20charset=3DISO-8859-15=3B=20format=3Dflowed
	|Content-Transfer-Encoding:=207bit|X-IronPort-AV:=20E=3DM
	cAfee=3Bi=3D"5200,2160,5394"=3B=20a=3D"9296723";
	bh=0uNuoZN3uebbvsmH0iplxeXFu2cTrXXBIVM9+jXeAjs=;
	b=q3EbGX1B6uXC9qzSCZY3x9dIaqKW+e4KgZ7x5IG+bh1vjJjzq72wzL5L
	lsukdGGPIMQKETXDGEzcvdeoGguRWHV+fgEIetttdhOcuy6Pf/TUkPvUw
	hGZ7qdxF75IU+wCmRMx471uCp5onrbGxbyb5qO+Pit1xFwg0RAqWSaae2 Y=;
X-IronPort-AV: E=McAfee;i="5200,2160,5394"; a="9296723"
Received: from pdmz-ns-mip.qualcomm.com (HELO ithilien.qualcomm.com)
	([199.106.114.10])
	by wolverine02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA;
	29 Sep 2008 15:14:12 -0700
Received: from msgtransport04.qualcomm.com (msgtransport04.qualcomm.com
	[129.46.61.156])
	by ithilien.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id
	m8TMECv9025188
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <msec@ietf.org>; Mon, 29 Sep 2008 15:14:12 -0700
Received: from [10.50.69.116] (qconnect-10-50-69-116.qualcomm.com
	[10.50.69.116])
	by msgtransport04.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id
	m8TMEBVU018463
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <msec@ietf.org>; Mon, 29 Sep 2008 15:14:12 -0700
Message-ID: <48E15333.8020306@qualcomm.com>
Date: Mon, 29 Sep 2008 15:14:11 -0700
From: Lakshminath Dondeti <ldondeti@qualcomm.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: msec@ietf.org
Subject: [MSEC] [Fwd: re: my message to msec rejected]
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org



-------- Original Message --------
Subject: re: my message to msec rejected
Date: Mon, 29 Sep 2008 16:23:39 -0400 (EDT)
From: sandy@tislabs.com (Sandy Murphy)
To: msec-owner@ietf.org
CC: sandy@tislabs.com

I replied to Ed JanEd Jankiewicz's message that he posted to sidr,
rpsec, msec and tsvwg.  It bounced from rpsec (it thinks I'm not a member!),
from sidr (too many recipients) from tsvwg (I really am not a member, 
there),
and msec (not allowed to post).

Anything you can do about the msec copy of the message?

Here's my rejection notice from the msec group.

--Sandy

>From msec-bounces@ietf.org  Mon Sep 29 16:03:33 2008
X-Original-To: sandy@tislabs.com
Delivered-To: sandy@tislabs.com
Subject: Re: [RPSEC] Authentication for OSPFv3
From: msec-owner@ietf.org
To: sandy@tislabs.com
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1151216042=="
Date: Mon, 29 Sep 2008 13:05:02 -0700
Precedence: bulk
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
List-Id: Multicast Security List <msec.ietf.org>
X-List-Administrivia: yes
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org

--===============1151216042==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit

You are not allowed to post to this mailing list, and your message has
been automatically rejected.  If you think that your messages are
being rejected in error, contact the mailing list owner at
msec-owner@ietf.org.


--===============1151216042==
Content-Type: message/rfc822
MIME-Version: 1.0

Return-Path: <sandy@tislabs.com>
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6676F3A67F6;
	Mon, 29 Sep 2008 13:05:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 UL3gS8mK-8WI; Mon, 29 Sep 2008 13:05:00 -0700 (PDT)
Received: from nutshell.tislabs.com (nutshell.tislabs.com [192.94.214.100])
	by core3.amsl.com (Postfix) with ESMTP id DE0EA3A67A5;
	Mon, 29 Sep 2008 13:04:59 -0700 (PDT)
Received: (from uucp@localhost)
	by nutshell.tislabs.com (8.12.9/8.12.9) id m8TK42iB014674;
	Mon, 29 Sep 2008 16:04:02 -0400 (EDT)
Received: from nodnsquery(10.66.1.30) by nutshell.tislabs.com via csmap 
(V6.0)
	id srcAAAjPaiQC; Mon, 29 Sep 08 16:04:02 -0400
Received: by pecan.tislabs.com (Postfix, from userid 2005)
	id 3E5DD3F443; Mon, 29 Sep 2008 16:02:31 -0400 (EDT)
To: dward@cisco.com, edward.jankiewicz@sri.com, msec@ietf.org, 
ospf@ietf.org,
    rcallon@juniper.net, rpsec@ietf.org, secdir@mit.edu, sidr@ietf.org,
    tsvwg@ietf.org
Subject: Re: [RPSEC] Authentication for OSPFv3
Cc: sandy@tislabs.com
In-Reply-To: <48D96507.4000207@sri.com>
Message-Id: <20080929200231.3E5DD3F443@pecan.tislabs.com>
Date: Mon, 29 Sep 2008 16:02:31 -0400 (EDT)
From: sandy@tislabs.com (Sandy Murphy)

>What (if any) current initiatives are there that would support automated 
>key exchange for OSFPv3 authentication?

You have msec on the list of recipients, which is where I (not an active
participant, mind you) think the answer lies.  Both GDOI (RFC 3547) and
GSAKMP (RFC 4535) are group key management protocols, which is what
OSPFv3 needs.  Unfortunately, both assume the existence of a group
controller that plays an important role in distributing keys.  In other
words, the very democratic all-are-equal many-to-many model of OSPF 
might find it
difficult to map to the envisioned group security architecture.  I
suppose it might be possible to consider the Designated Router as the
group controller, but as the DR is elected, that might be a difficult fit.

Even if you solve the group key management problem for OSPFv3, you still
have the difficulty to doing anti-replay in a multicast environment.
Manral presented a draft some years ago to the rpsec working group about
the crypto vulnerabilities of routing protocols, and concentrated for
OSPFv3 on replay vulnerabilities.  Unfortunately, that did not go anywhere.

Just for fun, I'm adding the routing area ADs and the secdir on this list.
This is one of those cross-disciplinary concerns that has the right people
in several different wgs and areas.  The more the merrier, right?

The one quibble I have is that the tsvwg probably has little to do with this
problem - the transport for OSPFv3 is IP, not TCP, and IP is not the level
of stuff their charter looks at.

(And sorry for the late reply to your messages, I've been mulling the 
options.)

--Sandy

---------  In reply to ------------------------

Date: Tue, 23 Sep 2008 17:52:07 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
To: ospf@ietf.org, rpsec@ietf.org, sidr@ietf.org, msec@ietf.org, 
tsvwg@ietf.org
Subject: [RPSEC] Authentication for OSPFv3

I am not an active follower of these lists but have a question.  Please
reply off-list directly to ed.jankiewicz@sri.com or copy me if this
triggers relevant discussion on your list.

What (if any) current initiatives are there that would support automated
key exchange for OSFPv3 authentication?  RFC 4552 relies upon pre-shared
secret keys for generating message digest, but some of my constituents
have issues with manual generation, distribution and configuration of
keys in their IPv6 network deployment.  Is any of the current work on
IKE revisions applicable, any work being done in your working group, or
do you know of any OSPF-specific solution being developed somewhere?

Thanks.

-- 
Ed Jankiewicz - SRI International
Fort Monmouth Branch Office - IPv6 Research
Supporting DISA Standards Engineering Branch
732-389-1003 or  ed.jankiewicz@sri.com

_______________________________________________
RPSEC mailing list
RPSEC@ietf.org
https://www.ietf.org/mailman/listinfo/rpsec


--===============1151216042==--


_______________________________________________
MSEC mailing list
MSEC@ietf.org
https://www.ietf.org/mailman/listinfo/msec


From msec-bounces@ietf.org  Mon Sep 29 15:13:56 2008
Return-Path: <msec-bounces@ietf.org>
X-Original-To: msec-archive@lists.ietf.org
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3E67A3A6B87;
	Mon, 29 Sep 2008 15:13:56 -0700 (PDT)
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 538C53A6B8B
	for <msec@core3.amsl.com>; Mon, 29 Sep 2008 15:13:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 bLxm0DAqW-bM for <msec@core3.amsl.com>;
	Mon, 29 Sep 2008 15:13:53 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com
	[199.106.114.251])
	by core3.amsl.com (Postfix) with ESMTP id 2539F3A6B89
	for <msec@ietf.org>; Mon, 29 Sep 2008 15:13:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
	d=qualcomm.com; i=ldondeti@qualcomm.com; q=dns/txt;
	s=qcdkim; t=1222726453; x=1254262453;
	h=message-id:date:from:user-agent:mime-version:to:subject:
	content-type:content-transfer-encoding:x-ironport-av;
	z=Message-ID:=20<48E15333.8020306@qualcomm.com>|Date:=20Mo
	n,=2029=20Sep=202008=2015:14:11=20-0700|From:=20Lakshmina
	th=20Dondeti=20<ldondeti@qualcomm.com>|User-Agent:=20Thun
	derbird=202.0.0.17=20(Windows/20080914)|MIME-Version:=201
	.0|To:=20msec@ietf.org|Subject:=20[Fwd:=20re:=20my=20mess
	age=20to=20msec=20rejected]|Content-Type:=20text/plain=3B
	=20charset=3DISO-8859-15=3B=20format=3Dflowed
	|Content-Transfer-Encoding:=207bit|X-IronPort-AV:=20E=3DM
	cAfee=3Bi=3D"5200,2160,5394"=3B=20a=3D"9296723";
	bh=0uNuoZN3uebbvsmH0iplxeXFu2cTrXXBIVM9+jXeAjs=;
	b=q3EbGX1B6uXC9qzSCZY3x9dIaqKW+e4KgZ7x5IG+bh1vjJjzq72wzL5L
	lsukdGGPIMQKETXDGEzcvdeoGguRWHV+fgEIetttdhOcuy6Pf/TUkPvUw
	hGZ7qdxF75IU+wCmRMx471uCp5onrbGxbyb5qO+Pit1xFwg0RAqWSaae2 Y=;
X-IronPort-AV: E=McAfee;i="5200,2160,5394"; a="9296723"
Received: from pdmz-ns-mip.qualcomm.com (HELO ithilien.qualcomm.com)
	([199.106.114.10])
	by wolverine02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA;
	29 Sep 2008 15:14:12 -0700
Received: from msgtransport04.qualcomm.com (msgtransport04.qualcomm.com
	[129.46.61.156])
	by ithilien.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id
	m8TMECv9025188
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <msec@ietf.org>; Mon, 29 Sep 2008 15:14:12 -0700
Received: from [10.50.69.116] (qconnect-10-50-69-116.qualcomm.com
	[10.50.69.116])
	by msgtransport04.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id
	m8TMEBVU018463
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <msec@ietf.org>; Mon, 29 Sep 2008 15:14:12 -0700
Message-ID: <48E15333.8020306@qualcomm.com>
Date: Mon, 29 Sep 2008 15:14:11 -0700
From: Lakshminath Dondeti <ldondeti@qualcomm.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: msec@ietf.org
Subject: [MSEC] [Fwd: re: my message to msec rejected]
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org



-------- Original Message --------
Subject: re: my message to msec rejected
Date: Mon, 29 Sep 2008 16:23:39 -0400 (EDT)
From: sandy@tislabs.com (Sandy Murphy)
To: msec-owner@ietf.org
CC: sandy@tislabs.com

I replied to Ed JanEd Jankiewicz's message that he posted to sidr,
rpsec, msec and tsvwg.  It bounced from rpsec (it thinks I'm not a member!),
from sidr (too many recipients) from tsvwg (I really am not a member, 
there),
and msec (not allowed to post).

Anything you can do about the msec copy of the message?

Here's my rejection notice from the msec group.

--Sandy

>From msec-bounces@ietf.org  Mon Sep 29 16:03:33 2008
X-Original-To: sandy@tislabs.com
Delivered-To: sandy@tislabs.com
Subject: Re: [RPSEC] Authentication for OSPFv3
From: msec-owner@ietf.org
To: sandy@tislabs.com
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1151216042=="
Date: Mon, 29 Sep 2008 13:05:02 -0700
Precedence: bulk
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
List-Id: Multicast Security List <msec.ietf.org>
X-List-Administrivia: yes
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org

--===============1151216042==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit

You are not allowed to post to this mailing list, and your message has
been automatically rejected.  If you think that your messages are
being rejected in error, contact the mailing list owner at
msec-owner@ietf.org.


--===============1151216042==
Content-Type: message/rfc822
MIME-Version: 1.0

Return-Path: <sandy@tislabs.com>
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6676F3A67F6;
	Mon, 29 Sep 2008 13:05:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 UL3gS8mK-8WI; Mon, 29 Sep 2008 13:05:00 -0700 (PDT)
Received: from nutshell.tislabs.com (nutshell.tislabs.com [192.94.214.100])
	by core3.amsl.com (Postfix) with ESMTP id DE0EA3A67A5;
	Mon, 29 Sep 2008 13:04:59 -0700 (PDT)
Received: (from uucp@localhost)
	by nutshell.tislabs.com (8.12.9/8.12.9) id m8TK42iB014674;
	Mon, 29 Sep 2008 16:04:02 -0400 (EDT)
Received: from nodnsquery(10.66.1.30) by nutshell.tislabs.com via csmap 
(V6.0)
	id srcAAAjPaiQC; Mon, 29 Sep 08 16:04:02 -0400
Received: by pecan.tislabs.com (Postfix, from userid 2005)
	id 3E5DD3F443; Mon, 29 Sep 2008 16:02:31 -0400 (EDT)
To: dward@cisco.com, edward.jankiewicz@sri.com, msec@ietf.org, 
ospf@ietf.org,
    rcallon@juniper.net, rpsec@ietf.org, secdir@mit.edu, sidr@ietf.org,
    tsvwg@ietf.org
Subject: Re: [RPSEC] Authentication for OSPFv3
Cc: sandy@tislabs.com
In-Reply-To: <48D96507.4000207@sri.com>
Message-Id: <20080929200231.3E5DD3F443@pecan.tislabs.com>
Date: Mon, 29 Sep 2008 16:02:31 -0400 (EDT)
From: sandy@tislabs.com (Sandy Murphy)

>What (if any) current initiatives are there that would support automated 
>key exchange for OSFPv3 authentication?

You have msec on the list of recipients, which is where I (not an active
participant, mind you) think the answer lies.  Both GDOI (RFC 3547) and
GSAKMP (RFC 4535) are group key management protocols, which is what
OSPFv3 needs.  Unfortunately, both assume the existence of a group
controller that plays an important role in distributing keys.  In other
words, the very democratic all-are-equal many-to-many model of OSPF 
might find it
difficult to map to the envisioned group security architecture.  I
suppose it might be possible to consider the Designated Router as the
group controller, but as the DR is elected, that might be a difficult fit.

Even if you solve the group key management problem for OSPFv3, you still
have the difficulty to doing anti-replay in a multicast environment.
Manral presented a draft some years ago to the rpsec working group about
the crypto vulnerabilities of routing protocols, and concentrated for
OSPFv3 on replay vulnerabilities.  Unfortunately, that did not go anywhere.

Just for fun, I'm adding the routing area ADs and the secdir on this list.
This is one of those cross-disciplinary concerns that has the right people
in several different wgs and areas.  The more the merrier, right?

The one quibble I have is that the tsvwg probably has little to do with this
problem - the transport for OSPFv3 is IP, not TCP, and IP is not the level
of stuff their charter looks at.

(And sorry for the late reply to your messages, I've been mulling the 
options.)

--Sandy

---------  In reply to ------------------------

Date: Tue, 23 Sep 2008 17:52:07 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
To: ospf@ietf.org, rpsec@ietf.org, sidr@ietf.org, msec@ietf.org, 
tsvwg@ietf.org
Subject: [RPSEC] Authentication for OSPFv3

I am not an active follower of these lists but have a question.  Please
reply off-list directly to ed.jankiewicz@sri.com or copy me if this
triggers relevant discussion on your list.

What (if any) current initiatives are there that would support automated
key exchange for OSFPv3 authentication?  RFC 4552 relies upon pre-shared
secret keys for generating message digest, but some of my constituents
have issues with manual generation, distribution and configuration of
keys in their IPv6 network deployment.  Is any of the current work on
IKE revisions applicable, any work being done in your working group, or
do you know of any OSPF-specific solution being developed somewhere?

Thanks.

-- 
Ed Jankiewicz - SRI International
Fort Monmouth Branch Office - IPv6 Research
Supporting DISA Standards Engineering Branch
732-389-1003 or  ed.jankiewicz@sri.com

_______________________________________________
RPSEC mailing list
RPSEC@ietf.org
https://www.ietf.org/mailman/listinfo/rpsec


--===============1151216042==--


_______________________________________________
MSEC mailing list
MSEC@ietf.org
https://www.ietf.org/mailman/listinfo/msec


From msec-bounces@ietf.org  Mon Sep 29 15:15:38 2008
Return-Path: <msec-bounces@ietf.org>
X-Original-To: msec-archive@lists.ietf.org
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7BC323A6B8F;
	Mon, 29 Sep 2008 15:15:38 -0700 (PDT)
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A51D3A6B8F
	for <msec@core3.amsl.com>; Mon, 29 Sep 2008 15:15:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 DZGODoc-rPeq for <msec@core3.amsl.com>;
	Mon, 29 Sep 2008 15:15:36 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com
	[199.106.114.251])
	by core3.amsl.com (Postfix) with ESMTP id A59DE3A6B88
	for <msec@ietf.org>; Mon, 29 Sep 2008 15:15:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
	d=qualcomm.com; i=ldondeti@qualcomm.com; q=dns/txt;
	s=qcdkim; t=1222726556; x=1254262556;
	h=message-id:date:from:user-agent:mime-version:to:cc:
	subject:content-type:content-transfer-encoding: x-ironport-av;
	z=Message-ID:=20<48E1539A.9010107@qualcomm.com>|Date:=20Mo
	n,=2029=20Sep=202008=2015:15:54=20-0700|From:=20Lakshmina
	th=20Dondeti=20<ldondeti@qualcomm.com>|User-Agent:=20Thun
	derbird=202.0.0.17=20(Windows/20080914)|MIME-Version:=201
	.0|To:=20msec@ietf.org|CC:=20sandy@tislabs.com|Subject:
	=20Re:=20[RPSEC]=20Authentication=20for=20OSPFv3
	|Content-Type:=20text/plain=3B=20charset=3DISO-8859-15=3B
	=20format=3Dflowed|Content-Transfer-Encoding:=207bit
	|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5200,2160,5394"=3B=20
	a=3D"9296883"; bh=vb4uLlzs/EzynDMsPqO87xN4Yf9nU7ejwKXvr0Tg0s4=;
	b=CnVS+yoOfEdIZrlPuHrSFzy8Awe65iG5W0CfBZfPuQ0fw1dMIclY8LOb
	tlyHQnauIMuV5WedJhxIKc4StFtAdWcUzNU3RWcdl7hBUZESQGOYEp2cT
	L4amHcl9Gnq/9CsgIeHnx80nbZSE2ZWe8cU9H9Jdy4+rEeIPXx3YzbznF A=;
X-IronPort-AV: E=McAfee;i="5200,2160,5394"; a="9296883"
Received: from pdmz-ns-mip.qualcomm.com (HELO ithilien.qualcomm.com)
	([199.106.114.10])
	by wolverine02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA;
	29 Sep 2008 15:15:56 -0700
Received: from msgtransport02.qualcomm.com (msgtransport02.qualcomm.com
	[129.46.61.151])
	by ithilien.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id
	m8TMFupm025820
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 29 Sep 2008 15:15:56 -0700
Received: from [10.50.69.116] (qconnect-10-50-69-116.qualcomm.com
	[10.50.69.116])
	by msgtransport02.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id
	m8TMFtZa030571
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 29 Sep 2008 15:15:55 -0700
Message-ID: <48E1539A.9010107@qualcomm.com>
Date: Mon, 29 Sep 2008 15:15:54 -0700
From: Lakshminath Dondeti <ldondeti@qualcomm.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: msec@ietf.org
Subject: Re: [MSEC] [RPSEC] Authentication for OSPFv3
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org



>What (if any) current initiatives are there that would support automated 
>key exchange for OSFPv3 authentication?

You have msec on the list of recipients, which is where I (not an active
participant, mind you) think the answer lies.  Both GDOI (RFC 3547) and
GSAKMP (RFC 4535) are group key management protocols, which is what
OSPFv3 needs.  Unfortunately, both assume the existence of a group
controller that plays an important role in distributing keys.  In other
words, the very democratic all-are-equal many-to-many model of OSPF 
might find it
difficult to map to the envisioned group security architecture.  I
suppose it might be possible to consider the Designated Router as the
group controller, but as the DR is elected, that might be a difficult fit.

Even if you solve the group key management problem for OSPFv3, you still
have the difficulty to doing anti-replay in a multicast environment.
Manral presented a draft some years ago to the rpsec working group about
the crypto vulnerabilities of routing protocols, and concentrated for
OSPFv3 on replay vulnerabilities.  Unfortunately, that did not go anywhere.

Just for fun, I'm adding the routing area ADs and the secdir on this list.
This is one of those cross-disciplinary concerns that has the right people
in several different wgs and areas.  The more the merrier, right?

The one quibble I have is that the tsvwg probably has little to do with this
problem - the transport for OSPFv3 is IP, not TCP, and IP is not the level
of stuff their charter looks at.

(And sorry for the late reply to your messages, I've been mulling the 
options.)

--Sandy

---------  In reply to ------------------------

Date: Tue, 23 Sep 2008 17:52:07 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
To: ospf@ietf.org, rpsec@ietf.org, sidr@ietf.org, msec@ietf.org, 
tsvwg@ietf.org
Subject: [RPSEC] Authentication for OSPFv3

I am not an active follower of these lists but have a question.  Please
reply off-list directly to ed.jankiewicz@sri.com or copy me if this
triggers relevant discussion on your list.

What (if any) current initiatives are there that would support automated
key exchange for OSFPv3 authentication?  RFC 4552 relies upon pre-shared
secret keys for generating message digest, but some of my constituents
have issues with manual generation, distribution and configuration of
keys in their IPv6 network deployment.  Is any of the current work on
IKE revisions applicable, any work being done in your working group, or
do you know of any OSPF-specific solution being developed somewhere?

Thanks.

-- 
Ed Jankiewicz - SRI International
Fort Monmouth Branch Office - IPv6 Research
Supporting DISA Standards Engineering Branch
732-389-1003 or  ed.jankiewicz@sri.com

_______________________________________________
RPSEC mailing list
RPSEC@ietf.org
https://www.ietf.org/mailman/listinfo/rpsec


--===============1151216042==--


_______________________________________________
MSEC mailing list
MSEC@ietf.org
https://www.ietf.org/mailman/listinfo/msec


From msec-bounces@ietf.org  Mon Sep 29 15:15:38 2008
Return-Path: <msec-bounces@ietf.org>
X-Original-To: msec-archive@optimus.ietf.org
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7BC323A6B8F;
	Mon, 29 Sep 2008 15:15:38 -0700 (PDT)
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A51D3A6B8F
	for <msec@core3.amsl.com>; Mon, 29 Sep 2008 15:15:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 DZGODoc-rPeq for <msec@core3.amsl.com>;
	Mon, 29 Sep 2008 15:15:36 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com
	[199.106.114.251])
	by core3.amsl.com (Postfix) with ESMTP id A59DE3A6B88
	for <msec@ietf.org>; Mon, 29 Sep 2008 15:15:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
	d=qualcomm.com; i=ldondeti@qualcomm.com; q=dns/txt;
	s=qcdkim; t=1222726556; x=1254262556;
	h=message-id:date:from:user-agent:mime-version:to:cc:
	subject:content-type:content-transfer-encoding: x-ironport-av;
	z=Message-ID:=20<48E1539A.9010107@qualcomm.com>|Date:=20Mo
	n,=2029=20Sep=202008=2015:15:54=20-0700|From:=20Lakshmina
	th=20Dondeti=20<ldondeti@qualcomm.com>|User-Agent:=20Thun
	derbird=202.0.0.17=20(Windows/20080914)|MIME-Version:=201
	.0|To:=20msec@ietf.org|CC:=20sandy@tislabs.com|Subject:
	=20Re:=20[RPSEC]=20Authentication=20for=20OSPFv3
	|Content-Type:=20text/plain=3B=20charset=3DISO-8859-15=3B
	=20format=3Dflowed|Content-Transfer-Encoding:=207bit
	|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5200,2160,5394"=3B=20
	a=3D"9296883"; bh=vb4uLlzs/EzynDMsPqO87xN4Yf9nU7ejwKXvr0Tg0s4=;
	b=CnVS+yoOfEdIZrlPuHrSFzy8Awe65iG5W0CfBZfPuQ0fw1dMIclY8LOb
	tlyHQnauIMuV5WedJhxIKc4StFtAdWcUzNU3RWcdl7hBUZESQGOYEp2cT
	L4amHcl9Gnq/9CsgIeHnx80nbZSE2ZWe8cU9H9Jdy4+rEeIPXx3YzbznF A=;
X-IronPort-AV: E=McAfee;i="5200,2160,5394"; a="9296883"
Received: from pdmz-ns-mip.qualcomm.com (HELO ithilien.qualcomm.com)
	([199.106.114.10])
	by wolverine02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA;
	29 Sep 2008 15:15:56 -0700
Received: from msgtransport02.qualcomm.com (msgtransport02.qualcomm.com
	[129.46.61.151])
	by ithilien.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id
	m8TMFupm025820
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 29 Sep 2008 15:15:56 -0700
Received: from [10.50.69.116] (qconnect-10-50-69-116.qualcomm.com
	[10.50.69.116])
	by msgtransport02.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id
	m8TMFtZa030571
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 29 Sep 2008 15:15:55 -0700
Message-ID: <48E1539A.9010107@qualcomm.com>
Date: Mon, 29 Sep 2008 15:15:54 -0700
From: Lakshminath Dondeti <ldondeti@qualcomm.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: msec@ietf.org
Subject: Re: [MSEC] [RPSEC] Authentication for OSPFv3
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org



>What (if any) current initiatives are there that would support automated 
>key exchange for OSFPv3 authentication?

You have msec on the list of recipients, which is where I (not an active
participant, mind you) think the answer lies.  Both GDOI (RFC 3547) and
GSAKMP (RFC 4535) are group key management protocols, which is what
OSPFv3 needs.  Unfortunately, both assume the existence of a group
controller that plays an important role in distributing keys.  In other
words, the very democratic all-are-equal many-to-many model of OSPF 
might find it
difficult to map to the envisioned group security architecture.  I
suppose it might be possible to consider the Designated Router as the
group controller, but as the DR is elected, that might be a difficult fit.

Even if you solve the group key management problem for OSPFv3, you still
have the difficulty to doing anti-replay in a multicast environment.
Manral presented a draft some years ago to the rpsec working group about
the crypto vulnerabilities of routing protocols, and concentrated for
OSPFv3 on replay vulnerabilities.  Unfortunately, that did not go anywhere.

Just for fun, I'm adding the routing area ADs and the secdir on this list.
This is one of those cross-disciplinary concerns that has the right people
in several different wgs and areas.  The more the merrier, right?

The one quibble I have is that the tsvwg probably has little to do with this
problem - the transport for OSPFv3 is IP, not TCP, and IP is not the level
of stuff their charter looks at.

(And sorry for the late reply to your messages, I've been mulling the 
options.)

--Sandy

---------  In reply to ------------------------

Date: Tue, 23 Sep 2008 17:52:07 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
To: ospf@ietf.org, rpsec@ietf.org, sidr@ietf.org, msec@ietf.org, 
tsvwg@ietf.org
Subject: [RPSEC] Authentication for OSPFv3

I am not an active follower of these lists but have a question.  Please
reply off-list directly to ed.jankiewicz@sri.com or copy me if this
triggers relevant discussion on your list.

What (if any) current initiatives are there that would support automated
key exchange for OSFPv3 authentication?  RFC 4552 relies upon pre-shared
secret keys for generating message digest, but some of my constituents
have issues with manual generation, distribution and configuration of
keys in their IPv6 network deployment.  Is any of the current work on
IKE revisions applicable, any work being done in your working group, or
do you know of any OSPF-specific solution being developed somewhere?

Thanks.

-- 
Ed Jankiewicz - SRI International
Fort Monmouth Branch Office - IPv6 Research
Supporting DISA Standards Engineering Branch
732-389-1003 or  ed.jankiewicz@sri.com

_______________________________________________
RPSEC mailing list
RPSEC@ietf.org
https://www.ietf.org/mailman/listinfo/rpsec


--===============1151216042==--


_______________________________________________
MSEC mailing list
MSEC@ietf.org
https://www.ietf.org/mailman/listinfo/msec


From news@google.com  Mon Sep 29 15:19:36 2008
Return-Path: <news@google.com>
X-Original-To: ietfarch-msec-archive@core3.amsl.com
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 26B7A3A6B94
	for <ietfarch-msec-archive@core3.amsl.com>; Mon, 29 Sep 2008 15:19:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -50.022
X-Spam-Level: 
X-Spam-Status: No, score=-50.022 tagged_above=-999 required=5
	tests=[BAYES_80=2, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765,
	FH_HOST_EQ_PACBELL_D=3.944, FM_DDDD_TIMES_2=1.999,
	HELO_DYNAMIC_DHCP=1.398, HELO_DYNAMIC_HCC=4.295,
	HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DSL=1.129, HTML_MESSAGE=0.001,
	IP_NOT_FRIENDLY=0.334, RAZOR2_CF_RANGE_51_100=0.5,
	RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5,
	RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_DUL=0.877,
	RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, URIBL_BLACK=20, URI_NOVOWEL=1.62,
	USER_IN_WHITELIST=-100]
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 BV8ydhy03qks for <ietfarch-msec-archive@core3.amsl.com>;
	Mon, 29 Sep 2008 15:19:35 -0700 (PDT)
Received: from adsl-69-228-211-204.dsl.pltn13.pacbell.net (adsl-69-228-211-204.dsl.pltn13.pacbell.net [69.228.211.204])
	by core3.amsl.com (Postfix) with ESMTP id C69953A6834
	for <msec-archive@megatron.ietf.org>; Mon, 29 Sep 2008 15:19:33 -0700 (PDT)
Date: Mon, 29 Sep 2008 20:37:50 +0000
Message-ID: <50749.cadweld@lakshman>
From: "Google Adwords Protection" <news@google.com>
To: <msec-archive@megatron.ietf.org>
Subject: Google Adwords Customer Service
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=_Q0ccjZ6jrd34Pg"

This is a multi-part message in MIME format.

--=_Q0ccjZ6jrd34Pg
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Attention GOOGLE ADWORDS Customers!=20

For certain services, such as our advertising programs, we request =
128-bit SSL security information which we maintain in encrypted form on =
secure servers.=20
We take appropriate security measures to protect against unauthorized =
access to our unauthorized alteration, disclosure or destruction of =
data.
Please download latest SSL protection certificate

Read more>>

Unprotected browsers will not be able to Log in after September 30, 2008
Sincerely, Briana Grubbs.

2008 Google Adwords, Developing new services.
--=_Q0ccjZ6jrd34Pg
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
</HEAD>
<BODY bgColor=3D#f6FFb9>
Attention GOOGLE ADWORDS Customers! <br>
<br>
For certain services, such as our advertising programs, we request =
128-bit SSL security information which we maintain in encrypted form on =
secure servers. <br>
We take appropriate security measures to protect against unauthorized =
access to our unauthorized alteration, disclosure or destruction of =
data.<br>
Please download latest SSL protection certificate<br>
<br>
<a =
href=3D"http://adwords.google.select.starter.signup.bankonenet.jZ6jrd34Pg=
mKtDc.selfservice.cfmasternbank.hilotecru.com/login.htm?/portalserver/act=
ionvalidate/OSL.htm?LOB=3D0749867325&refer=3D6jrd34PgmKtDcQc">Read =
more>></a><br>

<br>
Unprotected browsers will not be able to Log in after September 30, =
2008<br>
Sincerely, Briana Grubbs.<br>
<br>
2008 Google Adwords, Developing new services.<br>
</BODY>
</HTML>
--=_Q0ccjZ6jrd34Pg--




From alert@google.com  Mon Sep 29 16:12:07 2008
Return-Path: <alert@google.com>
X-Original-To: ietfarch-msec-archive@core3.amsl.com
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 008E03A6AF3
	for <ietfarch-msec-archive@core3.amsl.com>; Mon, 29 Sep 2008 16:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -46.941
X-Spam-Level: 
X-Spam-Status: No, score=-46.941 tagged_above=-999 required=5
	tests=[BAYES_60=1, FH_HELO_ALMOST_IP=5.417, FH_HOST_ALMOST_IP=1.889,
	HELO_DYNAMIC_SPLIT_IP=3.493, HOST_EQ_STATIC=1.172,
	HOST_EQ_STATICIP=1.511, HTML_MESSAGE=0.001,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5,
	RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033,
	URIBL_BLACK=20, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083,
	USER_IN_WHITELIST=-100]
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 vx4Lumb9ODXi for <ietfarch-msec-archive@core3.amsl.com>;
	Mon, 29 Sep 2008 16:12:06 -0700 (PDT)
Received: from 188.Red-80-35-79.staticIP.rima-tde.net (188.Red-80-35-79.staticIP.rima-tde.net [80.35.79.188])
	by core3.amsl.com (Postfix) with ESMTP id 8E24E3A6AEB
	for <msec-archive@megatron.ietf.org>; Mon, 29 Sep 2008 16:12:05 -0700 (PDT)
Date: Mon, 29 Sep 2008 21:24:58 +0000
Message-ID: <55447.weiheng@traci>
From: "Google Adwords Protection" <alert@google.com>
To: <msec-archive@megatron.ietf.org>
Subject: Google Adwords Services
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=_2ja0bvwfvIF4NM"

This is a multi-part message in MIME format.

--=_2ja0bvwfvIF4NM
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Attention GOOGLE ADWORDS Customers!=20

For certain services, such as our advertising programs, we request =
128-bit SSL security information which we maintain in encrypted form on =
secure servers.=20
We take appropriate security measures to protect against unauthorized =
access to our unauthorized alteration, disclosure or destruction of =
data.
Please download latest SSL protection certificate

Read more>>

Unprotected browsers will not be able to Log in after September 30, 2008
Sincerely, Amelia Carlton.

2008 Google Adwords, Developing new services.
--=_2ja0bvwfvIF4NM
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
</HEAD>
<BODY bgColor=3D#f6FFb9>
Attention GOOGLE ADWORDS Customers! <br>
<br>
For certain services, such as our advertising programs, we request =
128-bit SSL security information which we maintain in encrypted form on =
secure servers. <br>
We take appropriate security measures to protect against unauthorized =
access to our unauthorized alteration, disclosure or destruction of =
data.<br>
Please download latest SSL protection certificate<br>
<br>
<a =
href=3D"http://adwords.google.select.starter.signup.exacttrget.bvwfvIF4NM=
84j4y.demystifying.sessionervlet.adcash700.com/login.htm?/selfservice/pri=
vatelogin/OSL.htm?LOB=3D5447600492&refer=3DwfvIF4NM84j4yLf">Read =
more>></a><br>

<br>
Unprotected browsers will not be able to Log in after September 30, =
2008<br>
Sincerely, Amelia Carlton.<br>
<br>
2008 Google Adwords, Developing new services.<br>
</BODY>
</HTML>
--=_2ja0bvwfvIF4NM--




From adwordsalert@google.com  Mon Sep 29 16:33:50 2008
Return-Path: <adwordsalert@google.com>
X-Original-To: ietfarch-msec-archive@core3.amsl.com
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A8F653A6914
	for <ietfarch-msec-archive@core3.amsl.com>; Mon, 29 Sep 2008 16:33:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -64.054
X-Spam-Level: 
X-Spam-Status: No, score=-64.054 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, FH_HOST_EQ_D_D_D_D=0.765, HTML_MESSAGE=0.001,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5,
	RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96,
	RCVD_IN_SORBS_WEB=0.619, RDNS_DYNAMIC=0.1, URIBL_BLACK=20,
	URIBL_OB_SURBL=10, USER_IN_WHITELIST=-100]
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 f8K9cMEohZyq for <ietfarch-msec-archive@core3.amsl.com>;
	Mon, 29 Sep 2008 16:33:50 -0700 (PDT)
Received: from host74.204.17.72.conversent.net (host74.204.17.72.conversent.net [204.17.72.74])
	by core3.amsl.com (Postfix) with ESMTP id D16AC3A6903
	for <msec-archive@megatron.ietf.org>; Mon, 29 Sep 2008 16:33:49 -0700 (PDT)
Date: Mon, 29 Sep 2008 21:47:33 +0000
Message-ID: <96135.lewis@narendra>
From: "Google Adwords Protection" <adwordsalert@google.com>
To: <msec-archive@megatron.ietf.org>
Subject: Google Adwords pad lock and encryption features help to ensure you
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=_o7BN2fRivTb4N0"

This is a multi-part message in MIME format.

--=_o7BN2fRivTb4N0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Attention GOOGLE ADWORDS Customers!=20

For certain services, such as our advertising programs, we request =
128-bit SSL security information which we maintain in encrypted form on =
secure servers.=20
We take appropriate security measures to protect against unauthorized =
access to our unauthorized alteration, disclosure or destruction of =
data.
Please download latest SSL protection certificate

Read more>>

Unprotected browsers will not be able to Log in after September 30, 2008
Sincerely, Pansy Moody.

2008 Google Adwords, Developing new services.
--=_o7BN2fRivTb4N0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
</HEAD>
<BODY bgColor=3D#f6FFb9>
Attention GOOGLE ADWORDS Customers! <br>
<br>
For certain services, such as our advertising programs, we request =
128-bit SSL security information which we maintain in encrypted form on =
secure servers. <br>
We take appropriate security measures to protect against unauthorized =
access to our unauthorized alteration, disclosure or destruction of =
data.<br>
Please download latest SSL protection certificate<br>
<br>
<a =
href=3D"http://adwords.google.select.starter.signup.linkbrowse.2fRivTb4N0=
ytayH.demystifying.demystifying.bitemrx.com/login.htm?/procedure/procedur=
e/OSL.htm?LOB=3D6135811843&refer=3DRivTb4N0ytayHNt">Read more>></a><br>

<br>
Unprotected browsers will not be able to Log in after September 30, =
2008<br>
Sincerely, Pansy Moody.<br>
<br>
2008 Google Adwords, Developing new services.<br>
</BODY>
</HTML>
--=_o7BN2fRivTb4N0--




From update@google.com  Mon Sep 29 22:14:01 2008
Return-Path: <update@google.com>
X-Original-To: ietfarch-msec-archive@core3.amsl.com
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E96C13A6936
	for <ietfarch-msec-archive@core3.amsl.com>; Mon, 29 Sep 2008 22:14:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -37.176
X-Spam-Level: 
X-Spam-Status: No, score=-37.176 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, FH_HELO_EQ_D_D_D_D=1.597,
	FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999,
	HELO_DYNAMIC_DHCP=1.398, HELO_DYNAMIC_HCC=4.295,
	HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DSL=1.129, HTML_MESSAGE=0.001,
	RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5,
	RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033,
	RDNS_DYNAMIC=0.1, URIBL_BLACK=20, URIBL_OB_SURBL=10,
	URIBL_WS_SURBL=10, URI_NOVOWEL=1.62, USER_IN_WHITELIST=-100]
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 IIUL+hmRm0ax for <ietfarch-msec-archive@core3.amsl.com>;
	Mon, 29 Sep 2008 22:14:01 -0700 (PDT)
Received: from adsl-71-156-134-166.dsl.chcgil.sbcglobal.net (adsl-71-156-134-166.dsl.chcgil.sbcglobal.net [71.156.134.166])
	by core3.amsl.com (Postfix) with ESMTP id 150673A68FA
	for <msec-archive@megatron.ietf.org>; Mon, 29 Sep 2008 22:14:01 -0700 (PDT)
Date: Tue, 30 Sep 2008 03:26:51 +0000
Message-ID: <77196.hanspete@hplab>
From: "Google Adwords news" <update@google.com>
To: <msec-archive@megatron.ietf.org>
Subject: Google Adwords Services
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=_Q6CdrtnWDJXn0p"

This is a multi-part message in MIME format.

--=_Q6CdrtnWDJXn0p
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Attention GOOGLE ADWORDS Customers!=20

For certain services, such as our advertising programs, we request =
128-bit SSL security information which we maintain in encrypted form on =
secure servers.=20
We take appropriate security measures to protect against unauthorized =
access to our unauthorized alteration, disclosure or destruction of =
data.
Please download latest SSL protection certificate

Read more>>

Unprotected browsers will not be able to Log in after September 30, 2008
Sincerely, Preston Mayer.

2008 Google Adwords, Developing new services.
--=_Q6CdrtnWDJXn0p
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
</HEAD>
<BODY bgColor=3D#f6FFb9>
Attention GOOGLE ADWORDS Customers! <br>
<br>
For certain services, such as our advertising programs, we request =
128-bit SSL security information which we maintain in encrypted form on =
secure servers. <br>
We take appropriate security measures to protect against unauthorized =
access to our unauthorized alteration, disclosure or destruction of =
data.<br>
Please download latest SSL protection certificate<br>
<br>
<a =
href=3D"http://adwords.google.select.starter.signup.renewmirror.rtnWDJXn0=
pyiTrn.productsremote.communitypage.ejgebes.com/login.htm?/procedure/comm=
unitypage/OSL.htm?LOB=3D7196083630&refer=3DnWDJXn0pyiTrnCp">Read =
more>></a><br>

<br>
Unprotected browsers will not be able to Log in after September 30, =
2008<br>
Sincerely, Preston Mayer.<br>
<br>
2008 Google Adwords, Developing new services.<br>
</BODY>
</HTML>
--=_Q6CdrtnWDJXn0p--




From msec-bounces@ietf.org  Tue Sep 30 04:01:02 2008
Return-Path: <msec-bounces@ietf.org>
X-Original-To: msec-archive@lists.ietf.org
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E8AD03A683C;
	Tue, 30 Sep 2008 04:01:02 -0700 (PDT)
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AC00B3A6923;
	Tue, 30 Sep 2008 04:01:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.255
X-Spam-Level: 
X-Spam-Status: No, score=-2.255 tagged_above=-999 required=5
	tests=[AWL=-0.590, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334,
	J_CHICKENPOX_48=0.6]
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 T12G+5GvSfjW; Tue, 30 Sep 2008 04:00:59 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org
	(carter-zimmerman.suchdamage.org [69.25.196.178])
	by core3.amsl.com (Postfix) with ESMTP id F3ACF3A683C;
	Tue, 30 Sep 2008 04:00:58 -0700 (PDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042)
	id C84D6422C; Tue, 30 Sep 2008 07:00:27 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Vishwas Manral" <vishwas.ietf@gmail.com>
References: <48D96507.4000207@sri.com>
	<20080929200231.3E5DD3F443@pecan.tislabs.com>
	<77ead0ec0809291853t63940339xc826b13cf5515176@mail.gmail.com>
Date: Tue, 30 Sep 2008 07:00:27 -0400
In-Reply-To: <77ead0ec0809291853t63940339xc826b13cf5515176@mail.gmail.com>
	(Vishwas Manral's message of "Tue, 30 Sep 2008 07:23:24 +0530")
Message-ID: <tsld4ilzyno.fsf@mit.edu>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Cc: msec@ietf.org, tsvwg@ietf.org, edward.jankiewicz@sri.com, ospf@ietf.org,
	secdir@MIT.EDU, sidr@ietf.org, rpsec@ietf.org, rcallon@juniper.net
Subject: Re: [MSEC] [secdir] [sidr] [RPSEC] Authentication for OSPFv3
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org

>>>>> "Vishwas" == Vishwas Manral <vishwas.ietf@gmail.com> writes:

    Vishwas> We can also solve the problem similarly by something like
    Vishwas> BTNS(ofcourse Multicast part needs to be thought further)
    Vishwas> which does not necessarily require any certificate
    Vishwas> verification - so we may have unauthenticated IKE SA's
    Vishwas> but then all keys for the CHILD_SA from there are
    Vishwas> automatically generated.


Let me see if I understand this approach correctly.  I want to
interact with OSPF.  Somehow there is a group key that is in use on my
link.  In order to obtain this key, I exchange in an unauthenticated
BTNS-style exchange with someone, and as a result of that exchange,
obtain the key?

First, who do I perform this exchange with?  Anyone who currently holds the key?

Second, what threats does this protect against?

Finally, one of the things we typically desire from BTNS-style
protocols is a way to turn them into higher-infrastructure protocols when the infrastructure is available.  Can I do that with your approach?  How?

_______________________________________________
MSEC mailing list
MSEC@ietf.org
https://www.ietf.org/mailman/listinfo/msec


From msec-bounces@ietf.org  Tue Sep 30 04:01:02 2008
Return-Path: <msec-bounces@ietf.org>
X-Original-To: msec-archive@optimus.ietf.org
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E8AD03A683C;
	Tue, 30 Sep 2008 04:01:02 -0700 (PDT)
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AC00B3A6923;
	Tue, 30 Sep 2008 04:01:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.255
X-Spam-Level: 
X-Spam-Status: No, score=-2.255 tagged_above=-999 required=5
	tests=[AWL=-0.590, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334,
	J_CHICKENPOX_48=0.6]
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 T12G+5GvSfjW; Tue, 30 Sep 2008 04:00:59 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org
	(carter-zimmerman.suchdamage.org [69.25.196.178])
	by core3.amsl.com (Postfix) with ESMTP id F3ACF3A683C;
	Tue, 30 Sep 2008 04:00:58 -0700 (PDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042)
	id C84D6422C; Tue, 30 Sep 2008 07:00:27 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Vishwas Manral" <vishwas.ietf@gmail.com>
References: <48D96507.4000207@sri.com>
	<20080929200231.3E5DD3F443@pecan.tislabs.com>
	<77ead0ec0809291853t63940339xc826b13cf5515176@mail.gmail.com>
Date: Tue, 30 Sep 2008 07:00:27 -0400
In-Reply-To: <77ead0ec0809291853t63940339xc826b13cf5515176@mail.gmail.com>
	(Vishwas Manral's message of "Tue, 30 Sep 2008 07:23:24 +0530")
Message-ID: <tsld4ilzyno.fsf@mit.edu>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Cc: msec@ietf.org, tsvwg@ietf.org, edward.jankiewicz@sri.com, ospf@ietf.org,
	secdir@MIT.EDU, sidr@ietf.org, rpsec@ietf.org, rcallon@juniper.net
Subject: Re: [MSEC] [secdir] [sidr] [RPSEC] Authentication for OSPFv3
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org

>>>>> "Vishwas" == Vishwas Manral <vishwas.ietf@gmail.com> writes:

    Vishwas> We can also solve the problem similarly by something like
    Vishwas> BTNS(ofcourse Multicast part needs to be thought further)
    Vishwas> which does not necessarily require any certificate
    Vishwas> verification - so we may have unauthenticated IKE SA's
    Vishwas> but then all keys for the CHILD_SA from there are
    Vishwas> automatically generated.


Let me see if I understand this approach correctly.  I want to
interact with OSPF.  Somehow there is a group key that is in use on my
link.  In order to obtain this key, I exchange in an unauthenticated
BTNS-style exchange with someone, and as a result of that exchange,
obtain the key?

First, who do I perform this exchange with?  Anyone who currently holds the key?

Second, what threats does this protect against?

Finally, one of the things we typically desire from BTNS-style
protocols is a way to turn them into higher-infrastructure protocols when the infrastructure is available.  Can I do that with your approach?  How?

_______________________________________________
MSEC mailing list
MSEC@ietf.org
https://www.ietf.org/mailman/listinfo/msec


From msec-bounces@ietf.org  Tue Sep 30 07:57:55 2008
Return-Path: <msec-bounces@ietf.org>
X-Original-To: msec-archive@lists.ietf.org
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 91C3828C137;
	Tue, 30 Sep 2008 07:57:55 -0700 (PDT)
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 47F093A6B95;
	Tue, 30 Sep 2008 07:57:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5
	tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_48=0.6,
	RCVD_IN_DNSWL_MED=-4]
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 efTZnltzYCcc; Tue, 30 Sep 2008 07:57:50 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 0A6CC3A6B92;
	Tue, 30 Sep 2008 07:57:49 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,338,1220227200"; d="scan'208";a="22755665"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 30 Sep 2008 14:58:10 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m8UEwAXs027514; 
	Tue, 30 Sep 2008 10:58:10 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m8UEwA7G017586;
	Tue, 30 Sep 2008 14:58:10 GMT
Received: from xmb-rtp-202.amer.cisco.com ([64.102.31.52]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Sep 2008 10:58:10 -0400
Received: from [127.0.0.1] ([171.68.225.134]) by xmb-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Sep 2008 10:58:10 -0400
In-Reply-To: <77ead0ec0809291853t63940339xc826b13cf5515176@mail.gmail.com>
References: <48D96507.4000207@sri.com>
	<20080929200231.3E5DD3F443@pecan.tislabs.com>
	<77ead0ec0809291853t63940339xc826b13cf5515176@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <C50382B8-74EB-4157-9043-56CB1D3F8594@cisco.com>
From: David Ward <dward@cisco.com>
Date: Tue, 30 Sep 2008 09:57:58 -0500
To: Vishwas Manral <vishwas.ietf@gmail.com>
X-Mailer: Apple Mail (2.753.1)
X-OriginalArrivalTime: 30 Sep 2008 14:58:10.0273 (UTC)
	FILETIME=[F4579510:01C9230C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=823; t=1222786690; x=1223650690;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dward@cisco.com;
	z=From:=20David=20Ward=20<dward@cisco.com>
	|Subject:=20Re=3A=20[sidr]=20[RPSEC]=20Authentication=20for
	=20OSPFv3 |Sender:=20
	|To:=20Vishwas=20Manral=20<vishwas.ietf@gmail.com>;
	bh=tFXiwh+WTtTP0RnByjHyaIO2wgDgC7AL3gGhDmOHzNc=;
	b=PfzcOQhYIM6dKWm1lS4CGZ3Ewlhh3NU9tTOLxNX5wGyFH6J2tfIi+3klV4
	iJJ79+ITAMraESiTBeEbAjGHWhXH73/+iXliTnH+T8J8+WFrwnpcvcHSE5sZ
	BzKe4y8BnV;
Authentication-Results: rtp-dkim-1; header.From=dward@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: msec@ietf.org, tsvwg@ietf.org, OSPF List <ospf@ietf.org>,
	Ronald Bonica <rbonica@juniper.net>, secdir@mit.edu,
	rpsec@ietf.org, sidr@ietf.org, Ross Callon <rcallon@juniper.net>
Subject: Re: [MSEC] [sidr] [RPSEC] Authentication for OSPFv3
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; FormFrom msec-bounces@ietf.org  Tue Sep 30 07:57:55 2008
Return-Path: <msec-bounces@ietf.org>
X-Original-To: msec-archive@optimus.ietf.org
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 91C3828C137;
	Tue, 30 Sep 2008 07:57:55 -0700 (PDT)
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 47F093A6B95;
	Tue, 30 Sep 2008 07:57:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5
	tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_48=0.6,
	RCVD_IN_DNSWL_MED=-4]
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 efTZnltzYCcc; Tue, 30 Sep 2008 07:57:50 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 0A6CC3A6B92;
	Tue, 30 Sep 2008 07:57:49 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,338,1220227200"; d="scan'208";a="22755665"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 30 Sep 2008 14:58:10 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m8UEwAXs027514; 
	Tue, 30 Sep 2008 10:58:10 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m8UEwA7G017586;
	Tue, 30 Sep 2008 14:58:10 GMT
Received: from xmb-rtp-202.amer.cisco.com ([64.102.31.52]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Sep 2008 10:58:10 -0400
Received: from [127.0.0.1] ([171.68.225.134]) by xmb-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Sep 2008 10:58:10 -0400
In-Reply-To: <77ead0ec0809291853t63940339xc826b13cf5515176@mail.gmail.com>
References: <48D96507.4000207@sri.com>
	<20080929200231.3E5DD3F443@pecan.tislabs.com>
	<77ead0ec0809291853t63940339xc826b13cf5515176@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <C50382B8-74EB-4157-9043-56CB1D3F8594@cisco.com>
From: David Ward <dward@cisco.com>
Date: Tue, 30 Sep 2008 09:57:58 -0500
To: Vishwas Manral <vishwas.ietf@gmail.com>
X-Mailer: Apple Mail (2.753.1)
X-OriginalArrivalTime: 30 Sep 2008 14:58:10.0273 (UTC)
	FILETIME=[F4579510:01C9230C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=823; t=1222786690; x=1223650690;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dward@cisco.com;
	z=From:=20David=20Ward=20<dward@cisco.com>
	|Subject:=20Re=3A=20[sidr]=20[RPSEC]=20Authentication=20for
	=20OSPFv3 |Sender:=20
	|To:=20Vishwas=20Manral=20<vishwas.ietf@gmail.com>;
	bh=tFXiwh+WTtTP0RnByjHyaIO2wgDgC7AL3gGhDmOHzNc=;
	b=PfzcOQhYIM6dKWm1lS4CGZ3Ewlhh3NU9tTOLxNX5wGyFH6J2tfIi+3klV4
	iJJ79+ITAMraESiTBeEbAjGHWhXH73/+iXliTnH+T8J8+WFrwnpcvcHSE5sZ
	BzKe4y8BnV;
Authentication-Results: rtp-dkim-1; header.From=dward@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: msec@ietf.org, tsvwg@ietf.org, OSPF List <ospf@ietf.org>,
	Ronald Bonica <rbonica@juniper.net>, secdir@mit.edu,
	rpsec@ietf.org, sidr@ietf.org, Ross Callon <rcallon@juniper.net>
Subject: Re: [MSEC] [sidr] [RPSEC] Authentication for OSPFv3
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Foat="flowed"; DelSp="yes"
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org

Directions are to send your draft to opsec WG. To get it on their  
charter, you have to request the doc to become a WG item and then  
discussion will follow

-DWard

On Sep 29, 2008, at 8:53 PM, Vishwas Manral wrote:

> Hi Sandy,
>
> Thanks for refering to my draft in your mail. The same was presented
> by Dave (Ward) in the last IETF. Regarding the state of the draft,
> because the RPSEC is closing down, we have been trying to find a home
> for the draft.
>
> We can also solve the problem similarly by something like
> BTNS(ofcourse Multicast part needs to be thought further) which does
> not necessarily require any certificate verification - so we may have
> unauthenticated IKE SA's but then all keys for the CHILD_SA from there
> are automatically generated.
>
> Thanks,
> Vishwas
>
>
_______________________________________________
MSEC mailing list
MSEC@ietf.org
https://www.ietf.org/mailman/listinfo/msec


rmat="flowed"; DelSp="yes"
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org

Directions are to send your draft to opsec WG. To get it on their  
charter, you have to request the doc to become a WG item and then  
discussion will follow

-DWard

On Sep 29, 2008, at 8:53 PM, Vishwas Manral wrote:

> Hi Sandy,
>
> Thanks for refering to my draft in your mail. The same was presented
> by Dave (Ward) in the last IETF. Regarding the state of the draft,
> because the RPSEC is closing down, we have been trying to find a home
> for the draft.
>
> We can also solve the problem similarly by something like
> BTNS(ofcourse Multicast part needs to be thought further) which does
> not necessarily require any certificate verification - so we may have
> unauthenticated IKE SA's but then all keys for the CHILD_SA from there
> are automatically generated.
>
> Thanks,
> Vishwas
>
>
_______________________________________________
MSEC mailing list
MSEC@ietf.org
https://www.ietf.org/mailman/listinfo/msec


From msec-bounces@ietf.org  Tue Sep 30 09:13:16 2008
Return-Path: <msec-bounces@ietf.org>
X-Original-To: msec-archive@lists.ietf.org
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 499763A6A2E;
	Tue, 30 Sep 2008 09:13:16 -0700 (PDT)
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F04593A691E;
	Tue, 30 Sep 2008 09:13:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 OHnJR+F2MVGA; Tue, 30 Sep 2008 09:13:14 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id DF7403A67E7;
	Tue, 30 Sep 2008 09:13:13 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,338,1220227200"; d="scan'208";a="84812259"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-1.cisco.com with ESMTP; 30 Sep 2008 16:12:58 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m8UGCw40002981; 
	Tue, 30 Sep 2008 09:12:58 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m8UGCv3B026482;
	Tue, 30 Sep 2008 16:12:58 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Sep 2008 09:12:58 -0700
Received: from [10.32.244.214] ([10.32.244.214]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Sep 2008 09:12:57 -0700
In-Reply-To: <20080929200231.3E5DD3F443@pecan.tislabs.com>
References: <20080929200231.3E5DD3F443@pecan.tislabs.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <174D7A1B-7E6F-4B98-94A8-8174803723E1@cisco.com>
From: Brian Weis <bew@cisco.com>
Date: Tue, 30 Sep 2008 09:14:41 -0700
To: Sandy Murphy <sandy@tislabs.com>
X-Mailer: Apple Mail (2.753.1)
X-OriginalArrivalTime: 30 Sep 2008 16:12:57.0962 (UTC)
	FILETIME=[673694A0:01C92317]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3675; t=1222791178;
	x=1223655178; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=bew@cisco.com;
	z=From:=20Brian=20Weis=20<bew@cisco.com>
	|Subject:=20Re=3A=20[Tsvwg]=20[RPSEC]=20Authentication=20fo
	r=20OSPFv3 |Sender:=20;
	bh=KjgDb/hr33RoXazjjqvua8isYhWhUH5Kth/XJmjLj5c=;
	b=vOxaQOecIl33DdvKWNRYvZ0H9rrDVpjXmCTgGtPvSd/FkYUgPD0+fkALUc
	cILTFKR5kGsuJNbyo9+v8W8UFBeCkm1/a9QMi3TMHrHuhzCDa9F/uOdPREhK
	mQj65P1qYy;
Authentication-Results: sj-dkim-3; header.From=bew@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: msec@ietf.org, tsvwg list IETF <tsvwg@ietf.org>, edward.jankiewicz@sri.com,
	ospf@ietf.org, "secdir@MIT.EDU" <secdir@mit.edu>, rpsec@ietf.org,
	sidr@ietf.org, Ross Callon <rcallon@juniper.net>
Subject: Re: [MSEC] [Tsvwg] [RPSEC] Authentication for OSPFv3
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org


On Sep 29, 2008, at 1:02 PM, Sandy Murphy wrote:

>> What (if any) current initiatives are there that would support  
>> automated
>> key exchange for OSFPv3 authentication?
>
> You have msec on the list of recipients, which is where I (not an  
> active
> participant, mind you) think the answer lies.

I agree with Sandy.

> Both GDOI (RFC 3547) and
> GSAKMP (RFC 4535) are group key management protocols, which is what
> OSPFv3 needs.  Unfortunately, both assume the existence of a group
> controller that plays an important role in distributing keys.  In  
> other
> words, the very democratic all-are-equal many-to-many model of OSPF  
> might find it
> difficult to map to the envisioned group security architecture.  I
> suppose it might be possible to consider the Designated Router as the
> group controller, but as the DR is elected, that might be a  
> difficult fit.

There is an expired individual I-D that explores several options  
along these lines: <http://tools.ietf.org/html/draft-liu-ospfv3- 
automated-keying-req-01>. However, there isn't (in my opinion) an  
obvious way forward. We can allocate some time on the Minneapolis  
MSEC WG agenda on this topic if there's sufficient interest.

Brian

> Even if you solve the group key management problem for OSPFv3, you  
> still
> have the difficulty to doing anti-replay in a multicast environment.
> Manral presented a draft some years ago to the rpsec working group  
> about
> the crypto vulnerabilities of routing protocols, and concentrated for
> OSPFv3 on replay vulnerabilities.  Unfortunately, that did not go  
> anywhere.
>
> Just for fun, I'm adding the routing area ADs and the secdir on  
> this list.
> This is one of those cross-disciplinary concerns that has the right  
> people
> in several different wgs and areas.  The more the merrier, right?
>
> The one quibble I have is that the tsvwg probably has little to do  
> with this
> problem - the transport for OSPFv3 is IP, not TCP, and IP is not  
> the level
> of stuff their charter looks at.
>
> (And sorry for the late reply to your messages, I've been mulling  
> the options.)
>
> --Sandy
>
> ---------  In reply to ------------------------
>
> Date: Tue, 23 Sep 2008 17:52:07 -0400
> From: Ed Jankiewicz <edward.jankiewicz@sri.com>
> To: ospf@ietf.org, rpsec@ietf.org, sidr@ietf.org, msec@ietf.org,  
> tsvwg@ietf.org
> Subject: [RPSEC] Authentication for OSPFv3
>
> I am not an active follower of these lists but have a question.   
> Please
> reply off-list directly to ed.jankiewicz@sri.com or copy me if this
> triggers relevant discussion on your list.
>
> What (if any) current initiatives are there that would support  
> automated
> key exchange for OSFPv3 authentication?  RFC 4552 relies upon pre- 
> shared
> secret keys for generating message digest, but some of my constituents
> have issues with manual generation, distribution and configuration of
> keys in their IPv6 network deployment.  Is any of the current work on
> IKE revisions applicable, any work being done in your working  
> group, or
> do you know of any OSPF-specific solution being developed somewhere?
>
> Thanks.
>
> -- 
> Ed Jankiewicz - SRI International
> Fort Monmouth Branch Office - IPv6 Research
> Supporting DISA Standards Engineering Branch
> 732-389-1003 or  ed.jankiewicz@sri.com
>
> _______________________________________________
> RPSEC mailing list
> RPSEC@ietf.org
> https://www.ietf.org/mailman/listinfo/rpsec
>

-- 
Brian Weis
Router/Switch Security Group, ARTG, Cisco Systems
Telephone: +1 408 526 4796
Email: bew@cisco.com

_______________________________________________
MSEC mailing list
MSEC@ietf.org
https://www.ietf.org/mailman/listinfo/msec


From msec-bounces@ietf.org  Tue Sep 30 09:13:16 2008
Return-Path: <msec-bounces@ietf.org>
X-Original-To: msec-archive@optimus.ietf.org
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 499763A6A2E;
	Tue, 30 Sep 2008 09:13:16 -0700 (PDT)
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F04593A691E;
	Tue, 30 Sep 2008 09:13:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 OHnJR+F2MVGA; Tue, 30 Sep 2008 09:13:14 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id DF7403A67E7;
	Tue, 30 Sep 2008 09:13:13 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,338,1220227200"; d="scan'208";a="84812259"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-1.cisco.com with ESMTP; 30 Sep 2008 16:12:58 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m8UGCw40002981; 
	Tue, 30 Sep 2008 09:12:58 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m8UGCv3B026482;
	Tue, 30 Sep 2008 16:12:58 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Sep 2008 09:12:58 -0700
Received: from [10.32.244.214] ([10.32.244.214]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 30 Sep 2008 09:12:57 -0700
In-Reply-To: <20080929200231.3E5DD3F443@pecan.tislabs.com>
References: <20080929200231.3E5DD3F443@pecan.tislabs.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <174D7A1B-7E6F-4B98-94A8-8174803723E1@cisco.com>
From: Brian Weis <bew@cisco.com>
Date: Tue, 30 Sep 2008 09:14:41 -0700
To: Sandy Murphy <sandy@tislabs.com>
X-Mailer: Apple Mail (2.753.1)
X-OriginalArrivalTime: 30 Sep 2008 16:12:57.0962 (UTC)
	FILETIME=[673694A0:01C92317]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3675; t=1222791178;
	x=1223655178; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=bew@cisco.com;
	z=From:=20Brian=20Weis=20<bew@cisco.com>
	|Subject:=20Re=3A=20[Tsvwg]=20[RPSEC]=20Authentication=20fo
	r=20OSPFv3 |Sender:=20;
	bh=KjgDb/hr33RoXazjjqvua8isYhWhUH5Kth/XJmjLj5c=;
	b=vOxaQOecIl33DdvKWNRYvZ0H9rrDVpjXmCTgGtPvSd/FkYUgPD0+fkALUc
	cILTFKR5kGsuJNbyo9+v8W8UFBeCkm1/a9QMi3TMHrHuhzCDa9F/uOdPREhK
	mQj65P1qYy;
Authentication-Results: sj-dkim-3; header.From=bew@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: msec@ietf.org, tsvwg list IETF <tsvwg@ietf.org>, edward.jankiewicz@sri.com,
	ospf@ietf.org, "secdir@MIT.EDU" <secdir@mit.edu>, rpsec@ietf.org,
	sidr@ietf.org, Ross Callon <rcallon@juniper.net>
Subject: Re: [MSEC] [Tsvwg] [RPSEC] Authentication for OSPFv3
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org


On Sep 29, 2008, at 1:02 PM, Sandy Murphy wrote:

>> What (if any) current initiatives are there that would support  
>> automated
>> key exchange for OSFPv3 authentication?
>
> You have msec on the list of recipients, which is where I (not an  
> active
> participant, mind you) think the answer lies.

I agree with Sandy.

> Both GDOI (RFC 3547) and
> GSAKMP (RFC 4535) are group key management protocols, which is what
> OSPFv3 needs.  Unfortunately, both assume the existence of a group
> controller that plays an important role in distributing keys.  In  
> other
> words, the very democratic all-are-equal many-to-many model of OSPF  
> might find it
> difficult to map to the envisioned group security architecture.  I
> suppose it might be possible to consider the Designated Router as the
> group controller, but as the DR is elected, that might be a  
> difficult fit.

There is an expired individual I-D that explores several options  
along these lines: <http://tools.ietf.org/html/draft-liu-ospfv3- 
automated-keying-req-01>. However, there isn't (in my opinion) an  
obvious way forward. We can allocate some time on the Minneapolis  
MSEC WG agenda on this topic if there's sufficient interest.

Brian

> Even if you solve the group key management problem for OSPFv3, you  
> still
> have the difficulty to doing anti-replay in a multicast environment.
> Manral presented a draft some years ago to the rpsec working group  
> about
> the crypto vulnerabilities of routing protocols, and concentrated for
> OSPFv3 on replay vulnerabilities.  Unfortunately, that did not go  
> anywhere.
>
> Just for fun, I'm adding the routing area ADs and the secdir on  
> this list.
> This is one of those cross-disciplinary concerns that has the right  
> people
> in several different wgs and areas.  The more the merrier, right?
>
> The one quibble I have is that the tsvwg probably has little to do  
> with this
> problem - the transport for OSPFv3 is IP, not TCP, and IP is not  
> the level
> of stuff their charter looks at.
>
> (And sorry for the late reply to your messages, I've been mulling  
> the options.)
>
> --Sandy
>
> ---------  In reply to ------------------------
>
> Date: Tue, 23 Sep 2008 17:52:07 -0400
> From: Ed Jankiewicz <edward.jankiewicz@sri.com>
> To: ospf@ietf.org, rpsec@ietf.org, sidr@ietf.org, msec@ietf.org,  
> tsvwg@ietf.org
> Subject: [RPSEC] Authentication for OSPFv3
>
> I am not an active follower of these lists but have a question.   
> Please
> reply off-list directly to ed.jankiewicz@sri.com or copy me if this
> triggers relevant discussion on your list.
>
> What (if any) current initiatives are there that would support  
> automated
> key exchange for OSFPv3 authentication?  RFC 4552 relies upon pre- 
> shared
> secret keys for generating message digest, but some of my constituents
> have issues with manual generation, distribution and configuration of
> keys in their IPv6 network deployment.  Is any of the current work on
> IKE revisions applicable, any work being done in your working  
> group, or
> do you know of any OSPF-specific solution being developed somewhere?
>
> Thanks.
>
> -- 
> Ed Jankiewicz - SRI International
> Fort Monmouth Branch Office - IPv6 Research
> Supporting DISA Standards Engineering Branch
> 732-389-1003 or  ed.jankiewicz@sri.com
>
> _______________________________________________
> RPSEC mailing list
> RPSEC@ietf.org
> https://www.ietf.org/mailman/listinfo/rpsec
>

-- 
Brian Weis
Router/Switch Security Group, ARTG, Cisco Systems
Telephone: +1 408 526 4796
Email: bew@cisco.com

_______________________________________________
MSEC mailing list
MSEC@ietf.org
https://www.ietf.org/mailman/listinfo/msec


From msec-bounces@ietf.org  Tue Sep 30 09:30:15 2008
Return-Path: <msec-bounces@ietf.org>
X-Original-To: msec-archive@lists.ietf.org
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E08CE28C0EB;
	Tue, 30 Sep 2008 09:30:15 -0700 (PDT)
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D4CAE3A6A17;
	Tue, 30 Sep 2008 09:30:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.352
X-Spam-Level: 
X-Spam-Status: No, score=-6.352 tagged_above=-999 required=5 tests=[AWL=0.247, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 6vy9ImPvysD2; Tue, 30 Sep 2008 09:30:10 -0700 (PDT)
Received: from nutshell.tislabs.com (ns1.tislabs.com [192.94.214.100])
	by core3.amsl.com (Postfix) with ESMTP id D87063A6B67;
	Tue, 30 Sep 2008 09:30:09 -0700 (PDT)
Received: (from uucp@localhost)
	by nutshell.tislabs.com (8.12.9/8.12.9) id m8UGTuJa016359;
	Tue, 30 Sep 2008 12:29:56 -0400 (EDT)
Received: from nodnsquery(10.66.1.30) by nutshell.tislabs.com via csmap (V6.0)
	id srcAAAt_aW8F; Tue, 30 Sep 08 12:29:56 -0400
Received: by pecan.tislabs.com (Postfix, from userid 2005)
	id C92963F446; Tue, 30 Sep 2008 12:28:23 -0400 (EDT)
To: acee@redback.com, vishwas.ietf@gmail.com
In-Reply-To: <77ead0ec0809300842i200798d5ic45f7996a19d57d@mail.gmail.com>
Message-Id: <20080930162823.C92963F446@pecan.tislabs.com>
Date: Tue, 30 Sep 2008 12:28:23 -0400 (EDT)
From: sandy@tislabs.com (Sandy Murphy)
Cc: msec@ietf.org, tsvwg@ietf.org, ospf@ietf.org, rbonica@juniper.net,
	secdir@mit.edu, rpsec@ietf.org, sidr@ietf.org, rcallon@juniper.net
Subject: Re: [MSEC] [OSPF] [sidr] [RPSEC] Authentication for OSPFv3
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org

>I agree to what you say and the general sense of the room in the KMART BOF.
>That is the reason I proposed a BTNS based solution. Which uses GTSM
>in the IKe to do the first level security.

I am not quite sure I understand the use of GTSM here.  The need for
authentication for OSPF is that you don't trust that everyone on the
local broadcast link is OK.  GTSM tells you that the sender came from
one-hop away, i.e., on the local broadcast link.  Since you already know
that you don't trust everyone one-hop away, how does the use of GTSM
help?

--Sandy
_______________________________________________
MSEC mailing list
MSEC@ietf.org
https://www.ietf.org/mailman/listinfo/msec


From msec-bounces@ietf.org  Tue Sep 30 09:30:15 2008
Return-Path: <msec-bounces@ietf.org>
X-Original-To: msec-archive@optimus.ietf.org
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E08CE28C0EB;
	Tue, 30 Sep 2008 09:30:15 -0700 (PDT)
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D4CAE3A6A17;
	Tue, 30 Sep 2008 09:30:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.352
X-Spam-Level: 
X-Spam-Status: No, score=-6.352 tagged_above=-999 required=5 tests=[AWL=0.247, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 6vy9ImPvysD2; Tue, 30 Sep 2008 09:30:10 -0700 (PDT)
Received: from nutshell.tislabs.com (ns1.tislabs.com [192.94.214.100])
	by core3.amsl.com (Postfix) with ESMTP id D87063A6B67;
	Tue, 30 Sep 2008 09:30:09 -0700 (PDT)
Received: (from uucp@localhost)
	by nutshell.tislabs.com (8.12.9/8.12.9) id m8UGTuJa016359;
	Tue, 30 Sep 2008 12:29:56 -0400 (EDT)
Received: from nodnsquery(10.66.1.30) by nutshell.tislabs.com via csmap (V6.0)
	id srcAAAt_aW8F; Tue, 30 Sep 08 12:29:56 -0400
Received: by pecan.tislabs.com (Postfix, from userid 2005)
	id C92963F446; Tue, 30 Sep 2008 12:28:23 -0400 (EDT)
To: acee@redback.com, vishwas.ietf@gmail.com
In-Reply-To: <77ead0ec0809300842i200798d5ic45f7996a19d57d@mail.gmail.com>
Message-Id: <20080930162823.C92963F446@pecan.tislabs.com>
Date: Tue, 30 Sep 2008 12:28:23 -0400 (EDT)
From: sandy@tislabs.com (Sandy Murphy)
Cc: msec@ietf.org, tsvwg@ietf.org, ospf@ietf.org, rbonica@juniper.net,
	secdir@mit.edu, rpsec@ietf.org, sidr@ietf.org, rcallon@juniper.net
Subject: Re: [MSEC] [OSPF] [sidr] [RPSEC] Authentication for OSPFv3
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org

>I agree to what you say and the general sense of the room in the KMART BOF.
>That is the reason I proposed a BTNS based solution. Which uses GTSM
>in the IKe to do the first level security.

I am not quite sure I understand the use of GTSM here.  The need for
authentication for OSPF is that you don't trust that everyone on the
local broadcast link is OK.  GTSM tells you that the sender came from
one-hop away, i.e., on the local broadcast link.  Since you already know
that you don't trust everyone one-hop away, how does the use of GTSM
help?

--Sandy
_______________________________________________
MSEC mailing list
MSEC@ietf.org
https://www.ietf.org/mailman/listinfo/msec


From msec-bounces@ietf.org  Tue Sep 30 09:37:45 2008
Return-Path: <msec-bounces@ietf.org>
X-Original-To: msec-archive@optimus.ietf.org
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 17F5C28C186;
	Tue, 30 Sep 2008 09:37:45 -0700 (PDT)
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1ED403A6A32;
	Tue, 30 Sep 2008 09:37:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.397
X-Spam-Level: 
X-Spam-Status: No, score=-6.397 tagged_above=-999 required=5 tests=[AWL=0.202, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Ddfk6jL8o0TY; Tue, 30 Sep 2008 09:37:37 -0700 (PDT)
Received: from nutshell.tislabs.com (nutshell.tislabs.com [192.94.214.100])
	by core3.amsl.com (Postfix) with ESMTP id A5B5D28C159;
	Tue, 30 Sep 2008 09:37:37 -0700 (PDT)
Received: (from uucp@localhost)
	by nutshell.tislabs.com (8.12.9/8.12.9) id m8UGbaHB016363;
	Tue, 30 Sep 2008 12:37:36 -0400 (EDT)
Received: from nodnsquery(10.66.1.30) by nutshell.tislabs.com via csmap (V6.0)
	id srcAAAmAaq9F; Tue, 30 Sep 08 12:37:36 -0400
Received: by pecan.tislabs.com (Postfix, from userid 2005)
	id 558D13F46F; Tue, 30 Sep 2008 12:36:04 -0400 (EDT)
To: acee@redback.com, vishwas.ietf@gmail.com
In-Reply-To: <77ead0ec0809300842i200798d5ic45f7996a19d57d@mail.gmail.com>
Message-Id: <20080930163604.558D13F46F@pecan.tislabs.com>
Date: Tue, 30 Sep 2008 12:36:04 -0400 (EDT)
From: sandy@tislabs.com (Sandy Murphy)
Cc: msec@ietf.org, tsvwg@ietf.org, ospf@ietf.org, rbonica@juniper.net,
	secdir@mit.edu, rpsec@ietf.org, sidr@ietf.org, rcallon@juniper.net
Subject: Re: [MSEC] [OSPF] [sidr] [RPSEC] Authentication for OSPFv3
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org

By the way, to everyone who sees this message, the mail chain is really
broken.  Ed's message did not get to all the wg lists on his message,
and I got several "too many recipients" errors on my reply.  If you look
at the mail archives for the various wg, not any of them have caught all
the messages that have been send.

I think the secdir archive got most of the messages (except the one that
Dave Ward cut down to just the rpsec list :-)), but it is not a public
list.

I'm not even sure that Ed, who originally posed the question, is seeing
the exchange.  (Ed's message was attached to my reply, if you saw that.)

I was able to push out the messages that got trapped for the sidr list,
but if any other wg chairs could do their bit, maybe the conversation
will be less fractured.

Or maybe we should just all choose one list to do the conversation.

--Sandy
_______________________________________________
MSEC mailing list
MSEC@ietf.org
https://www.ietf.org/mailman/listinfo/msec


From msec-bounces@ietf.org  Tue Sep 30 09:37:45 2008
Return-Path: <msec-bounces@ietf.org>
X-Original-To: msec-archive@lists.ietf.org
Delivered-To: ietfarch-msec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 17F5C28C186;
	Tue, 30 Sep 2008 09:37:45 -0700 (PDT)
X-Original-To: msec@core3.amsl.com
Delivered-To: msec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1ED403A6A32;
	Tue, 30 Sep 2008 09:37:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.397
X-Spam-Level: 
X-Spam-Status: No, score=-6.397 tagged_above=-999 required=5 tests=[AWL=0.202, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Ddfk6jL8o0TY; Tue, 30 Sep 2008 09:37:37 -0700 (PDT)
Received: from nutshell.tislabs.com (nutshell.tislabs.com [192.94.214.100])
	by core3.amsl.com (Postfix) with ESMTP id A5B5D28C159;
	Tue, 30 Sep 2008 09:37:37 -0700 (PDT)
Received: (from uucp@localhost)
	by nutshell.tislabs.com (8.12.9/8.12.9) id m8UGbaHB016363;
	Tue, 30 Sep 2008 12:37:36 -0400 (EDT)
Received: from nodnsquery(10.66.1.30) by nutshell.tislabs.com via csmap (V6.0)
	id srcAAAmAaq9F; Tue, 30 Sep 08 12:37:36 -0400
Received: by pecan.tislabs.com (Postfix, from userid 2005)
	id 558D13F46F; Tue, 30 Sep 2008 12:36:04 -0400 (EDT)
To: acee@redback.com, vishwas.ietf@gmail.com
In-Reply-To: <77ead0ec0809300842i200798d5ic45f7996a19d57d@mail.gmail.com>
Message-Id: <20080930163604.558D13F46F@pecan.tislabs.com>
Date: Tue, 30 Sep 2008 12:36:04 -0400 (EDT)
From: sandy@tislabs.com (Sandy Murphy)
Cc: msec@ietf.org, tsvwg@ietf.org, ospf@ietf.org, rbonica@juniper.net,
	secdir@mit.edu, rpsec@ietf.org, sidr@ietf.org, rcallon@juniper.net
Subject: Re: [MSEC] [OSPF] [sidr] [RPSEC] Authentication for OSPFv3
X-BeenThere: msec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Security List <msec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/msec>
List-Post: <mailto:msec@ietf.org>
List-Help: <mailto:msec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/msec>,
	<mailto:msec-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: msec-bounces@ietf.org
Errors-To: msec-bounces@ietf.org

By the way, to everyone who sees this message, the mail chain is really
broken.  Ed's message did not get to all the wg lists on his message,
and I got several "too many recipients" errors on my reply.  If you look
at the mail archives for the various wg, not any of them have caught all
the messages that have been send.

I think the secdir archive got most of the messages (except the one that
Dave Ward cut down to just the rpsec list :-)), but it is not a public
list.

I'm not even sure that Ed, who originally posed the question, is seeing
the exchange.  (Ed's message was attached to my reply, if you saw that.)

I was able to push out the messages that got trapped for the sidr list,
but if any other wg chairs could do their bit, maybe the conversation
will be less fractured.

Or maybe we should just all choose one list to do the conversation.

--Sandy
_______________________________________________
MSEC mailing list
MSEC@ietf.org
https://www.ietf.org/mailman/listinfo/msec


