From owner-ospf@PEACH.EASE.LSOFT.COM  Thu Sep  2 08:32:04 2004
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 IAA28033
	for <ospf-archive@LISTS.IETF.ORG>; Thu, 2 Sep 2004 08:32:03 -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 <6.00E6995B@cherry.ease.lsoft.com>; Thu, 2 Sep 2004 8:32:01 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 33678440 for OSPF@PEACH.EASE.LSOFT.COM;
          Thu, 2 Sep 2004 08:32:00 -0400
Received: from 203.124.166.180 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i)
          with TCP; Thu, 2 Sep 2004 08:21:56 -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.0.6603.0
Thread-Topic: Regarding RFC 1765 OSPF Database Overflow
Thread-Index: AcSQ52pc6wVMSmrZRdmhkcKSIoPTaQ==
Message-ID:  <36993D449C7FA647BF43568E0793AB3E8F2F4B@nevis_pune_xchg.pune.nevisnetworks.com>
Date:         Thu, 2 Sep 2004 17:51:46 +0530
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Naresh Paliwal <naresh.paliwal@NEVISNETWORKS.COM>
Subject: FW: Regarding RFC 1765 OSPF Database Overflow
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: quoted-printable

Its said in the RFC that "Parameter, ospfExtLsdbLimit, must be the same
in all routers in the routing domain."

Same time we discuss a case of receiving a new AS-External-LSA which
causes
to hit the limiting parameter.

If the parameter, ospfExtLsdbLimit, is same on all the routers, such an
LSA
will never be generated. The originating router itself will hit the
limit,
and will enter in OverflowSate.

Please let me know if my understanding is wrong. Why should we implement
this case (the receiving of N'th AS-External-LSA).

Regards

- Naresh Paliwal

Nevis Networks Pvt Ltd

www.nevisnetworks.com


From owner-ospf@PEACH.EASE.LSOFT.COM  Thu Sep  2 10:56:04 2004
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 KAA10093
	for <ospf-archive@LISTS.IETF.ORG>; Thu, 2 Sep 2004 10:56:03 -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 <1.00E69C38@cherry.ease.lsoft.com>; Thu, 2 Sep 2004 10:56:03 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 33689429 for OSPF@PEACH.EASE.LSOFT.COM;
          Thu, 2 Sep 2004 10:56:02 -0400
Received: from 192.91.191.4 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Thu, 2 Sep 2004 10:56:02 -0400
Received: by goodman.datcon.co.uk with Internet Mail Service (5.5.2657.72) id
          <R0RAPX53>; Thu, 2 Sep 2004 15:55:48 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID:  <53F74F5A7B94D511841C00B0D0AB16F802870AD7@baker.datcon.co.uk>
Date:         Thu, 2 Sep 2004 15:55:54 +0100
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Nic Neate <Nic.Neate@DATACONNECTION.COM>
Subject: Unnumbered and tunnel interfaces in OSPFv3
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

Hi all,

I have a few OSPFv3 questions I was hoping someone could help me with.

1.  Is there any concept of an unnumbered interface in OSPFv3?  (As far as I
can see from RFC 2740, there isn't.)

2.  If yes, how do they work?  I would guess most principles from OSPFv2 can
be carried over, but what about usage of the Link-LSA?

3.  If not, are there any guidelines on how, for example, RSVP tunnel
interfaces should be handled?

Thanks in advance,

Nic


From owner-ospf@PEACH.EASE.LSOFT.COM  Thu Sep  2 13:24:04 2004
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 NAA20832
	for <ospf-archive@LISTS.IETF.ORG>; Thu, 2 Sep 2004 13:24:04 -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 <14.00E69E4C@cherry.ease.lsoft.com>; Thu, 2 Sep 2004 13:24:03 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 33706253 for OSPF@PEACH.EASE.LSOFT.COM;
          Thu, 2 Sep 2004 13:24:02 -0400
Received: from 64.233.170.202 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i)
          with TCP; Thu, 2 Sep 2004 13:24:02 -0400
Received: by mproxy.gmail.com with SMTP id 74so330361rnl for
          <ospf@peach.ease.lsoft.com>; Thu, 02 Sep 2004 10:24:01 -0700 (PDT)
Received: by 10.38.88.12 with SMTP id l12mr644159rnb; Thu, 02 Sep 2004 10:24:01
          -0700 (PDT)
Received: by 10.38.24.31 with HTTP; Thu, 2 Sep 2004 10:24:01 -0700 (PDT)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <36993D449C7FA647BF43568E0793AB3E8F2F4B@nevis_pune_xchg.pune.nevisnetworks.com>
Message-ID:  <c03d3047040902102473e82cba@mail.gmail.com>
Date:         Thu, 2 Sep 2004 10:24:01 -0700
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Dilip Kumar <dilipks@GMAIL.COM>
Subject: Re: FW: Regarding RFC 1765 OSPF Database Overflow
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To:  <36993D449C7FA647BF43568E0793AB3E8F2F4B@nevis_pune_xchg.pune.nevisnetworks.com>
Precedence: list
Content-Transfer-Encoding: 7bit

Self-Originated AS-External LSAs are not accounted for while comparing
with the ospfExtLsdbLimit. ospfExtLsdbLimit is compared with total
number of AS-Ext LSAs generated by other routers in OSPF domain.

-- Dilip


On Thu, 2 Sep 2004 17:51:46 +0530, Naresh Paliwal
<naresh.paliwal@nevisnetworks.com> wrote:
> Its said in the RFC that "Parameter, ospfExtLsdbLimit, must be the same
> in all routers in the routing domain."
>
> Same time we discuss a case of receiving a new AS-External-LSA which
> causes
> to hit the limiting parameter.
>
> If the parameter, ospfExtLsdbLimit, is same on all the routers, such an
> LSA
> will never be generated. The originating router itself will hit the
> limit,
> and will enter in OverflowSate.
>
> Please let me know if my understanding is wrong. Why should we implement
> this case (the receiving of N'th AS-External-LSA).
>
> Regards
>
> - Naresh Paliwal
>
> Nevis Networks Pvt Ltd
>
> www.nevisnetworks.com
>


From owner-ospf@PEACH.EASE.LSOFT.COM  Thu Sep  2 14:06:58 2004
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 OAA24667
	for <ospf-archive@LISTS.IETF.ORG>; Thu, 2 Sep 2004 14:06:58 -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 <1.00E6A076@cherry.ease.lsoft.com>; Thu, 2 Sep 2004 14:06:45 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 33710273 for OSPF@PEACH.EASE.LSOFT.COM;
          Thu, 2 Sep 2004 14:06:43 -0400
Received: from 192.75.23.69 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Thu, 2 Sep 2004 14:06:43 -0400
Received: from alcatel.com (localhost [127.0.0.1]) by tm2.ca.alcatel.com
          (8.13.0/8.13.0) with ESMTP id i82I6eEJ003578 for
          <OSPF@PEACH.EASE.LSOFT.COM>; Thu, 2 Sep 2004 14:06:40 -0400 (EDT)
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
References: <36993D449C7FA647BF43568E0793AB3E8F2F4B@nevis_pune_xchg.pune.nevisnetworks.com>
            <c03d3047040902102473e82cba@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID:  <4137612F.C6F38AB9@alcatel.com>
Date:         Thu, 2 Sep 2004 14:06:39 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Ehsan Rezaaifar <ehsan.rezaaifar@ALCATEL.COM>
Organization: Alcatel CID
Subject: Re: FW: Regarding RFC 1765 OSPF Database Overflow
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

Dilip Kumar wrote:

> Self-Originated AS-External LSAs are not accounted for while comparing
> with the ospfExtLsdbLimit. ospfExtLsdbLimit is compared with total
> number of AS-Ext LSAs generated by other routers in OSPF domain.

That's not correct. The total number of non-default AS-External LSAs
(including
the self originated ones) should not exceed the ospfExtLsdbLimit (Sec. 2.2 in
RFC).
If the ospfExtLsdbLimit parameter is the same in all routers the router
originating the
external LSA is the one going into overflow mode. But during LSDB convergence
it's
possible to receive type 5 LSAs causing a router going to overflow mode as
described in
sec. 2.3.1 of the RFC.

Take care,
Ehsan

>
>
> -- Dilip
>
> On Thu, 2 Sep 2004 17:51:46 +0530, Naresh Paliwal
> <naresh.paliwal@nevisnetworks.com> wrote:
> > Its said in the RFC that "Parameter, ospfExtLsdbLimit, must be the same
> > in all routers in the routing domain."
> >
> > Same time we discuss a case of receiving a new AS-External-LSA which
> > causes
> > to hit the limiting parameter.
> >
> > If the parameter, ospfExtLsdbLimit, is same on all the routers, such an
> > LSA
> > will never be generated. The originating router itself will hit the
> > limit,
> > and will enter in OverflowSate.
> >
> > Please let me know if my understanding is wrong. Why should we implement
> > this case (the receiving of N'th AS-External-LSA).
> >
> > Regards
> >
> > - Naresh Paliwal
> >
> > Nevis Networks Pvt Ltd
> >
> > www.nevisnetworks.com
> >


From owner-ospf@PEACH.EASE.LSOFT.COM  Thu Sep  2 17:26:31 2004
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 RAA12999
	for <ospf-archive@LISTS.IETF.ORG>; Thu, 2 Sep 2004 17:26:31 -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 <10.00E6A65B@cherry.ease.lsoft.com>; Thu, 2 Sep 2004 17:26:30 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 33732280 for OSPF@PEACH.EASE.LSOFT.COM;
          Thu, 2 Sep 2004 17:26:29 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Thu, 2 Sep 2004 17:26:29 -0400
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com
          (Postfix) with ESMTP id DFABFA10033 for <OSPF@PEACH.EASE.LSOFT.COM>;
          Thu,  2 Sep 2004 14:26:27 -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 16850-02 for 
          <OSPF@PEACH.EASE.LSOFT.COM>; Thu,  2 Sep 2004 14:26:27 -0700 (PDT)
Received: from aceeinspiron (unknown [172.31.253.64]) by prattle.redback.com
          (Postfix) with SMTP id 561A1A10031 for <OSPF@PEACH.EASE.LSOFT.COM>;
          Thu,  2 Sep 2004 14:26:27 -0700 (PDT)
References:  <53F74F5A7B94D511841C00B0D0AB16F802870AD7@baker.datcon.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Virus-Scanned: by amavisd-new at redback.com
Message-ID:  <0c4e01c49133$7ed40400$0202a8c0@aceeinspiron>
Date:         Thu, 2 Sep 2004 17:26:18 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Re: Unnumbered and tunnel interfaces in OSPFv3
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

Hi Nic,

----- Original Message -----
From: "Nic Neate" <Nic.Neate@DATACONNECTION.COM>
To: <OSPF@PEACH.EASE.LSOFT.COM>
Sent: Thursday, September 02, 2004 10:55 AM
Subject: Unnumbered and tunnel interfaces in OSPFv3


> Hi all,
>
> I have a few OSPFv3 questions I was hoping someone could help me with.
>
> 1.  Is there any concept of an unnumbered interface in OSPFv3?  (As far as I
> can see from RFC 2740, there isn't.)

Since OSPFv3 runs on a link rather than a subnet, there should be fewer
considerations.

>
> 2.  If yes, how do they work?  I would guess most principles from OSPFv2 can
> be carried over, but what about usage of the Link-LSA?

It seems that it could be suppressed for unnumbered LSAs. In fact, it has crossed
my mind that they could be suppressed for all OSPFv3 P2P links. At least in our
implementation, we don't need to discover the link local address and any prefixes
associated with the link are advertised in one of the router intra-area-prefix LSAs.


>
> 3.  If not, are there any guidelines on how, for example, RSVP tunnel
> interfaces should be handled?

I would think this would be transparent to OSPFv3.

>
> Thanks in advance,
>
> Nic


From owner-ospf@PEACH.EASE.LSOFT.COM  Mon Sep  6 10:21:17 2004
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 KAA07857
	for <ospf-archive@LISTS.IETF.ORG>; Mon, 6 Sep 2004 10:21:16 -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 <20.00E6FDBB@cherry.ease.lsoft.com>; Mon, 6 Sep 2004 10:21:16 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 34193373 for OSPF@PEACH.EASE.LSOFT.COM;
          Mon, 6 Sep 2004 10:21:15 -0400
Received: from 192.91.191.4 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Mon, 6 Sep 2004 10:21:15 -0400
Received: by goodman.datcon.co.uk with Internet Mail Service (5.5.2657.72) id
          <R0RARC5J>; Mon, 6 Sep 2004 15:21:00 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID:  <53F74F5A7B94D511841C00B0D0AB16F802870AE3@baker.datcon.co.uk>
Date:         Mon, 6 Sep 2004 15:20:55 +0100
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Nic Neate <Nic.Neate@DATACONNECTION.COM>
Subject: Re: Unnumbered and tunnel interfaces in OSPFv3
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

Hi Acee,

Thanks for your response.  I agree that the Link-LSA doesn't seem to have a
purpose on unnumbered links, and perhaps an option not to use the Link-LSA
on any P2P links would also be appropriate.

To tie things down, I think we agree that OSPFv3 should run over unnumbered
interfaces as follows.  Please let me know if there is anything missing or
incorrect.

 - For OSPFv3 purposes, an unnumbered interface is defined as an interface
with no link-local address (but possibly with site-local or global
addresses).

 - Any address on the corresponding node is used for the source/destination
address in protocol packets sent over unnumbered interfaces (as in OSPFv2).

 - Unnumbered interfaces are identified in the protocol (for example, in
Router-LSAs) by their Interface ID and Router ID (as with numbered
interfaces).

 - The Link-LSA is not sent over unnumbered interfaces.  Any site-local or
global addresses configured are advertised in the router's
Intra-area-prefix-LSA.

Do you think there would be scope/demand for a short draft to standardize
this?  I would be happy to contribute if so.

Thanks,

Nic


-----Original Message-----
From: Acee Lindem [mailto:acee@REDBACK.COM]
Sent: Thursday, September 02, 2004 10:26 PM
To: OSPF@PEACH.EASE.LSOFT.COM
Subject: Re: Unnumbered and tunnel interfaces in OSPFv3


Hi Nic,

----- Original Message -----
From: "Nic Neate" <Nic.Neate@DATACONNECTION.COM>
To: <OSPF@PEACH.EASE.LSOFT.COM>
Sent: Thursday, September 02, 2004 10:55 AM
Subject: Unnumbered and tunnel interfaces in OSPFv3


> Hi all,
>
> I have a few OSPFv3 questions I was hoping someone could help me with.
>
> 1.  Is there any concept of an unnumbered interface in OSPFv3?  (As far as
I
> can see from RFC 2740, there isn't.)

Since OSPFv3 runs on a link rather than a subnet, there should be fewer
considerations.

>
> 2.  If yes, how do they work?  I would guess most principles from OSPFv2
can
> be carried over, but what about usage of the Link-LSA?

It seems that it could be suppressed for unnumbered LSAs. In fact, it has
crossed
my mind that they could be suppressed for all OSPFv3 P2P links. At least in
our
implementation, we don't need to discover the link local address and any
prefixes
associated with the link are advertised in one of the router
intra-area-prefix LSAs.


>
> 3.  If not, are there any guidelines on how, for example, RSVP tunnel
> interfaces should be handled?

I would think this would be transparent to OSPFv3.

>
> Thanks in advance,
>
> Nic


From owner-ospf@PEACH.EASE.LSOFT.COM  Tue Sep  7 07:35:13 2004
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 HAA14161
	for <ospf-archive@LISTS.IETF.ORG>; Tue, 7 Sep 2004 07:35:12 -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 <18.00E713E3@cherry.ease.lsoft.com>; Tue, 7 Sep 2004 7:35:11 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 34310025 for OSPF@PEACH.EASE.LSOFT.COM;
          Tue, 7 Sep 2004 07:35:09 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Tue, 7 Sep 2004 07:35:09 -0400
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com
          (Postfix) with ESMTP id 98F6B73BD36 for <OSPF@PEACH.EASE.LSOFT.COM>;
          Tue,  7 Sep 2004 04:35:06 -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 09085-02 for 
          <OSPF@PEACH.EASE.LSOFT.COM>; Tue,  7 Sep 2004 04:35:06 -0700 (PDT)
Received: from aceeinspiron (unknown [172.31.253.49]) by prattle.redback.com
          (Postfix) with SMTP id D0D8B73BD32 for <OSPF@PEACH.EASE.LSOFT.COM>;
          Tue,  7 Sep 2004 04:35:05 -0700 (PDT)
References:  <53F74F5A7B94D511841C00B0D0AB16F802870AE3@baker.datcon.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
              reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Virus-Scanned: by amavisd-new at redback.com
Message-ID:  <00e101c494ce$b1a59850$0202a8c0@aceeinspiron>
Date:         Tue, 7 Sep 2004 07:34:53 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Re: Unnumbered and tunnel interfaces in OSPFv3
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

Hi Nic,

----- Original Message -----
From: "Nic Neate" <Nic.Neate@DATACONNECTION.COM>
To: <OSPF@PEACH.EASE.LSOFT.COM>
Sent: Monday, September 06, 2004 10:20 AM
Subject: Re: Unnumbered and tunnel interfaces in OSPFv3


> Hi Acee,
>
> Thanks for your response.  I agree that the Link-LSA doesn't seem to have a
> purpose on unnumbered links, and perhaps an option not to use the Link-LSA
> on any P2P links would also be appropriate.
>
> To tie things down, I think we agree that OSPFv3 should run over unnumbered
> interfaces as follows.  Please let me know if there is anything missing or
> incorrect.
>
> - For OSPFv3 purposes, an unnumbered interface is defined as an interface
> with no link-local address (but possibly with site-local or global
> addresses).

It funny but I would have interpreted it to be just the opposite - an interface
with a link-local address of one sort or another and no site-local or global
addresses.

>
> - Any address on the corresponding node is used for the source/destination
> address in protocol packets sent over unnumbered interfaces (as in OSPFv2).

I don't agree here since I think there still should be a link-local address.

>
> - Unnumbered interfaces are identified in the protocol (for example, in
> Router-LSAs) by their Interface ID and Router ID (as with numbered
> interfaces).

Agreed.

>
> - The Link-LSA is not sent over unnumbered interfaces.  Any site-local or
> global addresses configured are advertised in the router's
> Intra-area-prefix-LSA.

I don't think the Link-LSA is required on P2P links - see below.

>
> Do you think there would be scope/demand for a short draft to standardize
> this?  I would be happy to contribute if so.

In thinking about this more, I think an "unnumbered" link in IPv6 is simply
any interface that has a link-local address but no global addresses (note
that site-local addresses have been deprecated). Hence, this is already
handled by RFC 2740. We may want to have more discussion of allowing
link-LSAs to be omitted on P2P links.



>
> Thanks,
>
> Nic
>
>
> -----Original Message-----
> From: Acee Lindem [mailto:acee@REDBACK.COM]
> Sent: Thursday, September 02, 2004 10:26 PM
> To: OSPF@PEACH.EASE.LSOFT.COM
> Subject: Re: Unnumbered and tunnel interfaces in OSPFv3
>
>
> Hi Nic,
>
> ----- Original Message -----
> From: "Nic Neate" <Nic.Neate@DATACONNECTION.COM>
> To: <OSPF@PEACH.EASE.LSOFT.COM>
> Sent: Thursday, September 02, 2004 10:55 AM
> Subject: Unnumbered and tunnel interfaces in OSPFv3
>
>
>> Hi all,
>>
>> I have a few OSPFv3 questions I was hoping someone could help me with.
>>
>> 1.  Is there any concept of an unnumbered interface in OSPFv3?  (As far as
> I
>> can see from RFC 2740, there isn't.)
>
> Since OSPFv3 runs on a link rather than a subnet, there should be fewer
> considerations.
>
>>
>> 2.  If yes, how do they work?  I would guess most principles from OSPFv2
> can
>> be carried over, but what about usage of the Link-LSA?
>
> It seems that it could be suppressed for unnumbered LSAs. In fact, it has
> crossed
> my mind that they could be suppressed for all OSPFv3 P2P links. At least in
> our
> implementation, we don't need to discover the link local address and any
> prefixes
> associated with the link are advertised in one of the router
> intra-area-prefix LSAs.
>
>
>>
>> 3.  If not, are there any guidelines on how, for example, RSVP tunnel
>> interfaces should be handled?
>
> I would think this would be transparent to OSPFv3.
>
>>
>> Thanks in advance,
>>
>> Nic


From owner-ospf@PEACH.EASE.LSOFT.COM  Tue Sep  7 11:50:00 2004
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 LAA02054
	for <ospf-archive@LISTS.IETF.ORG>; Tue, 7 Sep 2004 11:49:59 -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 <16.00E71AF2@cherry.ease.lsoft.com>; Tue, 7 Sep 2004 11:49:59 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 34343832 for OSPF@PEACH.EASE.LSOFT.COM;
          Tue, 7 Sep 2004 11:49:58 -0400
Received: from 169.144.68.6 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Tue, 7 Sep 2004 11:49:58 -0400
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com
          [169.144.2.12]) by mailgate.pit.comms.marconi.com
          (8.12.10+Sun/8.12.10) with ESMTP id i87FnvxX028922 for
          <OSPF@PEACH.EASE.LSOFT.COM>; Tue, 7 Sep 2004 11:49:57 -0400 (EDT)
Received: from uspitsmsgrtr01.pit.comms.marconi.com
          (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221]) by
          mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA06244
          for <OSPF@PEACH.EASE.LSOFT.COM>; Tue, 7 Sep 2004 11:49:57 -0400 (EDT)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service
          (5.5.2657.72) id <Q02X0R5Y>; Tue, 7 Sep 2004 11:49:57 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID:  <5551AD75D2C0BC459A85A2CEFAE4F800013009@usvissfp01.win.marconi.com>
Date:         Tue, 7 Sep 2004 11:49:56 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: "Naidu, Venkata" <Venkata.Naidu@MARCONI.COM>
Subject: Re: Unnumbered and tunnel interfaces in OSPFv3
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

-> > - For OSPFv3 purposes, an unnumbered interface is defined
-> as an interface
-> > with no link-local address (but possibly with site-local or global
-> > addresses).
->
-> It funny but I would have interpreted it to be just the
-> opposite - an interface
-> with a link-local address of one sort or another and no
-> site-local or global
-> addresses.
->
-> >
-> > - Any address on the corresponding node is used for the
-> source/destination
-> > address in protocol packets sent over unnumbered
-> interfaces (as in OSPFv2).
->
-> I don't agree here since I think there still should be a
-> link-local address.
->

  I agree with Acee here. Look at RFC 3513, IPv6 Addressing Architecture
  section 2.1 says:

  . . .

   All interfaces are required to have at least one link-local unicast
   address (see section 2.8 for additional required addresses).  A
   single interface may also have multiple IPv6 addresses of any type
   (unicast, anycast, and multicast) or scope.  Unicast addresses with
   scope greater than link-scope are not needed for interfaces that are
   not used as the origin or destination of any IPv6 packets to or from
   non-neighbors.  This is sometimes convenient for point-to-point
   interfaces.  There is one exception to this addressing model:

  . . .

  The concept of unnumbered is completely re-designed in IPv6. It is
  so beautifully designed using link-local addresses, in such a way that,
  it is generalized for all types of interfaces (point-to-point,
  broadcast etc) alike. Such a generalization is achieved using
  Neighbor Discovery (ND) protocol learning Layer 2 addresses more
  effectively than ARP. Previously, as in IPv4, unnumbered used to
  make sense for point-to-point links only.

  In one line, IPv6 link-local addresses does all the trick.
  There is no need for OSPFv3 to specify unnumbered using IfIndexes
  etc, as in IPv4. In fact, look at the below explanation of IPv4
  unnumbered history tied to OSPFv2, in Fred's words.
  http://www.cs-ipv6.lancs.ac.uk/ipv6/mail-archive/rip/1999-01/0005.html


Venkata.


From owner-ospf@PEACH.EASE.LSOFT.COM  Thu Sep  9 02:37:29 2004
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 CAA22434
	for <ospf-archive@LISTS.IETF.ORG>; Thu, 9 Sep 2004 02:37:29 -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 <3.00E750DF@cherry.ease.lsoft.com>; Thu, 9 Sep 2004 2:37:27 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 34608420 for OSPF@PEACH.EASE.LSOFT.COM;
          Thu, 9 Sep 2004 02:37:16 -0400
Received: from 61.144.161.40 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Thu, 9 Sep 2004 02:37:11 -0400
Received: from dell60 (huawei.com [172.17.1.62]) by mta0.huawei.com (iPlanet
          Messaging Server 5.2 HotFix 1.21 (built Sep  8 2003)) with ESMTPA id
          <0I3R00MVDFIL9C@mta0.huawei.com> for OSPF@PEACH.EASE.LSOFT.COM; Thu,
          09 Sep 2004 14:03:59 +0800 (CST)
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.4024
Content-type: multipart/alternative;
              boundary="Boundary_(ID_7mEnhye7fRz5MTMvm4Qrvw)"
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-imss-version: 2.7
X-imss-result: Passed
X-imss-approveListMatch: *@huawei.com
Message-ID:  <000001c49697$98cbaed0$cf04120a@dell60>
Date:         Thu, 9 Sep 2004 23:35:30 +0530
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: sujay <sujayg@HUAWEI.COM>
Subject: Any auto-route announce feature draft ?
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

This is a multi-part message in MIME format.

--Boundary_(ID_7mEnhye7fRz5MTMvm4Qrvw)
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7BIT

hi group,

Does anyone know if there are any drafts for the "auto-route announce"
(or also known as igp-shortcut)  feature available.

Thank you very much,

Sujay
HTIPL,
India

--Boundary_(ID_7mEnhye7fRz5MTMvm4Qrvw)
Content-type: text/html; charset=us-ascii
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=us-ascii">
<TITLE>Message</TITLE>

<META content="MSHTML 6.00.2800.1458" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=078180218-09092004><FONT face="Lucida Console" size=2><EM>hi
group,</EM></FONT></SPAN></DIV>
<DIV><SPAN class=078180218-09092004><EM><FONT face="Lucida Console"
size=2></FONT></EM></SPAN>&nbsp;</DIV>
<DIV><SPAN class=078180218-09092004><EM><FONT face="Lucida Console" size=2>Does
anyone know if there are any drafts for the "auto-route announce" (or also known
as igp-shortcut)&nbsp;&nbsp;feature available.</FONT></EM></SPAN></DIV>
<DIV><SPAN class=078180218-09092004><EM><FONT face="Lucida Console"
size=2></FONT></EM></SPAN>&nbsp;</DIV>
<DIV><SPAN class=078180218-09092004><EM><FONT face="Lucida Console" size=2>Thank
you very much,</FONT></EM></SPAN></DIV>
<DIV><SPAN class=078180218-09092004><EM><FONT face="Lucida Console"
size=2></FONT></EM></SPAN>&nbsp;</DIV>
<DIV><SPAN class=078180218-09092004><EM><FONT face="Lucida Console"
size=2>Sujay</FONT></EM></SPAN></DIV>
<DIV><SPAN class=078180218-09092004><EM><FONT face="Lucida Console"
size=2>HTIPL,</FONT></EM></SPAN></DIV>
<DIV><SPAN class=078180218-09092004><EM><FONT face="Lucida Console"
size=2>India</FONT></EM></SPAN></DIV></BODY></HTML>

--Boundary_(ID_7mEnhye7fRz5MTMvm4Qrvw)--


From owner-ospf@PEACH.EASE.LSOFT.COM  Thu Sep  9 09:41:39 2004
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 JAA19116
	for <ospf-archive@LISTS.IETF.ORG>; Thu, 9 Sep 2004 09:41: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 <13.00E75B59@cherry.ease.lsoft.com>; Thu, 9 Sep 2004 9:41:34 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 34679302 for OSPF@PEACH.EASE.LSOFT.COM;
          Thu, 9 Sep 2004 09:41:31 -0400
Received: from 169.144.68.6 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Thu, 9 Sep 2004 09:41:31 -0400
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com
          [169.144.2.12]) by mailgate.pit.comms.marconi.com
          (8.12.10+Sun/8.12.10) with ESMTP id i89DfWCn014866 for
          <OSPF@PEACH.EASE.LSOFT.COM>; Thu, 9 Sep 2004 09:41:32 -0400 (EDT)
Received: from uspitsmsgrtr01.pit.comms.marconi.com
          (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221]) by
          mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA12055
          for <OSPF@PEACH.EASE.LSOFT.COM>; Thu, 9 Sep 2004 09:41:31 -0400 (EDT)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service
          (5.5.2657.72) id <Q02YBXR8>; Thu, 9 Sep 2004 09:41:31 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID:  <5551AD75D2C0BC459A85A2CEFAE4F80001300E@usvissfp01.win.marconi.com>
Date:         Thu, 9 Sep 2004 09:41:30 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: "Naidu, Venkata" <Venkata.Naidu@MARCONI.COM>
Subject: Re: Any auto-route announce feature draft ?
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

-> Does anyone know if there are any drafts for the "auto-route announce"
-> (or also known as igp-shortcut)  feature available.

http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-igp-shortcut-01.txt

Venkata.


From owner-ospf@PEACH.EASE.LSOFT.COM  Fri Sep 10 10:40:13 2004
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 KAA02286
	for <ospf-archive@LISTS.IETF.ORG>; Fri, 10 Sep 2004 10:40:12 -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 <4.00E77C03@cherry.ease.lsoft.com>; Fri, 10 Sep 2004 10:40:12 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 34826749 for OSPF@PEACH.EASE.LSOFT.COM;
          Fri, 10 Sep 2004 10:40:09 -0400
Received: from 209.119.0.100 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Fri, 10 Sep 2004 10:30:08 -0400
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for
          Digital Unix v1.1b) with SMTP id <3.00E77B8E@cherry.ease.lsoft.com>;
          Fri, 10 Sep 2004 10:30:10 -0400
Received: from 61.144.161.40 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Fri, 10 Sep 2004 10:30:03 -0400
Received: from DE (huawei.com [172.17.1.62]) by mta0.huawei.com (iPlanet
          Messaging Server 5.2 HotFix 1.21 (built Sep  8 2003)) with ESMTPA id
          <0I3T008GKVEVNR@mta0.huawei.com> for OSPF@DISCUSS.MICROSOFT.COM; Fri,
          10 Sep 2004 21:42:32 +0800 (CST)
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.6626
Content-type: multipart/alternative;
              boundary="Boundary_(ID_Xc3JSLH+7D6JGM1EZy+bjQ)"
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-imss-version: 2.7
X-imss-result: Passed
X-imss-approveListMatch: *@huawei.com
Message-ID:  <001501c4973c$42879430$8704120a@DE>
Date:         Fri, 10 Sep 2004 19:14:13 +0530
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Santosh Esale <santosh_e@HUAWEI.COM>
Organization: HTIPL
Comments: To: OSPF@DISCUSS.MICROSOFT.COM
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

This is a multi-part message in MIME format.

--Boundary_(ID_Xc3JSLH+7D6JGM1EZy+bjQ)
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7BIT




--Boundary_(ID_Xc3JSLH+7D6JGM1EZy+bjQ)
Content-type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7BIT

<html>

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">


<meta name=Generator content="Microsoft Word 10 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {font-family:Arial;
        color:windowtext;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
        {page:Section1;}
-->
</style>

</head>

<body lang=ZH-CN link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=1 face=Arial><span lang=EN-US style='font-size:
9.0pt;font-family:Arial'>&nbsp;</span></font></p>

</div>

</body>

</html>

--Boundary_(ID_Xc3JSLH+7D6JGM1EZy+bjQ)--


From owner-ospf@PEACH.EASE.LSOFT.COM  Mon Sep 13 15:18:07 2004
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 PAA28444
	for <ospf-archive@LISTS.IETF.ORG>; Mon, 13 Sep 2004 15:18:07 -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 <18.00E7C9A3@cherry.ease.lsoft.com>; Mon, 13 Sep 2004 15:18:05 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 35296207 for OSPF@PEACH.EASE.LSOFT.COM;
          Mon, 13 Sep 2004 15:18:02 -0400
Received: from 64.233.170.193 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i)
          with TCP; Mon, 13 Sep 2004 15:18:02 -0400
