April 2010 - NLNOG - mailman3.nlnog.net

NLNOG slowchat IRC?
by a.trouwborst＠vivor.net 20 Aug '10

20 Aug '10

Hi all, Ik geef ruimschoots toe dat ik de afgelopen twee jaar onder een steen heb gelegen, maar what ever happened to het IRC kanaal? -- Met vriendelijke groet, Ad Trouwborst VIVOR B.V. Internet voor professionals T. 035 - 52 394 16 F. 035 - 52 394 17 W. www.vivor.net E. info at vivor.net

6 9

DNSSEC Deployment in ARPA Children
by joe.abley＠icann.org 28 Apr '10

28 Apr '10

Colleagues, ICANN plans to begin a test deployment of DNSSEC in various zones starting on 2010-04-29: IN-ADDR-SERVERS.ARPA IP6.ARPA IP6-SERVERS.ARPA IRIS.ARPA URI.ARPA URN.ARPA These zones will be signed using RSASHA256 and NSEC with 2048-bit KSKs and 1024-bit ZSKs. Given DNSSEC deployment experience to date, ICANN does not expect the signing of these zones to cause any operational problems. However, should you have any concerns please feel free to contact us at ticket at dns.icann.org or phone +1 310 301 5810 (e-mail/ticket preferred). At the end of the test period, given no observed or reported harmful effects, ICANN will arrange for trust anchors for these zones to be included in ARPA as DS RRSets and will invite the five RIRs to submit DS RRSet add/delete requests in IP6.ARPA when they are ready. We anticipate the testing period to last at least two weeks. Regards, Joe Abley Director DNS Operations, ICANN

1 0

Posten op NLNOG
by erik＠bais.name 24 Apr '10

24 Apr '10

Hi, Ik heb begrepen van Ramses dat hij nog niet is approved op de posting lijst van NLNOG. Dat is opzich wel lekker rustig, maar wellicht is het een optie om hem na 9 jr beheer van AS20953 toch een keer op de lijst toe te laten. Mvg, Erik Bais

1 0

Root Zone DNSSEC Deployment Technical Status Update
by joe.abley＠icann.org 15 Apr '10

15 Apr '10

This is the fourth of a series of technical status updates intended to inform a technical audience on progress in signing the root zone of the DNS. RESOURCES Details of the project, including documentation published to date, can be found at http://www.root-dnssec.org/. We'd like to hear from you. If you have feedback for us, please send it to rootsign at icann.org. DOCUMENTATION The following draft document was recently published: - Resolver Testing with a DURZ - TCR - Proposed Approach to Root Key Management ICANN has begun the process of formally soliciting expressions of interest for volunteers from the technical community to act as Trusted Community Representatives. These volunteers will witness cryptographic key ceremonies and also carry out various important roles relating to KSK key management. For more information, see: http://www.icann.org/en/announcements/announcement-12apr10-en.htm Expressions of interest can be submitted here: http://www.root-dnssec.org/tcr/ DEPLOYMENT STATUS KSR exchanges continue between production platforms at VeriSign and ICANN. Build-out of KSK Key Ceremony facilities at ICANN continues, and both facilities (east- and west-coast USA) are expected to be ready on schedule. The incremental deployment of DNSSEC in the Root Zone is being carried out first by serving a Deliberately Unvalidatable Root Zone (DURZ), and subsequently by a conventionally signed root zone. Discussion of the approach can be found in the document "DNSSEC Deployment for the Root Zone", as well as in the technical presentations delivered at RIPE, NANOG, IETF and ICANN meetings. Twelve of the thirteen root servers have now made the transition to the DURZ. No harmful effects have been identified. Some early analysis of packet captures from many root servers surrounding each event was recently presented at the IETF meeting in Anaheim, CA, USA and can be found with other presentation materials at <http://www.root-dnssec.org/presentations/>. PLANNED DEPLOYMENT SCHEDULE Already completed: 2010-01-27: L starts to serve DURZ 2010-02-10: A starts to serve DURZ 2010-03-03: M, I start to serve DURZ 2010-03-24: D, K, E start to serve DURZ 2010-04-14: B, H, C, G, F start to serve DURZ To come: 2010-05-05: J starts to serve DURZ 2010-07-01: Distribution of validatable, production, signed root zone; publication of root zone trust anchor (Please note that this schedule is tentative and subject to change based on testing results or other unforeseen factors.) A more detailed DURZ transition timetable with maintenance windows can be found in the document "DNSSEC Deployment for the Root Zone", the most recent draft of which can be found on the project web page at <http://www.root-dnssec.org/>.

