netdev - Re: [RFC PATCH net-next 0/9] netlink: strict attribute checking option

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1444988411.2852230.411870761.15F9E4C9@webmail.messagingengine.com>
Date:	Fri, 16 Oct 2015 11:40:11 +0200
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	Jiri Benc <jbenc@...hat.com>, David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, tgraf@...g.ch
Subject: Re: [RFC PATCH net-next 0/9] netlink: strict attribute checking option

Hi,

On Fri, Oct 16, 2015, at 10:08, Jiri Benc wrote:
> On Fri, 16 Oct 2015 01:08:26 -0700 (PDT), David Miller wrote:
> > I think his point is that you'll be making changes to an RFC specified
> > protocol.
> 
> The RFC is only informational, it has never became an Internet
> standard (under the RFC terms). And no other OS picked it up. Keeping
> kernel uAPI documentation in IETF database sounds rather inefficient.

I would suggest you simply add a description to the rfc via the errata
process here: <https://www.rfc-editor.org/errata_report.php>

The original cover letter should be enough to post there. I am also not
sure if people do really implement this spec, at least they have a
pointer to it, then. AFAIK the IESG will look into that then and even
non-approved erratas will be listed on the rfc page.

Bye,
Hannes
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html