Deploy360 18 March 2018

IETF 101, Day 1: Would You IPv6 It?

By Kevin MeynellFormer Senior Manager, Technical and Operational Engagement

It’s another packed week at IETF 101 in London, and we’re bringing you daily blog posts highlighting the topics of interest to us in the ISOC Internet Technology Team. Monday is a very full day with two important IPv6 working groups, one on IoT, a couple on routing, and another couple related to crypto.

The week begins bright and early at 09.00 GMT/UTC with V6OPS, although it has a relatively light agenda with a discussion on implementing IPv6-preferred data centres to start the meeting, and 7 drafts on which comments are being requested.

The couple of new drafts are Requirements for IPv6 Routers that defines a set of recommendations for routers, switches, and middleboxes deployed in IPv6 networks; and Using Conditional Router Advertisements for Enterprise Multihoming that proposes a solution to the problem of enterprise multihoming without address translation by using Router Advertisements to influence the host source address.

The five existing drafts up for discussion are NAT64 Deployment Guidelines in Operator and Enterprise Networks; IPv6 Point-to-Point Links; Transition Requirements for IPv6 Customer Edge Routers to support IPv4; IPv6 Performance Measurement with Alternate Marking Method; and IP Fragmentation Considered Fragile.

NOTE: If you are unable to attend IETF 101 in person, there are multiple ways to participate remotely.

IPWAVE is running in parallel with V6OPS. It’s focusing on a couple of working group-sponsored drafts including a specification for transmitting IPv6 Packets over IEEE 802.11 Networks in Vehicle-to-Internet and Vehicle-to-Infrastructure communications; and defining the use cases for IP-based vehicular networks, but will also be discussing re-chartering.

6MAN meets straight after lunch at 13.30 GMT/UTC. This has 7 drafts up for discussion, as well as an update on multi-vendor interoperability testing results.

The new drafts are Privacy Extensions for Stateless Address Autoconfiguration in IPv6 that describes an extension that causes nodes to generate global scope addresses from interface identifiers that change over time; Recommendation on Temporary IPv6 Interface Identifiers specifies a set of requirements for generating temporary addresses and clarifies the stability requirements for IPv6 addresses; whilst Unified Identifier in IPv6 Segment Routing Networks extends the use of IPv6 Segment Routing Headers to segment identifiers encoded as MPLS labels and IPv4 addresses.

The other drafts include IPv6 Node Requirements; IPv6 Segment Routing Header; ICMPv6 errors for discarding packets due to processing limits; and IPv6 Router Advertisement IPv4 Unavailable Flag aims to update RFC 5175.

Following the afternoon break, there’s a choice between IDR or the Crypto Forum starting at 15.50 GMT/UTC.

IDR will be discussing a working group sponsored draft addressing the problem of route leaks – Methods for Detection and Mitigation of BGP Route Leaks – along with drafts on BGP Link State Extensions for IPv6 Segment Routing; and BGP Signaling of IPv6-Segment-Routing-based VPN Networks. There are also drafts on BGP-LS Extension for Inter-AS Topology Retrieval Under Different Scenario; BGP Extended Community for Identifying the Target Node; and BGP Link-State Extensions for BGP-only Fabric.

The Crypto Forum has yet to publish an agenda, but have recently been discussing drafts on the Transition from Classical to Post-Quantum Cryptography, Re-keying Mechanisms for Symmetric Keys, SPAKE2 (a secure, efficient password based key exchange protocol); Augmented Password-Authenticated Key Exchange (AugPAKE); Verifiable Random Functions (VRFs); The memory-hard Argon2 password hash and proof-of-work function; Hash-based Signatures; XMSS: Extended Hash-Based Signatures; and AES-GCM-SIV: Nonce Misuse-Resistant Authenticated Encryption.

In the evening session starting at 17.40 GMT/UTC, there’s a choice of TLS, DHC or GROW.

This is the first TLS session of the week, and the important TLS 1.3 agenda items will be covered during the Wednesday session. This session will discuss drafts on TLS Options for Negotiation of Visibility in Datacenters and Record Header Extensions for (D)TLS; and there will also be a discussion on TLS-SRP that a set of cryptographic protocols that provide secure communication based on passwords.

DHC has three IPv6-related drafts on its agenda, including DHCPv4 over DHCPv6 Source Address Option; YANG Data Model for DHCPv6 Configuration; and Link Layer Addresses Assignment Mechanism for DHCPv6.

Finally, GROW has an interesting agenda item relating to IRR vs RPKI parity regarding AS-SETs.

For more background, please read the Rough Guide to IETF 101 from Olaf, Dan, Andrei, Steve, Karen and myself.

Relevant Working Groups

IPv6 Operations (v6ops) – Viscount @ 09.30-12.00 GMT/UTC
IP Wireless Access in Vehicular Environments (ipwave) – Sandringham @ 09.30-12.00 GMT/UTC
IPv6 Maintenance (6man) – Viscount @ 13.30-15.30 GMT/UTC
Inter-Domain Routing (idr) – Buckingham @ 15.50-17.20 GMT/UTC
Crypto Forum (cfrg) – Balmoral @ 15.50-17.20 GMT/UTC
Transport Layer Security (tls) – Balmoral @ 17.40-18.40 GMT/UTC
Dynamic Host Configuration (dhc) – Viscount @ 17.40-18.40 GMT/UTC
Global Routing Operations (grow) – Blenheim @ 17.40-18.40 GMT/UTC

Deploy360, Encryption, IETF, Internet of Things (IoT), IPv6, Open Internet Standards, Securing Border Gateway Protocol (BGP), Transport Layer Security (TLS), Europe,

Disclaimer: Viewpoints expressed in this post are those of the author and may or may not reflect official Internet Society positions.

IETF 101, Day 1: Would You IPv6 It?

Relevant Working Groups

Recent Posts

Related Posts

DNS Privacy Frequently Asked Questions (FAQ)

Introduction to DNS Privacy

IPv6 Security for IPv4 Engineers