Stewart Bryant has entered the following ballot position for
draft-ietf-6man-udpchecksums-04: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.




----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Please see my discuss on draft-ietf-6man-udpzero, and note that I hope to
get to yes on this draft also, since I support the liberalization of this
protocol design when used for tunnelling. Specifically point 6 in this
draft is relevant to this discussion.
Additionally a tunnel may not have any way of knowing if the payload is
protected (as you suggest), since normally a tunnel has no knowledge of
the payload characteristics. 

In point 7 you suggest that an application cannot rely on packet length.
When PWs are used for tunneling we rely on exactly that (except in the
case of packets shorter than 64 octets for Ethenet padding reasons), and
I am not aware of any reported issues. Thus when the application is
tunnel encap/decap there is a body of evidence that suggests that this
OK.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

There is some text in the earlier part of document that looks like it
should be written in RFC2119 format. In this case it is not important
because the normative change is later and this used RFC2119 directives,
however the authors should consider making the document self consistent
in this regard.


--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to