This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ipv6-wg] Disband IPv6 WG
- Previous message (by thread): [ipv6-wg] Disband IPv6 WG
- Next message (by thread): [ipv6-wg] Disband IPv6 WG
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Riccardo Gori
rgori at wirem.net
Fri Oct 4 07:24:14 CEST 2019
Hello Jen Link, Il 03/10/2019 13:55, Jens Link ha scritto: > Uros Gaber <uros at ub330.net> writes: > >> 1. WHY should it have NAT > NATs are good. They provide security. Are you sure you are about networking? > >> 2. What do you understand under class, IPv4 "Classes" are just defined >> subnet groups (simply put) > Things need names. Numbers are hard to remember. We have Class-A for /8, > Class-B for /16 and Class-C for /24. We need names for the others as > well. > >> 3. AFAIK DHCPv6 is defined in RFC (3319,3646,4704,5007,6221,6355,6939,8415) > But it's DHCPv6. Not DHCP! It works differently. And Android does not > support it. Enterprise Customers want DHCP! > >> 6. Dots and colon, what's the difference? > I have do change my regex. > >> 7. Use DNS to resolve - no [] needed then. > DNS is to hard, to complex and fails to often. And in enterprise > networks it probably done by another team. > >> [5] what does the script have to do with network layer? > The script was just an example for software breaking when you implement > something that looks completely different like IPv4. I this case the > script is parsing log files and netflow data and we are back to the > regex. > > Jens __ Riccardo
- Previous message (by thread): [ipv6-wg] Disband IPv6 WG
- Next message (by thread): [ipv6-wg] Disband IPv6 WG
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]