Re: [yang-doctors] [Netconf] Yangdoctors last call review of draft-ietf-netconf-keystore-02

[Per Hedeland <[e-mail]>]

On 2017-07-28 12:36, Juergen Schoenwaelder wrote:
> On Fri, Jul 28, 2017 at 12:15:20PM +0200, Per Hedeland wrote:
>> On 2017-07-28 12:09, Per Hedeland wrote:
>>> On 2017-07-28 04:12, Kent Watsen wrote:
>>>>
>>>> Here's another idea, it turns out that the string "base64encoded==="
>>>> is itself a valid base64 string.
>>>
>>> Nice idea, but actually it isn't - i.e. there does not exist an octet
>>> sequence that will encode to that string, and a decoder "should" reject
>>> it as invalid. But maybe that is a feature?:-)
>>>
>>> (By definition, there can be at most 2 trailing '=' characters in the
>>> encoding. You can have "base64encode" or e.g. "base64encodedA==", but I
>>> guess neither is as appealing...)
>>
>> "base64encoding==" is also OK...
>>
> 
> base64encodedvalue== also seems to be OK

Yes, as far as I can see, any string that

a) is restricted to the alphabet
b) is a multiple of 4 characters long
c) has 0, 1, or 2 '=' characters at the end (only)

is valid. But it seemed there was a length restriction in the particular
usage considered here. "base64==" is also OK.:-)

--Per