diff options
author | Gerald Combs <gerald@wireshark.org> | 2020-09-15 14:58:08 -0700 |
---|---|---|
committer | AndersBroman <a.broman58@gmail.com> | 2020-10-07 08:01:51 +0000 |
commit | 9875011fda6d4a6f44fc75c62a25d31098c6b553 (patch) | |
tree | d7a439923f05657e57dc76373c54a34e2736a6ca /epan/dissectors/packet-ipv6.c | |
parent | 6590affa67822a8a1f88309cd7b33304ebfa68cf (diff) |
Update some field names to match what's in RFCs.
Update some field names and capitalization in the IPv4, IPv6, ICMPv4,
and TCP dissectors to match the names documented in their respective
RFCs. This is in no way comprehensive, but it ensures that the packet
diagram more closely matches the RFC diagrams for those protocols.
(I haven't found a document that explitly says so, but protocol field
names in IETF RFCs seem to follow Chicago Manual of Style capitalization
recommendations in section 3.4 of the RFC Style Guide[1] for the most
part.)
[1]https://tools.ietf.org/html/rfc7322#section-3.4
Diffstat (limited to 'epan/dissectors/packet-ipv6.c')
-rw-r--r-- | epan/dissectors/packet-ipv6.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/epan/dissectors/packet-ipv6.c b/epan/dissectors/packet-ipv6.c index fd8d596366..f173d263b1 100644 --- a/epan/dissectors/packet-ipv6.c +++ b/epan/dissectors/packet-ipv6.c @@ -2543,7 +2543,7 @@ proto_register_ipv6(void) NULL, HFILL } }, { &hf_ipv6_src, - { "Source", "ipv6.src", + { "Source Address", "ipv6.src", FT_IPv6, BASE_NONE, NULL, 0x0, "Source IPv6 Address", HFILL } }, @@ -2593,7 +2593,7 @@ proto_register_ipv6(void) "Source IPv4-Embedded IPv6 Address with Well-Known Prefix", HFILL } }, { &hf_ipv6_dst, - { "Destination", "ipv6.dst", + { "Destination Address", "ipv6.dst", FT_IPv6, BASE_NONE, NULL, 0x0, "Destination IPv6 Address", HFILL } }, |