IT and software
Protocol headers are read 32 bits wide
Protocol headers are drawn 32 bits wide because that is the unit they are read in: the width of a field is its bit count, and nothing that does not divide into 32 ever appears
This drawing comes from one YAML file. No shape was moved by hand.
Notes in the source (in Japanese)
幅がビットの数そのもの。 RFC の図が 32 ビット幅なのは、その単位で読むから。
4 + 4 + 6 + 2 + 16 = 32、16 + 3 + 13 = 32 ——32 で割り切れない並びは出てこない。 行がそろうように決めてある。
IHL と Data Offset があるから、うしろにオプションを足せる(ヘッダの長さを、ヘッダ自身が持っている)。
入れ子にすると MTU 1500 から IP 20 + TCP 20 を引いた 1460 が MSS。Ethernet の 14 + 4 バイトは MTU の外。
出典(2026-09-29 取得):IPv4 は RFC 791、DSCP は RFC 2474、ECN は RFC 3168、TCP は RFC 9293(Flags 8 ビット = CWR・ECE・URG・ACK・PSH・RST・SYN・FIN、Reserved 4 ビット)。https://www.rfc-editor.org/rfc/rfc791 / https://www.rfc-editor.org/rfc/rfc9293
Source (YAML)
examples/gallery/234-プロトコルのヘッダ.zumen.yaml
More in this field
An on-premise server layout rack by rack, with the redundant power feeds and network links drawn as separate paths
A cloud architecture showing the VPC and its subnets, and where the load balancer, application, database and object store sit
Where data goes from collection through transformation, storage and aggregation to display, and what kind of container holds it at each step
A network layout of the links and equipment between sites, with the address range carried by each segment
An order management ER diagram with primary and foreign keys, and the one-to-many relationships drawn as crow feet
A server room where racks face each other to make hot and cold aisles, with the clearance of each aisle written in
A UML class diagram where inheritance, realisation, association and aggregation are told apart by line type and end symbol
A UML state machine with transitions, the events and guards that fire them, and the pseudostates that begin and end it