From: Jiri Benc <jbenc@redhat.com>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, tgraf@suug.ch
Subject: Re: [RFC PATCH net-next 0/9] netlink: strict attribute checking option
Date: Fri, 16 Oct 2015 12:00:09 +0200 [thread overview]
Message-ID: <20151016120009.45459a75@griffin> (raw)
In-Reply-To: <1444988411.2852230.411870761.15F9E4C9@webmail.messagingengine.com>
On Fri, 16 Oct 2015 11:40:11 +0200, Hannes Frederic Sowa wrote:
> 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.
Okay, we may do that. But let's postpone this discussion after we
decide what route we'll go. We'll definitely need some form of
documentation but it's preliminary to discuss what exact form when we
haven't decided whether we'll implement something like this at all.
Jiri
--
Jiri Benc
next prev parent reply other threads:[~2015-10-16 10:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 16:39 [RFC PATCH net-next 0/9] netlink: strict attribute checking option Jiri Benc
2015-10-15 16:39 ` [RFC PATCH net-next 1/9] netlink: add NLM_F_STRICT for strict attribute checking Jiri Benc
2015-10-15 16:39 ` [RFC PATCH net-next 2/9] netlink: remove unnecesary goto's Jiri Benc
2015-10-15 16:39 ` [RFC PATCH net-next 3/9] netlink: strict attribute parsing Jiri Benc
2015-10-15 16:39 ` [RFC PATCH net-next 4/9] netlink: strict attribute validation Jiri Benc
2015-10-15 16:39 ` [RFC PATCH net-next 5/9] rtnetlink: support strict attribute checking Jiri Benc
2015-10-15 16:39 ` [RFC PATCH net-next 6/9] rtnetlink: add strict parameter to validate callbacks Jiri Benc
2015-10-15 16:39 ` [RFC PATCH net-next 7/9] rtnetlink: add strict parameter to validate_link_af Jiri Benc
2015-10-15 16:39 ` [RFC PATCH net-next 8/9] rtnetlink: support strict checking for newlink, setlink and dellink Jiri Benc
2015-10-15 16:39 ` [RFC PATCH net-next 9/9] veth: validate nested attributes Jiri Benc
2015-10-15 22:07 ` [RFC PATCH net-next 0/9] netlink: strict attribute checking option Hannes Frederic Sowa
2015-10-16 7:49 ` Jiri Benc
2015-10-16 8:08 ` David Miller
2015-10-16 8:08 ` Jiri Benc
2015-10-16 9:40 ` Hannes Frederic Sowa
2015-10-16 10:00 ` Jiri Benc [this message]
2015-10-16 6:50 ` David Miller
2015-10-16 7:39 ` Jiri Benc
2015-10-16 8:06 ` David Miller
2015-10-16 8:02 ` Jiri Benc
2015-10-16 8:09 ` Thomas Graf
2015-10-16 15:57 ` David Ahern
2015-10-19 2:29 ` David Miller
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=20151016120009.45459a75@griffin \
--to=jbenc@redhat.com \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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 NNTP newsgroup(s).