[tcpm] tcp-ao-crypto-03, IANA registry location question

Gregory Lebovitz <gregory.ietf@gmail.com> Wed, 24 March 2010 17:49 UTC

Return-Path: <gregory.ietf@gmail.com>
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 C51073A68B2 for <tcpm@core3.amsl.com>; Wed, 24 Mar 2010 10:49:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.964
X-Spam-Status: No, score=-99.964 tagged_above=-999 required=5 tests=[AWL=1.504, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id vQF8jk5tJZGx for <tcpm@core3.amsl.com>; Wed, 24 Mar 2010 10:49:42 -0700 (PDT)
Received: from mail-px0-f177.google.com (mail-px0-f177.google.com []) by core3.amsl.com (Postfix) with ESMTP id 2B3813A6910 for <tcpm@ietf.org>; Wed, 24 Mar 2010 10:49:36 -0700 (PDT)
Received: by pxi7 with SMTP id 7so3524164pxi.5 for <tcpm@ietf.org>; Wed, 24 Mar 2010 10:49:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type; bh=IUbSJ4jAoRDWn/ZXPBuyNsiGfNC9ZhbEpRRIMKSUnKw=; b=Fhr0jeIxMfSxkjuIdbjaKof40y4ybgPSUjWrHVop49w2q2phz0j5sQazZ7JPOR0RoY +1d/WfnRxWBJ2L/1XZfzkOYZfHMwr9Gyylh2EIrmCGj+4NsHjPuMExhOeVkzadf/fcOA ytPbzo6cYfm7uORmHp5IOIcQG+k9tHHAf6wwM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=UbmnvUzJUAGLS7mI5Le34jF4hDQpDQCUPupPw3bCZivpxxGVZ0euEhbXpdSy6AxQy5 fcdHya430lpTXPu1lTlnOBsSyMZuV8nHce5KtxrxgCp/Avp0LSrQKNPd8t/lufYrXyKw NkO/AGFFmlg2jsoW9CtcNgtjwkgMSoX2fJIX4=
MIME-Version: 1.0
Received: by with SMTP id e4mr8903224rvi.192.1269452991351; Wed, 24 Mar 2010 10:49:51 -0700 (PDT)
Date: Wed, 24 Mar 2010 10:49:51 -0700
Message-ID: <f1548841003241049y61d7e156o42c3e8c1a728f98c@mail.gmail.com>
From: Gregory Lebovitz <gregory.ietf@gmail.com>
To: tcpm-chairs@tools.ietf.org, Lars Eggert <lars.eggert@nokia.com>, michelle.cotton@icann.org
Content-Type: multipart/alternative; boundary="000e0cd1191e9bcc3e04828f8ec8"
Cc: ekr@rtfm.com, tcpm@ietf.org, iana@iana.org
Subject: [tcpm] tcp-ao-crypto-03, IANA registry location question
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: Wed, 24 Mar 2010 17:49:43 -0000

Draft-03 has now published addressing all issues.

Michelle (IANA team) had a good question:

Should the registry for this, "Cryptographic Algorithms for TCP-AO", be
stand alone or should it sit under the current "tcp-parameters"
registration? FYI, the other things in that "tcp-parameters" registry today
are only two:
  TCP Option Kind Numbers, and
  TCP Alternate Checksum Numbers

The specific question IANA will need answered:
Do we want to
(1) add "Cryptographic Algorithms for TCP-AO"  as a "tcp-parameter" registry
(2) Create "Cryptographic Algorithims for TCP-AO" as a stand-alone registry

Magnus happened to walk by while I was at IANA table with Michelle, and we
both thought (1) above was best. Chairs? Lars?

Michelle advises that IESG can clear the document, and we can address this
in Auth48.


On Wed, Mar 24, 2010 at 10:37 AM, IETF I-D Submission Tool <
idsubmission@ietf.org> wrote:

> A new version of I-D, draft-ietf-tcpm-tcp-ao-crypto-03.txt has been
> successfully submitted by Gregory Lebovitz and posted to the IETF
> repository.
> Filename:        draft-ietf-tcpm-tcp-ao-crypto
> Revision:        03
> Title:           Cryptographic Algorithms for TCP's Authentication Option,
> Creation_date:   2010-03-24
> WG ID:           tcpm
> Number_of_pages: 16
> Abstract:
> The TCP Authentication Option, TCP-AO, relies on security algorithms
> to provide authentication between two end-points.  There are many
> such algorithms available, and two TCP-AO systems cannot interoperate
> unless they are using the same algorithms.  This document specifies
> the algorithms and attributes that can be used in TCP-AO's current
> manual keying mechanism, and provides the interface for future MACs.
> The IETF Secretariat.

IETF related email from
Gregory M. Lebovitz
Juniper Networks