Citylink's official Debian mirror (ftp.nz.debian.org) is apparently
again broken (not even listening on port 80 from where I'm sitting).
Would anyone be seriously interested in donating rack space, national
transit, or hardware to the cause of another official Debian mirror for
Having reliable and cheap access to free software projects like Debian
is critically important, and having a second official mirror seems like
a no-brainer to me.
I am very happy to donate my time to admin and monitor any equipment
provided for this, and to liase with the Debian project as required.
Perhaps Citylink could give us some insight in to the traffic levels
their existing mirrors see?
Just thought I'd chuck this out there, as my Google-fu seems to be failing.
Does anyone have a known good, Chorus Wholesale, VDSL config for an
Huawei AR160 router?
(The look like a Cisco 800 series, NOT the white,plastic consumer version)
Specifically, I'm having an issue where PPPoE Active Discovery is
working. The ISP core starts sending PPPoE LCP requests, and the Huawei
_seems_ to think it's sending replies, but I'm wiresharking it in our
core, and PPPoE frames are NOT making it back to us...
The Total Team
0800 888 326 / +64 3 3779050
Please apologize if I breach any mailing-list rule with this email.
I recently joined this mailing-list and I would like to introduce myself
as I am actively looking for a job in telcos here.
I have 14 years’ experience in the telecommunication Industry in Europe
- in different types of companies like Renater (French equivalent to
REANNZ), BT, Orange Business Services, Level 3 Communications
- in different types of environments : Integrator, Telecommunications
- in different types of positions : network engineer, contract manager,
project manager, sales engineer
I recently relocated in New Zealand for family reason, and I'm now
actively looking for a Job here. As I found my last position in France
via the FRNOG Community, I though it would make sense to contact the
NZNOG Community here :)
I am mainly looking for presales or project manager positions, but I am
opened to hear about any vacancy that could match my profile.
My CV is available here:
Please reply off-list.
The National Library of New Zealand is looking for an experienced Digital Preservation Web Engineer to lead its web archiving programme.
You will be responsible for the strategic and operational management of the Library's web archiving programme. The primary purpose of the Digital Preservation Web Engineer is to define, implement and support the efficient acquisition, preservation and discovery/delivery of web based digital content subject to the Library's legislated mandate.
This includes harvesting via the Library's selective and whole-of-domain web archiving programmes and the design, deployment and implementation of mechanisms for storing, indexing and providing access (including data mining) to the web collections.
You will be working within a team of 8 digital preservation specialists in the Preservation Research & Consultancy team and be responsible for:
* developing a world class approach to the gathering, preservation, dissemination and interrogation of web based collections.
* drafting a business case for indexing, search and delivery for the Library approx 80Tb of web archives.
* contributing to the development of the strategic direction of the National Library with particular emphasis on the Library's digital (web) collection building, preservation and access roles.
* working closely with national and international peers, related teams within the department and with external vendors.
Working at the Department of Internal Affairs, you'll have the opportunity to make a real difference in the lives of New Zealanders.
The National Library of New Zealand sits within the Information and Knowledge Services branch, the Department's epicentre of information management. Our branch is all about collecting, storing and preserving important things that are precious to New Zealand.
You will have substantial practical experience in an IT environment with specific emphasis on web framework technologies and protocols, and preferably also demonstrated experience in web archiving. You will be a self-driven specialist, ideally with a tertiary qualification in information technology, computer science or information science or its equivalent.
This role also requires you to be legally entitled to work in New Zealand.
If you want to join a team of smart, committed people who do spectacular work for New Zealand - then this might be the right job for you.
Jay Gattuso | Digital Preservation Analyst | Preservation, Research and Consultancy
National Library of New Zealand | Te Puna Mātauranga o Aotearoa
PO Box 1467 Wellington 6140 New Zealand | +64 (0)4 474 3064
Five years ago PCH conducted the first, and to date only, comprehensive survey characterizing Internet peering agreements.
The document that resulted can be found here: https://www.pch.net/resources/Papers/peering-survey/PCH-Peering-Survey-2011… <https://www.pch.net/resources/Papers/peering-survey/PCH-Peering-Survey-2011…>
That document was one of the principal inputs to an important document that the OECD publishes every five years, one that recommends communications regulatory policy to OECD member nations: http://www.oecd.org/officialdocuments/publicdisplaydocumentpdf/?cote=DSTI/I… <http://www.oecd.org/officialdocuments/publicdisplaydocumentpdf/?cote=DSTI/I…>
The survey had several useful findings which hadn’t previously been established as fact—most notably the portion of peering relationships that are “handshake” agreements, without written contract. These findings have improved the regulatory environments in which many of us operate our networks.
At the time of the 2011 survey, we committed to repeating the survey every five years, so as to provide an ongoing indication of the direction peering trends take. It’s now five years later, so we’re repeating the survey.
The survey is global in scope, and our goal is to reflect the diversity of peering agreements in the world; we’re interested in large ISPs and small ISPs, ISPs in Afghanistan and in Zimbabwe, bilateral agreements and multilateral, private and public. Our intent is to be as comprehensive as possible. In 2011, the responses we received represented 86% of all of the world’s ISPs and 96 countries. We would like to be at least as inclusive this time.
In 2011, we promised to collect the smallest set of data necessary to answer the questions, to perform the analysis immediately, and not to retain the data after the analysis was accomplished. In that way, we ensured that the privacy of respondents was fully protected. We did as we said, no data was leaked, and the whole community benefited from the trust that was extended to us. We ask for your trust again now as we make the same commitment to protect the privacy of all respondents, using the same process as last time. We are asking for no more data than is absolutely necessary. We will perform the analysis immediately upon receiving all of the data. We will delete the data once the analysis has been performed.
We would like to know the following five pieces of information relative to each Autonomous System you peer with:
• Your ASN
• Your peer’s ASN (peers only, not upstream transit providers or downstream customers)
• Whether a written and signed peering agreement exists (the alternative being a less formal arrangement, such as a "handshake agreement")
• Whether the terms are roughly symmetric (the alternative being that they describe an agreement with different terms for each of the two parties, such as one compensating the other, or one receiving more or fewer than full customer routes)
• Whether a jurisdiction of governing law is defined
• Whether IPv6 routes are being exchanged (this year, we’ll still assume that IPv4 are)
The easiest way for us to receive the information is as a tab-text or CSV file or an Excel spreadsheet, consisting of rows with the following columns:
Your ASN: Integer
Peer ASN: Integer
Written agreement: Boolean
Governing Law: ISO 3166 two-digit country-code, or empty
IPv6 Routes: Boolean
42 <tab> 715 <tab> false <tab> true <tab> us <tab> true <cr>
42 <tab> 3856 <tab> true <tab> true <tab> us <tab> true <cr>
We are asking for the ASNs only so we can avoid double-counting a single pair of peers when we hear from both of them, and so that when we hear about a relationship in responses from both peers we can see how closely the two responses match, an important check on the quality of the survey. As soon as we've collated the data, we'll strip the ASNs to protect privacy, and only the final aggregate statistics will be published. We will never disclose any ASN or any information about any ASN. We already have more than 8,000 ASN-pair relationships documented, and we hope to receive as many more as possible. We'd like to finish collecting data by the end of September, about two weeks from now.
If you’re peering with an MLPA route-server, you’re welcome to include just the route-server’s ASN, if that’s easiest, rather than trying to include each of the peer ASNs on the other side of the route-server. Either way is fine.
If all of your sessions have the same characteristics, you can just tell us what those characteristics are once, your own ASN once, and give us a simple list of your peer ASNs.
If your number of peers is small enough to be pasted or typed into an email, rather than attached as a file, and that’s simpler, just go ahead and do that.
If you have written peering agreements that are covered by non-disclosure agreements, or if your organizational policy precludes disclosing your peers, but you’d still like to participate in the survey, please let us know, and we’ll work with whatever information you’re able to give us and try to ensure that your practices are statistically represented in our results.
If you're able to help us, please email me the data in whatever form you can. If you need a non-disclosure, we're happy to sign one.
Finally, if there are any other questions you’d like to see answered in the future, please let us know so that we can consider addressing them in the 2021 survey. The question about IPv6 routing in this year’s survey is there because quite a few of the 2011 respondents asked us to include it this time.
Please respond by replying to this email, before the end of September.
Thank you for considering participating. We very much appreciate it, and we look forward to returning the results to the community.
Packet Clearing House
Currently ( all? ) the NZIX route servers insert the exchange ASN into
routes that are advertised to the route servers.
The exchanges that we peer with overseas such as Any2 in LA, Equinix
Sydney and NSW-IX plus the new AKL-IX exchange do not insert the
exchange ASN into advertisements, so all else being equal the paths from
those exchanges are shorter than routes from APE and WIX by one AS hop.
There are other NZ networks like us that peer at APE and/or WIX and also
peer at overseas exchanges and to have optimal traffic flows with them,
we put in one off hacks per network. The least ugly ways of doing this
for us work fine but create per peer config that must be maintained.
Ideally we can put bilateral peering up at APE and WIX so that the extra
AS hop goes away but sometimes bilateral peering is impractical due to
the other networks peering policy.
I can't think of a reason why putting the exchange ASN in the path helps
anyone. Is this just a hangover from the old days? Or is there some
legitimate reason that it should be like this?
Lincoln Reid Head of Networks
ACSData - AS18119 lincoln(a)acsdata.co.nz
Phone: +64 4 939 2200 Fax: +64 4 939 2201
ICANN has updated the IANA IPv4 Recovered Address Space registry according to the Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA. The policy states that in each IPv4 allocation period, each RIR will receive a single IPv4 allocation unit from ICANN. An IPv4 allocation period is defined as a 6-month period following 1 March or 1 September in each year.
The address space selection software can be downloaded from: https://github.com/icann/
The list of allocations can be found at: https://www.iana.org/assignments/ipv4-recovered-address-space/
IANA Senior Specialist