Re: Secondary IP address

Acee Lindem <acee@REDBACK.COM> Wed, 11 June 2003 13:12 UTC

Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07592 for <ospf-archive@LISTS.IETF.ORG>; Wed, 11 Jun 2003 09:12:45 -0400 (EDT)
Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <3.00A0D7AA@cherry.ease.lsoft.com>; Wed, 11 Jun 2003 9:12:44 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 45299259 for OSPF@PEACH.EASE.LSOFT.COM; Wed, 11 Jun 2003 09:11:47 -0400
Received: from 24.93.67.83 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Wed, 11 Jun 2003 09:11:45 -0400
Received: from redback.com (rdu162-240-050.nc.rr.com [24.162.240.50]) by ms-smtp-02.southeast.rr.com (8.12.5/8.12.2) with ESMTP id h5BD93UD003776 for <OSPF@PEACH.EASE.LSOFT.COM>; Wed, 11 Jun 2003 09:09:04 -0400 (EDT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <20030611112343.29951.qmail@webmail27.rediffmail.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID: <3EE72A8C.4060904@redback.com>
Date: Wed, 11 Jun 2003 09:11:40 -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: Secondary IP address
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

Hi Krishna,

Krishna Rao wrote:
> Hi,
>       Secondary IP address usage in OSPF is little shaddy.

Paraphrasing Mark Twain, "The rumors of the lack of OSPF
support for secondary addresses are greatly exaggerated."

OSPFv2 runs a subnet and makes no distinction as to whether or
not the subnet is primary or secondary. There is at least one
heavily deployed implementation that doesn't support OSPF on
secondary addresses.

 From section 1.2 of RFC 2328:

         Network
             In this memo, an IP network/subnet/supernet.  It is possible
             for one physical network to be assigned multiple IP
             network/subnet numbers.  We consider these to be separate
             networks.  Point-to-point physical networks are an exception
             - they are considered a single network no matter how many
             (if any at all) IP network/subnet numbers are assigned to
             them.

         Interface
             The connection between a router and one of its attached
             networks.  An interface has state information associated
             with it, which is obtained from the underlying lower level
             protocols and the routing protocol itself.  An interface to
             a network has associated with it a single IP address and
             mask (unless the network is an unnumbered point-to-point
             network).  An interface is sometimes also referred to as a
             link.

> Should
> we allow secondary address to be advertised in point-to-point and
> point-to-multipoint?

 From the above, it seems the answer should be yes for P2MP and no
for P2P. However, in our implementation we do allow OSPF
to be configured on multiple subnets on a P2P interface. This
allows the P2P interface to be an intra-area link in more than one
area.

>
> Regards,
> Krishna
> ___________________________________________________
> Get email that means BUSINESS! me @ mycompany.com.
> Just Rs.1499/year.
> To start, click http://www.rediffmailpro.com
>


--
Acee