netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Timo Teräs" <timo.teras@iki.fi>
To: David Miller <davem@davemloft.net>
Cc: herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: [PATCH] af_key: parse and send SADB_X_EXT_NAT_T_OA extension
Date: Thu, 22 Jan 2009 08:14:13 +0200	[thread overview]
Message-ID: <49780EB5.60300@iki.fi> (raw)
In-Reply-To: <20090121.220304.211246256.davem@davemloft.net>

David Miller wrote:
> From: Timo Teräs <timo.teras@iki.fi>
> Date: Thu, 22 Jan 2009 07:56:57 +0200
> 
>> Is there any particular reason why setting NAT-OA info should/
>> must be done using netlink? Or is this just a way to try to
>> put more pressure for the change to happen?
> 
> Because it isn't deprecated if we keep adding features to it.

I would not consider this a new feature. It just makes pfkey
act consistently. If you don't want it supported, it'd make
more sense to not #define SADB_X_EXT_NAT_T_OA and drop all of
the verification code already present than to silently
ignore it. Make kernel return an error if some tried using it.

Now you give impression that it's supported but you just drop
it silently.

>> Also I find it a bit confusing which things are to be allowed
>> in pfkey and which not. We've had bigger fixes/changes to pfkey
>> in past like MIGRATE rewrite, etc.
> 
> That was a mistake on my part, I shouldn't have allowed the
> pfkey side of the changes there.

I see.

- Timo

  reply	other threads:[~2009-01-22  6:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21  7:34 [PATCH] af_key: parse and send SADB_X_EXT_NAT_T_OA extension Timo Teras
2009-01-21 22:33 ` Herbert Xu
2009-01-21 22:40   ` David Miller
2009-01-22  5:56     ` Timo Teräs
2009-01-22  6:03       ` David Miller
2009-01-22  6:14         ` Timo Teräs [this message]
2009-01-22  6:21           ` David Miller
2009-01-22  6:32             ` Herbert Xu
2009-01-22  6:39               ` Timo Teräs
2009-01-22  6:47                 ` Herbert Xu
2009-01-22  6:54                   ` Timo Teräs
2009-01-22  7:39                     ` Herbert Xu
2009-01-22  8:31                       ` Timo Teräs
2009-01-22  8:50                         ` Herbert Xu
2009-01-22  9:24                           ` Timo Teräs
2009-01-22  9:41                             ` Herbert Xu
2009-01-22 10:00                               ` Timo Teräs
2009-01-22 10:10                                 ` Herbert Xu
2009-01-23  6:18             ` Timo Teräs
2009-01-23  9:09               ` Herbert Xu
2009-01-22  6:22           ` Herbert Xu

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=49780EB5.60300@iki.fi \
    --to=timo.teras@iki.fi \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@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).