Re: [PATCH v2 1/1] Documentation: networking: document ISO 15765-2:2016

Oliver Hartkopp
2024-04-16T17:19:30Z

Hi Francesco and Vincent,

On 16.04.24 18:42, Francesco Valla wrote:
> On Sun, Apr 14, 2024 at 10:21:33PM +0200, Oliver Hartkopp wrote:
>> On 14.04.24 06:03, Vincent Mailhol wrote:

>>> Regardless, here is a verbatim extract from the Foreworld section of
>>> ISO 15765-2:2024
>>>
>>> This fourth edition cancels and replaces the third edition (ISO
>>> 15765-2:2016), which has been technically revised.
>>>
>>> The main changes are as follows:
>>>
>>> - restructured the document to achieve compatibility with OSI
>>> 7-layers model;
>>>
>>> - introduced T_Data abstract service primitive interface to
>>> achieve compatibility with ISO 14229-2;
>>>
>>> - moved all transport layer protocol-related information to Clause 9;
>>>
>>> - clarification and editorial corrections
>>>
>>
>> Yes, I've checked the release notes on the ISO website too.
>> This really looks like editorial stuff that has nothing to do with the data
>> protocol and its segmentation.
>>
>
> The :2016 suffix is cited both here and inside the Kconfig. We can:
> - keep the :2016 here and then update both the documentation and the
> Kconfig once the standard has been checked
> - move to :2024 both here and inside the Kconfig
> - drop the :2016 from everywhere (leaving only ISO 15765) and move to
> ISO 15765:2024 only inside the "Specifications used" paragraph
>
> What do you think? Shall the modifications to the Kconfig be done as part of
> this series?

So here is my completely new view on this version topic ... ;-D

I would vote for ISO 15765-2:2016 in all places.

The ISO 15765-2:2016 is the first ISO 15765-2 standard which supports
CAN FD and ISO 15765-2:2024 does not bring any functional change neither
to the standard nor to the implementation in the Linux kernel.

For that reason ISO 15765-2:2016 is still correct and relevant (due to
the CAN FD support) and does not confuse the users whether the 2024
version has some completely new feature or is potentially incompatible
to the 2016 version.

Best regards,
Oliver