OSPFv3 query (link LSAs & link local addresses)

Arthur Dimitrelis <arthurd@ARC.CORP.MOT.COM> Mon, 26 August 2002 09:55 UTC

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 FAA04948 for <ospf-archive@LISTS.IETF.ORG>; Mon, 26 Aug 2002 05:55:35 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <0.006EC93D@cherry.ease.lsoft.com>; Mon, 26 Aug 2002 5:56:53 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 91632 for OSPF@DISCUSS.MICROSOFT.COM; Mon, 26 Aug 2002 05:56:53 -0400
Received: from 129.188.136.100 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Mon, 26 Aug 2002 05:56:53 -0400
Received: [from pobox4.mot.com (pobox4.mot.com [10.64.251.243]) by motgate.mot.com (motgate 2.1) with ESMTP id CAA05633 for <OSPF@DISCUSS.MICROSOFT.COM>; Mon, 26 Aug 2002 02:56:52 -0700 (MST)]
Received: [from homer.arc.corp.mot.com (homer.arc.corp.mot.com [10.238.80.38]) by pobox4.mot.com (MOT-pobox4 2.0) with ESMTP id CAA09629 for <OSPF@DISCUSS.MICROSOFT.COM>; Mon, 26 Aug 2002 02:56:50 -0700 (MST)]
Received: from arc.corp.mot.com (arthurd.arc.corp.mot.com [10.238.80.59]) by homer.arc.corp.mot.com (8.12.2/8.12.2) with ESMTP id g7Q9uk7C012889 for <OSPF@DISCUSS.MICROSOFT.COM>; Mon, 26 Aug 2002 19:56:48 +1000 (EST)
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <3D69FB5F.94EE1AEC@arc.corp.mot.com>
Date: Mon, 26 Aug 2002 19:56:47 +1000
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: Arthur Dimitrelis <arthurd@ARC.CORP.MOT.COM>
Subject: OSPFv3 query (link LSAs & link local addresses)
To: OSPF@DISCUSS.MICROSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

Hi everyone,

I've got a query regarding OSPF for IPv6. With reference to RFC2740,
section 2.5 discusses how IPv6 link local addresses are used as the
source addresses in PDU exchanges between OSPFv3 speakers (including
HELLO packets), and goes on to state that an OSPFv3 router will learn
the link-local addresses of all other routers attached to its links. No
problems with all that.

Now, appendix A.4.8 defines the packet format of a link LSA, which
includes the link local address of its originating router. The
commentary in this section explains that one of the purposes of a link
LSA is to allow all routers on the link to learn the link-local address
of the LSA's originator. Could this information not have been deduced
from the Advertising Router ID field in the LSA's header (along with the
information gleaned from previously seen HELLO packets, ie from those
neighbors a router considers to be in the '2-way' state) ?

Anybody know about or have any ideas on this apparent (to me)
redundancy?

cheers,
arthur