Adding specification of more protocols

README.md

@@ -112,9 +112,9 @@ and [protocols/](protocols/) for specifications of the currently supported proto
 
 TODO: most of these are way underspecified
 
-- /ip4, /ip6
+- [/ip4](protocols/IP4.md), [/ip6](protocols/IP6.md)
 - /ipcidr
-- /dns4, /dns6
+- [/dns](protocols/DNS.md), [/dns4](protocols/DNS4.md), [/dns6](protocols/DNS6.md)
 - [/dnsaddr](protocols/DNSADDR.md)
 - /tcp
 - /udp

protocols/DNS.md

@@ -0,0 +1,21 @@
+# `dns`
+
+`dns` is a protocol that defines which domain name should be used.
+
+## Representation Format
+
+### Human-readable
+
+The human-readable format of the `dns` protocol uses the well-known textual representation:
+
+	example.com
+
+TODO: Consider also supporting with trailing dot.
+
+### Binary
+
+TODO: Consider binary format. Is it a string prefixed by an unsigned varint or should the FQDN encoding be used, where every label is prefixed and the last label has zero length?
+
+## Binary Size
+
+Unknown

protocols/DNS4.md

@@ -0,0 +1,21 @@
+# `dns4`
+
+`dns4` is a protocol that defines which domain name should be used, but only by resolving it to a IPv4 address.
+
+## Representation Format
+
+### Human-readable
+
+The human-readable format of the `dns4` protocol uses the well-known textual representation:
+
+	example.com
+
+TODO: Consider also supporting with trailing dot.
+
+### Binary
+
+TODO: Consider binary format. Is it a string prefixed by an unsigned varint or should the FQDN encoding be used, where every label is prefixed and the last label has zero length?
+
+## Binary Size
+
+Unknown

protocols/DNS6.md

@@ -0,0 +1,21 @@
+# `dns6`
+
+`dns6` is a protocol that defines which domain name should be used, but only by resolving it to a IPv6 address.
+
+## Representation Format
+
+### Human-readable
+
+The human-readable format of the `dns6` protocol uses the well-known textual representation:
+
+	example.com
+
+TODO: Consider also supporting with trailing dot.
+
+### Binary
+
+TODO: Consider binary format. Is it a string prefixed by an unsigned varint or should the FQDN encoding be used, where every label is prefixed and the last label has zero length?
+
+## Binary Size
+
+Unknown

protocols/IP4.md

@@ -0,0 +1,23 @@
+# `ip4`
+
+`ip4` is a protocol that defines which IPv4 address should be used.
+
+## Representation Format
+
+### Human-readable
+
+The human-readable format of the `ip4` protocol uses the quad-dotted format:
+
+	127.0.9.1
+
+TODO: Consider also supporting decimal format.
+
+### Binary
+
+The binary format of the `ip4` protocol uses the well-known binary format of 32 bits:
+
+	0x7F 0x00 0x00 0x01
+
+## Binary Size
+
+32 bits (Implicit)

protocols/IP6.md

@@ -0,0 +1,23 @@
+# `ip6`
+
+`ip6` is a protocol that defines which IPv6 address should be used.
+
+## Representation Format
+
+### Human-readable
+
+The human-readable format of the `ip6` protocol uses the colon-seperated format:
+
+	2604:1380:4602:5c00::3
+
+TODO: Consider also supporting decimal format and/or format that encloses the IP address with `[` and `]`.
+
+### Binary
+
+The binary format of the `ip6` protocol uses the well-known binary format of 128 bits:
+
+	0x26 0x04 0x13 0x80 0x46 0x02 0x5c 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x03
+
+## Binary Size
+
+128 bits (Implicit)