So after all the anguish about the rsync protocol, we now have a suggested
replacement. But there's been very little comment.
Tim did a thorough job of describing the design goals.
It would be useful if the wg paid attention to this.
--Sandy, speaking as one of the wg co-chairs
On Feb 17, 20
Sandy,
I reviewed the doc with David M., since he is a co-author and because his
office is down the hall :-).
As a result of our discussion he has a number of comments to be addressed in
the next version.
Steve
So after all the anguish about the rsync protocol, we now have a suggested
replace
A draft agenda has been posted.
Some of the requests for agenda time came to just one of the chairs. If you
made a request that is not on the agenda, you should send a query to the
sidr-cha...@ietf.org.
The deadline for drafts still has some time, so there may be other work to be
added to t
Route leaks problem definition is already work in progress in the GROW WG.
http://tools.ietf.org/html/draft-ietf-grow-route-leak-problem-definition-01
This related new draft addresses techniques for detection and mitigation of
route leaks.
The IDR chairs have agreed to include this draft in the
Hi all,
I have submitted a bis of RFC6487 as a -00 individual submission, and
will be presenting it in Dallas.
It's a minor change from RFC6487. Changes incorporated:
* all 3 verified errata
* RFC 7318 (update)
* two changes that were submitted as errata but rejected for being
technica
Randyet al.,
In hopes of restarting work on this draft, here is proposed text for
section 4. This is an attempt to integrate the original text with the
comments to the list submitted back in Feb 2014. My apologies if I've
mis-understood the original draft text or the comments. Does this
corr
