From: Einar Lueck <elelueck@linux.vnet.ibm.com>
To: Yuchung Cheng <ycheng@google.com>
Cc: netdev@vger.kernel.org, frankbla@de.ibm.com, raspl@de.ibm.com,
ubacher@de.ibm.com, samudrala@us.ibm.com, davem@davemloft.net
Subject: Re: [RFC PATCH] tcp: introduce raw access to experimental options
Date: Mon, 03 Dec 2012 19:44:19 +0100 [thread overview]
Message-ID: <50BCF303.9020201@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAK6E8=cXin1rSvQNMPife692wkd5tswsR_7RVG6FNB0rqymHeg@mail.gmail.com>
On 11/28/2012 01:01 PM, Yuchung Cheng wrote:
> On Sat, Nov 17, 2012 at 12:54 AM, <elelueck@linux.vnet.ibm.com> wrote:
>> From: Einar Lueck <elelueck@linux.vnet.ibm.com>
>>
>> This patch adds means for raw acces to TCP expirimental options
>> 253 and 254. The intention of this is to enable user space
>> applications to implement communication behaviour that depends
>> on experimental options. For that, new (set|get)sockopts are
>
> Could you elaborate on the use case? I am having a hard time
> understanding that. If you need to use experimental options for your
> applications, why not just use another magic number according to
> draft-ietf-tcpm-experimental-options-02 (since you cite that too)?
We want to enable application programmers to exploit this without
having to change the kernel with all the corresponding implications.
Einar.
prev parent reply other threads:[~2012-12-03 18:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 16:54 [RFC PATCH] tcp: introduce raw access to experimental options elelueck
2012-11-16 18:44 ` David Miller
2012-11-21 14:26 ` Einar Lueck
2012-11-28 10:12 ` Einar Lueck
2012-11-28 12:01 ` Yuchung Cheng
2012-12-03 18:44 ` Einar Lueck [this message]
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=50BCF303.9020201@linux.vnet.ibm.com \
--to=elelueck@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=frankbla@de.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=raspl@de.ibm.com \
--cc=samudrala@us.ibm.com \
--cc=ubacher@de.ibm.com \
--cc=ycheng@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.