Re: OSPF WG Minutes
Vishwas Manral <Vishwas@SINETT.COM> Tue, 16 August 2005 04:33 UTC
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E4t8r-0006Kf-B7 for ospf-archive@megatron.ietf.org; Tue, 16 Aug 2005 00:33:37 -0400
Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05171 for <ospf-archive@LISTS.IETF.ORG>; Tue, 16 Aug 2005 00:33:34 -0400 (EDT)
Received: from vms.dc.lsoft.com (209.119.0.2) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <21.010CD368@cherry.ease.lsoft.com>; Tue, 16 Aug 2005 0:33:35 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.4) with spool id 82690444 for OSPF@PEACH.EASE.LSOFT.COM; Tue, 16 Aug 2005 00:33:15 -0400
Received: from 63.197.255.158 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0m) with TCP; Tue, 16 Aug 2005 00:33:15 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: OSPF WG Minutes
Thread-Index: AcWhpoh7BmLR6MNUSRm4gKBsujpcYgAdK//w
Message-ID: <BB6D74C75CC76A419B6D6FA7C38317B290E932@sinett-sbs.SiNett.LAN>
Date: Mon, 15 Aug 2005 21:34:42 -0700
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Vishwas Manral <Vishwas@SINETT.COM>
Subject: Re: OSPF WG Minutes
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: quoted-printable
Hi Acee, > Acee: In practice, for OSPFv2 the sequence numbers are not monotically > increasing; Usage of router's clock for cryptographic sequence number > generation reduces the chance for replay attacks across restarts. > ?: OSPF spec does not say it ... Acee, what I meant was that although the OSPF spec does not state that we need to use clocks. I think the vulnerabilities draft is the right place to state the problems that can happen if we do not use a clock (or something equivalent which increments even when a system goes down). Another issue is that even if the sender uses clock for the "sequence number" and goes down, all the packets of a previous session can still be replayed by another router. So the chance of replay attacks is still there. Thanks, Vishwas -----Original Message----- From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM] On Behalf Of Acee Lindem Sent: Monday, August 15, 2005 7:50 PM To: OSPF@PEACH.EASE.LSOFT.COM Subject: OSPF WG Minutes Attached are the minutes from the Paris OSPF WG meeting. Thanks to Dimitri for taking them. Acee
- OSPF WG Minutes Acee Lindem
- Re: OSPF WG Minutes Vishwas Manral
- NSSA summarization Ajay Thakur
- Re: NSSA summarization sujay
- Re: OSPF WG Minutes Acee Lindem
- Re: OSPF WG Minutes Vishwas Manral
- Re: OSPF WG Minutes ashok
- Re: OSPF WG Minutes Paul Jakma
- [OSPF] OSPF WG Minutes Acee Lindem
- Re: [OSPF] OSPF WG Minutes Vishwas Manral
- Re: [OSPF] OSPF WG Minutes Acee Lindem
- [OSPF] OSPF WG Minutes Acee Lindem
- Re: [OSPF] OSPF WG Minutes Acee Lindem (acee)
- [OSPF] OSPF WG Minutes Acee Lindem (acee)
- Re: [OSPF] OSPF WG Minutes Shraddha Hegde