Received: from cnri by ietf.org id aa11131; 8 Jul 97 12:25 EDT Received: from mailhost2.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid MAA07008 for ; Tue, 8 Jul 1997 12:24:14 -0400 (EDT) Received: from mailhost.BayNetworks.COM ([132.245.135.115]) by mailhost2.BayNetworks.COM (8.8.5/BNET-97/07/07-E) with ESMTP id JAA21650 Received: from lobster1.corpeast.Baynetworks.com (lobster1.corpeast.baynetworks.com [192.32.72.17]) by mailhost.BayNetworks.COM (8.8.5/BNET-97/07/07-I) with SMTP id JAA02599 Received: from marvin.corpeast.Baynetworks.com by lobster1.corpeast.Baynetworks.com (4.1/BNET-97/04/29-S) id AA07451; Tue, 8 Jul 97 12:18:58 EDT for andrew@extremenetworks.com Received: by marvin.corpeast.Baynetworks.com (4.1/SMI-4.1) id AA12548; Tue, 8 Jul 97 12:16:13 EDT Received: from lobster1.corpeast.Baynetworks.com by marvin.corpeast.Baynetworks.com (4.1/SMI-4.1) id AA12542; Tue, 8 Jul 97 16:16:11 GMT Received: from mailhost2.BayNetworks.COM (ext-ns1.baynetworks.com) by lobster1.corpeast.Baynetworks.com (4.1/BNET-97/04/29-S) id AA07034; Tue, 8 Jul 97 12:15:24 EDT for ietf-rip@marvin Received: from dss.com (titan.dss.com [192.41.217.8]) by mailhost2.BayNetworks.COM (8.8.5/BNET-97/07/07-E) with SMTP id JAA21487; Tue, 8 Jul 1997 09:10:26 -0700 (PDT) for Posted-Date: Tue, 8 Jul 1997 09:10:26 -0700 (PDT) Received: by dss.com (4.1/SMI-4.1) id AA29879; Tue, 8 Jul 97 12:16:06 EDT From: Dan Bronstein Message-Id: <9707081616.AA29879@dss.com> Subject: Triggered RIP ? To: ietf-rip@baynetworks.com Date: Tue, 8 Jul 1997 12:16:05 -0400 (EDT) Cc: Dan Bronstein X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-ietf-rip@baynetworks.com Precedence: bulk After reading over RFC 2091, I have a couple of questions and was hoping that someone could please answer them- Update Request are to be sent (and retransmitted until ack with rsp): 1) when router is powered on 2) when circuit manager detects state change of interface from down to up. ?s If peer does not acknowledge power on update request and a retransmit of the request goes out 5 seconds later and in this period of 5 seconds, the interface transitions from down to up, do you need to send out a second update request for this transition ? and do you have to hold off sending the second update request until the power on update request is ackd with a update rsp ? Update Response are to be sent with flush flags set (and retransmitted until ackd): 1) when router is powered on 2) in response to an update request packet. 3) when circuit manager detects state change of interface from down to up. ?s How does router know that response to an update request when first powered on is not the the update response packet that is suppose be sent when router is powered on ? If peer does not acknowledge power on update response and a retransmit of the response goes out 5 seconds later and in this period of 5 seconds, the interface transitions from down to up, do you need to send out a second update response for this transition ? and do you have to hold off sending the second update response until the power on update response is ackd with a update ack ? Thanks, Dan ------------------------------------------------------------------------------- Daniel Bronstein Access Beyond, Inc. e-mail: dan1@dss.com 1 Palmer Terrace tel: 201-438-2400 x255 Carlstadt, N.J. 07072 fax: 201-438-7767   Received: from cnri by ietf.org id aa03090; 9 Jul 97 5:59 EDT Received: from mailhost2.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid FAA09486 for ; Wed, 9 Jul 1997 05:58:16 -0400 (EDT) Received: from mailhost.BayNetworks.COM ([134.177.1.107]) by mailhost2.BayNetworks.COM (8.8.5/BNET-97/07/07-E) with ESMTP id CAA21668 Received: from lobster1.corpeast.Baynetworks.com (lobster1.corpeast.baynetworks.com [192.32.72.17]) by mailhost.BayNetworks.COM (8.8.5/BNET-97/07/07-I) with SMTP id CAA23243 Received: from marvin.corpeast.Baynetworks.com by lobster1.corpeast.Baynetworks.com (4.1/BNET-97/04/29-S) id AA01878; Wed, 9 Jul 97 05:51:54 EDT for andrew@extremenetworks.com Received: by marvin.corpeast.Baynetworks.com (4.1/SMI-4.1) id AA10348; Wed, 9 Jul 97 05:50:01 EDT Received: from lobster1.corpeast.Baynetworks.com by marvin.corpeast.Baynetworks.com (4.1/SMI-4.1) id AA10342; Wed, 9 Jul 97 09:49:59 GMT Received: from mailhost1.BayNetworks.COM (ext-ns2.baynetworks.com) by lobster1.corpeast.Baynetworks.com (4.1/BNET-97/04/29-S) id AA01788; Wed, 9 Jul 97 05:49:11 EDT for ietf-rip@marvin Received: from lynx.europe.shiva.com (lynx.europe.shiva.com [134.191.64.5]) by mailhost1.BayNetworks.COM (8.8.5/BNET-97/07/07-E) with ESMTP id CAA01293; Wed, 9 Jul 1997 02:49:05 -0700 (PDT) for Posted-Date: Wed, 9 Jul 1997 02:49:05 -0700 (PDT) Received: from eurohub.europe.shiva.com (eurohub.europe.shiva.com [134.191.64.200]) by lynx.europe.shiva.com (8.8.5/8.8.5) with ESMTP id KAA22582; Wed, 9 Jul 1997 10:48:24 +0100 (BST) Received: from Lotus Notes (PU Serial #1281) by eurohub.europe.shiva.com (PostalUnion/SMTP(tm) v2.1.7 for Windows NT(tm)) id AA-1997Jul09.084357.1281.529980; Wed, 09 Jul 1997 10:45:34 +0100 From: CN=Gerry Meyer/OU=Eng/OU=EDI/O=Shiva To: Dan Bronstein Cc: Ietf-Rip , Dan Bronstein Message-Id: <1997Jul09.084357.1281.529980@eurohub.europe.shiva.com> X-Conversion-Id: X-Mailer: Lotus Notes via PostalUnion/SMTP for Windows NT Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Organization: Shiva Europe Ltd Date: Wed, 09 Jul 1997 10:45:34 +0100 Subject: Re: Triggered RIP ? Sender: owner-ietf-rip@baynetworks.com Precedence: bulk Dan Bronstein 08/07/97 17:21 To: ietf-rip @ EUROGATE cc: Dan Bronstein @ EUROGATE Subject: Triggered RIP ? >After reading over RFC 2091, I have a couple of questions and was hoping that >someone could please answer them- >Update Request are to be sent (and retransmitted until ack with rsp): >1) when router is powered on >2) when circuit manager detects state change of interface from down to up. >?s >If peer does not acknowledge power on update request and a retransmit of >the request goes out 5 seconds later and in this period of 5 seconds, the >interface transitions from down to up, do you need to send out a second >update request for this transition ? and do you have to hold off sending the >second update request until the power on update request is ackd with a update >rsp ? Your 'assumption' is that the interface is DOWN when RIP initialises. The appropriate course is to assume the interface is (capable of being) UP, at the point where RIP initialises and sends out its initial update request. You will then determine pretty soon whether the assumption that it is UP was a valid one (either the update will get acknowledged or the interface will indicate that it failed and it will transition to DOWN). >Update Response are to be sent with flush flags set (and retransmitted until >ackd): >1) when router is powered on >2) in response to an update request packet. >3) when circuit manager detects state change of interface from down to up. >?s >How does router know that response to an update request when first powered >on is not the the update response packet that is suppose be sent when router >is powered on ? It shouldn't matter. It contains the desired information. >If peer does not acknowledge power on update response and a retransmit of >the response goes out 5 seconds later and in this period of 5 seconds, the >interface transitions from down to up, do you need to send out a second >update response for this transition ? and do you have to hold off sending the >second update response until the power on update response is ackd with a update >ack ? Is this not the same question as above? The routing protocol has a view of whether the peer is reachable or unreachable. If it thinks the peer is reachable it can transmit requests or responses. If it thinks it is unreachable it can not (does not) transmit them. In the meantime at the lower layers there may or may not be a call open to the peer. I am thinking here of something like an ISDN call - but a leased line interface when up would be regarded as an open call. Starting at initialisation with the peer being assumed to be reachable. The routing protocol sends out its request causing a call to be placed. When the call is open responses are exchanged. The call closes. The peer is still reachable. The call opens and closes many times. The peer remains reachable. Occasional responses are issued and acknowledged when routing topology changes. The peer remains unreachable. Then at some point a call fails (as a result of trying to forward data - or possibly when trying to issue a routing response). The lower layer flags this event to the routing protocols. The peer is now unreachable. The routing protocols suppress sending requests or responses when unreachable. The lower layer takes responsibly for re-establishing connectivity. When it (eventually) succeeds, it flags this to the routing protocols. The peer is now reachable - but the routing protocol may need to issue requests and responses to reprime the routing database. >Thanks, >Dan ------------------------------------------------------------------------------- Daniel Bronstein Access Beyond, Inc. e-mail: dan1@dss.com 1 Palmer Terrace tel: 201-438-2400 x255 Carlstadt, N.J. 07072 fax: 201-438-7767 ------ Message Header Follows ------ Received: from lynx.europe.shiva.com by eurohub.europe.shiva.com (PostalUnion/SMTP(tm) v2.1.7 for Windows NT(tm)) id AA-1997Jul08.171951.1281.292419; Tue, 08 Jul 1997 17:19:51 +0100 Received: from mailhost2.BayNetworks.COM (ext-ns1.baynetworks.com [134.177.3.20]) by lynx.europe.shiva.com (8.8.5/8.8.5) with ESMTP id RAA04771 for ; Tue, 8 Jul 1997 17:22:36 +0100 (BST) Received: from mailhost.BayNetworks.COM ([132.245.135.115]) by mailhost2.BayNetworks.COM (8.8.5/BNET-97/07/07-E) with ESMTP id JAA21650 Received: from lobster1.corpeast.Baynetworks.com (lobster1.corpeast.baynetworks.com [192.32.72.17]) by mailhost.BayNetworks.COM (8.8.5/BNET-97/07/07-I) with SMTP id JAA02599 Received: from marvin.corpeast.Baynetworks.com by lobster1.corpeast.Baynetworks.com (4.1/BNET-97/04/29-S) id AA07451; Tue, 8 Jul 97 12:18:58 EDT for andrew@extremenetworks.com Received: by marvin.corpeast.Baynetworks.com (4.1/SMI-4.1) id AA12548; Tue, 8 Jul 97 12:16:13 EDT Received: from lobster1.corpeast.Baynetworks.com by marvin.corpeast.Baynetworks.com (4.1/SMI-4.1) id AA12542; Tue, 8 Jul 97 16:16:11 GMT Received: from mailhost2.BayNetworks.COM (ext-ns1.baynetworks.com) by lobster1.corpeast.Baynetworks.com (4.1/BNET-97/04/29-S) id AA07034; Tue, 8 Jul 97 12:15:24 EDT for ietf-rip@marvin Received: from dss.com (titan.dss.com [192.41.217.8]) by mailhost2.BayNetworks.COM (8.8.5/BNET-97/07/07-E) with SMTP id JAA21487; Tue, 8 Jul 1997 09:10:26 -0700 (PDT) for Posted-Date: Tue, 8 Jul 1997 09:10:26 -0700 (PDT) Received: by dss.com (4.1/SMI-4.1) id AA29879; Tue, 8 Jul 97 12:16:06 EDT From: dan1@dss.com (Dan Bronstein) Message-Id: <9707081616.AA29879@dss.com> Subject: Triggered RIP ? To: ietf-rip@BayNetworks.COM Date: Tue, 8 Jul 1997 12:16:05 -0400 (EDT) Cc: dan1@dss.com (Dan Bronstein) X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk   Received: from cnri by ietf.org id aa08417; 16 Jul 97 9:56 EDT Received: from mailhost1.BayNetworks.COM (ns2.BayNetworks.COM [134.177.3.16]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid JAA07621 for ; Wed, 16 Jul 1997 09:54:59 -0400 (EDT) Received: from mailhost.BayNetworks.COM ([134.177.1.107]) by mailhost1.BayNetworks.COM (8.8.5/BNET-97/07/07-E) with ESMTP id GAA29996 Received: from lobster1.corpeast.Baynetworks.com (lobster1.corpeast.baynetworks.com [192.32.72.17]) by mailhost.BayNetworks.COM (8.8.5/BNET-97/07/07-I) with SMTP id GAA05020 Received: from marvin.corpeast.Baynetworks.com by lobster1.corpeast.Baynetworks.com (4.1/BNET-97/04/29-S) id AA19111; Wed, 16 Jul 97 09:46:47 EDT for andrew@extremenetworks.com Received: by marvin.corpeast.Baynetworks.com (4.1/SMI-4.1) id AA11142; Wed, 16 Jul 97 09:41:58 EDT Received: from lobster1.corpeast.Baynetworks.com by marvin.corpeast.Baynetworks.com (4.1/SMI-4.1) id AA11136; Wed, 16 Jul 97 13:41:56 GMT Received: from mailhost3.BayNetworks.COM ([192.32.253.7]) by lobster1.corpeast.Baynetworks.com (4.1/BNET-97/04/29-S) id AA18417; Wed, 16 Jul 97 09:41:06 EDT for ietf-rip@marvin Received: from darling.cs.umd.edu (darling.cs.umd.edu [128.8.128.115]) by mailhost3.BayNetworks.COM (8.8.5/BNET-97/07/07-E) with ESMTP id JAA25594; Wed, 16 Jul 1997 09:49:22 -0400 (EDT) for From: rohit@cs.umd.edu Posted-Date: Wed, 16 Jul 1997 09:49:22 -0400 (EDT) Received: by darling.cs.umd.edu (8.8.5/UMIACS-0.9/04-05-88) id JAA20545; Wed, 16 Jul 1997 09:41:02 -0400 (EDT) Date: Wed, 16 Jul 1997 09:41:02 -0400 (EDT) Message-Id: <199707161341.JAA20545@darling.cs.umd.edu> To: ietf-rip@baynetworks.com Subject: RIP - BGP interaction Cc: rohit@cs.umd.edu Sender: owner-ietf-rip@baynetworks.com Precedence: bulk Hi, The usual repositories didn't reveal anything so I figured I would ask here - Is there a draft out there which discusses RIP2-BGP4 interaction; specifically the use of the Route Tag field in propagating aggregated BGP learnt routes thru a RIP cloud? Thanks, --rohit. ----------------------------------------------------------------------------- #include /* Sure, I speak only for myself */ -----------------------------------------------------------------------------   Received: from cnri by ietf.org id aa10799; 16 Jul 97 11:15 EDT Received: from mailhost2.BayNetworks.COM (ext-ns1.baynetworks.com [134.177.3.20]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid LAA08057 for ; Wed, 16 Jul 1997 11:14:33 -0400 (EDT) Received: from mailhost.BayNetworks.COM ([134.177.1.107]) by mailhost2.BayNetworks.COM (8.8.5/BNET-97/07/07-E) with ESMTP id IAA28590 Received: from lobster1.corpeast.Baynetworks.com (lobster1.corpeast.baynetworks.com [192.32.72.17]) by mailhost.BayNetworks.COM (8.8.5/BNET-97/07/07-I) with SMTP id IAA01493 Posted-Date: Wed, 16 Jul 1997 08:07:37 -0700 (PDT) Received: from marvin.corpeast.Baynetworks.com by lobster1.corpeast.Baynetworks.com (4.1/BNET-97/04/29-S) id AA00433; Wed, 16 Jul 97 11:07:31 EDT for andrew@extremenetworks.com Received: by marvin.corpeast.Baynetworks.com (4.1/SMI-4.1) id AA12186; Wed, 16 Jul 97 10:57:25 EDT Received: from lobster1.corpeast.Baynetworks.com by marvin.corpeast.Baynetworks.com (4.1/SMI-4.1) id AA12180; Wed, 16 Jul 97 14:57:23 GMT Received: from bl-mail1.corpeast.BayNetworks.com (bl-mail1-nf0) by lobster1.corpeast.Baynetworks.com (4.1/BNET-97/04/29-S) id AA28765; Wed, 16 Jul 97 10:56:33 EDT for ietf-rip@marvin Received: from atlas.xylogics.com ([132.245.33.7]) by bl-mail1.corpeast.BayNetworks.com (post.office MTA v2.0 0529 ID# 0-13458) with ESMTP id AAA15411 for ; Wed, 16 Jul 1997 10:56:27 -0400 Received: from bighorn.xylogics.com (bighorn.xylogics.com [132.245.32.188]) by atlas.xylogics.com (8.7.3/8.7.3) with SMTP id KAA02779; Wed, 16 Jul 1997 10:55:50 -0400 (EDT) Received: by bighorn.xylogics.com id AA07547 (5.x/UK-doug-sol2-951219); Wed, 16 Jul 1997 10:55:47 -0400 From: Gary Scott Malkin Date: Wed, 16 Jul 1997 10:55:47 -0400 Message-Id: <7547.9707161455@bighorn.xylogics.com> To: rohit@cs.umd.edu Cc: ietf-rip@baynetworks.com In-Reply-To: <199707161341.JAA20545@darling.cs.umd.edu> (rohit@cs.umd.edu) Subject: Re: RIP - BGP interaction Sender: owner-ietf-rip@baynetworks.com Precedence: bulk Not specifically, as far as I know. > The usual repositories didn't reveal anything so I figured I would ask here - > Is there a draft out there which discusses RIP2-BGP4 interaction; specifically > the use of the Route Tag field in propagating aggregated BGP learnt routes > thru a RIP cloud? -- Gary Malkin Cheap, Fast, Good (508) 916-4237 Pick two!   Received: from cnri by ietf.org id aa03703; 30 Jul 97 6:40 EDT Received: from mailhost2.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid GAA23811 for ; Wed, 30 Jul 1997 06:39:17 -0400 (EDT) Received: from mailhost.BayNetworks.COM (screen2r.BayNetworks.COM [134.177.3.1]) by mailhost2.BayNetworks.COM (8.8.6/BNET-97/07/07-E) with ESMTP id DAA09966 Received: from lobster1.corpeast.Baynetworks.com (ns2.corpeast.baynetworks.com [192.32.72.17]) by mailhost.BayNetworks.COM (8.8.6/BNET-97/07/07-I) with SMTP id GAA07653 Received: from marvin.corpeast.Baynetworks.com by lobster1.corpeast.Baynetworks.com (4.1/BNET-97/04/29-S) id AA18748; Wed, 30 Jul 97 06:32:05 EDT for anil@levers.enet.dec.com Received: by marvin.corpeast.Baynetworks.com (4.1/SMI-4.1) id AA17377; Wed, 30 Jul 97 06:30:26 EDT Received: from lobster1.corpeast.Baynetworks.com by marvin.corpeast.Baynetworks.com (4.1/SMI-4.1) id AA17371; Wed, 30 Jul 97 10:30:25 GMT Received: from mailhost3.BayNetworks.COM ([192.32.253.7]) by lobster1.corpeast.Baynetworks.com (4.1/BNET-97/04/29-S) id AA18549; Wed, 30 Jul 97 06:29:29 EDT for ietf-rip@marvin Received: from fsnt.future.futsoft.com ([38.242.192.5] (may be forged)) by mailhost3.BayNetworks.COM (8.8.6/BNET-97/07/07-E) with ESMTP id GAA27801; Wed, 30 Jul 1997 06:37:45 -0400 (EDT) for Posted-Date: Wed, 30 Jul 1997 06:37:45 -0400 (EDT) Received: from kailash.future.futsoft.com (unverified [38.242.192.4]) by fsnt.future.futsoft.com (Integralis SMTPRS 2.04) with ESMTP id ; Wed, 30 Jul 1997 16:07:13 +0530 Received: from pasadena.future.futsoft.com (pasadena.future.futsoft.com [10.0.6.18]) by kailash.future.futsoft.com (8.7.1/8.7.1) with SMTP id PAA10234; Wed, 30 Jul 1997 15:41:30 +0530 Date: Wed, 30 Jul 1997 15:52:03 -0400 (EDT) From: "Srinivasan.E.S" To: ietf-rip@baynetworks.com Cc: srinies@kailash.future.futsoft.com Subject: RIPv2 - BGP interaction. Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ietf-rip@baynetworks.com Precedence: bulk Hello, I just want to know whether any material (In the form of draft or something else) is available with regard to the interaction between RIpv2 and BGP-4, which seems to be possible. I guess, Malkin had also mentioned when he authored rfc1723, So, can you please lemme know about this ASAP, as i need the information immediately. Thanks in advance. With Warm Regards, E.S. +--------------------------------+ | Srinivasan.E.S | | Software Engineer | +--------------------------------+ Off. Details Res. Details ------------ ------------ #-----------------------------------------------# *-----------------------* | Future Software Private Ltd, | | 34, 4th street, | | 481, Mount Road, | | Sri Lakshmi Nagar, | | Nandanam, | | Velachery, | | Madras - 600 035, India. | | Madras - 600 042, | | | | India. | | e-mail :- srinies@future.futsoft.com | *-----------------------* | Tel :- +91-44-4340323, 4330589, 4342166. | | Fax :- +91-44-4344157, 4834551, 4834661. | #-----------------------------------------------# --------o----------o---------o-----------o---------   Received: from cnri by ietf.org id aa05480; 30 Jul 97 8:40 EDT Received: from mailhost2.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid IAA24040 for ; Wed, 30 Jul 1997 08:39:25 -0400 (EDT) Received: from mailhost.BayNetworks.COM (ns1.corpemea.baynetworks.com [141.251.211.30] (may be forged)) by mailhost2.BayNetworks.COM (8.8.6/BNET-97/07/07-E) with ESMTP id FAA12161 Received: from lobster1.corpeast.Baynetworks.com (lobster1.corpeast.baynetworks.com [192.32.72.17]) by mailhost.BayNetworks.COM (8.8.6/BNET-97/07/07-I) with SMTP id OAA23090 Received: from marvin.corpeast.Baynetworks.com by lobster1.corpeast.Baynetworks.com (4.1/BNET-97/04/29-S) id AA00319; Wed, 30 Jul 97 08:32:02 EDT for anil@levers.enet.dec.com Received: by marvin.corpeast.Baynetworks.com (4.1/SMI-4.1) id AA18038; Wed, 30 Jul 97 08:30:43 EDT Received: from lobster1.corpeast.Baynetworks.com by marvin.corpeast.Baynetworks.com (4.1/SMI-4.1) id AA18032; Wed, 30 Jul 97 12:30:41 GMT Received: from mailhost2.BayNetworks.COM (ext-ns1.baynetworks.com) by lobster1.corpeast.Baynetworks.com (4.1/BNET-97/04/29-S) id AA29986; Wed, 30 Jul 97 08:29:46 EDT for ietf-rip@marvin Received: from darling.cs.umd.edu (darling.cs.umd.edu [128.8.128.115]) by mailhost2.BayNetworks.COM (8.8.6/BNET-97/07/07-E) with ESMTP id FAA12063; Wed, 30 Jul 1997 05:29:24 -0700 (PDT) for Posted-Date: Wed, 30 Jul 1997 05:29:24 -0700 (PDT) Received: by darling.cs.umd.edu (8.8.5/UMIACS-0.9/04-05-88) id IAA06672; Wed, 30 Jul 1997 08:29:26 -0400 (EDT) Message-Id: <199707301229.IAA06672@darling.cs.umd.edu> To: "Srinivasan.E.S" Cc: ietf-rip@baynetworks.com Subject: Re: RIPv2 - BGP interaction. In-Reply-To: Your message of "Wed, 30 Jul 1997 15:52:03 EDT." Date: Wed, 30 Jul 1997 08:29:26 -0400 From: Rohit Dube Sender: owner-ietf-rip@baynetworks.com Precedence: bulk On Wed, 30 Jul 1997 15:52:03 -0400 (EDT) srinies@future.futsoft.com writes: => I just want to know whether any material (In the form of draft or something => else) is available with regard to the interaction between RIpv2 and BGP-4, => which seems to be possible. I guess, Malkin had also mentioned when he => authored rfc1723, So, can you please lemme know about this ASAP, as i need => the information immediately. AFAIK, no such material exists. I had asked a similar question some weeks ago on this list - I'll quote Gary's reply below. --rohit. From: Gary Scott Malkin Date: Wed, 16 Jul 1997 10:55:47 -0400 Message-Id: <7547.9707161455@bighorn.xylogics.com> To: rohit@cs.umd.edu Cc: ietf-rip@BayNetworks.COM In-Reply-To: <199707161341.JAA20545@darling.cs.umd.edu> (rohit@cs.umd.edu) Subject: Re: RIP - BGP interaction Not specifically, as far as I know. > The usual repositories didn't reveal anything so I figured I would ask here - > Is there a draft out there which discusses RIP2-BGP4 interaction; specifically > the use of the Route Tag field in propagating aggregated BGP learnt routes > thru a RIP cloud?