Re: type-5 las extarnal-tag field

Dave Katz <dkatz@JUNIPER.NET> Fri, 15 July 2005 02:32 UTC

Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtFzi-0005CI-0B for ospf-archive@megatron.ietf.org; Thu, 14 Jul 2005 22:32:06 -0400
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 WAA00947 for <ospf-archive@LISTS.IETF.ORG>; Thu, 14 Jul 2005 22:32: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 <3.010A71F0@cherry.ease.lsoft.com>; Thu, 14 Jul 2005 22:32:03 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.4) with spool id 79146757 for OSPF@PEACH.EASE.LSOFT.COM; Thu, 14 Jul 2005 22:32:00 -0400
Received: from 207.17.137.57 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0m) with TCP; Thu, 14 Jul 2005 22:32:00 -0400
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id j6F2W0976673 for <OSPF@PEACH.EASE.LSOFT.COM>; Thu, 14 Jul 2005 19:32:00 -0700 (PDT) (envelope-from dkatz@juniper.net)
Received: from [172.16.12.139] (nimbus-sf.juniper.net [172.16.12.139]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j6F2VsQ35185 for <OSPF@PEACH.EASE.LSOFT.COM>; Thu, 14 Jul 2005 19:31:54 -0700 (PDT) (envelope-from dkatz@juniper.net)
Mime-Version: 1.0 (Apple Message framework v733)
References: <44CF9D8D25966C4DB1072958419273DB40682C@aunswa002.au.tcnz.net>
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.733)
Message-ID: <228ACFCD-0B8E-425A-A977-8DC9C7F6D0D0@juniper.net>
Date: Thu, 14 Jul 2005 20:31:53 -0600
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Dave Katz <dkatz@JUNIPER.NET>
Subject: Re: type-5 las extarnal-tag field
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <44CF9D8D25966C4DB1072958419273DB40682C@aunswa002.au.tcnz.net>
Precedence: list
Content-Transfer-Encoding: 7bit

Back in prehistory (end of the Reagan years), this was known as the  
"Milo Word" (since Milo Medin was the guy who wanted it put in  
there.)  It was originally intended to be a pre-BGP way of  
controlling external route distribution, by carrying an AS number  
(for example.)  The choice of which externals to distribute back out  
of the domain was made in part by tags added at the point where the  
routes came in.  Yes, in those days people did inject full Internet  
routing into their IGP, but it was a smaller, slower world back then.

Now it's sort of a Rorschach test for routing interactions.


On Jul 14, 2005, at 7:54 PM, Paresh Khatri wrote:

> HI Ajay,
>
> The external route tag is not used by OSPF itself.  It is  
> transparently conveyed with type-5/type-7 LSAs so that applications  
> can make any desired use of it.  One particular application is when  
> you are doing two-way redistribution at multiple points.  In such a  
> case, you could associate a certain tag when redistributing routes  
> into OSPF.  That way, when you are redistributing *from* OSPF into  
> another protocol at some other redistribution point, you can dis- 
> regard the routes that have that tag associated with it.
>
> HTH,
> Paresh.
>
>
>
> -----Original Message-----
> From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM]On Behalf Of  
> tajay
> Sent: Thursday, 14 July 2005 12:07 AM
> To: OSPF@PEACH.EASE.LSOFT.COM
> Subject: type-5 las extarnal-tag field
>
>
> hi guys,
> I am not clear about extarnal-route-tag field in the type-5 lsa.  Can
> anyone  just give me some information about that. Also what should be
> the default value of the tag field? where it is useful ..?
>
> thanks
> ajay
>
>
> This communication, including any attachments, is confidential. If
>  you are not the intended recipient, you should not read it - please
>  contact me immediately, destroy it, and do not copy or use any  
> part of
>  this communication or disclose anything about it.
>
>
>