IETF Logo Mail Archive

Re: Draft Agenda for Houston

pays@faugeres.inria.fr Sat, 23 October 1993 08:44 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00747; 23 Oct 93 4:44 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa00743; 23 Oct 93 4:44 EDT
Received: from mhs-relay.cs.wisc.edu by CNRI.Reston.VA.US id aa02984; 23 Oct 93 4:44 EDT
Received: from cs.wisc.edu by mhs-relay.cs.wisc.edu with SMTP (PP) id <19535-0@mhs-relay.cs.wisc.edu>; Sat, 23 Oct 1993 03:15:47 +0000
Received: from faugeres.inria.fr by cs.wisc.edu; Sat, 23 Oct 93 03:15:41 -0500
X400-Received: by /PRMD=inria/ADMD=atlas/C=fr/; Relayed; 23 Oct 93 09:14:59+0100
Date: 23 Oct 93 09:14:59+0100
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: pays@faugeres.inria.fr
To: Genovese@es.net, ietf-osi-x400ops@cs.wisc.edu
Subject: Re: Draft Agenda for Houston
Cc: CXII@es.net
Message-Id: <751364099.11485.0-faugeres.inria.fr*@MHS>

> suggestions?

Yes, I have one because I don't know where it could be discussed

What is to be done (as a whole community) with terribly not conformant
  software that want to connect to GO-MHS? Or more precisely, would it be
  possible to have a common attitude with sites/domains using that type
  of software and really *endangering* the whole GO-MHS?

It concernrs PRMDs (eg. using today MS-MAIL gateways) but also some ADMDs :-(

As we have no direct control on what people buy and use, it is not an easy
matter. What I suggest is to maintain and publish very widely a
blacklist of products/providers which will give the name and version
of the culprits along with a description of the problems.
  - this would allow customers to check this list prior to buying choices?
  - this would put a high pressure over the suppliers to fix the
	problems as soon as possible.
being unable to solve this type of problem is in my mind a serious X.400
killer!

-- PAP

Unfortunatley, I will not be able to attend the Houston meeting

v2.8.7 | Report a Bug | By Email