From jb25718@sac.sfbay.sun.com Tue Dec 9 15:20:14 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mB9NKE5U003728 for ; Tue, 9 Dec 2008 15:20:14 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mB9NKE7V004956; Tue, 9 Dec 2008 15:20:14 -0800 (PST) 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 <0KBM00901U5QIS00@nwk-avmta-1.sfbay.Sun.COM>; Tue, 09 Dec 2008 15:20:14 -0800 (PST) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KBM002J7U5PQH90@nwk-avmta-1.sfbay.Sun.COM>; Tue, 09 Dec 2008 15:20:13 -0800 (PST) Received: from sac.sfbay.sun.com (new-sac.SFBay.Sun.COM [129.146.175.65]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mB9NKDPf058359; Tue, 09 Dec 2008 15:20:13 -0800 (PST) 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 mB9NKCuV003723; Tue, 09 Dec 2008 15:20:12 -0800 (PST) Received: (from jb25718@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id mB9NKCC5003719; Tue, 09 Dec 2008 15:20:12 -0800 (PST) Date: Tue, 09 Dec 2008 15:20:12 -0800 (PST) From: Jordan Brown Subject: CIFS Server: Client Side Caching Share Property [PSARC/2008/758 Self Review] To: PSARC-ext@sun.com Cc: cifs-eng@sun.com Message-id: <200812092320.mB9NKCC5003719@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 2695 I am sponsoring the following proposal. Because it supports a property defined by the CIFS protocol, uses names defined by the CIFS documentation, and required essentially no Solaris-side processing (only storing the value and providing it to clients), I believe it qualifies for automatic approval. This information is Copyright 2008 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Client-side caching share property 1.2. Name of Document Author/Supplier: Author: Alan Wright 1.3 Date of This Document: 8 December, 2008 4. Technical Description This fast-track proposes a new property for shares to provide per- share client-side caching (CSC) for offline files policy guidance to clients. Note that client-side caching is a client feature and the offline or cached files are managed entirely by clients. The property value has no meaning to the server, does not affect server behavior and the server does not and cannot control the caching or offline file policy implemented by clients. This property may be set on Windows servers and is required for compatibility and interoperability with Windows. The proposed csc property can take one of values described below. The value names and definitions are those used in the client-side caching for offline files documentation, for example, http://msdn.microsoft.com/en-us/library/aa369575(VS.85).aspx http://msdn.microsoft.com/en-us/library/cc212363.aspx csc=manual|auto|vdo|disabled manual Clients are allowed to cache files from the specified share for offline use as requested by users but automatic file-by-file reintegration is not allowed. This is the default setting. auto Clients are allowed to automatically cache files from the specified share for offline use and file-by-file reintegration is allowed. vdo Clients are allowed to automatically cache files from the specified share for offline use, file-by-file reintegration is allowed and clients are permitted to work from their local cache even while offline. disabled Client-side caching is not allowed for this share. Examples of setting the csc property using the sharemgr and zfs commands: sharemgr set -P smb -p csc=disabled -r zshare zgroup zfs sharesmb=csc=disabled tank/zvol 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: Automatic 6.6. ARC Exposure: open