1 0

14/8 and 223/8 allocated to APNIC
by leo.vegoda＠icann.org 14 Apr '10

14 Apr '10

Hi, The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to APNIC in April 2010: 14/8 and 223/8. You can find the IANA IPv4 registry at: http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.txt Please update your filters as appropriate. The IANA free pool contains 20 unallocated unicast IPv4 /8s. Regards, Leo Vegoda Number Resources Manager, IANA ICANN

1 0

Trusted Community Representatives
by joe.abley＠icann.org 13 Apr '10

13 Apr '10

Colleagues, ICANN and VeriSign, with the support of the US Department of Commerce, continue to work towards DNSSEC deployment in the root zone of the DNS. ICANN is looking for Trusted Community Representatives (TCRs) to help us carry out various technical security operations. An announcement can be found here: <http://www.icann.org/en/announcements/announcement-12apr10-en.htm> You can submit an expression of interest here: <http://www.root-dnssec.org/tcr/> DNSSEC key ceremonies are carried out in English. TCRs must therefore have a good understanding of written and spoken English. Regards, Joe

1 0

[dave@aalderingict.nl: RE: Breedband Nederland / AS 5524 Maintenance]
by sabri＠cluecentral.net 06 Apr '10

06 Apr '10

For the record... In 15 jaar heb ik nog nooit een full table gelekt. Helaas helaas helaas voel ik me nu een beetje Theo de Raadt: Only one route-leak in a heck of a long time. Het was niet Dave z'n schuld. Ik heb verzaakt. Niet goed opgelet. U mag mij nu allemaal uitlachen. *buig* Groeten, Sabri ----- Forwarded message from Dave Aaldering <dave at aalderingict.nl> ----- Date: Fri, 2 Apr 2010 18:03:11 +0200 From: Dave Aaldering <dave(a)aalderingict.nl> To: "tech-l at ams-ix.net" <tech-l at ams-ix.net> Subject: RE: Breedband Nederland / AS 5524 Maintenance Hi Peers, So I guess we are not the Easter Bunny after all.... We had trouble with migrating to the new equipment and leaked a full table while we were at it. We did a rollback and are rescheduling maintenance. Sorry for the inconvenience this may have caused. We also caused some max-prefix limits to be tripped. Please clear your sessions if needed. For now, a great Easter weekend to all of you. I do hope you will find some eggs elsewhere ;-) Regards, Dave Aaldering -----Oorspronkelijk bericht----- Van: Raymond Dijkxhoorn [mailto:raymond at prolocation.net] Verzonden: vrijdag 2 april 2010 17:40 Aan: Dave Aaldering CC: tech-l at ams-ix.net Onderwerp: Re: Breedband Nederland / AS 5524 Maintenance Hi Dave, > Breedband Nederland (AS5524, AMS-IX ip 195.69.145.104) will be > migrating its AMS-IX connection to a different router shortly. > > This might cause a BGP flap in the progress. Please be advised. Did you plan to insert some easter eggs? You not only 'might cause' route flaps, but you also 'might cause' some routing leaks :-) You were sending a full table. Please next time be sure you are able to handle the traffic before doing so... Grin. Happy easter! Bye, Raymond. _______________________________________________ tech-l mailing list tech-l at ams-ix.net http://melix.ams-ix.net/mailman/listinfo/tech-l ----- End forwarded message ----- -- Sabri

1 0