(In reply to comment #61)
> Kaspar, why do you disallow a wildcard to be followed by
> additional characters in the leftmost component? That
> requirement is not in RFCs 2595 and 4513.
It is, actually: both allow it as "*the* left-most component/DNS label", which implies that it can neither be preceded nor followed by any additional characters.
The rules which I implemented don't follow slavishly the RFCs in any case - e.g., none of them requires the component with the wildcard character to be followed by two additional components. We arrived at this solution in earlier discussions (see comment 25, inter alia).
(In reply to comment #61)
> Kaspar, why do you disallow a wildcard to be followed by
> additional characters in the leftmost component? That
> requirement is not in RFCs 2595 and 4513.
It is, actually: both allow it as "*the* left-most component/DNS label", which implies that it can neither be preceded nor followed by any additional characters.
The rules which I implemented don't follow slavishly the RFCs in any case - e.g., none of them requires the component with the wildcard character to be followed by two additional components. We arrived at this solution in earlier discussions (see comment 25, inter alia).