Re: [MEXT] Review of draft-ietf-mext-binding-revocation-03.txt

[Joel Hortelius <joel.hortelius at interpeak.se>]

Resending my questions in brief form;

1; Since some triggers do require specific actions, and the draft uses
the word "currently defined" for trigger definitions indicating new
triggers may be added - how is an implementation supposed to deal with
future triggers that may or may not require specific action?

2; What combinations are possible? What triggers may be used with the
'G' bit? Some triggers have been indicated that they should be used with
'G', but others do not. Some combinations do not make sense. Does 'G'
ONLY work with those explicitly specified? If so, what should one do
with the other combinations if they appear?

3; Since you define your own namespace regarding revocation trigger
message types (BRI, BRA), it would have made sense to me to split the
messages even further and have a Global BRI and Global BRA instead of
the 'G' bit, AND separate the trigger reason values into a global and
per binding trigger namespaces. Mixing global trigger reasons with
per-binding session reason, where the global "namespace" requires
specific actions based on trigger reason quickly gets complex. Having
them separated would remove the most obscure combinations, which are
either meaningless or invalid. 

4; Just remembered that the per-session revocation do require specific
action on some triggers (unknown handoff). Perhaps splitting the trigger
values:
< 128  -"soft" triggers; revoke and log - may use reason for for
undefined action to restore connectivity. This would be
"administrative", "user initiated", etc.
>= 128 -"hard" trigger. If unknown, reply with "unsupported trigger",
otherwise do the actions defined by the trigger. This would be
"per-peer", "node-local", "unknown handoff" etc.

5; What is one supposed to do if both 'G' and 'V' bit are set in a BRI?

6; The partial success on MAG is hazy; When is it supposed to be used?

7; The out of sync BCE state trigger, when is it supposed to be used? I
can't find any reference to it in the doc.

Regards,
Joel Hortelius