Conference hylndr::cdrom

   +---------------+
   | d i g i t a l |  I n t e r o f f i c e  M e m o r a n d u m
   +---------------+
                              

 To:  Distribution                 Date:   Jan. 10, 1997
                                   From:   Van C. Smick
					   Brand Strategy & Naming Mgr
                                   Dept:   DIGITAL Brand Equity Group
                                   Ext.:   DTN 223-5657
                                   M/S:    PKO2-1/J18
                                   E-mail: [email protected] or SALES::SMICK

                                                     
 Subject: Clarification of DIGITAL usage policy
                         
 There have been several questions on the new policy of using DIGITAL in
 place of Digital as described in the DIGITAL brand identity toolbox.
 This note is an attempt to clarify the policy.

 The reason for the change from Digital to DIGITAL is two-fold -- to
 emphasis the brand name and to distinguish it from the generic term
 digital. It is critically important that we build the equity in, and
 focus on, the master brand, DIGITAL. Research continues to show that
 prospects make their purchasing decisions first and foremost on their
 perceptions of the master brand. We need to link the DIGITAL brand
 promise to our products and the value and excitement of our products
 with the DIGITAL master brand.

  Policy:

  1. First, use DIGITAL in all caps (or small caps where supported)
     anywhere you now use the company name Digital with two simple
     exceptions -- the full legal name of the company, Digital Equipment
     Corporation, remains initial cap, and the logo will remain all
     lower case. Everywhere else we will be using DIGITAL in all caps.

  2. Avoid using the possessive of DIGITAL (DIGITAL's). The correct
     usage is "of DIGITAL".

  3. All products are required to use DIGITAL as the first name of the
     product name. In the past this was only required for products with
     generic names (Easy Web Server) but now we need to do this for all
     product names including proprietary names such as AlphaServer or
     OpenVMS. 

     Usage requirements:

     . DIGITAL (in all caps) must precede the product name in titles and
       headlines in all communications. 

     . In all communications other than marketing collateral and product
       documentation DIGITAL should also precede the product name in all
       text usage. 

     . In marketing collateral and product documentation use DIGITAL prior
       to the product name on the initial usage in text and in the
       remainder of the text on a regular basis but not for every
       occurrence of the product name. In addition, DIGITAL must
       precede the product name in titles and headlines

       This relaxation of the standard is designed to achieve the goal
       of increased repetition while recognizing the high repetition of
       the product names in these documents. 

     Implementation:

     In order to avoid any unreasonable inventory costs, it is not
     necessary to change existing marketing deliverables. The change in
     naming should be implemented in new work and when revising existing
     communication work -- including product marketing materials, product
     documentation, web pages, packaging, advertising, etc. 

     And as a reminder, product names which are trademarks must be used as
     adjectives rather than nouns in sentences. 

     - Trademark names stand by themselves in titles e.g. "DIGITAL
       AlphaServer" but must be used to modify another word in sentences
       e.g. "DIGITAL AlphaServer systems are ...."

     - Generic names stand by themselves in titles e.g. "DIGITAL Security
       Software", and may be used as nouns in sentences e.g. "Digital
       Security Software is ..."

 If you have any questions on this, feel free to send them directly to
 me.

 regards, 
 Van

    �Clarification of DIGITAL usage policy
    .
    .
    .
    �In marketing collateral and product documentation use DIGITAL prior
    �to the product name on the initial usage in text [etc]
    .
    .
    .
    �e.g. "Digital
    �Security Software is ..."
    
    Not being practised in the art of discussing how many angels can stand
    on the head of a pin, I find it hard to explain this last example.
    
    b

    
    Re. -1 From SALES::SMICK...
    
    From:   SALES::SMICK        "Van Smick Brand Strategy & Naming Mgr
    223-5657"
    To:     HYLNDR::BROWN
    CC:     SMICK
    Subj:   RE: Notefile CDROM Note 326.30; Clarification of DIGITAL usage
    
    There was an error in the email and the last example should read
    DIGITAL
    Security Software is ....
    
    Sorry for the confusion.
    
    Van
    

From:	NAME: Corporate Information Security <SECURITY@A1@SALES@PKO>
To:     See Below

From  Chuck Noble, [email protected], MSO, DTN 223-8728
    
                      DIGITAL INTERNAL USE ONLY

     Security Advisory for Problem with DoP in DIGITAL UNIX V4.0

  	The Corporate Information Security Group has just released
  Security Advisory 1997-02, "Potential Security Vulnerability with
  DoP in DIGITAL UNIX V4.0".  This Advisory is for all DIGITAL UNIX
  system managers supporting versions V4.0 - 4.0B.  Only these
  versions are affected.
  	A potential security vulnerability has been discovered  
  with the Division of Privilege (DoP), "/usr/sbin/dop" for DIGITAL
  UNIX V4.0, V4.0A, and V4.0B, where under certain circumstances an
  unauthorized user may gain unauthorized privileges.  

  	Security Advisory 1997-02 contains detailed information for
  obtaining and installing the appropriate patch kit for your
  DIGITAL UNIX system.  A complete copy of this advisory can be
  obtained from the Corporate Security home page at 
  http://corpsec.mso.dec.com/Ref-Advisories.htm, or in the Security
  Advisory Notefile at MINOTR::SECURITY_ADVISORY, or in VTX
  SECURITY.
  	CoC Managers hosting Contracted Personnel, who are 
  supporting DIGITAL UNIX V4.0 - 4.0B, are responsible for
  appropriate forwarding of this security communication.

  	Any questions or comments concerning this or any other CISG
  Security Communication should be addressed to CISG @MSO, or
  MINOTR::CISG, or [email protected].  

                      DIGITAL INTERNAL USE ONLY
Distribution:  This message was delivered to you utilizing the Reader's 
Choice delivery services.  You received this message because you are 
working at DIGITAL.  If you have questions regarding this message, please 
contact the author.

+---------------------------+TM
|   |   |   |   |   |   |   |
| d | i | g | i | t | a | l |      TIME   DEPENDENT   BLITZ
|   |   |   |   |   |   |   |
+---------------------------+


      BLITZ TITLE: Retirement of Specific Digital UNIX Versions


                                                DATE: 08-Apr-1997
      AUTHOR: Tom Hayden                        TD #:
      DTN: 381-0311
      ENET: KAMLIA::HAYDEN                      CROSS REFERENCE #'s:
      DEPARTMENT: UNIX Support Engineering      (PRISM/TIME/CLD#'s)

      INTENDED AUDIENCE: All                    PRIORITY LEVEL: 2
      (U.S./EUROPE/GIA)                         (1=TIME CRITICAL,
                                                 2=NON-TIME CRITICAL)


     
=====================================================================

      GENERAL INFORMATION:

      The standard warranty policy for support of DIGITAL developed
      software is one year after the release of the subsequent version.  
      Support for prior versions of Digital UNIX Operating System and related
      high-availability products has been extended for a longer period of 
      time to insure customer satisfaction. 

      The purpose of this memo is to announce the end of this extended 
      support for the following releases:

      On July 1, 1997, the UNIX Support Engineering Group will no longer 
      provide support for:

        o DEC OSF/1 V3.0, V3.0B, V3.2, V3.2B
        o DECsafe Available Server V1.2, ASE V1.2A

      On September 1, 1997, the UNIX Support Engineering Group will no 
      longer provide support for:

        o Digital UNIX V3.2C, V3.2D, V3.2E, V3.2F

      Ending support for a release means that engineering is not obligated 
      to answer new problem reports (e.g. new IPMTs, CLDs, SPRs or QARs), 
      nor deliver patches for that release.  Customers requiring this level 
      of continued support are encouraged to upgrade to Digital UNIX V3.2G 
      or to the latest V4.0* release (currently V4.0B.)  


      VERSIONS THAT WILL BE SUPPORTED:

      As of September 2, 1997, the following versions of Digital UNIX, ASE, 
      and TruClusters Software will continue to be supported:
                
        o Digital UNIX V3.2G 
            o DECsafe Available Server V1.3 on Digital UNIX V3.2G
            o TruCluster Production Server Software V1.0 on Digital UNIX V3.2G
                
        o Digital UNIX V4.0, V4.0A, V4.0B
            o TruCluster Production Server Software and TruCluster Available 
              Server Software V1.4 on Digital UNIX V4.0A and V4.0B

            o TruCluster Production Server Software and TruCluster Available 
              Server Software V1.4A on Digital UNIX V4.0A and V4.0B

      NOTE:

      DECsafe Available Server is also called ASE.
      TruCluster Production Server Software is also called TCR.
      TruCluster Available Server Software is also called ASE.  

                     *** DIGITAL INTERNAL USE ONLY ***