I was asked to perform a sublimental opsdir review of
draft-ietf-anima-grasp
https://datatracker.ietf.org/doc/draft-ietf-anima-grasp/
My conclusion after reading is that the document is ready with some
fairly serious caveats.
caveat 1 - Transport is fiddly. The document allows for the use of UDP
but is probably insufficiently specified to allow for reliable and
inter-operable operation. Use of tcp and therefore some assumption about
reliable transport go a long way towards ameliorating the concern.
caveat 2 - multicast / flooding is messy. The document is proscriptive
with respect to the sorts of information which can safely be carried via
multicast. but the desire to statelessly flood messages and the tendancy
for leakage probably encourage unsafe usage when the unicast (and
secured) transport is already required. multicast should probably be
limited exclusively to discovery and initial bootstrap.
I don't know if these considerations are important enough to be
blocking. considering the relative maturity of demonstrated
implementations, I would expect that developer's implementations would
be confined to what they need. marking it experimental might encourage a
future specification to be tighten up to what is in fact used.
joel