Hi Steve, all, Steven Newhouse wrote:
Michel,
No problem with the security credentials change. The notion of a 'my' personalized DEPR seems good. The ability to pass the DEPR add would make sense to me... for the use case where you want a colleague to look at your file. You can pass them a DEPR to reference the location, provide a credential to access it, so they can even drop it into their DMI transfer. This would mean that the DEPR would have value to an attacker and would have to be looked after...
Yes. This would require the spec to a) change syntactically as I proposed b) add those use cases (yours and mine) as non-normative text somehow c) Add a section on DEPRs being personalised and implications when a DEPR has been eavesdropped, to the security section
Do you want to alter the current draft for this change if no objections are raised?
Sure - I will wait until Monday to take the write pen on the document to give people time to object.
On the author list addition... should have asked... bad of me [SLAP TO HAND].
I am certainly fine with having you on the author list - should've done long before already.
The GFSG author list 'limit' has sort of gone away... just look at the BES list - seven I think! It did provoke some GFSG discussion which reached a conclusion of no conclusive limit... just 'as long as it makes sense'.
Yes, I remember the BES group being the trigger of this discussion, but I obviously missed the conclusion of non-conclusitivity *fg*
If we have the security stuff sorted... is that it at the moment. Have you been able to resolve the Base Faults issue?
I think that's it really except the security section. WRT the BaseFaults, I sent a mail earlier to the Mailing List today. Cheers, Michel