EzIP vs. YADA & YATT Re: Ready to compromise? was RE: V6 still not supported

2022-05-05 Thread Abraham Y. Chen
Dear Pascal: Have not heard your follow-up thoughts and comments. It would be much appreciated if we can carry this dialog forward. Regards, Abe (2022-05-05 11:23 EDT) On 2022-04-21 17:38, Abraham Y. Chen wrote: Dear Pascal: 0) Thanks for your clarification. It enabled me to study your

Re: Ready to compromise? was RE: V6 still not supported

2022-04-21 Thread Abraham Y. Chen
Dear Pascal: 0) Thanks for your clarification. It enabled me to study your draft a little closer and came up with the following observations to share. 1)   "Yes, this is plain IP in IP. For a router does not know about YADA, this looks like the most basic form of tunnel you can get.":    

RE: Ready to compromise? was RE: V6 still not supported

2022-04-20 Thread Pascal Thubert (pthubert) via NANOG
Dear Abe: Yes, this is plain IP in IP. For a router does not know about YADA, this looks like the most basic form of tunnel you can get. Which is where the inner/outer terminology comes from. All very classical. We could do an over-UDP variation if people want it. I used a condensed format to

Re: Ready to compromise? was RE: V6 still not supported

2022-04-14 Thread Abraham Y. Chen
Dear Pascal: 1)    I had a quick look at the below updated draft. I presume Figure 2 is intended to address my request. Since each IPv4 address has 4 bytes, what are the 12 bytes allocated for IPv4 header fields (outer) and (inner), each? Aren't they the standard first 12 bytes of packet

Ready to compromise? was RE: V6 still not supported

2022-04-08 Thread Pascal Thubert (pthubert) via NANOG
Dear all Following advice from thus list, I updated the YADA I-Draft (latest is https://www.ietf.org/archive/id/draft-thubert-v6ops-yada-yatt-03.html, more to come soon if feedback is heard) and proposed it to the v6ops WG at the IETF. For memory, the main goal here is to find a compromise as