Re: Devilish: Forget about DNS

Hadmut Danisch wrote:
> On Mon, Feb 09, 2004 at 02:20:51PM -0500, Yakov Shafranovich wrote:
> 
>>What bothers me is that there are two separate identities at stake here:
>>1. Identity of the incoming MTA.
>>2. Sender's identity
> 
> 
> Yeah, but that isn't new. My HTTP proposal is just about
> how and where to store, fetch and transmit the authorization record. 
> In what way is it affected by or does it affect the two 
> identities?
> 

Because identity #1 can be  successfully verified using DNS. Case in 
point - lets take a look at the XMPP protocol, section 14.3 
(http://www.ietf.org/internet-drafts/draft-ietf-xmpp-core-22.txt):

"  Client-to-server communications MUST NOT proceed until the DNS
    hostname asserted by the server has been resolved.  Such resolutions
    SHOULD first attempt to resolve the hostname using an [SRV] Service
    of "xmpp-client" and Proto of "tcp", resulting in resource records
    such as "_xmpp-client._tcp.example.com." (the use of the string
    "xmpp-client" for the service identifier is consistent with the IANA
    registration).  If the SRV lookup fails, the fallback is a normal
    IPv4/IPv6 address record resolution to determine the IP address,
    using the "xmpp-client" port of 5222 registered with the IANA.
"

Yakov
-------
Yakov Shafranovich / asrg <at> shaftek.org
SolidMatrix Technologies, Inc. / research <at> solidmatrix.com
"All that is gold does not glitter" (LOTR)
-------