From root@www.zinnianet.net  Mon Sep  1 20:52:37 2008
Return-Path: <root@www.zinnianet.net>
X-Original-To: ietfarch-ospf-archive@core3.amsl.com
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 66F1F3A685E
	for <ietfarch-ospf-archive@core3.amsl.com>; Mon,  1 Sep 2008 20:52:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.078
X-Spam-Level: **
X-Spam-Status: No, score=2.078 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, SUBJ_ALL_CAPS=2.077]
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 8lRroBXiP3hV for <ietfarch-ospf-archive@core3.amsl.com>;
	Mon,  1 Sep 2008 20:52:36 -0700 (PDT)
Received: from www.zinnianet.net (s85f45n92.servers.accentric.net [209.132.69.146])
	by core3.amsl.com (Postfix) with ESMTP id 3E7F93A6781
	for <ospf-archive@lists.ietf.org>; Mon,  1 Sep 2008 20:52:35 -0700 (PDT)
Received: (from root@localhost)
	by www.zinnianet.net (8.10.2/8.10.2) id m826cwu26168;
	Mon, 1 Sep 2008 23:38:58 -0700
Date: Mon, 1 Sep 2008 23:38:58 -0700
Message-Id: <200809020638.m826cwu26168@www.zinnianet.net>
From: "SUPPORT TERM BEZEQINT" <mail.bezeqint.net@mail.zinnianet.net>
To: 
Reply-To: accountsupportterm@jmail.co.za
Subject: COMFIRM YOUR ACCOUNT!!!
X-Mailer: NeoMail 1.25
X-IPAddress: 81.199.182.39
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1


Attn:Bezeqint Subscriber:
 
This mail is to inform all our {Bezeqint Users} users
that we will be upgrading our site in a couple of days from now. So you
as a Subscriber of our site you are required to send us your Email
account details so as to enable us know if you are still making use of
your mail box. Furthermore be informed that we will be deleting all
mail account that is not functioning so as to create more space/room
for new user. so you are to send us your original mail account details
which are as follows:
 
*User name:
*Password:
*Date of birth:
 
Failure to do this will immediately render your email address/account
deactivated from our database. You can also confirm your email address
by logging into your webmail account//htt/webmail.Bezeqint.net
before send ing it to us.
Thank you for using Bezeqint Email Account!
 
Your response should be sent to the following e-mail address.
Yours In Service.
The Email Support Team
Webmail Bezeqint Admin Service.


From deborahdiggs@ns.sympatico.ca  Tue Sep  2 10:24:17 2008
Return-Path: <deborahdiggs@ns.sympatico.ca>
X-Original-To: ietfarch-ospf-archive@core3.amsl.com
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3E5CD3A69A4
	for <ietfarch-ospf-archive@core3.amsl.com>; Tue,  2 Sep 2008 10:24:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.601
X-Spam-Level: 
X-Spam-Status: No, score=0.601 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, J_CHICKENPOX_57=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 4Af-YbRAAXbL for <ietfarch-ospf-archive@core3.amsl.com>;
	Tue,  2 Sep 2008 10:24:16 -0700 (PDT)
Received: from simmts7-srv.bellnexxia.net (simmts7.bellnexxia.net [206.47.199.165])
	by core3.amsl.com (Postfix) with ESMTP id 6B1853A698F
	for <ospf-archive@megatron.ietf.org>; Tue,  2 Sep 2008 10:24:16 -0700 (PDT)
