Hi Lucy,
Thank you for the response. Sorry for my slow response. I tried to be on
a vacation last week/weekend so my checking of emails was sparse at best
;) See inline.
8/12/2016, 1:51 PM, Lucy yong kirjoitti:
Hi Jouni,
Thank you for the review and correction. Pls see inline below.
-----Original Message-----
From: Gen-art [mailto:gen-art-boun...@ietf.org] On Behalf Of Jouni
Sent: Friday, August 12, 2016 1:51 AM
To: gen-art@ietf.org (gen-art@ietf.org);
draft-ietf-tsvwg-gre-in-udp-encap....@ietf.org
Subject: [Gen-art] Generate review of draft-ietf-tsvwg-gre-in-udp-encap-16
I am the assigned Gen-ART reviewer for this draft. The General Area Review Team
(Gen-ART) reviews all IETF documents being processed by the IESG for the IETF
Chair. Please treat these comments just like any other last call comments.
For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
Document: draft-ietf-tsvwg-gre-in-udp-encap-16
Reviewer: Jouni Korhonen
Review Date: 8/11/2016
IETF LC End Date: 2016-08-12
IESG Telechat date: (if known)
Summary: Ready with minor nits.
Major issues: None.
Minor issues: Read on..
Editorials/nits:
o My “complaint” of this document is basically on the following.. these are
writing
style things so feel free to neglect:
- It repeats.. the same statements multiple times.
- When reading the document I get the feeling it is actually two documents.
The
technical specification (which is very short) and the general deployment
considerations document. I would have split it to two but that is just me.
The other nits.
o There are bunch of acronyms that are not expanded either never or on their
first use.
Some examples include UDP, DSCP, DS, PMTU, MPLS, VNP, .. Pay attention to
these.
[Lucy] I will check.
o In the Introduction give a reference to EtherType e.g., the repository where
they
are maintained or by whom they are maintained.
[Lucy] I will put RFC7042 as the reference.
Or maybe http://standards.ieee.org/regauth/ethertype/eth.txt
Either one works.
o On line 129 is says:
This document specifies GRE-in-UDP tunnel requirements for two
Based on the earlier text I would suggest saying “..document also
specifies..”
[Lucy] ack.
o On line 143 I would also (following the previous style in the paragraph)
capitalize
“wide area networks” as well.
[Lucy] ack.
o In multiple places (lines 236, 887) the reference is after the full stop.
Place full
stop after the reference.
[Lucy] My mistake. Will correct them.
o The document uses both tunnel ingress/egress and encapsulator/decapsulator.
Is there a
specific reason to have this differentiation? If not use common terminology
throughout
the document.
[Lucy] I would prefer to use two teams in the document. Tunnel ingress and
egress is the view from network perspective,
And encapsulator/decapsulator is the view at the ingress or egress. E.g. it is
odd to say encapsulator IP address. I open to add a clarification if that
causes a concern.
Maybe you should say this also in the draft?
o On line 654 is says:
MUST comply with requirement 1 and 8-10 in Section 5 of
How is this “MUST” enforced?
[Lucy] Do you concern on the wording or the implementation?
See the discussion I had with David.
o In Section 7.1 I find it a bit odd discussing NATs in the specific context
of IPv6. If
you have a specific IPv6 NAT scenario in mind either spell it out or give a
reference
to a specification that describes the technology/use case.
[Lucy] This section describes middlebox specialty on IPv6 traffic. Most UDP
applications do not perform UDP checksum in IPv4 network; most UDP applications
perform UDP checksum in IPv6 network because of IPv6 requirement [RFC2460].
Thus some middleboxes validate UDP checksum if it is in IPv6. [RFC6935]
[RFC6936] relax the need to perform UDP checksum in some special cases, which
is applicable to this draft. But we need to state out the potential impact that
is specific in IPv6.
Here as well, see the discussion I had with David.
o In Section 8 and lines 784-785 has a “MUST NOT” for traffic that is not
known to be
congestion-controlled.. I would be interested in knowing how to enforce this
“MUST”
specifically in the Internet case.
[Lucy] By IETF standard. :) How about replace "MUST NOT" with "are not
appropriate"? (match the wording in requirement 3 of Section 2.1.1)
Again, we did some more elaborations with David. Anyway, one concern I
had was on having MUSTs on things that you cannot really guard or
control using some protocol.. they are more like deployment
recommendations or good wishes at best then.. which I think do not
belong to a protocol spec.
- JOuni
o Line 909 typo “ether” -> “either”.
[Lucy] ack. Thx.
Regards,
Lucy
_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art
_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art
