[tcpm] IANA TCP options registry ... -- Re: [IANA #282277] General Request for Assignments (tcp-parameters)

RFC Editor <rfc-editor@rfc-editor.org> Thu, 01 April 2010 22:28 UTC

Return-Path: <rfc-ed@rfc-editor.org>
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 693073A6869; Thu, 1 Apr 2010 15:28:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.532
X-Spam-Status: No, score=-0.532 tagged_above=-999 required=5 tests=[AWL=0.938, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id wuJKVzoO6OQQ; Thu, 1 Apr 2010 15:28:07 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 671D53A6800; Thu, 1 Apr 2010 15:28:04 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 6000) id B28EDE0797; Thu, 1 Apr 2010 15:28:37 -0700 (PDT)
Date: Thu, 01 Apr 2010 15:28:37 -0700
From: RFC Editor <rfc-editor@rfc-editor.org>
To: William Allen Simpson <william.allen.simpson@gmail.com>
Message-ID: <20100401222837.GA14648@rfc-editor.org>
References: <RT-Ticket-282277@icann.org> <20091125092230.DC5482A4018@isvc1.lax.icann.org> <rt-3.8.3pre1-6606-1259179914-435.282277-6-0@icann.org> <4B8C01CB.6030104@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4B8C01CB.6030104@gmail.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Cc: TCP Modifications WG <tcpm@ietf.org>, IESG <iesg@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [tcpm] IANA TCP options registry ... -- Re: [IANA #282277] General Request for Assignments (tcp-parameters)
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Apr 2010 22:28:08 -0000


We did not recgonize the document as a request for publication as an
Independent Submission because we thought the reqeust was to the IESG,
as the message below indicates "IESG, this is a formal request for
approval and publication." 

We apologize for the confusion and delay.  Please let us know if you
have any questions.

Thank you.

RFC Editor

Date: Thu, 01 Apr 2010 15:35:22 -0400
From: William Allen Simpson <william.allen.simpson@gmail.com>
To: RFC Editor <rfc-editor@rfc-editor.org>
CC: TCP Modifications WG <tcpm@ietf.org>
Subject: Re: [tcpm] IANA TCP options registry ... 

On 4/1/10 1:23 PM, RFC Editor wrote:

> Unfortunately, we did not recognize the mail received on 1 March as a
> request to consider<draft-simpson-tcpct-00.txt>  for publication as
> an Independent Submission, as we did not see a particular request for
> for the RFC Editor.  Once clarified, the document was processed as
> described in RFC 4846.
Pardon my unclear language in my first sentence of March 1st:                                                                                                                                   
# "this is a formal request for approval and publication." 

On Mon, Mar 01, 2010 at 01:04:59PM -0500, William Allen Simpson wrote:
> Amanda Baber via RT wrote:
>> This registry requires IESG Approval or Standards Action, so we can't take 
>> any action yet. Let us know when your draft has been posted, and we'll ask 
>> the IESG to review it and approve the assignments. 
> IESG, this is a formal request for approval and publication.  In the
> usual tradition (of T/TCP, etc), I'm not interested in Standards Action
> at this time.  This is not the product of a working group.
> 	Title		: TCP Cookie Transactions (TCPCT)
> 	Author(s)	: W. Simpson
> 	Filename	: draft-simpson-tcpct-00.txt
> 	Pages		: 34
> 	Date		: 2010-2-26
>    TCP Cookie Transactions (TCPCT) deter spoofing of connections and
>    prevent resource exhaustion, eliminating Responder (server) state
>    during the initial handshake.  The Initiator (client) has sole
>    responsibility for ensuring required delays between connections.  The
>    cookie exchange may carry data, limited to inhibit amplification and
>    reflection denial of service attacks.
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-simpson-tcpct-00.txt
>> Please note that we can't guarantee that these numbers won't be assigned 
>> in the interim.
> We chose them after examining tcpdump repositories and testing.
> TCPM scuttlebutt has Cisco using 33 (without reservation).  The official
> experimental numbers 253-254 were unusable over the Internet for testing,
> as those have been compromised by other shipping products (Cisco and
> some "middlebox discovery" vendor or two).
> So, we had to decide on a pair of numbers sooner rather than later!
> There are now many systems running this code.
>> On Wed Nov 25 09:22:31 2009, William.Allen.Simpson@gmail.com wrote:
>>> Contact Name :
>>> William Allen Simpson
>>> Contact Email :
>>> William.Allen.Simpson@gmail.com
>>> Type of Assignment :
>>> 31 TCP Cookie Extension (variable length)
>>> 32 TCP Time Stamp Extension
>>>    (3)
> Here's the draft's IANA Considerations, slightly more formal names:
>    TCP Cookie Option
>    Kind: 31
>    Length: variable.
>    TCP Timestamps Extended Option
>    Kind: 32
>    Length: 3.
>>> Registry :
>>> http://www.iana.org/assignments/tcp-parameters/