> -----Original Message----- > From: Andrew Newton [mailto:a...@hxr.us] > Sent: Wednesday, February 14, 2018 2:48 PM > To: Hollenbeck, Scott <shollenb...@verisign.com> > Cc: p...@dotandco.com; regext@ietf.org > Subject: [EXTERNAL] Re: [regext] I-D Action: draft-ietf-regext-rdap- > object-tag-00.txt > > On Tue, Feb 13, 2018 at 7:16 AM, Hollenbeck, Scott > <shollenb...@verisign.com> wrote: > > > > Agreed, which is why I'm trying to get some discussion going. Folks, if > you're either running an RDAP service or planning to do so in the future > it would be very helpful to talk through this proposal. > > Well, we discussed this in Chicago and there seemed to be pretty good > feedback. As both an operator and a client author I like this idea (even > if I'm not wild about the tilde character). Having a standard short cut to > say "this is meant for the XXX registry" would be beneficial to clients, > even if server operators don't actually append the tags to their objects. > I've thought about cludging something together for NicInfo using the > existing IANA .json files, but having a formal registry would be much > better.
Building on Andy's comment... It may help to explain (perhaps even in the document) where the tilde character came from. I didn't want to use a character with a URI-reserved value, so that led to looking at the list of unreserved characters from Section 2.3 of RFC 3986. Here's the description: unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~" ALPHA and DIGIT are out because they are commonly used in the identifiers themselves. I'm pretty sure, but not 100% certain, that "-" (HYPHEN MINUS) falls into the same category, which is why I changed from using that character between the -00 and -01 versions of the individual submission version of this document. That leaves ".", "_", or "~". If any one of these is better than the others I'm perfectly willing to make a change. Scott _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