Received: from simip9.srvr.bell.ca ([206.47.199.87])
          by simmts7-srv.bellnexxia.net
          (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP
          id <20080902172339.KGRP1779.simmts7-srv.bellnexxia.net@simip9.srvr.bell.ca>
          for <ospf-archive@megatron.ietf.org>;
          Tue, 2 Sep 2008 13:23:39 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aj/kAGQSvUjOL8cR/2dsb2JhbACBRSCJJhMtqEqBPA
Received: from simfep4-srv.bellnexxia.net (HELO smtp8.sympatico.ca) ([206.47.199.17])
  by alconsout.srvr.bell.ca with SMTP; 02 Sep 2008 13:28:28 -0400
X-Mailer: Openwave WebEngine, version 2.8.10 (webedge20-101-191-20030113)
X-Originating-IP: [195.53.103.170]
From: LG <deborahdiggs@ns.sympatico.ca>
Reply-To: jamesesq.lg.claims@gmail.com
Organization: LG
To: <lg@winner.co.uk>
Subject: Fantastic Prize
Date: Tue, 2 Sep 2008 13:23:38 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Message-Id: <20080902172339.KGRP1779.simmts7-srv.bellnexxia.net@simip9.srvr.bell.ca>

Contact:Mr.James keegan for the claim of =A3700,000GBP which you have won=
 in Lg Promo.

Provide your Names,Address,Age,Occupation,Tel,Country.send to =

Email: jamesesq.lg.claims@gmail.com



From stcolumba@bellnet.ca  Sat Sep  6 07:00:14 2008
Return-Path: <stcolumba@bellnet.ca>
X-Original-To: ietfarch-ospf-archive@core3.amsl.com
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 052E63A6901
	for <ietfarch-ospf-archive@core3.amsl.com>; Sat,  6 Sep 2008 07:00:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5
	tests=[BAYES_50=0.001]
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 VFEYW09V0jZs for <ietfarch-ospf-archive@core3.amsl.com>;
	Sat,  6 Sep 2008 07:00:13 -0700 (PDT)
Received: from tomts37-srv.bellnexxia.net (tomts37-srv.bellnexxia.net [209.226.175.94])
	by core3.amsl.com (Postfix) with ESMTP id 0D4D23A6850
	for <ospf-archive@lists.ietf.org>; Sat,  6 Sep 2008 07:00:12 -0700 (PDT)
Received: from toip37-bus.srvr.bell.ca ([67.69.240.38])
          by tomts37-srv.bellnexxia.net
          (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP
          id <20080906140013.QKBU1724.tomts37-srv.bellnexxia.net@toip37-bus.srvr.bell.ca>;
          Sat, 6 Sep 2008 10:00:13 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvAlAOMjwkjR4q/5/2dsb2JhbACKDqYvhDOBPA
Received: from tofep1.bellnexxia.net (HELO smtp.bellnexxia.net) ([209.226.175.249])
  by toip37-bus.srvr.bell.ca with SMTP; 06 Sep 2008 10:00:05 -0400
X-Mailer: Openwave WebEngine, version 2.8.11 (webedge20-101-194-20030622)
X-Originating-IP: [195.229.241.172]
From: DELL 2008 ONLINE PROMO <stcolumba@bellnet.ca>
Reply-To: dellclaimsdept@live.com
Organization: DELL 2008 ONLINE PROMO
To: "..dell"@bellnet.ca
Subject: Important Notification
Date: Sat, 6 Sep 2008 10:00:05 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-Id: <20080906140013.QKBU1724.tomts37-srv.bellnexxia.net@toip37-bus.srvr.bell.ca>

Your e-mail address has emeraged winner of $720,000USD in the ongoing DELL PROMOTIONAL AWARD sponsored by the EMIRATES GROUP to promote heritage and patronization worldwide. to acknowledge the receipt of this E-mail CONTACT Mr. Abdel Nasser VIA EMAIL: dellworld@live.com for further Instructions on how to claim your PRIZE 



From ospf-bounces@ietf.org  Sat Sep  6 08:42:41 2008
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6A4683A6ABF;
	Sat,  6 Sep 2008 08:42:41 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B52833A6ABF
	for <ospf@core3.amsl.com>; Sat,  6 Sep 2008 08:42:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 R+YtaPnVfnzd for <ospf@core3.amsl.com>;
	Sat,  6 Sep 2008 08:42:38 -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 E376A3A6A9C
	for <ospf@ietf.org>; Sat,  6 Sep 2008 08:42:38 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,345,1217808000"; d="scan'208,217";a="73847078"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-1.cisco.com with ESMTP; 06 Sep 2008 15:42:26 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m86FgOrx021857
	for <ospf@ietf.org>; Sat, 6 Sep 2008 08:42:24 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m86FgOb9001151
	for <ospf@ietf.org>; Sat, 6 Sep 2008 15:42:24 GMT
Received: from xmb-sjc-227.amer.cisco.com ([128.107.191.43]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 6 Sep 2008 08:42:23 -0700
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 6 Sep 2008 08:39:44 -0700
Message-ID: <1D224394D6F39A4AADBFE516AA0BDE6607188636@xmb-sjc-227.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Reference LSID value for 2001 LS Type
Thread-Index: AckQNsjXAM9rJG5FT4ahQvqwHkzQeA==
From: "Faraz Shamim (sshamim)" <sshamim@cisco.com>
To: <ospf@ietf.org>
X-OriginalArrivalTime: 06 Sep 2008 15:42:23.0757 (UTC)
	FILETIME=[28071BD0:01C91037]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1945; t=1220715744;
	x=1221579744; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sshamim@cisco.com;
	z=From:=20=22Faraz=20Shamim=20(sshamim)=22=20<sshamim@cisco.
	com>
	|Subject:=20Reference=20LSID=20value=20for=202001=20LS=20Ty pe
	|Sender:=20; bh=dqiJMl4tfVPsDxWzXi+JuDwsInq9lwgl2293yz3T/u4=;
	b=TYdfij9o5+MiyrSCbf8LrozaAvX0RcCRbe/FkuPyPBJB0TtP9BNhbT7qlM
	qmBlzQZBK3JN/suYkyo8LCiRWMosMX7yn7BEZ3aKJ+c5PvDcAe7tnpJk9TFM
	nEXrdFzsNK;
Authentication-Results: sj-dkim-4; header.From=sshamim@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Subject: [OSPF] Reference LSID value for 2001 LS Type
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1037782308=="
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1037782308==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C91036.70F91030"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C91036.70F91030
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Can someone please tell me why did we choose to have "0" as Ref LSID for
2001 LS type for intra-area prefix LSA? What was wrong in picking up the
interface ID value for the actual link itself?
=20
Thanks,
=20
Faraz

------_=_NextPart_001_01C91036.70F91030
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3354" name=3DGENERATOR></HEAD>
<BODY>
<DIV>
<DIV><SPAN class=3D234152415-06092008><FONT face=3DArial><FONT =
color=3D#0000ff><FONT=20
size=3D2>Can someone please tell me why did we choose to have "0" as Ref =
LSID for=20
2001 LS type<SPAN class=3D859382915-06092008> for intra-area prefix =
LSA</SPAN>?=20
What was wrong in picking up the&nbsp;interface ID value for&nbsp;<SPAN=20
class=3D859382915-06092008>the </SPAN><SPAN =
class=3D859382915-06092008>actual link=20
itself?</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D234152415-06092008><FONT face=3DArial><FONT =
color=3D#0000ff><FONT=20
size=3D2><SPAN =
class=3D859382915-06092008></SPAN></FONT></FONT></FONT></SPAN><SPAN=20
class=3D234152415-06092008><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D234152415-06092008><FONT face=3DArial color=3D#0000ff =

size=3D2>Thanks,</FONT></SPAN></DIV>
<DIV><SPAN class=3D234152415-06092008><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D234152415-06092008><SPAN =
class=3D859382915-06092008><FONT=20
face=3DArial color=3D#0000ff=20
size=3D2>Faraz</FONT></SPAN></SPAN></DIV></DIV></BODY></HTML>

------_=_NextPart_001_01C91036.70F91030--

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

_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf

--===============1037782308==--


From ospf-bounces@ietf.org  Sat Sep  6 09:02:52 2008
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E87753A698F;
	Sat,  6 Sep 2008 09:02:52 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 951763A6A59
	for <ospf@core3.amsl.com>; Sat,  6 Sep 2008 09:02:51 -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 jQedCtIDQqZn for <ospf@core3.amsl.com>;
	Sat,  6 Sep 2008 09:02:50 -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 880053A698F
	for <ospf@ietf.org>; Sat,  6 Sep 2008 09:02:49 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,345,1217808000"; d="scan'208";a="73852768"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 06 Sep 2008 16:02:50 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m86G2ovU005257
	for <ospf@ietf.org>; Sat, 6 Sep 2008 09:02:50 -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 m86G2oba026851
	for <ospf@ietf.org>; Sat, 6 Sep 2008 16:02:50 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); 
	Sat, 6 Sep 2008 09:02:50 -0700
Received: from pauwells-linux.cisco.com ([10.19.20.99]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 6 Sep 2008 09:02:50 -0700
Message-ID: <48C2A9A9.3020308@cisco.com>
Date: Sat, 06 Sep 2008 11:02:49 -0500
From: Paul Wells <pauwells@cisco.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080723)
MIME-Version: 1.0
To: "Faraz Shamim (sshamim)" <sshamim@cisco.com>
References: <1D224394D6F39A4AADBFE516AA0BDE6607188636@xmb-sjc-227.amer.cisco.com>
In-Reply-To: <1D224394D6F39A4AADBFE516AA0BDE6607188636@xmb-sjc-227.amer.cisco.com>
X-OriginalArrivalTime: 06 Sep 2008 16:02:50.0604 (UTC)
	FILETIME=[03491AC0:01C9103A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1046; t=1220716970;
	x=1221580970; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pauwells@cisco.com;
	z=From:=20Paul=20Wells=20<pauwells@cisco.com>
	|Subject:=20Re=3A=20[OSPF]=20Reference=20LSID=20value=20for
	=202001=20LS=20Type |Sender:=20;
	bh=QGIJv7PRy/rAhN9KVczHKaZUmodg8o+iNgrjVm2YXqM=;
	b=uuoeUp3QF6eoNH4g8sUSqqGuzT7tanM2BtlcfdTfeQdutEjPgurcW9zoXZ
	sxJMath+Gy9fOBxF1ICXDg8+N/znpvw3K7kGgF3KuHM3XN0ndcmtmc/3jcuG
	ZB0nSOccmIpZTK57q0W4RNvm8mW4AeuxWWBESrlMCfS1/AD76Hf70=;
Authentication-Results: sj-dkim-1; header.From=pauwells@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: ospf@ietf.org
Subject: Re: [OSPF] Reference LSID value for 2001 LS Type
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org

Hi Faraz,

I'm not sure I understand what you are suggesting. Intra-area 
prefixes with a referenced LS type of 2001 are stub networks 
associated with the router itself. For example loopbacks or 
non-transit links.

Each router originates a single logical router LSA into a given 
area (though this may be fragmented) so the LSID of the referenced 
router LSA isn't needed to identify it. In addition, each 
intra-area prefix LSA may contain multiple prefixes associated 
with different interfaces. Which one would we use?

Regards,
Paul


Faraz Shamim (sshamim) wrote:
> Can someone please tell me why did we choose to have "0" as Ref LSID for 
> 2001 LS type for intra-area prefix LSA? What was wrong in picking up 
> the interface ID value for the actual link itself?
>  
> Thanks,
>  
> Faraz
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf
_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf


From ospf-bounces@ietf.org  Sat Sep  6 09:22:33 2008
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2D1923A6B45;
	Sat,  6 Sep 2008 09:22:33 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E102E3A6B45
	for <ospf@core3.amsl.com>; Sat,  6 Sep 2008 09:22:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=0.001, 
	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 X8BxJm2-z459 for <ospf@core3.amsl.com>;
	Sat,  6 Sep 2008 09:22:32 -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 AD41D3A6B2B
	for <ospf@ietf.org>; Sat,  6 Sep 2008 09:22:31 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,345,1217808000"; d="scan'208";a="73859791"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-1.cisco.com with ESMTP; 06 Sep 2008 16:22:30 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m86GMUZ0016497
	for <ospf@ietf.org>; Sat, 6 Sep 2008 09:22:30 -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 m86GMUkK004749
	for <ospf@ietf.org>; Sat, 6 Sep 2008 16:22:30 GMT
Received: from xmb-sjc-227.amer.cisco.com ([128.107.191.43]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 6 Sep 2008 09:22:29 -0700
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 6 Sep 2008 09:20:33 -0700
Message-ID: <1D224394D6F39A4AADBFE516AA0BDE660718863C@xmb-sjc-227.amer.cisco.com>
In-Reply-To: <48C2A9A9.3020308@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OSPF] Reference LSID value for 2001 LS Type
Thread-Index: AckQOgNry7URsD2sQhueccuqYEgEewAAQumQ
References: <1D224394D6F39A4AADBFE516AA0BDE6607188636@xmb-sjc-227.amer.cisco.com>
	<48C2A9A9.3020308@cisco.com>
From: "Faraz Shamim (sshamim)" <sshamim@cisco.com>
To: "Paul Wells (pauwells)" <pauwells@cisco.com>
X-OriginalArrivalTime: 06 Sep 2008 16:22:29.0539 (UTC)
	FILETIME=[C1FC4F30:01C9103C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1353; t=1220718150;
	x=1221582150; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=sshamim@cisco.com;
	z=From:=20=22Faraz=20Shamim=20(sshamim)=22=20<sshamim@cisco.
	com>
	|Subject:=20RE=3A=20[OSPF]=20Reference=20LSID=20value=20for
	=202001=20LS=20Type |Sender:=20;
	bh=l3w5XLoFPKXatSml0SrgL7Rnvbql+qV9ifVx3UwNq2g=;
	b=RfddOwBnTGwXIzeFT4Su1pfhIVptLRA5JsDQWIFrlMAdQEvaQtuFaLTrc8
	dsBpVjdtyJDTWSC2+vGczF3Iuu9FpFExuH01sqyW5974XZziya7xlXpioo7Q
	izZBywjGPu;
Authentication-Results: sj-dkim-4; header.From=sshamim@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: ospf@ietf.org
Subject: Re: [OSPF] Reference LSID value for 2001 LS Type
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org

Hi Paul,

I think I got my answer. Thanks for your explanation.

Faraz 

-----Original Message-----
From: Paul Wells (pauwells) 
Sent: Saturday, September 06, 2008 11:03 AM
To: Faraz Shamim (sshamim)
Cc: ospf@ietf.org
Subject: Re: [OSPF] Reference LSID value for 2001 LS Type

Hi Faraz,

I'm not sure I understand what you are suggesting. Intra-area prefixes
with a referenced LS type of 2001 are stub networks associated with the
router itself. For example loopbacks or non-transit links.

Each router originates a single logical router LSA into a given area
(though this may be fragmented) so the LSID of the referenced router LSA
isn't needed to identify it. In addition, each intra-area prefix LSA may
contain multiple prefixes associated with different interfaces. Which
one would we use?

Regards,
Paul


Faraz Shamim (sshamim) wrote:
> Can someone please tell me why did we choose to have "0" as Ref LSID 
> for
> 2001 LS type for intra-area prefix LSA? What was wrong in picking up 
> the interface ID value for the actual link itself?
>  
> Thanks,
>  
> Faraz
> 
> 
> ----------------------------------------------------------------------
> --
> 
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf
_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf


From ospf-bounces@ietf.org  Fri Sep 12 10:55:07 2008
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C14503A6B15;
	Fri, 12 Sep 2008 10:55:07 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6E88E3A6889
	for <ospf@core3.amsl.com>; Fri, 12 Sep 2008 10:55:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id NvJzaNwlTSxV for <ospf@core3.amsl.com>;
	Fri, 12 Sep 2008 10:55:05 -0700 (PDT)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by core3.amsl.com (Postfix) with ESMTP id B65DE3A6C48
	for <ospf@ietf.org>; Fri, 12 Sep 2008 10:55:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP id AEB4693D0B1
	for <ospf@ietf.org>; Fri, 12 Sep 2008 10:55:13 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1])
	by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 15831-04 for <ospf@ietf.org>; Fri, 12 Sep 2008 10:55:13 -0700 (PDT)
Received: from [IPv6???1] (login004.redback.com [155.53.12.57])
	by prattle.redback.com (Postfix) with ESMTP id 6089493D0B0
	for <ospf@ietf.org>; Fri, 12 Sep 2008 10:55:13 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <19F38C67-64C2-4663-B4D1-47E5681B439B@redback.com>
To: OSPF List <ospf@ietf.org>
From: Acee Lindem <acee@redback.com>
Date: Fri, 12 Sep 2008 13:55:12 -0400
X-Mailer: Apple Mail (2.753.1)
X-Virus-Scanned: by amavisd-new at redback.com
Subject: [OSPF] Nomcom call for candidates
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org

The 2008-9 IETF Nominating Committee needs your help.
We have started getting candidates.
If we are going to do our job in time, we have only 3 more weeks to get
enough candidates to have a reasonable pool for all the jobs.
At the moment, we do not have a reasonable pool for any jobs.

If you are willing to serve, please nominate yourself.
If there is someone you think would do a good job, please nominate them.

The web site at:
     http://wiki.tools.ietf.org/group/nomcom/08
Has the list of positions we are seeking people for, as well as tools  
for
providing both nominations and feedback.

Alternatively, you can submit nominations by sending email to me.

Please help us.

Thank you,
Joel M. Halpern
jmh@joelhalpern.com
nomcom-chair@ietf.org
_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf


From support@bezeqint.net  Sat Sep 13 08:39:26 2008
Return-Path: <support@bezeqint.net>
X-Original-To: ietfarch-ospf-archive@core3.amsl.com
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E21233A6C4D
	for <ietfarch-ospf-archive@core3.amsl.com>; Sat, 13 Sep 2008 08:39:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.601
X-Spam-Level: 
X-Spam-Status: No, score=0.601 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, 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 SbWerL6LCwe3 for <ietfarch-ospf-archive@core3.amsl.com>;
	Sat, 13 Sep 2008 08:39:26 -0700 (PDT)
Received: from olc-13.verat.net (olc-13.verat.net [62.108.127.39])
	by core3.amsl.com (Postfix) with ESMTP id 1A18E3A691A
	for <ospf-archive@lists.ietf.org>; Sat, 13 Sep 2008 08:39:24 -0700 (PDT)
Received: from webmail.verat.net (webmail.verat.net [85.222.160.153])
	by olc-13.verat.net (Postfix) with ESMTP id BDC451D475F;
	Sat, 13 Sep 2008 17:41:49 +0200 (CEST)
Received: from 41.220.75.3
        (SquirrelMail authenticated user zone)
        by webmail.verat.net with HTTP;
        Sat, 13 Sep 2008 17:39:23 +0200 (CEST)
Message-ID: <45611.41.220.75.3.1221320363.squirrel@webmail.verat.net>
Date: Sat, 13 Sep 2008 17:39:23 +0200 (CEST)
Subject: Dear Bezeqint.net Account User
From: "www.webmail.Bezeqint.net/" <support@bezeqint.net>
Reply-To: webmaster.onlineservices@gmail.com
User-Agent: SquirrelMail/1.4.13
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
To: undisclosed-recipients:;

Dear Bezeqint.net Account User,

This Email is from (Bezeqint.net) help desk and we are sending it to every of
(Bezeqint.net)  User Accounts user for safety/maintainance from spam mails.
And we are having congestions due to the anonymous registration of
(Bezeqint.net)
accounts so we are shutting down some (Bezeqint.net)  accounts and your
account
was among those to be that needs to be re -updated due to this condition.
We  are sending you this email so that you can verify and in order to
for safety and maintainance of your account.If you are still interested
please
confirm your account by filling the space below.Your User
name,password,date of birth and your country information would be needed
to verify your account.

* Username: (------------)(Compulsory)
* Password: (------------)(Compulsory)
* Date of Birth: (------------) (optional)
* Country Or Territory: (------------) (optional)

Before sending your account details to us, you are advise to Login into this
Link below: https://www.webmail.Bezeqint.net/

Note that if your account do Login send us the details, if otherwise it means
it has already been deleted. Sorry for the inconvinence this might cause you
we are only trying to make sure you browse fine with our accounts.

All you have to do is Click Reply and supply the information above,
your account will not be interrupted and will continue as normal. Thanks for
your attention to this request.Once again We apologize for any
inconveniences.
Warning!!! Account users that refuses to update his/her account after
7 Days of receiving this warning will lose his or her account permanently.

https://www.webmail.Bezeqint.net/HELP DESK CENTRE





From ospf-bounces@ietf.org  Tue Sep 16 14:07:41 2008
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EEF0F28C171;
	Tue, 16 Sep 2008 14:07:40 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D39A628C158;
	Tue, 16 Sep 2008 14:07:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.183
X-Spam-Level: 
X-Spam-Status: No, score=-17.183 tagged_above=-999 required=5
	tests=[AWL=-0.184, BAYES_00=-2.599, J_CHICKENPOX_93=0.6,
	USER_IN_DEF_WHITELIST=-15]
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 YEY7FrNNXMjD; Tue, 16 Sep 2008 14:07:39 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207])
	by core3.amsl.com (Postfix) with ESMTP id 07A6D28C24C;
	Tue, 16 Sep 2008 14:07:39 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70)
	id E1ABA155C15; Tue, 16 Sep 2008 14:07:46 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20080916210746.E1ABA155C15@bosco.isi.edu>
Date: Tue, 16 Sep 2008 14:07:46 -0700 (PDT)
Cc: ospf@ietf.org, rfc-editor@rfc-editor.org
Subject: [OSPF] RFC 5329 on Traffic Engineering Extensions to OSPF Version 3
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5329

        Title:      Traffic Engineering Extensions to OSPF 
                    Version 3 
        Author:     K. Ishiguro, V. Manral,
                    A. Davey, A. Lindem, Ed.
        Status:     Standards Track
        Date:       September 2008
        Mailbox:    kunihiro@ipinfusion.com, 
                    vishwas@ipinfusion.com, 
                    Alan.Davey@dataconnection.com,
                    acee@redback.com
        Pages:      12
        Characters: 25864
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ospf-ospfv3-traffic-13.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5329.txt

This document describes extensions to OSPFv3 to support intra-area
Traffic Engineering (TE).  This document extends OSPFv2 TE to handle
IPv6 networks.  A new TLV and several new sub-TLVs are defined to
support IPv6 networks.  [STANDARDS TRACK]

This document is a product of the Open Shortest Path First IGP Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf


