netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefani Seibold <stefani@seibold.net>
To: David Miller <davem@davemloft.net>
Cc: eric.dumazet@gmail.com, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org, netdev@vger.kernel.org,
	shemminger@vyatta.com, jj@chaosbits.net, daniel.baluta@gmail.com,
	jochen@jochen.org, hagen@jauu.net, torvalds@linux-foundation.org,
	pavel@ucw.cz
Subject: Re: [PATCH] new UDPCP Communication Protocol
Date: Tue, 11 Jan 2011 22:14:40 +0100	[thread overview]
Message-ID: <1294780480.17388.2.camel@wall-e> (raw)
In-Reply-To: <20110111.125254.133402589.davem@davemloft.net>

Am Dienstag, den 11.01.2011, 12:52 -0800 schrieb David Miller:
> From: Stefani Seibold <stefani@seibold.net>
> Date: Tue, 11 Jan 2011 21:50:20 +0100
> 
> > Right, but currently there is no need for an IPV6 implementation, non of
> > our base station provide it and non of our mobile network customers use
> > it.
> > 
> > If it will be required in the future it will be implemented.
> 
> We require that you implement the ipv6 side for the submission right
> now.
> 
> Long gone are the days when we add ipv4 only implementations of
> protocols.

If nobody need it and no user in the near future out there, why should i
implement this? That is dogmatic only!

  reply	other threads:[~2011-01-11 21:14 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 16:48 [PATCH] new UDPCP Communication Protocol stefani
2011-01-11 17:01 ` Eric Dumazet
2011-01-11 20:50   ` Stefani Seibold
2011-01-11 20:52     ` David Miller
2011-01-11 21:14       ` Stefani Seibold [this message]
2011-01-11 21:19         ` David Miller
2011-01-11 21:41           ` Stefani Seibold
2011-01-11 21:46             ` Eric Dumazet
2011-01-11 22:23               ` Stefani Seibold
2011-01-11 21:30         ` Eric Dumazet
2011-01-11 21:40           ` Stefani Seibold
2011-01-11 21:06     ` Eric Dumazet
  -- strict thread matches above, loose matches on Subject: below --
2011-01-03 14:34 stefani
2011-01-02 22:39 stefani
2011-01-02 22:49 ` Eric Dumazet
2011-01-02 22:55   ` Stefani Seibold
2011-01-02 23:04     ` Jesper Juhl
2011-01-03  9:08       ` Stefani Seibold
2011-01-03  9:27         ` Eric Dumazet
2011-01-03  9:54           ` Stefani Seibold
2011-01-03 10:39             ` Eric Dumazet
2011-01-03 14:08               ` Stefani Seibold
2011-01-02 15:31 stefani
2011-01-02 16:34 ` Eric Dumazet
2011-01-02 19:48 ` Daniel Baluta
2011-01-02 21:33   ` Stefani Seibold
2011-01-02 21:40     ` Jesper Juhl
2011-01-02 19:55 ` Jesper Juhl
2011-01-02 21:46   ` Stefani Seibold
2011-01-02 22:04     ` Jesper Juhl
2011-01-02 22:21       ` Stefani Seibold
2011-01-02 20:16 ` Rémi Denis-Courmont
2011-01-02 21:37   ` Stefani Seibold
2011-01-02 21:55 ` Eric Dumazet
2011-01-02 22:16   ` Stefani Seibold
2011-01-02 22:31     ` Eric Dumazet
2011-01-01 21:44 stefani
2011-01-01 22:23 ` Eric Dumazet
2011-01-02 11:17   ` Stefani Seibold
2011-01-02 11:33     ` Eric Dumazet
2011-01-02 11:57       ` Stefani Seibold

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=1294780480.17388.2.camel@wall-e \
    --to=stefani@seibold.net \
    --cc=akpm@linux-foundation.org \
    --cc=daniel.baluta@gmail.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=hagen@jauu.net \
    --cc=jj@chaosbits.net \
    --cc=jochen@jochen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=shemminger@vyatta.com \
    --cc=torvalds@linux-foundation.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).