Re: [dns-wg] retaining ripe.int
Totally agree. The ripe.int domain comes from the time of ip6.int (another bad idea) and the perceived need of alternatives to arpa (for the wrong reasons). The sooner this gets dropped the better. Joao > On 30 Jun 2015, at 20:16, Jim Reid wrote: > > On 30 Jun 2015, at 18:53, Peter Koch wrote: > >> This is probably an exception for the lack of a drop catching risk, >> but keeping the domain to maintain a stake in the INT domain >> might be OK. > > That is a remarkably bad idea. The .int domain's supposed to be for > international treaty organisations. The NCC is not one. There is no reason > why it should "maintain a stake in the INT domain". It simply shouldn't have > a stake in this at all. If anything the NCC should be running away from .int > as fast as is humanly possible. > > signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [dns-wg] IDN registration question
> On 21 Apr 2016, at 15:26, Shane Kerr wrote: > > > > "𓎟𓀀 try registering the puny code version? xn--5o7dx5d.com Joao
Re: [dns-wg] Yeti DNS and the RIPE NCC
I think this fits the RIPE NCC very well given their role as “more than just an RIR”, their past and ongoing research work as well as their expertise in running of the Internet’s DNS root servers and their ability to both inform future experiments and translate outcomes into root server operations as applicable. Joao > On 24 May 2016, at 14:41, Shane Kerr wrote: > > Dear DNS folks, > > As many of you are aware, a group of researchers and other interested > people and groups has been building and operating a root server testbed > over the past year. This is the Yeti DNS project: > > http://yeti-dns.org/ > > We have just finished our first experiment, and have started our second > one. The network has 25 root servers from 14 different organizations, > along with a number of recursive resolvers configured to use them. > > We have approached the RIPE NCC to encourage them to run a Yeti root > server, and they feel that this is something that we should engage with > the RIPE community about. > > We are still looking for more Yeti root operators, and we think that > the RIPE NCC would be awesome in this capacity, given their unique role > in the DNS world (they are the only RIR who is also a root operator, > plus they do a lot of work supporting various ccTLD). Personally I > think that the goals of the Yeti project fit in very well with > the mission of the RIPE NCC. > > Please let us know what you think about this idea. I'm happy to answer > any questions about the project or what it would mean for the RIPE NCC > to run a Yeti root server. > > Cheers, > > -- > Shane
Re: [dns-wg] Yeti DNS and the RIPE NCC
Actually Jim, first comes the poll of the community to see if this fits, later comes what you suggest, if the community decides to ask the RIPE NCC to look into it, or have we become the Ministry of IP? Joao > On 25 May 2016, at 09:55, Jim Reid wrote: > > >> On 24 May 2016, at 13:41, Shane Kerr wrote: >> >> Please let us know what you think about this idea. > > > Before we take this idea forward, could someone please suggest metrics and > milestones that could be used to assess the success or failure of this > activity? For bonus points, it would be good to know what sort of resource > commitments will be needed and the level of reporting that can be expected > from the NCC being involved in Yeti DNS. > > We should be careful to not have the NCC get into open-ended, vague > commitments where there's uncertainty about the on-going value to the > community. Experiments are all very well but both the WG and the NCC's DNS > team need to know how/when to decide to kill the experiment or turn it into a > formally supported resource or do something else with it. > >
Re: [dns-wg] DNS WG co-chair nomination
I share what John said Joao > On 01 Sep 2016, at 11:58, John Bond wrote: > > On 01/09/2016 08:20, Shane Kerr wrote: >> Hello DNS working group, >> >> I nominate myself as co-chair of the DNS working group. > I think you would make a good co chair and would like to express my > support for this nomination. > > John >
Re: [dns-wg] Volunteer list for RIPE DNS working group chair
Hi Randy I agree with you and that’s why i pushed for the dns wg to have a blind period of candidate collection during which no one sees who else might be volunteering. What you see now is the publication of the candidate list after that period elapsed. Turns out no one else volunteered On top of that we have term limits to “force” renewal, so basically I think we agree Joao > On 15 Oct 2020, at 19:47, Randy Bush wrote: > > >> >> Supporting Joao is a no-brainer - +1 > > actually, i would suggest it is not. > > [ aside: i like joão, and think he has done a fine job. i might join > the +1s, except for the following ] > > i thought we wanted to encourage new/young folk to enter and play. when > we have an 'election' and an incumbent instantly steps up, and 42 people > all say +1, all within a day or two, this is a total barrier to any new > entrant. > > so, to put our money where our mouths are [0] two suggestions > > o no +1s. leave it until the actual election > > o we might think about term limits > > randy > > -- > > [0] idiom meaning to walk what we talk [1] > > [1] idiom meaning to do as we say :) >
[dns-wg] DNS wg co-chair selection: candidates
Dear all, The deadline for DNS WG co-chair candidate volunteering is now over. I am happy to announce that we have two great candidates. The period to express support for your preferred candidate(s) starts now and runs until November 24th 2021. Shane Kerr and myself, as continuing wg co-chairs hope to announce consensus at the DNS WG session during RIPE 83 Below find the candidate names and a few words from each === Moritz Müller - Dear RIPE WG, I would like to volunteer to become a DNS working group co-chair. As a frequent participant and an occasional presenter at this working group I would like to help making sure that the program of the working group meetings continues to stay interesting and relevant. I'm working for the research department of the Dutch ccTLD operator SIDN for more than 6 years. There, amongst other topics, I have been studying different aspects of DNSSEC and domain name abuse. Also, I'm a guest researcher at the University of Twente in the Design and Analysis of Communication Systems group (DACS). I believe that my experience working in industry and academia will help me finding and selecting speakers that provide relevant and novel insights to the working group members. Please feel free to contact me in case of any questions or if you would like to get to know me a bit better. Email: moritz.mul...@sidn.nl === Brett Carr —— Over the past 20 plus years I have worked with DNS holding a variety of industry related roles ranging from working for a global ISP to working at RIPE NCC (Leading the team who run K Root). I have also worked at ICANN (Assisting with the GTLD Programme) and for the last 13 years Nominet, helping to keep .uk safe and stable. I have designed, deployed and managed DNS and DNSSEC implementations both small and large and have been responsible for designing and operating Nominet’s GTLD DNS/DNSSEC Platform which has now grown to operating 80 TLDs. I am an experienced leader having led various engineering teams across operations during my time at Nominet. I have and continue to enjoy playing an active role in the DNS Community, giving presentations at OARC, RIPE and ICANN amongst others. I’m currently serving as the Vice Chair of the CSC at ICANN, I am an active member of the ICANN TLD Ops steering committee and have been a member of the OARC PC for the past year. I would relish the challenge of working with the other chairs to bring some fresh ideas to the DNS-WG. === Regards, see you soon, Joao on behalf of the DNS WG co-chairs
