From: Ken Goldman <kgoldman@us.ibm.com>
To: trousers-tech@lists.sourceforge.net
Cc: tpmdd-devel@lists.sourceforge.net, openssl-dev@openssl.org,
gnutls-devel@lists.gnutls.org
Subject: Re: [gnutls-devel] Proposal for the ASN.1 form of TPM1.2 and TPM2 keys
Date: Fri, 30 Dec 2016 10:40:24 -0500 [thread overview]
Message-ID: <o45v4u$60d$1@blaine.gmane.org> (raw)
In-Reply-To: <1482691491.3394.8.camel@HansenPartnership.com>
On 12/25/2016 1:44 PM, James Bottomley wrote:
> On Sun, 2016-12-25 at 10:18 +0100, Nikos Mavrogiannopoulos wrote:
>> On Sat, Dec 24, 2016 at 5:13 PM, James Bottomley
>>
>> I wouldn't expect RSA inc to be involved into this as part of PKCS.
>> They are dead long time ago and have moved to IETF.
>
> I think I should give TCG first crack at wanting to own the OID. The
> IETF ones are easy: once you codify it in an RFC, the oid registry auto
> extracts it.
Does this help at all? From the TCG Credential Profile EK specL
TCG has registered an object identifier (OID) namespace as an
“international body” in the ISO registration hierarchy. This leads to
shorter OIDs and gives TCG the ability to manage its own namespace. The
OID namespace is inherited from TCPA. These definitions are intended to
be used within the context of an X.509 v3 certificate specifically
leveraging the profile described in RFC 5280[11].
-- TCG specific OIDs
tcg OBJECT IDENTIFIER ::= {
joint-iso-itu-t(2) international-organizations(23) tcg(133) }
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
prev parent reply other threads:[~2016-12-30 15:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 18:06 Proposal for the ASN.1 form of TPM1.2 and TPM2 keys James Bottomley
2016-12-23 20:12 ` Richard Levitte
[not found] ` <20161223.211218.817856866219152234.levitte-MCmKBN63+BlAfugRpC6u6w@public.gmane.org>
2016-12-23 20:22 ` [openssl-dev] " James Bottomley
2016-12-24 13:25 ` Nikos Mavrogiannopoulos
[not found] ` <CAJU7zaKjXhKJ-3PJD6XrLW2hTixEqL0B56epbqG3trw3jmXjVg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-24 16:13 ` [gnutls-devel] " James Bottomley
2016-12-25 9:18 ` Nikos Mavrogiannopoulos
2016-12-25 18:44 ` [gnutls-devel] " James Bottomley
2016-12-25 21:08 ` Nikos Mavrogiannopoulos
2016-12-25 23:47 ` [gnutls-devel] " James Bottomley
2016-12-26 7:18 ` Nikos Mavrogianopoulos
[not found] ` <F37418F5-0ECC-4F8B-981A-2ED74FAADA51-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-12-26 18:13 ` [gnutls-devel] " James Bottomley
2016-12-26 20:13 ` Nikos Mavrogianopoulos
[not found] ` <671CBF50-E114-4FD1-995A-523C7B63F8D5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-12-29 23:57 ` [gnutls-devel] " James Bottomley
2016-12-27 15:35 ` Erwann Abalea
2016-12-30 15:40 ` Ken Goldman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='o45v4u$60d$1@blaine.gmane.org' \
--to=kgoldman@us.ibm.com \
--cc=gnutls-devel@lists.gnutls.org \
--cc=openssl-dev@openssl.org \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=trousers-tech@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.