Re: RFC 2328 : Appendix E
Acee Lindem <acee@REDBACK.COM> Wed, 13 August 2003 12:08 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 IAA16706 for <ospf-archive@LISTS.IETF.ORG>; Wed, 13 Aug 2003 08:08:15 -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 <2.00AD666D@cherry.ease.lsoft.com>; Wed, 13 Aug 2003 8:08:11 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 51065512 for OSPF@PEACH.EASE.LSOFT.COM; Wed, 13 Aug 2003 08:06:53 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Wed, 13 Aug 2003 08:06:52 -0400
Received: from redback.com (login005.redback.com [155.53.12.60]) by prattle.redback.com (Postfix) with ESMTP id 04A21442123 for <OSPF@PEACH.EASE.LSOFT.COM>; Wed, 13 Aug 2003 05:05:16 -0700 (PDT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <20030813081554.19730.qmail@webmail35.rediffmail.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID: <3F3A29A0.6090709@redback.com>
Date: Wed, 13 Aug 2003 08:05:52 -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: RFC 2328 : Appendix E
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <20030813081554.19730.qmail@webmail35.rediffmail.com>
Precedence: list
Content-Transfer-Encoding: 7bit
Vivek Dubey wrote: > Printing LSAs from e.g in previous mail : > > 1) LS2 : 10.0.255.255/16 ; Fwd Addr N1; Metric 10; Type 1; > originated by R1 > > 2) LS1 : 10.0.0.0/16 ; Fwd Addr N1; Metric 10; Type 1; > originated by R2. > > Masks are same here and also the destination advertised > (Though Link State Id at OSPF level might be different). > So they should be functionally equivalent. Ok - misread your E-mail. They both advertise the same destination and will both need to be considered when calculating the route to prefix 10.0.0.0/16. > > Or i am misisng a point!!! > > Vivek > > > On Wed, 13 Aug 2003 Acee Lindem wrote : > >> Hi Vivek, >> >> Vivek Dubey wrote: >> >>> Hi Acee, >>> Continuing the thread: >>> Router R1 originates AS Ext LSAs: >>> LS1 : 10.0.0.0/8 >>> LS2 : 10.0.255.255/16 ; Fwd Addr N1; Metric 10; Type 1 >>> >>> Router R2 originates AS Ext LSA: >>> LS1 : 10.0.0.0/16 ; Fwd Addr N1; Metric 10; Type 1 >>> >>> 1)Now are LS2(R1) and LS1(R2) functionally equivalent ?? >> >> >> No - the masks in the body of the LSA are different. >> >>> >>> 2)Further is there a possibility of routers, >>> with some supporting Appendix E and others not, >>> being present in same domain ?? >> >> >> Yes. An OSPFv2 router can't make any assumptions regarding >> te setting of the host bits in the Link State ID for type 3 >> or 5 LSA's originated by another router. Incremental SPF >> computations must take this fact into account. >> >>> >>> Vivek >>> >>> >>> >>> >>> >>> On Wed, 06 Aug 2003 Acee Lindem wrote : >>> >>>> Hi Vivek, >>>> >>>> It might be a bit clearer as you suggest but the outcome >>>> is the same. The description is from the perspective of the >>>> LSAs while the example is from the perspective of >>>> routes which need to be advertised. >>>> >>>> >>>> Vivek Dubey wrote: >>>> >>>>> Conflict in description and example ?? >>>>> >>>>> RFC 2328:Appendix E >>>>> -------------------- >>>>> (2) >>>>> Obtain the network mask from the body of the already >>>>> existing >>>>> AS-external-LSA. Call this mask NM2. There are then two >>>>> cases: >>>>> >>>>> o NM2 is longer than NM1. In this case, change the >>>>> existing >>>>> LSA (having Link State ID of NA) to reference >>>>> the >>>>> new >>>>> network [NA,NM1] by incrementing the sequence >>>>> number, >>>>> changing the mask in the body to NM1 and inserting the >>>>> cost >>>>> of the new network. Then originate a new LSA for >>>>> the >>>>> old >>>>> network [NA,NM2], with Link State ID equal to NA >>>>> or'ed >>>>> together with the bits that are not set in NM2 >>>>> (i.e., >>>>> network [NA,NM2]'s broadcast address). >>>>> >>>>> As an example of the algorithm, consider its operation when >>>>> the >>>>> following sequence of events occurs in a single router >>>>> (Router >>>>> A). >>>>> (1) Router A wants to originate an AS-external-LSA for >>>>> [10.0.0.0,255.255.255.0]: >>>>> (a) A Link State ID of 10.0.0.0 is used. >>>>> >>>>> (2) Router A then wants to originate an AS-external-LSA for >>>>> [10.0.0.0,255.255.0.0]: >>>>> >>>>> (a) The LSA for [10.0.0,0,255.255.255.0] is >>>>> reoriginated >>>>> using a new Link State ID of 10.0.0.255. >>>>> >>>>> (b) A Link State ID of 10.0.0.0 is used for >>>>> [10.0.0.0,255.255.0.0]. >>>>> >>>>> vivek>> >>>>> Point (2) in e.g should be: >>>>> a) Reoriginate existing LSA with >>>>> 10.0.0.0 [10.0.0.0, 255.255.0.0], incrementing >>>>> sequence number,changing the mask in the body, and >>>>> inserting the cost of new network. >>>>> >>>>> b) Originate a new LSA for LsId >>>>> 10.0.0.255 [10.0.0.0, 255.255.255.0] >>>>> >>>>> >>>>> Vivek >>>>> >>>>> ___________________________________________________ >>>>> Download the hottest & happening ringtones here! >>>>> OR SMS: Top tone to 7333 >>>>> Click here now: >>>>> http://sms.rediff.com/cgi-bin/ringtone/ringhome.pl >>>>> >>>> >>>> -- >>>> Acee >>> >>> >>> >>> ___________________________________________________ >>> Meet your old school or college friends from >>> 1 Million + database... >>> Click here to reunite www.batchmates.com/rediff.asp >>> >> >> -- >> Acee > > > ___________________________________________________ > Meet your old school or college friends from > 1 Million + database... > Click here to reunite www.batchmates.com/rediff.asp > -- Acee
- RFC 2328 : Appendix E Vivek Dubey
- Re: RFC 2328 : Appendix E Acee Lindem
- Re: RFC 2328 : Appendix E Vivek Dubey
- Re: RFC 2328 : Appendix E Acee Lindem
- Re: RFC 2328 : Appendix E Vivek Dubey
- Re: RFC 2328 : Appendix E Acee Lindem