PSARC Questions Version 1.22
Approved Oct. 2008 (PSARC/2008/625)

The 20 questions outline serves several purposes. One is to present to
the ARC in a uniform manner pertinent information about any case. Many
of the answers to these questions can be direct and specific references
to other case materials (although care must be taken to keep the
references current). A second purpose is to allow an ARC member to get
a concise overview of the case in an efficient manner. Another purpose
is that the 20 questions should provoke thought and questions for
project teams unfamiliar with the ARC process, by asking questions
about aspects of the project that need be considered. Lastly, the 20
questions serves as a vehicle between the case owner and the project
team as an indicator of preparedness. The 20 questions, as do other ARC
materials, remain as documentation of the case plan of record.


1.  What is the proposal being presented for review?

    * Give an overview of the project and its phase(s).
  
	This project proposes using symbolic links as reparse points
	to support a generic mechanism for namespace location redirection.
	Please refer to the PSARC 2009/387 case material for more details.

    * Describe the exposure (OpenSolaris), scope and type of review desired
      (overview, full case, etc.)

	The exposure is Nevada and this is a full case.

    * Indicate the release binding requested by the project team. See:

    	Minor binding is requested.

    * What are the project's deliverables?

	reparsed daemon
	libreparse.so library

    * How does this project align with existing or proposed ARC cases?

	PSARC 2009/399

2.  Describe user interactions.

    * Are new user interfaces being proposed, or existing interfaces being
      changed?

	Please refer to section 4 and 5 of reparse_spec.txt in the 2009/387 case
	material.

    * Are there any install time changes?
  
	No install time changes.

3.  What are the exported (defined by your project) and imported (defined by
    another project that your project then references) interfaces or protocols
    and their respective stability levels?  See:

	Please refer to the Interface table in the 2009/387 case material.

4. Describe any dependencies on hardware (e.g. SPARC exclusive), and on other
   projects within Solaris.

	There are no hardware or software dependencies.

5.  Projects need to be aware of the overall security of the system and how
    their components affect it. Which parts of this project are critical to
    the security of the system to avoid such unintended consequences such
    as unauthorized system entry, unauthorized access to or modification of
    data, elevation of privilege, denial of service, violation of labeled
    security, ...? Does this project require elevated privilege?

    A number of specific policies and practices address various aspects of
    the security of the system. They are found in appendix 1. Which of
    these are applicable to this project, and how are they addressed?

	Please refer to sections 5.7 through 5.10 and also section
	6 of reparse_spec.txt in the 2009/387 case material.

6.  Describe means of observing project functionality and performance, by
    an end user or by a system administrator.

	A test CLI program, rp, is being introduced that is intended
	for use in testing only.

7.  How does the project deal with faults and interruptions? Initialization
    and restarting?

	Please refer to section 5.7 of reparse_spec.txt in the 2009/387 case
	material.

8.  How does the project interact with Solaris virtualization technologies
    (xVM, LDOMs, zones, Branded zones, SunCluster, etc.)? 

	Please refer to section 5.10 of reparse_spec.txt in the 2009/387 case
	material.

9.  Does this project require administration (i.e., configuration or
    management)? If so,

	No special configuration or management is required.

10. Have you reviewed the Policies and Best Practices? Are there any
    exceptions this project needs? See

	No exceptions.