Query on RFC1793 (OSPF over demain circuits)

Paresh Khatri <Paresh.Khatri@AAPT.COM.AU> Fri, 08 July 2005 10:49 UTC

Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqqQT-0003g3-3V for ospf-archive@megatron.ietf.org; Fri, 08 Jul 2005 06:49:45 -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 GAA19430 for <ospf-archive@LISTS.IETF.ORG>; Fri, 8 Jul 2005 06:49:42 -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 <9.0109ECE7@cherry.ease.lsoft.com>; Fri, 8 Jul 2005 6:49:43 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.4) with spool id 78366586 for OSPF@PEACH.EASE.LSOFT.COM; Fri, 8 Jul 2005 06:49:28 -0400
Received: from 146.171.13.196 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0l) with TCP; Fri, 8 Jul 2005 06:49:28 -0400
Received: from aksmtpmdr2 (ish3-internal [146.171.1.21]) by smtp3.telecom.co.nz (Postfix) with ESMTP id 220461F37 for <OSPF@PEACH.EASE.LSOFT.COM>; Fri, 8 Jul 2005 22:43:32 +1200 (NZST)
Received: from 146.171.227.25 by aksmtpmdr2 with ESMTP (Tumbleweed MMS SMTP Relay); Fri, 08 Jul 2005 22:49:15 +1200
X-Server-Uuid: 39C90538-1505-4F6D-9FBD-402FA253957C
Received: from AUNSWA003.au.tcnz.net ([10.136.168.51]) by akexsmtp02.telecom.tcnz.net with Microsoft SMTPSVC(6.0.3790.211); Fri, 8 Jul 2005 22:49:14 +1200
Received: from aunswa002.au.tcnz.net ([10.136.168.50]) by AUNSWA003.au.tcnz.net with Microsoft SMTPSVC(5.0.2195.6747); Fri, 8 Jul 2005 20:49:14 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
MIME-Version: 1.0
X-MS-TNEF-Correlator: <44CF9D8D25966C4DB1072958419273DB406826@aunswa002.au.tcnz.net>
Thread-Topic: RFC-3630: Router Address TLV
thread-index: AcWBvSnjeIYfmcewRvagdrEmd8DriQB67EDG
X-OriginalArrivalTime: 08 Jul 2005 10:49:14.0411 (UTC) FILETIME=[AE6EE7B0:01C583AA]
X-WSS-ID: 6ED085A11HG7930253-01-01
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Message-ID: <44CF9D8D25966C4DB1072958419273DB406826@aunswa002.au.tcnz.net>
Date: Fri, 08 Jul 2005 20:49:14 +1000
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Paresh Khatri <Paresh.Khatri@AAPT.COM.AU>
Subject: Query on RFC1793 (OSPF over demain circuits)
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: quoted-printable

Hi all,

I'm trying to understand the example in Section 2.5 - Interoperability with unmodified OSPF routers.  

The example states that router B (a non-DC capable router) will treat DoNotAge LSAs as MaxAge LSAs and will acknowledge them as such to router A.  But router A will notice that the ack is for a different instance and will re-transmit the LSA.  My question is - why would router A consider it to be an ack for a different instance ?  Is the implication here that router B would set the Age in the LSAck to be MaxAge and not the Age that was present in the received LSA ?

Thanks in advance.

Paresh




This communication, including any attachments, is confidential. If 
 you are not the intended recipient, you should not read it - please 
 contact me immediately, destroy it, and do not copy or use any part of 
 this communication or disclose anything about it.