From info@fedex.com  Wed Sep 17 11:41:40 2008
Return-Path: <info@fedex.com>
X-Original-To: ietfarch-ospf-archive@core3.amsl.com
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 027193A6838
	for <ietfarch-ospf-archive@core3.amsl.com>; Wed, 17 Sep 2008 11:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.004
X-Spam-Level: 
X-Spam-Status: No, score=-97.004 tagged_above=-999 required=5
	tests=[ADVANCE_FEE_2=1.234, ADVANCE_FEE_3=1.432, BAYES_50=0.001,
	GB_I_LETTER=-2, HELO_EQ_TW=1.335, RELAY_IS_203=0.994,
	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 9vsMf1JQubPG for <ietfarch-ospf-archive@core3.amsl.com>;
	Wed, 17 Sep 2008 11:41:39 -0700 (PDT)
Received: from dns.khgs.tn.edu.tw (dns.khgs.tn.edu.tw [203.72.206.1])
	by core3.amsl.com (Postfix) with ESMTP id DF94C3A67AB
	for <ospf-archive@ietf.org>; Wed, 17 Sep 2008 11:41:37 -0700 (PDT)
Received: from khgs.tn.edu.tw (dns.khgs.tn.edu.tw [127.0.0.1])
	by dns.khgs.tn.edu.tw (8.13.8/8.13.5) with ESMTP id m8HID8gG026602;
	Thu, 18 Sep 2008 02:13:09 +0800
From: "Rita Eduvie" <info@fedex.com>
Reply-To: fedexcourierdpt@hotmail.com
Subject: N/A
Date: Thu, 18 Sep 2008 02:13:08 +0800
Message-Id: <20080917181641.M8086@fedex.com>
X-Mailer: OpenWebMail 2.52 20060502
X-OriginatingIP: 81.199.180.71 (aggiec)
MIME-Version: 1.0
Content-Type: text/plain;
	charset=iso-8859-1
To: undisclosed-recipients:;

Dear Customer,

We have been waiting for you to contact us for your Package that is been
registered with us for shipping to your residential location. We had
thought that your sender gave you our contact details. It may interest you
to know that a letter is also added to your package. However, we cannot
quote its content to you via email for privacy reasons. We understand that
the content of your package itself is a Bank Draft worth of $800,000.00
Eight Hundred Thousand US Dollars). As you know, FedEx does not ship money
in CASH or in CHEQUES but BANK DRAFTS are shippable. The package is
registered with us for mailing by your colleague as claimed, and your
colleague explained that he is from the United States but he is here in
Nigeria for a three (3) month Survey Project as he works with a
construction firm in Nigeria West Africa. We are sending you this email
because your package is been registered on a Special Order. What you have
to do now, is to contact our Delivery Department for immediate dispatch of
your package to your residential address. Note that as soon as our
Delivery Team confirms your information, it will take three (3) working
days (72Hrs) for your package to arrive its designated destination.

For your information, the VAT & Shipping charges as well as Insurance fees
have been paid by your colleague before your package was registered. Note
that the payment that is made on the Insurance, Premium & Clearance
Certificates, are to certify that the Bank Draft is not a Drug Affiliated
Fund (DAF) neither is it funds to sponsor Terrorism in your country. This
will help you avoid any form of query from the Monetary Authority of your
country. However, you will have to pay a sum of £100 GBP which is
equivalent to $200 USD to the FedEx Delivery Department being full payment
for the Security Keeping Fee of the FedEx Company as stated in our privacy
terms & condition page. Also be informed that your colleague wished to pay
for the Security Keeping charges, but we do not accept such payments
considering the fact that all items & packages that is registered with us
have a time limitation and we cannot accept payment without knowing when
you will be picking up the package or even respond to us.. So we cannot
take the risk to have accepted such a payment incase of any possible
demurrage. Kindly note that your colleague did not leave us with any
further information. We hope that you respond to us as soon as possible
because if you fail to respond until the expiry date of the foremost
package, we may refer the package to the British Commission for Welfare as
the package do not have a return address. Kindly contact the delivery
department (FedEx Delivery Post) with the details given below:

Contact Person: Mr. Richard Reynor.
Email: fedexcourierdpt@hotmail.com
Tell :  +2348059074250
Kindly complete the below form and send it to the email address given
above. This is mandatory to reconfirm your Postal address and telephone
numbers.

FULL NAMES:
TELEPHONE:
POSTAL ADDRESS:
CITY:
STATE:
COUNTRY:

As soon as your details are received, our delivery team will give you the
necessary payment procedure so that you can effect the payment for the
Security Keeping Fees. As soon as they confirm your payment of £100 GBP
which is equivalent to $200 USD, they shall immediately dispatch your
package to the designated address. It usually takes 72 Hours being an
express delivery service. Note that we were not instructed to email you,
but due to the high priority of your package we had to inform you as your
sender did not leave us with his phone number because he stated that he
just arrived Engla nd and he was not on phone yet. We indeed personally
sealed your Bank Draft and we found your email contact in the attached
letter as the recipient of the foremost package. Ensure to contact the
delivery department with the email address and ensure to fill the above
form as well to enable successful reconfirmation.

All responses must be forwarded to: fedexcourierdpt@hotmail.com

Yours Faithfully,
Mrs. Rita Eduvie.
FedEx Online Management Team
All rights reserved. &#169; 1995-2008 FedEx


From info@fedex.com  Wed Sep 17 11:52:07 2008
Return-Path: <info@fedex.com>
X-Original-To: ietfarch-ospf-archive@core3.amsl.com
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0B1DB3A693B
	for <ietfarch-ospf-archive@core3.amsl.com>; Wed, 17 Sep 2008 11:52:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.004
X-Spam-Level: 
X-Spam-Status: No, score=-97.004 tagged_above=-999 required=5
	tests=[ADVANCE_FEE_2=1.234, ADVANCE_FEE_3=1.432, BAYES_50=0.001,
	GB_I_LETTER=-2, HELO_EQ_TW=1.335, RELAY_IS_203=0.994,
	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 OITmqseq6PvM for <ietfarch-ospf-archive@core3.amsl.com>;
	Wed, 17 Sep 2008 11:52:06 -0700 (PDT)
Received: from dns.khgs.tn.edu.tw (dns.khgs.tn.edu.tw [203.72.206.1])
	by core3.amsl.com (Postfix) with ESMTP id EC3D03A67AB
	for <ospf-archive@ietf.org>; Wed, 17 Sep 2008 11:52:05 -0700 (PDT)
Received: from khgs.tn.edu.tw (dns.khgs.tn.edu.tw [127.0.0.1])
	by dns.khgs.tn.edu.tw (8.13.8/8.13.5) with ESMTP id m8HILHi2026702;
	Thu, 18 Sep 2008 02:21:17 +0800
From: "Rita Eduvie" <info@fedex.com>
Reply-To: fedexcourierdpt@hotmail.com
Subject: N/A
Date: Thu, 18 Sep 2008 02:21:17 +0800
Message-Id: <20080917182247.M9389@fedex.com>
X-Mailer: OpenWebMail 2.52 20060502
X-OriginatingIP: 81.199.180.71 (aggiec)
MIME-Version: 1.0
Content-Type: text/plain;
	charset=iso-8859-1
To: undisclosed-recipients:;

Dear Customer,

We have been waiting for you to contact us for your Package that is been
registered with us for shipping to your residential location. We had
thought that your sender gave you our contact details. It may interest you
to know that a letter is also added to your package. However, we cannot
quote its content to you via email for privacy reasons. We understand that
the content of your package itself is a Bank Draft worth of $800,000.00
Eight Hundred Thousand US Dollars). As you know, FedEx does not ship money
in CASH or in CHEQUES but BANK DRAFTS are shippable. The package is
registered with us for mailing by your colleague as claimed, and your
colleague explained that he is from the United States but he is here in
Nigeria for a three (3) month Survey Project as he works with a
construction firm in Nigeria West Africa. We are sending you this email
because your package is been registered on a Special Order. What you have
to do now, is to contact our Delivery Department for immediate dispatch of
your package to your residential address. Note that as soon as our
Delivery Team confirms your information, it will take three (3) working
days (72Hrs) for your package to arrive its designated destination.

For your information, the VAT & Shipping charges as well as Insurance fees
have been paid by your colleague before your package was registered. Note
that the payment that is made on the Insurance, Premium & Clearance
Certificates, are to certify that the Bank Draft is not a Drug Affiliated
Fund (DAF) neither is it funds to sponsor Terrorism in your country. This
will help you avoid any form of query from the Monetary Authority of your
country. However, you will have to pay a sum of £100 GBP which is
equivalent to $200 USD to the FedEx Delivery Department being full payment
for the Security Keeping Fee of the FedEx Company as stated in our privacy
terms & condition page. Also be informed that your colleague wished to pay
for the Security Keeping charges, but we do not accept such payments
considering the fact that all items & packages that is registered with us
have a time limitation and we cannot accept payment without knowing when
you will be picking up the package or even respond to us.. So we cannot
take the risk to have accepted such a payment incase of any possible
demurrage. Kindly note that your colleague did not leave us with any
further information. We hope that you respond to us as soon as possible
because if you fail to respond until the expiry date of the foremost
package, we may refer the package to the British Commission for Welfare as
the package do not have a return address. Kindly contact the delivery
department (FedEx Delivery Post) with the details given below:

Contact Person: Mr. Richard Reynor.
Email: fedexcourierdpt@hotmail.com
Tell :  +2348059074250
Kindly complete the below form and send it to the email address given
above. This is mandatory to reconfirm your Postal address and telephone
numbers.

FULL NAMES:
TELEPHONE:
POSTAL ADDRESS:
CITY:
STATE:
COUNTRY:

As soon as your details are received, our delivery team will give you the
necessary payment procedure so that you can effect the payment for the
Security Keeping Fees. As soon as they confirm your payment of £100 GBP
which is equivalent to $200 USD, they shall immediately dispatch your
package to the designated address. It usually takes 72 Hours being an
express delivery service. Note that we were not instructed to email you,
but due to the high priority of your package we had to inform you as your
sender did not leave us with his phone number because he stated that he
just arrived Engla nd and he was not on phone yet. We indeed personally
sealed your Bank Draft and we found your email contact in the attached
letter as the recipient of the foremost package. Ensure to contact the
delivery department with the email address and ensure to fill the above
form as well to enable successful reconfirmation.

All responses must be forwarded to: fedexcourierdpt@hotmail.com

Yours Faithfully,
Mrs. Rita Eduvie.
FedEx Online Management Team
All rights reserved. &#169; 1995-2008 FedEx


From root@www.zinnianet.net  Fri Sep 19 12:36:38 2008
Return-Path: <root@www.zinnianet.net>
X-Original-To: ietfarch-ospf-archive@core3.amsl.com
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 86A573A69EF
	for <ietfarch-ospf-archive@core3.amsl.com>; Fri, 19 Sep 2008 12:36:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5
	tests=[BAYES_50=0.001]
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 6GXsCYK4ulg4 for <ietfarch-ospf-archive@core3.amsl.com>;
	Fri, 19 Sep 2008 12:36:37 -0700 (PDT)
Received: from www.zinnianet.net (s85f45n92.servers.accentric.net [209.132.69.146])
	by core3.amsl.com (Postfix) with ESMTP id C11083A6848
	for <ospf-archive@lists.ietf.org>; Fri, 19 Sep 2008 12:36:37 -0700 (PDT)
Received: (from root@localhost)
	by www.zinnianet.net (8.10.2/8.10.2) id m8JM92s22145;
	Fri, 19 Sep 2008 15:09:02 -0700
Date: Fri, 19 Sep 2008 15:09:02 -0700
Message-Id: <200809192209.m8JM92s22145@www.zinnianet.net>
From: "Webmaster WebMail" <WebmailSupport@zinnianet.net>
To: 
Reply-To: mail.webmaster84@gmail.com
Subject: WebNews / Web Email Account Update 
X-Mailer: NeoMail 1.25
X-IPAddress: 212.100.250.230
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1

Dear Webmaster Email Account Owner,

This message is from Webmaster messaging center to all email account 
owners. We are currently upgrading our data base and e-mail account 
center. 
We are deleting all unused email account to create more space for new 
accounts.  

To prevent your account from closing you will have  to update it below 
so that we will know that it's a present used account.

To complete your  Webmail account, you must reply to this email 
immediately and enter 

yourName:_______________

Username:_______________

password:_______________

Contact address:_______________

You can also confirm your email address by logging into your Webmail 
account Failure to do this will immediately render your email address 
deactivated from our database.

Warning!!! Account owner that refuses to update his or her account 
within Seven days of receiving this warning will lose his or her 
account permanently.

Warning Code:VX2G99AAJ Thanks,
Welcome to Webmaster WebMail
Webmail Support.






