[Babel-users] Source-sensitive packet's format

[Juliusz Chroboczek]

> SS Update
> 0                   1                   2                   3
> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |   Type = 13   |    Length     |      AE       |     Flags     |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |      Plen     |    Omitted    |            Interval           |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |             Seqno             |             Metric            |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |        Prefix...
> +-+-+-+-+-+-+-+-+-+-+-+-
> |    Src Plen   |  Src Omitted  |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |        Source prefix...
> +-+-+-+-+-+-+-+-+-+-+-+-

Okay, there's a problem with that.  I think you mentioned it to me, but
I didn't listen.

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.

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.

-- Juliusz