Reply to Naming MTAs

Kevin Jordan <> Tue, 31 January 1995 15:30 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa03019; 31 Jan 95 10:30 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa03015; 31 Jan 95 10:30 EST
Received: from by CNRI.Reston.VA.US id aa09786; 31 Jan 95 10:30 EST
Received: by; Tue, 31 Jan 95 09:30:21 -0600
X-From: Tue Jan 31 09:30 CST 1995
Received: from localhost by; Tue, 31 Jan 95 09:30:19 -0600
To: MHS Mail <>
cc: MHSDS list <>
Subject: Reply to Naming MTAs
In-reply-to: Your message of "Tue, 31 Jan 95 16:11:07 +0700" <9501311511.AA17636@karl.wtk.suresnes>
Date: Tue, 31 Jan 95 09:30:18 -0600
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Kevin Jordan <>
Message-Id: <>

> regarding the naming of the MTAs, I wonder if the bilateral
> table(s) are always used during the checking of an incoming
> MTA association or the entry of the remote MTA may be used
> directly if no bilateral aggrements exits. In that case,
> it means for 1984 MTAs named with MTAName, there is a risk
> of collision between two MTAs from differents domains. How can it
> be handled except naming 1984 MTAs with gdi AND mta name.

If an 84 MTA needs to validate all incoming associations, then it will be
necessary for that MTA to register in its bilateral table(s) all of the MTA's
from which it is willing to accept connections.  It should also register
its responder authentication requirements in its own directory entry.

Some MTA's are willing to accept connections from any other MTA's.  These
MTA's do not need to validate incoming associations.  Therefore, they have
no need for bilateral tables, or any well-defined scheme for MTA naming
in the directory.