Hi authors, The idea of a shim layer to provide the generic delivery function is interesting. I have 3 questions for clarification.
1. The draft request a new number of Internet Protocol Number registry for GDFH, I assume in this case, GDFH is used together with IP header. I wonder what the benefit is to have this generic header other than directly specifying the functionality as the next header? 2. If the GDFH is used with MPLS, what is the difference compared to G-ACh? 3. If you suggest to use one uniform encapsulation in Figure 2 for IP/MPLS/BIER, starting with 0000 would make sense when it is encapsulated in MPLS, but seems unnecessary in IP. Because in IP, usually 5-tuple is used for hashing algorithm. First 4 zeroes don't help to avoid the hashing problem. Best regards, Fan -----邮件原件----- 发件人: mpls [mailto:[email protected]] 代表 Jeffrey (Zhaohui) Zhang 发送时间: 2021年1月12日 22:27 收件人: [email protected]; mpls <[email protected]>; [email protected] 抄送: Kireeti Kompella <[email protected]>; Ron Bonica <[email protected]> 主题: [mpls] draft-zzhang-intarea-generic-delivery-functions Hi, I just posted https://datatracker.ietf.org/doc/draft-zzhang-intarea-generic-delivery-functions/. The initial version was posted to the tsvwg (https://tools.ietf.org/html/draft-zzhang-tsvwg-generic-transport-functions-00). After discussions/feedback we are re-homing it to intarea wg. This new version also contains quite some changes based on the comments and feedback that we received (special thanks to Stewart). Comments and suggestions are appreciated. Thanks. Jeffrey Juniper Business Use Only _______________________________________________ mpls mailing list [email protected] https://www.ietf.org/mailman/listinfo/mpls _______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
