CAMEL is OK but the first thing that occurred to me was, for symmetry with DNSOP, call it DNSINT.
Thanks, Donald =============================== Donald E. Eastlake 3rd 2386 Panoramic Circle, Apopka, FL 32703 USA [email protected] On Tue, Oct 6, 2026 at 1:22 PM Joe Abley <[email protected]> wrote: > > Hi all, > > I realise that thinking up names for things is everybody's favourite hobby, > but I suggest that since dnsext is an old, closed working group and what we > are talking about is a new, open working group with a fresh charter, a > different name is the path of least confusion. > > I'm sure I'm not the only one who suggested the name camel for this new > working group, but I do think it is excellent. Anybody who doesn't understand > it has a motivation to find out about it, which is an exercise I might > suggest is entirely worthwhile. > > > Joe > > On 6 Oct 2026, at 18:59, Frederico A C Neves > <[email protected]> wrote: > > On Tue, Oct 06, 2026 at 03:22:09PM +0200, Ondřej Surý wrote: > > If we need a boring self-explanatory name, I would be happy to go back to > dnsext... > > > dnsext will definitely help with old archives, lists, .procmail, mutt > macros and obviously good memories ;-) > > > Ondrej > -- > > > Fred > > Ondřej Surý (He/Him) > [email protected] > > A gentle nudge is always appreciated if I take a little longer to reply. > > On 6. 10. 2026, at 15:18, Paul Wouters <[email protected]> wrote: > > > Congratulations on doing the split that had been needed since dnsext closed > decades ago! > > > On Oct 6, 2026, at 09:04, Ondřej Surý <[email protected]> wrote: > > Hi everyone, > > my humble proposal for the name of the new INT WG DNS group is... > > CAMEL - Continued Amendment and Maintenance of Essential Lookups > > > Cute ! > > But more seriously, names should be meaningful and where possible self > explanatory- especially to help new participants, so something as boring as > dnsdev would be much better even if it’s far less fun. > > Note that as I have previously said, the role of Tech Advisor is ill defined > at the IETF level already, and is especially a poor fit for dnsop, which is > literally a room full of Tech Advisors. It puts an uncomfortable poorly > defined weight on the opinion of one dns expert’s view. (I hold this view > this irrespectively of the person assigned to this role, past, current and > future, and think this position should be abolished entirely, including the > one I am uncomfortably holding at WIMSE - I think that was a mistake too and > I’d be happy to lose that role there) > > Paul > > > _______________________________________________ > DNSOP mailing list -- [email protected] > To unsubscribe send an email to [email protected] > > _______________________________________________ > DNSOP mailing list -- [email protected] > To unsubscribe send an email to [email protected] > > > _______________________________________________ > DNSOP mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
