From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6•org>
To: Stephen Hemminger <shemminger@vyatta•com>
Cc: davem@davemloft•net, Pekka Savola <pekkas@netcore•fi>,
Nick Hilliard <nick@inex•ie>,
netdev@vger•kernel.org,
YOSHIFUJI Hideaki <yoshfuji@linux-ipv6•org>
Subject: Re: [PATCH 1/3] IPv6: Generic TTL Security Mechanism (original version)
Date: Mon, 05 Apr 2010 13:48:26 +0900 [thread overview]
Message-ID: <4BB96B9A.3000203@linux-ipv6.org> (raw)
In-Reply-To: <20100403232922.489187907@vyatta.com>
Hi,
(2010/04/04 8:21), Stephen Hemminger wrote:
> The original proposed code; the IPV6 and IPV4 socket options are seperate.
> With this method, the server does have to deal with both IPv4 and IPv6
> socket options and the client has to handle the different for each
> family.
I am for 1/3 (original), not for 2/3, 3/3.
Because we should allow users to set respective value
for IPv4 and IPv6, as we allow users to do so for TTL
and hoplimit itself.
--yoshfuji
next prev parent reply other threads:[~2010-04-05 4:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 23:21 [PATCH 0/3] GTSM support for IPv6 three alternatives Stephen Hemminger
2010-04-03 23:21 ` [PATCH 1/3] IPv6: Generic TTL Security Mechanism (original version) Stephen Hemminger
2010-04-05 4:48 ` YOSHIFUJI Hideaki [this message]
2010-04-05 19:06 ` Nick Hilliard
2010-04-22 16:23 ` Stephen Hemminger
2010-04-22 21:38 ` David Miller
2010-04-22 22:18 ` [PATCH] IPv6: Generic TTL Security Mechanism (final version) Stephen Hemminger
2010-04-22 22:27 ` David Miller
2010-04-03 23:21 ` [PATCH 2/3] IPv6: Generic TTL Security Mechanism (alternate version) Stephen Hemminger
2010-04-03 23:21 ` [PATCH 3/3] IPv6: Generic TTL Security Mechanism (unified version) Stephen Hemminger
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=4BB96B9A.3000203@linux-ipv6.org \
--to=yoshfuji@linux-ipv6$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nick@inex$(echo .)ie \
--cc=pekkas@netcore$(echo .)fi \
--cc=shemminger@vyatta$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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