The New Zealand Network Operators' Group
The New Zealand Network Operators' Group (NZNOG) has no king,
president or formal membership. At present it consists of the
subscribers to this mailing list, which anyone is free to join.
Meetings
Our next annual conference is to be hosted by the WAND group in Hamilton
on February 2nd to 4th, 2005. See http://www.nznog.org/ for more
information, including the Call For Presentations. Offers to present are
due in by 22nd October, and all presenters
should have had their acceptance confirmed by 31st October.
Also see http://auckland.thursdaynightcurry.com/ if you live in or near
Auckland or Wellington.
Operators' Contact List
See http://www.usenet.net.nz/noc/ for operational contact details
for most New Zealand ISP's. These are intended for use by other
network operators, not by most customers.
Internet Exchanges
See http://www.ape.net.nz/ for details of the Auckland Peering
Exchange and those connected there. See http://www.wix.net.nz/ for the
Wellington Internet Exchange.
About This Mailing List
This list has slightly over 700 addresses subscribed. You may only post
to the list from a subscribed address. A number of people subscribe
addresses which do not receive email purely to allow posting from them.
You may choose to receive postings as they come in, or just to receive
daily "digests". See the bottom of the page
http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in
which you receive postings.
The NZNOG mailing list is provided through a server at The University of
Waikato, and is administered by employees of Alcatel NZ Ltd, Citylink
and Telecom. None of these organisations, nor any administrator, is
responsible for its content.
NZNOG Mailing List Acceptable Use Policy
The NZNOG mailing list exists to provide a forum for the exchange of
technical information and the discussion of implementation issues
that require cooperation among New Zealand network service providers.
In order to continue to provide a useful forum for discussion of
relevant technical issues, users of the list are asked to respect the
following guidelines.
1. Discussion will focus on Internet operational and technical
issues.
2. Discussion related to meetings of network service providers is
appropriate.
3. Discussion unrelated to these topics is not appropriate.
4. Postings to multiple mailing lists are discouraged.
5. Postings that include foul language, character assassination, and
lack of respect for other participants are unacceptable.
6. Blatant product or service marketing is unacceptable.
7. Postings of a political, philosophical or legal nature are
discouraged.
8. Postings to the list should be in ASCII or MIME encoded as
text/plain. Attachments should not be sent to the list. To
present a document, a suitable URL may be referred to. For
documents of general interest, the use of proprietary file
formats is discouraged.
9. Breaches of list etiquette should be dealt with privately with the
offending list user, and should not result in complaints being
sent to the list.
10. A person repeatedly breaching list etiquette shall receive warnings
from the list administrator. A further breach after the second such
warning within thirty days shall result in the offender being
unsubscribed from the list. Other action may also be taken to block
postings to the list by the offender. Any such unsubscription is to
be immediately announced to the list.
Mailing List Archives
A full archive is available at
http://list.waikato.ac.nz/pipermail/nznog/
Any message sent to the list will be archived and made available on the
web automatically. Changes are not made to the archive on request,
though the administrators remain happy to assist the Office of the
Privacy Commissioner should any complaint be laid with that office.
One way to search the archive is to use google and prefix your search
with
site:list.waikato.ac.nz .
Subscribing to the List
See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe.
Donald Neal
NZNOG Mailing List Owner/Administrator/Muggins
Donald Neal |Palmersdale: Are you in charge here?
Technical Specialist |The Doctor: No, but I'm full of
Operations Engineering | ideas.
Integration & Services Division +-----------------------
Alcatel NZ Ltd - Telecom's network operations manager
------------------------------------------------------------------------------
"This communication, including any attachments, is confidential.
If you are not the intended recipient, you should not read
it - please contact me immediately, destroy it, and do not
copy or use any part of this communication or disclose
anything about it. Thank you. Please note that this
communication does not designate an information system for
the purposes of the Electronic Transactions Act 2002."
------------------------------------------------------------------------------
Dear Colleague,
This is to notify you that some object(s) in NZRR database
which you either maintain or are listed as to-be-notified have
been added, deleted or changed.
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.
---
OBJECT BELOW CREATED:
aut-num: AS24386
as-name: NZRR-AS24386
descr: Networker
descr: APE peering at '192.203.154.15'
descr: see Citylink RT job #2115
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
import: from AS9560
accept ANY AND NOT fltr-bogons
export: to AS9560
announce AS24386
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: simon(a)networker.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050401
source: NZRR
---
OBJECT BELOW CREATED:
route-set: AS9560:RS-ROUTES:AS24386
descr: Route set advertised to AS9560 by Networker - AS24386
members: 203.109.148.24/29,
203.109.194.16/28^28-29,
203.118.128.32/27^27-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: simon(a)networker.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050401
source: NZRR
Dear Colleague,
This is to notify you that some object(s) in NZRR database
which you either maintain or are listed as to-be-notified have
been added, deleted or changed.
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.
---
PREVIOUS OBJECT:
aut-num: AS23754
as-name: NZRR-AS23754
descr: CityLink
descr: SIX peering at '218.100.25.3'
descr: see Citylink RT job #1927
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
import: from AS24387
accept ANY AND NOT fltr-bogons
export: to AS24387
announce AS23754
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: asjl(a)citylink.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050331
source: NZRR
REPLACED BY:
aut-num: AS23754
as-name: NZRR-AS23754
descr: CityLink
descr: SMARTLINX3 peering at '218.100.26.3'
descr: see Citylink RT job #1927
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
import: from AS24385
accept ANY AND NOT fltr-bogons
export: to AS24385
announce AS23754
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: asjl(a)citylink.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050331
source: NZRR
---
OBJECT BELOW CREATED:
route-set: AS24385:RS-ROUTES:AS23754
descr: Route set advertised to AS24385 by CityLink - AS23754
members: 202.8.44.0/22^22-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: asjl(a)citylink.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050331
source: NZRR
Dear Colleague,
This is to notify you that some object(s) in NZRR database
which you either maintain or are listed as to-be-notified have
been added, deleted or changed.
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.
---
PREVIOUS OBJECT:
aut-num: AS23754
as-name: NZRR-AS23754
descr: CityLink
descr: CHIX peering at '218.100.24.3'
descr: see Citylink RT job #1927
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
import: from AS24388
accept ANY AND NOT fltr-bogons
export: to AS24388
announce AS23754
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: asjl(a)citylink.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050331
source: NZRR
REPLACED BY:
aut-num: AS23754
as-name: NZRR-AS23754
descr: CityLink
descr: SIX peering at '218.100.25.3'
descr: see Citylink RT job #1927
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
import: from AS24387
accept ANY AND NOT fltr-bogons
export: to AS24387
announce AS23754
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: asjl(a)citylink.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050331
source: NZRR
Dear Colleague,
This is to notify you that some object(s) in NZRR database
which you either maintain or are listed as to-be-notified have
been added, deleted or changed.
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.
---
PREVIOUS OBJECT:
aut-num: AS23754
as-name: NZRR-AS23754
descr: CityLink
descr: SIX peering at '218.100.25.2'
descr: see Citylink RT job #1927
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
import: from AS24387
accept ANY AND NOT fltr-bogons
export: to AS24387
announce AS23754
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: asjl(a)citylink.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050331
source: NZRR
REPLACED BY:
aut-num: AS23754
as-name: NZRR-AS23754
descr: CityLink
descr: CHIX peering at '218.100.24.3'
descr: see Citylink RT job #1927
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
import: from AS24388
accept ANY AND NOT fltr-bogons
export: to AS24388
announce AS23754
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: asjl(a)citylink.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050331
source: NZRR
---
OBJECT BELOW CREATED:
route-set: AS24388:RS-ROUTES:AS23754
descr: Route set advertised to AS24388 by CityLink - AS23754
members: 202.8.44.0/22^22-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: asjl(a)citylink.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050331
source: NZRR
Dear Colleague,
This is to notify you that some object(s) in NZRR database
which you either maintain or are listed as to-be-notified have
been added, deleted or changed.
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.
---
PREVIOUS OBJECT:
aut-num: AS23754
as-name: NZRR-AS23754
descr: CityLink
descr: DPE peering at '218.100.23.3'
descr: see Citylink RT job #1927
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
import: from AS24384
accept ANY AND NOT fltr-bogons
export: to AS24384
announce AS23754
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: asjl(a)citylink.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050331
source: NZRR
REPLACED BY:
aut-num: AS23754
as-name: NZRR-AS23754
descr: CityLink
descr: SIX peering at '218.100.25.2'
descr: see Citylink RT job #1927
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
import: from AS24387
accept ANY AND NOT fltr-bogons
export: to AS24387
announce AS23754
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: asjl(a)citylink.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050331
source: NZRR
---
OBJECT BELOW CREATED:
route-set: AS24387:RS-ROUTES:AS23754
descr: Route set advertised to AS24387 by CityLink - AS23754
members: 202.8.44.0/22^22-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: asjl(a)citylink.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050331
source: NZRR
Dear Colleague,
This is to notify you that some object(s) in NZRR database
which you either maintain or are listed as to-be-notified have
been added, deleted or changed.
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.
---
OBJECT BELOW CREATED:
route-set: AS24384:RS-ROUTES:AS23755
descr: Route set advertised to AS24384 by CityLink - AS23755
members: 202.8.44.0/22^22-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: asjl(a)citylink.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050331
source: NZRR
Dear Colleague,
This is to notify you that some object(s) in NZRR database
which you either maintain or are listed as to-be-notified have
been added, deleted or changed.
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.
---
PREVIOUS OBJECT:
route: 202.8.44.0/22
descr: Route for CityLink - AS23754
origin: AS23754
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20041028
source: NZRR
REPLACED BY:
route: 202.8.44.0/22
descr: Route for CityLink - AS23754
origin: AS23754
notify: rpsl-admin(a)nzix.net
notify: asjl(a)citylink.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050331
source: NZRR
---
OBJECT BELOW CREATED:
route-set: AS24384:RS-ROUTES:AS23754
descr: Route set advertised to AS24384 by CityLink - AS23754
members: 202.8.44.0/22^22-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: asjl(a)citylink.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050331
source: NZRR
Hi guys - this isn't strictly operational but I think it's an
appropriate audience.
As per the subject, I'm after current info about experiences with MFAT
over the export of strong crypto, either as software, or embedded in
hardware. The online references I can find (Some listed below) are
reasonably old and I was hoping there had been some change.
(I quote from a 1997 letter from Sec Foreign affairs and trade - Mr
Borrie)
"This sort of product (encrpytion software) is considered a "dual use"
good in terms of the New Zealand Export Controls which means that they
are able to be adapted for military, terrorist or criminal use" (I could
adapt a plastic spoon for criminal use - but that's beside the
point!)
Source : http://www.cs.auckland.ac.nz/~pgut001/policy/mfat_2r.html
I looked at the MFAT site and they still list encryption software on
their "New Zealand Strategic Goods List Index of Controlled Goods"
page.
Source : http://www.mfat.govt.nz/foreign/dis/nzsgl/pages/laste.html
So I guess my question is does anyone know if they have relaxed their
approach to 3DES (or even AES-xxx) given that these 'technologies'
are freely available internationally, and that 128bit encryption has
been effectively opened way up by international adoption in browsers?
I'm happy to summarise if there's a bit of feedback.
Cheers - Neil Gardner.
NOTICE: This message contains privileged and confidential
information intended only for the use of the addressee
named above. If you are not the intended recipient of
this message you are hereby notified that you must not
disseminate, copy or take any action in reliance on it.
If you have received this message in error please
notify Allied Telesyn Research Ltd immediately.
Any views expressed in this message are those of the
individual sender, except where the sender has the
authority to issue and specifically states them to
be the views of Allied Telesyn Research.
