Project Long Bud Participation, small corrections

Urs Eppenberger <Eppenberger@switch.ch> Tue, 04 May 1993 19:05 UTC

X400-Trace: us*attmail*cdc; arrival 04 May 93 12:14:20 -0500 action Relayed
X400-Trace: US*_*XNREN; arrival 04 May 93 17:13:30 Z action Relayed
X400-Trace: CH*arcom*switch; arrival 04 May 93 11:12:43 Z action Relayed
X400-Trace: CH*ARCOM*SWITCH; arrival 03 May 93 13:11:41 +0200 action Relayed
X400-Internal-Trace: mercury.os.cdc.us; arrival 04 May 93 12:24:38 -0500 action Relayed
X400-Internal-Trace: cdc.us; arrival 04 May 93 12:14:20 -0500 action Relayed
P1-Message-ID: CH*ARCOM*SWITCH; 930503131141
UA-Content-ID: 1695
Original-Encoded-Information-Types: IA5-Text
Delivery-Options: allow alternate recipients, return contents
Message-Id: <1695*Eppenberger@switch.ch>
Date: Mon, 03 May 1993 13:11:41 +0200
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Urs Eppenberger <Eppenberger@switch.ch>
To: mhs-ds@mercury.udev.cdc.com
Subject: Project Long Bud Participation, small corrections

Page 2 on top
o A group of MTA's ...
(this is outlined as a subpoint, but it is the only one, therefore there is
 absolutely no need for a subpoint.)

page 2
4 Periodically receiving ...
It's not periodic at all. New routing tables are distributed as fast as
possible. Only the mapping tables have a fixed schedule, but this is not
the issue here.

Page 2
6 Supplying the new, integrated routing information ...
Supplying is an unusual word, just use 'configure the MTA with the integrated
routing information ...'

Add the OR addresses where an RFC22 address is given. We want to get the
X.400 people interested in Long Bod, won't we?
But maybe we decide not to give the RFC822 addresses to sell our
X.400 <-> Internet-SMTP gateway services ;-)

Urs.

Project Long Bud Participation, small corrections Urs Eppenberger