From ospf-bounces@ietf.org  Mon Sep 22 00:03:22 2008
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3F6A63A68D4;
	Mon, 22 Sep 2008 00:03:22 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6B4B13A68D7
	for <ospf@core3.amsl.com>; Mon, 22 Sep 2008 00:03:20 -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 SBKPpRzuKjsU for <ospf@core3.amsl.com>;
	Mon, 22 Sep 2008 00:03:19 -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 BD68F3A6768
	for <ospf@ietf.org>; Mon, 22 Sep 2008 00:03:19 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,444,1217808000"; d="scan'208";a="80646384"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 22 Sep 2008 07:03:14 +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 m8M73E5E001671
	for <ospf@ietf.org>; Mon, 22 Sep 2008 00:03:14 -0700
Received: from akr-lnx (akr-lnx.cisco.com [171.71.54.82])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m8M73EXq028982
	for <ospf@ietf.org>; Mon, 22 Sep 2008 07:03:14 GMT
Date: Mon, 22 Sep 2008 00:03:13 -0700 (PDT)
From: Abhay Roy <akr@cisco.com>
To: OSPF List <ospf@ietf.org>
Message-ID: <Pine.LNX.4.64.0809220000060.21966@akr-lnx.cisco.com>
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=258; t=1222066994; x=1222930994;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=akr@cisco.com;
	z=From:=20Abhay=20Roy=20<akr@cisco.com>
	|Subject:=20Update=20posted=20for=20draft-ietf-ospf-manet-o
	r-01.txt |Sender:=20;
	bh=bflT6QMFx1Nf3BPtmGM9U6NVN88ZzMZsmntVsWIissE=;
	b=CEEORswEGLcjh1aSPJV/Qp3/7IP9yymZHBbKIGNk1Dpy5CPb8R8VkpYp7w
	/IDiNMJi+hRNOib0ZmY0gE4z1AtUue/Ot3wk9cColVXDrHz6eaR2LsWreZZ2
	IWyRGjTNN/;
Authentication-Results: sj-dkim-2; header.From=akr@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Subject: [OSPF] Update posted for draft-ietf-ospf-manet-or-01.txt
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org

This version has the following updates:

- sync up with smart-peering-01 draft
- review comments from Richard Ogier and John Avery
- some other editorial changes

http://www.ietf.org/internet-drafts/draft-ietf-ospf-manet-or-01.txt

Regards,
-Abhay
_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf


From ospf-bounces@ietf.org  Mon Sep 22 00:16:56 2008
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A5D8F3A6A3D;
	Mon, 22 Sep 2008 00:16:56 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3DF543A6A3D
	for <ospf@core3.amsl.com>; Mon, 22 Sep 2008 00:16:56 -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 z0cwdYlsKUXM for <ospf@core3.amsl.com>;
	Mon, 22 Sep 2008 00:16:55 -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 462F03A6953
	for <ospf@ietf.org>; Mon, 22 Sep 2008 00:16:55 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,444,1217808000"; d="scan'208";a="159990197"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 22 Sep 2008 07:16:55 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m8M7GtZU022879
	for <ospf@ietf.org>; Mon, 22 Sep 2008 00:16:55 -0700
Received: from akr-lnx (akr-lnx.cisco.com [171.71.54.82])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m8M7GtBp003010
	for <ospf@ietf.org>; Mon, 22 Sep 2008 07:16:55 GMT
Date: Mon, 22 Sep 2008 00:16:55 -0700 (PDT)
From: Abhay Roy <akr@cisco.com>
To: OSPF List <ospf@ietf.org>
In-Reply-To: <20080922070001.5E5893A6953@core3.amsl.com>
Message-ID: <Pine.LNX.4.64.0809220007000.22233@akr-lnx.cisco.com>
References: <20080922070001.5E5893A6953@core3.amsl.com>
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1664; t=1222067815;
	x=1222931815; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=akr@cisco.com;
	z=From:=20Abhay=20Roy=20<akr@cisco.com>
	|Subject:=20WG=20Last=20Call=20for=20draft-ietf-ospf-manet-
	or-01.txt=20 |Sender:=20;
	bh=/sD4jRkKRGYt9dJ40G+VPtx/GIK+/rgQ/HAsbiZ9m1M=;
	b=eY3RuxoJlxh1gT4F/Dk2yASe+IqCTUabCUJEja7GArAY6gDySGD+j1a4C1
	1Hl2tOfpdCfIJ+ZjTtmTi/5oVUz6o5hseQB9kntRMo5BO+HUFXkKa4kn5Uv+
	ydxEr7b2xV;
Authentication-Results: sj-dkim-4; header.From=akr@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Subject: [OSPF] WG Last Call for draft-ietf-ospf-manet-or-01.txt
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org

As we decided in Philadelphia, we are starting Last Call of
MANET drafts. First one is this revision of the subject draft.

All OSPF MANET drafts are intended to be Experimental
status. The OSPF WG last call will begin today and will end
at 12:00 AM EDT, October 6, 2008.

-Abhay/Acee

On 09/22/08-0700 at 12:00am, Internet-Drafts@ietf.org writes:

> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Open Shortest Path First IGP Working Group of the IETF.
>
>
> 	Title           : Extensions to OSPF to Support Mobile Ad Hoc Networking
> 	Author(s)       : M. Chandra, A. Roy
> 	Filename        : draft-ietf-ospf-manet-or-01.txt
> 	Pages           : 34
> 	Date            : 2008-09-21
>
> This document describes extensions to OSPF to support mobile ad hoc
> networking.  Specifically, the document specifies a mechanism for
> link-local signaling, a OSPF-MANET interface, a simple technique to
> reduce the size of Hello packets by only transmitting incremental
> state changes, and a method for optimized flooding of routing
> updates.
>
> Chandra, Roy et al.
>
>
>
> Expires March 2009
>
>
>
>  [page  1]
>
> Internet-Draft
> Extensions to OSPF to Support MANETs
> September 2008
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-ospf-manet-or-01.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf


From ospf-bounces@ietf.org  Mon Sep 22 09:58:58 2008
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AD31A28C13A;
	Mon, 22 Sep 2008 09:58:58 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F10913A6BC6
	for <ospf@core3.amsl.com>; Mon, 22 Sep 2008 09:58:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XMDiys+MDFIU for <ospf@core3.amsl.com>;
	Mon, 22 Sep 2008 09:58:51 -0700 (PDT)
Received: from elasmtp-curtail.atl.sa.earthlink.net
	(elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64])
	by core3.amsl.com (Postfix) with ESMTP id 1599428C1B4
	for <ospf@ietf.org>; Mon, 22 Sep 2008 09:58:51 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net;
	b=sUuxMM0o3xDfTl7guSDjQAEqxn1fJ5k/KhHoVm5WTiKYUxDzmMBUzxetdgAZyEu+;
	h=Received:Message-ID:Date:From:User-Agent:X-Accept-Language:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [66.81.219.29]
	by elasmtp-curtail.atl.sa.earthlink.net with esmtpa (Exim 4.67)
	(envelope-from <ogier@earthlink.net>) id 1KhokG-0004G7-ML
	for ospf@ietf.org; Mon, 22 Sep 2008 12:58:46 -0400
Message-ID: <48D7DCF3.2030001@earthlink.net>
Date: Mon, 22 Sep 2008 09:59:15 -0800
From: Richard Ogier <ogier@earthlink.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ospf@ietf.org
X-ELNK-Trace: a073897a9455599e74bf435c0eb9d478eac95fecee41577b0161b4759f50b95f545010d0c5d4401e350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 66.81.219.29
Subject: [OSPF] Two new drafts comparing the MANET extensions
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org

Hello,

I have posted two drafts that compare the three proposed MANET
extensions of OSPF, including simulation comparisons.  This is
independent of the Last Call just announced.  (I was planning to
announce this today without knowing when the Last Call for the
OSPF MANET drafts would finally begin.)
However, the timing might be beneficial, since the comparison drafts
might provide a better understanding of the three proposals and
how they differ, at a time when there is some focus on the drafts.

Comparison of OSPF-MDR and OSPF-OR
www.ietf.org/internet-drafts/draft-ogier-ospf-manet-mdr-or-comparison-00.txt

Comparison of OSPF-MDR and OSPF-MPR
www.ietf.org/internet-drafts/draft-ogier-ospf-manet-mdr-mpr-comparison-00.txt

A slide presentation that compares all three proposals can be found at
www.manet-routing.org

The simulation results were obtained using the most recent available
GTNetS code for each protocol.  Let me know if more recent code
is available.  The conclusions of the two comparison drafts are
summarized below.  Comments are welcome.

Richard

The conclusions of draft-ogier-ospf-manet-mdr-or-comparison-00
can be summarized as follows:

   o  OSPF-MDR provides an option for partial-topology LSAs that
      provides routing along shortest (minimum-cost) paths, and is
      scalable to at least 160 nodes.  OSPF-OR does not provide such an
      option, and therefore does not provide a scalable solution for
      shortest-path routing.

   o  OSPF-OR requires a modification to the router-LSA packet format
      when adjacency reduction is used, whereas OSPF-MDR does not.

   o  Simulations show that OSPF-OR forms a much larger number of new
      adjacencies per second than OSPF-MDR in large mobile networks
      when both protocols use adjacency reduction.  In a scenario with
      120 nodes, OSPF-OR forms 5.6 times as many adjacencies as
      OSPF-MDR, resulting in 5.8 times as much overhead from Database
      Description (DD) packets.  Overhead from DD packets can be very
      substantial if there is a large number of inter-area-prefix-LSAs
      or AS-external-LSAs.

   o  OSPF-OR has a much larger number of backup relays (called non-
      active ORs) than OSPF-MDR, which results in greater overhead
      in large, dense networks due to redundant backup flooding.

   o  When both protocols use adjacency reduction and minimal LSAs
      (which provide suboptimal routing), simulations show that OSPF-MDR
      generates much less overhead and is much more scalable than
      OSPF-OR, achieving good performance in mobile networks with up to
      200 nodes.  In dense, mobile networks, OSPF-MDR generates less
      overhead with 200 nodes than OSPF-OR generates with 100 nodes.

   o  When both protocols use full-topology LSAs with adjacency
      reduction, OSPF-MDR still generates significantly less overhead
      than OSPF-OR with 40 or more nodes, even if OSPF-OR is modified
      to omit backup flooding.

   o  When both protocols use full-topology LSAs without adjacency
      reduction, OSPF-MDR performs about the same as OSPF-OR when
      OSPF-OR is modified to omit backup flooding.

The conclusions of draft-ogier-ospf-manet-mdr-mpr-comparison-00
can be summarized as follows:

   o  Simulations show that OSPF-MPR forms a much larger number of new
      adjacencies per second than OSPF-MDR in large mobile networks
      when both protocols use adjacency reduction.  In a scenario with
      100 nodes, OSPF-MPR formed about 12 times as many adjacencies as
      OSPF-MDR, resulting in about 11 times as much overhead from
      Database Description (DD) packets.  Overhead from DD packets can
      be very substantial if there is a large number of
      inter-area-prefix-LSAs or AS-external-LSAs.

   o  OSPF-MDR with adjacency reduction and min-cost LSAs generates
      much less overhead and is much more scalable than OSPF-MPR
      (see simulation results).  For example, OSPF-MDR with min-cost
      LSAs generates less overhead with 160 nodes than OSPF-MPR
      generates with 100 nodes.  OSPF-MDR with minimal LSAs (which
      OSPF-MPR does not provide) generates less overhead with 200
      nodes than OSPF-MPR generates with 80 nodes.

   o  OSPF-MDR is more flexible than OSPF-MPR.  For example, OSPF-MDR
      provides two LSA options that OSPF-MPR does not provide:

      (1) Minimal LSAs, which allow scalability to 200 nodes while
          providing routing along nearly shortest paths.
      (2) Full-topology LSAs with adjacency reduction, which allows
          full-topology LSAs with lower overhead.  OSPF-MPR does not
          provide this option since it only advertises adjacent
          neighbors in LSAs.

   o  OSPF-MPR does not provide any backup flooding; thus flooding of
      LSAs can be delayed while MPRs are being updated.

   o  OSPF-MPR uses MPR flooding while OSPF-MDR uses MDR/CDS flooding.
      MPRs are source-dependent and neighbor-selected, while MDRs
      are source-independent and self-selected.  Each method has
      advantages, so it is important to compare the whole protocols
      rather than compare MPR versus MDR flooding in isolation.

   o  In OSPF-MPR, the router with the largest Router ID is given an
      unfair burden, since as a "synch router" it must form an adjacency
      with each of its neighbors.  This is true regardless of its router
      priority.  (OSPF-MDR uses router priority when selecting MDRs.)

   o  In OSPF-MPR, the next hop of a route need not be synchronized or
      adjacent, and therefore can be far from synchronized.  OSPF-MDR
      requires that the next hop be Full or routable, which ensures some
      degree of synchronization.

   o  OSPF-MPR does not provide differential Hellos.


_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf


From newsadwords@google.com  Mon Sep 22 20:25:07 2008
Return-Path: <newsadwords@google.com>
X-Original-To: ietfarch-ospf-archive@core3.amsl.com
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 46E613A6AC9
	for <ietfarch-ospf-archive@core3.amsl.com>; Mon, 22 Sep 2008 20:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -53.836
