[Disman] Fw: [IANA #160366] RFC3877 - Matrix update

"Randy Presuhn" <randy_presuhn@mindspring.com> Tue, 22 September 2009 17:11 UTC

Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: disman@core3.amsl.com
Delivered-To: disman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6693A3A67B6 for <disman@core3.amsl.com>; Tue, 22 Sep 2009 10:11:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.601
X-Spam-Level:
X-Spam-Status: No, score=0.601 tagged_above=-999 required=5 tests=[BAYES_50=0.001, J_CHICKENPOX_55=0.6]
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 Yvu6u7P8rnW7 for <disman@core3.amsl.com>; Tue, 22 Sep 2009 10:11:06 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by core3.amsl.com (Postfix) with ESMTP id 576033A67F4 for <disman@ietf.org>; Tue, 22 Sep 2009 10:11:06 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=BIHxuvgwNHc6UdUQRyiFMKwUUaQa1H7U+aaWZXMEcwQt7waXfAHTkcSdnn7jlOkO; h=Received:Message-ID:From:To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.187.239.105] (helo=oemcomputer) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1Mq8uQ-000108-2y for disman@ietf.org; Tue, 22 Sep 2009 13:12:10 -0400
Message-ID: <005f01ca3ba7$e7232da0$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman" <disman@ietf.org>
Date: Tue, 22 Sep 2009 10:12:44 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8881afdcb5313ff34f9c41299cf9c6015122fb355d57c7b21be350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.187.239.105
Subject: [Disman] Fw: [IANA #160366] RFC3877 - Matrix update
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/disman>, <mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/disman>, <mailto:disman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Sep 2009 17:11:07 -0000

Hi -

Forwarded for your information.

Randy

----- Original Message ----- 
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <iana-questions@iana.org>
Cc: <schishol@nortelnetworks.com>om>; "Randy Presuhn" <randy_presuhn@mindspring.com>
Sent: Tuesday, September 22, 2009 4:25 AM
Subject: RE: [IANA #160366] RFC3877 - Matrix update 


Hi Pearl,

See in-line. 

Regards,

Dan
 

> -----Original Message-----
> From: Pearl Liang via RT [mailto:iana-questions@iana.org] 
> Sent: Monday, September 21, 2009 10:31 PM
> Cc: Romascanu, Dan (Dan)
> Subject: [IANA #160366] RFC3877 - Matrix update 
> 
> Hi, Dan,
> 
> Can you also help in answering the questions for the IANA ITU 
> Alarm TC MIB registry?
> 
> Thank you,
> ~pl
> 
> 
> On Fri Jul 31 20:29:26 2009, pearl.liang wrote:
> > Hello Dan,
> > 
> > Here is another one for you :)
> > 
> > > RELATED REGISTRY: IANA Maintained MIBs - IANA ITU Alarm TC MIB
> > > 
> > > URL: http://www.iana.org/assignments/ianaitualarmtc-mib
> > > 
> > > REVIEWER COMMENTS: RFC 3877 Section 5.2 "IANA Considerations" 
> > > provides registration procedures for the registry "IANA 
> Maintained 
> > > MIBs - IANA ITU Alarm TC MIB" but numbers.html shows (?).
> > > 
> > > PROPOSED ACTIONS: Reg. procedures are also listed in 
> registry. Add 
> > > to Matrix.
> > 
> > Two questions:
> > 1.  What would the registration procedures be for the ITU 
> Alarm TC MIB?

Section 5.2 seems to be pretty clear: 

   To aid IANA in the administration of probable cause names and values,
   the OPS Area Director will appoint one or more experts to help review
   requests.


> > 
> > 2. Review the IC section of this RFC,
> > 
> > "IANAItuProbableCause value of 0 is reserved for special 
> purposes and 
> > MUST NOT be assigned. Values of IANAItuProbableCause in the 
> range 1 to 
> > 1023 are reserved for causes that correspond to ITU-T 
> probable cause. 
> > All other requests for new causes will be handled on a first-come 
> > basis, with 1025."
> > 
> > Is the value 1024 missing from the definition?

It's allocated for value other(1024) which is mentioned both in the RFC
and on the Web page. 

> > 
> > Thank you for your help.
> > 
> > Regards,
> > 
> > Pearl Liang
> > IANA
> > 
> 
>