From 269a9b61b8d258dcce8f0893ab94e0b7153255fd Mon Sep 17 00:00:00 2001 From: Willy Tarreau Date: Tue, 25 Feb 2020 18:04:39 +0100 Subject: [PATCH] DOC: proxy-protocol: clarify IPv6 address representation in the spec Daniel Barclay reported that the wording around "IPv6 addresses must be indicated as series of 4 hex digits" is confusing and can be interpreted two ways (only 4 digits or series of sets of 4 digits), so let's adjust the wording to resolve this ambiguity. --- doc/proxy-protocol.txt | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/proxy-protocol.txt b/doc/proxy-protocol.txt index 52d7bc71c..26f86a345 100644 --- a/doc/proxy-protocol.txt +++ b/doc/proxy-protocol.txt @@ -223,11 +223,11 @@ flowing from the sender to the receiver : written in decimal representation separated by exactly one dot between each other. Heading zeroes are not permitted in front of numbers in order to avoid any possible confusion with octal numbers. IPv6 addresses must be - indicated as series of 4 hexadecimal digits (upper or lower case) delimited - by colons between each other, with the acceptance of one double colon - sequence to replace the largest acceptable range of consecutive zeroes. The - total number of decoded bits must exactly be 128. The advertised protocol - family dictates what format to use. + indicated as series of sets of 4 hexadecimal digits (upper or lower case) + delimited by colons between each other, with the acceptance of one double + colon sequence to replace the largest acceptable range of consecutive + zeroes. The total number of decoded bits must exactly be 128. The + advertised protocol family dictates what format to use. - exactly one space : " " ( \x20 )