Re: a question on policy gateways

村山優子 <> Fri, 15 October 1993 04:21 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa24981; 15 Oct 93 0:21 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa24977; 15 Oct 93 0:21 EDT
Received: from PIZZA.BBN.COM by CNRI.Reston.VA.US id aa11451; 15 Oct 93 0:21 EDT
Received: from pizza by PIZZA.BBN.COM id aa13417; 15 Oct 93 0:14 EDT
Received: from BBN.COM by PIZZA.BBN.COM id aa13413; 15 Oct 93 0:12 EDT
Received: from by BBN.COM id aa24872; 15 Oct 93 0:13 EDT
Received: by (5.64/6.4J.6) id AA07603; Fri, 15 Oct 93 13:13:38 JST
Return-Path: <>
Message-Id: <>
Subject: Re: a question on policy gateways
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-2022-jp"
Date: Fri, 15 Oct 1993 13:13:37 JST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: =?ISO-2022-JP?B?GyRCQjw7M00lO1IbKEI=?= <>

Woody, Danny, and Martha,

Thank you all for your informative replies.

The reason why I asked the question is this.
In Routing by Preference, the source or the destination
of a communication flow wants the traffic to take 
the shortest paths in unfavoured ADs.  
If there were multiple virtual links between ADs, 
cost information of *inra-AD* paths would be required 
to decide *inter-AD* paths in terms of policy gateways.

However, it seems a bit awkward that inter-domain
routing needs intra-domain information in
hierarchical routing.  
On the other hand, I thought that we could collect intra-domain
cost information by means of network monitoring tools, 
if it was not provided by the distributed inter-domain 
routing information.

Yes, we expected that a part of routing by preference
would be solved by idpr, because the source's preference
can be treated as a source's policy in idpr.
However, there is yet another part of the problem: 
destination's preference.

We would not be able to attend IETFs, but would be interested
in presenting our research topic in the form of video tapes
(10-20 minutes).  Would that be possible?