Received: by mproxy.gmail.com with SMTP id 75so326380rnl for
          <ospf@peach.ease.lsoft.com>; Mon, 13 Sep 2004 12:18:03 -0700 (PDT)
Received: by 10.38.24.58 with SMTP id 58mr118838rnx; Mon, 13 Sep 2004 12:18:02
          -0700 (PDT)
Received: by 10.38.86.5 with HTTP; Mon, 13 Sep 2004 12:18:01 -0700 (PDT)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-ID:  <60fc97be04091312186fc628e0@mail.gmail.com>
Date:         Mon, 13 Sep 2004 12:18:01 -0700
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Sanjay BM <sanjaybm@GMAIL.COM>
Subject: OSPF graceful restart question
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

Hi,

RFC3623 Section 2.2, bullet item #2 says:

      2) Router X receives an LSA that is inconsistent with its pre-
         restart router-LSA.  For example, X receives a router-LSA
         originated by router Y that does not contain a link to X, even
         though X's pre-start router-LSA did contain a link to Y.  This
         indicates that either a) Y does not support graceful restart,
         b) Y never received the grace-LSA or c) Y has terminated its
         helper mode for some reason (Section 3.2).  A special case of
         LSA inconsistency is when Router X establishes an adjacency
         with router Y and doesn't receive an instance of its own pre-
         restart router LSA.


Is the opposite of this example also true? i.e, X receives a
router-LSA originated by router Y that contains a link to X, but X's
pre-start router-LSA does not contain a link to Y. This indicates that
router Y was cut-off from the network before router X entered graceful
restart and router Y's router-LSA has not yet max aged.

Should router X exit restart mode unsuccessfully for this above case?

Thanx,
Sanjay


From owner-ospf@PEACH.EASE.LSOFT.COM  Tue Sep 14 01:24:08 2004
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 BAA17180
	for <ospf-archive@LISTS.IETF.ORG>; Tue, 14 Sep 2004 01:24:08 -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 <15.00E7DA80@cherry.ease.lsoft.com>; Tue, 14 Sep 2004 1:24:06 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 35352416 for OSPF@PEACH.EASE.LSOFT.COM;
          Tue, 14 Sep 2004 01:24:04 -0400
Received: from 63.197.255.158 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i)
          with TCP; Tue, 14 Sep 2004 01:24:04 -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 graceful restart question
Thread-Index: AcSZxxyy6K9RnyGbQNSWh7n4bS7/DAAU47mQ
Message-ID:  <BB6D74C75CC76A419B6D6FA7C38317B23CE946@sinett-sbs.SiNett.LAN>
Date:         Mon, 13 Sep 2004 22:28:26 -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 graceful restart question
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: quoted-printable

Hi Sanjay,

Let me get to your question in a broader sense. Graceful Restart is used
to prevent as far as possible any packet loss when the control plane is
brought down. On the otherside, we get out of Graceful restart as soon
as we figure out that a loop could occur. So for any change which could
result in a loop in the network we should exit hitless restart. (Your
case included)

The RFC also states of future enhancements for even stricter checks to
prevent exiting graceful restart, as far as possible (hence utilizing
Graceful Restart to the fullest).=20

This is a reply to my mail from John Moy (way back in time)
http://peach.ease.lsoft.com/scripts/wa.exe?A2=3Dind0203&L=3Dospf&T=3D0&F=3D=
&S=3D&P
=3D1888 . I intend to publish this as a draft sometime to meet future
enhancements for Hitless Restart.

Thanks,
Vishwas

-----Original Message-----
From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM] On Behalf Of
Sanjay BM
Sent: Tuesday, September 14, 2004 12:48 AM
To: OSPF@PEACH.EASE.LSOFT.COM
Subject: OSPF graceful restart question

Hi,

RFC3623 Section 2.2, bullet item #2 says:

      2) Router X receives an LSA that is inconsistent with its pre-
         restart router-LSA.  For example, X receives a router-LSA
         originated by router Y that does not contain a link to X, even
         though X's pre-start router-LSA did contain a link to Y.  This
         indicates that either a) Y does not support graceful restart,
         b) Y never received the grace-LSA or c) Y has terminated its
         helper mode for some reason (Section 3.2).  A special case of
         LSA inconsistency is when Router X establishes an adjacency
         with router Y and doesn't receive an instance of its own pre-
         restart router LSA.


Is the opposite of this example also true? i.e, X receives a
router-LSA originated by router Y that contains a link to X, but X's
pre-start router-LSA does not contain a link to Y. This indicates that
router Y was cut-off from the network before router X entered graceful
restart and router Y's router-LSA has not yet max aged.

Should router X exit restart mode unsuccessfully for this above case?

Thanx,
Sanjay


