- dns-wg - mailman.ripe.net

RIPE NCC domain registrations
by Romeo Zwart 17 Sep '15

17 Sep '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dear colleagues, We have completed the release of some currently unused domains. We informed you of these plans in June: <https://www.ripe.net/ripe/mail/archives/dns-wg/2015-June/003097.html> The deleted domains are: ripe-ncc.org ripe-ncc.com ripe-ncc.net ripencc.com ripencc.net ripencc.org ripelabs.net ripen.cc ripe.int ipv6roadshow.com ipv6roadshow.net ipv6roadshow.org We welcome any and all feedback from the community. Kind regards, Romeo Zwart -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJV+nYZAAoJEKnY9vIUvfudRnoQAJRUVW3f/OEyVQ0rTcQ7Xaj7 PReR2pDSDHdCYxdsOhYvLL99bhz/YAubCRNlSKPPggiYIVSEE7o16Mg0QljmLr9s S5Sclw7IaDlADesHr+hw9NG4Y4MRIq6QwFDGV7zrmm6AfRFnIkWsqIjrsMC15p1T 0Vtp+RWQT229EQsigywsjwy4gbJozex5aHfASYINya3Qzs50NFOExRv42B1aPYSm 9Nv/oY50HpZ7bIbLYXEQEZfLMs0ek8nbIkbpymqgAD642F32R54u4FUgU3eZIRpS HHLwGuNopoaX2m6wrRUSvn2CREEOwnuseWRF2fBQ/v0TaJRRRsU/igvrIJjV3kYr vJrT563uInSHImm3Zdv+cJU+XsUYO2WefoY+hBSrH68FQTT9CbnBQcbTfK1+9RAE UZezZ/P1kKI6Zs1UzaVIas1+dmjW1Z8cnLasilSEPGkSAb8iSjj3/+hBx74arNIz Y5uvpMs3pOJENE7JHcmGaRSN6jEZGc6pk30LLiE9+PGIJ4lxtAPkf4F3WHxU0+H7 fkUvzL+cMqdv68MLsfHJrUr/wu3yQswIb4bpknbpJRXXv+J7IpARQi8Srcx4hZSz esjuA79AoR3Tn1slsxY3sNXZCp5q6Cfu5V4H8PZi4YPIFtdr+d5ucwuSE3SlxKLH m9v2no6AXHYdMxqPFLmp =goAX -----END PGP SIGNATURE-----

2 1

New zones added to DNSMON (.is, .nu, .om, .ua)
by Vesna Manojlovic 04 Sep '15

04 Sep '15

Dear colleagues, We continue to receive requests to add new zones to the DNSMON service, and are currently waiting for guidelines regarding an official process for this from the DNS Working Group. In the meantime, we have decided to accept only those requests from ccTLDs from the RIPE NCC service region or from RIPE NCC members, and only if requested by the zone operator. Out of the 12 requests we’ve received so far, four zones met these criteria. These four zones have now been added to DNSMON: https://atlas.ripe.net/dnsmon/group/is https://atlas.ripe.net/dnsmon/group/nu https://atlas.ripe.net/dnsmon/group/om https://atlas.ripe.net/dnsmon/group/ua If you have any suggestion about the process, please join the discussion on this mailing list. For other questions, please contact us at atlas(a)ripe.net Kind regards, Vesna Manojlovic Manager of Measurements Community Building RIPE NCC

1 0

2nd Call for presentations RIPE 71
by Benno Overeinder 02 Sep '15

02 Sep '15

Colleagues, Please note the approaching deadline of 13 September 2015 for RIPE 71 plenary programme submissions. You can find the CFP for RIPE 71 below, or at https://ripe71.ripe.net/submit-topic/cfp/, for your proposals for plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. Kind regards, Benno Overeinder RIPE PC Chair https://www.ripe.net/participate/meetings/ripe-meetings/pc ---------------------------------------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. RIPE 71 will take place from 16-20 November 2015 in Bucharest, Romania. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 71. See the full descriptions of the different presentation formats, https://ripe71.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 13 September 2015. Proposals submitted after this date will be considered depending on the remaining available space in the programme. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity in operations - Commercial transactions of IPv4 addresses - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange Submissions RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour - Lightning talks: 10 minutes The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe71.ripe.net/submit-topic/submission-form/. - Lightning talks should also be submitted using the meeting submission system (https://ripe71.ripe.net/submit-topic/submission-form/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice---in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. - Due to potential technical issues, presenters/panellists should be physically present at the RIPE Meeting. If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0

Agenda items for RIPE71
by Jim Reid 13 Aug '15

