shehzad's message

Martha Steenstrup <msteenst@bbn.com> Mon, 24 August 1992 18:31 UTC

Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa11633; 24 Aug 92 14:31 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa11629; 24 Aug 92 14:31 EDT
Received: from PIZZA.BBN.COM by NRI.Reston.VA.US id aa17636; 24 Aug 92 14:32 EDT
Received: from pizza by PIZZA.BBN.COM id aa02920; 24 Aug 92 13:16 EDT
To: idpr-wg@bbn.com
Subject: shehzad's message
Date: Mon, 24 Aug 1992 14:13:47 -0400
From: Martha Steenstrup <msteenst@bbn.com>
Message-ID: <9208241432.aa17636@NRI.Reston.VA.US>

> "If no suitable cache entry exists, the path agent queries the route
> server, providing it with the source and destination domains together
> with the source policy information carried in the host message and
> specified through configuration".

> When it says "source policy information" above, does it mean requested
> service information or actual source policy information i.e the source
> policy number. I would think its the former, in which case it may be
> better to rephrase that statement. If it actually means the source
> policy number, then I don't see how that information would be there in
> the host message.

Shehzad, the referenced source policy information is that information
carried in the Route Request message.  Specifically, this information
includes the UCI, the requested services, and the domains to favor,
avoid, or exclude in the route.  IDPR does not send entire source
policies in messages nor does it refer to actual source policy numbers
in messages.  Source policy numbers exist primarily for network
management.

We can specify source policy information as part of source policy
configuration.  However, there is currently no mechanism within IDPR
for a host to convey source policy information to a path agent.  SRI
is currently working on such a mechanism and I expect will describe
the mechanism to the idpr-wg list, once the mechanism has been fully
defined.

m