From owner-ospf@PEACH.EASE.LSOFT.COM  Tue Sep 14 17:38:28 2004
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 RAA24079
	for <ospf-archive@LISTS.IETF.ORG>; Tue, 14 Sep 2004 17:38:28 -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 <8.00E7EDB8@cherry.ease.lsoft.com>; Tue, 14 Sep 2004 17:38:27 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 35481265 for OSPF@PEACH.EASE.LSOFT.COM;
          Tue, 14 Sep 2004 17:38:23 -0400
Received: from 64.233.170.199 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i)
          with TCP; Tue, 14 Sep 2004 17:38:23 -0400
Received: by mproxy.gmail.com with SMTP id 74so4730rnl for
          <ospf@peach.ease.lsoft.com>; Tue, 14 Sep 2004 14:38:24 -0700 (PDT)
Received: by 10.38.125.33 with SMTP id x33mr31572rnc; Tue, 14 Sep 2004 14:38:24
          -0700 (PDT)
Received: by 10.38.86.46 with HTTP; Tue, 14 Sep 2004 14:38:24 -0700 (PDT)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <BB6D74C75CC76A419B6D6FA7C38317B23CE946@sinett-sbs.SiNett.LAN>
Message-ID:  <60fc97be0409141438601c700c@mail.gmail.com>
Date:         Tue, 14 Sep 2004 14:38:24 -0700
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Sanjay BM <sanjaybm@GMAIL.COM>
Subject: Re: OSPF graceful restart question
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To:  <BB6D74C75CC76A419B6D6FA7C38317B23CE946@sinett-sbs.SiNett.LAN>
Precedence: list
Content-Transfer-Encoding: 7bit

Hi Vishwas,

I was wondering how could there be a loop in the case I mentioned?
Assume the following network:

  Router-D ------ Router-A ------ Router-B -------- Router-C

Router-D is a backbone router, Router-A is an ABR, Router-B and
Router-C are in area 2. There is a virtual-link from Router-A to
Router-C.

Suppose Router-C went down for some reason, we would have its area 0
Router-LSA in the database of Router-A and Router-D till it ages out.
Note that at this point Router-A has removed the virtual-link from its
area 0 Router-LSA.

Before Router-C's area 0 Router-LSA ages out, if Router-A enters OSPF
graceful restart, then Router-D as a helper will eventually send
Router-C's area 0 Router-LSA to Router-A.

My questions is: Should Router-A consider this as a LSA inconsistency
and hence exit the restart mode unsuccessfully?

Would the following be a wrong thing to do?
      If Router-A looks at its own pre-start area 0 router-LSA, it
will find that there is no virtual-link in it. Hence Router-A should
not consider Router-C's area 0 Router-LSA as a inconsistency. Thereby,
Router-A should not exit restart mode unsuccessfully.

Kindly let me know.

Thanx,
Sanjay

On Mon, 13 Sep 2004 22:28:26 -0700, Vishwas Manral <vishwas@sinett.com> wrote:
> Hi Sanjay,
>
> Let me get to your question in a broader sense. Graceful Restart is used
> to prevent as far as possible any packet loss when the control plane is
> brought down. On the otherside, we get out of Graceful restart as soon
> as we figure out that a loop could occur. So for any change which could
> result in a loop in the network we should exit hitless restart. (Your
> case included)
>
> The RFC also states of future enhancements for even stricter checks to
> prevent exiting graceful restart, as far as possible (hence utilizing
> Graceful Restart to the fullest).
>
> This is a reply to my mail from John Moy (way back in time)
> http://peach.ease.lsoft.com/scripts/wa.exe?A2=ind0203&L=ospf&T=0&F=&S=&P
> =1888 . I intend to publish this as a draft sometime to meet future
> enhancements for Hitless Restart.
>
> Thanks,
> Vishwas
>
>
>
> -----Original Message-----
> From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM] On Behalf Of
> Sanjay BM
> Sent: Tuesday, September 14, 2004 12:48 AM
> To: OSPF@PEACH.EASE.LSOFT.COM
> Subject: OSPF graceful restart question
>
> Hi,
>
> RFC3623 Section 2.2, bullet item #2 says:
>
>      2) Router X receives an LSA that is inconsistent with its pre-
>         restart router-LSA.  For example, X receives a router-LSA
>         originated by router Y that does not contain a link to X, even
>         though X's pre-start router-LSA did contain a link to Y.  This
>         indicates that either a) Y does not support graceful restart,
>         b) Y never received the grace-LSA or c) Y has terminated its
>         helper mode for some reason (Section 3.2).  A special case of
>         LSA inconsistency is when Router X establishes an adjacency
>         with router Y and doesn't receive an instance of its own pre-
>         restart router LSA.
>
> Is the opposite of this example also true? i.e, X receives a
> router-LSA originated by router Y that contains a link to X, but X's
> pre-start router-LSA does not contain a link to Y. This indicates that
> router Y was cut-off from the network before router X entered graceful
> restart and router Y's router-LSA has not yet max aged.
>
> Should router X exit restart mode unsuccessfully for this above case?
>
> Thanx,
> Sanjay
>


From owner-ospf@PEACH.EASE.LSOFT.COM  Mon Sep 20 18:18:12 2004
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 SAA28838
	for <ospf-archive@LISTS.IETF.ORG>; Mon, 20 Sep 2004 18:18:12 -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 <6.00E8907F@cherry.ease.lsoft.com>; Mon, 20 Sep 2004 18:18:10 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 36436526 for OSPF@PEACH.EASE.LSOFT.COM;
          Mon, 20 Sep 2004 18:18:06 -0400
Received: from 132.151.6.71 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Mon, 20 Sep 2004 18:08:06 -0400
Received: from apache by megatron.ietf.org with local (Exim 4.32) id
          1C9WEZ-0006DM-Sv; Mon, 20 Sep 2004 18:02:07 -0400
X-test-idtracker: no
Message-ID:  <E1C9WEZ-0006DM-Sv@megatron.ietf.org>
Date:         Mon, 20 Sep 2004 18:02:07 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: The IESG <iesg-secretary@ietf.org>
Subject: Document Action: 'OSPF Refresh and Flooding Reduction in Stable Topologies' to Informational RFC
Comments: To: IETF-Announce <ietf-announce@ietf.org>
Comments: cc: Internet Architecture Board <iab@iab.org>,
          RFC Editor <rfc-editor@rfc-editor.org>,
          ospf chair <acee@redback.com>, ospf chair <rohit@utstar.com>
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

The IESG has approved the following document:

- 'OSPF Refresh and Flooding Reduction in Stable Topologies '
   <draft-pillay-esnault-ospf-flooding-07.txt> as an Informational RFC

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

The IESG contact persons are Bill Fenner and Alex Zinin.

Technical Summary

   This document describes an extension to the OSPF protocol to
   reduce periodic flooding of Link State Advertisements in
   stable topologies.  It generalizes the use of DoNotAge LSAs
   (originally used only in dial-on-demand configurations) to
   reduce or eliminate refreshing of unchanging topology information.

Working Group Summary

   The working group had consensus to publish this specification.

Protocol Quality

   Bill Fenner and Alex Zinin reviewed this spec for the IESG.

RFC Editor's Note:

Please replace section 6 with the standard IPR text from
section 5 of RFC3668.


From owner-ospf@PEACH.EASE.LSOFT.COM  Tue Sep 21 02:20:36 2004
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 CAA14144
	for <ospf-archive@LISTS.IETF.ORG>; Tue, 21 Sep 2004 02:20:36 -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 <7.00E89AE0@cherry.ease.lsoft.com>; Tue, 21 Sep 2004 2:20:34 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 36482731 for OSPF@PEACH.EASE.LSOFT.COM;
          Tue, 21 Sep 2004 02:20:31 -0400
Received: from 209.119.0.100 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Tue, 21 Sep 2004 02:20:31 -0400
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for
          Digital Unix v1.1b) with SMTP id <22.00E89AAC@cherry.ease.lsoft.com>;
          Tue, 21 Sep 2004 2:20:32 -0400
Received: from 61.144.161.41 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Tue, 21 Sep 2004 02:20:24 -0400
Received: from DE (mta1.huawei.com [172.17.1.60]) by mta1.huawei.com (iPlanet
          Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) with ESMTPA id
          <0I4D00FBSLHEB5@mta1.huawei.com> for OSPF@DISCUSS.MICROSOFT.COM; Tue,
          21 Sep 2004 13:20:04 +0800 (CST)
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.6626
Content-type: multipart/alternative;
              boundary="Boundary_(ID_tFZCJ+mPIkaZ+bEaQpZaSA)"
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-imss-version: 2.7
X-imss-result: Passed
X-imss-approveListMatch: *@huawei.com
Message-ID:  <000401c49f9c$7c418600$8704120a@DE>
Date:         Tue, 21 Sep 2004 11:03:10 +0530
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Santosh Esale <santosh_e@HUAWEI.COM>
Organization: HTIPL
Subject: OSPFv3 and Cost configured on loopback interface
Comments: To: OSPF@DISCUSS.MICROSOFT.COM
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

This is a multi-part message in MIME format.

--Boundary_(ID_tFZCJ+mPIkaZ+bEaQpZaSA)
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7BIT

Hi ,

     I was reading the RFC 2740 and had a question regarding the setting of
cost for ospfv3 routes configured on loopback interface.



RFC 2740section 3.4.3.7. says -

