Applicability of routing policy to reports

"Kevin E. Jordan" <Kevin.E.Jordan@cdc.com> Thu, 16 June 1994 16:04 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04912; 16 Jun 94 12:04 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa04908; 16 Jun 94 12:04 EDT
Received: from [129.179.91.61] by CNRI.Reston.VA.US id aa09152; 16 Jun 94 12:03 EDT
Received: from mercury91.udev.cdc.com by mhub61.udev.cdc.com; Thu, 16 Jun 94 10:51:56 -0600
Received: by mercury.udev.cdc.com; Thu, 16 Jun 94 10:47:51 -0500
X-From: kej@mercury.udev.cdc.com Thu Jun 16 10:47 CDT 1994
Received: from localhost by mercury.udev.cdc.com; Thu, 16 Jun 94 10:46:03 -0500
To: mhs-ds@mercury.udev.cdc.com, s.kille@mercury.udev.cdc.com
Subject: Applicability of routing policy to reports
Date: Thu, 16 Jun 94 10:46:02 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Kevin E. Jordan" <Kevin.E.Jordan@cdc.com>
Message-Id: <2e0073bb3598002@mercury.udev.cdc.com>

The mTAWillRoute attribute provides for the specification of routing policy
on a per-MTA basis.  It is a multivalued attribute.  Each value specifies
a policy.  Each policy defines a possibly empty set of originators from
which the MTA is willing to accept messages, a possibly empty set of recipients
to which these originators may send messages, and a pair of sets which allow
exclusions to be specified for the "from" and "to" sets.

It is clear how this information can be applied to IPM's.  But, how should
it be applied to non/delivery reports?  X.400 reports do not include an
originator address.  The first external trace entry specifies the X.400
domain from which a report originates, but this includes only C, ADMD, and PRMD.
Application of mTAWillRoute policies to the originating domain could result
in discarding a report unnecessarily and improperly.

Perhaps reports should simply be immune to X.400 routing policies?