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

"Michelle Cotton via RT" <iana-questions@iana.org> Wed, 24 March 2010 20:02 UTC

Return-Path: <iana-shared@icann.org>
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 181853A6C81 for <tcpm@core3.amsl.com>; Wed, 24 Mar 2010 13:02:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.177
X-Spam-Level:
X-Spam-Status: No, score=-8.177 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_HI=-8]
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 S0RwHjG0VD+p for <tcpm@core3.amsl.com>; Wed, 24 Mar 2010 13:02:29 -0700 (PDT)
Received: from request.lax.icann.org (request.iana.org [208.77.188.221]) by core3.amsl.com (Postfix) with ESMTP id DFA513A6CFB for <tcpm@ietf.org>; Wed, 24 Mar 2010 13:02:29 -0700 (PDT)
Received: from request.lax.icann.org (localhost.localdomain [127.0.0.1]) by request.lax.icann.org (8.13.8/8.13.8) with ESMTP id o2OK1nPK032571; Wed, 24 Mar 2010 13:01:49 -0700
Received: (from apache@localhost) by request.lax.icann.org (8.13.8/8.13.8/Submit) id o2OK1n9o032570; Wed, 24 Mar 2010 13:01:49 -0700
From: Michelle Cotton via RT <iana-questions@iana.org>
In-Reply-To: <f1548841003241135i476d2b2yb9e7c24a14f86f20@mail.gmail.com>
References: <RT-Ticket-309212@icann.org> <f1548841003241049y61d7e156o42c3e8c1a728f98c@mail.gmail.com> <f1548841003241135i476d2b2yb9e7c24a14f86f20@mail.gmail.com>
Message-ID: <rt-3.8.3pre1-31043-1269460909-791.309212-7-0@icann.org>
Precedence: bulk
X-RT-Loop-Prevention: IANA
RT-Ticket: IANA #309212
Managed-by: RT 3.8.3pre1 (http://www.bestpractical.com/rt/)
RT-Originator: michelle.cotton@icann.org
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Date: Wed, 24 Mar 2010 20:01:49 +0000
X-Mailman-Approved-At: Wed, 24 Mar 2010 19:08:07 -0700
Cc: tcpm-chairs@tools.ietf.org, ekr@rtfm.com, tcpm@ietf.org
Subject: [tcpm] [IANA #309212] tcp-ao-crypto-03, IANA registry location question
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: iana-questions@iana.org
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 20:02:31 -0000

Gregory,

I don't think any text changes are needed.  We'll make a note that the registry should be placed in tcp-
parameters.

Thanks,

Michelle



On Wed Mar 24 18:36:14 2010, gregory.ietf@gmail.com wrote:
> Michelle,
> After discussion with Lars, and with Magnus input, we believe (1) add
> "Cryptographic Algorithms for TCP-AO"  as a "tcp-parameter" registry
> is
> best.
> 
> IESG review has already completed.
> 
> Do we want to edit IANA section to reflect this in Auth48, or how did
> you
> want to handle getting the text chagned?
> 
> pls advise,
> Gregory
> 
> On Wed, Mar 24, 2010 at 10:49 AM, Gregory Lebovitz
> <gregory.ietf@gmail.com>wrote:
> 
> > 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
> > or
> > (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.
> >
> > Gregory
> >
> > 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,
> >> TCP-AO
> >> 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
> >
> 
> 
>