[rohc] Empty CSRC list issue in IR packet.

Hi,

A couple of weeks ago, there was a discussion about a section in the latest
implementer's guide that corrects RFC 3095 with regards to the handling of
empty CSRC lists: section 5.7.7.6 of the RFC says that an empty generic list
is inserted, while section 4.3.3. of the implementer's guide modifies the
RFC by saying that no generic list should be present.

There seemed to be a concensus among those involved in the discussion to
follow the RFC since this is how interoperability was tested.  That's fine
and I do not want to restart the discussion on this.

Now, it has been a couple of weeks and there hasn't been any final
conclusion on this issue (i.e. officially stating that the RFC method should
be used, anouncing the associated correction to the implementer's guide,
etc...).  

Based on the concensus that existed, I don't think there's a problem for
those who currently receive mailing list messages.  However, it seems to me
like there's a risk that future implementations may use either methods,
leading to interoperability problems.

Thanks,
Remi.

_______________________________________________
Rohc mailing list
Rohc@ietf.org
https://www1.ietf.org/mailman/listinfo/rohc