Routing Domain

Tony Li <tli@cisco.com> Sun, 10 January 1993 20:19 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07898; 10 Jan 93 15:19 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa07894; 10 Jan 93 15:19 EST
Received: from atlas.xylogics.com by CNRI.Reston.VA.US id aa07211; 10 Jan 93 15:20 EST
Received: by atlas.xylogics.com id AA32371 (5.65c/UK-2.1-921001); Sun, 10 Jan 1993 15:20:47 -0500
Received: from lager.cisco.com by atlas.xylogics.com with SMTP id AA02917 (5.65c/UK-2.1-921001); Sun, 10 Jan 1993 15:20:40 -0500
Received: by lager.cisco.com; Sun, 10 Jan 93 12:18:14 -0800
Date: Sun, 10 Jan 93 12:18:14 -0800
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Tony Li <tli@cisco.com>
Message-Id: <9301102018.AA00887@lager.cisco.com>
To: 0004373580@mcimail.com
Cc: ietf-rip@xylogics.com
In-Reply-To: "RND - RAD NETWORK DEVICES LTD."'s message of Sun, 10 Jan 93 18:26 GMT <50930110182605/0004373580NA1EM@mcimail.com>
Subject: Routing Domain

   Another, even more confused question, is about passing
   routing information between domains:
   A router operating in two RIP2 routing domains shouldn't 
   include in its RIP messages to one domain its routing table 
   entries that belong to the other domain, should it ?
   Is the router expected to do route leaking between them ? 
   Based on configured policies ?

The router should leak between them if and ONLY if it is configured to
do so.  Note that most vendors will probably also want to implement
unidirectional leaking as well.

Tony