I think it should be in informative references. I cited it inline just for clarity in mailing list communications.
We rely on ICANN for "Assigned Names and Numbers", so I think it is perfectly fine to cite their board resolution here (either URL works for me). There are no RFC2119 words in this sentence, but I think readers definitely need to know about this resolution if they're working in this area. thanks, Rob On Thu, Feb 2, 2023 at 12:27 PM Orie Steele <orie@transmute.industries> wrote: > Yes, as the document shepherd this raises questions for me on "normative" > / "informative" etc... > > I welcome any guidance on if this will be acceptable in its current state. > > OS > > On Thu, Feb 2, 2023 at 2:12 PM Rob Sayre <say...@gmail.com> wrote: > >> Martin wrote that he thought the ICANN citation needed to be more >> concrete. The document at >> https://features.icann.org/ssac-advisory-use-emoji-domain-names >> says: >> >> "SSAC Advisory on the Use of Emoji in Domain Names >> Resolution of the ICANN Board >> Meeting Date: >> Thu, 2 Nov 2017 >> Resolution Number: >> 2017.11.02.09 – 2017.11.02.12 >> URL for Resolution: >> >> https://www.icann.org/resources/board-material/resolutions-2017-11-02-en#1.e >> " >> >> I don't see a problem with the citation as it stands, but maybe that >> resolution URL would work? I think the current one is fine, though. No >> strong feelings here. >> >> thanks, >> Rob >> >> _______________________________________________ >> Uta mailing list >> Uta@ietf.org >> https://www.ietf.org/mailman/listinfo/uta >> > > > -- > *ORIE STEELE* > Chief Technical Officer > www.transmute.industries > > <https://www.transmute.industries> >
_______________________________________________ Uta mailing list Uta@ietf.org https://www.ietf.org/mailman/listinfo/uta
