Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!neat.cs.toronto.edu!rayan From: rayan@cs.toronto.edu (Rayan Zachariassen) Newsgroups: comp.protocols.tcp-ip Subject: Re: New Host-Requirement RFCs Message-ID: <89Oct28.142001edt.2700@neat.cs.toronto.edu> Date: 28 Oct 89 18:20:34 GMT References: <1989Oct27.212939.11277@agate.berkeley.edu> <89Oct27.235825edt.2687@neat.cs.toronto.edu> Lines: 20 lear@NET.BIO.NET (Eliot Lear) writes: >Rayan Zachariassen writes that it isn't reasonable to expect sites to >demand that every mailer support DNS properly. Yes it is. ... >... That is to say, why should we expect sites to >support the % hack, when we cannot expect other sites to support MXes? Eliot, that's not what I said. Perhaps I should rephrase: I don't think it is reasonable to expect every site to map all the hosts reachable from that site into the DNS. Therefore there must be some way of specifying the hosts that are not mapped in this way. I don't care which method is used but there must be some (perhaps specific to the site), unless the intention is to have no communication. There is a long way from "Your mailer must support the DNS" to "Your mailer must ONLY support the DNS (from our point of view)". This doesn't belong in tcp-ip, or anywhere else I can think of. I'll create a mailing list for this kind of stuff if people still want to discuss it.