- Original Message -
From: "Joe Touch"
To: "Templin, Fred L" ; "Linda Dunbar"
;
Cc:
Sent: Friday, October 07, 2016 4:00 PM
> Hi, Fred,
> On 10/7/2016 7:43 AM, Templin, Fred L wrote:
> >
> > Joe’s analogy of ATM AAL5 is also exactly correct. And, as Joe says,
> > the cell
> >
> > size
- Original Message -
From: "Joe Touch"
Sent: Saturday, October 08, 2016 12:24 AM
> Hi, Tom,
>
> Thanks for pointing that out. I'll try to revise to make that easier.
>
> If you have any other specific examples, please let me know (either
> on-list or directly).
Joe
How about
' o Tu
- Original Message -
From: "Joe Touch"
Sent: Monday, October 10, 2016 7:15 PM
> HI, Fred (et al.),
>
> ...
> > IMHO, your draft is getting wrapped up with too many new acronyms
for no
> > good reason when simple English-language text would make things
easier to
> > understand.
> We're dea
Joe
Looking some more, I think that the carefully defined terminology is not
then used so carefully!
s.2.2 defines the term 'forwarder' but by 3.5, 'router' moves in and
forwarder is never used again. Is this of technical significance, or
just a question of the style of the author(?s)? I think
Lionel
On FQDN, would RFC1983 do?
Tom Petch
- Original Message -
From: "Lionel Morand"
To:
Cc: ;
;
Sent: Wednesday, January 25, 2017 1:28 PM
> Reviewer: Lionel Morand
> Review result: Ready
>
> I have reviewed this document as part of the Operational directorate's
> ongoing effort to
I wonder if the mix of SHOULD and should is intentional.
And I cannot recall seeing RFC2119 as an Informative Reference before.
s.1
/ entierly/ entirely/
And I am surprised at the lack of mention of IPv6 which did its bit for
the planet by eliminating broadcast.
Tom Petch
- Original Mes
