From: Herbert Xu <herbert@gondor.apana.org.au>
To: Lukas Wunner <lukas@wunner.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-spdx@vger.kernel.org, David Howells <dhowells@redhat.com>,
Tadeusz Struk <tadeusz.struk@linaro.org>,
"David S. Miller" <davem@davemloft.net>,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
Hyunchul Lee <hyc.lee@gmail.com>,
Namjae Jeon <linkinjeon@kernel.org>,
Steve French <sfrench@samba.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Tom Talpey <tom@talpey.com>,
linux-cifs@vger.kernel.org, Taehee Yoo <ap420073@gmail.com>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Florian Westphal <fw@strlen.de>,
coreteam@netfilter.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] treewide: Add SPDX identifier to IETF ASN.1 modules
Date: Fri, 27 Oct 2023 18:55:56 +0800 [thread overview]
Message-ID: <ZTuXPAZWVkLvVPHq@gondor.apana.org.au> (raw)
In-Reply-To: <143690ecc1102c0f67fa7faec437ec7b02bb2304.1697885975.git.lukas@wunner.de>
On Sat, Oct 21, 2023 at 01:23:44PM +0200, Lukas Wunner wrote:
> Per section 4.c. of the IETF Trust Legal Provisions, "Code Components"
> in IETF Documents are licensed on the terms of the BSD-3-Clause license:
>
> https://trustee.ietf.org/documents/trust-legal-provisions/tlp-5/
>
> The term "Code Components" specifically includes ASN.1 modules:
>
> https://trustee.ietf.org/documents/trust-legal-provisions/code-components-list-3/
>
> Add an SPDX identifier as well as a copyright notice pursuant to section
> 6.d. of the Trust Legal Provisions to all ASN.1 modules in the tree
> which are derived from IETF Documents.
>
> Section 4.d. of the Trust Legal Provisions requests that each Code
> Component identify the RFC from which it is taken, so link that RFC
> in every ASN.1 module.
>
> Signed-off-by: Lukas Wunner <lukas@wunner.de>
> ---
> I'm adding a new IETF ASN.1 module for PCI device authentication, hence
> had to research what the correct license is. Thought I'd fix this up
> treewide while at it.
>
> Not included here is fs/smb/client/cifs_spnego_negtokeninit.asn1,
> which is similar to fs/smb/client/ksmbd_spnego_negtokeninit.asn1,
> but contains a Microsoft extension published as Open Specifications
> Documentation. It's unclear to me what license they use:
> https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-spng/
>
> crypto/asymmetric_keys/pkcs7.asn1 | 7 +++++++
> crypto/asymmetric_keys/pkcs8.asn1 | 6 ++++++
> crypto/asymmetric_keys/x509.asn1 | 7 +++++++
> crypto/asymmetric_keys/x509_akid.asn1 | 5 +++++
> crypto/rsaprivkey.asn1 | 7 +++++++
> crypto/rsapubkey.asn1 | 7 +++++++
> fs/smb/server/ksmbd_spnego_negtokeninit.asn1 | 8 ++++++++
> fs/smb/server/ksmbd_spnego_negtokentarg.asn1 | 7 +++++++
> net/ipv4/netfilter/nf_nat_snmp_basic.asn1 | 8 ++++++++
> 9 files changed, 62 insertions(+)
Patch applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2023-10-27 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-21 11:23 [PATCH] treewide: Add SPDX identifier to IETF ASN.1 modules Lukas Wunner
2023-10-21 13:23 ` Richard Fontana
2023-10-22 8:53 ` Lukas Wunner
2023-10-31 2:23 ` J Lovejoy
2023-10-27 10:55 ` Herbert Xu [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=ZTuXPAZWVkLvVPHq@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=ap420073@gmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=fw@strlen.de \
--cc=gregkh@linuxfoundation.org \
--cc=hyc.lee@gmail.com \
--cc=kadlec@netfilter.org \
--cc=keyrings@vger.kernel.org \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=senozhatsky@chromium.org \
--cc=sfrench@samba.org \
--cc=tadeusz.struk@linaro.org \
--cc=tglx@linutronix.de \
--cc=tom@talpey.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).