Quoting Paul Hoffman <paul.hoff...@vpnc.org>: > On Sep 25, 2011, at 1:53 PM, xun...@isi.edu wrote: > > > Sure, thanks for the advise. We can add "_" for "instance_id" and > "node_id" > > also, "_instance_id._ns-diagnostics.$ORIGIN", > > "_node_id._ns-diagnostics.$ORIGIN" > > Sounds good. > > > Yes, the is not the first time we have this terminology problem. "node" is > > defined in RFC 4786 while RFC 4892 use "instance". > > > > We only have a slight explanation of the two in Section 1 the first goal, > > > > "The mechanism should be able to identify both specific anycast > > instances (a specific computer running anycast), and also anycast > > nodes (defined in RFC 4786 [RFC4786] as the topology location > > where multiple instances may run)" > > > > but we should definitely give a clear differentiation at the beginning. > > Ah, I missed that. Maybe a two-paragraph terminology section would make it > more obvious for the too-quick like me...
Sure, we will do that. > > --Paul Hoffman > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop > _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
