> On 22. Aug 2022, at 11:41, Andrew McConachie <and...@depht.com> wrote:
>
>
>
> On 20 Aug 2022, at 2:55, Warren Kumari wrote:
>
>> On Fri, Aug 19, 2022 at 5:46 PM, Stephen Farrell <stephen.farr...@cs.tcd.ie>
>> wrote:
>>
>>> Hiya,
>>>
>>> On 19/08/2022 20:43, Warren Kumari wrote:
>>>
>>> So, it is perfectly acceptable (in my view) for it to have:
>>>
>>> Reference Name
>>> ---------------------------------
>>> a-cool-document foo.alt
>>> another-document foo.alt
>>> yet-another-doc bar.alt
>>>
>>> I agree that such duplicate names are acceptable in this registry.
>>>
>>> I scanned the draft quickly and think it's good. (I'll try do a closer
>>> read in a few days.)
>>>
>>> Only thing with which I'd argue for now is that I think RFC required is a
>>> much simpler rule for the registry.
>>>
>
> The draft doesn’t specify if this registry is restricted to ASCII LDH or not.
> Can I write an RFC and get #&^%&^%)(}{.alt?
>
> How about ..alt? Or .alt? (My proposed string is NULL)
>
> Why not allow unicode or at least some subset of it? If we want people to use
> this registry for their hip new naming system I think we should encourage
> developers to move away from ASCII LDH.My interpretation is that there are no restrictions at all after ".alt". (I assume ".alt" should be in a format that DNS resolvers / servers understand). I can see the pros and cons of this approach. Implementing any kind of restrictions will open pandora's box wrt registration policy / reviewer considerations. Not having any kind of restrictions will leave the registry open to strange requests like the ones you highlight. I think you have pick one of those evils. Also: Given that it is unknown what encoding a protocol may use, it may be reasonable to consider that instead of Unicode, a byte string is provided with an optional encoding hint? For GNS, Unicode/UTF-8 would work fine, however. BR > > —Andrew > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