RTX adds the IPv6 prefixes for any directly attached hosts

      belonging to the area (see Section C.7) to the intra-area-prefix-

      LSA



   o  If RTX has one or more virtual links configured through the area,

      it includes one of its site-local or global scope IPv6 interface

      addresses in the LSA (if it hasn't already), setting the LA-bit in

      the PrefixOptions field, and setting the PrefixLength to 128 and

      the Metric to 0. This information will be used later in the

      routing calculation so that the two ends of the virtual link can

      discover each other's IPv6 addresses.



Now if I have configured ipv6 global address on loopback interface  and this
router has only p2p links to transit area , Then we need to orginate
intra-prefix LSA for this loopback address with LA bit set and cost set to 0
.

so does it mean the cost configured on loopback interface should not be used
while advertising in intra-prefix LSA and downloading the route to RIB??



Thanks in advance

santosh


--Boundary_(ID_tFZCJ+mPIkaZ+bEaQpZaSA)
Content-type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7BIT

<html>

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">


<meta name=Generator content="Microsoft Word 10 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {font-family:Arial;
        color:windowtext;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
        {page:Section1;}
-->
</style>

</head>

<body lang=ZH-CN link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=1 face=Arial><span lang=EN-US style='font-size:
9.0pt;font-family:Arial'>Hi ,</span></font></p>

<p class=MsoNormal><font size=1 face=Arial><span lang=EN-US style='font-size:
9.0pt;font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp; </span></font><em><i><font
size=2 face=Arial><span lang=EN-US style='font-size:10.0pt;font-family:Arial'>I
was reading the RFC 2740 and had a question </span></font></i></em><font
size=2 face=Arial><span lang=EN-US style='font-size:10.0pt;font-family:Arial'>regarding<em><i><font
face=Arial><span style='font-family:Arial'> the setting of cost for ospfv3 routes
configured on loopback interface.</span></font></i></em></span></font></p>

<p class=MsoNormal><em><i><font size=2 face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></i></em></p>

<p class=MsoNormal><em><i><font size=2 face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial'>RFC 2740section </span></font></i></em><b><font
size=2 color="#000032" face="Courier New"><span lang=EN-US style='font-size:
10.0pt;font-family:"Courier New";color:#000032;font-weight:bold'>3.4.3.7.</span></font></b><em><i><font
size=2 face=Arial><span lang=EN-US style='font-size:10.0pt;font-family:Arial'>
says &#8211;</span></font></i></em></p>

<p class=MsoNormal style='text-indent:35.0pt;text-autospace:none'><font size=2
color=black face="Courier New"><span lang=EN-US style='font-size:10.0pt;
font-family:"Courier New";color:black'>RTX adds the IPv6 prefixes for any
directly attached hosts</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; belonging to the area (see Section
C.7) to the intra-area-prefix-</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></font><font size=2
color=black face="Courier New"><span lang=FR style='font-size:10.0pt;
font-family:"Courier New";color:black'>LSA</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black'>&nbsp;</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black'>&nbsp;&nbsp; o&nbsp; If RTX has one or more virtual links
configured through the area,</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; it includes one of its site-local
or global scope IPv6 interface</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; addresses in the LSA (if it hasn't
already), setting the LA-bit in</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the PrefixOptions field, and
setting the PrefixLength to 128 and</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the Metric to 0. This information
will be used later in the</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; routing calculation so that the two
ends of the virtual link can</span></font></p>

<p class=MsoNormal style='text-autospace:none'><font size=2 color=black
face="Courier New"><span lang=EN-US style='font-size:10.0pt;font-family:"Courier New";
color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; discover each other's IPv6
addresses.</span></font></p>

<p class=MsoNormal><font size=1 face=Arial><span lang=EN-US style='font-size:
9.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=1 face=Arial><span lang=EN-US style='font-size:
9.0pt;font-family:Arial'>Now if I have configured ipv6 global address on
loopback interface&nbsp; and this router has only p2p links to transit area ,
Then we need to orginate intra-prefix LSA for this loopback address with LA bit
set and cost set to 0 .</span></font></p>

<p class=MsoNormal><font size=1 face=Arial><span lang=EN-US style='font-size:
9.0pt;font-family:Arial'>so does it mean the cost configured on loopback interface
should not be used while advertising in intra-prefix LSA and downloading the
route to RIB??</span></font></p>

<p class=MsoNormal><font size=1 face=Arial><span lang=EN-US style='font-size:
9.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=1 face=Arial><span lang=EN-US style='font-size:
9.0pt;font-family:Arial'>Thanks in advance </span></font></p>

<p class=MsoNormal><font size=1 face=Arial><span lang=EN-US style='font-size:
9.0pt;font-family:Arial'>santosh</span></font></p>

</div>

</body>

</html>

--Boundary_(ID_tFZCJ+mPIkaZ+bEaQpZaSA)--


From owner-ospf@PEACH.EASE.LSOFT.COM  Tue Sep 21 09:08:53 2004
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 JAA11895
	for <ospf-archive@LISTS.IETF.ORG>; Tue, 21 Sep 2004 09:08:52 -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 <5.00E8A0A8@cherry.ease.lsoft.com>; Tue, 21 Sep 2004 9:08:51 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 36544041 for OSPF@PEACH.EASE.LSOFT.COM;
          Tue, 21 Sep 2004 09:08:48 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Tue, 21 Sep 2004 09:08:48 -0400
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com
          (Postfix) with ESMTP id E29B0BACF1 for <OSPF@PEACH.EASE.LSOFT.COM>;
          Tue, 21 Sep 2004 06:08:48 -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 23152-08 for 
          <OSPF@PEACH.EASE.LSOFT.COM>; Tue, 21 Sep 2004 06:08:48 -0700 (PDT)
Received: from aceeinspiron (unknown [172.31.253.41]) by prattle.redback.com
          (Postfix) with SMTP id CAC21BACE4 for <OSPF@PEACH.EASE.LSOFT.COM>;
          Tue, 21 Sep 2004 06:08:47 -0700 (PDT)
References:  <000401c49f9c$7c418600$8704120a@DE>
MIME-Version: 1.0
Content-Type: multipart/alternative;
              boundary="----=_NextPart_000_0021_01C49FBA.8FA7F8A0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Virus-Scanned: by amavisd-new at redback.com
Message-ID:  <002401c49fdc$17218230$0202a8c0@aceeinspiron>
Date:         Tue, 21 Sep 2004 09:08:29 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Re: OSPFv3 and Cost configured on loopback interface
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

This is a multi-part message in MIME format.

------=_NextPart_000_0021_01C49FBA.8FA7F8A0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Santosh,

Functionally, I don't see any problem with allowing a loopback cost to =
be configurable.
In fact, my implementation allows this.=20

Hope this helps,=20
Acee
  ----- Original Message -----=20
  From: Santosh Esale=20
  To: OSPF@PEACH.EASE.LSOFT.COM=20
  Sent: Tuesday, September 21, 2004 1:33 AM
  Subject: OSPFv3 and Cost configured on loopback interface


  Hi ,

       I was reading the RFC 2740 and had a question regarding the =
setting of cost for ospfv3 routes configured on loopback interface.



  RFC 2740section 3.4.3.7. says -

  RTX adds the IPv6 prefixes for any directly attached hosts

        belonging to the area (see Section C.7) to the =
intra-area-prefix-

        LSA



     o  If RTX has one or more virtual links configured through the =
area,

        it includes one of its site-local or global scope IPv6 interface

        addresses in the LSA (if it hasn't already), setting the LA-bit =
in

        the PrefixOptions field, and setting the PrefixLength to 128 and

        the Metric to 0. This information will be used later in the

        routing calculation so that the two ends of the virtual link can

        discover each other's IPv6 addresses.



  Now if I have configured ipv6 global address on loopback interface  =
and this router has only p2p links to transit area , Then we need to =
orginate intra-prefix LSA for this loopback address with LA bit set and =
cost set to 0 .

  so does it mean the cost configured on loopback interface should not =
be used while advertising in intra-prefix LSA and downloading the route =
to RIB??



  Thanks in advance=20

  santosh

------=_NextPart_000_0021_01C49FBA.8FA7F8A0
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">
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR>
<STYLE>@font-face {
        font-family: SimSun;
}
@font-face {
        font-family: SimSun;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
        COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
        COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
        COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
        COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
        COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
        page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DZH-CN vLink=3Dpurple link=3Dblue bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi Santosh,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Functionally, I don't see any problem =
with allowing=20
a loopback cost to be configurable.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>In fact, my implementation allows this. =

</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Hope this helps, </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Acee</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dsantosh_e@HUAWEI.COM =
href=3D"mailto:santosh_e@HUAWEI.COM">Santosh=20
  Esale</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3DOSPF@PEACH.EASE.LSOFT.COM=20
  =
href=3D"mailto:OSPF@PEACH.EASE.LSOFT.COM">OSPF@PEACH.EASE.LSOFT.COM</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, September 21, =
2004 1:33=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> OSPFv3 and Cost =
configured on=20
  loopback interface</DIV>
  <DIV><BR></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">Hi ,</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN></FONT><EM><I><FONT face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I was reading the RFC =
2740 and had=20
  a question </SPAN></FONT></I></EM><FONT face=3DArial size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">regarding<EM><I><FONT=20
  face=3DArial><SPAN style=3D"FONT-FAMILY: Arial"> the setting of cost =
for ospfv3=20
  routes configured on loopback=20
  interface.</SPAN></FONT></I></EM></SPAN></FONT></P>
  <P class=3DMsoNormal><EM><I><FONT face=3DArial size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"></SPAN></FONT></I></EM>&nbsp;</P>
  <P class=3DMsoNormal><EM><I><FONT face=3DArial size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">RFC 2740section=20
  </SPAN></FONT></I></EM><B><FONT face=3D"Courier New" color=3D#000032 =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #000032; =
FONT-FAMILY: 'Courier New'">3.4.3.7.</SPAN></FONT></B><EM><I><FONT=20
  face=3DArial size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"> says =
=96</SPAN></FONT></I></EM></P>
  <P class=3DMsoNormal style=3D"TEXT-INDENT: 35pt"><FONT face=3D"Courier =
New"=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">RTX adds the=20
  IPv6 prefixes for any directly attached hosts</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" color=3Dblack =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  belonging to the area (see Section C.7) to the=20
  intra-area-prefix-</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" color=3Dblack =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN></FONT><FONT face=3D"Courier New" color=3Dblack size=3D2><SPAN =
lang=3DFR=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">LSA</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" color=3Dblack =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" color=3Dblack =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">&nbsp;&nbsp;=20
  o&nbsp; If RTX has one or more virtual links configured through the=20
  area,</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" color=3Dblack =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  it includes one of its site-local or global scope IPv6=20
  interface</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" color=3Dblack =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  addresses in the LSA (if it hasn't already), setting the LA-bit=20
  in</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" color=3Dblack =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  the PrefixOptions field, and setting the PrefixLength to 128=20
  and</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" color=3Dblack =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  the Metric to 0. This information will be used later in =
the</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" color=3Dblack =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  routing calculation so that the two ends of the virtual link=20
  can</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" color=3Dblack =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  discover each other's IPv6 addresses.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">Now if I have configured =
ipv6=20
  global address on loopback interface&nbsp; and this router has only =
p2p links=20
  to transit area , Then we need to orginate intra-prefix LSA for this =
loopback=20
  address with LA bit set and cost set to 0 .</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">so does it mean the cost =
configured=20
  on loopback interface should not be used while advertising in =
intra-prefix LSA=20
  and downloading the route to RIB??</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">Thanks in advance=20
</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; FONT-FAMILY: =
Arial">santosh</SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0021_01C49FBA.8FA7F8A0--


From owner-ospf@PEACH.EASE.LSOFT.COM  Tue Sep 21 12:29:30 2004
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 MAA29415
	for <ospf-archive@LISTS.IETF.ORG>; Tue, 21 Sep 2004 12:29:30 -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 <4.00E8A5DB@cherry.ease.lsoft.com>; Tue, 21 Sep 2004 12:29:30 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 36559708 for OSPF@PEACH.EASE.LSOFT.COM;
          Tue, 21 Sep 2004 12:29:29 -0400
Received: from 192.91.191.4 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Tue, 21 Sep 2004 12:29:28 -0400
Received: by goodman.datcon.co.uk with Internet Mail Service (5.5.2657.72) id
          <R0RAXNVK>; Tue, 21 Sep 2004 17:29:28 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID:  <53F74F5A7B94D511841C00B0D0AB16F802870B2E@baker.datcon.co.uk>
Date:         Tue, 21 Sep 2004 17:29:20 +0100
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Nic Neate <Nic.Neate@DATACONNECTION.COM>
Subject: Re: OSPF-V3 Instance ID
Comments: To: "acee@redback.com" <acee@redback.com>,
          "djoyal@nortelnetworks.com" <djoyal@nortelnetworks.com>,
          "vishwas@sinett.com" <vishwas@sinett.com>
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

Guys,

Acee indicated below that the ospfv3IfTable should be indexed by both
ospfv3IfIndex and ospfv3InstId.

I think it follows that the ospfv3NbrTable, ospfv3NbmaNbrTable and
ospfv3LinkLsdbTable (which are all currently indexed on their interface
index) also need new interface instance index fields.  Is that right?

Incidentally, I notice that draft-ietf-ospf-ospfv3-mib-08 expired in April.
Are there plans to make updates and refresh it?

Thanks,

Nic


-----Original Message-----
From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM]On Behalf Of Acee
Lindem
Sent: Friday, July 09, 2004 4:15 AM
To: OSPF@PEACH.EASE.LSOFT.COM
Subject: Re: OSPF-V3 Instance ID


Hi Dilip,

----- Original Message -----
From: "Dilip Kumar" <dilipks@GMAIL.COM>
To: <OSPF@PEACH.EASE.LSOFT.COM>
Sent: Thursday, July 08, 2004 10:37 PM
Subject: OSPF-V3 Instance ID


> Hello,
>     I have couple of doubts w.r.to OSPF-V3's Instance ID interpretation
> 1. Can one router interface have more than one "Instance ID"
> configured simultaneously ?

Yes.  However,  there may be implementations that only support one to
be configured.

> OSPF-V3 MIB draft (draft-ietf-ospf-ospfv3-mib-08) indicates that it is
> not possible.

This is wrong. ospfv3IfTable should be indexed by both ospfv3IfIndex
and ospfv3InstId.


> However, RFC-2740 indirectly points that it is possible.
> Following is the excerpt from the RFC-2740
>
>   "Another use for running multiple OSPF instances is if you want, for
>    one reason or another, to have a single link belong to two or more
>    OSPF areas."

This is one application of multiple instance IDs.

>
> 2. Can LSAs received from a neighbor 'A' which has instance ID=2 be
> flooded to another neighbor B that has instance ID=5 ?
>
>        InstanceID=2                  InstanceID=5
> A=================R================B

The base OSPFv3 specification (RFC 2740) certainly doesn't preclude this
since the interface instance ID only has significance for that interface.
In case of draft-mirtorabi-ospf-multi-area-adj-00.txt, the instance ID has
significance beyond the scope of the interface and you would not.

Hope this helps,
Acee

>
>
> Thanks in advance for any help.
> -- Dilip


From owner-ospf@PEACH.EASE.LSOFT.COM  Tue Sep 21 12:43:27 2004
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 MAA00692
	for <ospf-archive@LISTS.IETF.ORG>; Tue, 21 Sep 2004 12:43:26 -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 <17.00E8A6DF@cherry.ease.lsoft.com>; Tue, 21 Sep 2004 12:43:27 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 36561242 for OSPF@PEACH.EASE.LSOFT.COM;
          Tue, 21 Sep 2004 12:43:26 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Tue, 21 Sep 2004 12:43:25 -0400
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com
          (Postfix) with ESMTP id E7F9678A047 for <OSPF@PEACH.EASE.LSOFT.COM>;
          Tue, 21 Sep 2004 09:43:22 -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 11645-02 for 
          <OSPF@PEACH.EASE.LSOFT.COM>; Tue, 21 Sep 2004 09:43:22 -0700 (PDT)
Received: from aceeinspiron (unknown [172.31.253.41]) by prattle.redback.com
          (Postfix) with SMTP id 0DEFA78A048 for <OSPF@PEACH.EASE.LSOFT.COM>;
          Tue, 21 Sep 2004 09:43:20 -0700 (PDT)
References: <53F74F5A7B94D511841C00B0D0AB16F802870B2E@baker.datcon.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
              reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Virus-Scanned: by amavisd-new at redback.com
Message-ID:  <00ae01c49ffa$0ff43700$0202a8c0@aceeinspiron>
Date:         Tue, 21 Sep 2004 12:43:02 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Re: OSPF-V3 Instance ID
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

----- Original Message -----
From: "Nic Neate" <Nic.Neate@dataconnection.com>
To: "'Mailing List'" <OSPF@PEACH.EASE.LSOFT.COM>; <acee@redback.com>; <djoyal@nortelnetworks.com>; <vishwas@sinett.com>
Sent: Tuesday, September 21, 2004 12:29 PM
Subject: RE: OSPF-V3 Instance ID


> Guys,
>
> Acee indicated below that the ospfv3IfTable should be indexed by both
> ospfv3IfIndex and ospfv3InstId.
>
> I think it follows that the ospfv3NbrTable, ospfv3NbmaNbrTable and
> ospfv3LinkLsdbTable (which are all currently indexed on their interface
> index) also need new interface instance index fields.  Is that right?

Hi Nic,
I would think so.
Thanks,
Acee
>
> Incidentally, I notice that draft-ietf-ospf-ospfv3-mib-08 expired in April.
> Are there plans to make updates and refresh it?
>
> Thanks,
>
> Nic
>
>
> -----Original Message-----
> From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM]On Behalf Of Acee
> Lindem
> Sent: Friday, July 09, 2004 4:15 AM
> To: OSPF@PEACH.EASE.LSOFT.COM
> Subject: Re: OSPF-V3 Instance ID
>
>
> Hi Dilip,
>
> ----- Original Message -----
> From: "Dilip Kumar" <dilipks@GMAIL.COM>
> To: <OSPF@PEACH.EASE.LSOFT.COM>
> Sent: Thursday, July 08, 2004 10:37 PM
> Subject: OSPF-V3 Instance ID
>
>
>> Hello,
>>     I have couple of doubts w.r.to OSPF-V3's Instance ID interpretation
>> 1. Can one router interface have more than one "Instance ID"
>> configured simultaneously ?
>
> Yes.  However,  there may be implementations that only support one to
> be configured.
>
>> OSPF-V3 MIB draft (draft-ietf-ospf-ospfv3-mib-08) indicates that it is
>> not possible.
>
> This is wrong. ospfv3IfTable should be indexed by both ospfv3IfIndex
> and ospfv3InstId.
>
>
>> However, RFC-2740 indirectly points that it is possible.
>> Following is the excerpt from the RFC-2740
>>
>>   "Another use for running multiple OSPF instances is if you want, for
>>    one reason or another, to have a single link belong to two or more
>>    OSPF areas."
>
> This is one application of multiple instance IDs.
>
>>
>> 2. Can LSAs received from a neighbor 'A' which has instance ID=2 be
>> flooded to another neighbor B that has instance ID=5 ?
>>
>>        InstanceID=2                  InstanceID=5
>> A=================R================B
>
> The base OSPFv3 specification (RFC 2740) certainly doesn't preclude this
> since the interface instance ID only has significance for that interface.
> In case of draft-mirtorabi-ospf-multi-area-adj-00.txt, the instance ID has
> significance beyond the scope of the interface and you would not.
>
> Hope this helps,
> Acee
>
>>
>>
>> Thanks in advance for any help.
>> -- Dilip


From owner-ospf@PEACH.EASE.LSOFT.COM  Tue Sep 21 13:55:53 2004
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 NAA05903
	for <ospf-archive@LISTS.IETF.ORG>; Tue, 21 Sep 2004 13:55:52 -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 <13.00E8A873@cherry.ease.lsoft.com>; Tue, 21 Sep 2004 13:55:50 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 36570634 for OSPF@PEACH.EASE.LSOFT.COM;
          Tue, 21 Sep 2004 13:55:49 -0400
Received: from 63.197.255.158 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i)
          with TCP; Tue, 21 Sep 2004 13:55:48 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C4A004.F7C83CE8"
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: OSPF-V3 Instance ID
Thread-Index: AcSf+Ouy2ao3d+3QQXCH6HEsRM4PiAAC9yfm
Message-ID:  <BB6D74C75CC76A419B6D6FA7C38317B207EA03@sinett-sbs.SiNett.LAN>
Date:         Tue, 21 Sep 2004 10:59:47 -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-V3 Instance ID
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4A004.F7C83CE8
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Nic,
=20
I think the draft was posted in April so should expire in October.=20
=20
Yes, we will refresh the draft and take care of all comments that we =
have got.
=20
Thanks,
Vishwas

________________________________

From: Mailing List on behalf of Nic Neate
Sent: Tue 9/21/2004 9:29 AM
To: OSPF@PEACH.EASE.LSOFT.COM
Subject: Re: OSPF-V3 Instance ID



Guys,

Acee indicated below that the ospfv3IfTable should be indexed by both
ospfv3IfIndex and ospfv3InstId.

I think it follows that the ospfv3NbrTable, ospfv3NbmaNbrTable and
ospfv3LinkLsdbTable (which are all currently indexed on their interface
index) also need new interface instance index fields.  Is that right?

Incidentally, I notice that draft-ietf-ospf-ospfv3-mib-08 expired in =
April.
Are there plans to make updates and refresh it?

Thanks,

Nic


-----Original Message-----
From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM]On Behalf Of Acee
Lindem
Sent: Friday, July 09, 2004 4:15 AM
To: OSPF@PEACH.EASE.LSOFT.COM
Subject: Re: OSPF-V3 Instance ID


Hi Dilip,

----- Original Message -----
From: "Dilip Kumar" <dilipks@GMAIL.COM>
To: <OSPF@PEACH.EASE.LSOFT.COM>
Sent: Thursday, July 08, 2004 10:37 PM
Subject: OSPF-V3 Instance ID


> Hello,
>     I have couple of doubts w.r.to OSPF-V3's Instance ID =
interpretation
> 1. Can one router interface have more than one "Instance ID"
> configured simultaneously ?

Yes.  However,  there may be implementations that only support one to
be configured.

> OSPF-V3 MIB draft (draft-ietf-ospf-ospfv3-mib-08) indicates that it is
> not possible.

This is wrong. ospfv3IfTable should be indexed by both ospfv3IfIndex
and ospfv3InstId.


> However, RFC-2740 indirectly points that it is possible.
> Following is the excerpt from the RFC-2740
>
>   "Another use for running multiple OSPF instances is if you want, for
>    one reason or another, to have a single link belong to two or more
>    OSPF areas."

This is one application of multiple instance IDs.

>
> 2. Can LSAs received from a neighbor 'A' which has instance ID=3D2 be
> flooded to another neighbor B that has instance ID=3D5 ?
>
>        InstanceID=3D2                  InstanceID=3D5
> =
A=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DR=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3DB

The base OSPFv3 specification (RFC 2740) certainly doesn't preclude this
since the interface instance ID only has significance for that =
interface.
In case of draft-mirtorabi-ospf-multi-area-adj-00.txt, the instance ID =
has
significance beyond the scope of the interface and you would not.

Hope this helps,
Acee

>
>
> Thanks in advance for any help.
> -- Dilip



------_=_NextPart_001_01C4A004.F7C83CE8
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">=0A=
<HTML>=0A=
<HEAD>=0A=
=0A=
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.6944.0">=0A=
<TITLE>Re: OSPF-V3 Instance ID</TITLE>=0A=
</HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText83171 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Hi =
Nic,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>I think the draft was posted =
in April so =0A=
should expire in October. </FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Yes, we will refresh the =
draft and take =0A=
care of all comments that we have got.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Vishwas</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Mailing List on behalf of Nic =0A=
Neate<BR><B>Sent:</B> Tue 9/21/2004 9:29 AM<BR><B>To:</B> =0A=
OSPF@PEACH.EASE.LSOFT.COM<BR><B>Subject:</B> Re: OSPF-V3 Instance =0A=
ID<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Guys,<BR><BR>Acee indicated below that the =
ospfv3IfTable should =0A=
be indexed by both<BR>ospfv3IfIndex and ospfv3InstId.<BR><BR>I think it =
follows =0A=
that the ospfv3NbrTable, ospfv3NbmaNbrTable and<BR>ospfv3LinkLsdbTable =
(which =0A=
are all currently indexed on their interface<BR>index) also need new =
interface =0A=
instance index fields.&nbsp; Is that right?<BR><BR>Incidentally, I =
notice that =0A=
draft-ietf-ospf-ospfv3-mib-08 expired in April.<BR>Are there plans to =
make =0A=
updates and refresh =
it?<BR><BR>Thanks,<BR><BR>Nic<BR><BR><BR>-----Original =0A=
Message-----<BR>From: Mailing List [<A =0A=
href=3D"mailto:OSPF@PEACH.EASE.LSOFT.COM">mailto:OSPF@PEACH.EASE.LSOFT.CO=
M</A>]On =0A=
Behalf Of Acee<BR>Lindem<BR>Sent: Friday, July 09, 2004 4:15 AM<BR>To: =0A=
OSPF@PEACH.EASE.LSOFT.COM<BR>Subject: Re: OSPF-V3 Instance =
ID<BR><BR><BR>Hi =0A=
Dilip,<BR><BR>----- Original Message -----<BR>From: "Dilip Kumar" =0A=
&lt;dilipks@GMAIL.COM&gt;<BR>To: =
&lt;OSPF@PEACH.EASE.LSOFT.COM&gt;<BR>Sent: =0A=
Thursday, July 08, 2004 10:37 PM<BR>Subject: OSPF-V3 Instance =
ID<BR><BR><BR>&gt; =0A=
Hello,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; I have couple of doubts w.r.to =
OSPF-V3's =0A=
Instance ID interpretation<BR>&gt; 1. Can one router interface have more =
than =0A=
one "Instance ID"<BR>&gt; configured simultaneously ?<BR><BR>Yes.&nbsp; =0A=
However,&nbsp; there may be implementations that only support one =
to<BR>be =0A=
configured.<BR><BR>&gt; OSPF-V3 MIB draft =
(draft-ietf-ospf-ospfv3-mib-08) =0A=
indicates that it is<BR>&gt; not possible.<BR><BR>This is wrong. =
ospfv3IfTable =0A=
should be indexed by both ospfv3IfIndex<BR>and =
ospfv3InstId.<BR><BR><BR>&gt; =0A=
However, RFC-2740 indirectly points that it is possible.<BR>&gt; =
Following is =0A=
the excerpt from the RFC-2740<BR>&gt;<BR>&gt;&nbsp;&nbsp; "Another use =
for =0A=
running multiple OSPF instances is if you want, =
for<BR>&gt;&nbsp;&nbsp;&nbsp; =0A=
one reason or another, to have a single link belong to two or =0A=
more<BR>&gt;&nbsp;&nbsp;&nbsp; OSPF areas."<BR><BR>This is one =
application of =0A=
multiple instance IDs.<BR><BR>&gt;<BR>&gt; 2. Can LSAs received from a =
neighbor =0A=
'A' which has instance ID=3D2 be<BR>&gt; flooded to another neighbor B =
that has =0A=
instance ID=3D5 =
?<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
InstanceID=3D2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
InstanceID=3D5<BR>&gt; =
A=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DR=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3DB<BR><BR>The base OSPFv3 =0A=
specification (RFC 2740) certainly doesn't preclude this<BR>since the =
interface =0A=
instance ID only has significance for that interface.<BR>In case of =0A=
draft-mirtorabi-ospf-multi-area-adj-00.txt, the instance ID =
has<BR>significance =0A=
beyond the scope of the interface and you would not.<BR><BR>Hope this =0A=
helps,<BR>Acee<BR><BR>&gt;<BR>&gt;<BR>&gt; Thanks in advance for any =0A=
help.<BR>&gt; -- Dilip<BR></FONT></P></DIV>=0A=
=0A=
</BODY>=0A=
</HTML>
------_=_NextPart_001_01C4A004.F7C83CE8--


