> If the Flags field contains any flags, then the resulting parser state > will be different for original and source-specific implementations. This > will break interoperability.
Yes, there is a problem with the compression mechanism for the destination prefix. The solutions are: - no compression, - consider that updates will not know the extension: either - announce all ss-updates at the end of the message, or - systematically resend the destination prefix when it has been updated by an ss-update, - define another destination compressed prefix. Currently, the solution 2 is implemented, but ss-updates are not regrouped at the end of the message. > Rather than setting up complex rules to avoid the issue, I suggest we dump > the Flags field from SS-Updates. We can either remove the field, or mark > it as reserved. I suggest we remove it and be done with that. While choosing an extremist solution, I would prefer the third one. Matthieu _______________________________________________ Babel-users mailing list Babel-users@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users