[v6ops] "Getting IPv6 Private Addressing Right" AusNOG presentation

Mark Smith <markzzzsmith@gmail.com> Tue, 17 September 2019 09:17 UTC

Return-Path: <markzzzsmith@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 775541200EF for <v6ops@ietfa.amsl.com>; Tue, 17 Sep 2019 02:17:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.498
X-Spam-Level:
X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0D5sAWB4ZEfw for <v6ops@ietfa.amsl.com>; Tue, 17 Sep 2019 02:17:47 -0700 (PDT)
Received: from mail-ot1-x32f.google.com (mail-ot1-x32f.google.com [IPv6:2607:f8b0:4864:20::32f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E23321200DE for <v6ops@ietf.org>; Tue, 17 Sep 2019 02:17:46 -0700 (PDT)
Received: by mail-ot1-x32f.google.com with SMTP id 21so2356778otj.11 for <v6ops@ietf.org>; Tue, 17 Sep 2019 02:17:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=ag+WrkbzEsDBSEzER4Z+cOmgFIkkLpIo06nDYr6KqdQ=; b=k/MxOweUbDxdKSikssq8H2gOvWDhge7m4FGL06ZfNoHYgfcLTat9uasJ9v+1J7FC7s mVw2pXpGOkHZapKULnuHOnknq38+dFoa9WEwRsSxeqBs6mpfF3kNLMXOZ4cgnq/Hgsia u6KsFzkuLv20GXTZywi0/3z9WlEIwzuLl2ktq7HKdDGFh7UcmAL0zWRk457x/TG062MW UHykdYB82vbV3RPiyYLJ1dfTpOS/1rvrDNxPLFgd79+PQG/Hbs98gDeJyFVZJYShN4Cw Ncbtq+ceHDwjx7bSw55hpIrDd0CVUepUhygEsslnahnjixHPpvSKawujBf3H7WNiUPdi 1/SQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=ag+WrkbzEsDBSEzER4Z+cOmgFIkkLpIo06nDYr6KqdQ=; b=OWBeQAV8VRePgTxDoaL+5+Y2kseQw0CyMZNcYljV4DJ56tunwyqVDCAdMXqkG520Qg r+xVJYVfb7ED4S1ik+TpNY7ISWXFJZT0SCtWir4YZDgiEXWPGsib14ppcwu+TqH+cOl9 YpgJ09qCTRlsYsiP/H2XOWo4U35sRVpFkfi2jh1C++I0ZhkuAPry3cJToB/WQEtzV+Cm qNTt+1N52nOSTcdp9NSlm3SC6TD7lWYn/eJ0nT97MPb6ZsBOpAfYUsZFvZmeb38+wSEe 2SAVOL5w0q++Vc0eJl3YeeJfIQhftYisLWG9iDcZumuDQAfpFe09jm2GdJ+ReIHjjDuj HCOw==
X-Gm-Message-State: APjAAAVrwfX80ouhuUv4/L+wxkGl+DcRj/TKNt9k2Pu5Zice2oCfeaT9 BXk6/aTB8Mc3TW3G1kEkB3AfftGtr/EmFfW7MVw2h86J
X-Google-Smtp-Source: APXvYqzW24TMVnwVnhDtf6yCPgq3KMn1N3EFhUdtMSM24Kkefu1RX8MAR0DISThasyMDhvzmjmxmp0ZXnSyO/scgmZo=
X-Received: by 2002:a9d:6189:: with SMTP id g9mr1774479otk.348.1568711865918; Tue, 17 Sep 2019 02:17:45 -0700 (PDT)
MIME-Version: 1.0
From: Mark Smith <markzzzsmith@gmail.com>
Date: Tue, 17 Sep 2019 19:17:19 +1000
Message-ID: <CAO42Z2yJWgswT6+RYqunqYX70tg4BY3s3rsBGscvNfi-+uFqcQ@mail.gmail.com>
To: v6ops list <v6ops@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/rw5x5sfEMMBJKu-mZlhR9ozmcLA>
Subject: [v6ops] "Getting IPv6 Private Addressing Right" AusNOG presentation
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Sep 2019 09:17:48 -0000

Hi,

I've noticed on a number of occasions now over a number of years that
some people are treating the ULA address space as though it is an
exact duplicate of RFC 1918, and not including a unique Global ID -
typically using all zeros for that part.

So I recently prepared and presented at the AusNOG conference on
"Getting IPv6 Private Addressing" right. My goal wasn't just to
present there, but to also have a slide deck available that describes
exactly why we went away from Site-Locals and why globally unique ULA
prefixes are required.

Feel free to share as widely as possible!

On Slideshare:

https://www.slideshare.net/MarkSmith214/ausnog-2019-getting-ipv6-private-addressing-right

PDF:

http://www.users.on.net/~markachy/AusNOG%202019%20-%20Getting%20IPv6%20Private%20Addressing%20Right.pdf

Regards,
Mark.