From owner-ospf@PEACH.EASE.LSOFT.COM  Tue Sep 21 14:59:27 2004
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 OAA10235
	for <ospf-archive@LISTS.IETF.ORG>; Tue, 21 Sep 2004 14:59:26 -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 <12.00E8AA9C@cherry.ease.lsoft.com>; Tue, 21 Sep 2004 14:59:24 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 36584090 for OSPF@PEACH.EASE.LSOFT.COM;
          Tue, 21 Sep 2004 14:59:18 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Tue, 21 Sep 2004 14:59:18 -0400
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com
          (Postfix) with ESMTP id 711295D6667; Tue, 21 Sep 2004 11:59:17 -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 03846-07; Tue,
          21 Sep 2004 11:59:17 -0700 (PDT)
Received: from aceeinspiron (unknown [172.31.253.41]) by prattle.redback.com
          (Postfix) with SMTP id 16A5D5D6666; Tue, 21 Sep 2004 11:59:15 -0700
          (PDT)
References: <6204FDDE129D364D8040A98BCCB290EF0FF6AE5E@zbl6c004.corpeast.baynetworks.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
              boundary="----=_NextPart_000_010E_01C49FEB.8447DE90"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Virus-Scanned: by amavisd-new at redback.com
Message-ID:  <011101c4a00d$0c10c0a0$0202a8c0@aceeinspiron>
Date:         Tue, 21 Sep 2004 14:58:55 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Re: OSPF-V3 Instance ID
Comments: To: Daniel Joyal <djoyal@nortelnetworks.com>,
          Nic Neate <Nic.Neate@dataconnection.com>, vishwas@sinett.com
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

This is a multi-part message in MIME format.

------=_NextPart_000_010E_01C49FEB.8447DE90
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

RE: OSPF-V3 Instance IDHi Dan,

I think the OSPFv3 interface instance ID is somewhat different than =
multiple=20
protocol instances and, as such, should be considered separately:

   1. Unlike multiple OSPF(v3) instances, the instance ID is specified
       explicitly by the OSPF 2740.

   2. OSPFv3 runs on a link while OSPFv2 runs on a subnet. As such,
       the instance ID can be used so that a link can be configured in=20
       multiple OSPFv3 instances or for the link to be part of multiple =
areas.=20

Thanks,
Acee=20
--- Original Message -----=20
  From: Daniel Joyal=20
  To: 'Nic Neate' ; 'Mailing List' ; 'acee@redback.com' ; =
'vishwas@sinett.com'=20
  Sent: Tuesday, September 21, 2004 2:06 PM
  Subject: RE: OSPF-V3 Instance ID


  If we are talking about support for multiple instances of OSPFv3=20
  I think the MIB should be handled the same way as the OSPFv2 MIB and=20
  the IS-IS MIB in that neither have explicit instance ID objects=20
  (all of the instance index objects in the IS-IS MIB have recently been =

  removed). The syntax of the ospfv3InstId object should be changed to=20
  read-only to provide a view of the system allocated instance ID.=20

  Yes, the MIB will be refreshed.=20

  -Dan =20

  > -----Original Message-----=20
  > From: Nic Neate [mailto:Nic.Neate@dataconnection.com]=20
  > Sent: Tuesday, September 21, 2004 12:29 PM=20
  > To: 'Mailing List'; 'acee@redback.com'; Joyal, Daniel=20
  > [BL60:NP31:EXCH]; 'vishwas@sinett.com'=20
  > Subject: RE: OSPF-V3 Instance ID=20
  >=20
  >=20
  > Guys,=20
  >=20
  > Acee indicated below that the ospfv3IfTable should be indexed=20
  > by both ospfv3IfIndex and ospfv3InstId.=20
  >=20
  > I think it follows that the ospfv3NbrTable,=20
  > ospfv3NbmaNbrTable and ospfv3LinkLsdbTable (which are all=20
  > currently indexed on their interface=20
  > index) also need new interface instance index fields.  Is that =
right?=20
  >=20
  > Incidentally, I notice that draft-ietf-ospf-ospfv3-mib-08=20
  > expired in April. Are there plans to make updates and refresh it?=20
  >=20
  > Thanks,=20
  >=20
  > Nic=20
  >=20
  >=20
  > -----Original Message-----=20
  > From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM]On=20
  > Behalf Of Acee Lindem=20
  > Sent: Friday, July 09, 2004 4:15 AM=20
  > To: OSPF@PEACH.EASE.LSOFT.COM=20
  > Subject: Re: OSPF-V3 Instance ID=20
  >=20
  >=20
  > Hi Dilip,=20
  >=20
  > ----- Original Message -----=20
  > From: "Dilip Kumar" <dilipks@GMAIL.COM>=20
  > To: <OSPF@PEACH.EASE.LSOFT.COM>=20
  > Sent: Thursday, July 08, 2004 10:37 PM=20
  > Subject: OSPF-V3 Instance ID=20
  >=20
  >=20
  > > Hello,=20
  > >     I have couple of doubts w.r.to OSPF-V3's Instance ID=20
  > > interpretation 1. Can one router interface have more than one=20
  > > "Instance ID" configured simultaneously ?=20
  >=20
  > Yes.  However,  there may be implementations that only=20
  > support one to be configured.=20
  >=20
  > > OSPF-V3 MIB draft (draft-ietf-ospf-ospfv3-mib-08) indicates=20
  > that it is=20
  > > not possible.=20
  >=20
  > This is wrong. ospfv3IfTable should be indexed by both=20
  > ospfv3IfIndex and ospfv3InstId.=20
  >=20
  >=20
  > > However, RFC-2740 indirectly points that it is possible.=20
  > Following is=20
  > > the excerpt from the RFC-2740=20
  > >=20
  > >   "Another use for running multiple OSPF instances is if=20
  > you want, for=20
  > >    one reason or another, to have a single link belong to=20
  > two or more=20
  > >    OSPF areas."=20
  >=20
  > This is one application of multiple instance IDs.=20
  >=20
  > >=20
  > > 2. Can LSAs received from a neighbor 'A' which has instance ID=3D2 =
be=20
  > > flooded to another neighbor B that has instance ID=3D5 ?=20
  > >=20
  > >        InstanceID=3D2                  InstanceID=3D5=20
  > > =
A=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DR=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3DB=20
  >=20
  > The base OSPFv3 specification (RFC 2740) certainly doesn't=20
  > preclude this since the interface instance ID only has=20
  > significance for that interface. In case of=20
  > draft-mirtorabi-ospf-multi-area-adj-00.txt, the instance ID=20
  > has significance beyond the scope of the interface and you would =
not.=20
  >=20
  > Hope this helps,=20
  > Acee=20
  >=20
  > >=20
  > >=20
  > > Thanks in advance for any help.=20
  > > -- Dilip=20
  >=20
  >=20

------=_NextPart_000_010E_01C49FEB.8447DE90
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><TITLE>RE: OSPF-V3 Instance ID</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi Dan,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I think the OSPFv3 interface instance =
ID is=20
somewhat different than multiple </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>protocol instances and, as such, should =
be=20
considered separately:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; 1. Unlike multiple =
OSPF(v3) instances,=20
the instance ID is specified</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
explicitly by=20
the OSPF 2740.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; 2. OSPFv3 runs on a link =
while OSPFv2=20
runs on a subnet. As such,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
the instance=20
ID can be used so that a&nbsp;link&nbsp;can be&nbsp;configured=20
in&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&nbsp;multiple&nbsp;</FONT><FONT face=3DArial size=3D2>OSPFv3 instances =
or for the=20
link to be part of multiple areas. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Acee </FONT></DIV>
<DIV>--- Original Message ----- </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Ddjoyal@nortelnetworks.com=20
  href=3D"mailto:djoyal@nortelnetworks.com">Daniel Joyal</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3DNic.Neate@dataconnection.com=20
  href=3D"mailto:Nic.Neate@dataconnection.com">'Nic Neate'</A> ; <A=20
  title=3DOSPF@PEACH.EASE.LSOFT.COM=20
  href=3D"mailto:OSPF@PEACH.EASE.LSOFT.COM">'Mailing List'</A> ; <A=20
  title=3Dacee@redback.com =
href=3D"mailto:'acee@redback.com'">'acee@redback.com'</A>=20
  ; <A title=3Dvishwas@sinett.com=20
  href=3D"mailto:'vishwas@sinett.com'">'vishwas@sinett.com'</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, September 21, =
2004 2:06=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: OSPF-V3 Instance =
ID</DIV>
  <DIV><BR></DIV>
  <P><FONT size=3D2>If we are talking about support for multiple =
instances of=20
  OSPFv3</FONT> <BR><FONT size=3D2>I think the MIB should be handled the =
same way=20
  as the OSPFv2 MIB and</FONT> <BR><FONT size=3D2>the IS-IS MIB in that =
neither=20
  have explicit instance ID objects</FONT> <BR><FONT size=3D2>(all of =
the instance=20
  index objects in the IS-IS MIB have recently been</FONT> <BR><FONT=20
  size=3D2>removed). The syntax of the ospfv3InstId object should be =
changed=20
  to</FONT> <BR><FONT size=3D2>read-only to provide a view of the system =
allocated=20
  instance ID.</FONT> </P>
  <P><FONT size=3D2>Yes, the MIB will be refreshed.</FONT> </P>
  <P><FONT size=3D2>-Dan&nbsp; </FONT></P>
  <P><FONT size=3D2>&gt; -----Original Message-----</FONT> <BR><FONT =
size=3D2>&gt;=20
  From: Nic Neate [<A=20
  =
href=3D"mailto:Nic.Neate@dataconnection.com">mailto:Nic.Neate@dataconnect=
ion.com</A>]=20
  </FONT><BR><FONT size=3D2>&gt; Sent: Tuesday, September 21, 2004 12:29 =
PM</FONT>=20
  <BR><FONT size=3D2>&gt; To: 'Mailing List'; 'acee@redback.com'; Joyal, =
Daniel=20
  </FONT><BR><FONT size=3D2>&gt; [BL60:NP31:EXCH]; =
'vishwas@sinett.com'</FONT>=20
  <BR><FONT size=3D2>&gt; Subject: RE: OSPF-V3 Instance ID</FONT> =
<BR><FONT=20
  size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; </FONT><BR><FONT =
size=3D2>&gt;=20
  Guys,</FONT> <BR><FONT size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; =
Acee indicated=20
  below that the ospfv3IfTable should be indexed </FONT><BR><FONT =
size=3D2>&gt; by=20
  both ospfv3IfIndex and ospfv3InstId.</FONT> <BR><FONT size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; I think it follows that the =
ospfv3NbrTable,=20
  </FONT><BR><FONT size=3D2>&gt; ospfv3NbmaNbrTable and =
ospfv3LinkLsdbTable (which=20
  are all </FONT><BR><FONT size=3D2>&gt; currently indexed on their=20
  interface</FONT> <BR><FONT size=3D2>&gt; index) also need new =
interface instance=20
  index fields.&nbsp; Is that right?</FONT> <BR><FONT size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; Incidentally, I notice that=20
  draft-ietf-ospf-ospfv3-mib-08 </FONT><BR><FONT size=3D2>&gt; expired =
in April.=20
  Are there plans to make updates and refresh it?</FONT> <BR><FONT =
size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; Thanks,</FONT> <BR><FONT size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; Nic</FONT> <BR><FONT size=3D2>&gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; -----Original =
Message-----</FONT>=20
  <BR><FONT size=3D2>&gt; From: Mailing List [<A=20
  =
href=3D"mailto:OSPF@PEACH.EASE.LSOFT.COM">mailto:OSPF@PEACH.EASE.LSOFT.CO=
M</A>]On=20
  </FONT><BR><FONT size=3D2>&gt; Behalf Of Acee Lindem</FONT> <BR><FONT=20
  size=3D2>&gt; Sent: Friday, July 09, 2004 4:15 AM</FONT> <BR><FONT =
size=3D2>&gt;=20
  To: OSPF@PEACH.EASE.LSOFT.COM</FONT> <BR><FONT size=3D2>&gt; Subject: =
Re:=20
  OSPF-V3 Instance ID</FONT> <BR><FONT size=3D2>&gt; </FONT><BR><FONT =
size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; Hi Dilip,</FONT> <BR><FONT =
size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; ----- Original Message -----</FONT> =
<BR><FONT=20
  size=3D2>&gt; From: "Dilip Kumar" &lt;dilipks@GMAIL.COM&gt;</FONT> =
<BR><FONT=20
  size=3D2>&gt; To: &lt;OSPF@PEACH.EASE.LSOFT.COM&gt;</FONT> <BR><FONT =
size=3D2>&gt;=20
  Sent: Thursday, July 08, 2004 10:37 PM</FONT> <BR><FONT size=3D2>&gt; =
Subject:=20
  OSPF-V3 Instance ID</FONT> <BR><FONT size=3D2>&gt; </FONT><BR><FONT =
size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; &gt; Hello,</FONT> <BR><FONT =
size=3D2>&gt;=20
  &gt;&nbsp;&nbsp;&nbsp;&nbsp; I have couple of doubts w.r.to OSPF-V3's =
Instance=20
  ID </FONT><BR><FONT size=3D2>&gt; &gt; interpretation 1. Can one =
router=20
  interface have more than one </FONT><BR><FONT size=3D2>&gt; &gt; =
"Instance ID"=20
  configured simultaneously ?</FONT> <BR><FONT size=3D2>&gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; Yes.&nbsp; However,&nbsp; there may be implementations =
that only=20
  </FONT><BR><FONT size=3D2>&gt; support one to be configured.</FONT> =
<BR><FONT=20
  size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; &gt; OSPF-V3 MIB draft=20
  (draft-ietf-ospf-ospfv3-mib-08) indicates </FONT><BR><FONT =
size=3D2>&gt; that it=20
  is </FONT><BR><FONT size=3D2>&gt; &gt; not possible.</FONT> <BR><FONT=20
  size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; This is wrong. =
ospfv3IfTable should=20
  be indexed by both </FONT><BR><FONT size=3D2>&gt; ospfv3IfIndex and=20
  ospfv3InstId.</FONT> <BR><FONT size=3D2>&gt; </FONT><BR><FONT =
size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; &gt; However, RFC-2740 indirectly =
points that it=20
  is possible. </FONT><BR><FONT size=3D2>&gt; Following is =
</FONT><BR><FONT=20
  size=3D2>&gt; &gt; the excerpt from the RFC-2740</FONT> <BR><FONT =
size=3D2>&gt;=20
  &gt;</FONT> <BR><FONT size=3D2>&gt; &gt;&nbsp;&nbsp; "Another use for =
running=20
  multiple OSPF instances is if </FONT><BR><FONT size=3D2>&gt; you want, =

  for</FONT> <BR><FONT size=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; one reason =
or another,=20
  to have a single link belong to </FONT><BR><FONT size=3D2>&gt; two or=20
  more</FONT> <BR><FONT size=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; OSPF =
areas."</FONT>=20
  <BR><FONT size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; This is one =
application of=20
  multiple instance IDs.</FONT> <BR><FONT size=3D2>&gt; </FONT><BR><FONT =

  size=3D2>&gt; &gt;</FONT> <BR><FONT size=3D2>&gt; &gt; 2. Can LSAs =
received from a=20
  neighbor 'A' which has instance ID=3D2 be </FONT><BR><FONT =
size=3D2>&gt; &gt;=20
  flooded to another neighbor B that has instance ID=3D5 ?</FONT> =
<BR><FONT=20
  size=3D2>&gt; &gt;</FONT> <BR><FONT size=3D2>&gt;=20
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
InstanceID=3D2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  InstanceID=3D5</FONT> <BR><FONT size=3D2>&gt; &gt;=20
  =
A=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DR=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3DB</FONT> <BR><FONT size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; The base OSPFv3 specification (RFC =
2740)=20
  certainly doesn't </FONT><BR><FONT size=3D2>&gt; preclude this since =
the=20
  interface instance ID only has </FONT><BR><FONT size=3D2>&gt; =
significance for=20
  that interface. In case of </FONT><BR><FONT size=3D2>&gt;=20
  draft-mirtorabi-ospf-multi-area-adj-00.txt, the instance ID =
</FONT><BR><FONT=20
  size=3D2>&gt; has significance beyond the scope of the interface and =
you would=20
  not.</FONT> <BR><FONT size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; =
Hope this=20
  helps,</FONT> <BR><FONT size=3D2>&gt; Acee</FONT> <BR><FONT =
size=3D2>&gt;=20
  </FONT><BR><FONT size=3D2>&gt; &gt;</FONT> <BR><FONT size=3D2>&gt; =
&gt;</FONT>=20
  <BR><FONT size=3D2>&gt; &gt; Thanks in advance for any help.</FONT> =
<BR><FONT=20
  size=3D2>&gt; &gt; -- Dilip</FONT> <BR><FONT size=3D2>&gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; </FONT></P></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_010E_01C49FEB.8447DE90--


From owner-ospf@PEACH.EASE.LSOFT.COM  Wed Sep 22 04:31:03 2004
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 EAA13324
	for <ospf-archive@LISTS.IETF.ORG>; Wed, 22 Sep 2004 04:31:02 -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 <8.00E8B952@cherry.ease.lsoft.com>; Wed, 22 Sep 2004 4:31:02 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 36650144 for OSPF@PEACH.EASE.LSOFT.COM;
          Wed, 22 Sep 2004 04:31:01 -0400
Received: from 203.199.83.148 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i)
          with TCP; Wed, 22 Sep 2004 04:31:00 -0400
Received: (qmail 29974 invoked by uid 510); 22 Sep 2004 08:30:57 -0000
Received: from unknown (203.126.136.220) by rediffmail.com via HTTP; 22 sep
          2004 08:30:57 -0000
MIME-Version: 1.0
Content-type: multipart/alternative;
              boundary="Next_1095841857---0-203.199.83.148-29963"
