Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id LAA27782 for ; Tue, 21 Nov 2000 11:54:35 -0500 (EST) Received: by segue.merit.edu (Postfix) id 12CCD5DDD6; Tue, 21 Nov 2000 11:54:10 -0500 (EST) Delivered-To: idr-outgoing@merit.edu Received: by segue.merit.edu (Postfix, from userid 56) id F2A685DDA0; Tue, 21 Nov 2000 11:54:09 -0500 (EST) Received: from cisco.com (omega.cisco.com [171.69.63.141]) by segue.merit.edu (Postfix) with ESMTP id 5B04F5DDD6 for ; Tue, 21 Nov 2000 11:54:08 -0500 (EST) Received: from localhost (yakov@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id IAA15497 for ; Tue, 21 Nov 2000 08:54:07 -0800 (PST) Message-Id: <200011211654.IAA15497@cisco.com> To: idr@merit.edu Subject: List of the Current BGP Documents MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <15495.974825647.1@cisco.com> Date: Tue, 21 Nov 2000 08:54:07 -0800 From: Yakov Rekhter Sender: owner-idr@merit.edu Precedence: bulk fyi ------- Forwarded Message Date: Tue, 21 Nov 2000 05:55:18 -0500 From: Internet-Drafts@ietf.org To: IETF-Announce: ; Subject: I-D ACTION:draft-chen-bgp-reference-00.txt - --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : List of the Current BGP Documents Author(s) : E. Chen, Y. Rekhter Filename : draft-chen-bgp-reference-00.txt Pages : 8 Date : 20-Nov-00 This document lists the most recent RFCs and Internet Drafts that are related to the BGP protocol and its applications. It is expected that this document will be updated on a on-going basis. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-chen-bgp-reference-00.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-chen-bgp-reference-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-chen-bgp-reference-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. - --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" - --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20001120151115.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-chen-bgp-reference-00.txt - --OtherAccess Content-Type: Message/External-body; name="draft-chen-bgp-reference-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20001120151115.I-D@ietf.org> - --OtherAccess-- - --NextPart-- ------- End of Forwarded Message Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id KAA03926 for ; Mon, 20 Nov 2000 10:04:20 -0500 (EST) Received: by segue.merit.edu (Postfix) id 57E735DE6A; Mon, 20 Nov 2000 10:02:07 -0500 (EST) Delivered-To: idr-outgoing@merit.edu Received: by segue.merit.edu (Postfix, from userid 56) id 457A35DE87; Mon, 20 Nov 2000 10:02:07 -0500 (EST) Received: from mailrelay00.aa.ops.us.uu.net (mailrelay00.aa.ops.us.uu.net [147.225.22.28]) by segue.merit.edu (Postfix) with ESMTP id 9D18E5DE6A for ; Mon, 20 Nov 2000 10:02:05 -0500 (EST) Received: from tenornetworks.com (rtu.tenornetworks.com [63.77.213.2]) by mailrelay00.aa.ops.us.uu.net (8.9.3/8.9.3) with ESMTP id KAA08245 for ; Mon, 20 Nov 2000 10:02:05 -0500 (EST) Received: from tenornet.com (newman [192.168.0.185]) by tenornetworks.com (Switch-2.1.0/Switch-2.1.0) with SMTP id eAKF22v20642; Mon, 20 Nov 2000 10:02:03 -0500 (EST) Received: from 192.168.0.185 by tenornet.com; MON, 20 Nov 2000 09:51:48 -0700 Received: by newman.tenornet.com with Internet Mail Service (5.5.2650.21) id ; Mon, 20 Nov 2000 09:51:48 -0500 Message-ID: <6B190B34070BD411ACA000B0D0214E563A80F8@newman.tenornet.com> From: "Shah, Himanshu" To: "'subodh@samsung.co.kr'" , bgp@ans.net Subject: RE: bgp-igp doubts Date: Mon, 20 Nov 2000 09:51:40 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-idr@merit.edu Precedence: bulk question 1) In Cisco's language, use "network" command to import routes into the BGP. As and when the IGP routes are placed/removed in/from the routing table, BGP will advertise/withdraw these routes to its peers. Use this command in both BGP routers A and C in AS200. You can also use "redistribute" command to import route from your IGP to BGP. Since this is one way leak, it would not destabilize your AS. Your router should have similar features to do the same. question 2) If all your routers within an AS speaks IBGP and they import (aka cisco's "network") directly connected networks, your IBGP+EBGP router (e.g. A and C) will know of all networks within your AS via IBGP peers. A couple of important things to remember here is IBGP requires to be of full mesh of peers and "network" command is necessary to import all (including stub) networks. Himanshu Tenor Networks Acton, Mass -----Original Message----- From: subodh@samsung.co.kr [mailto:subodh@samsung.co.kr] Sent: Saturday, November 18, 2000 5:08 AM To: bgp@ans.net Subject: bgp-igp doubts BGP-IGP interaction doubt 1: ibgp between a,c e----------------------------A----------B-----------C----------------------- ---d ebgp ospf ospf bgp As100 As200 As300 As 200 is having three routers A,B,C a and c are multiprotocol router. As100 is having one router e As300 is having one router d Inside our AS 200 we are running igp (we have igp domain ex. rip, ospf etc) and have 20 NLRI. We want to advertise our NLRI to AS100 and As 200 via bgp. could you pl. explan how router A and C should take igp domain information and advertise NLRI without creating instability inside the AS. doubt 2; In rfc-1772, a.2.4 pervassive bgp example is given. It says if all routers in AS are bgp speaker, there is no need to have any interaction between bgp and igp. I am unabe to visualise pervassive bgp. coud you pl. explain with diagram how the routing will take place. If possibe pl mentioned the reference material. bye, subodh.. Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id HAA02253 for ; Mon, 20 Nov 2000 07:24:15 -0500 (EST) Received: by segue.merit.edu (Postfix) id 1A1B25DE5B; Mon, 20 Nov 2000 07:23:42 -0500 (EST) Delivered-To: idr-outgoing@merit.edu Received: by segue.merit.edu (Postfix, from userid 56) id E87505DE5C; Mon, 20 Nov 2000 07:23:41 -0500 (EST) Received: from mailrelay00.aa.ops.us.uu.net (mailrelay00.aa.ops.us.uu.net [147.225.22.28]) by segue.merit.edu (Postfix) with ESMTP id 390A95DE5B for ; Mon, 20 Nov 2000 07:23:40 -0500 (EST) Received: from omail01.samsung.co.kr (omail01.samsung.co.kr [203.254.197.73]) by mailrelay00.aa.ops.us.uu.net (8.9.3/8.9.3) with ESMTP id HAA29889 for ; Mon, 20 Nov 2000 07:23:38 -0500 (EST) From: subodh@samsung.co.kr Received: from localhost (root@localhost) by gp_xman. (8.8.8H1/8.8.8) with ESMTP id VAA22511 for ; Mon, 20 Nov 2000 21:24:49 +0900 (KST) X-OpenMail-Hops: 2 Date: Mon, 20 Nov 2000 20:19:08 +0900 Message-Id: In-Reply-To: <3A18FEC1.D0293C72@lucent.com> Subject: (Reply) Re: (Reply) Re: bgp-igp doubts MIME-Version: 1.0 To: bgp@ans.net Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline; filename="mail.txt" ;Creation-Date="Mon, 20 Nov 2000 16:06:49 +0530" ;Modification-Date="Mon, 20 Nov 2000 20:18:56 +0900" Content-Transfer-Encoding: 8bit Sender: owner-idr@merit.edu Precedence: bulk oops! when b advertises to a, a will not process, till it knows route to c thru some means (IGP/static) so, a cant reach d. BTW, pl. put the questions to group. --Siva S Kotthapalli subodh@samsung.co.kr wrote: > > q2: if b is also capable of speaking bgp, the rule says to run ibgp for router inside AS which does not advertise next hop as a self . so how router A will be abe to reach > router C fr destinatin d. > > q1. check the documentation of ur router. > u'll find some means of redistributing the routing info from IGP to > BGP > > q2. in ur diagram, if router b is also capable of speaking bgp then u > dont need any igp. > > hope this helps > > --Siva S Kotthapalli > > subodh@samsung.co.kr wrote: > > > > BGP-IGP interaction > > > > doubt 1: > > > > ibgp between a,c > > e----------------------------A----------B-----------C--------------------------d > > ebgp ospf ospf bgp > > > > As100 As200 As300 > > > > As 200 is having three routers A,B,C > > a and c are multiprotocol router. > > > > As100 is having one router e > > As300 is having one router d > > > > Inside our AS 200 we are running igp (we have igp domain ex. rip, ospf etc) and have 20 NLRI. We want to advertise our NLRI to AS100 and As 200 via bgp. > > > > could you pl. explan how router A and C should take igp domain information and advertise NLRI without creating instability inside the AS. > > > > doubt 2; > > > > In rfc-1772, a.2.4 pervassive bgp example is given. > > > > It says if all routers in AS are bgp speaker, there is no need to have any interaction between bgp and igp. I am unabe to visualise pervassive bgp. > > coud you pl. explain with diagram how the routing will take place. > > > > If possibe pl mentioned the reference material. > > > > bye, > > subodh.. > > -- > --Siva S Kotthapalli, Infosys India. > Tel- H: 91-80-6342709 W:91-80-8520261 > /* If you don't have an engineer on your side to balance out the > changes made by the other, that's when you have problems.*/ -- --Siva S Kotthapalli, Infosys India. Tel- H: 91-80-6342709 W:91-80-8520261 /* If you don't have an engineer on your side to balance out the changes made by the other, that's when you have problems.*/ Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id BAA27846 for ; Mon, 20 Nov 2000 01:23:59 -0500 (EST) Received: by segue.merit.edu (Postfix) id C61F85DD9D; Mon, 20 Nov 2000 01:23:31 -0500 (EST) Delivered-To: idr-outgoing@merit.edu Received: by segue.merit.edu (Postfix, from userid 56) id AF7EB5DDA4; Mon, 20 Nov 2000 01:23:31 -0500 (EST) Received: from mailrelay00.aa.ops.us.uu.net (mailrelay00.aa.ops.us.uu.net [147.225.22.28]) by segue.merit.edu (Postfix) with ESMTP id E0F065DD9D for ; Mon, 20 Nov 2000 01:23:29 -0500 (EST) Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1]) by mailrelay00.aa.ops.us.uu.net (8.9.3/8.9.3) with ESMTP id BAA15104 for ; Mon, 20 Nov 2000 01:23:29 -0500 (EST) Received: from fw-ext.ascend.com (fw-ext [198.4.92.5]) by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id WAA03039; Sun, 19 Nov 2000 22:15:05 -0800 (PST) Received: from russet.ascend.com by fw-ext.ascend.com via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 20 Nov 2000 06:23:06 UT Received: from wopr.eng.ascend.com (wopr.eng.ascend.com [206.65.212.178]) by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id WAA26062; Sun, 19 Nov 2000 22:23:05 -0800 (PST) Received: from india.ascend.com (indiamail.india.ascend.com [192.168.64.198]) by wopr.eng.ascend.com (8.9.1/8.9.1) with ESMTP id WAA13478; Sun, 19 Nov 2000 22:22:55 -0800 (PST) Received: from lucent.com (pawnee.india.ascend.com [192.168.64.52]) by india.ascend.com (8.8.8+Sun/8.8.8) with ESMTP id LAA25146; Mon, 20 Nov 2000 11:52:48 +0530 (IST) Message-ID: <3A18C338.20CD73C7@lucent.com> Date: Mon, 20 Nov 2000 11:52:48 +0530 From: Siva S Kotthapalli Organization: Lucent INS X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.5.1 i86pc) X-Accept-Language: en MIME-Version: 1.0 To: subodh@samsung.co.kr Cc: bgp@ans.net Subject: Re: bgp-igp doubts References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-idr@merit.edu Precedence: bulk q1. check the documentation of ur router. u'll find some means of redistributing the routing info from IGP to BGP q2. in ur diagram, if router b is also capable of speaking bgp then u dont need any igp. hope this helps --Siva S Kotthapalli subodh@samsung.co.kr wrote: > > BGP-IGP interaction > > doubt 1: > > ibgp between a,c > e----------------------------A----------B-----------C--------------------------d > ebgp ospf ospf bgp > > As100 As200 As300 > > As 200 is having three routers A,B,C > a and c are multiprotocol router. > > As100 is having one router e > As300 is having one router d > > Inside our AS 200 we are running igp (we have igp domain ex. rip, ospf etc) and have 20 NLRI. We want to advertise our NLRI to AS100 and As 200 via bgp. > > could you pl. explan how router A and C should take igp domain information and advertise NLRI without creating instability inside the AS. > > doubt 2; > > In rfc-1772, a.2.4 pervassive bgp example is given. > > It says if all routers in AS are bgp speaker, there is no need to have any interaction between bgp and igp. I am unabe to visualise pervassive bgp. > coud you pl. explain with diagram how the routing will take place. > > If possibe pl mentioned the reference material. > > bye, > subodh.. -- --Siva S Kotthapalli, Infosys India. Tel- H: 91-80-6342709 W:91-80-8520261 /* If you don't have an engineer on your side to balance out the changes made by the other, that's when you have problems.*/ Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id FAA18369 for ; Sat, 18 Nov 2000 05:19:34 -0500 (EST) Received: by segue.merit.edu (Postfix) id 8E3665DDB0; Sat, 18 Nov 2000 05:19:09 -0500 (EST) Delivered-To: idr-outgoing@merit.edu Received: by segue.merit.edu (Postfix, from userid 56) id 7A43E5DD9B; Sat, 18 Nov 2000 05:19:09 -0500 (EST) Received: from omail01.samsung.co.kr (omail01.samsung.co.kr [203.254.197.73]) by segue.merit.edu (Postfix) with ESMTP id 292C15DD93 for ; Sat, 18 Nov 2000 05:19:07 -0500 (EST) From: subodh@samsung.co.kr Received: from localhost (root@localhost) by gp_xman. (8.8.8H1/8.8.8) with ESMTP id TAA00670 for ; Sat, 18 Nov 2000 19:20:04 +0900 (KST) X-OpenMail-Hops: 2 Date: Sat, 18 Nov 2000 19:19:15 +0900 Message-Id: Subject: bgp-igp doubts MIME-Version: 1.0 To: ben@layer8.net Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline; filename="mail.txt" ;Creation-Date="Sat, 18 Nov 2000 19:16:56 +0900" ;Modification-Date="Sat, 18 Nov 2000 19:19:07 +0900" Content-Transfer-Encoding: 8bit Sender: owner-idr@merit.edu Precedence: bulk BGP-IGP interaction doubt 1: ibgp between a,c e----------------------------A----------B-----------C--------------------------d ebgp ospf ospf bgp As100 As200 As300 As 200 is having three routers A,B,C a and c are multiprotocol router. As100 is having one router e As300 is having one router d Inside our AS 200 we are running igp (we have igp domain ex. rip, ospf etc) and have 20 NLRI. We want to advertise our NLRI to AS100 and As 200 via bgp. could you pl. explan how router A and C should take igp domain information and advertise NLRI without creating instability inside the AS. doubt 2; In rfc-1772, a.2.4 pervassive bgp example is given. It says if all routers in AS are bgp speaker, there is no need to have any interaction between bgp and igp. I am unabe to visualise pervassive bgp. coud you pl. explain with diagram how the routing will take place. If possibe pl mentioned the reference material. bye, subodh.. Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id FAA17960 for ; Sat, 18 Nov 2000 05:08:40 -0500 (EST) Received: by segue.merit.edu (Postfix) id 95D3D5DD8F; Sat, 18 Nov 2000 05:08:04 -0500 (EST) Delivered-To: idr-outgoing@merit.edu Received: by segue.merit.edu (Postfix, from userid 56) id 6F1CA5DD93; Sat, 18 Nov 2000 05:08:04 -0500 (EST) Received: from mailrelay00.aa.ops.us.uu.net (mailrelay00.aa.ops.us.uu.net [147.225.22.28]) by segue.merit.edu (Postfix) with ESMTP id C96805DD8F for ; Sat, 18 Nov 2000 05:08:01 -0500 (EST) Received: from omail01.samsung.co.kr (omail01.samsung.co.kr [203.254.197.73]) by mailrelay00.aa.ops.us.uu.net (8.9.3/8.9.3) with ESMTP id FAA09014 for ; Sat, 18 Nov 2000 05:08:00 -0500 (EST) From: subodh@samsung.co.kr Received: from localhost (root@localhost) by gp_xman. (8.8.8H1/8.8.8) with ESMTP id TAA23811 for ; Sat, 18 Nov 2000 19:09:06 +0900 (KST) X-OpenMail-Hops: 2 Date: Sat, 18 Nov 2000 19:08:18 +0900 Message-Id: Subject: bgp-igp doubts MIME-Version: 1.0 To: bgp@ans.net Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline; filename="mail.txt" ;Creation-Date="Sat, 18 Nov 2000 18:39:37 +0900" ;Modification-Date="Sat, 18 Nov 2000 19:08:12 +0900" Content-Transfer-Encoding: 8bit Sender: owner-idr@merit.edu Precedence: bulk BGP-IGP interaction doubt 1: ibgp between a,c e----------------------------A----------B-----------C--------------------------d ebgp ospf ospf bgp As100 As200 As300 As 200 is having three routers A,B,C a and c are multiprotocol router. As100 is having one router e As300 is having one router d Inside our AS 200 we are running igp (we have igp domain ex. rip, ospf etc) and have 20 NLRI. We want to advertise our NLRI to AS100 and As 200 via bgp. could you pl. explan how router A and C should take igp domain information and advertise NLRI without creating instability inside the AS. doubt 2; In rfc-1772, a.2.4 pervassive bgp example is given. It says if all routers in AS are bgp speaker, there is no need to have any interaction between bgp and igp. I am unabe to visualise pervassive bgp. coud you pl. explain with diagram how the routing will take place. If possibe pl mentioned the reference material. bye, subodh.. Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id XAA05357 for ; Sat, 11 Nov 2000 23:21:32 -0500 (EST) Received: by segue.merit.edu (Postfix) id 2233E5DE00; Sat, 11 Nov 2000 23:21:06 -0500 (EST) Delivered-To: idr-outgoing@merit.edu Received: by segue.merit.edu (Postfix, from userid 56) id 0754B5DE0F; Sat, 11 Nov 2000 23:21:06 -0500 (EST) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by segue.merit.edu (Postfix) with ESMTP id 0514D5DE00 for ; Sat, 11 Nov 2000 23:21:05 -0500 (EST) Received: from randy by rip.psg.com with local (Exim 3.16 #1) id 13uodb-000LdT-00; Sat, 11 Nov 2000 20:21:03 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Yakov Rekhter Cc: idr@merit.edu, skh@nexthop.com Subject: Re: agenda items References: <200011120034.QAA27023@cisco.com> X-Mailer: VM 6.82 under Emacs 19.34.1 Message-Id: Date: Sat, 11 Nov 2000 20:21:03 -0800 Sender: owner-idr@merit.edu Precedence: bulk > Please submit proposed agenda items for the IDR WG meeting > in San Diego to me and Sue. approaches to the possible exhaustion of asns randy Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id TAA03097 for ; Sat, 11 Nov 2000 19:35:13 -0500 (EST) Received: by segue.merit.edu (Postfix) id C611B5DE19; Sat, 11 Nov 2000 19:34:48 -0500 (EST) Delivered-To: idr-outgoing@merit.edu Received: by segue.merit.edu (Postfix, from userid 56) id B67625DE0F; Sat, 11 Nov 2000 19:34:48 -0500 (EST) Received: from cisco.com (omega.cisco.com [171.69.63.141]) by segue.merit.edu (Postfix) with ESMTP id 7DC985DDFD for ; Sat, 11 Nov 2000 19:34:47 -0500 (EST) Received: from localhost (yakov@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id QAA27023; Sat, 11 Nov 2000 16:34:46 -0800 (PST) Message-Id: <200011120034.QAA27023@cisco.com> To: idr@merit.edu Cc: skh@nexthop.com, yakov@cisco.com Subject: agenda items MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <27021.973989286.1@cisco.com> Date: Sat, 11 Nov 2000 16:34:46 -0800 From: Yakov Rekhter Sender: owner-idr@merit.edu Precedence: bulk Folks, Please submit proposed agenda items for the IDR WG meeting in San Diego to me and Sue. Yakov. Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id JAA19372 for ; Mon, 6 Nov 2000 09:09:14 -0500 (EST) Received: by segue.merit.edu (Postfix) id 0283E5DDA6; Mon, 6 Nov 2000 09:08:42 -0500 (EST) Delivered-To: idr-outgoing@merit.edu Received: by segue.merit.edu (Postfix, from userid 56) id C77F15DDDD; Mon, 6 Nov 2000 09:08:41 -0500 (EST) Received: from tenornetworks.com (rtu.tenornetworks.com [63.77.213.2]) by segue.merit.edu (Postfix) with ESMTP id 9893C5DDA6 for ; Mon, 6 Nov 2000 09:08:39 -0500 (EST) Received: from tsillas (tsillas [192.168.0.133]) by tenornetworks.com (Switch-2.1.0/Switch-2.1.0) with SMTP id eA6E8cH09234 for ; Mon, 6 Nov 2000 09:08:38 -0500 (EST) Reply-To: From: "James Tsillas" To: "IDR" Subject: EGP Origin type Date: Mon, 6 Nov 2000 09:07:47 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-idr@merit.edu Precedence: bulk Does the EGP origin type refer to routes learned from _an_ EGP protocol (such as BGP) or does it refer to routes learned from _the_ EGP protocol (Cisco's EGP). I haven't been able to find a reference which is clear on this point. -Jim. Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id OAA15747 for ; Thu, 2 Nov 2000 14:12:08 -0500 (EST) Received: by segue.merit.edu (Postfix) id 969D35DD8D; Thu, 2 Nov 2000 14:11:39 -0500 (EST) Delivered-To: idr-outgoing@merit.edu Received: by segue.merit.edu (Postfix, from userid 56) id 741FA5DD9E; Thu, 2 Nov 2000 14:11:39 -0500 (EST) Received: from tenornetworks.com (rtu.tenornetworks.com [63.77.213.2]) by segue.merit.edu (Postfix) with ESMTP id DED065DD8D for ; Thu, 2 Nov 2000 14:11:37 -0500 (EST) Received: from tsillas (tsillas [192.168.0.133]) by tenornetworks.com (Pro-8.9.3/Pro-8.9.3) with SMTP id OAA20818 for ; Thu, 2 Nov 2000 14:11:37 -0500 (EST) Reply-To: From: "James Tsillas" To: "IDR" Subject: Setting ORIGIN Date: Thu, 2 Nov 2000 14:10:31 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-idr@merit.edu Precedence: bulk Can someone give guidance on how the ORIGIN attribute should be set? What are the circumstances when we want to set the attribute to IGP, EGP or INC. What are the default settings for redistributed or static routes? Why would we want to override the defaults? Also please comment on any difference between vendors in implementation that you know of. thanks much, -Jim.