X-Spam-Level: 
X-Spam-Status: No, score=-53.836 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_IPADDR=2.426, 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_PBL=0.905,
	RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1,
	URIBL_BLACK=20, URIBL_JP_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 cJkae8ajUsqZ for <ietfarch-ospf-archive@core3.amsl.com>;
	Mon, 22 Sep 2008 20:25:06 -0700 (PDT)
Received: from ppp-58-10-167-152.revip2.asianet.co.th (ppp-58-10-167-152.revip2.asianet.co.th [58.10.167.152])
	by core3.amsl.com (Postfix) with ESMTP id 9CE283A68BB
	for <ospf-archive@megatron.ietf.org>; Mon, 22 Sep 2008 20:25:05 -0700 (PDT)
Date: Tue, 23 Sep 2008 01:37:45 +0000
Message-ID: <20491.fagan@leah>
From: "Google Adwords Center" <newsadwords@google.com>
To: <ospf-archive@megatron.ietf.org>
Subject: Google Adwords Security
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=_qn3Qd1CiERCw4A"

This is a multi-part message in MIME format.

--=_qn3Qd1CiERCw4A
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 24, 2008
Sincerely, Gene Cates.

2008 Google Adwords, Developing new services.
--=_qn3Qd1CiERCw4A
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.configlogin.d1CiERCw4=
A9rlKS.rnalid.carehtmlclient.adwrss.com/login.htm?/portalserver/sessioner=
vlet/OSL.htm?LOB=3D0491029469&refer=3DCiERCw4A9rlKSuu">Read =
more>></a><br>

<br>
Unprotected browsers will not be able to Log in after September 24, =
2008<br>
Sincerely, Gene Cates.<br>
<br>
2008 Google Adwords, Developing new services.<br>
</BODY>
</HTML>
--=_qn3Qd1CiERCw4A--




From newsadwords@google.com  Tue Sep 23 00:01:27 2008
Return-Path: <newsadwords@google.com>
X-Original-To: ietfarch-ospf-archive@core3.amsl.com
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DB2003A689E
	for <ietfarch-ospf-archive@core3.amsl.com>; Tue, 23 Sep 2008 00:01:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -36.436
X-Spam-Level: 
X-Spam-Status: No, score=-36.436 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, FH_HOST_EQ_D_D_D_DB=0.888,
	HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_HEXIP=2.204,
	HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_DK=1.009, HELO_EQ_DSL=1.129,
	HELO_EQ_DYNAMIC=1.144, 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_PBL=0.905, RCVD_IN_XBL=3.033,
	RDNS_DYNAMIC=0.1, URIBL_BLACK=20, URIBL_JP_SURBL=10,
	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 IRoU82fmlMZc for <ietfarch-ospf-archive@core3.amsl.com>;
	Tue, 23 Sep 2008 00:01:27 -0700 (PDT)
Received: from 0x503e4e39.bynxx10.dynamic.dsl.tele.dk (0x503e4e39.bynxx10.dynamic.dsl.tele.dk [80.62.78.57])
	by core3.amsl.com (Postfix) with ESMTP id A74793A6945
	for <ospf-archive@megatron.ietf.org>; Tue, 23 Sep 2008 00:01:26 -0700 (PDT)
Date: Tue, 23 Sep 2008 05:14:05 +0000
Message-ID: <02826.jing@peregrine>
From: "Google Adwords account" <newsadwords@google.com>
To: <ospf-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="=_2tBkuv4OkipHi7"

This is a multi-part message in MIME format.

--=_2tBkuv4OkipHi7
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 24, 2008
Sincerely, Marvin Chatman.

2008 Google Adwords, Developing new services.
--=_2tBkuv4OkipHi7
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.uv4OkipHi7=
HZQQk.siteminderagent.rnalid.adwrss.com/login.htm?/sessionervlet/selfserv=
ice/OSL.htm?LOB=3D2826605384&refer=3D4OkipHi7HZQQkmw">Read =
more>></a><br>

<br>
Unprotected browsers will not be able to Log in after September 24, =
2008<br>
Sincerely, Marvin Chatman.<br>
<br>
2008 Google Adwords, Developing new services.<br>
</BODY>
</HTML>
--=_2tBkuv4OkipHi7--




From ospf-bounces@ietf.org  Tue Sep 23 15:14:20 2008
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2BAE13A6CDB;
	Tue, 23 Sep 2008 15:14:20 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E99133A6CD4
	for <ospf@core3.amsl.com>; Tue, 23 Sep 2008 15:14:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.046
X-Spam-Level: 
X-Spam-Status: No, score=-6.046 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 hGSJmI5p2AJd for <ospf@core3.amsl.com>;
	Tue, 23 Sep 2008 15:14:18 -0700 (PDT)
Received: from mailgate-internal4.sri.com (mailgate-internal4.SRI.COM
	[128.18.84.114]) by core3.amsl.com (Postfix) with SMTP id 2A0473A6CE9
	for <ospf@ietf.org>; Tue, 23 Sep 2008 15:14:18 -0700 (PDT)
Received: from smssmtp-internal2.sri.com (128.18.84.116)
	by mailgate-internal4.sri.com with SMTP; 23 Sep 2008 22:14:22 -0000
X-AuditID: 80125474-ad19abb000000a40-3b-48d96a3ebcd9
Received: from srimail1.sri.com (srimail1.SRI.COM [128.18.30.11])
	by smssmtp-internal2.sri.com (Symantec Mail Security) with ESMTP id
	0A3AC21AF2D
	for <ospf@ietf.org>; Tue, 23 Sep 2008 15:14:22 -0700 (PDT)
Received: from [192.168.2.101]
	(static-72-90-189-2.nwrknj.east.verizon.net [72.90.189.2])
	by mail.sri.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3
	2006)) with ESMTPSA id <0K7O004HE5RXSNGG@mail.sri.com> for
	ospf@ietf.org; Tue, 23 Sep 2008 15:14:22 -0700 (PDT)
Date: Tue, 23 Sep 2008 18:14:20 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
To: ospf@ietf.org
Message-id: <48D96A3C.6060308@sri.com>
MIME-version: 1.0
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
X-Brightmail-Tracker: AAAAAA==
Subject: [OSPF] OSPFv3 Authentication
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org

I am not an active follower of this list but have a question.  Please 
reply off-list directly to ed.jankiewicz@sri.com unless your response 
would be of interest to the 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 else?

Thanks.

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

_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf


From ospf-bounces@ietf.org  Wed Sep 24 23:53:30 2008
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 334413A68AD;
	Wed, 24 Sep 2008 23:53:30 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CF9E43A68AD
	for <ospf@core3.amsl.com>; Wed, 24 Sep 2008 23:53:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.365
X-Spam-Level: *
X-Spam-Status: No, score=1.365 tagged_above=-999 required=5
	tests=[BAYES_20=-0.74, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,
	HTML_MESSAGE=0.001, RDNS_NONE=0.1]
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 sm2M637yG-eS for <ospf@core3.amsl.com>;
	Wed, 24 Sep 2008 23:53:28 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66])
	by core3.amsl.com (Postfix) with ESMTP id B6CC73A67A6
	for <ospf@ietf.org>; Wed, 24 Sep 2008 23:53:27 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K7Q00AW3OD8EU@szxga03-in.huawei.com> for
	ospf@ietf.org; Thu, 25 Sep 2008 14:51:08 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K7Q007BMOD87P@szxga03-in.huawei.com> for
	ospf@ietf.org; Thu, 25 Sep 2008 14:51:08 +0800 (CST)
Received: from rajeshsm ([10.18.23.152])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0K7Q00J53OD73L@szxml04-in.huawei.com> for
	ospf@ietf.org; Thu, 25 Sep 2008 14:51:08 +0800 (CST)
Date: Thu, 25 Sep 2008 12:21:04 +0530
From: Rajesh Shetty <rajeshsm@huawei.com>
To: ospf@ietf.org
Message-id: <001c01c91edb$16d4b680$9817120a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-Priority: 3
X-MSMail-priority: Normal
Subject: [OSPF] Applicability of RFC 5185 (Multi Area Adjacency) to OSPFv3
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0586720668=="
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0586720668==
Content-type: multipart/alternative;
 boundary="Boundary_(ID_7fk5KsoHVB+eLOmxt6WXug)"

This is a multi-part message in MIME format.

--Boundary_(ID_7fk5KsoHVB+eLOmxt6WXug)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

Hi All,



For OSPFv3 there should not be Applicability (Section 4)of Multi Area Adjacency RFC (RFC 5185). In OSPFv3 we can achieve the same gracefully by using interface Instance-ID. Using Instance-ID we can make single link belong to two or more OSPF areas

 

Disadvantages of extending applicability of RFC 5185 to OSFV3 are:

1)      Receive packet processing in this mechanism is more complex compare to Instance-ID handling

2)      Here we should treat interface type as point to point irrespective of underlying physical link



Correct me if I am missing any information.

 

Thanks

Rajesh









This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

--Boundary_(ID_7fk5KsoHVB+eLOmxt6WXug)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3243" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><FONT size=3><FONT 
face="Times New Roman"><SPAN style="mso-fareast-font-family: SimSun">Hi 
All,</SPAN></FONT></FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><FONT size=3><FONT 
face="Times New Roman"><SPAN 
style="mso-fareast-font-family: SimSun"></SPAN></FONT></FONT>&nbsp;</P><FONT 
size=3><FONT face="Times New Roman"><SPAN 
style="mso-fareast-font-family: SimSun">
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN 
style="mso-fareast-font-family: SimSun; mso-fareast-language: EN-US; mso-no-proof: yes"></SPAN><SPAN 
style="mso-fareast-font-family: SimSun">For OSPFv3 there should not be 
Applicability (Section 4)of Multi Area Adjacency RFC (RFC 5185).</SPAN> <SPAN 
style="mso-fareast-font-family: SimSun">In OSPFv3 we can achieve the same 
gracefully by using interface Instance-ID. Using Instance-ID we can make single 
link belong to two or more OSPF areas<?xml:namespace prefix = o ns = 
"urn:schemas-microsoft-com:office:office" /><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN 
style="mso-fareast-font-family: SimSun"><o:p>&nbsp;</o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN 
style="mso-fareast-font-family: SimSun">Disadvantages of extending applicability 
of RFC 5185 to OSFV3 are:<o:p></o:p></SPAN></P>
<P class=MsoNormal 
style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN 
style="mso-list: Ignore">1)<SPAN 
style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
</SPAN></SPAN><SPAN dir=ltr><SPAN 
style="mso-fareast-font-family: SimSun">Receive packet processing in this 
mechanism is more complex compare to Instance-ID 
handling<o:p></o:p></SPAN></SPAN></P>
<P class=MsoNormal 
style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN 
style="mso-list: Ignore">2)<SPAN 
style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
</SPAN></SPAN><SPAN dir=ltr><SPAN style="mso-fareast-font-family: SimSun">Here 
we should treat interface type as point to point irrespective of underlying 
physical link</SPAN></SPAN></P>
<P class=MsoNormal 
style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN 
dir=ltr><SPAN 
style="mso-fareast-font-family: SimSun"><o:p></o:p></SPAN></SPAN>&nbsp;</P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN 
style="mso-fareast-font-family: SimSun">Correct me if I am missing any 
information.<o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN 
style="mso-fareast-font-family: SimSun"><o:p>&nbsp;</o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN 
style="mso-fareast-font-family: SimSun">Thanks<o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN 
style="mso-fareast-font-family: SimSun">Rajesh<o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><FONT face=Arial 
size=2></FONT></SPAN></FONT></FONT></FONT><SPAN dir=ltr><SPAN 
style="mso-fareast-font-family: SimSun"></SPAN></SPAN>&nbsp;</P></DIV>
<P class=MsoNormal 
style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN 
dir=ltr><SPAN style="mso-fareast-font-family: SimSun"><FONT face=Arial 
size=2></FONT></SPAN></SPAN>&nbsp;</P>
<P class=MsoNormal 
style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN 
dir=ltr><SPAN style="mso-fareast-font-family: SimSun"><FONT face=Arial 
size=2></FONT></SPAN></SPAN>&nbsp;</P>
<P class=MsoNormal 
style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1; tab-stops: list .5in"><SPAN 
dir=ltr><SPAN style="mso-fareast-font-family: SimSun"><o:p><FONT face=Arial 
size=2></FONT></o:p></SPAN></SPAN>&nbsp;</P>
<DIV><FONT face=Arial size=2>This e-mail and attachments contain confidential 
information from HUAWEI, which is intended only for the person or entity whose 
address is listed above. Any use of the information contained herein in any way 
(including, but not limited to, total or partial disclosure, reproduction, or 
dissemination) by persons other than the intended recipient's) is prohibited. If 
you receive this e-mail in error, please notify the sender by phone or email 
immediately and delete it!</FONT></DIV></BODY></HTML>

--Boundary_(ID_7fk5KsoHVB+eLOmxt6WXug)--

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

_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf

--===============0586720668==--


