On Mon, Mar 23, 2015 at 02:22:28AM +0000, Alexey Melnikov wrote:
> Another alternative is to allow for uniformResourceIdentifier for the
> purpose you describe (they are currently prohibited by the draft, but only
> because they are not used).
I think I would avoid URI, too much unnecessary flexibility.
Other than the "authority", the rest of the URI is not meaningful
for submission/imap/pop once we know the service.
You're likely tracking the discussion of URI on kitten, there the
URI really does carry more information (protocol TCP vs UDP and
path information for KDC proxy via HTTP).
So I'm not keen on seeing an overly general solution here, unless
I'm missing what URI has to offer.
--
Viktor.
_______________________________________________
Uta mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/uta
