(apology for any duplicate - slightly less tech in nature but worth
sharing as its about DNS admin)
Dear colleagues,
My first mail in 2008 - so very warm greetings all.
First up I'd like to highlight this very important information from
ICANN. ccTLD managers in each economy have received this as well.
ICANN in the past have had its fair share of critics "for/against"
the current model or it's relationship with the US Govt and
transition to
independence. (just have to Goggle to read …
[View More]this)
May I request those that particularly follow ICANN work (and those
new to this space) to spare some time to read through the latest
announcement from ICANN website particularly the "Joint Project
Agreement - ICANN response" about the Notice of Inquiry put out by
the USG regarding ICANN and the USG Joint Partnership Agreement.
The documents referenced will clarify why ICANN was formed and
delegated the role to perform the technical coordination and
management of the Internet’s domain name and addressing system (DNS).
ICANN's role is now in midterm review with this Notice of Inquiry
requested for by the USG. http://www.icann.org/
As you will see from ICANN's submission, among other things, it is
the view
of the ICANN Board that:
~ The JPA like the memorandums of understanding before it has helped
ICANN to become a stable organization;
~ ICANN has executed the terms of the JPA commenced in September 2006;
~ ICANN is meeting its responsibilities under the JPA;
~ The JPA is no longer necessary. Concluding it is the next step in
transition
of the coordination of the Domain Name System (DNS) to the private
sector;
~ This step will provide continuing confidence that the original
vision laid out
in the White Paper is being delivered;
~ Concluding the JPA will not affect existing accountabilities
expressed in the
IANA contract and the United States Government¹s participation
through the
Governmental Advisory Committee.
I am sure that both ICANN and the US Department of Commerce would
appreciate hearing the views of the Internet community on this important
review.
As there's a very narrow window in which to tailor and submit
responses/comments I hope I can again contact some of you to discuss
or please feel free to contact me at any time to clarify. It will be
useful under this review term that as many responses are received
from those parties interested to have a say. I encourage those
interested in
this list to also contribute to this process and to add to a truly
global response.
Now is the chance to get your voices heard.
Comments close on 15 February.
regards,
--
Save Vocea
Global Partnerships
Manager, Regional Relations - Australasia/Pacific Islands
http://www.icann.org
ICANN is about coordination, not control
[View Less]
Hi There,
Does anyone have ssh access to a well connected host that can run iperf
that is either directly connected or very near AS7018 in the US?
If so, can you please contact me offlist thanks?
Cheers
Jamie
Some of the list members who were around in the early 90's may have
known Martin Hunt, a Sysadmin based in Wellington. He passed away
suddenly at home last week aged 46. There was a death notice in
Saturday's Dominion Post.
He was a really nice guy.
Martin worked at Govt Print (with Don Stokes, Larry Hall and Ian
Calhaem, etc), then WCC IT Dept and latterly at Fairfax Media. While
at WCC he was one of the Sysadmins who looked after WCC CityNet. He
was active in DECUS in the early 90's.…
[View More]
A service for Martin will be held in St Lukes, cnr Pitt St and
Wadestown Rd, Wednesday 16 January at 1100
(sadly I have to be working elsewhere).
Messages to Martin's family c/o P O Box 50-347 Porirua, or I can pass
on emails via his brother.
A really nice guy. He will be missed.
Richard
[View Less]
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 …
[View More]all times and
consequently a full set of routes.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9560:RS-ROUTES:AS9889
descr: advertised to AS9560 by Maximum Internet Ltd - AS9889
members: 123.100.64.0/18^18-29,
124.198.128.0/18^18-29,
202.89.32.0/19^19-29,
203.89.160.0/19^19-29,
202.189.160.0/21^21-29,
210.55.100.0/22^22-29,
210.55.104.0/22^22-29,
210.54.142.0/23^23-29,
117.53.150.0/24^24-29,
192.138.251.0/24^24-29,
202.6.5.0/24^24-29,
202.27.8.0/24^24-29,
202.27.204.0/24^24-29,
202.36.70.0/24^24-29,
202.36.227.0/24^24-29,
202.37.72.0/24^24-29,
202.37.162.0/24^24-29,
202.37.181.0/24^24-29,
202.49.141.0/24^24-29,
202.150.102.0/24^24-29,
203.12.15.0/24^24-29,
203.97.42.0/24^24-29,
210.54.13.0/24^24-29,
210.55.169.0/24^24-29,
210.55.214.0/24^24-29,
210.55.230.0/24^24-29,
203.167.219.56/29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)maxnet.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20071120
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS9889
descr: advertised to AS9560 by Maximum Internet Ltd - AS9889
members: 123.100.64.0/18^18-29,
124.198.128.0/18^18-29,
202.89.32.0/19^19-29,
203.89.160.0/19^19-29,
202.55.96.0/20^20-29,
202.189.160.0/21^21-29,
210.55.100.0/22^22-29,
210.55.104.0/22^22-29,
117.53.150.0/23^23-29,
210.54.142.0/23^23-29,
192.138.251.0/24^24-29,
202.6.5.0/24^24-29,
202.27.8.0/24^24-29,
202.27.204.0/24^24-29,
202.36.70.0/24^24-29,
202.36.227.0/24^24-29,
202.37.72.0/24^24-29,
202.37.162.0/24^24-29,
202.37.181.0/24^24-29,
202.150.102.0/24^24-29,
203.12.15.0/24^24-29,
203.97.42.0/24^24-29,
210.54.13.0/24^24-29,
210.55.169.0/24^24-29,
210.55.214.0/24^24-29,
210.55.230.0/24^24-29,
203.167.219.56/29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)maxnet.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20080115
source: NZRR
---
PREVIOUS OBJECT:
route-set: AS9439:RS-ROUTES:AS64533
descr: advertised to AS9439 by ERMA - AS64533
members: 202.68.89.96/28^28-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: Mark.Harris(a)ermanz.govt.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060727
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS64533
descr: advertised to AS9439 by ERMA - AS64533
members: 202.68.89.96/28^28-29,
202.68.89.120/29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: Mark.Harris(a)ermanz.govt.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20080115
source: NZRR
------------------------------------------------------------
[View Less]
> The primary downside initially is that any legitimate server is doing
> two transactions for every email. This would delay mail slightly and
> increase queue lengths and CPU usage of every legitimate mail server
> sending to you. If everybody implemented this it would load mail
> servers up a bit.
My observation would be that a TCP reject doesn't result in a requeuing
of the email. With postix, it would appear that the smtp sending
process immediately tries the MX in the …
[View More]chain upto a max of 5 ( but this
is configurable ). There is a SYN packet, an RST and then a SYN to the
secondary, not IMHO a significant overhead or delay. NB: The first MX
must reject the connection not just drop it, otherwise the behaviour you
describe does occur.
> Again it is a temporary workaround but it might be worthwhile for
> knowledgable system administrators. Over time the issues of spam still
> need to be sorted out but that is a longer term project and is both
> technical and political.
It would seem that all spam solutions are just sticking plasters but a
'defense-in-depth' approach using multiple techniques does seem to be
viable for the time being.
Glen.
[View Less]
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 …
[View More]all times and
consequently a full set of routes.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9439:RS-ROUTES:AS10022
descr: Route set for AS10022
members: 202.27.77.0/24, 202.175.136.0/21^+
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20030407
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS10022
descr: advertised to AS9439 by Datacom Systems Wellington Limited - AS10022
members: 202.175.142.0/23^23-29,
192.203.216.0/24^24-29,
202.27.77.0/24^24-29,
202.36.12.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: matthewda(a)datacom.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20080111
source: NZRR
------------------------------------------------------------
[View Less]
I would like to hold a lightning talk session during the Sysadmin Miniconf
stream at NZNOG 2008 (in Dunedin very soon; register now!). If you
would be willing to talk for 5-15 minutes about either:
- a tool, or technique that you find useful and think others should know
about; or
- how your AS looks after servers, users, etc (eg, what you use for
deploying servers, how you manage trouble tickets, how you handle
mail, etc)
I'd like to hear from you soon. Email nznog08 @ nznog.miniconf.…
[View More]org
to register your interest in speaking with an indication of how much
time you need to cover your topic (eg 5 minutes, or 15 minutes).
Also if anyone is willing to talk about:
- Deploying IPv6 aware applications[0]; or
- A comparision of trouble ticket/helpdesk systems (RT versus OTRS versus...)
I'd love to hear from you ASAP. Email nznog08 @ nznog.miniconf.org
with offers to speak. Other topics are of course welcome too, but I'd
need to know this week.
Ewen McNeill
For the Sysadmin Miniconf
[0] Yes, I know there's an entire IPv6 stream on at the same time. But
a shorter overview of the application aspects would still be very
useful especially from a sysadmin who has "been there, done that"
without necessarily having got involved in IPv6 routing.
[View Less]
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 …
[View More]all times and
consequently a full set of routes.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9560:RS-ROUTES:AS2687
descr: advertised to AS9560 by AT&T - AS2687
members: 202.46.160.0/20^20-29,
202.126.80.0/21^21-29,
202.160.112.0/21^21-29,
202.36.192.0/22^22-29,
152.158.254.0/23^23-29,
202.36.68.0/23^23-29,
202.135.48.0/23^23-29,
203.163.70.0/23^23-29,
125.236.50.0/24^24-29,
192.203.216.0/24^24-29,
202.12.105.0/24^24-29,
202.14.252.0/24^24-29,
202.21.128.0/24^24-29,
202.27.160.0/24^24-29,
202.36.29.0/24^24-29,
202.36.80.0/24^24-29,
202.37.254.0/24^24-29,
202.49.144.0/24^24-29,
202.50.137.0/24^24-29,
202.135.20.0/24^24-29,
202.135.34.0/24^24-29,
202.135.38.0/24^24-29,
202.135.62.0/24^24-29,
202.135.64.0/24^24-29,
202.135.85.0/24^24-29,
202.135.107.0/24^24-29,
202.135.111.0/24^24-29,
202.135.112.0/24^24-29,
202.135.116.0/24^24-29,
202.135.142.0/24^24-29,
202.135.146.0/24^24-29,
202.135.182.0/24^24-29,
202.135.185.0/24^24-29,
202.135.190.0/24^24-29,
202.135.192.0/24^24-29,
202.135.231.0/24^24-29,
202.135.234.0/24^24-29,
203.57.145.0/24^24-29,
203.163.68.0/24^24-29,
203.163.86.0/24^24-29,
203.163.94.0/24^24-29,
203.163.98.0/24^24-29,
203.196.101.0/24^24-29,
203.196.119.0/24^24-29,
203.196.121.0/24^24-29,
219.88.103.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: attnzdns(a)ap.att.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20070601
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS2687
descr: advertised to AS9560 by AT&T - AS2687
members: 202.46.160.0/20^20-29,
202.126.80.0/21^21-29,
202.160.112.0/21^21-29,
202.36.192.0/22^22-29,
152.158.254.0/23^23-29,
202.36.68.0/23^23-29,
202.135.48.0/23^23-29,
202.175.142.0/23^23-29,
203.163.70.0/23^23-29,
125.236.50.0/24^24-29,
192.203.216.0/24^24-29,
202.12.105.0/24^24-29,
202.14.252.0/24^24-29,
202.21.128.0/24^24-29,
202.27.77.0/24^24-29,
202.27.160.0/24^24-29,
202.36.12.0/24^24-29,
202.36.29.0/24^24-29,
202.36.80.0/24^24-29,
202.37.254.0/24^24-29,
202.49.144.0/24^24-29,
202.50.137.0/24^24-29,
202.135.20.0/24^24-29,
202.135.34.0/24^24-29,
202.135.38.0/24^24-29,
202.135.62.0/24^24-29,
202.135.64.0/24^24-29,
202.135.85.0/24^24-29,
202.135.107.0/24^24-29,
202.135.111.0/24^24-29,
202.135.112.0/24^24-29,
202.135.116.0/24^24-29,
202.135.142.0/24^24-29,
202.135.146.0/24^24-29,
202.135.182.0/24^24-29,
202.135.185.0/24^24-29,
202.135.190.0/24^24-29,
202.135.192.0/24^24-29,
202.135.231.0/24^24-29,
202.135.234.0/24^24-29,
203.57.145.0/24^24-29,
203.163.68.0/24^24-29,
203.163.86.0/24^24-29,
203.163.94.0/24^24-29,
203.163.98.0/24^24-29,
203.196.101.0/24^24-29,
203.196.119.0/24^24-29,
203.196.121.0/24^24-29,
219.88.103.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: brian.gould(a)ap.att.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20080109
source: NZRR
------------------------------------------------------------
[View Less]
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 …
[View More]all times and
consequently a full set of routes.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9439:RS-ROUTES:AS2687
descr: advertised to AS9439 by AT&T - AS2687
members: 202.46.160.0/20^20-29,
202.126.80.0/21^21-29,
202.160.112.0/21^21-29,
202.36.192.0/22^22-29,
152.158.254.0/23^23-29,
202.36.68.0/23^23-29,
202.135.48.0/23^23-29,
203.163.70.0/23^23-29,
125.236.50.0/24^24-29,
192.203.216.0/24^24-29,
202.12.105.0/24^24-29,
202.14.252.0/24^24-29,
202.21.128.0/24^24-29,
202.27.160.0/24^24-29,
202.36.29.0/24^24-29,
202.36.80.0/24^24-29,
202.37.254.0/24^24-29,
202.49.144.0/24^24-29,
202.50.137.0/24^24-29,
202.135.20.0/24^24-29,
202.135.34.0/24^24-29,
202.135.38.0/24^24-29,
202.135.62.0/24^24-29,
202.135.64.0/24^24-29,
202.135.85.0/24^24-29,
202.135.107.0/24^24-29,
202.135.111.0/24^24-29,
202.135.112.0/24^24-29,
202.135.116.0/24^24-29,
202.135.142.0/24^24-29,
202.135.146.0/24^24-29,
202.135.182.0/24^24-29,
202.135.185.0/24^24-29,
202.135.190.0/24^24-29,
202.135.192.0/24^24-29,
202.135.231.0/24^24-29,
202.135.234.0/24^24-29,
203.57.145.0/24^24-29,
203.163.68.0/24^24-29,
203.163.86.0/24^24-29,
203.163.94.0/24^24-29,
203.163.98.0/24^24-29,
203.196.101.0/24^24-29,
203.196.119.0/24^24-29,
203.196.121.0/24^24-29,
219.88.103.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: attnzdns(a)ap.att.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20070601
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS2687
descr: advertised to AS9439 by AT&T - AS2687
members: 202.46.160.0/20^20-29,
202.126.80.0/21^21-29,
202.160.112.0/21^21-29,
202.36.192.0/22^22-29,
152.158.254.0/23^23-29,
202.36.68.0/23^23-29,
202.135.48.0/23^23-29,
202.175.142.0/23^23-29,
203.163.70.0/23^23-29,
125.236.50.0/24^24-29,
192.203.216.0/24^24-29,
202.12.105.0/24^24-29,
202.14.252.0/24^24-29,
202.21.128.0/24^24-29,
202.27.77.0/24^24-29,
202.27.160.0/24^24-29,
202.36.12.0/24^24-29,
202.36.29.0/24^24-29,
202.36.80.0/24^24-29,
202.37.254.0/24^24-29,
202.49.144.0/24^24-29,
202.50.137.0/24^24-29,
202.135.20.0/24^24-29,
202.135.34.0/24^24-29,
202.135.38.0/24^24-29,
202.135.62.0/24^24-29,
202.135.64.0/24^24-29,
202.135.85.0/24^24-29,
202.135.107.0/24^24-29,
202.135.111.0/24^24-29,
202.135.112.0/24^24-29,
202.135.116.0/24^24-29,
202.135.142.0/24^24-29,
202.135.146.0/24^24-29,
202.135.182.0/24^24-29,
202.135.185.0/24^24-29,
202.135.190.0/24^24-29,
202.135.192.0/24^24-29,
202.135.231.0/24^24-29,
202.135.234.0/24^24-29,
203.57.145.0/24^24-29,
203.163.68.0/24^24-29,
203.163.86.0/24^24-29,
203.163.94.0/24^24-29,
203.163.98.0/24^24-29,
203.196.101.0/24^24-29,
203.196.119.0/24^24-29,
203.196.121.0/24^24-29,
219.88.103.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: brian.gould(a)ap.att.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20080109
source: NZRR
------------------------------------------------------------
[View Less]
[Apologies for any duplicates...]
A quick reminder that the NZNOG 2008 conference is only two weeks
away now.
http://conference.nznog.org
We need to finalise numbers very shortly now, so go ahead and
register NOW if you intend to come and haven't already.
The largely-finalised programme is up on the website, there's been
some great new additions over the past month so do check it out at:
http://conference.nznog.org/conferenceprogramme.html
Thanks, and looking forward to …
[View More]seeing you in Dunedin!
Jonny.
[View Less]