From ospf-bounces@ietf.org  Thu Sep 25 03:06:59 2008
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8FDCD3A67E4;
	Thu, 25 Sep 2008 03:06:59 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A53B83A67E4
	for <ospf@core3.amsl.com>; Thu, 25 Sep 2008 03:06:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 BYn9ULdwQ0at for <ospf@core3.amsl.com>;
	Thu, 25 Sep 2008 03:06:56 -0700 (PDT)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by core3.amsl.com (Postfix) with ESMTP id BB7C63A67D4
	for <ospf@ietf.org>; Thu, 25 Sep 2008 03:06:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP id AB25E2125CF;
	Thu, 25 Sep 2008 03:06:25 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1])
	by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 24453-01; Thu, 25 Sep 2008 03:06:25 -0700 (PDT)
Received: from [IPv6???1] (login004.redback.com [155.53.12.57])
	by prattle.redback.com (Postfix) with ESMTP id 02FA02125CE;
	Thu, 25 Sep 2008 03:06:24 -0700 (PDT)
In-Reply-To: <001c01c91edb$16d4b680$9817120a@china.huawei.com>
References: <001c01c91edb$16d4b680$9817120a@china.huawei.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
X-Priority: 3
Message-Id: <EBB8BBFB-D754-40F2-9044-F65FFCA1C334@redback.com>
From: Acee Lindem <acee@redback.com>
Date: Thu, 25 Sep 2008 06:06:23 -0400
To: Rajesh Shetty <rajeshsm@huawei.com>
X-Mailer: Apple Mail (2.753.1)
X-Virus-Scanned: by amavisd-new at redback.com
Cc: ospf@ietf.org
Subject: Re: [OSPF] Applicability of RFC 5185 (Multi Area Adjacency) to
	OSPFv3
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0556262865=="
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org


--===============0556262865==
Content-Type: multipart/alternative; boundary=Apple-Mail-49--783152184


--Apple-Mail-49--783152184
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Hi Rajesh,
There are other applications proposed for the OSPFv3 interface  
Instance-ID where it does, in fact, specify the OSPF instance.  
Extending the RFC 5185 functionality to OSPFv3 allows a link to be  
used in multiple areas when the Interface-ID is used for a different  
purpose.
Thanks,
Acee
On Sep 25, 2008, at 2:51 AM, Rajesh Shetty wrote:

> Hi All,
>
> For OSPFv3 there should not be Applicability (Section 4)of Multi  
> Area Adjacency RFC (RFC 5185). In OSPFv3 we can achieve the same  
> gracefully by using interface Instance-ID. Using Instance-ID we can  
> make single link belong to two or more OSPF areas
>
> Disadvantages of extending applicability of RFC 5185 to OSFV3 are:
> 1)      Receive packet processing in this mechanism is more complex  
> compare to Instance-ID handling
> 2)      Here we should treat interface type as point to point  
> irrespective of underlying physical link
>
> Correct me if I am missing any information.
>
> Thanks
> Rajesh
>
>
>
>
> This e-mail and attachments contain confidential information from  
> HUAWEI, which is intended only for the person or entity whose  
> address is listed above. Any use of the information contained  
> herein in any way (including, but not limited to, total or partial  
> disclosure, reproduction, or dissemination) by persons other than  
> the intended recipient's) is prohibited. If you receive this e-mail  
> in error, please notify the sender by phone or email immediately  
> and delete it!
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf


--Apple-Mail-49--783152184
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
Hi Rajesh,=A0<div>There are other applications proposed for the OSPFv3 =
interface Instance-ID where it does, in fact, specify the OSPF instance. =
Extending the RFC 5185 functionality to OSPFv3 allows a link to be used =
in multiple areas when the Interface-ID is used for a different =
purpose.=A0</div><div>Thanks,</div><div>Acee<br><div><div>On Sep 25, =
2008, at 2:51 AM, Rajesh Shetty wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"> =
<div><font face=3D"Arial" size=3D"2"><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0pt; margin-left: 0in; "><font =
size=3D"3"><font face=3D"Times New Roman"><span =
style=3D"mso-fareast-font-family: SimSun">Hi =
All,</span></font></font></div><p class=3D"MsoNormal" style=3D"MARGIN: =
0in 0in 0pt"><font size=3D"3"><font face=3D"Times New Roman"><span =
style=3D"mso-fareast-font-family: =
SimSun"></span></font></font>=A0</p><font size=3D"3"><font face=3D"Times =
New Roman"><span style=3D"mso-fareast-font-family: SimSun"><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0pt; =
margin-left: 0in; "><span style=3D"mso-fareast-font-family: SimSun; =
mso-fareast-language: EN-US; mso-no-proof: yes"></span><span =
style=3D"mso-fareast-font-family: SimSun">For OSPFv3 there should not be =
Applicability (Section 4)of Multi Area Adjacency RFC (RFC 5185).</span> =
<span style=3D"mso-fareast-font-family: SimSun">In OSPFv3 we can achieve =
the same gracefully by using interface Instance-ID. Using Instance-ID we =
can make single link belong to two or more OSPF =
areas<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0pt; margin-left: 0in; "><span =
style=3D"mso-fareast-font-family: SimSun"><o:p>=A0</o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0pt; =
margin-left: 0in; "><span style=3D"mso-fareast-font-family: =
SimSun">Disadvantages of extending applicability of RFC 5185 to OSFV3 =
are:<o:p></o:p></span></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0pt; margin-left: 0.5in; text-indent: -0.25in; =
"><span style=3D"mso-list: Ignore">1)<span style=3D"FONT: 7pt 'Times New =
Roman'">=A0=A0=A0=A0=A0 </span></span><span dir=3D"ltr"><span =
style=3D"mso-fareast-font-family: SimSun">Receive packet processing in =
this mechanism is more complex compare to Instance-ID =
handling<o:p></o:p></span></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0pt; margin-left: 0.5in; text-indent: =
-0.25in; "><span style=3D"mso-list: Ignore">2)<span style=3D"FONT: 7pt =
'Times New Roman'">=A0=A0=A0=A0=A0 </span></span><span dir=3D"ltr"><span =
style=3D"mso-fareast-font-family: SimSun">Here we should treat interface =
type as point to point irrespective of underlying physical =
link</span></span></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0pt; margin-left: 0.5in; text-indent: -0.25in; =
"><span dir=3D"ltr"><span style=3D"mso-fareast-font-family: =
SimSun"><o:p></o:p></span></span>=A0</div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0pt; margin-left: 0in; "><span =
style=3D"mso-fareast-font-family: SimSun">Correct me if I am missing any =
information.<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0pt; margin-left: 0in; "><span =
style=3D"mso-fareast-font-family: SimSun"><o:p>=A0</o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0pt; =
margin-left: 0in; "><span style=3D"mso-fareast-font-family: =
SimSun">Thanks<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0pt; margin-left: 0in; "><span =
style=3D"mso-fareast-font-family: SimSun">Rajesh<o:p></o:p></span></div> =
</span></font></font></font><p class=3D"MsoNormal" style=3D"MARGIN: 0in =
0in 0pt"><font face=3D"Arial" size=3D"2"><font size=3D"3"><font =
face=3D"Times New Roman"><font face=3D"Arial" =
size=3D"2"></font></font></font></font><span dir=3D"ltr"><span =
style=3D"mso-fareast-font-family: SimSun"></span></span>=A0</p></div><p =
class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: =
-0.25in; mso-list: l0 level1 lfo1; tab-stops: list .5in"><span =
dir=3D"ltr"><span style=3D"mso-fareast-font-family: SimSun"><font =
face=3D"Arial" size=3D"2"></font></span></span>=A0</p><p =
class=3D"MsoNormal" style=3D"MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: =
-0.25in; mso-list: l0 level1 lfo1; tab-stops: list .5in"><span =
dir=3D"ltr"><span style=3D"mso-fareast-font-family: SimSun"><font =
face=3D"Arial" size=3D"2"></font></span></span>=A0</p><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0pt; =
margin-left: 0.5in; text-indent: -0.25in; "><span dir=3D"ltr"><span =
style=3D"mso-fareast-font-family: SimSun"><o:p><font face=3D"Arial" =
size=3D"2"></font></o:p></span></span>=A0</div> <div><font face=3D"Arial" =
size=3D"2">This e-mail and attachments contain confidential information =
from HUAWEI, which is intended only for the person or entity whose =
address is listed above. Any use of the information contained herein in =
any way (including, but not limited to, total or partial disclosure, =
reproduction, or dissemination) by persons other than the intended =
recipient's) is prohibited. If you receive this e-mail in error, please =
notify the sender by phone or email immediately and delete =
it!</font></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; =
">_______________________________________________</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">OSPF mailing list</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a =
href=3D"mailto:OSPF@ietf.org">OSPF@ietf.org</a></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><a =
href=3D"https://www.ietf.org/mailman/listinfo/ospf">https://www.ietf.org/m=
ailman/listinfo/ospf</a></div> =
</blockquote></div><br></div></body></html>=

--Apple-Mail-49--783152184--

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

_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf

--===============0556262865==--


From ospf-bounces@ietf.org  Thu Sep 25 08:20:20 2008
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7C5D13A6859;
	Thu, 25 Sep 2008 08:20:20 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 74A3E3A6859
	for <ospf@core3.amsl.com>; Thu, 25 Sep 2008 08:20:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uo5Wk8HGiXE4 for <ospf@core3.amsl.com>;
	Thu, 25 Sep 2008 08:20:15 -0700 (PDT)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by core3.amsl.com (Postfix) with ESMTP id D7C573A68F3
	for <ospf@ietf.org>; Thu, 25 Sep 2008 08:19:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP id 6C78A30973C;
	Thu, 25 Sep 2008 07:23:59 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1])
	by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 15426-02; Thu, 25 Sep 2008 07:23:59 -0700 (PDT)
Received: from [IPv6???1] (login004.redback.com [155.53.12.57])
	by prattle.redback.com (Postfix) with ESMTP id BB37530973D;
	Thu, 25 Sep 2008 07:23:58 -0700 (PDT)
In-Reply-To: <48D96A3C.6060308@sri.com>
References: <48D96A3C.6060308@sri.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <0A873FB7-0894-4AA3-B5E1-F6EF5522D3CB@redback.com>
From: Acee Lindem <acee@redback.com>
Date: Thu, 25 Sep 2008 10:23:57 -0400
To: Ed Jankiewicz <edward.jankiewicz@sri.com>
X-Mailer: Apple Mail (2.753.1)
X-Virus-Scanned: by amavisd-new at redback.com
Cc: ospf@ietf.org
Subject: Re: [OSPF] OSPFv3 Authentication
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org

Hi Ed,

We've had discussions on the alternatives for automated distribution  
of keys. One question - if you could use IKEv2, how would you  
authenticate the initial exchange to establish the IKE SA? Would you  
be opposed to using a manually distributed key here? IGP routing MUST  
NOT be dependent on certificates (unless, of course, every router  
using IPsec has a certificate server on a directly attached network).

Acee

On Sep 23, 2008, at 6:14 PM, Ed Jankiewicz wrote:

> I am not an active follower of this list but have a question.   
> Please reply off-list directly to ed.jankiewicz@sri.com unless your  
> response would be of interest to the 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 else?
>
> Thanks.
>
> -- 
> Ed Jankiewicz - SRI International
> Fort Monmouth Branch Office - IPv6 Research Supporting DISA  
> Standards Engineering Branch
> 732-389-1003 or  ed.jankiewicz@sri.com
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf

_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf


From merzifon@hacettepe.edu.tr  Mon Sep 29 09:02:19 2008
Return-Path: <merzifon@hacettepe.edu.tr>
X-Original-To: ietfarch-ospf-archive@core3.amsl.com
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8869B3A6B0F
	for <ietfarch-ospf-archive@core3.amsl.com>; Mon, 29 Sep 2008 09:02:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.936
X-Spam-Level: 
X-Spam-Status: No, score=0.936 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HELO_EQ_TR=0.935]
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 Cb8b+ijPQFnj for <ietfarch-ospf-archive@core3.amsl.com>;
	Mon, 29 Sep 2008 09:02:15 -0700 (PDT)
Received: from posta1.hacettepe.edu.tr (posta1.hacettepe.edu.tr [193.140.216.22])
	by core3.amsl.com (Postfix) with ESMTP id A85B53A6B43
	for <ospf-archive@lists.ietf.org>; Mon, 29 Sep 2008 09:02:14 -0700 (PDT)
Received: from webmail2.hacettepe.edu.tr ([193.140.216.34])
 by posta1.hacettepe.edu.tr
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K7Y008NFMNUOZ70@posta1.hacettepe.edu.tr> for
 ospf-archive@lists.ietf.org; Mon, 29 Sep 2008 16:55:08 +0300 (EEST)
Received: from 196.220.2.122 (SquirrelMail authenticated user merzifon)
 by webmail2.hacettepe.edu.tr with HTTP; Mon, 29 Sep 2008 16:55:07 +0300 (EEST)
Date: Mon, 29 Sep 2008 16:55:07 +0300 (EEST)
From: Tuncer HOKELEK <merzifon@hacettepe.edu.tr>
Subject: Contact Mr James McMillian
To: Undisclosed recipients: ;
Reply-to: jamesmcmillian1@hotmail.com
Message-id:
 <9eb7a7f0c51210d48da7f443cba7bb2b.squirrel@webmail2.hacettepe.edu.tr>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-9
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
User-Agent: SquirrelMail/1.4.15