13 Aug '15

Colleagues, it may seem odd to be doing this at the height of the summer holidays when the next RIPE meeting is 3 months away. If you have suggestions for agenda topics or presentations for the WG session(s) in Bucharest, could you please contact the co-chairs at dns-wg-chairs(a)ripe.net? Thanks. The draft meeting plan has allocated just one slot for the WG. It's tentatively scheduled for the Thursday morning (https://ripe71.ripe.net/programme/meeting-plan) The WG will only get a second slot (ideally also on the Thursday) if we have a draft agenda which shows the extra slot is needed. We also need to do that before any other WGs try to grab the currently free slots. So the sooner we can get an outline agenda put together, the better! Your co-chairs often get last-minute suggestions and/or overspill from the plenary which can be tricky to accommodate. That could be harder if we just have a single slot next time. So to avoid disappointment, please try to give us plenty of advance notice for your proposed agenda items and discussion topics. Ta. I hope you all enjoy the summer holidays and look forward to seeing everyone at RIPE71.

1 0

FYI: Live-streaming the Root Zone Key-Signing Key Ceremony 22
by Jaap Akkerhuis 12 Aug '15

12 Aug '15

In case people missed this announcment and are interested. jaap FYI, (Apologies if you see duplicates of this message.) ICANN, as the IANA Functions Operator, will be live-streaming the Root Zone Key-Signing Key Ceremony (number 22) on Thursday, August 13. The "main" ceremony that day is scheduled to begin at 2000UTC. (This is an activity related to DNSSEC.) For more information about the event see: https://www.iana.org/dnssec/ceremonies/22 On Thursday there will be two cermonies as listed on that web page. The first ceremnoy will rotate cryptographic officer duties, basically, a change in some of the trusted community representatives participating in the key ceremonies. The second ceremony (the "main") will feature the introduction of two new Hardware Security Modules. This is the ceremony that will start at 2000 UTC. Please see the above link for more information. The live-streaming link is at the bottom of the page. (https://icann.adobeconnect.com/kskceremony)

1 0

Live-streaming the Root Zone Key-Signing Key Ceremony 22
by Edward Lewis 12 Aug '15

12 Aug '15

FYI, (Apologies if you see duplicates of this message.) ICANN, as the IANA Functions Operator, will be live-streaming the Root Zone Key-Signing Key Ceremony (number 22) on Thursday, August 13. The "main" ceremony that day is scheduled to begin at 2000UTC. (This is an activity related to DNSSEC.) For more information about the event see: https://www.iana.org/dnssec/ceremonies/22 On Thursday there will be two cermonies as listed on that web page. The first ceremnoy will rotate cryptographic officer duties, basically, a change in some of the trusted community representatives participating in the key ceremonies. The second ceremony (the "main") will feature the introduction of two new Hardware Security Modules. This is the ceremony that will start at 2000 UTC. Please see the above link for more information. The live-streaming link is at the bottom of the page. (https://icann.adobeconnect.com/kskceremony)

1 0

FYI: Design Team Review of Plan for DNS Root Zone KSK Change
by Jaap Akkerhuis 07 Aug '15

07 Aug '15

The next annoncement might be of interest to readers this mail list. <https://www.icann.org/public-comments/root-ksk-2015-08-06-en> Purpose: This public comment proceeding seeks to review the Design Team’s findings to date related to issues and plans for changing the cryptographic key used to originate the DNSSEC chain of trust. Current Status: The Design Team has generated a preliminary report and will accept wider review. Next Steps: After the public comment proceeding, the Design Team will finalize its report and plan for changing the cryptographic key. jaap

1 0

RIPE NCC secondary DNS configuration changes complete
by Anand Buddhdev 03 Aug '15

