- NZNOG - lists.nznog.org

RIPE NCC Position On The ITU IPv6 Group
by Skeeve Stevens 26 Feb '10

26 Feb '10

This is an FYI for those interested. Btw, RIPE NCC is the European version of APNIC for those that don't know. The ITU are looking at bypassing the RIR's (Ripe, APNIC, ARIN, AFRINIC, LACNIC) and becoming their own numbering authority. Clearly this is not the desired option as the structure already exists for exactly what they want to do, but rather than regionally, they want to do it per country.... for who knows what reason. -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? -----Original Message----- From: admin-bounces(a)tuenti.com [mailto:admin-bounces(a)tuenti.com] On Behalf Of Axel Pawlik Sent: Friday, 26 February 2010 3:20 AM To: ncc-announce(a)ripe.net Subject: [Admin] [members-discuss] [ncc-announce] RIPE NCC Position On The ITU IPv6 Group Dear Colleagues, As you may be aware, the International Telecommunication Union's (ITU) Telecommunication Standardization Bureau (TSB) has convened an ITU IPv6 Group, the first meeting of which will be held on 15-16 March 2010 in Geneva, Switzerland. Information on this group is available at: http://www.itu.int/ITU-T/othergroups/ipv6/ Among the group's Terms of Reference are the following: * To draft a global policy proposal for the reservation of a large IPv6 block, taking into consideration the future needs of developing countries (as outlined in paragraph 23 of ITU document C09/29). * To further study possible methodologies and related implementation mechanisms to ensure 'equitable access' to IPv6 resource by countries. * To further study the possibility for ITU to become another Internet Registry, and propose policies and procedures for ITU to manage a reserved IPv6 block. * To further study the feasibility and advisability of implementing the CIR [Country Internet Registry] model for those countries who would request national allocations. The ITU IPv6 Group is open to ITU Member States and Sector Members of ITU-T and ITU-D. RIRs that are not members have also been extended an invitation to participate. IPv6 address policy is clearly of critical importance to the RIPE NCC membership, and the unsympathetic implementation of any of the Terms of Reference stated above would have serious impact on the global IP address distribution environment. Members of RIPE NCC staff will be participating in this meeting of the ITU IPv6 Group to represent the interests of our members and community. The position of the RIPE NCC is based on support for smooth and reliable working of the Internet globally, and for the bottom-up, open policy development process that allows for all stakeholders, including business, government and the technical community, to participate. Some of the issues addressed in the Terms of Reference listed above are a cause for concern because they could directly affect the RIPE NCC operations as a Regional Internet Registry (RIR). Therefore, the RIPE NCC position on the Terms of Reference is as follows: * The needs of developing economies in IP address policy are important. Network operators in these economies have fair and equal access to IPv6 resources from the Regional Internet Registries (RIRs), and to the Policy Development Processes in their RIR and globally. Each of the RIRs has been allocated an equal block of IPv6 to distribute to networks in their region. (eg. AfriNIC has been allocated the same sized block of IPv6 as the RIPE NCC). * IPv6 allocations made by RIRs to date amount to the equivalent of 500 times the size of the entire IPv4 address pool, allocated to networks in over 150 economies. * If a significant sector in the Internet community feels that the "reservation of a large IPv6 block" for "the future needs of developing countries" is warranted, the open, bottom-up Policy Development Processes (PDPs) of the RIRs provide an appropriate forum in which to argue that case and develop such a policy. * The RIRs, as the recognised stewards of Internet Number Resources, are working, individually, jointly, and with invited experts, to engage the ITU membership. We have closely followed discussions in the ITU to date. The RIPE NCC does not believe that there are any problems that would be solved by the shift to a country-based allocation system or the installation of the ITU as an Internet Registry. The purpose of this email is to ensure that all RIPE NCC members are informed of the RIPE NCC's participation in this ITU IPv6 Group, and our position. If you have any comments or questions regarding this information, please send an email to <ncc(a)ripe.net>. Kind regards, Axel Pawlik Managing Director RIPE NCC ---- If you don't want to receive mails from the RIPE NCC Members Discuss list, please log in to your LIR Portal account at: http://lirportal.ripe.net/ First click on General and then click on Edit. At the bottom of the Page you can add or remove addresses.

1 0

Re: [nznog] [AusNOG] MEDIA RELEASE FROM EINTELLEGO - eintellego encourages APNIC members to vote for local representative
by Shain Singh 25 Feb '10

25 Feb '10