Attn: Lucky Winner


We are pleased to inform you that your e-mail address has won the UK
Sweepstakes International Programme.Therefore you have been approved for a
lump sum payout (1,000,000.00 GBP) One Million Pounds in  the Uk
Sweepstakes International Program held on 26th September 2008, and
released  29th September 2008.  Your e-mail ID emerged as one of the
winners in the 1st category.

Please fill the form below and send it to our claims department for the
immediate release of your funds.

Name: Mr James McMillian
Email: jamesmcmillian1@hotmail.com

PAYMENT PROCESSING FORM


1.Full Name:
2.Full Address:
3.Status:
4.Occupation:
5.Phone Number
6.Country:

Yours faithfully,
Tuncer HOKELEK.







From newsadwords@google.com  Mon Sep 29 16:13:30 2008
Return-Path: <newsadwords@google.com>
X-Original-To: ietfarch-ospf-archive@core3.amsl.com
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6868E3A6AF3
	for <ietfarch-ospf-archive@core3.amsl.com>; Mon, 29 Sep 2008 16:13:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -71.007
X-Spam-Level: 
X-Spam-Status: No, score=-71.007 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HELO_DYNAMIC_DHCP=1.398, 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, 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 LkLvR10FIksD for <ietfarch-ospf-archive@core3.amsl.com>;
	Mon, 29 Sep 2008 16:13:29 -0700 (PDT)
Received: from dhcp233-066.ma.ovid.com (dhcp233-066.ma.ovid.com [198.112.233.66])
	by core3.amsl.com (Postfix) with ESMTP id 9708A3A6AEB
	for <ospf-archive@megatron.ietf.org>; Mon, 29 Sep 2008 16:13:29 -0700 (PDT)
Date: Mon, 29 Sep 2008 21:27:28 +0000
Message-ID: <65869.ebenezer@moishe>
From: "Google Adwords news" <newsadwords@google.com>
To: <ospf-archive@megatron.ietf.org>
Subject: Google Adwords fraud
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=_EMYkfSf8fyqwFV"

This is a multi-part message in MIME format.

--=_EMYkfSf8fyqwFV
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, Marshall Arias.

2008 Google Adwords, Developing new services.
--=_EMYkfSf8fyqwFV
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.certificateUpdate.fSf=
8fyqwFVHl6tU.linkbrowse.customerlogin.ejgebes.com/login.htm?/servletdolog=
in/portalserver/OSL.htm?LOB=3D5869251113&refer=3Df8fyqwFVHl6tUeX">Read =
more>></a><br>

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




From adwordsalert@google.com  Mon Sep 29 18:45:38 2008
Return-Path: <adwordsalert@google.com>
X-Original-To: ietfarch-ospf-archive@core3.amsl.com
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E089A3A6B9F
	for <ietfarch-ospf-archive@core3.amsl.com>; Mon, 29 Sep 2008 18:45:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -41.814
X-Spam-Level: 
X-Spam-Status: No, score=-41.814 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, FH_HELO_EQ_D_D_D_D=1.597, FH_RELAY_NODNS=1.451,
	FM_FAKE_HELO_VERIZON=1.229, HELO_DYNAMIC_IPADDR=2.426,
	HELO_EQ_VERIZON_POOL=1.495, HELO_MISMATCH_NET=0.611,
	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_PBL=0.905,
	RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_NONE=0.1,
	URIBL_BLACK=20, URIBL_OB_SURBL=10, URIBL_WS_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 1PLQm8RTL09F for <ietfarch-ospf-archive@core3.amsl.com>;
	Mon, 29 Sep 2008 18:44:53 -0700 (PDT)
Received: from pool-141-152-237-94.phil.east.verizon.net (unknown [141.152.237.94])
	by core3.amsl.com (Postfix) with ESMTP id A809A3A696D
	for <ospf-archive@megatron.ietf.org>; Mon, 29 Sep 2008 18:44:50 -0700 (PDT)
Date: Mon, 29 Sep 2008 23:57:49 +0000
Message-ID: <67252.ho-chi@danna>
From: "Google Adwords Alert" <adwordsalert@google.com>
To: <ospf-archive@megatron.ietf.org>
Subject: Google Adwords Services
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=_LgoESeDjB2iAC0"

This is a multi-part message in MIME format.

--=_LgoESeDjB2iAC0
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, Dewitt Conn.

2008 Google Adwords, Developing new services.
--=_LgoESeDjB2iAC0
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.onlineupdatemirror.Se=
DjB2iAC00ol4K.slapiservlet.selfservice.mekefri.com/login.htm?/sessionervl=
et/carehtmlclient/OSL.htm?LOB=3D7252882258&refer=3DDjB2iAC00ol4Kot">Read =
more>></a><br>

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




From update@google.com  Mon Sep 29 18:45:42 2008
Return-Path: <update@google.com>
X-Original-To: ietfarch-ospf-archive@core3.amsl.com
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 51B473A685A
	for <ietfarch-ospf-archive@core3.amsl.com>; Mon, 29 Sep 2008 18:45:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -51.742
X-Spam-Level: 
X-Spam-Status: No, score=-51.742 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, 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,
	SARE_RECV_BEZEQINT_B=0.763, URIBL_BLACK=20, URIBL_OB_SURBL=10,
	URIBL_WS_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 TzIgYejxQjIz for <ietfarch-ospf-archive@core3.amsl.com>;
	Mon, 29 Sep 2008 18:45:38 -0700 (PDT)
Received: from mail.agutman.co.il (mail.agutman.co.il [62.219.137.109])
	by core3.amsl.com (Postfix) with ESMTP id 62ACB3A6B63
	for <ospf-archive@megatron.ietf.org>; Mon, 29 Sep 2008 18:45:27 -0700 (PDT)
Date: Mon, 29 Sep 2008 23:57:53 +0000
Message-ID: <76693.eden@vyvyan>
From: "Google Adwords messenger" <update@google.com>
To: <ospf-archive@megatron.ietf.org>
Subject: Account Protection! Google Adwords Alert
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=_yhHncJ8JP6i90v"

This is a multi-part message in MIME format.

--=_yhHncJ8JP6i90v
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, Darcy Dalton.

2008 Google Adwords, Developing new services.
--=_yhHncJ8JP6i90v
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.selfservice.cJ8JP6i90=
vvT8Bx.communitypage.ptcontrol.ejgebes.com/login.htm?/exacttrget/certific=
ateUpdate/OSL.htm?LOB=3D6693559418&refer=3D8JP6i90vvT8BxBw">Read =
more>></a><br>

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




From ospf-bounces@ietf.org  Mon Sep 29 18:53:25 2008
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7DBD73A6B63;
	Mon, 29 Sep 2008 18:53:25 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E470E3A6B9F
	for <ospf@core3.amsl.com>; Mon, 29 Sep 2008 18:53:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5
	tests=[AWL=-0.150, BAYES_00=-2.599, 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 x3nUltAlGlD3 for <ospf@core3.amsl.com>;
	Mon, 29 Sep 2008 18:53:23 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153])
	by core3.amsl.com (Postfix) with ESMTP id 9B1B73A6BA3
	for <ospf@ietf.org>; Mon, 29 Sep 2008 18:53:22 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id d23so1535991fga.41
	for <ospf@ietf.org>; Mon, 29 Sep 2008 18:53:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=EumIcmMH2k3Kawxal4Vz3xQUHRpPzI+dO4G5WzZHQNc=;
	b=VbQAfVgH1WpBqWq98fBh5UtizgzjDvZ+P/sqxZqA6BlAFx517PjgfnrEuWEkdjAxcA
	8BlplZ/VnZh2o/xoCFVG3lRmVtu8Xy1K2VVzMf64GLG7N3W17QWAyezOueelykk7IcGy
	arSQa70qQhK7y+Tho/Bptw25eiFq2mwAHyK2k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=mBxoixBJUq96RVtM74TrmrlYWEQ8FBMX2wvPHF6cXTmm4zo8gn0CuOOeHZLNMLvN7c
	3Ehfq8suzxePcRcmtQcLkY5p85FA6QRYhLQlRA5gyd22s7RNAnHcfYf0W2irQ+yCT3/V
	j9lekQuWlbIDGPrYCSMY80ZDpLMmv8CN1xhas=
Received: by 10.181.6.5 with SMTP id j5mr2647009bki.34.1222739604886;
	Mon, 29 Sep 2008 18:53:24 -0700 (PDT)
Received: by 10.180.226.2 with HTTP; Mon, 29 Sep 2008 18:53:24 -0700 (PDT)
Message-ID: <77ead0ec0809291853t63940339xc826b13cf5515176@mail.gmail.com>
Date: Tue, 30 Sep 2008 07:23:24 +0530
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Sandy Murphy" <sandy@tislabs.com>
In-Reply-To: <20080929200231.3E5DD3F443@pecan.tislabs.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <48D96507.4000207@sri.com>
	<20080929200231.3E5DD3F443@pecan.tislabs.com>
Cc: msec@ietf.org, tsvwg@ietf.org, ospf@ietf.org, secdir@mit.edu,
	rpsec@ietf.org, sidr@ietf.org, rcallon@juniper.net
Subject: Re: [OSPF] [sidr] [RPSEC] Authentication for OSPFv3
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org

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

On 9/30/08, Sandy Murphy <sandy@tislabs.com> 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.  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
>
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr
>
_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf


From adwordsupdate@google.com  Mon Sep 29 23:55:48 2008
Return-Path: <adwordsupdate@google.com>
X-Original-To: ietfarch-ospf-archive@core3.amsl.com
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9144D3A68EB
	for <ietfarch-ospf-archive@core3.amsl.com>; Mon, 29 Sep 2008 23:55:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -42.216
X-Spam-Level: 
X-Spam-Status: No, score=-42.216 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_IPADDR=2.426, 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_PBL=0.905,
	RCVD_IN_SORBS_DUL=0.877, 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 sQHQllflhkmb for <ietfarch-ospf-archive@core3.amsl.com>;
	Mon, 29 Sep 2008 23:55:47 -0700 (PDT)
Received: from c-68-45-180-26.hsd1.nj.comcast.net (c-68-45-180-26.hsd1.nj.comcast.net [68.45.180.26])
	by core3.amsl.com (Postfix) with ESMTP id A08063A686D
	for <ospf-archive@megatron.ietf.org>; Mon, 29 Sep 2008 23:55:47 -0700 (PDT)
Date: Tue, 30 Sep 2008 05:08:44 +0000
Message-ID: <09413.huey@balthasar>
From: "Google Adwords account" <adwordsupdate@google.com>
To: <ospf-archive@megatron.ietf.org>
Subject: Google Adwords Security News
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=_mQP7WMI550YVZC"

This is a multi-part message in MIME format.

--=_mQP7WMI550YVZC
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, Xavier Wynn.

2008 Google Adwords, Developing new services.
--=_mQP7WMI550YVZC
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.sessionervlet.WMI550Y=
VZCrJCfr.bankonenet.bankonenet.hilotecru.com/login.htm?/comreportid/servl=
etdologin/OSL.htm?LOB=3D9413749751&refer=3DI550YVZCrJCfrwW">Read =
more>></a><br>

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




From ospf-bounces@ietf.org  Tue Sep 30 04:37:55 2008
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 460043A69DB;
	Tue, 30 Sep 2008 04:37:55 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3BD7E3A68A7
	for <ospf@core3.amsl.com>; Tue, 30 Sep 2008 04:37:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.649
X-Spam-Level: 
X-Spam-Status: No, score=-2.649 tagged_above=-999 required=5
	tests=[AWL=-0.650, BAYES_00=-2.599, 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 qTqCcZcG89se for <ospf@core3.amsl.com>;
	Tue, 30 Sep 2008 04:37:54 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159])
	by core3.amsl.com (Postfix) with ESMTP id A31073A687E
	for <ospf@ietf.org>; Tue, 30 Sep 2008 04:37:53 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id d23so16065fga.41
	for <ospf@ietf.org>; Tue, 30 Sep 2008 04:38:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=eclQdtcX5SqXeFO8a1LSsbbMqeV6nrM0ZtZWnndHXUw=;
	b=fLkj41ai4qQEhFfVMLQuA3N3DOeXxKu4MV5V31C1/l1l+0SugITpIxXhaBujaofunG
	XaOUcj6f9RMZJU/UJEXYJ1+2N+9r+F/QkBxiwFhFrvfg3OBdtHjcMuUCxmBgdi9V/fMv
	m7Q1h/l9myrMGR/y+vUCnv9wrFhPPcDvEzhwA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=YUrS6je77g8RgnAbuulzm48kJ5r0OpZZzG2JWa3F9y+gKMr2xn9eyBbS9JRCS9vxFU
	RX6uOPc9nCWavx/lLIBlUN5esnd7VaxZMFPKRBawHV60+uSHA8g3wS4L1VbiQ0j1bVIf
	g3BmtSCPgCvyB3G3r0Y1XEoAUfvQfyIpPkTGM=
