UPS+UTF-8 (Was: Re: Anyone there?)

Randy Presuhn <rpresuhn@dorothy.peer.com> Wed, 06 May 1998 19:54 UTC

Delivery-Date: Wed, 06 May 1998 15:54:52 -0400
Return-Path: owner-ups-mib@CS.UTK.EDU
Received: from cnri.reston.va.us (ns.cnri.reston.va.us [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id PAA22114 for <ietf-archive@ietf.org>; Wed, 6 May 1998 15:54:51 -0400 (EDT)
Received: from CS.UTK.EDU (CS.UTK.EDU [128.169.94.1]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id PAA14347 for <ietf-archive@cnri.reston.va.us>; Wed, 6 May 1998 15:57:14 -0400 (EDT)
Received: from localhost (root@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id PAA12719; Wed, 6 May 1998 15:46:13 -0400 (EDT)
Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id PAA12702; Wed, 6 May 1998 15:46:07 -0400 (EDT)
Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id OAA27876 for <ups-mib@cs.utk.edu>; Wed, 6 May 1998 14:46:06 -0500 (CDT)
Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma027863; Wed, 6 May 98 14:45:46 -0500
Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id OAA19159 for <ups-mib@cs.utk.edu>; Wed, 6 May 1998 14:45:22 -0500 (CDT)
Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma018900; Wed, 6 May 98 14:44:59 -0500
Received: from dorothy.peer.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id OAA17777; Wed, 6 May 1998 14:45:21 -0500 (CDT)
Received: (from rpresuhn@localhost) by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id MAA14380; Wed, 6 May 1998 12:45:19 -0700 (PDT)
Date: Wed, 06 May 1998 12:45:19 -0700
From: Randy Presuhn <rpresuhn@dorothy.peer.com>
Message-Id: <199805061945.MAA14380@dorothy.peer.com>
To: ups-mib@CS.UTK.EDU
Subject: UPS+UTF-8 (Was: Re: Anyone there?)
Cc: ops-area@dokka.kvatro.no
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi - 

> Date: Wed, 6 May 1998 15:25:18 -0400
> From: maria@xedia.com (Maria Greene)
> To: Randy Presuhn <rpresuhn@dorothy.peer.com>
> Cc: ups-mib@cs.utk.edu
> Subject: Re: Anyone there?
> References: <199805061854.LAA13788@dorothy.peer.com>
> 
> 
> >>>>> "Randy" == Randy Presuhn <rpresuhn@dorothy.peer.com> writes:
>     ...
> 
>     Randy> RFC 1628 has lots of DisplayString objects.  Would
>     Randy> loosening this constraint to allow UTF-8 for
>     Randy> internationalization (SnmpAdminString) cause problems?  The
>     Randy> underlying syntax (OCTET STRING) and length constraints
>     Randy> would presumably be unchanged.
> 
> Hi, Randy. Good question. According to the "letter of the law"
> (RFC1902, section 10.2) it can't be. I believe we would need to
> deprecate and re-define the objects. However, agents implemented to
> the old MIB would still be conformant to the new definition, so this
> seems overly restrictive. I believe we would have to get "special
> dispensation" to make this change without giving the objects new
> OBJECT IDENTIFIERs. How important do you think this is? It effects
> many working groups with MIBs that are advancing so maybe it should be
> discussed on the v3 list?
...

I agree with your analysis.
I'd like to see the mibs be "internationalization non-hostile" :-).
Our area directors should be able to give the definitive answers.

 -----------------------------------------------------------------------
 Randy Presuhn           Email: rpresuhn@bmc.com      http://www.bmc.com     
 Voice: +1 408 616-3100  BMC Software, Inc.           965 Stewart Drive
 Fax:   +1 408 616-3101  Sunnyvale, California 94086  USA
 -----------------------------------------------------------------------
 In accordance with the BMC Communications Systems Use and Security
 Policy, I explicitly state that although my affiliation with BMC may be
 apparent, implied, or provided, my opinions are not necessarily those
 of BMC Software and that all external representations on behalf of
 BMC must first be cleared with a member of "the top management team."
 -----------------------------------------------------------------------