transit policies based on host sets
Shehzad Merchant <merchant@erg.sri.com> Wed, 22 July 1992 02:51 UTC
Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa11563; 21 Jul 92 22:51 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa11559; 21 Jul 92 22:51 EDT
Received: from PIZZA.BBN.COM by NRI.Reston.VA.US id aa08269; 21 Jul 92 22:54 EDT
Received: from pizza by PIZZA.BBN.COM id aa17275; 21 Jul 92 22:44 EDT
Received: from BBN.COM by PIZZA.BBN.COM id aa17271; 21 Jul 92 22:41 EDT
Received: from alder.erg.sri.com by BBN.COM id aa12332; 21 Jul 92 22:44 EDT
Received: by alder.erg.sri.com (4.1/2.7davy) id AA16475; Tue, 21 Jul 92 19:46:03 PDT
Message-Id: <9207220246.AA16475@alder.erg.sri.com>
Date: Tue, 21 Jul 1992 19:46:03 -0700
From: Shehzad Merchant <merchant@erg.sri.com>
To: idpr-wg@bbn.com
Subject: transit policies based on host sets
In the IDPR configuration document, there is provision for implementing transit policies based on host sets. However I am not clear about the semantics of including a host set in a transit policy specification. If a host set is included in the TP specification does that mean that that host set is to be excluded from routes traversing the domain or does it mean that only hosts included in the host sets mentioned in the TP are to be allowed to traverse the domain. Also does it mean that the hosts in the host sets mentioned in the TP are to be excluded ( or permitted) as source hosts or destination hosts or both. As far as the Route Server Query Protocol goes, in the ROUTE REQUEST message type I see no provision for indicating the source and destination hosts to the route server. In order to be able to compute routes in the presence of TPs specifying host sets, the route server should know the source and destination hosts for the request so that it can compute valid routes. Inputs anyone? -Shehzad
- transit policies based on host sets Shehzad Merchant