On Thu, Feb 25, 2010 at 8:00 AM, Mark Smith < nanog(a)85d5b20a518b8f6864949bd940457dc124746ddc.nosense.org> wrote: > On Wed, 24 Feb 2010 17:50:31 +1100 > Skeeve Stevens <Skeeve(a)eintellego.net> wrote: > > > Hey all, > > > > This is a media release which is specifically of interest to the ANZ*NOG > lists. > > > > Did you really need to send a Media Release to this list announce your > opinion here? Just stating it would have been fine. I've > understood lists like this one are to be corporate PR/marketing > free zones, and media releases are definitely corporate PR/marketing. > > > I encourage all APNIC members to not hesitate to support Jonny Martin in > his run for the APNIC EC. > > > > If you aren't interested in this post, please just devnull it. > > > > Maybe next time you find yourself writing that, think about whether > you really should be sending what you've written. You're basically > saying to everybody to use the delete key/button if necessary - and if > people on this list know how the Internet works they probably already > know how to delete emails, and don't need to be told what do with > ones they aren't interested in ... > > +1 Manila is also spelt incorrectly in the press release.. Lucky it's for an ANZ rep and not a Filipino one. </pedantic> -- Shaineel Singh e: shain.singh(a)gmail.com p: +61 422 921 951 -- "Too many have dispensed with generosity to practice charity" - Albert Camus

1 0

MEDIA RELEASE FROM EINTELLEGO - eintellego encourages APNIC members to vote for local representative
by Skeeve Stevens 25 Feb '10

25 Feb '10

Hey all, This is a media release which is specifically of interest to the ANZ*NOG lists. I encourage all APNIC members to not hesitate to support Jonny Martin in his run for the APNIC EC. If you aren't interested in this post, please just devnull it. ...Skeeve MEDIA RELEASE For Immediate Release eintellego encourages APNIC members to vote for local representative SYDNEY, Feb 24, 2010 - eintellego is encouraging all APNIC members in Australia and New Zealand to vote in the upcoming elections for the Executive Committee being held in Kuala Lumpur, Malaysia at the APNIC 29 member meeting early in March 2010. At each APNIC meeting there are hundreds of Australian and New Zealand members of APNIC who fail to exercise their voting power. At APNIC 28 held in Manilla, the Australia and New Zealand internet communities rallied and were successful in getting James Spenceley, CEO of Vocus Communications elected to the EC. For some years now the Australian and New Zealand communities have been under-represented and as we have the opportunity to get additional representation, eintellego is encouraging all members to either vote, or assign a proxy vote to someone who is attending the conference. eintellego is fully supporting Jonny Martin, a NZ citizen and Internet Analyst with Packet Clearing House, as a nominee for the APNIC EC. Jonny Martin started work in the Internet Industry with Telecom New Zealand in 1998 working on access technologies. After Telecom Jonny held senior roles with ISPs in NZ such as CityLink and FX Networks working primarily on fibre optic deployments. In his spare time and holidays, Jonny assists with training at events such as Apricot, SANOG and NZNOG and has been actively involved with the NZ Internet Community for many years. Since 2006, Jonny has been a Councillor of InternetNZ, the body which manages the .nz namespace and .nz registry. eintellego has had the pleasure of working with Jonny and hopes that all APNIC members in the region will rally to help get him elected. Assigning proxy votes or voting online closes on the 3rd of March 2010 at 9am (KL time) with the election being held on the 5th of March. If any members are considering casting their vote and need assistance, they can contact APNIC directly on +617 3858 3100 or helpdesk(a)apnic.net Skeeve Stevens, CEO of eintellego will be onsite at the conference and election, and any members who want to assign a proxy are able to complete a pre-filled proxy form available at www.eintellego.net/apnicec29proxy.pdf<http://www.eintellego.net/apnicec29proxy.pdf>. Please make sure that this form is completed by the official 'Corporate Contact' for your APNIC membership. About eintellego eintellego is a specialist network and systems integrator to the ISP industry and wider corporate world, where cutting edge networking is required. eintellego operates all across Australia, New Zealand, Asia and the Pacific region. http://www.eintellego.net/ Editorial contacts: Skeeve Stevens, CEO +61414 753 383 skeeve(a)eintellego.net eintellego Pty Ltd - www.eintellego.net -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

2 1

Re: [nznog] Stateful firewalls
by Joel Wiramu Pauling 24 Feb '10

24 Feb '10

