RE: entity mib support for tcif

"David T. Perkins" <[email protected]>
Newsgroups gmane.ietf.entmib
Message-ID <[email protected]>
HI,

Can you provide us with pricing. Say, if SNMPinfo created
a product that had a chassis, and 3 field replacable components,
than how much would it cost SNMPinfo to obtain CLEI codes
from Telcordia?

Also, the link below, http://www.atis.org/doccenter.shtml, is
to an organization that provides copies of docs for a fee.
I don't see how it answers any questions. It does provide
a way for me to pay US$58 for an electronic copy of document
T1.213. (It doens't specify the page count.) Can you provide
a copy of the document to us for review?

On Sun, 14 Sep 2003, Kaj Tesink wrote:

> At 09:44 PM 9/12/2003 -0700, C. M. Heard wrote:
> 
> >On Sun, 7 Sep 2003, David T. Perkins wrote:
> > > In addition to the redundancy of objects, I have big issue
> > > with including in a standards track MIB module, support for
> > > a proprietary network management platform, and one where
> > > there is significant costs for device vendors.
> > >
> > > Here is a FAQ on CLEIs from telcordia:
> > > 
> > http://www.telcordia.com/resources/commonlang/productshowroom/showroom/equip_id/carriers/faq.html
> >
> >[ ... remainder snipped ... ]
> >
> >It may be worth pointing out that CLEI codes (along with other
> >Telcordia Common Language(TM) products) have been adopted as
> >identifiers in ANSI standards, and there is a proposal on the table
> >to add mappings of these ANSI standards to ITU-T Rec. M.1401.  See
> >T1M1.3/2003-032, a URL for which is in the attached message from the
> >T1M1.3 mail exploder.
> 
> 
> Yup, that is right; Telcordia is actually the designated maintenance agent 
> for the ANSI document T1.213,
> Coded Identification of Equipment Entities of the North American 
> Telecommunications System for
> Information Exchange. This document provides the format and structure for 
> the CLEI code.
> For details see http://www.atis.org/doccenter.shtml.
> 
> Telcordia assigns CLEI codes on a request basis from a supplier for their 
> communications equipment.
> For example, these codes are then placed on a linear bar code label which 
> is affixed onto the plug-in card as well as
> the container for that plug-in card. What we're talking about here is to 
> make that information
> accessible for network management ssystems.
> 
> kaj
> 
> 
> 
> 
> 
> 
> 
> >Mike Heard
> >Return-Path: <[email protected]>
> >Received: from psmtp.com (exprod6mx17.postini.com [12.158.35.157])
> >         by shell4.bayarea.net (8.11.6/8.11.6) with SMTP id h8D3tOu13177
> >         for <[email protected]>; Fri, 12 Sep 2003 20:55:24 -0700
> >Received: from source ([205.219.84.13]) by exprod6mx17.postini.com 
> >([12.158.35.251]) with SMTP;
> >         Fri, 12 Sep 2003 23:55:24 EDT
> >Received: from psmtp.com (exprod6mx37.postini.com [12.158.35.177])
> >         by postman.bayarea.net (8.12.8p1/8.12.8) with SMTP id h8D3tNKH097287
> >         for <[email protected]>; Fri, 12 Sep 2003 20:55:23 -0700 (PDT)
> >Received: from source ([216.65.124.72]) by exprod6mx37.postini.com 
> >([12.158.35.251]) with SMTP;
> >         Fri, 12 Sep 2003 20:55:23 PDT
> >Received: from t1.rxcpi.com (T1.RXCPI.COM[208.30.94.3])
> >         by orb.pobox.com (Postfix) with ESMTP id CBAE21561BB
> >         for <[email protected]>; Fri, 12 Sep 2003 23:55:22 -0400 (EDT)
> >Received: (from daemon@localhost)
> >         by t1.rxcpi.com (8.9.3/8.9.3) id AAA26208
> >         for <[email protected]>; Sat, 13 Sep 2003 00:27:18 -0400
> >Received: (from root@localhost)
> >         by t1.rxcpi.com (8.9.3/8.9.3) id AAA11541
> >         for t1m13-outgoing; Sat, 13 Sep 2003 00:25:53 -0400
> >Received: (from daemon@localhost)
> >         by t1.rxcpi.com (8.9.3/8.9.3) id AAB11533
> >         for <[email protected]>; Sat, 13 Sep 2003 00:25:52 -0400
> >From: [email protected]
> >Received: from t1.org (www.t1.org [63.137.53.132])
> >         by t1.rxcpi.com (8.9.3/8.9.3) with SMTP id AAA11444
> >         for [email protected]; Sat, 13 Sep 2003 00:25:52 -0400
> >Message-Id: <[email protected]>
> >Subject: [T1M1.3] New Files Uploaded
> >Date: Fri, 12 Sep 2003 23:57:22 -0500
> >To: [email protected]
> >Cc:
> >X-AntiVirus: scanned for viruses by Computer Pharmacy Inc. 
> >(http://www.computerpharmacy.com/)
> >Sender: [email protected]
> >Precedence: bulk
> >Reply-To: [email protected]
> >X-AntiVirus: scanned for viruses by Computer Pharmacy Inc. 
> >(http://www.computerpharmacy.com/)
> >MIME-Version: 1.0
> >X-MIME-Autoconverted: from 8bit to quoted-printable by 
> >smtpout1.bayarea.net id h8D4lmJb014712
> >
> >Files Uploaded on: 09/12/2003 for T1M1.3
> >
> >CONTRIBUTION#: T1M1.3/2003-032 (3M130320)
> >LINK: http://www.t1.org/FileMgr/GetOneFile.taf?FileName=3M130320&NW=Y
> >TITLE: Proposal for mapping T1 American National Standards to proposed
> >ITU-T Rec. M.1401
> >DESC: Provides proposed mappings of American National Standards (ANS)
> >for Telecommunications - Information Interchange to ITU-T Rec. M.1401.
> >These T1 standards, based on Telcordia Technologies COMMON LANGUAGE‚
> >Products, primarily provide structures and formats for identifying
> >network resources.
> >CONTACT(S): Paul Levine ([email protected] (732) 873-8496)
> >SOURCE: Telcordia Technologies
> >
> >
> >CONTRIBUTION#: T1M1.3/2003-033 (3M130330)
> >LINK: http://www.t1.org/FileMgr/GetOneFile.taf?FileName=3M130330&NW=Y
> >TITLE: T1M1.3 WG (CLDR) Sept. 12, 2003 Meeting Report
> >DESC: Documents the proceedings of the September 12, 2003
> >teleconference call meeting of the T1M1.3 WG (CLDR).
> >CONTACT(S): Paul Levine ([email protected] (732) 873-8496)
> >SOURCE: T1M1.3 WG Chair
> 
> 
> _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> 
> Kaj Tesink
> Telcordia Technologies. Inc.

Regards,
/david t. perkins
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.