Clarification on multiple instances for OSPFv3
gail_browne@AGILENT.COM Tue, 09 September 2003 20:47 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 QAA03905 for <ospf-archive@LISTS.IETF.ORG>; Tue, 9 Sep 2003 16:47:22 -0400 (EDT)
Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <0.00B64395@cherry.ease.lsoft.com>; Tue, 9 Sep 2003 16:47:25 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 54564596 for OSPF@PEACH.EASE.LSOFT.COM; Tue, 9 Sep 2003 16:47:23 -0400
Received: from 192.25.240.36 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Tue, 9 Sep 2003 16:47:23 -0400
Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas1x.cos.agilent.com (Postfix) with ESMTP id 6D5F9273C0 for <OSPF@PEACH.EASE.LSOFT.COM>; Tue, 9 Sep 2003 14:47:23 -0600 (MDT)
Received: from wcosbh22.cos.agilent.com (wcosbh22.cos.agilent.com [130.29.152.178]) by relcos2.cos.agilent.com (Postfix) with ESMTP id 4C9E4DA7 for <OSPF@PEACH.EASE.LSOFT.COM>; Tue, 9 Sep 2003 14:47:23 -0600 (MDT)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Thread-Topic: Clarification on multiple instances for OSPFv3
Thread-Index: AcN3E4w6lHsnVO6tQeiFcGfL1QM+/w==
Message-ID: <0D9185CE635BD511ACA50090277A6FCF037EA72D@axcs18.cos.agilent.com>
Date: Tue, 09 Sep 2003 14:47:14 -0600
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: gail_browne@AGILENT.COM
Subject: Clarification on multiple instances for OSPFv3
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: quoted-printable
Hi All, In OSPFv3 as per RFC2740 section 2.4, multiple instances are supported through the parameter Instance ID. My understanding is that this is used because multiple OSPFv3 instances will potentially run over the same physical interface, and therefore use the same IPv6 addresses, and the instance ID will help in delivery of incoming OSPFv3 packets. New for OSPFv3 is the fact that neighbors are identified solely by their router Id (Section 3.2.2.1), this should imply that there needs to be an enforcement of no duplicate router Id's so that every instance of ospfv3 configured on a router must have its own unique router Id. Am I correct in this assumption? Thanks in advance, Gail
- Clarification on multiple instances for OSPFv3 gail_browne
- Re: Clarification on multiple instances for OSPFv3 Acee Lindem