Hi Stéphane,
Good idea, I find the RFC simple and straightforward but I have one
question.
Thanks for having taken the time to read the document.
2.1 :
[S] COMPRESS DEFLATE X-SHRINK
Is the last capability a good example, giving RFC 6648?
7.1 :
To avoid the risk of a clash with a future registered NNTP
compression algorithm, the names of private compression algorithms
SHOULD begin with "X-".
Same remark.
I agree that it should be changed somehow, as well as Section 2.2.3
where X-SHRINK is also mentioned.
Suggestion: using "SHRINK" instead of "X-SHRINK" as capability label,
and just remove sentences about "X" or "X-" in Section 7.1.
Thanks again Stéphane for recalling the existence of RFC 6648.
--
Julien ÉLIE
« Ça n'a été qu'un coup de glaive dans l'eau. » (Astérix)