On 25 February 2010 22:30, Joel Wiramu Pauling <aenertia(a)aenertia.net> wrote: >> The place do to this is at the edges via routing policies and stateless ACLs, not in firewalls. >> >> And, no, the largest enterprise firewalls make all these marketing claims about the numbers they can handle, but the reality is quite different - having spent the better part of a decade working for the largest vendor of firewalls in the world, I can assure you of that. >> There is a trend in router manufacturers to offer flow classification add-in modules for doing service differentiation. While not state-full firewalls as such, they do deep packet inspection and flow tagging in much the same way. These are designed to scale with the routing capacity's. And they definitely exist. Also there is currently a bunch of cool pf kernalspace extensions being added to openbsd to allow similar offload to GPU's which would bring this sort of ability to consumer level hardware. This is a little off topic from the original context however. -JoelW

1 0

Be Heard! APNIC Community Consultation Next Week
by Elly Tawhai 24 Feb '10

24 Feb '10

_______________________________________________________________________ Be Heard! APNIC Community Consultation Next Week _______________________________________________________________________ Hi NZNOG Community, Internet address management may be on the brink of change. The ITU (International Telecommunications Union) is studying the creation of an alternative International Internet Registry model to operate in parallel to the existing RIR model. In collaboration with the NRO, APNIC is hosting a special session at APNIC 29 / APRICOT 2010 to give the global Internet community an opportunity to discuss the issues and ramifications of the alternative model proposed by the ITU. APNIC invites all Members of the global Internet Community to participate at: IPv6 Address Management and ITU - Is an "additional parallel structure" required? Where: APNIC 29, Kuala Lumpur, Malaysia When: 14:00 - 15:30 (UTC +8), Wednesday, 3 March 2010 APNIC is an ITU-D sector Member and will attend the ITU IPv6 Working Group meeting in March that has been commissioned to study this issue in depth. APNIC will be reporting feedback from our Consultation to ensure community feedback is heard. Topics of discussion -------------------- 1. Where is the demand for this alternative system coming from? Would competition between IP address management systems bring any benefits to current and future Internet stakeholders? 2. Is it realistic to expect the policies of an alternative model as proposed by the ITU, to be consistent with RIR policies? Would the possibility of nationalized addressing systems lead to divergent policy systems? What would be the risks to the Internet of divergent policy environments? 3. If the ITU were to become an Internet registry, how would the ITU model affect the existing RIR model of open, bottom-up, and consensus-driven policy-making? More detailed information is available on: http://meetings.apnic.net/29/program/consultation How can you participate? ------------------------ Onsite ------ APNIC 29, Conference Hall 2, Kuala Lumpur Convention Center, Kuala Lumpur, Malaysia. Remotely -------- Remote participants can watch via webcasting and can ask questions and make comments for the record via Jabber Chat. These tools can be adjusted to accommodate low bandwidth. Submissions ----------- APNIC is accepting written submissions. Please post your submission, identifying your name and affiliation and your comments on any or all of three discussion topics as well as general comments to: ipv6(a)apnic.net More Information ---------------- For more information on remote participation, visit: http://meetings.apnic.net/29/remote For more information on the APNIC 29 program, visit: http://meetings.apnic.net/29 For further assistance, contact: helpdesk(a)apnic.net _______________________________________________________________________ APNIC Secretariat Asia Pacific Network Information Centre (APNIC) Tel: +61-7-3858-3100 PO Box 2131 Milton, QLD 4064 Australia Fax: +61-7-3858-3199 Level 1, 33 Park Road, Milton, QLD http://www.apnic.net _______________________________________________________________________

1 0

