论文标题
必须，不在乎：TCP在野外的一致性
MUST, SHOULD, DON'T CARE: TCP Conformance in the Wild
论文作者
论文摘要
标准管理协议实施者的互操作性的应有和必须要求。如果TCP带有大部分互联网流量，则这些要求在RFC中定义。虽然已知并非所有可选功能均已实现并且存在不合格，但人们会认为TCP实现至少符合最低要求的最低要求。在本文中，我们使用范围内的扫描来展示互联网主机和路径如何符合这些基本要求。我们发现了一套不可忽略的宿主和路径，这些宿主和路径甚至不符合基本要求。例如，我们观察到无法正确处理TCP选项中的校验和中间箱干扰的案例的主机。当紧急指针设置或简单地崩溃时，我们确定丢弃数据包的主机。我们公开获得的结果强调，不应将符合甚至基本协议要求的一致性视为理所当然，而应定期检查。
Standards govern the SHOULD and MUST requirements for protocol implementers for interoperability. In case of TCP that carries the bulk of the Internets' traffic, these requirements are defined in RFCs. While it is known that not all optional features are implemented and nonconformance exists, one would assume that TCP implementations at least conform to the minimum set of MUST requirements. In this paper, we use Internet-wide scans to show how Internet hosts and paths conform to these basic requirements. We uncover a non-negligible set of hosts and paths that do not adhere to even basic requirements. For example, we observe hosts that do not correctly handle checksums and cases of middlebox interference for TCP options. We identify hosts that drop packets when the urgent pointer is set or simply crash. Our publicly available results highlight that conformance to even fundamental protocol requirements should not be taken for granted but instead checked regularly.