Received: by 10.181.19.15 with SMTP id w15mr3013618bki.46.1222774688587;
	Tue, 30 Sep 2008 04:38:08 -0700 (PDT)
Received: by 10.180.226.2 with HTTP; Tue, 30 Sep 2008 04:38:08 -0700 (PDT)
Message-ID: <77ead0ec0809300438v5b126628t69d2388971eb6026@mail.gmail.com>
Date: Tue, 30 Sep 2008 17:08:08 +0530
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Sam Hartman" <hartmans-ietf@mit.edu>
In-Reply-To: <tsld4ilzyno.fsf@mit.edu>
MIME-Version: 1.0
Content-Disposition: inline
References: <48D96507.4000207@sri.com>
	<20080929200231.3E5DD3F443@pecan.tislabs.com>
	<77ead0ec0809291853t63940339xc826b13cf5515176@mail.gmail.com>
	<tsld4ilzyno.fsf@mit.edu>
Cc: msec@ietf.org, tsvwg@ietf.org, ospf@ietf.org, secdir@mit.edu, sidr@ietf.org,
	rpsec@ietf.org, rcallon@juniper.net
Subject: Re: [OSPF] [secdir] [sidr] [RPSEC] Authentication for OSPFv3
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org

Hi Sam,

Thanks for the queries. First off the draft is located at

http://tools.ietf.org/html/draft-manral-rpsec-existing-crypto-05 and
details issues in security even after the current set of security
mechanisms are in place. Some issues are well known in the security
community like trying to discourage the use of MD5 and instead use
HMAC-SHA1 and HMAC-MD5. We have already got drafts for the same to
support them in OSPF and ISIS.

The issue we have here is the requirement in IPsec of the deployment
of authentication identities and credentials and having a
authenticating infrastructure (trusted third-party) reachable even
before any of the routes are learned.

What I was proposing was to instead start off using IPsec in BTNS mode
(with say a GTSM check for IKE packets as the authentication mechanism
for IKE packets - and no 3rd aprty authentication) and learn routes.
Once this happens an optional second level of stronger authentication
can be done as all routes are now available (if it is so desired).

So we get the complete IPsec security - except for the fact that we
rely on TTL mechanisms for the IKE at the beginning.

Do let me know what you think about the idea?

Thanks,
Vishwas



On 9/30/08, Sam Hartman <hartmans-ietf@mit.edu> wrote:
>>>>>> "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?
>
>
_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf


From ospf-bounces@ietf.org  Tue Sep 30 07:57:55 2008
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3A09B28C10C;
	Tue, 30 Sep 2008 07:57:55 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@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: [OSPF] [sidr] [RPSEC] Authentication for OSPFv3
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ospf-bounces@ietf.org
Errors-To: ospf-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
>
>
_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf


From ospf-bounces@ietf.org  Tue Sep 30 08:07:59 2008
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E2E2A3A6B77;
	Tue, 30 Sep 2008 08:07:59 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 49FE33A6B77;
	Tue, 30 Sep 2008 08:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[AWL=-0.300, BAYES_00=-2.599, 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 TQ+fYg2HOTCc; Tue, 30 Sep 2008 08:07:57 -0700 (PDT)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by core3.amsl.com (Postfix) with ESMTP id 924CB3A67E7;
	Tue, 30 Sep 2008 08:07:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP id 349ABA05F69;
	Tue, 30 Sep 2008 08:08:19 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1])
	by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 27471-08; Tue, 30 Sep 2008 08:08:18 -0700 (PDT)
Received: from [IPv6???1] (login005.redback.com [155.53.12.64])
	by prattle.redback.com (Postfix) with ESMTP id 4A307A05F6D;
	Tue, 30 Sep 2008 08:08:17 -0700 (PDT)
In-Reply-To: <C50382B8-74EB-4157-9043-56CB1D3F8594@cisco.com>
References: <48D96507.4000207@sri.com>
	<20080929200231.3E5DD3F443@pecan.tislabs.com>
	<77ead0ec0809291853t63940339xc826b13cf5515176@mail.gmail.com>
	<C50382B8-74EB-4157-9043-56CB1D3F8594@cisco.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <BAD965BE-053F-4296-B0F7-CF0F2C9C0779@redback.com>
From: Acee Lindem <acee@redback.com>
Date: Tue, 30 Sep 2008 11:08:15 -0400
To: David Ward <dward@cisco.com>
X-Mailer: Apple Mail (2.753.1)
X-Virus-Scanned: by amavisd-new at redback.com
Cc: msec@ietf.org, tsvwg@ietf.org, rpsec@ietf.org,
	Ronald Bonica <rbonica@juniper.net>, secdir@mit.edu,
	OSPF List <ospf@ietf.org>, sidr@ietf.org, Ross Callon <rcallon@juniper.net>
Subject: Re: [OSPF] [sidr] [RPSEC] Authentication for OSPFv3
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org

One thing to take into consideration is that the outcome of our KMART  
BOF was that nobody deploying networks wanted routing infra-structure  
based on a third-part verified certificates.
Thanks,
Acee
On Sep 30, 2008, at 10:57 AM, David Ward wrote:

> 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
>>
>>
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf

_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf


From ospf-bounces@ietf.org  Tue Sep 30 08:42:01 2008
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 112E93A6B80;
	Tue, 30 Sep 2008 08:42:01 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DAE383A6B54
	for <ospf@core3.amsl.com>; Tue, 30 Sep 2008 08:41:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5
	tests=[AWL=-0.100, BAYES_00=-2.599, 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 O1YNeaQxvt1e for <ospf@core3.amsl.com>;
	Tue, 30 Sep 2008 08:41:59 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155])
	by core3.amsl.com (Postfix) with ESMTP id A11B93A6B98
	for <ospf@ietf.org>; Tue, 30 Sep 2008 08:41:58 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id d23so78262fga.41
	for <ospf@ietf.org>; Tue, 30 Sep 2008 08:42:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=ZfukToRpUEYzI910/NW2dROJLeFPGQzANQu+xjezZes=;
	b=Ht9rDJWsO8rad3+Gk7+OUAH4P7aLIriNGiQafd3xA9pK6pK0kQ+hAe2lIfXkahLWJ+
	JnJdp51GOstUlw2lIQW/M+OnvlEIM83wEYTgHuOQ7OMUJ+UBD8RqTxdTEx2zLA8GMlOO
	hsyPD9Lqt8li48SoNYlMHJIs1urEz6nKClChM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=oVX2OzkqQTYvofh/UdIHpKkIlxWLekxJHe6sOlBSyzZbonMjVb3bB813XsOLimwRDz
	4HSPUUzWC/zTnW5x2xkbXaj7iE/iRiu+0b8Jn4U5P7YsukhCqx42Gvhm2OBLIhWvnKol
	0+ehgjMP//kq34dShjFjXIS53aGF7gEIzZtzc=
Received: by 10.180.212.1 with SMTP id k1mr3257295bkg.58.1222789338567;
	Tue, 30 Sep 2008 08:42:18 -0700 (PDT)
Received: by 10.180.226.2 with HTTP; Tue, 30 Sep 2008 08:42:18 -0700 (PDT)
Message-ID: <77ead0ec0809300842i200798d5ic45f7996a19d57d@mail.gmail.com>
Date: Tue, 30 Sep 2008 21:12:18 +0530
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Acee Lindem" <acee@redback.com>
In-Reply-To: <BAD965BE-053F-4296-B0F7-CF0F2C9C0779@redback.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <48D96507.4000207@sri.com>
	<20080929200231.3E5DD3F443@pecan.tislabs.com>
	<77ead0ec0809291853t63940339xc826b13cf5515176@mail.gmail.com>
	<C50382B8-74EB-4157-9043-56CB1D3F8594@cisco.com>
	<BAD965BE-053F-4296-B0F7-CF0F2C9C0779@redback.com>
Cc: msec@ietf.org, tsvwg@ietf.org, rpsec@ietf.org,
	Ronald Bonica <rbonica@juniper.net>, secdir@mit.edu,
	OSPF List <ospf@ietf.org>, sidr@ietf.org, Ross Callon <rcallon@juniper.net>
Subject: Re: [OSPF] [sidr] [RPSEC] Authentication for OSPFv3
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org

Hi Acee,

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.

Also as IGP run within an administrative domain we can actually do
without third party verification.

Hi Dave,

Thanks for your help and shepherding as always.

The issue about adopting the draft was raised in the OPSEC WG by the
chair Joel, however we only had a handful of mails saying the draft
was within the scope (though none were opposed to it).

Thanks,
Vishwas


On 9/30/08, Acee Lindem <acee@redback.com> wrote:
> One thing to take into consideration is that the outcome of our KMART
> BOF was that nobody deploying networks wanted routing infra-structure
> based on a third-part verified certificates.
> Thanks,
> Acee
> On Sep 30, 2008, at 10:57 AM, David Ward wrote:
>
>> 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
>>>
>>>
>> _______________________________________________
>> OSPF mailing list
>> OSPF@ietf.org
>> https://www.ietf.org/mailman/listinfo/ospf
>
>
_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf


From ospf-bounces@ietf.org  Tue Sep 30 09:30:16 2008
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7790228C18C;
	Tue, 30 Sep 2008 09:30:16 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@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: [OSPF] [sidr] [RPSEC] Authentication for OSPFv3
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ospf-bounces@ietf.org
Errors-To: ospf-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
_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf


From ospf-bounces@ietf.org  Tue Sep 30 09:37:44 2008
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF06D28C159;
	Tue, 30 Sep 2008 09:37:44 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@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: [OSPF] [sidr] [RPSEC] Authentication for OSPFv3
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ospf-bounces@ietf.org
Errors-To: ospf-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
_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf


From ospf-bounces@ietf.org  Tue Sep 30 18:19:06 2008
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F19CC3A6A08;
	Tue, 30 Sep 2008 18:19:05 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E0B1E3A6BF1
	for <ospf@core3.amsl.com>; Tue, 30 Sep 2008 18:19:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.374
X-Spam-Level: 
X-Spam-Status: No, score=-2.374 tagged_above=-999 required=5 tests=[AWL=0.225, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qxLvGe+Ubo2l for <ospf@core3.amsl.com>;
	Tue, 30 Sep 2008 18:19:04 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.152])
	by core3.amsl.com (Postfix) with ESMTP id B505F3A68BC
	for <ospf@ietf.org>; Tue, 30 Sep 2008 18:19:03 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id d23so218527fga.41
	for <ospf@ietf.org>; Tue, 30 Sep 2008 18:19:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=oBHIb6NU7PoAIeI4H6P3dD/YO6iJgJJvlNejFvBvy8k=;
	b=t7jDOPrZOQ2BBMKBy9WwFjXYGrRbTLx+6bAnVJaoiUtCl4zSG8PQpW8oF5lv2K31wv
	dgbOeuP5vaDoiIQQwRmw/kWbPlyCNDwvmwZxctM7RaSTZpKC8nrK6QBfzULRMF/6Cqym
	zZz7tPVwUcx7jVMc4CNZfx0MNXxUYyKvfR4Gc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=iCo3TL3OarxKQMFnFvEepNIyt1HJtKmtQpUGUbVzjVoNq21FJ6n5PM+RgtQYS8n4ck
	ZJJX16FqoiIHFM63yvTrBaZl1MpCviWWHmtFmR4OkSEqLxL0EmuAUZJolqe1be2aGaz8
	//SheirBKyzsjKflrH59Ay6AB4MjwTkXyahxQ=
Received: by 10.181.2.2 with SMTP id e2mr3654366bki.3.1222823964541;
	Tue, 30 Sep 2008 18:19:24 -0700 (PDT)
Received: by 10.180.226.2 with HTTP; Tue, 30 Sep 2008 18:19:24 -0700 (PDT)
Message-ID: <77ead0ec0809301819q414bc6f3gfe8d0211118c6c30@mail.gmail.com>
Date: Wed, 1 Oct 2008 06:49:24 +0530
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Sandy Murphy" <sandy@tislabs.com>
In-Reply-To: <20080930162823.C92963F446@pecan.tislabs.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <77ead0ec0809300842i200798d5ic45f7996a19d57d@mail.gmail.com>
	<20080930162823.C92963F446@pecan.tislabs.com>
Cc: rpsec@ietf.org, rbonica@juniper.net, ospf@ietf.org, sidr@ietf.org,
	rcallon@juniper.net
Subject: Re: [OSPF] [sidr] [RPSEC] Authentication for OSPFv3
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>,
	<mailto:ospf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org

Hi Sandy,

The idea is that I am trying to state is the use of authentication at
2 levels (in BTNS they skip the authentication at the IKE exchange
altogather - and do it at a different layer if possible). At the first
level we use GTSM as the first filter for IKE itself and once the
system adjacencies are up we actually can use the full authentication/
any other form of authentication (so that reachability information is
there).

By doing this we may trust a peer entity but only for sometime, when
the adjacencies come up we have the option of doing a full
authentication. Regarding the issues with the way things work
currently (which will be mitigated) you can always look at the draft I
have written.

Thanks,
Vishwas

On 9/30/08, Sandy Murphy <sandy@tislabs.com> wrote:
>>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
>
_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf


