[SPKM] Interoperability

Hi.

I think one of the most important outcomes of the BOF is likely to be
an understanding of what level of interoperability is required between
the existing SPKM RFC and our solution to the NFS V4 problem and what
pressures there are to minimize change to the spec.

First, if we break interoperability, we're changing the OID.  If we're
not sure we're maintaining interoperability we're changing the OID.
RPC supports a mechanism for advertizing GSS mechanisms and so the
cost of changing the OID is relatively low.  Servers and clients that
want to implement both mechanisms can do so.

Here are some questions to think about:

* What deployed production code is out there that either interoperates
  with the RFC or draft-adamson?

* Can we meet our security and other requirements without making
  backward incompatible changes and forcing an OID change?

* Going forward, can we obtain a simpler spec or implementation by
  making non-backward compatible changes?

* When will we get a spec out?  How long will the market wait?
  Sometimes, you have to accept that the market will deploy something
  and you have little influence on it.  In those cases it's better to
  write a compelling spec and hope that people will migrate.  Other
  times, if you can stretch to meet market timing, you can avoid the
  market deploying something that does not meet your spec.  That is
  very desirable.

* Which will take longer: fixing this spec or starting from scratch?

--Sam

_______________________________________________
SPKM mailing list
SPKM@ietf.org
https://www1.ietf.org/mailman/listinfo/spkm