Re: [Roll] I-D Action: draft-ietf-roll-nsa-extension-02.txt

[<[e-mail]>]

Hello Pascal,

Here is the point being discussed. (see the surrounding text at https://tools.ietf.org/html/draft-ietf-roll-nsa-extension-03#section-4.2)


  *   Section 4.2: "Therefore, the PS IPv6 address(es) field SHOULD be compressed using the compression method for Source Routing Header 6LoRH (SRH-6LoRH)". I understand that a similar compression mechanism could be used. However, this requires defining a protocol element that does not exist today, unless I missed something. Therefore, the normative SHOULD is irrelevant. I guess this section is merely suggesting future work.
We do have this almost fully implemented (almost: only works in single root RPL instances).
Would it make sense to spell out the exact specification of the compression even if it is largely a copy of the SRH-6LoRH compression method?
I can lowercase the SHOULD, but using this kind of compression really makes big difference in practice.

[DB] talk to Pascal about this, he looks pretty knowledgeable in SHOULDs. Anyway, if you capitalise SHOULD, then you have to explain the consequences of not following the recommendation. Whereas if you lowercase it, it's only free advice. You can stil explain why you think it is a good idea. My worry is that a capitalised SHOULD here will stop the draft later in the IESG processing because you are referring to a non-existent specification (formally speaking). Again, ask Pascal, I totally trust him on this question.


Best regards
Dominique

_________________________________________________________________________________________________________________________

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.