Owen DeLong wrote:
It is the first step to have the RSIP style transparent Internet.
The second step is to use port numbers for routing within ISPs. But, it is not necessary today.
Still doesn't scale. 40 bits isn't enough to uniquely identify a conversation end-point.
It's 48 bit.
If you use port numbers for routing, you don't have enough port numbers for conversation IDs.
That you use IPv4 addresses for routing does not make it unusable for identifications. Moreover, it is easy to have a transport protocol with 32bit or 48bit port numbers with the end to end fashion only by modifying end part of the Internet.
Unlike IPv4 with natural boundary of /24, routing table explosion of IPv6 is a serious scalability problem.
Solvable.
It was solvable.
IPv6 has enough bits that we can use map/encap or other various forms of herarchical overlay ASN-based routing to resolve those issues over time.
The reality is that situation has been worsening over time. As RFC2374 was obsoleted long ago, it is now impossible to restore it. Masataka Ohta