Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming

[Sander Steffann <[e-mail]>]

Hi,

> I believe the /20 example was what Softbank seems to be using for their (very large?) network and use-cases. It’s an example of how much IPv6 space they’ve got from ARIN. A millionth of that for SRv6 indicates a /40 (if I’ve got my maths right). Now, I don’t claim to be aware of Softbank’s current and future use-cases. I don’t think it is a topic for discussion on an IETF mailing list.

I disagree. I think the RFCs that the IETF produces should be deployable in the real world, and where that requires changes at other organisations in the internet ecosystem like the RIRs and their communities that requires cooperation, communication and consideration. The IETF does not exist in a vacuum.

To help start the discussion and awareness, I just made a list of all the IPv6 current assignment and allocation sizes in the RIPE NCC service region:

/19:     3
/20:     2
/21:     2
/22:     2
/23:     5
/24:     5
/25:     5
/26:     8
/27:    11
/28:     7
/29: 11614
/30:   107
/31:    54
/32:  6346
/40:     1
/42:     1
/43:     1
/44:     2
/45:     7
/46:    17
/47:    39
/48:  2998

This is the operational context that these standards exist in. If anything needs to be changed that will need cooperation with the RIR communities at the least.

Cheers,
Sander

Source:
wget ftp://ftp.ripe.net/pub/stats/ripencc/delegated-ripencc-extended-latest
grep ipv6 delegated-ripencc-extended-latest | grep -E 'allocated|assigned' | cut -d '|' -f 5 | sort -n | uniq -c