Hi Bruno, Many thanks for your readthrough. 1, DetNet uses three toolsets (i) Resource allocation, (ii) Service protection, and (iii) Explicit routes. ECMP is not allowed within DetNet. As You wrote, a single forwarding path can be used through an SR-Policy.
2, Yes, we are open regarding names, they can follow the naming convention. Adding a "D" is OK, also finding a shorter name may have some advantages. Thanks & Cheers Bala'zs -----Original Message----- From: bruno.decra...@orange.com <bruno.decra...@orange.com> Sent: Tuesday, July 23, 2024 5:53 PM To: draft-varga-spring-preof-...@ietf.org Cc: SPRING WG <spring@ietf.org> Subject: draft-varga-spring-preof-sid [speaking as individual contributor] Hi authors, I've quickly read your draft. In the interest of saving meeting time, please find below two comments. 1) You are adding the packet sequence number in the IPv6 destination address. As consequence, in case of load balancing, packets from the same flow may have their order changed by IPv6 routers. Is this an issue of may be you don't care since DetNet re-ordering will take care of this? Or may be you are mandating a single forwarding path through an SR-Policy? Would increased packet de-ordering increase the DETNET re-ordering cost (e.g., extra delay, jitter, high bandwidth memory...)? If so (*2) you may consider discussing this in the draft. 2) End.PREOF performs SRv6 decapsulation. So far in SRv6 there seem to be a convention from [1] to use the letter "D" in the name of the behavior to indicate that decapsulation is performed. Perhaps you could consider using this soft convention. (e.g., :s/ End.PREOF/ End.DPREOF ) [1] https://datatracker.ietf.org/doc/html/rfc8986 Thanks, Regards, --Bruno ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ spring mailing list -- spring@ietf.org To unsubscribe send an email to spring-le...@ietf.org