- NZNOG - lists.nznog.org

IPv6 address allocation questions
by Qinwen Hu 06 Feb '14

06 Feb '14

Hi All, My name is Qinwen(Steven) Hu from the University of Auckland. I am working on my PhD thesis in which I am trying to observe potential new security issues in IPv6 networks. I have two questions I would like to ask network operators: 1) Recently, we did a survey to investigate how network administrators are actually allocating IPv6 Interface IDs around the world. Our results show that 82% of domains use sequential small integer values in the interface ID field for their IPv6 addresses. - What IPv6 address allocation mechanisms do you (or will you) use in your IPv6 network/services? could you please give us your reasons for using these mechanisms? 2) What new security issues, i.e. issues that don't exist in IPv4, do you think are likely to arise? Any replies would be very helpful, please send them to me off-list.Many thanks for your kind consideration. Have a nice day. Regards, Steven 胡勤文／Qinwen Hu Ph.D. Candidate, Computer Science, University of Auckland 奥克兰大学计算机科学博士研究生

1 0

FW: Trusted Community Representation for Root KSK
by Leo Vegoda 06 Feb '14

06 Feb '14

Hi, People on this list might also want to submit responses. Regards, Leo From: dns-operations-bounces(a)mail.dns-oarc.net [mailto:dns-operations-bounces(a)mail.dns-oarc.net] On Behalf Of Kim Davies Sent: Thursday, February 06, 2014 12:38 PM To: DNS Operations Subject: [dns-operations] Trusted Community Representation for Root KSK Hi folks, ICANN is currently performing a consultation on how to evolve the participation of Trusted Community Representatives in the management of the root key signing key. I think this consultation is of particular interest to this group as ultimately these TCRs are there to instill trust in the DNS operations community that the KSK is being managed in a proper fashion. I'd encourage you to provide feedback to this consultation - available at http://www.icann.org/en/news/public-comment/tcr-dnssec-key-signing-21jan 14-en.htm - by 11th February. It is important we have a model of TCR participation that is satisfactory to the community. For convenience, here are the terms of reference replicated: Background Since July 2010, the DNS Root Zone has been secured using DNSSEC[1]. The model of using DNSSEC in the DNS Root Zone revolves around a "key signing key" (KSK) that is managed by ICANN in two secure facilities. Four times a year, a ceremony is conducted at these facilities to perform operations involving the KSK. As a key part of this process, a minimum of three from a pool of 21 trusted community representatives (TCRs) attend each ceremony to enable access to the secure materials, to witness the procedure, and to attest that the ceremony was conducted properly[2]. Each ceremony is attended by ICANN staff, the TCRs, representatives of the Root Zone Maintainer (Verisign), representatives of an independent audit firm retained by ICANN to monitor the process, and often additional external witnesses. Ceremonies are recorded by three audit cameras and webcast online. A typical ceremony lasts approximately four hours, and involves a process of temporarily removing the key signing key from a safe and performing key-signing operations in a secure manner following a formal script. The script is designed to perform each operation in a transparent manner to ensure the key signing key is only used for its proper purpose, and there is no ability for its contents to be disclosed for other purposes. Materials from each ceremony - such as the scripts, video recordings, and system output - are posted online[3]. De-briefings and discussions are conducted post-ceremony, where participants discuss how to improve future ceremonies. This feedback helps inform the evolution of the KSK ceremony to be both efficient and effective, while ensuring maximum trust in how ceremonies are performed. The TCRs were selected[4] from the global community based on a number of criteria[5]. These selection criteria relate to the volunteers ability to travel to ceremonies, conscientiously oversee the process, ensure transparency in its operation, and ultimately contribute to the broader community's trust that the private component of the key signing key has not been compromised. The TCRs are privately funded volunteers who are not reimbursed or compensated by ICANN for their participation nor their expenses. The original TCR proposal was silent on the length of service of individual TCRs. Of the 21 TCRs, seven are credentialed as "crypto officers" (COs) for each of the two facilities, and the remaining seven act as "recovery key shareholders" who only participate in ceremonies in the event the requisite number of COs are unable to participate or there is a need to rebuild the KSK following an unforeseen event. Of the seven COs for each facility, ICANN aims to have four attend each ceremony, with an absolute minimum of three required to successfully perform a ceremony. Each facility hosts two ceremonies per year, approximately once every six months. In practice, a TCR will attend at minimum one ceremony per year, and some will attend two in order to ensure sufficient attendance. Of the initial pool of 21 TCRs, one has resigned and been replaced from the pool of recovery key shareholders. No TCR has been removed owing to the other three criteria for replacement in the TCR selection document, relating to lack of integrity or trustworthiness; assumption of a conflicting role within a root management organization; or being unable to serve in their position. Based on feedback from the current TCRs and our experience from the first 14 ceremonies, we are reviewing what changes, if any, should be made to the current model of TCR participation. Comments Comments are welcome on any aspect of the consultation, and specifically on the following questions: 1. Is the current TCR model effectively performing its function of ensuring trust in the KSK management process? 2. Is the current size of the TCR pool appropriate to ensure sufficient participation in the ceremonies, while not overburdening the availability of specific volunteers? 3. Should there be a minimum level of participation required of a TCR in order to be considered to be successfully discharging their duties? 4. There is no standard provision to refresh the list of TCRs except when they are replaced due to inability to effectively perform their function. Should there be a process to renew the pool of TCRs, such as using term limits or another rotation mechanism? 5. The current model does not compensate TCRs for their services in order to ensure their independence from ICANN. a. Should the model of TCRs paying the costs of their participation be retained? b. Would some form of compensation to offset the expenses incurred by the TCRs detract from their independence in performing the role? c. If you support compensating TCRs for their expenses, are there requirements or limitations on whom the funding organization should be? Please send your comments to comments-tcr-dnssec-key-signing-21jan14(a)icann.org <mailto:comments-tcr-dnssec-key-signing-21jan14(a)icann.org> References [1] http://www.root-dnssec.org [2] https://www.iana.org/dnssec/icann-dps.txt [3] http://data.iana.org/ksk-ceremony/ [4] http://www.root-dnssec.org/tcr/selection-2010/ [5] http://www.root-dnssec.org/wp-content/uploads/2010/04/ICANN-TCR-Proposal -20100408.pdf kim

