Re: [v6ops] draft-yu-v6ops-split6 question

[hsyu <[e-mail]>]

Dear Brian

         My idea is not to fix the route without changing, long CIDR can ensure that the route is more accurate, so it can be routed to the destination faster, which is very necessary. But considering the bottleneck of the routing device and the speed of finding routes, the aggregation of routes is necessary. We know that the number of routing entries is positively related to the number of networks. The more networks there are, the more routes there must be. What we expect is that network changes that occur in a short period of time (such as a month) do not affect changes in the number of networks and changes in the number of routing tables. This is the most fundamental reason for me to consider doing this draft.

         Best regards.

https://maas.mail.163.com/dashi-web-extend/html/proSignature.html?ftlId=1&name=Haisheng+Yu%28Johnson%29&uid=hsyu%40cfiec.net&iconUrl=https%3A%2F%2Fmail-online.nosdn.127.net%2Fsm50a1433bca9fb284d4265d35e9ed54d3.jpg&items=%5B%22%22%2C%22hsyu%40cfiec.net%22%2C%22%22%2C%22%22%2C%22%22%5D" rel="nofollow">

https://mail-online.nosdn.127.net/sm50a1433bca9fb284d4265d35e9ed54d3.jpg">	Haisheng Yu(Johnson)
[e-mail]

On 3/24/2022 10:17，Brian E Carpenter<[e-mail]> wrote：

We've had this discussion before, I thought.

https://datatracker.ietf.org/doc/html/draft-bourbaki-6man-classless-ipv6 makes the opposite argument. It wasn't strictly speaking necessary to make the argument at all, because BCP 198 (RFC 7608) settled the question.

Brian
On 21-Mar-22 22:23, Gert Doering wrote:

Hi,

On Mon, Mar 21, 2022 at 04:42:55PM +0800, hsyu wrote:

</span></div><div><span><br></span></div><div><span>I think with the development of IPv6, the location and separation of IPv6 addresses is an issue worth discussing, such as:<br>By separating location and identity, a robust routing table can be achieved, reducing the risk of route explosion.<br>Let the routing address work in the routing space, and let the identity domain work in the identity space. Ensure easier routing and easier and more accurate authentication.</span></div>

While this sounds really nice, I have a hard time understanding how
this would be achieved.

Mandate aggregation of routes?  To what level?

Disallow IPv6 PI space?

How would DNS look like, how would "small enterprise" multihoming look like?

Gert Doering
-- NetMaster

_______________________________________________
v6ops mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/v6ops