Message-ID:  <20040922083057.29973.qmail@webmail26.rediffmail.com>
Date:         Wed, 22 Sep 2004 08:30:57 -0000
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Vivek Dubey <vivek_ospf@REDIFFMAIL.COM>
Subject: draft-vasseur-ospf-te-caps-00
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

 This is a multipart mime message


--Next_1095841857---0-203.199.83.148-29963
Content-type: text/html;
        charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

<P>=0ASection 3:<BR>=0A&gt;The TE-NODE-CAP TLV type is 1<BR>=0A<BR>=0Adraft=
-ietf-ospf-cap-03: Section 2.1:<BR>=0A&gt;The first defined TLV in the body=
 of an RI opaque LSA is the Router <BR>=0A&gt;Capabilities TLV.....<BR>=0A&=
gt;Type&nbsp; &nbsp; &nbsp; &nbsp; A 16 bit field set to 1<BR>=0A<BR>=0A1)I=
s the draft &quot;draft-vasseur-ospf-te-caps-00&quot; proposing to avoid <B=
R>=0A&nbsp; Capabilities TLV in RI opaque LSA?<BR>=0A<BR>=0AThanks<BR>=0A-V=
ivek<BR>=0A<BR>=0A<BR>=0A<BR>=0A&nbsp; <BR>=0A<BR>=0A<BR>=0A=0A</P>=0A<br><=
br>=0A<A target=3D"_blank" HREF=3D"http://clients.rediff.com/signature/trac=
k_sig.asp"><IMG SRC=3D"http://ads.rediff.com/RealMedia/ads/adstream_nx.cgi/=
www.rediffmail.com/inbox.htm@Bottom" BORDER=3D0 VSPACE=3D0 HSPACE=3D0></a>=
=0A
--Next_1095841857---0-203.199.83.148-29963
Content-type: text/plain;
        charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Section 3:=0A>The TE-NODE-CAP TLV type is 1=0A=0Adraft-ietf-ospf-cap-03: Se=
ction 2.1:=0A>The first defined TLV in the body of an RI opaque LSA is the =
Router =0A>Capabilities TLV.....=0A>Type        A 16 bit field set to 1=0A=
=0A1)Is the draft "draft-vasseur-ospf-te-caps-00" proposing to avoid =0A  C=
apabilities TLV in RI opaque LSA?=0A=0AThanks=0A-Vivek=0A=0A=0A=0A =A0=0A=
=0A=0A
--Next_1095841857---0-203.199.83.148-29963--


From owner-ospf@PEACH.EASE.LSOFT.COM  Wed Sep 22 18:40:24 2004
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 SAA23510
	for <ospf-archive@LISTS.IETF.ORG>; Wed, 22 Sep 2004 18:40:23 -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 <19.00E8CC7D@cherry.ease.lsoft.com>; Wed, 22 Sep 2004 18:40:22 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 36781966 for OSPF@PEACH.EASE.LSOFT.COM;
          Wed, 22 Sep 2004 18:40:20 -0400
Received: from 171.71.176.72 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Wed, 22 Sep 2004 18:40:18 -0400
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com
          with ESMTP; 22 Sep 2004 15:52:23 +0000
X-BrightmailFiltered: true
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223]) by
          sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i8MMe6SI002260 for
          <OSPF@PEACH.EASE.LSOFT.COM>; Wed, 22 Sep 2004 15:40:06 -0700 (PDT)
Received: from [66.189.47.89] (rtp-vpn3-270.cisco.com [10.82.217.16]) by
          wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id
          PAA22191 for <OSPF@PEACH.EASE.LSOFT.COM>; Wed, 22 Sep 2004 15:40:07
          -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v619)
References: <20040922083057.29973.qmail@webmail26.rediffmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Mailer: Apple Mail (2.619)
Message-ID:  <5B529510-0CE8-11D9-BDAB-000D93330B14@cisco.com>
Date:         Wed, 22 Sep 2004 18:40:08 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: JP Vasseur <jvasseur@CISCO.COM>
Subject: Re: draft-vasseur-ospf-te-caps-00
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To:  <20040922083057.29973.qmail@webmail26.rediffmail.com>
Precedence: list
Content-Transfer-Encoding: quoted-printable

Hi,

On Sep 22, 2004, at 4:30 AM, Vivek Dubey wrote:

> Section 3:
>> The TE-NODE-CAP TLV type is 1
>
> draft-ietf-ospf-cap-03: Section 2.1:
>> The first defined TLV in the body of an RI opaque LSA is the Router
>> Capabilities TLV.....
>> Type        A 16 bit field set to 1
>
> 1)Is the draft "draft-vasseur-ospf-te-caps-00" proposing to avoid
>   Capabilities TLV in RI opaque LSA?
>

Not at all ! The TE TLV will be using the RI LSA. TLV type will be=20
adjusted, thanks for pointing this out.

JP.

> Thanks
> -Vivek
>
>
>
>  =A0
>
>


From owner-ospf@PEACH.EASE.LSOFT.COM  Tue Sep 28 04:06:38 2004
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 EAA04642
	for <ospf-archive@LISTS.IETF.ORG>; Tue, 28 Sep 2004 04:06:38 -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 <19.00E961CA@cherry.ease.lsoft.com>; Tue, 28 Sep 2004 4:06:37 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 37570281 for OSPF@PEACH.EASE.LSOFT.COM;
          Tue, 28 Sep 2004 04:06:36 -0400
Received: from 203.199.83.148 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i)
          with TCP; Tue, 28 Sep 2004 04:06:35 -0400
Received: (qmail 18994 invoked by uid 510); 28 Sep 2004 08:07:49 -0000
Received: from unknown (203.126.136.220) by rediffmail.com via HTTP; 28 sep
          2004 08:07:49 -0000
MIME-Version: 1.0
Content-type: multipart/alternative;
              boundary="Next_1096358869---0-203.199.83.148-18984"
Message-ID:  <20040928080749.18992.qmail@webmail26.rediffmail.com>
Date:         Tue, 28 Sep 2004 08:07:49 -0000
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Vivek Dubey <vivek_ospf@REDIFFMAIL.COM>
Subject: draft-vasseur-ospf-te-caps-00
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

 This is a multipart mime message


--Next_1096358869---0-203.199.83.148-18984
Content-type: text/html;
        charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

<P>=0A6.1. TE-NODE-CAP TLV&nbsp; <BR>=0AThe flooding scope is defined on a =
per capability basis.<BR>=0A<BR>=0Avivek&gt; It would be better if it is sp=
ecified what are the recommended/defined flooding scope for different capab=
ilities advertised through this TLV.<BR>=0A<BR>=0A-Vivek<BR>=0A<BR>=0A<BR>=
=0A<BR>=0A<BR>=0AOn Thu, 23 Sep 2004 JP Vasseur wrote :<BR>=0A&gt;Hi,<BR>=
=0A&gt;<BR>=0A&gt;On Sep 22, 2004, at 4:30 AM, Vivek Dubey wrote:<BR>=0A&gt=
;<BR>=0A&gt;&gt;Section 3:<BR>=0A&gt;&gt;&gt;The TE-NODE-CAP TLV type is 1<=
BR>=0A&gt;&gt;<BR>=0A&gt;&gt;draft-ietf-ospf-cap-03: Section 2.1:<BR>=0A&gt=
;&gt;&gt;The first defined TLV in the body of an RI opaque LSA is the Route=
r<BR>=0A&gt;&gt;&gt;Capabilities TLV.....<BR>=0A&gt;&gt;&gt;Type&nbsp; &nbs=
p; &nbsp; &nbsp; A 16 bit field set to 1<BR>=0A&gt;&gt;<BR>=0A&gt;&gt;1)Is =
the draft &quot;draft-vasseur-ospf-te-caps-00&quot; proposing to avoid<BR>=
=0A&gt;&gt;&nbsp;  Capabilities TLV in RI opaque LSA?<BR>=0A&gt;&gt;<BR>=0A=
&gt;<BR>=0A&gt;Not at all ! The TE TLV will be using the RI LSA. TLV type w=
ill be adjusted, thanks for pointing this out.<BR>=0A&gt;<BR>=0A&gt;JP.<BR>=
=0A&gt;<BR>=0A&gt;&gt;Thanks<BR>=0A&gt;&gt;-Vivek<BR>=0A&gt;&gt;<BR>=0A&gt;=
&gt;<BR>=0A&gt;&gt;<BR>=0A&gt;&gt;&nbsp; =A0<BR>=0A&gt;&gt;<BR>=0A=0A</P>=
=0A<br><br>=0A<A target=3D"_blank" HREF=3D"http://clients.rediff.com/signat=
ure/track_sig.asp"><IMG SRC=3D"http://ads.rediff.com/RealMedia/ads/adstream=
_nx.cgi/www.rediffmail.com/inbox.htm@Bottom" BORDER=3D0 VSPACE=3D0 HSPACE=
=3D0></a>=0A
--Next_1096358869---0-203.199.83.148-18984
Content-type: text/plain;
        charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

6.1. TE-NODE-CAP TLV  =0AThe flooding scope is defined on a per capability =
basis.=0A=0Avivek> It would be better if it is specified what are the recom=
mended/defined flooding scope for different capabilities advertised through=
 this TLV.=0A=0A-Vivek=0A=0A=0A=0A=0AOn Thu, 23 Sep 2004 JP Vasseur wrote :=
=0A>Hi,=0A>=0A>On Sep 22, 2004, at 4:30 AM, Vivek Dubey wrote:=0A>=0A>>Sect=
ion 3:=0A>>>The TE-NODE-CAP TLV type is 1=0A>>=0A>>draft-ietf-ospf-cap-03: =
Section 2.1:=0A>>>The first defined TLV in the body of an RI opaque LSA is =
the Router=0A>>>Capabilities TLV.....=0A>>>Type        A 16 bit field set t=
o 1=0A>>=0A>>1)Is the draft "draft-vasseur-ospf-te-caps-00" proposing to av=
oid=0A>>   Capabilities TLV in RI opaque LSA?=0A>>=0A>=0A>Not at all ! The =
TE TLV will be using the RI LSA. TLV type will be adjusted, thanks for poin=
ting this out.=0A>=0A>JP.=0A>=0A>>Thanks=0A>>-Vivek=0A>>=0A>>=0A>>=0A>>  =
=A0=0A>>=0A
--Next_1096358869---0-203.199.83.148-18984--


From owner-ospf@PEACH.EASE.LSOFT.COM  Tue Sep 28 10:50:38 2004
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 KAA27209
	for <ospf-archive@LISTS.IETF.ORG>; Tue, 28 Sep 2004 10:50:38 -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 <4.00E96B1E@cherry.ease.lsoft.com>; Tue, 28 Sep 2004 10:50:38 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 37637913 for OSPF@PEACH.EASE.LSOFT.COM;
          Tue, 28 Sep 2004 10:50:34 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Tue, 28 Sep 2004 10:50:34 -0400
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com
          (Postfix) with ESMTP id 805CBBDFE6A for <OSPF@PEACH.EASE.LSOFT.COM>;
          Tue, 28 Sep 2004 07:50:30 -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 29128-05 for 
          <OSPF@PEACH.EASE.LSOFT.COM>; Tue, 28 Sep 2004 07:50:30 -0700 (PDT)
Received: from aceeinspiron (unknown [172.31.253.75]) by prattle.redback.com
          (Postfix) with SMTP id F1576BDFE69 for <OSPF@PEACH.EASE.LSOFT.COM>;
          Tue, 28 Sep 2004 07:50:28 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
              reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Virus-Scanned: by amavisd-new at redback.com
Message-ID:  <06f801c4a56a$7394e230$0202a8c0@aceeinspiron>
Date:         Tue, 28 Sep 2004 10:50:09 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Important Dates for 61st IETF in Washington DC
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

October 11, Monday - WG Chair approval for initial WG document (Version -00) submission due by 09:00 ET
October 18, Monday - Internet Draft Cut-off for initial document (-00) submission at 09:00 ET

Thanks,
------
Acee


From owner-ospf@PEACH.EASE.LSOFT.COM  Wed Sep 29 12:40:49 2004
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 MAA18063
	for <ospf-archive@LISTS.IETF.ORG>; Wed, 29 Sep 2004 12:40:49 -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 <5.00E98884@cherry.ease.lsoft.com>; Wed, 29 Sep 2004 12:40:47 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 37829261 for OSPF@PEACH.EASE.LSOFT.COM;
          Wed, 29 Sep 2004 12:40:45 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Wed, 29 Sep 2004 12:40:19 -0400
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com
          (Postfix) with ESMTP id 1BFB7A4124E for <OSPF@PEACH.EASE.LSOFT.COM>;
          Wed, 29 Sep 2004 09:40:18 -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 15026-08 for 
          <OSPF@PEACH.EASE.LSOFT.COM>; Wed, 29 Sep 2004 09:40:18 -0700 (PDT)
Received: from aceeinspiron (unknown [172.31.253.67]) by prattle.redback.com
          (Postfix) with SMTP id EFBFDA41250 for <OSPF@PEACH.EASE.LSOFT.COM>;
          Wed, 29 Sep 2004 09:40:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
              reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Virus-Scanned: by amavisd-new at redback.com
Message-ID:  <026801c4a642$f1c52ce0$0202a8c0@aceeinspiron>
Date:         Wed, 29 Sep 2004 12:39:51 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: OSPF Muli-Area Adjacency - draft-ietf-ospf-multi-area-adj-02.txt
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

This is the start of the Working Group Last Call for
OSPF Multi-Area Adjacency.  All comments must be
received by Thursday, October 14th, 2004 at 12:00 AM.
The proposed document status is informational.


------
Acee


From owner-ospf@PEACH.EASE.LSOFT.COM  Wed Sep 29 16:05:33 2004
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 QAA04366
	for <ospf-archive@LISTS.IETF.ORG>; Wed, 29 Sep 2004 16:05:32 -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 <11.00E98CDC@cherry.ease.lsoft.com>; Wed, 29 Sep 2004 16:05:32 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 37857808 for OSPF@PEACH.EASE.LSOFT.COM;
          Wed, 29 Sep 2004 16:05:29 -0400
Received: from 207.217.120.46 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i)
          with TCP; Wed, 29 Sep 2004 16:05:29 -0400
Received: from user-2ivfmjo.dialup.mindspring.com ([165.247.218.120]
          helo=earthlink.net) by grebe.mail.pas.earthlink.net with esmtp (Exim
          3.33 #1) id 1CCkhc-0007IG-00 for OSPF@PEACH.EASE.LSOFT.COM; Wed, 29
          Sep 2004 13:05:29 -0700
X-Sender: "Erblichs" <@smtp.earthlink.net> (Unverified)
X-Mailer: Mozilla 4.72 [en]C-gatewaynet  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
References: <026801c4a642$f1c52ce0$0202a8c0@aceeinspiron>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID:  <415B15CF.24B10802@earthlink.net>
Date:         Wed, 29 Sep 2004 13:06:39 -0700
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Erblichs <erblichs@EARTHLINK.NET>
Subject: Re: OSPF Muli-Area Adjacency - draft-ietf-ospf-multi-area-adj-02.txt
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

Comments:

        1.1 Motivation

        1) Should a link be locally configurable
        as a single area link or as a possible
        multiple area link?

        Why wouldn't we want to restrict certain
        links via configurability?

        If so, suggestion that the default is to
        the former, and 2.3 must first check the
        configured value for this link.

        1.3 proposed Solution

        2) What is the result of the failure of
        the first primary link? Is one of the
        secondaries promoted, is their a cascade
        effect that fails all secondaries, or can
        you have ONLY secondaries?

        2b) What is the definition of a secondary?
        Shouldn't you say something about this?

        3) NIT. Their is no Reference as [OSPF]. This
        is repeated a few times. Their is a [RFC2328].
        Shouldn't they match?

        2.3 Multi-Area ....

        4) NIT Bullet in 2.3.. vilrtual -> virtual

        5) NIT. What is VL and TA?

        6) [...] what is this change in 2.3?

        7) Why isn't primary and or secondary specified
        here?

        8) NIT.. adjacencis -> adjacencies

        2.7 Advertising ...

        9) Link ID is set to two different values?

        General comment:

        10) Is their a limit to the number of secondary
        adjacencies?


        Thanks,

        Mitchell Erblich

        ------------------------






Acee Lindem wrote:
>
> This is the start of the Working Group Last Call for
> OSPF Multi-Area Adjacency.  All comments must be
> received by Thursday, October 14th, 2004 at 12:00 AM.
> The proposed document status is informational.
>
> ------
> Acee


From owner-ospf@PEACH.EASE.LSOFT.COM  Wed Sep 29 21:21:56 2004
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 VAA11424
	for <ospf-archive@LISTS.IETF.ORG>; Wed, 29 Sep 2004 21:21:56 -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 <5.00E9925E@cherry.ease.lsoft.com>; Wed, 29 Sep 2004 21:21:55 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 37886823 for OSPF@PEACH.EASE.LSOFT.COM;
          Wed, 29 Sep 2004 21:21:53 -0400
Received: from 171.68.227.75 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Wed, 29 Sep 2004 21:21:53 -0400
Received: from smirtoraw2k03 (sjc-vpn1-214.cisco.com [10.21.96.214]) by
          fire.cisco.com (8.11.7+Sun/8.8.8) with ESMTP id i8U1LqC07122 for
          <OSPF@PEACH.EASE.LSOFT.COM>; Wed, 29 Sep 2004 18:21:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300
Importance: Normal
Message-ID:  <039a01c4a68b$dd5cd4d0$6001a8c0@amer.cisco.com>
Date:         Wed, 29 Sep 2004 21:21:51 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Sina Mirtorabi <sina@CISCO.COM>
Subject: Re: OSPF Muli-Area Adjacency - draft-ietf-ospf-multi-area-adj-02.txt
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To:  <415B15CF.24B10802@earthlink.net>
Precedence: list
Content-Transfer-Encoding: 7bit

Mitchell,

Thanks for the comments, please see in line

->
->Comments:
->
->        1.1 Motivation
->
->        1) Should a link be locally configurable
->        as a single area link or as a possible
->        multiple area link?
->
->        Why wouldn't we want to restrict certain
->        links via configurability?
->
->        If so, suggestion that the default is to
->        the former, and 2.3 must first check the
->        configured value for this link.

The multi-area adjacency has to be explicitly configured, if you don't
want then you won't configure and you have a single adjacency. What do
you want to restrict?

->
->        1.3 proposed Solution
->
->        2) What is the result of the failure of
->        the first primary link? Is one of the
->        secondaries promoted, is their a cascade
->        effect that fails all secondaries, or can
->        you have ONLY secondaries?