03 Aug '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dear colleagues, We announced some changes to the RIPE NCC's DNS provisioning infrastructure in June: https://www.ripe.net/ripe/mail/archives/dns-wg/2015-June/003095.html We have now completed this configuration change. The new servers are functioning as the hidden masters for ns.ripe.net, and the old server (193.0.0.198) is no longer performing this function. If you have any questions, please reply to <dns(a)ripe.net> Regards, Anand Buddhdev RIPE NCC -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVv0GcAAoJEBXgoyUMySoFXeQP/2R5fp28whuZxVWIncpk8wKg 00pZ07BDbPChyaxhF2f6NHMmTfJV3yp1xXI6tIoQbzmo602lTMnBvywH2ic4P8fO vOsSlBHqSkR5SCsNJ+AoMVbqpUygH7Sr9Om3H7hRFWzfS3PWfLd2YSdRRrV9LR9r 8A5B6sqy5dKWGcT1FfBJvmNHXBnLLDaFA6PpibNA8dN+9mteARyPuBPwF/u+tfCC dD4neRw5eI2M7C7B5313W33R4l57oCvHX7eeuKsfRQzWCOMHqlVQoWP/+/JfVZRG iMBtEUKpfXTMNOIDh1ikRHV7Ra6yWY57g8uWqs9umW6PfY3zSGAL1U+U7ExARvyU /6Ags0/71FWQUM26nNnvYuhpWP2IHoNuOHt1IFZ4UqNgGxRH+IGL8Nagm60DeHnT cOltmiygMs2MWs+ej560URsze82pAPFCauqIv1r0HArUhSPQEX90PbsPzyESL4PL G6rJfw5k1PtEApeos9ezlI4HRuMfWHMEO5HgQ5Eb6dSDv7XHfZMbKKxTgup1jPUk sjfSTPidbWj4pFsMkI+a3er8IPk1vEe2Z53BQR+ateMDK6Oa5aUoqz5sZBrklI5z 4EqRsn2Z44bQFVHMv71wiG55r4s9MP+MrBmyS4JIcK1OJmOYt86YBwtT37o+evsT FRu9FqzOQ3L9+wj7S/6h =07hR -----END PGP SIGNATURE-----

2 1

DNS-WG co-chair selection process
by Jaap Akkerhuis 07 Jul '15

07 Jul '15

All, In May we published the last proposal to adopt the co-chair selection process[1]. At the ripe-70 meeting Jim repeated this status and asked for last comments. Given that there has been no discussion after May, I'm happy to declare consensus to adopt the process as stated in [1]. Regards, jaap, speaking as co-chair [1] <https://www.ripe.net/ripe/mail/archives/dns-wg/2015-May/003089.html>

1 0

RIPE NCC domain registrations
by Romeo Zwart 01 Jul '15

01 Jul '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dear colleagues, The RIPE NCC holds a number of domains besides ripe.net. Some of these domains were only registered as a "protection" mechanism, which was considered good practice at the time. We now plan to release the following domains, which are not being actively used by the RIPE NCC: ripe-ncc.org ripe-ncc.com ripe-ncc.net ripencc.com ripencc.net ripencc.org ripelabs.net ripen.cc ripe.int ipv6roadshow.com ipv6roadshow.net ipv6roadshow.org Depending on the registration expiration date of each of these domains, we will either let the domain expire or take steps to actively delete it. The following domains held by the RIPE NCC are still in use. We have no immediate plans to release any of these domains: ripe.net enumdata.org enog.org nro.net nro.org ipv6eyechart.net ipv6actnow.org ipv6actnow.com ipv6actnow.net Please let us know within two weeks if you have any comments or feedback about this process. Kind regards, Romeo Zwart -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVkovvAAoJEKnY9vIUvfudPR8P/0PEnpvz435gKM941vSf7j3U rqYcnBD54MQBiw8MaUA4Q+UTjw/DsHsFw/EISXt1EFITp2ACrLBesQbMWWtr/V3Q ylz1DRDiRI8JKWuKvoAbCKcdwpbeH6C3JhNl4wlSvmNUq47EFF7la24XvpiuyrBo 1vf8K9q0I9HfBixXbbqfipd0VGlvw9RKejpTRhUwJ90kR5VytvJMcR+COJlBr/83 q9EHrXmk8fZn8rp/pakygITSxny+psvaaJY9HxffQJM23iClSPz11kwGmFFvhYFf JIxDvzbVtYPZHpZCKK20UWisXcrQsu7XdVNV4zechKzf+H7kHR5O+ODGsKE6w91A G1bWOlqqC9jLDIaq8pTKLV1kwtyM/1Ng2ZA8yG9Xk1RHnKkDCVBLZiShyjbd/MWs xwdqs9JKXVwKjaIBJq5p64pR3i94rHdn9qepfNgXQ8bbtEy+xHtlBpLce0jMoHKA y87Z7a82NyZymose6xfPIdF+Jz6FqDKyOxk3MwjC9b3XeEGbh9WpvzvSCn1b7ZIx gD3fcFC7xgQxTqo898CiZjDrxSwE7MXG0rSfZ3jDH9prrPyK6L4MpMalISqW5vvK Vu6m/vQQSIb4qamc1BaGBtLCroEQJP94Cs3OvwEg4mAKpmysfn9ZMyxnjdsDHSsw YnZLUwD60vPiurov+Am0 =4MS6 -----END PGP SIGNATURE-----

9 12