netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hugo Santos <hsantos@av.it.pt>
To: yoshfuji@linux-ipv6.org, davem@davemloft.net
Cc: netdev@vger.kernel.org, usagi-core@linux-ipv6.org
Subject: Regarding offloading IPv6 addrconf and ndisc
Date: Thu, 27 Jul 2006 12:25:31 +0100	[thread overview]
Message-ID: <20060727112531.GN6026@innerghost.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

Hi all,

   In the same line as some of the recent IPv6 patches being submited
 for comments, and taking into consideration RFCs such as 'SEcure
 Neighbor Discovery (SEND)' (RFC 3971) and 'Cryptographically Generated
 Addresses (CGA)' (RFC 3972) where the complexity associated with
 maintaining addresses and performing neighbor discovering increases
 considerably, what would be the possibility of inclusion of code that
 would allow the outsource of address configuration, DAD and neighbor
 discovery to a user-space control application (being that the first two
 can already be somewhat outsourced)? Of course that the final decision
 is always based on the patch itself but i would like to probe the
 developers about the possibility of ever merging such code. Personally
 i believe that this kind of control logic should always be in
 user-space to allow for greater flexibility -- but i'm aware that lots
 of people prefer to have it in kernel to minimize deployment
 dependencies.

    Comments?

    Hugo

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2006-07-27 11:25 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27 11:25 Hugo Santos [this message]
2006-07-27 12:25 ` Regarding offloading IPv6 addrconf and ndisc Kazunori Miyazawa
2006-07-27 17:56   ` Hugo Santos
2006-07-27 23:56   ` Herbert Xu
2006-07-28  1:34     ` David Miller
2006-07-28  1:45       ` Hugo Santos
2006-07-28  2:27         ` David Miller
2006-07-28  3:13           ` Hugo Santos
2006-07-28  3:20             ` David Miller
2006-07-28  3:31               ` Hugo Santos
2006-07-28  4:07                 ` Stephen Hemminger
2006-07-28  8:34                   ` Hugo Santos
2006-07-28 12:45                     ` Jamal Hadi Salim
2006-07-29 13:34                       ` Hugo Santos
2006-07-30  3:28                         ` Kazunori Miyazawa
2006-07-30 11:30                           ` Hugo Santos
2006-07-31 21:23                             ` David Miller
2006-08-01 11:50                               ` Hugo Santos
2006-08-01 21:54                                 ` David Miller
2006-08-01  0:16                             ` Kazunori Miyazawa
2006-07-28  2:22       ` Herbert Xu
2006-07-28  2:33         ` David Miller
2006-08-01  0:31       ` Andi Kleen
2006-08-01  0:46         ` David Miller
2006-08-01  0:49           ` Roland Dreier
2006-08-01  1:24             ` Jamal Hadi Salim
2006-08-01  1:30               ` Herbert Xu
2006-08-01  1:47                 ` Jamal Hadi Salim
2006-08-01 12:13                   ` Hugo Santos
2006-08-01 12:00           ` Hugo Santos
2006-08-01 21:57             ` David Miller
2006-08-03 13:28               ` Ingo Oeser

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=20060727112531.GN6026@innerghost.net \
    --to=hsantos@av.it.pt \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=usagi-core@linux-ipv6.org \
    --cc=yoshfuji@linux-ipv6.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).