Skip to main content

Last Call Review of draft-ietf-v6ops-ipv6-ehs-in-real-world-02
review-ietf-v6ops-ipv6-ehs-in-real-world-02-opsdir-lc-jiang-2016-02-21-00

Request Review of draft-ietf-v6ops-ipv6-ehs-in-real-world
Requested revision No specific revision (document currently at 02)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2016-02-02
Requested 2016-01-25
Authors Fernando Gont , Jen Linkova , Tim Chown , Will (Shucheng) LIU
Draft last updated 2016-02-21
Completed reviews Opsdir Last Call review of -02 by Sheng Jiang
Assignment Reviewer Sheng Jiang
State Completed
Review review-ietf-v6ops-ipv6-ehs-in-real-world-02-opsdir-lc-jiang-2016-02-21
Reviewed revision 02
Result Has Issues
Completed 2016-02-21
review-ietf-v6ops-ipv6-ehs-in-real-world-02-opsdir-lc-jiang-2016-02-21-00
Hi, OPS-DIR, Authors,

I have reviewed this document as part of the Operational directorate's ongoing
effort to review all IETF documents being processed by the IESG. These comments
were written with the intent of improving the operational aspects of the IETF
drafts. Comments that are not addressed in last call may be included in AD
reviews during the IESG review. Document editors and WG chairs should treat
these comments just like any other last call comments.

This Informational document presents real-world measurement result regarding
the extent to which packets with IPv6 extension headers are dropped in the
Internet. This document also explains its measurement mechanism. This document
is well written. I don't see any major issues from the operations and
management perspective. It is almost ready to be published with a couple of
minor comments below:

This document assumes all IPv6 packets to all these tested destination are 100%
reached. However, this does not clearly state in the document either by text or
data in the table. Without this assumption, it is not proven that these packet
lose are caused by the attendance of extend headers, or some other aspects. I
assume this is only the lack of representation. Otherwise, it would be a major
or even fundamental issue for this document.

Unused Reference: RFC1034, RFC4443, RFC4861, RFC5927, RFC6980, RFC7045,
RFC7113, and RFC7123.

Best regards,

Sheng