netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Herbert <therbert@google.com>
To: Jesse Gross <jesse@nicira.com>
Cc: Pravin Shelar <pshelar@nicira.com>,
	David Miller <davem@davemloft.net>,
	Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 0/3] openvswitch: Add STT support.
Date: Mon, 2 Feb 2015 14:49:37 -0800	[thread overview]
Message-ID: <CA+mtBx9RYKY0zDAZEe5Pcc759ysAoXfgwn1rb3PfC92rM-_VvA@mail.gmail.com> (raw)
In-Reply-To: <CAEP_g=_rBmDKDM7fjud78YY=HLnf1r3OdcXux=tm55TxG1DFig@mail.gmail.com>

On Mon, Feb 2, 2015 at 12:39 PM, Jesse Gross <jesse@nicira.com> wrote:
> On Mon, Feb 2, 2015 at 8:23 AM, Tom Herbert <therbert@google.com> wrote:
>>> I would recommend you take a look at the draft if you haven't already:
>>> http://tools.ietf.org/html/draft-davie-stt-06
>>>
>>> It is currently in the final stages of the RFC publication process.
>>
>> Sorry, but this statement is completely wrong and misleading.
>> According to datatracker this draft has been expired since October,
>> there's been no discussion on it in IETF, and this has not gone to
>> IESG. You cannot say this is an IETF standard nor that it is about to
>> be published as one.  See
>> https://datatracker.ietf.org/doc/draft-davie-stt/ and please read the
>> Internet Standards process in RFC2026.
>>
>> I suggest that you update the draft and post it on both nvo3 and tsvwg
>> so there can be some real discussion on the implications of
>> repurposing an IP protocol number and breaking TCP protocol standards.
>
> Seriously, Tom?
>
> It's currently in the ISE queue to be published as an RFC, which you
> can see in the history in the datatracker link. I didn't say that it
> was being published as a standard, I said RFC. This is the same
> process and status that VXLAN has.. It also was presented in nvo3
> before you started coming.
>
> Please get your facts straight before making accusations.

The draft has not come up before the IESG, I have confirmed that with the ADs.

  reply	other threads:[~2015-02-02 22:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 20:25 [PATCH net-next 0/3] openvswitch: Add STT support Pravin B Shelar
2015-01-20 23:06 ` Tom Herbert
2015-01-21  9:08   ` Pravin Shelar
2015-01-21 16:51     ` Tom Herbert
2015-01-21 18:30       ` Pravin Shelar
2015-01-21 19:45         ` Tom Herbert
2015-01-21 20:22           ` Eric Dumazet
2015-01-21 20:35           ` Jesse Gross
2015-01-21 21:54             ` Tom Herbert
2015-01-21 22:14               ` Jesse Gross
2015-01-21 23:46                 ` Vincent JARDIN
2015-01-22 16:24                   ` Tom Herbert
2015-01-22 17:51                     ` Vincent JARDIN
2015-01-23  9:04                       ` David Miller
2015-01-23  9:00                     ` David Miller
2015-02-02 16:23             ` Tom Herbert
2015-02-02 20:39               ` Jesse Gross
2015-02-02 22:49                 ` Tom Herbert [this message]
2015-01-23 16:58 ` Tom Herbert
2015-01-23 17:38   ` Jesse Gross
2015-01-23 18:25     ` Tom Herbert
2015-01-23 20:20       ` Jesse Gross
2015-01-23 20:57         ` Tom Herbert
2015-01-23 21:11           ` Pravin Shelar
2015-02-02 16:15         ` Tom Herbert

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=CA+mtBx9RYKY0zDAZEe5Pcc759ysAoXfgwn1rb3PfC92rM-_VvA@mail.gmail.com \
    --to=therbert@google.com \
    --cc=davem@davemloft.net \
    --cc=jesse@nicira.com \
    --cc=netdev@vger.kernel.org \
    --cc=pshelar@nicira.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 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).