1 0

Re: [nznog] NZNOG Digest, Vol 134, Issue 2
by Jonathan Spence 04 Feb '14

04 Feb '14

Hi Trent, You may want to try geekzone.co.nz as there are a few good Telecom contacts on there. Thanks, Jonathan ---------------------------------------- From: nznog-request(a)list.waikato.ac.nz Sent: Wednesday, February 5, 2014 12:01 PM To: nznog(a)list.waikato.ac.nz Subject: NZNOG Digest, Vol 134, Issue 2 Send NZNOG mailing list submissions to nznog(a)list.waikato.ac.nz To subscribe or unsubscribe via the World Wide Web, visit http://list.waikato.ac.nz/mailman/listinfo/nznog or, via email, send a message with subject or body 'help' to nznog-request(a)list.waikato.ac.nz You can reach the person managing the list at nznog-owner(a)list.waikato.ac.nz When replying, please edit your Subject line so it is more specific than "Re: Contents of NZNOG digest..." Today's Topics: 1. Telecom NZ Contact (Trent Farrell) ---------------------------------------------------------------------- Message: 1 Date: Tue, 4 Feb 2014 12:19:25 +0000 From: Trent Farrell <tfarrell(a)riotgames.com> To: "nznog(a)list.waikato.ac.nz" <nznog(a)list.waikato.ac.nz> Subject: [nznog] Telecom NZ Contact Message-ID: <80289F43-A47C-4290-ABFC-5728C91EB5BA(a)riotgames.com> Content-Type: text/plain; charset="us-ascii" Hi all, Looking for someone from Telecom NZ to reach out off list, your customers are having issues with parts of our service. Cheers. - Trent ------------------------------ _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog End of NZNOG Digest, Vol 134, Issue 2 *************************************

1 0

Telecom NZ Contact
by Trent Farrell 03 Feb '14

03 Feb '14

Hi all, Looking for someone from Telecom NZ to reach out off list, your customers are having issues with parts of our service. Cheers. - Trent

1 0

Fwd: BCP 38
by Andy Linton 31 Jan '14

31 Jan '14

At NZNOG, Jamie Baddeley mention the spoofer tool at http://spoofer.cmand.org/ I ran it on the net I run at VUW and here are the traces from a couple of runs. I ran it once, realised I was being slack and turned on the 'rfp-check' feature on the edge Juniper and then ran the test again. A nice tool to demonstrate why we should do BCP 38.

1 0

Re: [nznog] Do you stream video?
by Richard Naylor 29 Jan '14

29 Jan '14

At 05:15 p.m. 15/01/2014, Dean Pemberton wrote: >Due to unforeseen circumstances our usual video streaming company of >choice (R2) is unable to stream NZNOG live this year. We're in AKL on another job. The plan is to send a camera operator to Nelson with a small portable encoder. The encoder planned is still in USA and won't be back in time. It died just after New Years day. I think we can free up one from the AKL job on wednesday, but need it back on the Saturday or Sunday after NZNOG, and are not confident couriers can do it. We also have very limited transport and time in AKL as we are parked up on a job. But if anyone can collect the unit from us on the Wednesday and take it to Nelson, then bring it back to AKL on the Saturday (we may have wheels on Saturday) that would solve the issue. I can probably meet someone at the airport and provide a ride home on the Saturday. The encoder is in a small plastic case about 200mmx150x100. Richard 021 897 089

