Re: Spin bit decision

[<[e-mail]>]

On 10/02/18 14:55, Lars Eggert wrote:
> Hi,
> 
> again, as an individual:
> 
> On 2018-10-2, at 15:41, <[e-mail]> <[e-mail]> wrote:
>> Well, if the spec says that en endpoint MUST copy of flip a bit, an implementor would be fairly ill-advised not do comply.
> 
> sure, it may be "ill-advised", but in practice, it won't affect interop at all.
> 
>> And nothing prevents from adding a "does it spin ?" criterion to the interop test suite.
> 
> We can certainly consider this - it may give us some data about the current capabilities and configurations of the participating stacks.

More than that: you seem to be implying that automated interop testing outweighs 
textual specification. No problem with that; let's focus on test definition then.

>> Clearly you now have this degree of freedom: weaken that MUST into a MAY or a SHOULD, separately for each role. But for what purpose ?
> 
> The point I'm trying to make is that it in practice doesn't matter if the spec says "MUST", "SHOULD" or "MAY", since it doesn't affect interop, and doesn't affect performance. Essentially, each stack can decide in isolation whether to spin, echo, do nothing, grease the bits, etc., no matter what language we put in the spec.

Sure. So, what is there to lose by saying "MUST" anyway ?


_________________________________________________________________________________________________________________________

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.