Reply to MHS-DS at the next IETF
Michael.R.Storz@lrz.lrz-muenchen.d400.de Mon, 21 February 1994 17:05 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa02198;
21 Feb 94 12:05 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa02194;
21 Feb 94 12:05 EST
Received: from mercury91.udev.cdc.com by CNRI.Reston.VA.US id aa14013;
21 Feb 94 12:05 EST
Received: by mercury.udev.cdc.com; Mon, 21 Feb 94 11:04:36 -0600
X-From: Michael.R.Storz@lrz.lrz-muenchen.d400.de Mon Feb 21 11:04 CST 1994
Received: from wally.udev.cdc.com by mercury.udev.cdc.com;
Mon, 21 Feb 94 11:04:28 -0600
Received: by wally.udev.cdc.com; Mon, 21 Feb 94 11:08:10 +0600
X400-Received: by /c=us/admd=attmail/prmd=cdc/ ; Relayed ;
21 Feb 94 11:03:18 -0600
X400-Received: by /c=US/admd=/prmd=XNREN/ ; Relayed ; 21 Feb 94 17:03:21 Z
X400-Received: by /c=de/admd=d400/prmd=dfnrelay/ ; Relayed ;
21 Feb 94 17:04:16 Z
X400-Received: by /c=de/admd=d400/prmd=lrz-muenchen/ ; Relayed ;
21 Feb 94 17:00:31 Z
X400-Received: by mta MTAwally in /c=us/admd=attmail/prmd=cdc/ ; Relayed ;
21 Feb 94 11:07:27 +0600
X400-Received: by mta cdc.us in /c=us/admd=attmail/prmd=cdc/ ; Relayed ;
21 Feb 94 11:03:18 -0600
X400-MTS-Identifier: /c=de/admd=d400/prmd=lrz-muenchen/ ;
940221172836747-MTALRZVEE
Content-Identifier: 940221172836747
Content-Return: Allowed
X400-Content-Type: P2-1984 ( 2 )
Conversion: Allowed
Original-Encoded-Information-Types: IA5-Text
Priority: normal
Disclose-Recipients: Prohibited
Alternate-Recipient: Prohibited
X400-Originator: Michael.R.Storz@lrz.lrz-muenchen.d400.de
X400-Recipients: non-disclosure: ;
Message-Id: <940221172836747-MTALRZVEE*/c=de/admd=d400/prmd=lrz-muenchen/o=/ou=LRZ/s=Storz/g=Michael/i=R/@MHS>
In-Reply-To: <2d68ce85707c002@zeus.cd
*/c=us/admd=attmail/prmd=cdc/o=zeus/s=2d68ce85707c002/@MHS>
Date: 21 Feb 94 17:00:31 Z
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Michael.R.Storz@lrz.lrz-muenchen.d400.de
To: "/c=no/admd=
/prmd=uninett/o=uninett/s=Alvestrand/g=Harald/i=T/"@wally-gw.udev.cdc.com,
Return requested <mhs-ds@mercury.udev.cdc.com>
cc: Return requested <CDC-Postmasters@lrz.lrz-muenchen.d400.de>
Subject: Reply to MHS-DS at the next IETF
> Hello,
>
> just to let you know some things:
>
> - The chairs DO plan to have an MHS-DS meeting in Seattle
>
> - Steve Kille has promised to have all the updates done by
> March 11
Does this include a solution to my empty PRMD/ORG problem ? There seems to be
no interest of this list to discuss this problem or to discuss the solution
proposed bu Kevin Jordan.
>
> - We are currently discussing with the IETF management trying
> to reconcile our views on the status of the group.
>
> In order to make progress on the last point, could those who
> are doing activity within this area, whether inside or outside
> the LongBud pilot, please send a message to the list describing
> their work and its status?
> Regards,
>
> Harald Tveit Alvestrand
> Co-chair, MHS-DS
>
We have installed Mail*Hub Version 2.1 and are using routing trees internally.
We want to replace the X.500 directory, which is connected to the german X.500
pilot project and has a few experimental entries with the internal X.500
directory with holds a lot more information together with the routing trees
as soon as the legal problems with data privacy are resolved here.
The University of Giessen, another site in Germany, is exactly in the same
situation as we. They have installed and configured their routing trees
internally and will connect to the outside as soon as it is possible for them.
Some other sites here in Germanyare waiting till we have mastered our problems
before they will upgrade their software and participate at Long Bud.
The main problem we encountered till now is the use of routing trees for
mapping between X.400 and SMTP. First, it is not possible to represent empty
PRMDs and O(rganization) in the routing tree, which means we must use large
configuration files for these entries. Second, it seems that there are no
tools to administer a routing tree with the information from the RARE Mapping
Tables. Such local routing trees must be used as long as this information is
not put by someone in the Open Community Routing Tree. Manual administration
of such routing trees is painful and error prone.
In summary it takes us much longer as we expected to make our configurations
and to connect to Long Bud. If we have resolved our problems some sites will
show up in Germany, which will actively participate in Long Bud (at least I hope
so :-).
What about others ???
--
Michael Storz
================================================================================
! X.400 : G=michael;S=storz;OU1=lrz;
Leibniz-Rechenzentrum ! P=lrz-muenchen;A=d400;C=de
Barer Str. 21 ! RFC822: michael.storz@lrz-muenchen.de
80333 Muenchen ! Fax : ++ 49 89 2809460
Germany ! Tel : ++ 49 89 2105 8720
================================================================================
- Reply to MHS-DS at the next IETF Michael.R.Storz
- Re: Reply to MHS-DS at the next IETF Harald T. Alvestrand