-
Notifications
You must be signed in to change notification settings - Fork 7
/
draft-momoka-v6ops-ipv6-only-resolver-ops.html
109 lines (89 loc) · 3.38 KB
/
draft-momoka-v6ops-ipv6-only-resolver-ops.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
<!DOCTYPE html>
<html>
<head>
<title>IETF Hackathon - [Project Name] </title>
<meta charset="utf-8">
<style>
@import url(https://fonts.googleapis.com/css?family=Yanone+Kaffeesatz);
@import url(https://fonts.googleapis.com/css?family=Droid+Serif:400,700,400italic);
@import url(https://fonts.googleapis.com/css?family=Ubuntu+Mono:400,700,400italic);
div.left-column { width: 49%; float: left; }
div.right-column { width: 49%; float: right; }
div.right-column ~ p { clear: both; }
div.right-column ~ ul { clear: both; }
div.my-footer {
border-top: 1px solid #ccc;
font-size: 10pt;
text-align: center;
position: fixed;
bottom: 0px;
left: 0px;
height: 30px;
width: 100%;
}
div.my-footer p {
margin-top: 10px;
height: 30px;
}
body { font-family: 'Droid Serif'; }
h1, h2, h3 {
font-family: 'Yanone Kaffeesatz';
font-weight: normal;
}
.remark-code, .remark-inline-code { font-family: 'Ubuntu Mono'; }
</style>
</head>
<body>
<textarea id="source">
class: center, middle
# IETF Hackathon
IETF 118
4-5 November 2023
Prague
---
# Hackathon Plan
Plan:
- Setup some anycast Unbound instances running 1.18.0 supporting draft-momoka-v6ops-ipv6-only-resolver-02
- Figure out whether "prefer-ip6: yes" should be set
<div class="my-footer"><p>IETF Hackathon - 2a06:d1c7:: </p></div>
---
# What got done: 2a06:d1c7::
- There now is a public v6 only resolver at 2a06:d1c7:: (with somewhat reasonable rate limits) using a NAT64 pool of 8 addr/host
- We tested replaying some dual-stack zones, and noticed the implementation indeed needs prefer-ip6: yes to not use NAT64 for some DS hosts
- Looking forward to some evaluation traffic if somebody feels like it; Service will likely remain in place for some time
- We need to take a look at NAT64 port exhaustion for resolvers, as port-reuse is not easy with NAT64
<div class="my-footer"><p>IETF Hackathon - 2a06:d1c7:: </p></div>
---
# Using 2a06:d1c7::
<code>
% dig @2a06:d1c7:: A tudelft.nl</br>
</br>
; <<>> DiG 9.16.42 <<>> @2a06:d1c7:: A tudelft.nl</br>
; (1 server found)</br>
;; global options: +cmd</br>
;; Got answer:</br>
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8731</br>
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1</br>
</br>
;; OPT PSEUDOSECTION:</br>
; EDNS: version: 0, flags:; udp: 1232</br>
;; QUESTION SECTION:</br>
;tudelft.nl. IN A</br>
</br>
;; ANSWER SECTION:</br>
tudelft.nl. 600 IN A 130.161.128.82</br>
</br>
;; Query time: 33 msec</br>
;; SERVER: 2a06:d1c7::#53(2a06:d1c7::)</br>
;; WHEN: Sun Nov 05 10:00:13 CET 2023</br>
;; MSG SIZE rcvd: 55</br>
</code>
<div class="my-footer"><p>IETF Hackathon - 2a06:d1c7:: </p></div>
</textarea>
<script src="https://remarkjs.com/downloads/remark-latest.min.js">
</script>
<script>
var slideshow = remark.create();
</script>
</body>
</html>