Haoyu Song <[email protected]> wrote: > Title: Short Hierarchical IP Addresses at Edge Networks https://datatracker.ietf.org/doc/draft-song-ship-edge/. > Abstract: To mitigate the IPv6 header overhead in edge networks, this draft > proposes to use short hierarchical addresses excluding the network > prefix within edge networks. An edge network can be further > organized into a hierarchical architecture containing one or more > levels of networks. The border routers for each hierarchical level > are responsible for address augmenting and pruning. Specifically, > the top-level border routers convert the internal IP header to and > from the standard IPv6 header. This draft presents an incrementally > deployable scheme allowing packet header to be effectively compressed > in edge networks without affecting the network interoperability. > Presenter: Haoyu Song > Purpose: gain awareness and interests from the WG, collect feedback and > suggestions for the next step
Interesting. I browsed the document quickly. I'm not sure I understand how it is "orthogonal" to RFC6282. It seems to be an alternative. If it was orthogonal, then it would work on a different basis vector, and I could use both at the same time. It seems like you are doing a static compression scheme by re-encoding the IPv6 header to a new format. I hope to see some table explaining the size of your header compared to RFC6282. Since you have assumed some kind of hierarchal network, would you use RFC6550 for routing, or is it that you don't need any routing due to your architecture? -- Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ 6lo mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lo
