6bone Routing Guidelines I-D (HARDEN-03) cleanup for
forwarding
Bob Fink
fink@es.net
Tue, 07 Dec 1999 10:29:22 -0800
--=====================_102647042==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed
Peter,
At 01:10 PM 12/7/99 +0000, Peter Bunclark wrote:
>On Tue, 7 Dec 1999, Wilfried Woeber, UniVie/ACOnet wrote:
> > Puzzled....
> > Have you been a victim of an outdate local or cache copy?
>Go to http://www.6bone.net/ and click on ``6bone Registry Documentation''
>which takes you to http://www.6bone.net/RIPE-registry.html where there's a
>link to
>http://www.es.net/pub/internet-drafts/draft-ietf-ngtrans-6bone-registry-01.txt
> ^^
>which is non-existant.
Absolutely true... sorry about that.
> > I've pulled the doc from the server only yesterday, and just re-checked,
> > the link is working fine, although it points to
> >
> >
> http://www.ip.qwest.net/~david/6bone/draft-ietf-ngtrans-6bone-registry-02.txt
> > ^^
>Ah, great, I can see that document, thanks. Somebody needs to fix the
>broken link, though.
It's fixed.
> > But I agree, there are some loose ends, still :-)
> > Wilfried.
Much of the user-level documentation for the registry is only minimal. I
would very much appreciate suggestions of what folk think needs to be more
clearly spelled out, etc. I've been planning a rewrite for a while, but
haven't gotten around to it, so this is good impetus.
So... keep those suggestions coming in.
Thanks,
Bob
--=====================_102647042==_.ALT
Content-Type: text/html; charset="us-ascii"
<html>
Peter,<br>
<br>
At 01:10 PM 12/7/99 +0000, Peter Bunclark wrote:<br>
<br>
<blockquote type=cite cite>On Tue, 7 Dec 1999, Wilfried Woeber,
UniVie/ACOnet wrote:<br>
> Puzzled....<br>
> Have you been a victim of an outdate local or cache
copy?<br>
Go to
<a href="http://www.6bone.net/" eudora="autourl">http://www.6bone.net/</a>
and click on ``6bone Registry Documentation''<br>
which takes you to <a href="http://www.6bone.net/RIPE-registry.html" eudora="autourl">http://www.6bone.net/RIPE-registry.html</a> where there's a<br>
link to <br>
<a href="http://www.es.net/pub/internet-drafts/draft-ietf-ngtrans-6bone-registry-01.txt" eudora="autourl">http://www.es.net/pub/internet-drafts/draft-ietf-ngtrans-6bone-registry-01.txt</a><br>
^^<br>
which is non-existant.</blockquote><br>
Absolutely true... sorry about that.<br>
<br>
<br>
<blockquote type=cite cite>> I've pulled the doc from the server only yesterday, and just re-checked,<br>
> the link is working fine, although it points to<br>
> <br>
> <a href="http://www.ip.qwest.net/~david/6bone/draft-ietf-ngtrans-6bone-registry-02.txt" eudora="autourl">http://www.ip.qwest.net/~david/6bone/draft-ietf-ngtrans-6bone-registry-02.txt</a><br>
> ^^<br>
Ah, great, I can see that document, thanks. Somebody needs to fix the<br>
broken link, though.</blockquote><br>
It's fixed.<br>
<br>
<br>
<blockquote type=cite cite>> But I agree, there are some loose ends, still :-)<br>
> Wilfried.</blockquote><br>
<br>
Much of the user-level documentation for the registry is only minimal. I would very much appreciate suggestions of what folk think needs to be more clearly spelled out, etc. I've been planning a rewrite for a while, but haven't gotten around to it, so this is good impetus.<br>
<br>
So... keep those suggestions coming in.<br>
<br>
<br>
Thanks,<br>
<br>
Bob<br>
</html>
--=====================_102647042==_.ALT--