Re: [tcpm] IANA TCP options registry ...

Alfred Hönes <ah@TR-Sys.de> Thu, 01 April 2010 14:02 UTC

Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7E0573A686E for <tcpm@core3.amsl.com>; Thu, 1 Apr 2010 07:02:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -94.358
X-Spam-Level:
X-Spam-Status: No, score=-94.358 tagged_above=-999 required=5 tests=[AWL=0.847, BAYES_40=-0.185, CHARSET_FARAWAY_HEADER=3.2, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id onrEzj1zNhpx for <tcpm@core3.amsl.com>; Thu, 1 Apr 2010 07:01:56 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id B77293A6868 for <tcpm@ietf.org>; Thu, 1 Apr 2010 07:01:53 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA105320515; Thu, 1 Apr 2010 16:01:55 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id QAA28384; Thu, 1 Apr 2010 16:01:54 +0200 (MESZ)
From: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@TR-Sys.de>
Message-Id: <201004011401.QAA28384@TR-Sys.de>
To: william.allen.simpson@gmail.com
Date: Thu, 1 Apr 2010 16:01:53 +0200 (MESZ)
In-Reply-To: <4BB48E63.10309@gmail.com> from William Allen Simpson at Apr "1, " 2010 "08:15:31" am
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset=hp-roman8
Content-Transfer-Encoding: 7bit
Cc: tcpm@ietf.org
Subject: Re: [tcpm] IANA TCP options registry ...
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 14:02:02 -0000

William Allen Simpson wrote:

> On 4/1/10 4:36 AM, Alexander Zimmermann wrote:
>>> Section 10 is pretty clear, in that RFC5690 is for limited
>>> experimentation only at this time and hence no separate option
>>> numbers will be assigned.  Experimenters are supposed to use the
>>  normal TCP option numbers set aside for general experimentation
>>> (253/254) when playing with this proposal:
>>
>> this could be funny in Linux. You request ACKcc as TCP sender (option 253)
>> and get Mr. Simpson's TCP Cookie Transactions back ;-)
>>
> Haven't seen that (RFC5690) so far, but there's somebody else using 253 and
> another somebody using 254 in deployed code!  There are earlier messages on
> this list about the culprits.
>
> Last year's Linux code used the experimental numbers and followed the usual
> procedures (you have to explicitly turn it on with a sysctl or sockopt),
> but the conflicts were quickly obvious.  Don't turn it on outside your lab.

That's it.
The rules about these 'experimental' code points have been set out
very clearly in RFC 4727, and "deployed code" or even "commercial"
implementations are not compatible with these.


> The only reason that I've bothered putting up the internet-draft is to get
> official IANA assignments.  I'd sent in the reservation back in November,
> but IANA refused to send it to IESG for approval without an internet-draft.
> Unfortunately, IESG has been *terribly* slow to act.

Well, I fear in *this* case neither IANA nor the IESG should be blamed:

The IANA registry at
  <http://www.IANA.ORG/assignments/tcp-parameters/>
clearly points out:

|  Registry Name: TCP Option Kind Numbers
|  Reference: [RFC2780]
|  Registration Procedures: IESG Approval or Standards Action

RFC 5226 (lower half of page 11) explains the "IESG Approval" policy
as exceptional and gives two indications for when it should be applied:
   - urgency (used recently to get early code point assignments for TLS
     after a new class of MitM attacks had been discovered and work to
     counter these had started), and
   - strong WG consensus (for a non- Standards Track proposal).
RFC 5226 also states there:
   "IESG Approval is not intended to circumvent the public review
    processes implied by other policies that could have been employed
    for a particular assignment."

In this case, RFC 2780 has established approval of an I-D as a
Standards Track RFC as the "normal" requirement ("Standards Action").

Obviously both exceptions quoted above are not proper matches for your
case, and so I still do not see the procedural rule on which you have
based your expectation of exceptional treatment.
Or did I miss something?

Sorry: In this case, avoidance of IETF WGs strikes back.


> Unlike certain commercial interests, I'm trying to avoid conflicts.
> But next time, I'll not bother.  IETF officialdom has become too
> ossified.

I do not want to argue on the final point here, but it looks like in
this case the IETF (an the IESG) is simply eating their own doggy-food,
and as shown above, this has nothing to do with ossification of the
institutions tasked with the execution of the procedures set by the
IETF.  If the taste of the doggy-food is perceived as being bad, we
should better try to modify it (i.e. the rule in RFC 2780 -- see my
previous posting on this thread), and not merely complain about it.

It is generally seen that for major protocols where experiments
in closed lab environments do not suffice to gain siginificant
experience before standardization, some rules set by the IETF
for IANA policy are too restrictive.  The wave of RFCs and drafts
seen during the last couple of years that aim at making additions
to IETF protocols easier is a clear indication that in some Areas
of the IETF the value of experiments and running code is gaining
back momentum.  For TCP and TLS, that's not the case, for instance.
It's ours to request and drive change for the rules if they hurt.


Kind regards,
  Alfred.

-- 

+------------------------+--------------------------------------------+
| TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  |
| Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18         |
| D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de                     |
+------------------------+--------------------------------------------+