--
You received this message because you are subscribed to the Google Groups "Technical Oversight Board" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tob+uns...@opencontainers.org.
Image that is content addressable
Security that is based on signing image content address
Naming that is federated based on DNS (enables ec2 cr, gcr, quay.io, localhost registry, etc) and can be delegated
Distribution that is based on HTTPS and enables other protocols (e.g. dockyard bittorrent p2p)
--
You received this message because you are subscribed to the Google Groups "Technical Oversight Board" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tob+uns...@opencontainers.org.
There seem to be 5 elements to this proposal:I agree we should do this
Image that is content addressable
I'd like to hear a little more detail about this. Why is this not just a simple content hash?
Security that is based on signing image content address
This seems to be the crux of the debates and I think is what we should discuss
Naming that is federated based on DNS (enables ec2 cr, gcr, quay.io, localhost registry, etc) and can be delegated
This seems like it is out of scope, but I'm willing to be convinced.
Distribution that is based on HTTPS and enables other protocols (e.g. dockyard bittorrent p2p)