InTAC != Network Architecture
The Internet and the technology which enables it is much larger than
just Network Architecture.
So there's no need to append “from a network architecture perspective”
to identity and trust. It's enough to be talking about technical
solutions which enable identity and trust to be enhanced within the
architecture of the Internet.
You're right in so far as we should make it clear to attendees that
this is a technical architecture meeting, but we should make it
equally clear that it's not focussed purely on network architecture.
The scope is Technical topics which effect the Architecture of the
Internet within New Zealand. If those Technical topics are Security
based, or Authentication based or etc etc etc, then I'm happy to have
Technical Policy Advisor
+64 21 920 363 (mob)
To promote the Internet's benefits and uses, and protect its potential.
On Wed, Apr 23, 2014 at 8:25 PM, Nathan Ward <nznog(a)daork.net> wrote:
On 16/04/2014, at 7:23 am, Dean Pemberton
InTAC conference to be held again on the 9th of July in Auckland.
The participants at last years conference gave plenty of feedback as to the directions
that they wanted to see the Internet within New Zealand take.
Feedback was that there needed to be more focus on the following areas:
. Technical issues relating to the security of the infrastructure of the New Zealand
. Technical mechanisms to assist in the development of more appropriate Authentication,
Identity and Trust systems relating to the use of the Internet
. Technical ways to ensure the Future-proofing the infrastructure of the New Zealand
What I'm suggesting for InTAC this year is the following structure...
45 Min - On DNSSEC
45 Min - On RPKI
45 Min - On Identity and trust online
45 Min - On Authentication (federated signon, 2fa, lockers)
45 Min - On SDN
45 Min - On UFB
Does anyone have any feedback before I look to secure topic speakers and make it a real
This looks fantastic, as I’m sure you can imagine given my rant after the last one. I
like the exclusion of IPv6 specific talks - lets keep it that way.
Let’s make sure that we are very clear to attendees that this is a technical architecture
meeting. The identity and trust bit somewhat worries me, but, if you stick “from a network
architecture perspective” on the end, or merge it in to the authentication section, then
I’m not sure we can fill 45 mins with RPKI. DNSSEC might be possible to fill 45 mins with
- let’s see.
I think this is a good outline - lets not leave it set in stone of course.