From Jordan.Brown@sun.com Wed Oct 7 10:10:54 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n97HAsWw004974 for ; Wed, 7 Oct 2009 10:10:54 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n97HAp3h044236 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Wed, 7 Oct 2009 11:10:54 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KR500J0LME5DI00@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 07 Oct 2009 10:10:53 -0700 (PDT) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KR500D0EME47HA0@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 07 Oct 2009 10:10:52 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n97HAqmA017954 for ; Wed, 07 Oct 2009 10:10:52 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KR500100KV86V00@fe-sfbay-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 07 Oct 2009 10:10:52 -0700 (PDT) Received: from [129.145.155.154] ([unknown] [129.145.155.154]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KR500MGJMDZMVE0@fe-sfbay-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Wed, 07 Oct 2009 10:10:47 -0700 (PDT) Date: Wed, 07 Oct 2009 10:10:47 -0700 From: Jordan Brown Subject: PSARC 2009/534 - SMB/CIFS Standalone DFS Sender: Jordan.Brown@sun.com To: PSARC-ext@sun.com Message-id: <4ACCCB97.9030301@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.14 (X11/20080505) Status: RO Content-Length: 10093 [ Somehow the automatic message didn't go out. ] I'm sponsoring the following for fast track approval. The timer expires 14 October 2009. Template Version: @(#)onepager.txt 1.35 07/11/07 SMI Copyright 2007 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: SMB/CIFS Standalone DFS 1.2. Name of Document Author/Supplier: Author: Afshin Salek 1.3. Date of This Document: 10/01/09 1.4. Name of Major Document Customer(s)/Consumer(s): PSARC CIFS team 1.5. Email Aliases: 1.5.1. Responsible Manager: Barry.Greenberg@Sun.COM 1.5.2. Responsible Engineer: Afshin.Ardakani@Sun.COM 1.5.3. Marketing Manager: 1.5.4. Interest List: cifs-team@sun.com A patch binding is requested for this change. 4. Technical Description: 4.1. Details: This is a follow on case to PSARC 2009/399 "Reparse Points and Referral Umbrella Case" to introduce support for SMB/CIFS standalone DFS namespaces. INTRODUCTION The Distributed File System (DFS) is a Microsoft technology delivered over the SMB/CIFS and MSRPC protocols. DFS allows administrators to group shared folders located on different servers by transparently connecting them to one or more DFS namespaces. A DFS namespace is a virtual view of shared folders in an organization. An administrator can select which shared folders to present in the namespace, design the hierarchy in which those folders appear and determine the names that the shared folders show in the namespace. When a user views the namespace, the folders appear to reside in a single, high-capacity file system. Users can navigate the folders in the namespace without needing to know the server names or shared folders hosting the data. DFS also provides many other benefits, including fault tolerance and load-sharing capabilities, making it an attractive feature for many organizations. DFS TERMINOLOGY DFS namespace A virtual view of shared folders on different servers as provided by DFS. A DFS namespace consists of a root and many links and targets. The namespace starts with a root that maps to one or more root targets. Below the root are links that map to their own targets. DFS link A component in a DFS path that lies below the root and maps to one or more link targets. DFS path Any Universal Naming Convention (UNC) path that starts with a DFS root. DFS root The starting point of the DFS namespace. The root is often used to refer to the namespace as a whole. A root maps to one or more root targets, each of which corresponds to a shared folder on a separate server. A DFS root has one of the following formats: \\ServerName\RootName or \\DomainName\RootName. domain-based DFS namespace A DFS namespace that has configuration information stored in Active Directory (AD). The path to access the root or a link starts with the host domain name. A domain-based DFS root can have multiple root targets, which offers fault tolerance and load sharing. link referral A type of referral that contains a list of link targets for a particular link. link target The mapping destination of a link. A link target can be any UNC path. For example, a link target could be a shared folder or another DFS path. referral A list of targets, transparent to the user, that a DFS client receives from DFS when the user is accessing a root or a link in the DFS namespace. Referral information may be cached on DFS clients for a time period specified in the DFS configuration. root referral A type of referral that contains a list of root targets for a particular root. root target A physical server that hosts a DFS namespace. A domain-based DFS root can have multiple root targets, whereas a standalone DFS root can only have one root target. Root targets are also called root servers. standalone DFS namespace A DFS namespace whose configuration information is stored locally on the the root server. The path to access the root or a link starts with the root server name. A standalone DFS root has only one root target. Standalone roots are not fault tolerant; when the root target is unavailable, the entire DFS namespace is inaccessible. Fault tolerance can be added externally with the use of server clusters. SIMPLIFIED REFERRAL PROCESS FOR STANDALONE NAMESPACES 1. A user attempts to access a DFS path, such as by typing \\Software\Public\Documents in the Run dialog box. 2. The DFS client computer sends a query to the root server hosting the standalone namespace. 3. The root server returns a root referral to the client. The root referral contains the single root target. 4. The client requests a link target from the root server. 5. The root server constructs a list of link targets in the referral and returns this to the client. 6. The client selects a link target and establishes a connection. STANDALONE NAMESPACES IN SOLARIS The DFS root is a share that must reside on a ZFS dataset. A new boolean share property, dfsroot, will mark a share as a DFS root share to distinguish it from regular shares. The dfsroot property will not be defined by default, which is equivalent to a value of false. The dfsroot property can be managed locally, as a share property, or by Windows clients using Windows utilities to connect to the DFS and SRVSVC MSRPC services, which are available in the CIFS Service (PSARC 2006/715). DFS root shares need to be distinguished from regular shares so that the server can indicate to clients that a particular share is a DFS root share, which is done with a flag on tree connect responses. When connected to a DFS root share, clients use UNC paths to access objects within the namespace rather than relative paths. With regular shares, paths are assumed to be relative to the shared directory. Also, for compatibility with Windows behavior, DFS root shares cannot be removed or unshared remotely over SMB and MSRPC. Local management will be no different from regular shares. Only one standalone DFS namespace is supported per system. Multiple DFS namespace support will be available in a future project based on Active Directory (AD) domain-based DFS namespaces. Once domain-based namespaces are supported, the CIFS Service will also support multiple standalone DFS namespaces - these are tied together by the DFS support level that is announced by a server. DFS links within a namespace are represented using reparse points (PSARC 2009/387). The service type will be smb-dfs and a reparse plugin will be delivered to support this service type. The link target format used to store smb-dfs service type data can be considered opaque, even though it will be visible in the reparse point, since no local tools will be provided to create or manage DFS referrals and they will be interpreted by the dfs-smb reparse point plugin library. DFS referrals will be managed using Windows desktop or command line utilities and the referral content will be driven by the data that needs to be stored on behalf of the management applications. INTERFACE TABLE Imported interfaces |Specified | |in what | Interface Name |Document? |Comments ============================================================ XAT_REPARSE |PSARC 2009/387 |Reparse extensible |Private |attribute | | reparse_kderef |PSARC 2009/387 |Reparse kernel reparse_init | |routines reparse_parse | | reparse_free | | | | /usr/lib/ |PSARC 2009/387 |Reparse library libreparse.so.1 | |routines and ops | | Exported interfaces |Proposed |Specified | |Stability |in what | Interface Name |Classification |Document? | Comments ============================================================================== reparse point syntax |Committed | |Service type "smb-dfs" for DFS referrals |Private | | | | | /usr/lib/reparse/ |Committed | |Reparse point plugin libsmb_dfs.so.1 |Private | | | | | REFERENCES [1] DFS Technical Reference http://technet.microsoft.com/en-us/library/cc757042(WS.10).aspx [2] Distributed File System (DFS): Namespace Management Protocol Specification http://msdn.microsoft.com/en-us/library/cc227078%28PROT.10%29.aspx [3] Distributed File System (DFS): Referral Protocol Specification http://msdn.microsoft.com/en-us/library/cc226982(PROT.10).aspx 4.2. Bug/RFE Number(s): 6711751 4.6. Doc Impact: Solaris CIFS Administration Guide Modifications to sharemgr(1M) man page: ------------------------------------------------------------------- The general properties supported for SMB are: + dfsroot=boolean + + Marks a share as a DFS root share to distinguish it from regular + shares. dfsroot is not defined by default. If dfsroot is false + or not defined, the share is not a dfs root share. 6. Resources and Schedule: 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: ON 6.5. ARC review type: FastTrack From glenn.skinner@sun.com Wed Oct 7 12:26:55 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n97JQsbH008755 for ; Wed, 7 Oct 2009 12:26:54 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n97JQq9G061349; Wed, 7 Oct 2009 13:26:54 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KR500401SOT5B00@nwk-avmta-2.sfbay.sun.com>; Wed, 07 Oct 2009 12:26:53 -0700 (PDT) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KR5000XHSOTUF30@nwk-avmta-2.sfbay.sun.com>; Wed, 07 Oct 2009 12:26:53 -0700 (PDT) Received: from ivrel.sfbay.sun.com (ivrel.SFBay.Sun.COM [129.146.74.76]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n97JQr3A040943; Wed, 07 Oct 2009 12:26:53 -0700 (PDT) Received: from ivrel (ivrel [129.146.74.76]) by ivrel.sfbay.sun.com (8.14.3+Sun/8.14.3) with SMTP id n97JJNsU005959; Wed, 07 Oct 2009 12:19:23 -0700 (PDT) Date: Wed, 07 Oct 2009 12:19:23 -0700 (PDT) From: Glenn Skinner Subject: Re: 2009/534 - SMB/CIFS Standalone DFS To: PSARC-ext@sun.com, Jordan.Brown@sun.com Cc: cifs-eng@sun.com Reply-to: Glenn Skinner Message-id: <200910071919.n97JJNsU005959@ivrel.sfbay.sun.com> MIME-version: 1.0 X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.6_36 SunOS 5.11 sun4u sparc Content-type: TEXT/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-MD5: TEM8V3FZ3tIpN30NLAFjWg== X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 920 Date: Wed, 07 Oct 2009 10:10:47 -0700 From: Jordan Brown Subject: PSARC 2009/534 - SMB/CIFS Standalone DFS To: PSARC-ext@sun.com I'm sponsoring the following for fast track approval. The timer expires 14 October 2009. ... STANDALONE NAMESPACES IN SOLARIS ... Only one standalone DFS namespace is supported per system. Multiple DFS namespace support will be available in a future project based on Active Directory (AD) domain-based DFS namespaces. Once domain-based namespaces are supported, the CIFS Service will also support multiple standalone DFS namespaces - these are tied together by the DFS support level that is announced by a server. When I saw "per system" above, it made me wonder about zones. So, could you say a a bit about how zones interact with this feature (and what changes you anticipate when AD support is added)? -- Glenn From Afshin.Ardakani@sun.com Wed Oct 7 12:47:35 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n97JlYQc009027 for ; Wed, 7 Oct 2009 12:47:34 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n97JlVJp007567; Wed, 7 Oct 2009 13:47:34 -0600 (MDT) 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 <0KR500J09TNAK100@brm-avmta-1.central.sun.com>; Wed, 07 Oct 2009 13:47:34 -0600 (MDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KR500L5DTN9IXY2@brm-avmta-1.central.sun.com>; Wed, 07 Oct 2009 13:47:34 -0600 (MDT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n97JlSrl007688; Wed, 07 Oct 2009 12:47:28 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KR500K00TJ9XA00@fe-sfbay-10.sun.com>; Wed, 07 Oct 2009 12:47:28 -0700 (PDT) Received: from [10.1.106.212] ([unknown] [10.1.106.212]) by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KR500M7QTN3O100@fe-sfbay-10.sun.com>; Wed, 07 Oct 2009 12:47:27 -0700 (PDT) Date: Wed, 07 Oct 2009 12:47:08 -0700 From: Afshin Salek Subject: Re: 2009/534 - SMB/CIFS Standalone DFS In-reply-to: <200910071919.n97JJNsU005959@ivrel.sfbay.sun.com> Sender: Afshin.Ardakani@sun.com To: Glenn Skinner Cc: PSARC-ext@sun.com, Jordan.Brown@sun.com, cifs-eng@sun.com Message-id: <4ACCF03C.9010606@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200910071919.n97JJNsU005959@ivrel.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.9 (X11/20080213) Status: RO Content-Length: 1449 Currently, CIFS service is only supported for the global zone so DFS support is only available in the global zone as well. When AD support is added, DFS namespace will be created and managed on AD domain controller instead of the Solaris system running CIFS server. CIFS server as a root server obtains the namespace information from AD domain controller using LDAP queries. So, most changes for supporting AD would be internal to CIFS server. Afshin Glenn Skinner wrote: > Date: Wed, 07 Oct 2009 10:10:47 -0700 > From: Jordan Brown > Subject: PSARC 2009/534 - SMB/CIFS Standalone DFS > To: PSARC-ext@sun.com > > I'm sponsoring the following for fast track approval. The timer > expires 14 October 2009. > > ... > STANDALONE NAMESPACES IN SOLARIS > > ... > Only one standalone DFS namespace is supported per system. > Multiple DFS namespace support will be available in a future > project based on Active Directory (AD) domain-based DFS > namespaces. Once domain-based namespaces are supported, the > CIFS Service will also support multiple standalone DFS > namespaces - these are tied together by the DFS support level > that is announced by a server. > > When I saw "per system" above, it made me wonder about zones. > > So, could you say a a bit about how zones interact with this feature > (and what changes you anticipate when AD support is added)? > > -- Glenn > From Jordan.Brown@sun.com Tue Oct 13 15:26:39 2009 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 n9DMQd59011990 for ; Tue, 13 Oct 2009 15:26:39 -0700 (PDT) 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.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id n9DMQYIb019727 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Tue, 13 Oct 2009 15:26:39 -0700 (PDT) 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 <0KRH00F3950E5W00@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 13 Oct 2009 15:26:38 -0700 (PDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KRH008PT50DZO30@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 13 Oct 2009 15:26:37 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n9DMQb2C028494 for ; Tue, 13 Oct 2009 15:26:37 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KRH000004OFVJ00@fe-sfbay-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 13 Oct 2009 15:26:37 -0700 (PDT) Received: from [129.145.155.154] ([unknown] [129.145.155.154]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KRH00DJ450CXMC0@fe-sfbay-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 13 Oct 2009 15:26:37 -0700 (PDT) Date: Tue, 13 Oct 2009 15:26:36 -0700 From: Jordan Brown Subject: 2009/534 SMB/CIFS DFS - hello? Sender: Jordan.Brown@sun.com To: psarc-ext@sun.com Message-id: <4AD4FE9C.80007@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.14 (X11/20080505) Status: RO Content-Length: 267 There's been one comment on this case, last Wednesday, that's been responded to. There's no meeting tomorrow, and that's when the timer expires. If I get two(?) +1s, the case is automatically approved when the timer expires, right? Can I have those +1s, please? From glenn.skinner@Sun.COM Tue Oct 13 15:43:07 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n9DMh5jB012082 for ; Tue, 13 Oct 2009 15:43:06 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n9DMguK1000399 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Wed, 14 Oct 2009 06:43:04 +0800 (SGT) 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 <0KRH00H0N5RRE500@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 13 Oct 2009 15:43:03 -0700 (PDT) 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 <0KRH008N55RQZQ40@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Tue, 13 Oct 2009 15:43:02 -0700 (PDT) Received: from ivrel.sfbay.sun.com (ivrel.SFBay.Sun.COM [129.146.74.76]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n9DMh2i7060809; Tue, 13 Oct 2009 15:43:02 -0700 (PDT) Received: from ivrel (ivrel [129.146.74.76]) by ivrel.sfbay.sun.com (8.14.3+Sun/8.14.3) with SMTP id n9DMZW0v015768; Tue, 13 Oct 2009 15:35:32 -0700 (PDT) Date: Tue, 13 Oct 2009 15:35:32 -0700 (PDT) From: Glenn Skinner Subject: Re: 2009/534 SMB/CIFS DFS - hello? To: psarc-ext@Sun.COM, Jordan.Brown@Sun.COM Reply-to: Glenn Skinner Message-id: <200910132235.n9DMZW0v015768@ivrel.sfbay.sun.com> MIME-version: 1.0 X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.6_36 SunOS 5.11 sun4u sparc Content-type: TEXT/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-MD5: stNQMChTFFHcGeOVRrG/hw== X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 474 Date: Tue, 13 Oct 2009 15:26:36 -0700 From: Jordan Brown Subject: 2009/534 SMB/CIFS DFS - hello? There's been one comment on this case, last Wednesday, that's been responded to. There's no meeting tomorrow, and that's when the timer expires. If I get two(?) +1s, the case is automatically approved when the timer expires, right? Can I have those +1s, please? Here's one (and you only need one). -- Glenn From Jordan.Brown@sun.com Mon Oct 19 17:02:08 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n9K028aG018612 for ; Mon, 19 Oct 2009 17:02:08 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n9K026fl062882 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Mon, 19 Oct 2009 18:02:07 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KRS0030FDFIG300@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 19 Oct 2009 17:02:06 -0700 (PDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KRS00E1TDFIVP80@nwk-avmta-2.sfbay.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 19 Oct 2009 17:02:06 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n9K026qh010905 for ; Mon, 19 Oct 2009 17:02:06 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KRS00700DFAA100@fe-sfbay-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 19 Oct 2009 17:02:06 -0700 (PDT) Received: from [129.145.155.154] ([unknown] [129.145.155.154]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KRS00IM1DFH51C0@fe-sfbay-09.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@sun.com); Mon, 19 Oct 2009 17:02:06 -0700 (PDT) Date: Mon, 19 Oct 2009 17:02:05 -0700 From: Jordan Brown Subject: 2009/534 - SMB/CIFS Standalone DFS Sender: Jordan.Brown@sun.com To: psarc-ext@sun.com Message-id: <4ADCFDFD.4010107@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.14 (X11/20080505) Status: RO Content-Length: 49 One +1, no complaints, timer expired - Approved.