There is no relation between primary and secondary adjacency. If the
link fail then obviously all adjacency over the link will fail. So no
relationship between different adjacencies

->
->        2b) What is the definition of a secondary?
->        Shouldn't you say something about this?

There is one mention of secondary adjacency in section 2.7 however it
should be replaced by "multi-area adjacency" which is defined through
out the document

->
->        3) NIT. Their is no Reference as [OSPF]. This
->        is repeated a few times. Their is a [RFC2328].
->        Shouldn't they match?

Yes, this will be corrected

->
->        2.3 Multi-Area ....
->
->        4) NIT Bullet in 2.3.. vilrtual -> virtual

Will be corrected

->
->        5) NIT. What is VL and TA?

Humm, it should be virtual link and multi-area adjacency...

->
->        6) [...] what is this change in 2.3?

Means the remaining is not changed from OSPF standard (section 8.2)

->
->        7) Why isn't primary and or secondary specified
->        here?
->

Secondary should be replaced by multi-area adjacency

->        8) NIT.. adjacencis -> adjacencies
->

Will be corrected

->        2.7 Advertising ...
->
->        9) Link ID is set to two different values?

The second should be Link Data. It Will be corrected

->
->        General comment:
->
->        10) Is their a limit to the number of secondary
->        adjacencies?

No, unless there is a reason to restrict. Typically you would use 1 (or
very few) depending on path requirement and number of ABR's attached
areas..

Thanks
Sina


->
->
->        Thanks,
->
->        Mitchell Erblich
->
->        ------------------------
->
->
->
->
->
->
->Acee Lindem wrote:
->>
->> This is the start of the Working Group Last Call for
->> OSPF Multi-Area Adjacency.  All comments must be
->> received by Thursday, October 14th, 2004 at 12:00 AM.
->> The proposed document status is informational.
->>
->> ------
->> Acee
->


From owner-ospf@PEACH.EASE.LSOFT.COM  Thu Sep 30 02:09:29 2004
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 CAA09032
	for <ospf-archive@LISTS.IETF.ORG>; Thu, 30 Sep 2004 02:09:29 -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 <14.00E998B8@cherry.ease.lsoft.com>; Thu, 30 Sep 2004 2:09:28 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 37913852 for OSPF@PEACH.EASE.LSOFT.COM;
          Thu, 30 Sep 2004 02:09:20 -0400
Received: from 61.144.161.40 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Thu, 30 Sep 2004 02:09:20 -0400
Received: from KSProsonna (huawei.com [172.17.1.62]) by mta0.huawei.com
          (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep  8 2003)) with
          ESMTPA id <0I4U00HIBBMOOG@mta0.huawei.com> for
          OSPF@PEACH.EASE.LSOFT.COM; Thu, 30 Sep 2004 14:06:26 +0800 (CST)
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: multipart/alternative;
              boundary="Boundary_(ID_eZEzEMfAyN+bXPbJCxwtRQ)"
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-imss-version: 2.7
X-imss-result: Passed
X-imss-approveListMatch: *@huawei.com
Message-ID:  <000701c4a6b4$1ae4e8b0$8804120a@KSProsonna>
Date:         Thu, 30 Sep 2004 11:39:53 +0530
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: prasanna <KSPrasanna@HUAWEI.COM>
Organization: huawei
Subject: some doubt about use of instance-id with vlink in OSPFV3
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

This is a multi-part message in MIME format.

--Boundary_(ID_eZEzEMfAyN+bXPbJCxwtRQ)
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7BIT

While sending the OSPFv3 packet for virtual-link, those packets will
have instance-id zero (if the virtual-link is not configured with
instance-id).

If there are multiple processes attached to an incoming interface, to
which process the hello packet is delivered?

To all the process/ only to the process to which the interface is
attached with instance-id zero?



One more doubt. When I configure a virtual-link with instance-id (n),
should both sender's and receiver's interfaces should be configured with
same instance-id(n)


--Boundary_(ID_eZEzEMfAyN+bXPbJCxwtRQ)
Content-type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7BIT

<html>

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">


<meta name=Generator content="Microsoft Word 10 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:"\@SimSun";
        panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {font-family:Arial;
        color:windowtext;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
        {page:Section1;}
-->
</style>

</head>

<body lang=EN-GB link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'>While sending the OSPFv3 packet for virtual-link, those
packets will have instance-id zero (if the virtual-link is not configured with
instance-id).</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'>If there are multiple processes attached to an
incoming interface, to which process the hello packet is delivered? </span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'>To all the process/ only to the process to which the
interface is attached with instance-id zero?</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span lang=EN-US style='font-size:
10.0pt;font-family:Arial'>One more doubt. When I configure a virtual-link with
instance-id (n), should both sender&#8217;s and receiver&#8217;s interfaces should
be configured with same instance-id(n) </span></font></p>

</div>

</body>

</html>

--Boundary_(ID_eZEzEMfAyN+bXPbJCxwtRQ)--


From owner-ospf@PEACH.EASE.LSOFT.COM  Thu Sep 30 02:44:45 2004
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 CAA16098
	for <ospf-archive@LISTS.IETF.ORG>; Thu, 30 Sep 2004 02:44:45 -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 <5.00E99945@cherry.ease.lsoft.com>; Thu, 30 Sep 2004 2:44:45 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 37914866 for OSPF@PEACH.EASE.LSOFT.COM;
          Thu, 30 Sep 2004 02:44:42 -0400
Received: from 203.197.124.190 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i)
          with TCP; Thu, 30 Sep 2004 02:34:41 -0400
Received: from raman (raman.alumnus.co.in [192.168.10.41]) by alumnux.com
          (8.9.3/8.9.3) with SMTP id MAA11814 for <OSPF@PEACH.EASE.LSOFT.COM>;
          Thu, 30 Sep 2004 12:02:29 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;
              boundary="----=_NextPart_000_001D_01C4A6E5.9ED07640"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4942.400
Importance: Normal
Message-ID:  <001c01c4a6b7$85183a40$290aa8c0@raman>
Date:         Thu, 30 Sep 2004 12:04:20 +0530
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Joseph Placid <joseph@ALUMNUX.COM>
Subject: External Routes
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

This is a multi-part message in MIME format.

------=_NextPart_000_001D_01C4A6E5.9ED07640
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Hi,
            How does an OSPF router learn external route information from
the External Routing Protocol (eg. BGP). Is this implementation specific?

Thanks,
Joseph Placid.

------=_NextPart_000_001D_01C4A6E5.9ED07640
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C4A6E5.9E393F50">
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {mso-style-parent:"";
        margin:0in;
        margin-bottom:.0001pt;
        mso-pagination:widow-orphan;
        font-size:12.0pt;
        font-family:"Times New Roman";
        mso-fareast-font-family:"Times New Roman";}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
        {margin:0in;
        margin-bottom:.0001pt;
        mso-pagination:widow-orphan;
        font-size:12.0pt;
        font-family:"Times New Roman";
        mso-fareast-font-family:"Times New Roman";}
span.EmailStyle15
        {mso-style-type:personal-compose;
        mso-ansi-font-size:10.0pt;
        mso-ascii-font-family:Arial;
        mso-hansi-font-family:Arial;
        mso-bidi-font-family:Arial;
        color:black;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.25in 1.0in 1.25in;
        mso-header-margin:.5in;
        mso-footer-margin:.5in;
        mso-paper-source:0;}
div.Section1
        {page:Section1;}
-->
</style>
</head>

<body lang=3DEN-US style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>Hi,<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><span =
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; </span>How
does an OSPF router learn external route information from the External =
Routing
Protocol (eg. BGP). Is this implementation =
specific?<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>Thanks,<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>Joseph Placid.<o:p></o:p></span></font></span></p>

</div>

</body>

</html>

------=_NextPart_000_001D_01C4A6E5.9ED07640--


From owner-ospf@PEACH.EASE.LSOFT.COM  Thu Sep 30 02:45:39 2004
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 CAA16197
	for <ospf-archive@LISTS.IETF.ORG>; Thu, 30 Sep 2004 02:45:38 -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 <7.00E99A32@cherry.ease.lsoft.com>; Thu, 30 Sep 2004 2:45:39 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 37915358 for OSPF@PEACH.EASE.LSOFT.COM;
          Thu, 30 Sep 2004 02:45:36 -0400
Received: from 63.197.255.158 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i)
          with TCP; Thu, 30 Sep 2004 02:45:36 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C4A6B9.E160C996"
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: External Routes
thread-index: AcSmucav3w5HcLyQRKKe37kVIHLKhAAAAhKQ
Message-ID:  <BB6D74C75CC76A419B6D6FA7C38317B2475685@sinett-sbs.SiNett.LAN>
Date:         Wed, 29 Sep 2004 23:50:28 -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: External Routes
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4A6B9.E160C996
Content-Type: text/plain;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Yes.

=20

________________________________

From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM] On Behalf Of
Joseph Placid
Sent: Thursday, September 30, 2004 12:04 PM
To: OSPF@PEACH.EASE.LSOFT.COM
Subject: External Routes

=20

Hi,

            How does an OSPF router learn external route information
from the External Routing Protocol (eg. BGP). Is this implementation
specific?

=20

Thanks,

Joseph Placid.


------_=_NextPart_001_01C4A6B9.E160C996
Content-Type: text/html;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
span.EmailStyle16
        {mso-style-type:personal;
        font-family:Arial;
        color:black;}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:Arial;
        color:navy;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
        {page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Yes.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
<st1:PersonName
w:st=3D"on">Mailing List</st1:PersonName> =
[mailto:OSPF@PEACH.EASE.LSOFT.COM] <b><span
style=3D'font-weight:bold'>On Behalf Of </span></b>Joseph Placid<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, September =
30, 2004
12:04 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> =
OSPF@PEACH.EASE.LSOFT.COM<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> External =
Routes</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><span class=3DEmailStyle16><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt'>Hi,<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle16><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; How does an OSPF router
learn external route information from the External Routing Protocol (eg. =
BGP).
Is this implementation specific?<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle16><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle16><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt'>Thanks,<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle16><font size=3D2 =
color=3Dblack
face=3DArial><span style=3D'font-size:10.0pt'>Joseph =
Placid.<o:p></o:p></span></font></span></p>

</div>

</body>

</html>

------_=_NextPart_001_01C4A6B9.E160C996--


From owner-ospf@PEACH.EASE.LSOFT.COM  Thu Sep 30 08:00:29 2004
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 IAA13424
	for <ospf-archive@LISTS.IETF.ORG>; Thu, 30 Sep 2004 08:00:29 -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 <23.00E99FBF@cherry.ease.lsoft.com>; Thu, 30 Sep 2004 8:00:28 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 37971082 for OSPF@PEACH.EASE.LSOFT.COM;
          Thu, 30 Sep 2004 08:00:26 -0400
Received: from 61.144.161.40 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Thu, 30 Sep 2004 08:00:25 -0400
Received: from DE (huawei.com [172.17.1.62]) by mta0.huawei.com (iPlanet
          Messaging Server 5.2 HotFix 1.21 (built Sep  8 2003)) with ESMTPA id
          <0I4U00CXBQS2BX@mta0.huawei.com> for OSPF@PEACH.EASE.LSOFT.COM; Thu,
          30 Sep 2004 19:33:39 +0800 (CST)
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.6626
Content-type: multipart/alternative;
              boundary="Boundary_(ID_4DYvp9dCLjdGSLUOhQ2FnA)"
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-imss-version: 2.7
X-imss-result: Passed
X-imss-approveListMatch: *@huawei.com
Message-ID:  <001101c4a6e1$983c2f30$8704120a@DE>
Date:         Thu, 30 Sep 2004 17:05:31 +0530
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Santosh Esale <santosh_e@HUAWEI.COM>
Organization: HTIPL
Subject: Re: some doubt about use of instance-id with vlink in OSPFV3
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To:  <000701c4a6b4$1ae4e8b0$8804120a@KSProsonna>
Precedence: list

This is a multi-part message in MIME format.

--Boundary_(ID_4DYvp9dCLjdGSLUOhQ2FnA)
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7BIT

Hey prasanna,

                         If there are multiple process attached to an
incoming interface, the hello packet will be delivered to all the process,
and will be accepted by the process in which Vlink has been configured with
peer router id which is equal to router id in the received packet.



To answer second question, its implementation specific, but I think there is
no use of instance id on virtual-link, our implementation won't care of
instance id.



Regards

Santosh





-----Original Message-----
From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM] On Behalf Of prasanna
Sent: Thursday, September 30, 2004 11:40 AM
To: OSPF@PEACH.EASE.LSOFT.COM
Subject: some doubt about use of instance-id with vlink in OSPFV3



While sending the OSPFv3 packet for virtual-link, those packets will have
instance-id zero (if the virtual-link is not configured with instance-id).

If there are multiple processes attached to an incoming interface, to which
process the hello packet is delivered?

To all the process/ only to the process to which the interface is attached
with instance-id zero?



One more doubt. When I configure a virtual-link with instance-id (n), should
both sender's and receiver's interfaces should be configured with same
instance-id(n)


--Boundary_(ID_4DYvp9dCLjdGSLUOhQ2FnA)
Content-type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7BIT

<html>

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">


<meta name=Generator content="Microsoft Word 10 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline;}
span.emailstyle17
        {font-family:Arial;
        color:windowtext;}
span.EmailStyle18
        {font-family:Arial;
        color:navy;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
        {page:Section1;}
-->
</style>

</head>

<body lang=ZH-CN link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=1 color=navy face=Arial><span lang=EN-US
style='font-size:9.0pt;font-family:Arial;color:navy'>Hey prasanna,</span></font></p>

<p class=MsoNormal><font size=1 color=navy face=Arial><span lang=EN-US
style='font-size:9.0pt;font-family:Arial;color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
If there are multiple process attached to an incoming interface, the hello
packet will be delivered to all the process, and will be accepted by the process
in which Vlink has been configured with peer router id which is equal to router
id in the received packet.</span></font></p>

<p class=MsoNormal><font size=1 color=navy face=Arial><span lang=EN-US
style='font-size:9.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=1 color=navy face=Arial><span lang=EN-US
style='font-size:9.0pt;font-family:Arial;color:navy'>To answer second question,
its implementation specific, but I think there is no use of instance id on virtual-link,
our implementation won&#8217;t care of instance id.</span></font></p>

<p class=MsoNormal><font size=1 color=navy face=Arial><span lang=EN-US
style='font-size:9.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=1 color=navy face=Arial><span lang=EN-US
style='font-size:9.0pt;font-family:Arial;color:navy'>Regards</span></font></p>

<p class=MsoNormal><font size=1 color=navy face=Arial><span lang=EN-US
style='font-size:9.0pt;font-family:Arial;color:navy'>Santosh</span></font></p>

<p class=MsoNormal><font size=1 color=navy face=Arial><span lang=EN-US
style='font-size:9.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=1 color=navy face=Arial><span lang=EN-US
style='font-size:9.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Tahoma><span
lang=EN-US style='font-size:10.0pt;font-family:Tahoma'>-----Original
Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> Mailing List
[mailto:OSPF@PEACH.EASE.LSOFT.COM] <b><span style='font-weight:bold'>On Behalf
Of </span></b>prasanna<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, September 30, 2004
11:40 AM<br>
<b><span style='font-weight:bold'>To:</span></b> OSPF@PEACH.EASE.LSOFT.COM<br>
<b><span style='font-weight:bold'>Subject:</span></b> some doubt about use of
instance-id with vlink in OSPFV3</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
lang=EN-US style='font-size:12.0pt'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
lang=EN-US style='font-size:10.0pt;font-family:Arial'>While sending the OSPFv3
packet for virtual-link, those packets will have instance-id zero (if the
virtual-link is not configured with instance-id).</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
lang=EN-US style='font-size:10.0pt;font-family:Arial'>If there are multiple
processes attached to an incoming interface, to which process the hello packet
is delivered? </span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
lang=EN-US style='font-size:10.0pt;font-family:Arial'>To all the process/ only
to the process to which the interface is attached with instance-id zero?</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
lang=EN-US style='font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Arial><span
lang=EN-US style='font-size:10.0pt;font-family:Arial'>One more doubt. When I
configure a virtual-link with instance-id (n), should both sender&#8217;s and
receiver&#8217;s interfaces should be configured with same instance-id(n) </span></font></p>

</div>

</body>

</html>

--Boundary_(ID_4DYvp9dCLjdGSLUOhQ2FnA)--


From owner-ospf@PEACH.EASE.LSOFT.COM  Thu Sep 30 08:21:30 2004
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 IAA14921
	for <ospf-archive@LISTS.IETF.ORG>; Thu, 30 Sep 2004 08:21:29 -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 <8.00E99EEF@cherry.ease.lsoft.com>; Thu, 30 Sep 2004 8:21:28 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 37973869 for OSPF@PEACH.EASE.LSOFT.COM;
          Thu, 30 Sep 2004 08:21:25 -0400
Received: from 64.233.170.205 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i)
          with TCP; Thu, 30 Sep 2004 08:11:25 -0400
Received: by mproxy.gmail.com with SMTP id 74so182276rnk for
          <OSPF@PEACH.EASE.LSOFT.COM>; Thu, 30 Sep 2004 05:11:25 -0700 (PDT)
Received: by 10.38.59.51 with SMTP id h51mr2633581rna; Thu, 30 Sep 2004
          05:11:25 -0700 (PDT)
Received: by 10.38.102.60 with HTTP; Thu, 30 Sep 2004 05:11:25 -0700 (PDT)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-ID:  <ce8d9033040930051160b5c35d@mail.gmail.com>
Date:         Thu, 30 Sep 2004 17:41:25 +0530
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Abhishek Verma <abhishekv.verma@GMAIL.COM>
Subject: Cost involved in running SPF
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

Hi,

Is there a difference in cost involved in running the SPF for AS
External LSAs vis-a-vis the normal Type 1 or 2 LSAs?

My question is, that what is more expensive for an OSPF router?
Receiving too many Type 5 LSAs or say, Type 3 LSAs?

Or is there no difference at all?

Cheers,
Abhishek


From owner-ospf@PEACH.EASE.LSOFT.COM  Thu Sep 30 08:24:30 2004
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 IAA15007
	for <ospf-archive@LISTS.IETF.ORG>; Thu, 30 Sep 2004 08:24:29 -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.00E99FD9@cherry.ease.lsoft.com>; Thu, 30 Sep 2004 8:24:30 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 37974843 for OSPF@PEACH.EASE.LSOFT.COM;
          Thu, 30 Sep 2004 08:24:27 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Thu, 30 Sep 2004 08:24:27 -0400
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com
          (Postfix) with ESMTP id 8AFB5ACB9E9 for <OSPF@PEACH.EASE.LSOFT.COM>;
          Thu, 30 Sep 2004 05:24:27 -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 15194-07 for 
          <OSPF@PEACH.EASE.LSOFT.COM>; Thu, 30 Sep 2004 05:24:27 -0700 (PDT)
