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: AS9281:RS-ROUTES:AS38477
descr: advertised to AS9281 by Unleash - AS38477
members: 116.90.128.0/20^20-29,
103.11.124.0/22^22-29,
113.130.120.0/22^22-29,
114.23.96.0/22^22-29,
182.50.160.0/22^22-29,
202.44.60.0/22^22-29,
131.203.134.0/23^23-29,
202.6.116.0/23^23-29,
202.37.124.0/23^23-29,
131.203.133.0/24^24-29,
192.138.251.0/24^24-29,
202.50.102.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: noc(a)unleash.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20111026
source: NZRR
REPLACED BY:
route-set: AS9281:RS-ROUTES:AS38477
descr: advertised to AS9281 by Unleash - AS38477
members: 116.90.128.0/20^20-29,
103.11.124.0/22^22-29,
113.130.120.0/22^22-29,
114.23.96.0/22^22-29,
182.50.160.0/22^22-29,
202.44.60.0/22^22-29,
131.203.134.0/23^23-29,
202.6.116.0/23^23-29,
202.37.124.0/23^23-29,
103.246.250.0/24^24-29,
131.203.133.0/24^24-29,
192.138.251.0/24^24-29,
202.50.102.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: noc(a)unleash.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20111125
source: NZRR
------------------------------------------------------------
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: AS9439:RS-ROUTES:AS38477
descr: advertised to AS9439 by Unleash - AS38477
members: 116.90.128.0/20^20-29,
103.11.124.0/22^22-29,
113.130.120.0/22^22-29,
114.23.96.0/22^22-29,
182.50.160.0/22^22-29,
202.44.60.0/22^22-29,
131.203.134.0/23^23-29,
202.6.116.0/23^23-29,
202.37.124.0/23^23-29,
131.203.133.0/24^24-29,
192.138.251.0/24^24-29,
202.50.102.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: noc(a)unleash.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20111025
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS38477
descr: advertised to AS9439 by Unleash - AS38477
members: 116.90.128.0/20^20-29,
103.11.124.0/22^22-29,
113.130.120.0/22^22-29,
114.23.96.0/22^22-29,
182.50.160.0/22^22-29,
202.44.60.0/22^22-29,
131.203.134.0/23^23-29,
202.6.116.0/23^23-29,
202.37.124.0/23^23-29,
103.246.250.0/24^24-29,
131.203.133.0/24^24-29,
192.138.251.0/24^24-29,
202.50.102.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: noc(a)unleash.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20111125
source: NZRR
------------------------------------------------------------
-------- Original Message --------
Subject: [apnic-talk] APRICOT-2012: Call for Papers
Date: Wed, 23 Nov 2011 17:51:59 +0800
From: Mark Tinka <mtinka(a)globaltransit.net>
Reply-To: mtinka(a)globaltransit.net
Organization: Global Transit International
To: apnic-talk(a)lists.apnic.net
Asia Pacific Regional Internet Conference on Operational Technologies
(APRICOT)
21 February - 2 March 2012, New Delhi, India
http://www.apricot2012.net
CALL FOR PAPERS
===============
The APRICOT 2012 Programme Committee is now seeking contributions for
Presentations and Tutorials for APRICOT 2012.
We are looking for people and proposals that would:
- Offer a technical tutorial on an appropriate topic; and/or
- Participate in the technical conference sessions as a speaker; and/or
- Convene and chair a Birds of a Feather (BOF) session.
Please submit proposals on-line at:
http://submission.apnic.net/
CONFERENCE MILESTONES
---------------------
Call for Papers Opens: 22 November 2011
First Draft Program Published: 19 December 2011
Final Deadline for Submissions: 10 February 2012
Final Program Published: 17 February 2012
Final Slides Received: 25 February 2012
PROGRAM MATERIAL
----------------
The APRICOT Programme is organised in three parts, including
workshops, tutorials and the conference. The APNIC Policy SIG and
Annual Members Meeting will be held during the APRICOT conference.
Topics for tutorials and conference would include amongst others
relevant to Internet Operations and Technologies:
- IPv4 / IPv6 Routing and operations
- IPv4 address runout / IPv6 deployment and transition technologies
- Backbone operations
- ISP and Carrier services
- Network security issues (NSP-SEC, DDoS Anti-Spam, Anti-Malware)
- Peering / IXPs
- DNS / DNSSEC
- Internet policy (Security, Regulation, Content Management, Addressing,
etc)
- Access and Transport Technologies, including broadband deployment,
Cable/DSL, wireless, WiMax, metro ethernet, fiber
network, MPLS
- Content & Service Delivery (Multicast, Voice, Video, "telepresence",
Gaming)
CfP SUBMISSION
--------------
All draft and complete slides must be submitted in PDF format
only.
Draft slides for both tutorials and conference sessions MUST be
provided with CfP submissions otherwise the Programme Committee will
be unable to review the submission. For work in progress, the most
current information available at time of submission is acceptable.
Final slides are to be provided by the specified deadline for
publication on the APRICOT website.
While the majority of speaking slots will be filled by the first
submission deadline, a limited number of slots may be available up to
the final submission deadline for presentations that are exceptionally
timely, important, or of critical operational importance.
Please submit on-line at:
http://submission.apnic.net/
Any questions or concerns should be addressed to the Programme
Committee by e-mail at:
pc-chairs at apricot.net
We look forward to receiving your presentation proposals.
Mark Tinka & Jonny Martin
Co-Chairs, APRICOT Programme Committee
program(a)apricot.net
Very interesting tool in these times of ip runout.
…Skeeve
--
Skeeve Stevens, CEO - eintellego Pty Ltd
skeeve(a)eintellego.net<mailto:skeeve(a)eintellego.net> ; www.eintellego.net
Phone: 1300 753 383 ; Fax: (+612) 8572 9954
Cell +61 (0)414 753 383 ; skype://skeeve
facebook.com/eintellegotwitter.com/networkceoau ; www.linkedin.com/in/skeeve
PO Box 7726, Baulkham Hills, NSW 1755 Australia
--
eintellego - The Experts Who The Experts Call
Juniper - HP Networking - Cisco - Brocade
On 23/11/11 8:13 AM, "ARIN" <info(a)arin.net<mailto:info(a)arin.net>> wrote:
ARIN is pleased to announce the availability of a trial WHOWAS service
that will provide historical registration information for a given IP
address or ASN. During the trial, requests should be submitted via email
to hostmaster(a)arin.net<mailto:hostmaster(a)arin.net> and must include details about the registration
in question and the reason for the request.
Requestors will then be required to sign and return an WHOWAS Terms of
Use Agreement before their WHOWAS request can be processed. Because
requests will be manually processed during the trial, ARIN reserves the
right to set limits on the number of requests that can be made by any
single entity, regarding both the number of requests and period of time
for requests.
ARIN will make every effort to process requests in a timely fashion, but
makes no specific guarantees related to processing time.
This trial period will run for the remainder of 2011, and will serve to
provide much needed data to assist ARIN in defining the scope and
requirements for automating this service. ARIN reserves the right to
terminate this service prior to the end of 2011 should request volumes
exceed ARIN’s ability to provide responses in a timely manner. During
the trial, ARIN will evaluate, what, if any fees may be charged for
future availability of this service.
For full details, instructions on how to take advantage this trial
service, and to view the Terms of Use Agreement, please visit:
https://www.arin.net/resources/whowas/
Regards,
Nate Davis
Chief Operating Officer
American Registry for Internet Numbers (ARIN)
_______________________________________________
ARIN-Announce
You are receiving this message because you are subscribed to
the ARIN Announce Mailing List (ARIN-announce(a)arin.net<mailto:ARIN-announce(a)arin.net>).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-announce
Please contact info(a)arin.net<mailto:info(a)arin.net> if you experience any issues.
________________________________________________________________________
Changes to APNIC IPv4 transfer policy
________________________________________________________________________
APNIC account holders wishing to be the recipient of IPv4 transfers
must now justify their need for the resources as a result of a policy
change taking effect from today, Monday, 21 November 2011.
To streamline the process, those seeking to be the recipient of IPv4
transfers may apply for pre-approval by demonstrating their need before
locating a source for the address space.
http://www.apnic.net/pre-approval
Updated policy documents
------------------------
This policy change is the implementation of prop-096: Maintaining
demonstrated needs requirement in transfer policy after the final
/8 phase
You can view the history of this policy proposal at:
http://www.apnic.net/policy/proposals/prop-096
The revised APNIC transfer, merger, acquisition, and takeover policy is
now open for final editorial comments. Please provide comments before
21 December 2011.
You can access the editorial call for comment at the link below.
http://www.apnic.net/community/policy/draft
Regards
Sunny
Had this come through from one of our techs. Thought I should pass it on in case it's appearing elsewhere
Cheers
Jodi
--
Jodi Thomson
Network & Systems Engineer
[Description: Description: Wasp New Zealand]
Ph +64-6-8355800
Fax +64-6-8355811
Mob +64-21-903712
E-Mail jodi(a)team.waspnet.co.nz
www.waspnet.co.nz<http://www.waspnet.co.nz/>
From: murray
Sent: Monday, 21 November 2011 6:14 p.m.
Subject: A new scam is appearing
Hi all, I been on the phone this avo to a few people who I support and help out, asking about telcos wanting them to pay their bill via credit card, what they are doing to phoning people saying they are either from Telecom / Xtra or another isp saying their account was overdue and if they dont pay they would be disconnected, and they had to pay via credit card and also they want remote access to check adsl modem settings are ok.
I phoned Telecom and vodafone about this one and they said its a new scam happening, so I thought I better pass this info for you to inform your clients or while talking on ph to customers that this is a scam to be aware of it.
Cheers
Muzz
http://ipcacoal.org/ipcacoal/includes/kiwi.htm
Firefox/Thunderbird often picks up a lot of this crap. I don't know how
it's done.
I don't know how you give the browsers the heads up so this crap doesn't
impact other users who have less clue than the likes of us.
I don't know if ISPs are putting blocks in for this sort of crap in
their proxys.
I don't know if KiwiBank have an active team dealing with this sort of
rubbish, though I get hit with them quite often, so clearly someone has
KB in their sights.
I do appreciate that some of this is just noise and business as usual,
but I welcome any comment on or off list.
As operators or people with some level of clue, I do consider it our
role to take some ownership.
D
--
Don Gould
31 Acheson Ave
Mairehau
Christchurch, New Zealand
Ph: + 64 3 348 7235
Mobile: + 64 21 114 0699
Dear Colleagues:
During the past few days, two major milestones have been accomplished in
the journey to enable DNSSEC for .nz
On Friday November 18th, the cryptographic keys required to sign the .nz
zones with DNSSEC were created. We have posted part of the materials
used during this procedure in our website:
http://nzrs.net.nz/content/first-key-generation
At 10:00am on Monday November 21st NZDT, a signed version of the .nz
zone went live. The DNSKEY records have been obscured to prevent
validation as a first step on the deployment phase. More details
available at
http://nzrs.net.nz/content/nz-signed-zone-published-obscured-keys
We've been monitoring the service closely during the past few hours and
no major changes have been observed. We are ready to see an spike on
DNSKEY queries starting from now ;)
Kind Regards,
--
Sebastian Castro
DNS Specialist
.nz Registry Services (New Zealand Domain Name Registry Limited)
desk: +64 4 495 2337
mobile: +64 21 400535
