-
Notifications
You must be signed in to change notification settings - Fork 822
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set up Organizational ID with IANA for X.509 Attributes #1959
Comments
@randomvariable i've submitted the application, will report back when we have the OID (used the sc1 - steering email id) |
Thanks! |
|
@randomvariable sorry just caught up with this again. |
/close |
@dims: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Great, thanks for this! |
Should we update the contact info to someone at the CNCF? |
Did that list / standardization ever happen? There are two proposed usages underneath the issued PEN and I want to make sure we maintain an accurate canonical list |
The Kubernetes GCP Cloud Provider uses Google owned IANA ASN.1 OIDs for extension attributes in CSRs for the Kubelet. We would like to genericise this mechanism in Kubernetes Cluster API but feel that it would be more appropriate to use CNCF / Kubernetes Project owned OIDs instead of using something from Google's block.
Would it therefore be possible to register for a OID at https://pen.iana.org/pen/PenApplication.page , and then we can maintain a list of attributes and definitions within this repository.
/assign @dims
Who I had chatted with previously about this.
The text was updated successfully, but these errors were encountered: