From <IMAP4.psuedo.sims> Wed Oct  8 13:17:11 2008
Date: Wed, 8 Oct 2008 13:17:11 -0700 (PDT)
From: Postmaster
Subject: Message from mail server       
Content-Length: 96
Mime-Version: 1.0
Status: RO
X-IMAP: 1223497031 3

Delete.
This is a system message.                                















--END+PSEUDO--

From sacadmin Thu Jul 31 16:42:13 2008
Received: from sac.sfbay.sun.com (localhost [127.0.0.1])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m6VNgDXC026171;
	Thu, 31 Jul 2008 16:42:13 -0700 (PDT)
Received: (from kasso@localhost)
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id m6VNgDmR026163;
	Thu, 31 Jul 2008 16:42:13 -0700 (PDT)
Date: Thu, 31 Jul 2008 16:42:13 -0700 (PDT)
From: Chris Kasso <kasso@sac.sfbay.sun.com>
Message-Id: <200807312342.m6VNgDmR026163@sac.sfbay.sun.com>
To: LSARC@sac.sfbay.sun.com
Cc: kasso@sun.com
Subject: Update Center 2 Toolkit - IPS Enhancements [LSARC/2008/493 OnePager]
Content-Length: 13833
Status: RO
X-Status: $$$$
X-UID: 0000000001


Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI
This information is Copyright 2008 Sun Microsystems
1. Introduction
    1.1. Project/Component Working Name:
	 Update Center 2 Toolkit - IPS Enhancements
    1.2. Name of Document Author/Supplier:
	 Author:  Tom Mueller
    1.3  Date of This Document:
	31 July, 2008
4. Technical Description

1. Introduction

    1.1. Project/Component Working Name:

Update Center 2 Toolkit - IPS Enhancements

    1.2. Name of Document Author/Supplier:

Chris Kasso

    1.3. Date of This Document:

July 31, 2008

     1.3.1. Date this project was conceived:

October, 2007

    1.4. Name of Major Document Customer(s)/Consumer(s):

     1.4.1. The PAC or CPT you expect to review your project:

Java ES PAC

     1.4.2. The ARC(s) you expect to review your project:

LSARC

     1.4.3. The Director/VP who is "Sponsoring" this project:

Martin Knutson

     1.4.4. The name of your business unit:

Software

    1.5. Email Aliases:
         1.5.1. Responsible Manager: nazrul.islam@sun.com
         1.5.2. Responsible Engineer: tom.mueller@sun.com
         1.5.3. Marketing Manager: ed.conzel@sun.com
     1.5.4. Interest List: dev@updatecenter.dev.java.net

2. Project Summary
    2.1. Project Description:

This is a sub-project of the Update Center 2 Toolkit project which
focuses on the IPS Enhancements, Java-based Bootstrap Initialization
Interface, IPS Java API and Python Dependency.

For details of the overall project see:

http://sac.eng/LSARC/2008/411/20080627_christopher.kampmeier

    2.2. Risks and Assumptions:

See:

http://sac.eng/LSARC/2008/411/20080627_christopher.kampmeier

3. Business Summary

    3.1. Problem Area:

See:

http://sac.eng/LSARC/2008/411/20080627_christopher.kampmeier

    3.2. Market/Requester:

See:

http://sac.eng/LSARC/2008/411/20080627_christopher.kampmeier


    3.3. Business Justification:

See:

http://sac.eng/LSARC/2008/411/20080627_christopher.kampmeier

    3.4. Competitive Analysis:

See:

http://sac.eng/LSARC/2008/411/20080627_christopher.kampmeier

    3.5. Opportunity Window/Exposure:

See:

http://sac.eng/LSARC/2008/411/20080627_christopher.kampmeier

    3.6. How will you know when you are done?:

See:

http://sac.eng/LSARC/2008/411/20080627_christopher.kampmeier

4. Technical Description:
     4.1. Details:

For general info see:

http://sac.eng/LSARC/2008/411/20080627_christopher.kampmeier

This project includes:

Port of IPS
-----------
The Update Center project is responsible for porting the OpenSolaris
project's IPS client and repository infrastructure to a variety of OS 
platforms.

The results of the porting effort are integrated back into the IPS 
project's source and build system, but the Update Center project 
produces and maintains the binary IPS packages for a variety of OS 
platforms apart from OpenSolaris. (Eventually, these binaries may be 
built within the OpenSolaris IPS project's build environment).

Packaging:

The UC2 toolkit project delivers the IPS binaries in an IPS
package.  The IPS package can either be pre-installed in a
distribution or dynamically added to an image during initial
installation via the image initialization feature (see below).

When distribution owners are confident that a suitable installation
of IPS is already present on the target system, the distribution
assemblers may elect to exclude the IPS package from their
distributions.

Image Initialization
--------------------
This subproject enables distro assemblers delivering
primarily Java-based images to:
 
* deliver universal download images and dynamically complete
platform-specific dependencies using Java-based tooling.

* convey user-specified configuration settings during
initial installation

Universal images are those that can be applied to a wide range
of OS platforms and contain little, if any, OS platform-specific
binaries.  For example, it is common for Java-oriented middleware
open source projects to deliver basic zip-based downloads of their
project binaries that can be readily expanded and used across
OS platforms.

User-specified installation-time settings include network
proxy settings and opt-in preferences for transmission of
anonymous usage information.

IPS Java API
------------
Given the target applications of the UC2 toolkit where Java
is prevalent, it is important for the UC2 toolkit project
to provide a Java binding to some of the key IPS interfaces.
Initially, the scope of interfaces addressed by Java bindings
will enable administrative applications to detect the presence
of available updates and to list available updates and add-ons.
Over time, the UC2 toolkit project will progressively build
out Java coverage of the IPS interfaces to enable greater access
to IPS' functionality.

Packaging:

The IPS Java API is delivered as a distinct IPS package that
installs in the same general filesystem location as the IPS
Python implementation.

External, Bundled Dependencies
------------------------------
The target market of unpackaged, zip-based distributions typically
impose very little requirements on end users to satisfy external
dependencies.  With Java-based distributions, often a user is
required to ensure that a suitable version of Java is installed
on their system prior to installing or using the distribution.
 
To meet the out of the box ease of use requirements, the UC2
toolkit project chose a direction in which several of the key
external dependencies are included in the set of UC2 toolkit
packages.  Requiring end users to satisfy this diverse set of
external dependencies prior to using a distribution is not
acceptable from both ease of use and business perspectives.
For example, the versions and download forms of the wx toolkits
across the targeted OS platforms are so diverse that requiring
end users to manually satisfy the wx dependency would result
in immediately dissatisfied users.
 
The embedded external dependencies include:
* Python
* wxPython
* wxWidgets
* OpenSSL
 
Since the target distributions typically require as small
as download sizes as feasible, the UC2 toolkit project has
minimized these external dependencies as part of the process
of embedding them within the toolkit packages.  Interface
implementations that are clearly not required for the
operation of IPS and the wx toolkits are excluded from these
embedded copies of the dependencies.  Python tools that
automatically identify dependency chains are used to
help ease the process of producing minimized builds
of the Python-based components.

The embedded external dependencies are delivered in their own
IPS packages to ease the process of sustaining the content over
time. The packages are identified as "-minimal" and documented as
being positioned for IPS and the UC2 toolkit usage only so as
to avoid other applications from using them.  The content of these
packages are also installed under the IPS (pkg/) and Update Tool
(updatetool/) areas so as to avoid promoting their existence
via their location in the filesystem.

The UC2 toolkit project maintains source controlled build
scripts and, where appropriate, source controlled copies
of the external dependencies such that maintenance fixes
and new versions can be introduced in an efficient and
high quality manner.


     4.2. Bug/RFE Number(s):

See UC2 Toolkit bug/RFE database:

http://wiki.updatecenter.java.net/Wiki.jsp?page=BugsRFEs

     4.3. In Scope:

          4.3.1 OS Platform Support

The primary OS platforms being supported by the project include:

     * Windows XP and Vista on x86
     * Mac OS X on PowerPC and x86
     * Popular, Recent Linux Distributions on x86
     * Solaris 9 and 10 on SPARC and x64
     * OpenSolaris 2008.05 and above

Both 32- and 64-bit are supported on each of the platforms.

Support for other Unix platforms such as AIX and HP-UX, although not
initially addressed by this project, could be supported with a modest
amount of effort. To support any OS platform, at a minimum, a suitable
Python runtime must be made available. If desktop support is also
required, then suitable versions of wxPython and wxWidgets are required.

     4.4. Out of Scope:

See above.

     4.5. Interfaces:

Deferred to more detailed subcase material.

     4.6. Doc Impact:

          4.6.1. End User Documentation

* IPS man pages are provided as part of the port of IPS

* Online help is provided as part of the Update Tool GUI

          4.6.2. Distribution Documentation

* UC2 Toolkit Release Notes can be used by distribution owners
to augment their own distribution release notes when they
embed the toolkit in their distributions.

* UC2 and IPS overview and usage information modules will be
provided such that they can be plugged into each distribution's
documentation set as appropriate.

          4.6.3. Developer Documentation

* Package Maintainer Best Practices

* Distribution Assembler Guide

For more information on documentation, see:

http://wiki.updatecenter.java.net/Wiki.jsp?page=UC2Documentation

     4.7. Admin/Config Impact:

Operation of the technologies included in distributions does not
have to be affected by the introduction of the UC2 toolkit and IPS.
At one level, use of IPS packaging can be viewed as an overlay
on top of existing unpackaged zip-based distributions.

Distribution owners may elect to integrate update, add-on and image
management functions within their existing management interfaces
by using the IPS APIs.

     4.8. HA Impact:

Not applicable.

     4.9. I18N/L10N Impact:

The Update Tool GUI and desktop notifier are i18n-compliant and the
conventional set of languages supported by Sun software products
will be supported.

     4.10. Packaging & Delivery:

See above and, for additional details, see the related ARC
subcases.

         4.10.1  Overall Filesystem Layout

General layout:

bin/                                       # Wrappers/links to actual 
commands
   pkg
   updatetool
   <other top level administrative commands>

   <other, distro/product-specific directories>

pkg/                                     # Self contained pkg (IPS) 
directory
   bin/
     pkg, pkgsend, pkg.depotd
   vendor-packages/pkg/                   # Actual IPs python modules 
are here
   python2.4-minimal/                     # Minimized python runtime

updatetool/                              # Self contained updatetool 
directory
   bin/updatetool
   bin/updatetoolconfig
   vendor-packages/updatetool             # Updatetool python code
   vendor-packages/wx-2.8                 # wxPython toolkit


Example GlassFish-based distribution:

bin/
   pkg
   updatetool
   asadmin                         # Wrapper/link to actual asadmin 
command in glassfish3/bin
   imqcmd
   imqadm

glassfish/
   bin/
   lib/
   ...

mq/
  bin/
  lib/

pkg/

updatetool/

     4.11. Security Impact:

Installation image management security is essentially
limited to end users' ability to access the filesystem, directories
and file residing under an installation image of interest.  In this
sense, overlaying IPS package on top of formerly unpackaged zip-based
installation does not introduce any new security concerns.

The Update Tool GUI and desktop notifier carry out local communications
over a port in order to coordinate their activities.  The connection is
made when needed and is generally short lived.  Only simple
commands (e.g reload config, initiate update check, restart, etc.) are
sent.  No data, beyond the command set is sent over the wire.  The 
connection is
TCP based with the port derived from the private port range (49152 - 65535).

     4.12. Dependencies:

See:

http://sac.eng/LSARC/2008/411/20080627_christopher.kampmeier

This is a subcase of LSARC/2008/411. 

This case depends on PSARC/2008/190 - pkg(5) - Image Packaging System (IPS)

5. Reference Documents:

See this more comprehensive project overview:

http://wiki.updatecenter.java.net/Wiki.jsp?page=UC20FSD.Overview

All project documentation material is available here:

http://wiki.updatecenter.java.net

Multi-install Specifications (umbrella: WSARC/2006/130)
http://sac.eng/Archives/CaseLog/arc/WSARC/2006/130/

Multi-install Filesystem Layout (WSARC/2006/239)
http://sac.sfbay.sun.com/Archives/CaseLog/arc/WSARC/2006/239/

Multi-install Dependency Wiring (WSARC/2007/445)
http://sac.sfbay/arc/WSARC/2007/445/

OpenSolaris IPS information:

http://www.opensolaris.org/os/project/pkg/

6. Resources and Schedule:
    6.1. Projected Availability:

Production quality release August-September 2008.

Quarterly update releases to follow.

    6.2. Cost of Effort:

5 development engineers for 9 months plus Quality, Globalization and 
other project resources.

    6.3. Cost of Capital Resources:

Addressed via existing resources.

    6.4. Product Approval Committee requested information:
        6.4.1. Consolidation or Component Name:

Not applicable.

     6.4.3. Type of CPT Review and Approval expected:

Not applicable.

         6.4.4. Project Boundary Conditions:

Not applicable.

     6.4.5. Is this a necessary project for OEM agreements:

Not at this time.

     6.4.6. Notes:

Not applicable.

     6.4.7. Target RTI Date/Release:

Not applicable.

     6.4.8. Target Code Design Review Date:

Reviews have been occurring throughout the development process.

     6.4.9. Update approval addition:

Not applicable.

    6.5. ARC review type:

Standard

    6.6. ARC Exposure:

Open

    6.6.1. Rationale:

Not applicable.

7. Prototype Availability:

An initial preview release already available as part of the GlassFish
Technology Preview 2 release in May, 2008.

https://glassfish.dev.java.net/downloads/v3-techPreview-2.html


6. Resources and Schedule
    6.4. Steering Committee requested information
   	6.4.1. Consolidation C-team Name:
		unknown
    6.5. ARC review type: OnePager
    6.6. ARC Exposure: open


From sacadmin Fri Sep  5 16:35:09 2008
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m85NZ821001320
	for <lsarc@sac.eng.sun.com>; Fri, 5 Sep 2008 16:35:08 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m85NZ3L4010295
	for <@sunmail2sca.sfbay.sun.com:lsarc@sun.com>; Sat, 6 Sep 2008 00:35:07 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K6Q00M0HXIGPM00@nwk-avmta-1.sfbay.Sun.COM> for lsarc@sun.com
 (ORCPT lsarc@sun.com); Fri, 05 Sep 2008 16:35:04 -0700 (PDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K6Q0008IXIFAOE0@nwk-avmta-1.sfbay.Sun.COM> for lsarc@sun.com
 (ORCPT lsarc@sun.com); Fri, 05 Sep 2008 16:35:04 -0700 (PDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m85NZ3LE013228	for
 <lsarc@sun.com>; Fri, 05 Sep 2008 23:35:03 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0K6Q00C01XA57U00@mail-amer.sun.com> (original mail from Aarti.Pai@Sun.COM)
 for lsarc@sun.com (ORCPT lsarc@sun.com); Fri, 05 Sep 2008 17:35:03 -0600 (MDT)
Received: from [129.145.154.87] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0K6Q00C9LXIDCO40@mail-amer.sun.com> for lsarc@sun.com
 (ORCPT lsarc@sun.com); Fri, 05 Sep 2008 17:35:03 -0600 (MDT)
Date: Fri, 05 Sep 2008 16:35:01 -0700
From: Aarti Pai <Aarti.Pai@sun.com>
Subject: Materials for 2008/493
Sender: Aarti.Pai@sun.com
To: lsarc@sun.com
Cc: Tom Mueller <Tom.Mueller@sun.com>
Reply-to: Aarti.Pai@sun.com
Message-id: <48C1C225.7050600@Sun.COM>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_f1KdpFU5DUWoQXTL9RYk8w)"
X-PMX-Version: 5.4.1.325704
User-Agent: Thunderbird 2.0.0.14 (X11/20080505)
Content-Length: 2172
Status: RO
X-Status: $$$$
X-UID: 0000000002

This is a multi-part message in MIME format.

--Boundary_(ID_f1KdpFU5DUWoQXTL9RYk8w)
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

/shared/sac/Archives/CaseLog/arc/LSARC/2008/493/inception.materials
sac% ls -l
total 965
-r--r--r--   1 apai     sac        31250 Aug 27 14:21 20-questions.txt
-r-xr-xr-x   1 apai     sac          423 Aug 27 12:36 copyspecs.sh
dr-xr-xr-x   2 apai     sac           20 Aug 27 12:55 FSD_files
-r--r--r--   1 apai     sac        56581 Sep  5 11:33 FSD.html
dr-xr-xr-x   4 apai     sac           14 Aug 27 12:36 javadocs
-r--r--r--   1 apai     sac       309421 Sep  5 16:30 LSARC-2008-493.zip
dr-xr-xr-x   2 apai     sac           13 Aug 27 12:36 manifests


--Boundary_(ID_f1KdpFU5DUWoQXTL9RYk8w)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="-1">/shared/sac/Archives/CaseLog/arc/LSARC/2008/493/inception.materials<br>
sac% ls -l<br>
total 965<br>
-r--r--r--&nbsp;&nbsp; 1 apai&nbsp;&nbsp;&nbsp;&nbsp; sac&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 31250 Aug 27 14:21 20-questions.txt<br>
-r-xr-xr-x&nbsp;&nbsp; 1 apai&nbsp;&nbsp;&nbsp;&nbsp; sac&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 423 Aug 27 12:36 copyspecs.sh<br>
dr-xr-xr-x&nbsp;&nbsp; 2 apai&nbsp;&nbsp;&nbsp;&nbsp; sac&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 20 Aug 27 12:55 FSD_files<br>
-r--r--r--&nbsp;&nbsp; 1 apai&nbsp;&nbsp;&nbsp;&nbsp; sac&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 56581 Sep&nbsp; 5 11:33 FSD.html<br>
dr-xr-xr-x&nbsp;&nbsp; 4 apai&nbsp;&nbsp;&nbsp;&nbsp; sac&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 14 Aug 27 12:36 javadocs<br>
-r--r--r--&nbsp;&nbsp; 1 apai&nbsp;&nbsp;&nbsp;&nbsp; sac&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 309421 Sep&nbsp; 5 16:30 LSARC-2008-493.zip<br>
dr-xr-xr-x&nbsp;&nbsp; 2 apai&nbsp;&nbsp;&nbsp;&nbsp; sac&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 13 Aug 27 12:36 manifests<br>
<br>
</font>
</body>
</html>

--Boundary_(ID_f1KdpFU5DUWoQXTL9RYk8w)--

From sac-owner Thu Sep 25 09:36:57 2008
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m8PGaueb000624
	for <all-arcs@sac.sfbay.sun.com>; Thu, 25 Sep 2008 09:36:57 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m8PGakFV009493
	for <@sunmail2sca.sfbay.sun.com:All-ARCs@sun.com>; Thu, 25 Sep 2008 17:36:56 +0100 (BST)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K7R00K2AFHJMD00@brm-avmta-1.central.sun.com> for All-ARCs@sun.com
 (ORCPT All-ARCs@Sun.COM); Thu, 25 Sep 2008 10:36:55 -0600 (MDT)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K7R00C0GFHI5FA0@brm-avmta-1.central.sun.com> for
 All-ARCs@sun.com (ORCPT All-ARCs@Sun.COM); Thu,
 25 Sep 2008 10:36:55 -0600 (MDT)
Received: from fe-amer-09.sun.com ([192.18.109.79])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m8PGas9V006177	for
 <All-ARCs@Sun.COM>; Thu, 25 Sep 2008 16:36:54 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0K7R00301F6ZTF00@mail-amer.sun.com> (original mail from Aarti.Pai@Sun.COM)
 for All-ARCs@Sun.COM (ORCPT All-ARCs@Sun.COM); Thu,
 25 Sep 2008 10:36:54 -0600 (MDT)
Received: from [129.145.154.52] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0K7R0058SFH74FD0@mail-amer.sun.com> for All-ARCs@Sun.COM
 (ORCPT All-ARCs@Sun.COM); Thu, 25 Sep 2008 10:36:45 -0600 (MDT)
Date: Thu, 25 Sep 2008 09:36:43 -0700
From: Aarti Pai <Aarti.Pai@sun.com>
Subject: LSARC Approved Update Center 2 Toolkit - IPS Enhancements (2008/493)
Sender: Aarti.Pai@sun.com
To: Aarti Pai <Aarti.Pai@sun.com>
Reply-to: Aarti.Pai@sun.com
Message-id: <48DBBE1B.40309@Sun.COM>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_LXuhEh/d+a5/eGu/JA7jMw)"
X-PMX-Version: 5.4.1.325704
User-Agent: Thunderbird 2.0.0.14 (X11/20080505)
Content-Length: 1090
Status: RO
X-Status: $$$$
X-UID: 0000000003

This is a multi-part message in MIME format.

--Boundary_(ID_LXuhEh/d+a5/eGu/JA7jMw)
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

LSARC approved on 09/23/2008:
  Case: Update Center 2 Toolkit - IPS Enhancements (2008/493)  
<http://sac.sfbay/Archives/Minutes/LSARC/2008/20080923.html#case1>
  Incompatible Changes: none
  Precedent: none

If more information is needed, please contact the case owner/intern.

--Boundary_(ID_LXuhEh/d+a5/eGu/JA7jMw)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
LSARC approved on 09/23/2008:
<br>
&nbsp; Case: Update Center 2 Toolkit - IPS Enhancements (2008/493)&nbsp;<a
 href="http://sac.sfbay/Archives/Minutes/LSARC/2008/20080923.html#case1"></a><br>
&nbsp; Incompatible Changes: none
<br>
&nbsp; Precedent: none
<br>
<br>
If more information is needed, please contact the case owner/intern.
</body>
</html>

--Boundary_(ID_LXuhEh/d+a5/eGu/JA7jMw)--

