+ Plus https://dl.acm.org/doi/pdf/10.1145/347057.347390 for PGMCC,
+ whence the ACK packet type comes; there are some I-Ds for PGMCC,
+ draft-ietf-rmt-bb-pgmcc-00 through draft-ietf-rmt-bb-pgmcc-03,
+ but none of them give any description of the packet-level
+ changes to PGM, unlike the paper in question, which merely gives
+ an *insufficient* description of said changes. In particular,
+ it doesn't indicate what the packet type code for ACK is.
+
+ Luigi Rizzo's PGMCC code for FreeBSD, at
+
+ https://web.archive.org/web/20020302084503/http://info.iet.unipi.it/~luigi/pgm-code/
+
+ uses 0x0b (11) for ACK.
+
+ A capture file attached to
+
+ https://gitlab.com/wireshark/wireshark/-/issues/4798
+
+ has packets that use 0x0d for ACK, as does the Wireshark dissector
+ for PGM, and as does OpenPGM at https://github.com/steve-o/openpgm.
+ It may be that some proprietary PGMCC implementations, such as
+ SmartPGM, do so as well.
+
+ We use *both*, treating *either one* as a PGMCC ACK, pending
+ more information, such as an answer to
+
+ https://github.com/steve-o/openpgm/issues/75.
+
+ */
+
+#include <config.h>
+
+#include "netdissect-stdinc.h"
+
+#define ND_LONGJMP_FROM_TCHECK
+#include "netdissect.h"