Received: from aceeinspiron (unknown [172.31.253.67]) by prattle.redback.com
          (Postfix) with SMTP id D94BFACB9E8 for <OSPF@PEACH.EASE.LSOFT.COM>;
          Thu, 30 Sep 2004 05:24:26 -0700 (PDT)
References:  <000701c4a6b4$1ae4e8b0$8804120a@KSProsonna>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
              reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Virus-Scanned: by amavisd-new at redback.com
Message-ID:  <04c501c4a6e8$5d5e9680$0202a8c0@aceeinspiron>
Date:         Thu, 30 Sep 2004 08:23:59 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Re: some doubt about use of instance-id with vlink in OSPFV3
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

> ----- Original Message -----
> From: prasanna
> To: OSPF@PEACH.EASE.LSOFT.COM
> Sent: Thursday, September 30, 2004 2:09 AM
> Subject: some doubt about use of instance-id with vlink in OSPFV3
>
>
> While sending the OSPFv3 packet for virtual-link, those packets will have instance-id zero (if the virtual-link is not configured
> with instance-id).

Yes.

> If there are multiple processes attached to an incoming interface, to which process the hello packet is delivered?

The virtual link interface - you DON'T match instance ID on the incoming interface. Just assure that it is
configured in the transit area for the virtual link.

> To all the process/ only to the process to which the interface is attached with instance-id zero?
>
> One more doubt. When I configure a virtual-link with instance-id (n), should both sender's and receiver's interfaces should be
> configured with same > instance-id(n)

Of course.

Hope this helps,
Acee


From owner-ospf@PEACH.EASE.LSOFT.COM  Thu Sep 30 08:38:55 2004
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 IAA15927
	for <ospf-archive@LISTS.IETF.ORG>; Thu, 30 Sep 2004 08:38:54 -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 <19.00E99EDF@cherry.ease.lsoft.com>; Thu, 30 Sep 2004 8:38:54 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 37976922 for OSPF@PEACH.EASE.LSOFT.COM;
          Thu, 30 Sep 2004 08:38:29 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Thu, 30 Sep 2004 08:38:29 -0400
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com
          (Postfix) with ESMTP id AA695548024 for <OSPF@PEACH.EASE.LSOFT.COM>;
          Thu, 30 Sep 2004 05:38:29 -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 05489-05 for 
          <OSPF@PEACH.EASE.LSOFT.COM>; Thu, 30 Sep 2004 05:38:29 -0700 (PDT)
Received: from aceeinspiron (unknown [172.31.253.67]) by prattle.redback.com
          (Postfix) with SMTP id 6E8A8548025 for <OSPF@PEACH.EASE.LSOFT.COM>;
          Thu, 30 Sep 2004 05:38:28 -0700 (PDT)
References:  <001101c4a6e1$983c2f30$8704120a@DE>
MIME-Version: 1.0
Content-Type: multipart/alternative;
              boundary="----=_NextPart_000_04FC_01C4A6C8.CB827110"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Virus-Scanned: by amavisd-new at redback.com
Message-ID:  <04ff01c4a6ea$52f45980$0202a8c0@aceeinspiron>
Date:         Thu, 30 Sep 2004 08:38:01 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Re: some doubt about use of instance-id with vlink in OSPFV3
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

This is a multi-part message in MIME format.

------=_NextPart_000_04FC_01C4A6C8.CB827110
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Santosh,
I think that the instance IDs should match for virtual links. If you =
want to=20
support multiple instances within the same routing to domain then you
need it to demux packets (e.g., to support unicast and multicast =
topologies).=20

Thanks,
Acee=20
  ----- Original Message -----=20
  From: Santosh Esale=20
  To: OSPF@PEACH.EASE.LSOFT.COM=20
  Sent: Thursday, September 30, 2004 7:35 AM
  Subject: Re: some doubt about use of instance-id with vlink in OSPFV3


  Hey prasanna,

                           If there are multiple process attached to an =
incoming interface, the hello packet will be delivered to all the =
process, and will be accepted by the process in which Vlink has been =
configured with peer router id which is equal to router id in the =
received packet.



  To answer second question, its implementation specific, but I think =
there is no use of instance id on virtual-link, our implementation won't =
care of instance id.



  Regards

  Santosh





  -----Original Message-----
  From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM] On Behalf Of =
prasanna
  Sent: Thursday, September 30, 2004 11:40 AM
  To: OSPF@PEACH.EASE.LSOFT.COM
  Subject: some doubt about use of instance-id with vlink in OSPFV3



  While sending the OSPFv3 packet for virtual-link, those packets will =
have instance-id zero (if the virtual-link is not configured with =
instance-id).

  If there are multiple processes attached to an incoming interface, to =
which process the hello packet is delivered?=20

  To all the process/ only to the process to which the interface is =
attached with instance-id zero?



  One more doubt. When I configure a virtual-link with instance-id (n), =
should both sender's and receiver's interfaces should be configured with =
same instance-id(n)=20

------=_NextPart_000_04FC_01C4A6C8.CB827110
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">
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR>
<STYLE>@font-face {
        font-family: SimSun;
}
@font-face {
        font-family: Tahoma;
}
@font-face {
        font-family: SimSun;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
        COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
        COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
        COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
        COLOR: purple; TEXT-DECORATION: underline
}
SPAN.emailstyle17 {
        COLOR: windowtext; FONT-FAMILY: Arial
}
SPAN.EmailStyle18 {
        COLOR: navy; FONT-FAMILY: Arial
}
DIV.Section1 {
        page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DZH-CN vLink=3Dpurple link=3Dblue bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi Santosh,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I think that the&nbsp;instance IDs =
should=20
match&nbsp;for virtual links. If you want to </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>support multiple instances within the =
same routing=20
to domain then you</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>need&nbsp;it to demux packets (e.g., to =

support&nbsp;unicast and multicast topologies). </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Acee </FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dsantosh_e@HUAWEI.COM =
href=3D"mailto:santosh_e@HUAWEI.COM">Santosh=20
  Esale</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3DOSPF@PEACH.EASE.LSOFT.COM=20
  =
href=3D"mailto:OSPF@PEACH.EASE.LSOFT.COM">OSPF@PEACH.EASE.LSOFT.COM</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, September 30, =
2004 7:35=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: some doubt about =
use of=20
  instance-id with vlink in OSPFV3</DIV>
  <DIV><BR></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">Hey=20
  prasanna,</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
  If there are multiple process attached to an incoming interface, the =
hello=20
  packet will be delivered to all the process, and will be accepted by =
the=20
  process in which Vlink has been configured with peer router id which =
is equal=20
  to router id in the received packet.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">To answer =
second=20
  question, its implementation specific, but I think there is no use of =
instance=20
  id on virtual-link, our implementation won=92t care of instance=20
  id.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial">Regards</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial">Santosh</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DTahoma =
size=3D2><SPAN=20
  lang=3DEN-US style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">-----Original=20
  Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
Mailing=20
  List [mailto:OSPF@PEACH.EASE.LSOFT.COM] <B><SPAN style=3D"FONT-WEIGHT: =
bold">On=20
  Behalf Of </SPAN></B>prasanna<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Thursday, September 30, =
2004 11:40=20
  AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
  OSPF@PEACH.EASE.LSOFT.COM<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> some doubt about use =
of=20
  instance-id with vlink in OSPFV3</SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
  size=3D3><SPAN lang=3DEN-US style=3D"FONT-SIZE: =
12pt"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
size=3D2><SPAN=20
  lang=3DEN-US style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">While =
sending the=20
  OSPFv3 packet for virtual-link, those packets will have instance-id =
zero (if=20
  the virtual-link is not configured with =
instance-id).</SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
size=3D2><SPAN=20
  lang=3DEN-US style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">If there =
are multiple=20
  processes attached to an incoming interface, to which process the =
hello packet=20
  is delivered? </SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
size=3D2><SPAN=20
  lang=3DEN-US style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">To all the =
process/=20
  only to the process to which the interface is attached with =
instance-id=20
  zero?</SPAN></FONT></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
size=3D2><SPAN=20
  lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
size=3D2><SPAN=20
  lang=3DEN-US style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">One more =
doubt. When I=20
  configure a virtual-link with instance-id (n), should both sender=92s =
and=20
  receiver=92s interfaces should be configured with same instance-id(n)=20
  </SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_04FC_01C4A6C8.CB827110--


From owner-ospf@PEACH.EASE.LSOFT.COM  Thu Sep 30 10:19:45 2004
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 KAA24920
	for <ospf-archive@LISTS.IETF.ORG>; Thu, 30 Sep 2004 10:19:44 -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 <17.00E9A239@cherry.ease.lsoft.com>; Thu, 30 Sep 2004 10:19:43 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 37984374 for OSPF@PEACH.EASE.LSOFT.COM;
          Thu, 30 Sep 2004 10:19:40 -0400
Received: from 61.144.161.41 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Thu, 30 Sep 2004 10:19:39 -0400
Received: from KSProsonna (mta1.huawei.com [172.17.1.60]) by mta1.huawei.com
          (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) with
          ESMTPA id <0I4U0007MTPF2C@mta1.huawei.com> for
          OSPF@PEACH.EASE.LSOFT.COM; Thu, 30 Sep 2004 20:36:52 +0800 (CST)
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-imss-version: 2.7
X-imss-result: Passed
X-imss-approveListMatch: *@huawei.com
Message-ID:  <000201c4a6ec$43603e10$8804120a@KSProsonna>
Date:         Thu, 30 Sep 2004 18:21:53 +0530
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: prasanna <KSPrasanna@HUAWEI.COM>
Organization: huawei
Subject: Re: some doubt about use of instance-id with vlink in OSPFV3
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To:  <04c501c4a6e8$5d5e9680$0202a8c0@aceeinspiron>
Precedence: list
Content-Transfer-Encoding: 7BIT

Hi Acee
   Your answer is bit confusing
   In first case(where Vlink is configured without instance-id) you say
the instance-id is not matched. And in the second case (where Vlink is
configured with instance-id) you say the in/out interface's instance id
should match with the instance-id of the Vlink

Or You mean that instance id of the V-link configuration should be same
at both ends

I.e
For example consider I have configured vlink between RTA and RTB as
follows
! RTA
  ipv6 router ospf 1
       router-id 1.1.1.1
       area 1 v-link 2.2.2.2 instance-id y
! RTB
  ipv6 router ospf 1
       router-id 2.2.2.2
       area 1 v-link 1.1.1.1 instance-id x

Here in this case, x and y should be same. Am I right?

Thanx and Regards
Prasanna


-----Original Message-----
From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM] On Behalf Of Acee
Lindem
Sent: Thursday, September 30, 2004 5:54 PM
To: OSPF@PEACH.EASE.LSOFT.COM
Subject: Re: some doubt about use of instance-id with vlink in OSPFV3

> ----- Original Message -----
> From: prasanna
> To: OSPF@PEACH.EASE.LSOFT.COM
> Sent: Thursday, September 30, 2004 2:09 AM
> Subject: some doubt about use of instance-id with vlink in OSPFV3
>
>
> While sending the OSPFv3 packet for virtual-link, those packets will
have instance-id zero (if the virtual-link is not configured
> with instance-id).

Yes.

> If there are multiple processes attached to an incoming interface, to
which process the hello packet is delivered?

The virtual link interface - you DON'T match instance ID on the incoming
interface. Just assure that it is
configured in the transit area for the virtual link.

> To all the process/ only to the process to which the interface is
attached with instance-id zero?
>
> One more doubt. When I configure a virtual-link with instance-id (n),
should both sender's and receiver's interfaces should be
> configured with same > instance-id(n)

Of course.

Hope this helps,
Acee


From owner-ospf@PEACH.EASE.LSOFT.COM  Thu Sep 30 10:29:34 2004
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 KAA26114
	for <ospf-archive@LISTS.IETF.ORG>; Thu, 30 Sep 2004 10:29:33 -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 <10.00E9A29D@cherry.ease.lsoft.com>; Thu, 30 Sep 2004 10:29:34 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 37985385 for OSPF@PEACH.EASE.LSOFT.COM;
          Thu, 30 Sep 2004 10:29:30 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Thu, 30 Sep 2004 10:29:30 -0400
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com
          (Postfix) with ESMTP id 9EE0A8B4998 for <OSPF@PEACH.EASE.LSOFT.COM>;
          Thu, 30 Sep 2004 07:29:31 -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 19205-05 for 
          <OSPF@PEACH.EASE.LSOFT.COM>; Thu, 30 Sep 2004 07:29:31 -0700 (PDT)
Received: from aceeinspiron (unknown [172.31.253.67]) by prattle.redback.com
          (Postfix) with SMTP id E02C08B4997 for <OSPF@PEACH.EASE.LSOFT.COM>;
          Thu, 30 Sep 2004 07:29:30 -0700 (PDT)
References:  <000201c4a6ec$43603e10$8804120a@KSProsonna>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
              reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Virus-Scanned: by amavisd-new at redback.com
Message-ID:  <055501c4a6f9$d5edb750$0202a8c0@aceeinspiron>
Date:         Thu, 30 Sep 2004 10:29:03 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Re: some doubt about use of instance-id with vlink in OSPFV3
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

Hi Prasanna,

----- Original Message -----
From: "prasanna" <KSPrasanna@HUAWEI.COM>
To: <OSPF@PEACH.EASE.LSOFT.COM>
Sent: Thursday, September 30, 2004 8:51 AM
Subject: Re: some doubt about use of instance-id with vlink in OSPFV3


> Hi Acee
>   Your answer is bit confusing
>   In first case(where Vlink is configured without instance-id) you say
> the instance-id is not matched. And in the second case (where Vlink is
> configured with instance-id) you say the in/out interface's instance id
> should match with the instance-id of the Vlink

No confusion - in the first case the instance-id is 0 and in the second
case it is non-0.

>
> Or You mean that instance id of the V-link configuration should be same
> at both ends

Exactly.

>
> I.e
> For example consider I have configured vlink between RTA and RTB as
> follows
> ! RTA
>  ipv6 router ospf 1
>       router-id 1.1.1.1
>       area 1 v-link 2.2.2.2 instance-id y
> ! RTB
>  ipv6 router ospf 1
>       router-id 2.2.2.2
>       area 1 v-link 1.1.1.1 instance-id x
>
> Here in this case, x and y should be same. Am I right?

Yes - packet will be delivered iff (x == y).


>
> Thanx and Regards
> Prasanna
>
>
> -----Original Message-----
> From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM] On Behalf Of Acee
> Lindem
> Sent: Thursday, September 30, 2004 5:54 PM
> To: OSPF@PEACH.EASE.LSOFT.COM
> Subject: Re: some doubt about use of instance-id with vlink in OSPFV3
>
>> ----- Original Message -----
>> From: prasanna
>> To: OSPF@PEACH.EASE.LSOFT.COM
>> Sent: Thursday, September 30, 2004 2:09 AM
>> Subject: some doubt about use of instance-id with vlink in OSPFV3
>>
>>
>> While sending the OSPFv3 packet for virtual-link, those packets will
> have instance-id zero (if the virtual-link is not configured
>> with instance-id).
>
> Yes.
>
>> If there are multiple processes attached to an incoming interface, to
> which process the hello packet is delivered?
>
> The virtual link interface - you DON'T match instance ID on the incoming
> interface. Just assure that it is
> configured in the transit area for the virtual link.
>
>> To all the process/ only to the process to which the interface is
> attached with instance-id zero?
>>
>> One more doubt. When I configure a virtual-link with instance-id (n),
> should both sender's and receiver's interfaces should be
>> configured with same > instance-id(n)
>
> Of course.
>
> Hope this helps,
> Acee


From owner-ospf@PEACH.EASE.LSOFT.COM  Thu Sep 30 11:56:22 2004
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 LAA03096
	for <ospf-archive@LISTS.IETF.ORG>; Thu, 30 Sep 2004 11:56:22 -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 <0.00E9A4AC@cherry.ease.lsoft.com>; Thu, 30 Sep 2004 11:56:23 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 37995546 for OSPF@PEACH.EASE.LSOFT.COM;
          Thu, 30 Sep 2004 11:56:22 -0400
Received: from 61.144.161.40 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with
          TCP; Thu, 30 Sep 2004 11:56:21 -0400
Received: from DE (huawei.com [172.17.1.62]) by mta0.huawei.com (iPlanet
          Messaging Server 5.2 HotFix 1.21 (built Sep  8 2003)) with ESMTPA id
          <0I4V00MA41ZYUL@mta0.huawei.com> for OSPF@PEACH.EASE.LSOFT.COM; Thu,
          30 Sep 2004 23:35:59 +0800 (CST)
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.6626
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-imss-version: 2.7
X-imss-result: Passed
X-imss-approveListMatch: *@huawei.com
Message-ID:  <002801c4a703$72bb1420$8704120a@DE>
Date:         Thu, 30 Sep 2004 21:07:51 +0530
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Santosh Esale <santosh_e@HUAWEI.COM>
Organization: HTIPL
Subject: Re: Cost involved in running SPF
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To:  <ce8d9033040930051160b5c35d@mail.gmail.com>
Precedence: list
Content-Transfer-Encoding: 7BIT

Hi Abhishek,
           I think in case of ABR,if we receive type-3 LSA's from backbone
area , we need to calculate the route for these LSA's as well GENERATE
type-3 LSA's to be flooded into other non backbone ares in SPF, so its bit
costly compare to type-5 LSA's which is only used for calculating routes and
not for regenerating as well ASBR orginates external LSA's in other routine
and not is SPF.....so I guess receiving too many type-3 LSA's is costly in
some routers(ABR) compare to type-5 in SPF.

Thanks
Santosh

-----Original Message-----
From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM] On Behalf Of Abhishek
Verma
Sent: Thursday, September 30, 2004 5:41 PM
To: OSPF@PEACH.EASE.LSOFT.COM
Subject: Cost involved in running SPF

Hi,

Is there a difference in cost involved in running the SPF for AS
External LSAs vis-a-vis the normal Type 1 or 2 LSAs?

My question is, that what is more expensive for an OSPF router?
Receiving too many Type 5 LSAs or say, Type 3 LSAs?

Or is there no difference at all?

Cheers,
Abhishek