Re: [nznog] [Ticket #1751456] RE: Stateful firewalls
by Mark Foster 24 Feb '10

24 Feb '10

Erm, seriously? iSERVE support is going to generate a trouble ticket for EVERY new NZNOG thread? This could be entertaining... On Thu, 25 Feb 2010, iSERVE Support wrote: > > Hi, > > This is a quick, automatically generated email to let you know that we have got your email, and our team will get on to it just as soon as they can. > > If you need to get in touch with us in the mean time about the same issue please quote the ticket number or simply reply to this email. > > Thanks, > iSERVE Support > > >

6 5

FW: [Ticket #1750663] MEDIA RELEASE FROM EINTELLEGO - eintellego encourages APNIC
by Skeeve Stevens 23 Feb '10

23 Feb '10

Odd. ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? -----Original Message----- From: iSERVE Support [mailto:support(a)iserve.co.nz] Sent: Wednesday, 24 February 2010 5:54 PM To: Skeeve Stevens Subject: RE: [Ticket #1750663] [nznog] MEDIA RELEASE FROM EINTELLEGO - eintellego encourages APNIC Hi, This is a quick, automatically generated email to let you know that we have got your email, and our team will get on to it just as soon as they can. If you need to get in touch with us in the mean time about the same issue please quote the ticket number or simply reply to this email. Thanks, iSERVE Support

1 0

NZRR Route Registry Update
by NZRR Database Notifications 23 Feb '10

23 Feb '10

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Communications - NO VERIFICATION NEEDED - AS4826 members: 118.92.0.0/15^15-29, 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 121.90.0.0/16^16-29, 131.203.0.0/16^16-29, 147.209.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 113.203.0.0/17^17-29, 180.181.0.0/17^17-29, 203.60.128.0/17^17-29, 203.109.128.0/17^17-29, 210.48.0.0/17^17-29, 112.141.0.0/18^18-29, 112.141.128.0/18^18-29, 114.129.128.0/18^18-29, 125.253.0.0/18^18-29, 203.60.64.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 203.173.128.0/18^18-29, 203.208.64.0/18^18-29, 210.185.0.0/18^18-29, 58.96.128.0/19^19-29, 112.141.64.0/19^19-29, 112.141.192.0/19^19-29, 113.192.0.0/19^19-29, 115.69.160.0/19^19-29, 118.127.0.0/19^19-29, 118.127.64.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 119.252.0.0/19^19-29, 121.79.192.0/19^19-29, 122.99.64.0/19^19-29, 123.50.128.0/19^19-29, 123.100.128.0/19^19-29, 124.6.192.0/19^19-29, 125.254.64.0/19^19-29, 175.107.128.0/19^19-29, 180.189.192.0/19^19-29, 180.222.0.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.171.160.0/19^19-29, 202.181.0.0/19^19-29, 203.60.32.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.129.32.0/19^19-29, 203.152.96.0/19^19-29, 203.173.192.0/19^19-29, 203.201.128.0/19^19-29, 210.54.160.0/19^19-29, 210.56.224.0/19^19-29, 221.121.128.0/19^19-29, 58.84.224.0/20^20-29, 111.67.0.0/20^20-29, 111.118.160.0/20^20-29, 112.109.64.0/20^20-29, 112.141.96.0/20^20-29, 112.141.224.0/20^20-29, 113.20.0.0/20^20-29, 114.31.192.0/20^20-29, 114.111.128.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 117.55.224.0/20^20-29, 119.10.128.0/20^20-29, 119.47.112.0/20^20-29, 119.160.224.0/20^20-29, 119.161.64.0/20^20-29, 121.127.208.0/20^20-29, 121.200.32.0/20^20-29, 122.102.96.0/20^20-29, 122.200.160.0/20^20-29, 122.201.80.0/20^20-29, 124.155.224.0/20^20-29, 125.214.64.0/20^20-29, 125.253.96.0/20^20-29, 125.254.96.0/20^20-29, 175.107.160.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.55.144.0/20^20-29, 202.56.32.0/20^20-29, 202.68.160.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.79.160.0/20^20-29, 202.86.96.0/20^20-29, 202.126.192.0/20^20-29, 202.129.144.0/20^20-29, 202.144.160.0/20^20-29, 202.170.160.0/20^20-29, 202.174.160.0/20^20-29, 203.60.16.0/20^20-29, 203.83.192.0/20^20-29, 203.88.112.0/20^20-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 203.161.128.0/20^20-29, 203.212.144.0/20^20-29, 210.56.32.0/20^20-29, 110.44.24.0/21^21-29, 112.140.176.0/21^21-29, 112.141.112.0/21^21-29, 112.141.240.0/21^21-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 114.110.32.0/21^21-29, 114.141.96.0/21^21-29, 115.124.32.0/21^21-29, 115.126.128.0/21^21-29, 115.178.16.0/21^21-29, 115.178.104.0/21^21-29, 116.212.64.0/21^21-29, 117.18.80.0/21^21-29, 117.104.176.0/21^21-29, 119.63.200.0/21^21-29, 119.63.216.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 121.101.136.0/21^21-29, 121.127.200.0/21^21-29, 121.200.208.0/21^21-29, 122.49.200.0/21^21-29, 122.99.112.0/21^21-29, 122.201.72.0/21^21-29, 124.248.136.0/21^21-29, 125.213.160.0/21^21-29, 175.107.176.0/21^21-29, 180.92.192.0/21^21-29, 180.92.216.0/21^21-29, 180.94.232.0/21^21-29, 180.214.168.0/21^21-29, 202.4.232.0/21^21-29, 202.12.248.0/21^21-29, 202.36.16.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.136.0/21^21-29, 202.49.64.0/21^21-29, 202.56.48.0/21^21-29, 202.67.120.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.86.208.0/21^21-29, 202.90.48.0/21^21-29, 202.90.240.0/21^21-29, 202.126.80.0/21^21-29, 202.137.240.0/21^21-29, 202.160.112.0/21^21-29, 202.162.176.0/21^21-29, 202.169.16.0/21^21-29, 202.169.200.0/21^21-29, 202.169.208.0/21^21-29, 202.191.8.0/21^21-29, 203.1.240.0/21^21-29, 203.60.8.0/21^21-29, 203.149.80.0/21^21-29, 203.170.8.0/21^21-29, 203.173.240.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.4.208.0/21^21-29, 210.9.136.0/21^21-29, 210.50.56.0/21^21-29, 58.179.60.0/22^22-29, 58.179.124.0/22^22-29, 59.86.172.0/22^22-29, 59.86.176.0/22^22-29, 59.86.184.0/22^22-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 110.76.132.0/22^22-29, 110.76.136.0/22^22-29, 110.93.8.0/22^22-29, 110.173.224.0/22^22-29, 110.232.144.0/22^22-29, 111.118.208.0/22^22-29, 111.125.160.0/22^22-29, 111.235.140.0/22^22-29, 113.29.240.0/22^22-29, 113.52.128.0/22^22-29, 113.130.120.0/22^22-29, 114.111.144.0/22^22-29, 114.141.104.0/22^22-29, 115.69.28.0/22^22-29, 116.90.72.0/22^22-29, 116.240.184.0/22^22-29, 119.15.96.0/22^22-29, 119.63.212.0/22^22-29, 119.161.84.0/22^22-29, 119.161.92.0/22^22-29, 119.252.176.0/22^22-29, 121.127.192.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 122.201.68.0/22^22-29, 122.201.100.0/22^22-29, 124.108.96.0/22^22-29, 175.107.184.0/22^22-29, 180.148.24.0/22^22-29, 180.189.152.0/22^22-29, 180.222.192.0/22^22-29, 198.48.0.0/22^22-29, 202.4.228.0/22^22-29, 202.6.124.0/22^22-29, 202.36.24.0/22^22-29, 202.36.36.0/22^22-29, 202.37.32.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.129.244.0/22^22-29, 202.130.32.0/22^22-29, 202.153.64.0/22^22-29, 202.160.48.0/22^22-29, 202.169.180.0/22^22-29, 202.169.196.0/22^22-29, 202.169.216.0/22^22-29, 202.177.220.0/22^22-29, 203.0.124.0/22^22-29, 203.4.200.0/22^22-29, 203.11.104.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.30.44.0/22^22-29, 203.55.232.0/22^22-29, 203.62.184.0/22^22-29, 203.80.60.0/22^22-29, 203.82.100.0/22^22-29, 203.83.208.0/22^22-29, 203.92.28.0/22^22-29, 203.99.132.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.188.216.0/22^22-29, 203.190.232.0/22^22-29, 203.202.132.0/22^22-29, 203.211.56.0/22^22-29, 203.212.128.0/22^22-29, 203.217.152.0/22^22-29, 210.11.144.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 58.179.136.0/23^23-29, 59.86.170.0/23^23-29, 59.86.188.0/23^23-29, 63.218.156.0/23^23-29, 110.76.128.0/23^23-29, 111.125.168.0/23^23-29, 114.111.148.0/23^23-29, 114.134.176.0/23^23-29, 114.141.108.0/23^23-29, 114.142.160.0/23^23-29, 114.142.168.0/23^23-29, 115.178.6.0/23^23-29, 116.90.128.0/23^23-29, 116.90.132.0/23^23-29, 116.90.140.0/23^23-29, 118.107.60.0/23^23-29, 119.63.208.0/23^23-29, 119.82.150.0/23^23-29, 119.161.80.0/23^23-29, 121.127.196.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.201.64.0/23^23-29, 122.252.12.0/23^23-29, 141.243.8.0/23^23-29, 141.243.32.0/23^23-29, 180.235.104.0/23^23-29, 199.212.92.0/23^23-29, 202.4.162.0/23^23-29, 202.4.226.0/23^23-29, 202.6.56.0/23^23-29, 202.6.116.0/23^23-29, 202.7.2.0/23^23-29, 202.8.44.0/23^23-29, 202.12.70.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.62.0/23^23-29, 202.14.248.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.218.0/23^23-29, 202.37.240.0/23^23-29, 202.46.176.0/23^23-29, 202.46.190.0/23^23-29, 202.49.62.0/23^23-29, 202.49.148.0/23^23-29, 202.49.164.0/23^23-29, 202.56.62.0/23^23-29, 202.61.2.0/23^23-29, 202.65.160.0/23^23-29, 202.67.118.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.150.60.0/23^23-29, 202.158.254.0/23^23-29, 202.162.64.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.169.176.0/23^23-29, 202.169.220.0/23^23-29, 202.174.6.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.10.76.0/23^23-29, 203.16.60.0/23^23-29, 203.17.112.0/23^23-29, 203.18.102.0/23^23-29, 203.21.76.0/23^23-29, 203.22.70.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.30.98.0/23^23-29, 203.33.60.0/23^23-29, 203.33.70.0/23^23-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20100210 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Communications - NO VERIFICATION NEEDED - AS4826 members: 118.92.0.0/15^15-29, 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 121.90.0.0/16^16-29, 131.203.0.0/16^16-29, 147.209.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 113.203.0.0/17^17-29, 180.181.0.0/17^17-29, 203.60.128.0/17^17-29, 203.109.128.0/17^17-29, 210.48.0.0/17^17-29, 112.141.0.0/18^18-29, 112.141.128.0/18^18-29, 114.129.128.0/18^18-29, 125.253.0.0/18^18-29, 203.60.64.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 203.173.128.0/18^18-29, 203.208.64.0/18^18-29, 210.185.0.0/18^18-29, 58.96.128.0/19^19-29, 112.141.64.0/19^19-29, 112.141.192.0/19^19-29, 113.192.0.0/19^19-29, 115.69.160.0/19^19-29, 118.127.0.0/19^19-29, 118.127.64.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 119.252.0.0/19^19-29, 121.79.192.0/19^19-29, 122.99.64.0/19^19-29, 123.50.128.0/19^19-29, 123.100.128.0/19^19-29, 124.6.192.0/19^19-29, 125.254.64.0/19^19-29, 175.107.128.0/19^19-29, 180.189.192.0/19^19-29, 180.222.0.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.171.160.0/19^19-29, 202.181.0.0/19^19-29, 203.60.32.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.129.32.0/19^19-29, 203.152.96.0/19^19-29, 203.173.192.0/19^19-29, 203.201.128.0/19^19-29, 210.54.160.0/19^19-29, 210.56.224.0/19^19-29, 221.121.128.0/19^19-29, 58.84.224.0/20^20-29, 111.67.0.0/20^20-29, 111.118.160.0/20^20-29, 112.109.64.0/20^20-29, 112.141.96.0/20^20-29, 112.141.224.0/20^20-29, 113.20.0.0/20^20-29, 114.31.192.0/20^20-29, 114.111.128.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 117.55.224.0/20^20-29, 119.10.128.0/20^20-29, 119.47.112.0/20^20-29, 119.63.208.0/20^20-29, 119.160.224.0/20^20-29, 119.161.64.0/20^20-29, 121.127.208.0/20^20-29, 121.200.32.0/20^20-29, 122.102.96.0/20^20-29, 122.200.160.0/20^20-29, 124.155.224.0/20^20-29, 125.214.64.0/20^20-29, 125.253.96.0/20^20-29, 125.254.96.0/20^20-29, 175.107.160.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.55.144.0/20^20-29, 202.56.32.0/20^20-29, 202.68.160.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.79.160.0/20^20-29, 202.86.96.0/20^20-29, 202.126.192.0/20^20-29, 202.129.144.0/20^20-29, 202.144.160.0/20^20-29, 202.170.160.0/20^20-29, 202.174.160.0/20^20-29, 203.60.16.0/20^20-29, 203.83.192.0/20^20-29, 203.88.112.0/20^20-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 203.161.128.0/20^20-29, 203.212.144.0/20^20-29, 210.56.32.0/20^20-29, 110.44.24.0/21^21-29, 112.140.176.0/21^21-29, 112.141.112.0/21^21-29, 112.141.240.0/21^21-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 114.110.32.0/21^21-29, 114.141.96.0/21^21-29, 115.124.32.0/21^21-29, 115.126.128.0/21^21-29, 115.178.16.0/21^21-29, 115.178.104.0/21^21-29, 116.212.64.0/21^21-29, 116.240.160.0/21^21-29, 117.18.80.0/21^21-29, 117.104.176.0/21^21-29, 119.63.200.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 121.101.136.0/21^21-29, 121.127.200.0/21^21-29, 121.200.208.0/21^21-29, 122.49.200.0/21^21-29, 122.99.112.0/21^21-29, 122.201.72.0/21^21-29, 124.248.136.0/21^21-29, 125.213.160.0/21^21-29, 175.107.176.0/21^21-29, 175.176.200.0/21^21-29, 180.92.192.0/21^21-29, 180.92.216.0/21^21-29, 180.94.232.0/21^21-29, 180.214.168.0/21^21-29, 182.23.192.0/21^21-29, 202.4.232.0/21^21-29, 202.12.248.0/21^21-29, 202.36.16.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.136.0/21^21-29, 202.56.48.0/21^21-29, 202.67.120.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.86.208.0/21^21-29, 202.90.48.0/21^21-29, 202.90.240.0/21^21-29, 202.126.80.0/21^21-29, 202.137.240.0/21^21-29, 202.160.112.0/21^21-29, 202.162.176.0/21^21-29, 202.169.16.0/21^21-29, 202.169.200.0/21^21-29, 202.169.208.0/21^21-29, 202.191.8.0/21^21-29, 203.1.240.0/21^21-29, 203.60.8.0/21^21-29, 203.149.80.0/21^21-29, 203.170.8.0/21^21-29, 203.173.240.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.4.208.0/21^21-29, 210.9.136.0/21^21-29, 210.50.56.0/21^21-29, 58.179.60.0/22^22-29, 58.179.124.0/22^22-29, 59.86.172.0/22^22-29, 59.86.176.0/22^22-29, 59.86.184.0/22^22-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 110.76.132.0/22^22-29, 110.76.136.0/22^22-29, 110.93.8.0/22^22-29, 110.173.224.0/22^22-29, 110.232.144.0/22^22-29, 111.118.208.0/22^22-29, 111.125.160.0/22^22-29, 111.235.140.0/22^22-29, 113.29.240.0/22^22-29, 113.52.128.0/22^22-29, 113.130.120.0/22^22-29, 114.111.144.0/22^22-29, 114.141.104.0/22^22-29, 114.142.160.0/22^22-29, 115.69.28.0/22^22-29, 116.90.72.0/22^22-29, 116.240.184.0/22^22-29, 119.15.96.0/22^22-29, 119.161.84.0/22^22-29, 119.161.92.0/22^22-29, 119.252.176.0/22^22-29, 121.127.192.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 122.201.68.0/22^22-29, 122.201.100.0/22^22-29, 124.108.96.0/22^22-29, 125.254.112.0/22^22-29, 175.107.184.0/22^22-29, 175.111.100.0/22^22-29, 180.148.24.0/22^22-29, 180.148.176.0/22^22-29, 180.189.152.0/22^22-29, 180.222.192.0/22^22-29, 198.48.0.0/22^22-29, 202.4.228.0/22^22-29, 202.6.124.0/22^22-29, 202.36.24.0/22^22-29, 202.36.36.0/22^22-29, 202.37.32.0/22^22-29, 202.37.48.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.129.244.0/22^22-29, 202.130.32.0/22^22-29, 202.153.64.0/22^22-29, 202.160.48.0/22^22-29, 202.169.180.0/22^22-29, 202.169.196.0/22^22-29, 202.169.216.0/22^22-29, 202.177.220.0/22^22-29, 203.0.124.0/22^22-29, 203.4.200.0/22^22-29, 203.11.104.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.30.44.0/22^22-29, 203.55.232.0/22^22-29, 203.62.184.0/22^22-29, 203.80.60.0/22^22-29, 203.82.100.0/22^22-29, 203.83.208.0/22^22-29, 203.92.28.0/22^22-29, 203.99.132.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.156.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.188.216.0/22^22-29, 203.190.232.0/22^22-29, 203.202.132.0/22^22-29, 203.211.56.0/22^22-29, 203.212.128.0/22^22-29, 203.217.152.0/22^22-29, 210.11.144.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 58.179.136.0/23^23-29, 59.86.170.0/23^23-29, 59.86.188.0/23^23-29, 63.218.156.0/23^23-29, 110.76.128.0/23^23-29, 111.125.168.0/23^23-29, 114.111.148.0/23^23-29, 114.134.176.0/23^23-29, 114.141.108.0/23^23-29, 114.142.168.0/23^23-29, 115.178.6.0/23^23-29, 116.90.128.0/23^23-29, 116.90.132.0/23^23-29, 116.90.140.0/23^23-29, 118.107.60.0/23^23-29, 119.161.80.0/23^23-29, 121.127.196.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.201.64.0/23^23-29, 141.243.8.0/23^23-29, 141.243.32.0/23^23-29, 180.235.104.0/23^23-29, 199.212.92.0/23^23-29, 202.4.162.0/23^23-29, 202.4.226.0/23^23-29, 202.6.56.0/23^23-29, 202.6.116.0/23^23-29, 202.7.2.0/23^23-29, 202.8.44.0/23^23-29, 202.12.70.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.62.0/23^23-29, 202.14.248.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.218.0/23^23-29, 202.37.240.0/23^23-29, 202.46.176.0/23^23-29, 202.46.190.0/23^23-29, 202.49.62.0/23^23-29, 202.49.148.0/23^23-29, 202.49.164.0/23^23-29, 202.56.62.0/23^23-29, 202.61.2.0/23^23-29, 202.65.160.0/23^23-29, 202.67.118.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.150.60.0/23^23-29, 202.158.254.0/23^23-29, 202.162.64.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.169.176.0/23^23-29, 202.169.220.0/23^23-29, 202.174.6.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.10.76.0/23^23-29, 203.16.60.0/23^23-29, 203.17.112.0/23^23-29, 203.18.102.0/23^23-29, 203.21.76.0/23^23-29, 203.22.70.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.30.98.0/23^23-29, 203.33.60.0/23^23-29, 203.33.70.0/23^23-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20100224 source: NZRR ------------------------------------------------------------

2 1

Re: [nznog] Counting Teredo traffic...
by Nathan Ward 21 Feb '10

21 Feb '10

Sorry, I know you replied off list but you're not the first person to talk about these sorts of things with me so I'm replying on list so more people benefit. On 22/02/2010, at 11:04 PM, Joel Wiramu Pauling wrote: >> No. >> Teredo servers are using for essentially control traffic. >> Teredo relays move data to/from the native IPv6 network (non-Teredo). >> >> Unless you really really know what you're doing, don't run a Teredo server. Run a Teredo *relay*. > > Sure, but you might want to do both so you can both: > > a) Grab the control traffic so it does not leave the network for > instances where it's impracticle to specify a teredo server to edge > clients. > b) Tell it to use your relay -> Feed into your native v6 > infrastructure and benefit from not having potentially long inefficent > routes. > c) This would work where you have v6 but for whatever reason can't get > it out to the edge. And don't want to push a tunnel client etc out. > (not ideal but, it's just another option in the whole transition > ecosystem). No, that won't work. 1) Your customer sends an ICMPv6 echo request to a web server, through your Teredo server (but they really mean to sent it elsewhere) 2) You send it to some server of yours that is configured to respond to every ICMPv6 echo request, with the source address set to the destination address of the request. 3) ICMPv6 echo reply goes through your Teredo relay, and then to the customer. 4) Customer's Teredo stack detects your relay's IPv4 and UDP port. 5) Customer sends a TCP SYN to the web server, through your relay. 6) Your relay decapsulates it, and sends it on to the IPv6 network, probably over a longer path than it would take than an automatically discovered relay would use. 7) No worry though, because the SYN+ACK will come back through the better relay. 8) Your customer will detect the IPv4 address and UDP port of the new, better relay. Don't try to shoe horn Teredo in to doing these things, it's designed to be hard for ISPs to control, quite intentionally. Install a relay when you roll out your native IPv6 network and move on. > It's essentially your TUI box idea, with dns hacks. ;-) Not really, the only thing that the Tui boxes do with Teredo is relay. They aren't Teredo servers. You could probably configure one to be because they just have Miredo inside, but that's not what they're for. The Tui boxes are also 6to4 relays, and they build a peering mesh over IPv4 best-paths between other Tui boxes. The only similarities between what you're proposing, and Tui, is that they both implement parts of Teredo. -- Nathan Ward

2 2

Counting Teredo traffic...
by Joel Wiramu Pauling 21 Feb '10

21 Feb '10

So, what is the best way to count teredo traffic on their networks, assume I just want packet counts and nothing else. * I know that if I have netflows I can look for the 2001:0000: address marker inside packets, but this is a) resource intensive, b) assumes I have full netflows. * I can also count traffic originating from the various teredo relays/servers... but this again would require being able to mark a full flow and track things Does anyone know of a better way or at least other techniques? Kind regards -JoelW

3 4