xun...@isi.edu wrote:
> One result of that work is that we think additional information
> would make anycast dianosis much easier---
How can it be made much easier?
All the anycast servers should have unicast addresses to be
used for zone transfer, which can be used for most, if not all,
diagnos
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. "n
On Sun, Sep 25, 2011 at 12:19 PM, Paul Hoffman wrote:
> On Sep 25, 2011, at 11:26 AM, xun...@isi.edu wrote:
>
> > We have a draft of our proposal with rationale at
> > http://www.isi.edu/~xunfan/research/draft-anycast-diagnostics.txt
>
> Instead of "ns-diagnostics", using "_ns-diagnostics" woul
On Sep 25, 2011, at 11:26 AM, xun...@isi.edu wrote:
> We have a draft of our proposal with rationale at
> http://www.isi.edu/~xunfan/research/draft-anycast-diagnostics.txt
Instead of "ns-diagnostics", using "_ns-diagnostics" would be much better. The
"_ at the beginning of a label is not a hostn
Hi all,
Our research group has been looking at assessing anycast usage.
(We have a technical report about our early findings at
ftp://ftp.isi.edu/isi-pubs/tr-671.pdf if you're interested.)
One result of that work is that we think additional information
would make anycast dianosis much easier---we
