On Oct 21, 2014, at 5:58 PM, Nick Hilliard wrote:
...
> We'd prefer to leave the section in.
Ok.
--John
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow
On 21/10/2014 19:22, John G. Scudder wrote:
> where where in the
> the spring
cut-n-paste typo. Not present in the .txt.
> I agree with all that. However I think the point at which DFZ size
> becomes the upper bound is well below the point at which a practical
> problem rears its ugly head.
the
Hi Nick,
A few remarks and nits below. You can assume that I'm fine with anything I've
trimmed.
On Oct 20, 2014, at 8:06 PM, Nick Hilliard wrote:
...
> thanks for your extensive review - it has been very helpful.
You're welcome.
...
> Long term link persistence for rfc references is a problem
John,
thanks for your extensive review - it has been very helpful.
On 18/09/2014 21:50, John G.Scudder wrote:
[...]
> - Throughout the document, various terms are used to describe what RFC
> 4271 calls a "route". The definition given in RFC 4271 is:
>
> Route A unit of information that pairs a
Hello,
I have been selected as the Routing Directorate reviewer for this draft. The
Routing Directorate seeks to review all routing or routing-related drafts as
they pass through IETF last call and IESG review, and sometimes on special
request. The purpose of the review is to provide assistance
