Hi all,
I've done my AD review of this - comments are below.
I'm ok to start IETF LC on this now and you can handle
my comments as IETF LC comments, or if you prefer you
can spin another version (once submissions re-open) to
handle them now. I'll wait for the chairs to let me
know whether to start IETF LC or set this to revised
ID needed.
Thanks,
S.
1. In general there are a number of times where this document
seems to be wishful thinking. I think it'd be better if you
reduced it to the more concrete use-cases where implementation is
actually planned and where you can be more authoritative about
how abfab will be beneficial. Sections 3.5 and 3.9 in particular
seem weak to me and the document might be better if they were
deleted - would you really miss them?
2. ID nits says:
-- Obsolete informational reference (is this intentional?): RFC
2060 (Obsoleted by RFC 3501)
-- Obsolete informational reference (is this intentional?): RFC
2821 (Obsoleted by RFC 5321)
-- No information found for draft-freeman-plasma-requirements -
is the name correct?
Looks like these should be updated as noted in the writeup.
3. Please expand CRM on 1st use
4. Maybe move the reference to SSH to the end of 3.1, from the
start of 3.2, or ideally provide a reference to an "abfab-enabled
SSH" if you have one. (And say "secure shell (SSH)" on 1st use.)
5. 2nd last para of 3.3 could do with some references really.
6. The argument in 3.3 that grid admin complexity is really due
to X.509 seems weak to me. I'd expect you to get comments about
that. And replacing the entire VO thing would be a large task.
It'd be better if you had a very specific use-case here I think
rather than being so general.
7. Its not clear to me how abfab helps in 3.5 - I think you'd
maybe need to say some more about how that'd work.
8. 3.9: is it "smart object" or "smart device" just using one
marketing term would be better (zero even moreso;-)
9. 3.9 seems quite far-fetched to me. Do you really expect
sensors to use gss-eap?
_______________________________________________
abfab mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/abfab
