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/address-policy-wg@ripe.net/
[address-policy-wg] R: 2017-03 New Policy Proposal (Reducing Initial IPv4 Allocation, aiming to preserve a minimum of IPv4 space)
- Previous message (by thread): [address-policy-wg] R: 2017-03 New Policy Proposal (Reducing Initial IPv4 Allocation, aiming to preserve a minimum of IPv4 space)
- Next message (by thread): [address-policy-wg] R: 2017-03 New Policy Proposal (Reducing Initial IPv4 Allocation, aiming to preserve a minimum of IPv4 space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tim Chown
tjc at ecs.soton.ac.uk
Fri Sep 22 12:22:16 CEST 2017
> On 22 Sep 2017, at 11:11, Daniel Suchy <danny at danysek.cz> wrote: > > <snip> > > Even standardisation of IPv6 was quite slow in some details - we had to > wait 18 years for RFC 8200... But that rally wasn’t a major change in any way from RFC2460, modulo the few errata that had already been applied over the years. The point of RFC 8200 was to move the core IPv6 spec to full Internet Standard status, which actually very few RFCs have. Tim
- Previous message (by thread): [address-policy-wg] R: 2017-03 New Policy Proposal (Reducing Initial IPv4 Allocation, aiming to preserve a minimum of IPv4 space)
- Next message (by thread): [address-policy-wg] R: 2017-03 New Policy Proposal (Reducing Initial IPv4 Allocation, aiming to preserve a minimum of IPv4 space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]