Re: [Roll] text for MOPEX

[Pascal Thubert <[e-mail]>]

Hello Dominique,


If the MOP is in the existing values 0.. 6, then it takes only one of 
the values 0..6 in MOPext to signal v2. e.g., MOPex value of 0 would 
mean v1 (current), and a value of 1 would mean rev1 etc...

The way we're handling it today opens for inconsistency between mop and 
mopex (e.g., one is 2 and the other is 1), and seems like a waste of 
room in mopex.


just a thought;

Pascal


Le 30/03/2024 à 08:05, [e-mail] a écrit :
>
> Hi all,
>
>
> Long overdue, I just submitted a pull request to the GitHub MOPEX 
> draft repo, adding custom names for the values 0-4 of MOPEX and 
> referring to [this document], instead of pointing at RFC 6550.
>
> As discussed during our recent interim meetings, these names hint at 
> the MOP of same values, but do not consist in a specification that we 
> are unable to write at the present time.
>
> See copy of ASCII rendition below.
>
> Best regards
>
>
> Dominique
>
>
>
>      +=============+================================+=================+
>      | MOPex Value |          Description           |    Reference    |
>      +=============+================================+=================+
>      |      0      |     RESERVED_NoDownward_v2     | [this document] |
>      +-------------+--------------------------------+-----------------+
>      |      1      |     RESERVED_NonStoring_v2     | [this document] |
>      +-------------+--------------------------------+-----------------+
>      |      2      | RESERVED_StoringNoMulticast_v2 | [this document] |
>      +-------------+--------------------------------+-----------------+
>      |      3      |  RESERVED_StoringMulticast_v2  | [this document] |
>      +-------------+--------------------------------+-----------------+
>      |      4      |        RESERVED_P2P_v2         | [this document] |
>      +-------------+--------------------------------+-----------------+
>
>                      Table 4: Registry for MOPex values
>
> ____________________________________________________________________________________________________________
> 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.