IETF Logo Mail Archive

[secdir] [IANA #236966] Re: Last Call: draft-ietf-rmt-pi-norm-revised (NACK-Oriented Reliable Multicast Protocol) to Proposed Standard

"Amanda Baber via RT" <drafts-lastcall@icann.org> Wed, 22 April 2009 21:58 UTC

Return-Path: <apache@request.iana.org>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1E0973A6D62 for <secdir@core3.amsl.com>; Wed, 22 Apr 2009 14:58:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.29
X-Spam-Level:
X-Spam-Status: No, score=-1.29 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, MISSING_HEADERS=1.292]
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 lBsngDEeuqHo for <secdir@core3.amsl.com>; Wed, 22 Apr 2009 14:58:02 -0700 (PDT)
Received: from request.iana.org (request.iana.org [208.77.188.221]) by core3.amsl.com (Postfix) with ESMTP id 6A29C3A6DE2 for <secdir@ietf.org>; Wed, 22 Apr 2009 14:58:02 -0700 (PDT)
Received: from request.iana.org (localhost.localdomain [127.0.0.1]) by request.iana.org (8.13.8/8.13.8) with ESMTP id n3MLwBrN024559; Wed, 22 Apr 2009 14:58:11 -0700
Received: (from apache@localhost) by request.iana.org (8.13.8/8.13.8/Submit) id n3MLw7SN024558; Wed, 22 Apr 2009 14:58:07 -0700
From: Amanda Baber via RT <drafts-lastcall@icann.org>
In-Reply-To: <p0624080cc6129da0f6e2@[192.168.1.201]>
References: <RT-Ticket-236966@icann.org> <03a101c9ba16$74bf49f0$0600a8c0@china.huawei.com> <4FC76EA8-D6AC-44C0-AA0F-01D02A7651E6@itd.nrl.navy.mil> <070201c9bec1$68a68980$0600a8c0@china.huawei.com> <p0624080cc6129da0f6e2@[192.168.1.201]>
Message-ID: <rt-3.8.3pre1-18044-1240437487-1887.236966-7-0@icann.org>
Precedence: bulk
X-RT-Loop-Prevention: IANA
RT-Ticket: IANA #236966
Managed-by: RT 3.8.3pre1 (http://www.bestpractical.com/rt/)
RT-Originator: amanda.baber@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, 22 Apr 2009 21:58:07 +0000
X-Mailman-Approved-At: Wed, 22 Apr 2009 23:44:36 -0700
Cc: magnus.westerlund@ericsson.com, secdir@ietf.org, tim.polk@nist.gov, Pasi.Eronen@nokia.com, adamson@itd.nrl.navy.mil, M.Handley@cs.ucl.ac.uk, cabo@tzi.org, macker@itd.nrl.navy.mil, lorenzo@vicisano.net
Subject: [secdir] [IANA #236966] Re: Last Call: draft-ietf-rmt-pi-norm-revised (NACK-Oriented Reliable Multicast Protocol) to Proposed Standard
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: drafts-lastcall@icann.org
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2009 21:58:03 -0000

Hi Brian,

A couple of questions about the new IANA Considerations:

- Is there an upper limit to the values available in the NORM 
Stream Control Codes registry?

- Is the NORM_CMD Message Sub-types registry open for further 
assignments? If so, what are the registration procedures and 
upper limits? Should "0" be marked "Reserved"?

Thanks,

Amanda
IANA

On Mon Apr 20 21:50:49 2009, adamson@itd.nrl.navy.mil wrote:
> Hello,
> 
> I have posted an updated version of the NORM draft which addresses 
> Spencer's GEN-ART comments and attempts to clarify the Security 
> Considerations per Dave Harrington's comments and the IANA 
> Consideration per comments from IANA.
> 
> This update also makes the TFMCC RFC a Normative reference per 
> Magnus' request at the last RMT meeting.
> 
> best regards,
>

v2.23.0 | Report a Bug | By Email