"Push" TAM Protocols. Was: Asessment of TAMP with vendor hat on

["Anders Rundgren" <anders.rundgren@xxxxxxxxx>]

I fully agree with Stefan's conclusions.

Now to the possible query/response protocol.

I don't see why anybody (be it consumer or enterprise) would be interested in opening a hole in the firewall allowing inbound TA-TTP
updates to for example the browser TA store.

This does however not dismiss such a protocol, it just narrows the scope.  IMHO, this may even increase the chances that it
succeeds.

If we rather think of the scope as a set of networked devices (servers, routers etc) centrally managed by an organization, you may
indeed want to have an immediate update rather than waiting for the local "pull" scheme to kick in.

If I were to design such a protocol I would base it on Web Services to not end-up with yet another esoteric protocol that you must
ask IT to support.

But as earlier stated, I'm not going to follow the protocol port of TAM, so please feel free using ASN.1 and registering TCP ports.
It was just a friendly advice from a person who see deployment and adoption as a bigger hurdle than passing a final call in IETF.

Another possibility which I unfortunately has zero knowledge of, could be using SNMP.

Anders Rundgren
With the independent observer hat on