Any opinions on SVCINFO[0]. I was really big fan of SRV until I read the draft, it made really compelling arguments to me.
I'm not sure I agree on how the information is encoded, coworker sent some of his thought to the author explaining how to encode in a way which makes machine-parsing easier. But this is minor detail. Goal should be that 1 query returns all the information client needs to decide how it wants to connect to service, SVCINFO delivers this. If we had had SVINFO (or even SRV) for years, we'd likely have less BGP bloat, as now you need to rely on really low-level stuff to deliver services reliably due to naivety of A/AAAA. [0] http://tools.ietf.org/html/draft-lear-httpbis-svcinfo-rr-01 -- ++ytti _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
