netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: eric@regit.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 3/5] Selected corrections from Mr. Dash Four
Date: Sun, 18 Dec 2011 15:11:15 +0000	[thread overview]
Message-ID: <4EEE0293.90408@googlemail.com> (raw)
In-Reply-To: <1324155743-25999-4-git-send-email-jengelh@medozas.de>


> -At the time of the writing there is no routing-based implementation of
> +At the time of the writing, there is no routing-based implementation of
>  `rp_filter` in the Linux kernel for IPv6. Manual anti-spoofing via Netfilter
>  rules is thus needed.
>   
I don't mean to be picky (again) but the above should be "At the time of 
writing, there is no routing-based implementation of `rp_filter` in the 
Linux kernel for IPv6 - manual anti-spoofing via Netfilter rules is 
needed." or "At the time of writing, there is no routing-based 
implementation of `rp_filter` in the Linux kernel for IPv6, therefore 
manual anti-spoofing via Netfilter rules is needed."

> -The anti-spoofing must be done on a per-interface basis. For each interface,
> +Anti-spoofing must be done on a per-interface basis. For each interface,
>  we must list the authorized network on the interface. There is exception,
>   
"For each interface, we must list the authorized network on that interface."


  reply	other threads:[~2011-12-18 15:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-17 21:02 secure-conntrack-helpers: updates Jan Engelhardt
2011-12-17 21:02 ` [PATCH 1/5] Use modern -m conntrack match Jan Engelhardt
2011-12-17 21:02 ` [PATCH 2/5] Sentence ordering Jan Engelhardt
2011-12-17 21:02 ` [PATCH 3/5] Selected corrections from Mr. Dash Four Jan Engelhardt
2011-12-18 15:11   ` Mr Dash Four [this message]
2011-12-17 21:02 ` [PATCH 4/5] " Jan Engelhardt
2011-12-17 21:02 ` [PATCH 5/5] Plural forms Jan Engelhardt
2011-12-18 15:14   ` Mr Dash Four
2011-12-22 13:32     ` Eric Leblond

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=4EEE0293.90408@googlemail.com \
    --to=mr.dash.four@googlemail.com \
    --cc=eric@regit.org \
    --cc=jengelh@medozas.de \
    --cc=netfilter-devel@vger.kernel.org \
    /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).