9 10

Lightning talks
by Richard Nelson 29 Jan '14

29 Jan '14

If anyone has a lightning talk and can’t find me at the conference. Just email me off list. Richard.

1 0

One Day down.... Four to go
by Dean Pemberton 26 Jan '14

26 Jan '14

Hello from NZNOG 2014 in sunny Nelson! The venue is awesome and we're off to a great start. The BGP Routing and Network Security workshops are underway and the participants have been giving outstanding feedback. We've got less than 10 more registration slots left for the main conference before we're all sold out. If you're leaving it until the last minute... I'd suggest that you don't . See you all here. Dean

1 0

Re: [nznog] NZNOG Digest, Vol 133, Issue 14
by Jonathan Spence 26 Jan '14

26 Jan '14

They have been doing this for ages (maybe 6 months at least). We had to disable IPv6 on our mail server as we were struggling to get rDNS delegation from Orcon. Got too busy to follow up on it but will do so when I get a minute. Jonathan Spence Chief Executive Officer Fixed: +64 9 9510448 Mobile: +64211055634 ---------------------------------------- From: nznog-request(a)list.waikato.ac.nz Sent: Sunday, January 26, 2014 12:01 PM To: nznog(a)list.waikato.ac.nz Subject: NZNOG Digest, Vol 133, Issue 14 Send NZNOG mailing list submissions to nznog(a)list.waikato.ac.nz To subscribe or unsubscribe via the World Wide Web, visit http://list.waikato.ac.nz/mailman/listinfo/nznog or, via email, send a message with subject or body 'help' to nznog-request(a)list.waikato.ac.nz You can reach the person managing the list at nznog-owner(a)list.waikato.ac.nz When replying, please edit your Subject line so it is more specific than "Re: Contents of NZNOG digest..." Today's Topics: 1. heads up.. gmail now checking ipv6 rdns (Blair Harrison) 2. Re: heads up.. gmail now checking ipv6 rdns (Scott Howard) 3. Re: heads up.. gmail now checking ipv6 rdns (Michael Fincham) 4. Re: heads up.. gmail now checking ipv6 rdns (Phil Regnauld) ---------------------------------------------------------------------- Message: 1 Date: Sat, 25 Jan 2014 13:43:28 +1300 From: Blair Harrison <nznog(a)jedi.school.nz> To: NZNOG <nznog(a)list.waikato.ac.nz> Subject: [nznog] heads up.. gmail now checking ipv6 rdns Message-ID: <CAHn0gTveE=Nh-jp9Lfdw67UDAy=4Y-rgi-4h7t8zr1R_4p73zg(a)mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" Hi Folks, Just got caught out with this on my personal box today. It looks as if Gmail is now checking RDNS on any inbound ipv6 smtp connections and rejecting with 500 error if it doesn't match. example fail - SMTP error from remote mail server after end of data: host gmail-smtp-in.l.google.com [2a00:1450:4008:c01::1a]: 550-5.7.1 [2402:6000:1000:x::x] Our system has detected that this message does 550-5.7.1 not meet IPv6 sending guidelines regarding PTR records and 550-5.7.1 authentication. Please review 550-5.7.1 https://support.google.com/mail/?p=ipv6_authentication_errorfor more 550 5.7.1 information. oq6si4802967bkb.182 - gsmtp So if you have ipv6 enabled on your mail servers and haven't yet set some RDNS for them.. now is the time. Cheers, Blair

1 0

heads up.. gmail now checking ipv6 rdns
by Blair Harrison 24 Jan '14

24 Jan '14

Hi Folks, Just got caught out with this on my personal box today. It looks as if Gmail is now checking RDNS on any inbound ipv6 smtp connections and rejecting with 500 error if it doesn't match. example fail - SMTP error from remote mail server after end of data: host gmail-smtp-in.l.google.com [2a00:1450:4008:c01::1a]: 550-5.7.1 [2402:6000:1000:x::x] Our system has detected that this message does 550-5.7.1 not meet IPv6 sending guidelines regarding PTR records and 550-5.7.1 authentication. Please review 550-5.7.1 https://support.google.com/mail/?p=ipv6_authentication_errorfor more 550 5.7.1 information. oq6si4802967bkb.182 - gsmtp So if you have ipv6 enabled on your mail servers and haven't yet set some RDNS for them.. now is the time. Cheers, Blair

4 3