Announcement: IPv6 Deployathon by MISPA & AFRINIC

From: Dr P Nyirenda paulos@sdnp.org.mw
To: mispa-l@sdnp.org.mw
Date sent: Sat, 17 Aug 2019 12:56:18 +0200
Subject: [Mispa-l] IPv6 traning workshop for engineers by AFRINIC - hosted by MISPA - 09-13 September 2019 - HOLD THE DATES

MISPA, [ Group Photo ]

I am pleased to advise that MISPA will host an AFRINIC IPv6 Training Workshop for Engineers [ Group Photo ] at College of Medicine from 09-13 September 2019 in Blantyre.

Please HOLD THOSE DATES for this workshop.

The workshop will be facilitated by 4 staff members of AFRINIC.

You, as a MISPA member, are, therefore, invited to recommend names of your staff that you would like to attend the workshop.

There are a limited number of 20 seats for the workshop for MISPA members plus an additional 10 for outsiders.

I will be making further updates as we approach the event dates (see below).

Regards,

Dr Paulos B Nyirenda
Malawi SDNP PC: http://www.sdnp.org.mw
NIC.MW & .mw ccTLD http://www.registrar.mw
Chair: MISPA http://www.mispa.org.mw
Tel: +265-(0)-882089166
Cell: +265-(0)-888-824787
E-mail: mispa-chair@mix.mw

What Actually Happens During the Deployathon?

Date sent: Thu, 5 Sep 2019 08:25:33 +0000
To: paulos@sdnp.org.mw
From: "do@afrinic.net"
Subject: What Actually Happens During the Deployathon?

Dear participant

Today, I want to give you a deeper view of what actually happens during a Deployathon. Remember:
- it's not a training workshop(no long lectures from us every day)
- it's hackathon-style, meaning that you'll be doing brainstorming, research & validation
- it's very informal, and it's focused on DOing.

When you applied for the event, we asked you to select an objective that you'd like to accomplish during the event. Your mission (should you choose to accept it) is to leave at the end of 3 days having accomplished that, in accordance with the change control procedure of your network.

On the first day, we will have an IPv6 deep-dive tutorial to refresh everyone on the core concepts of IPv6. Thereafter, for each problem, here's the general process we will follow:

Clarify ? Prototype ? Develop ? Validate ? Implement ? Document

CLARIFY

You will need to clarify exactly what you're actually trying to accomplish. No, you are not going to deploy IPv6 in 3 days! even if you have Vibranium in your blood. However, you can:
- Do a complete passive audit of your network to determine which devices are ready.
- Create the perfect IPv6 address plan and have it implemented in an IPAMS(we ban anyone doing address planning in a spreadsheet!!).
- Create candidate configurations for different devices ready for review by your change control board.
- Announce your IPv6 prefix in a MANRS-compliant way.
- etc etc etc

Here's an example of how clarity looks like:

Objective: Securely advertise our IPv6 Prefix(2001:db8::/32)
+ KR#1: Prefix 2001:db8::/32 visible from at least one external looking glass
+ KR#2: One IPv6 interface on our network is reachable over IPv6 from outside
+ KR#3: A route6 object in the whois database for 2001:db8::/32

You get the idea? We're not trying to solve world hunger, we just want to feed the person in front of us, then the next and the next and the next until one day we might solve world hunger!(yeah right) and it helps to be clear about that up front.

PROTOTYPE

With a clear problem, it's time to map out the implementation details. For this, all you really a large piece of paper, a marker, a network diagram and within 30 - 60 minutes you can
- sketch the section of the network that is going to be affected
- identify all the relevant interfaces on each of the devices
- write out IP addressing and other relevant attributes
- jot down notes/illustrations that you'll develop later

As you can probably tell, this isn't some straight forward do this, then that, then that and bam!! you're done. You'll research, discuss with fellow engineers, and the guides will explain any IPv6-specific concepts and best practices you need to understand.

DEVELOP & VALIDATE

Here, you take your prototype and flesh it out into a candidate configuration that will go through your change control process.

It may start with a template configuration with placeholder text and grows into a configuration. It could be a cloned VM or container of an existing service in a lab environment that you try to configure towards the target state. In either case, you will have a full understanding of every single change implied by every single command, it's impact and the risks involved.

Part of this also entails developing a test plan to ensure that nothing will break when the change is applied as well as a rollback plan.

IMPLEMENT

After your change request is approved, it's time to implement it. For some participants and for some deployment objectives, this could happen at the deployathon. In other cases, it will happen after the event during the maintenance window.

You might be wondering how long it takes to get through this cycle? Well, it depends on you and the change control process in your organisation. In the past, we've had participants go through that process within one day and ended up enabling IPv6 on their Internet edges, deploying IPv6 on a test VLAN or creating and implementing an IPv6 address plan in an IPAMS.

Tomorrow, we'll send you an email on how you can prepare to have a fruitful deployathon.

Warm regards

The AFRINIC Deployment Support team

P/S: Is your ORGANISATION an ISP? Do you know any of your customers engineers who would be interested in getting started with IPv6 deployment? Imagine what could be accomplished if both you were in the same room for 3 days! Invite them to join the deployathon with you(mail us to let us know so we can let them in)

--
The AFRINIC Deployment Support team
Deployment Operationalisation Engineer - Deployment Support Team
AFRINIC Ltd.
t: +230 403 51 00 | f: +230 466 6758 | tt: @afrinic | w: www.afrinic.net
powered by phpList