Dear All, Last week I submitted 2 I-D on Intarea WG under the topic of a flexible IP address structure. I'd like to share the key points of these 2 I-D before it could be discussed at IETF 109.
First, we see that increasingly networks expect a direct TCP/IP stack for its global reachability and facility. However, various scenarios naturally face challenges when adopting current IP protocol. As one example, satellite networks introduce routing oscillation due to topology dynamics, leading to low routing efficiency even though it is theoretically possible. The first I-D describe these well-recognized scenarios that prefer a "flexible" IP address structure. By "flexible" in this I-D, we mean that the IP address is constructed as multi-semantics and length variable. Based on scenarios and the correlated requirements, the second draft describe an instance of a potential "flexible" IP address structure, i.e., FlexIP, and details the considerations behind the design. To still benefit from global reachability, FlexIP is expected to work only in limited domain (RFC8799) and be interoperable with IPv6. The main purpose of FlexIP design is to construct a flexible network address, and such address should be prospective enough to accommodate unforeseeable scenarios and futuristic requirements. Attached below are 2 I-D that mentioned in this email. I would be happy if you have any questions on this topic. Warmly welcome! ---------------- Draft 1: Scenarios for Flexible Address Structure https://datatracker.ietf.org/doc/draft-jia-scenarios-flexible-address-structure/ Draft 2: Flexible IP: An Adaptable IP Address Structure https://datatracker.ietf.org/doc/draft-jia-flex-ip-address-structure/ Thanks, Yihao Jia.
_______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
