Common Internet File System (CIFS) Browser Auxiliary Protocol Optionally used by Browser Service to query configuration information for the domains from the domain master browser server. Common Internet File System (CIFS) Protocol Specification Defines the Common Internet File System (CIFS), a protocol that provides a mechanism for client systems to use file and print services made available by server systems over a network. Distributed File System (DFS): Referral Protocol Specification Allows file system clients to resolve names from a namespace distributed across many servers and geographies into local names on specific file servers. File System Algorithms Algorithms used by the object stores that back the protocols specified by the documents and [MS-CIFS]. These algorithms specify the behavior of operations like CreateFile, ReadFile, Close, and so on. These algorithms specify state, events,
HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV) Defines HTTP protocol extensions that enable users to collaboratively edit and manage files on remote web servers. Web Distributed Authoring and Versioning (WebDAV) Protocol: Client Extensions Extensions defined in this specification extend the WebDAV Protocol, as specified in [RFC4918]. Web Distributed Authoring and Versioning (WebDAV) Protocol: Microsoft Extensions Documents more extensions to the WebDAV Protocol. Web Distributed Authoring and Versioning (WebDAV) Protocol: Server Extensions Extends WebDAV by introducing new HTTP request and response headers that both enable file types that are not currently manageable and optimize protocol interactions for file system clients. Member Protocol Roles This section describes all member protocol roles. The Remote Administration (RAP) Protocol (as described in ) is an administrative protocol whose function has largely been replaced by newer protocols. In the File Access Services System, RAP is used by legacy systems as a discovery protocol. RAP also supports certain client and server administration methods, such as SMB file share enumeration, but this functionality has been superseded by the
Open a File in an NFS File Share This use case supports the Two Applications Communicate via a Shared File use case (section ). The application accesses a file the NFS version 2 protocol , or the NFS version 3 protocol . Context of Use: To open or create a file when the User has located a shared directory and wants to open or create a file in that directory using an NFS network access protocol. Goal: To open or create a file in an NFS network share directory. Actors Application File Client NFS File Service Authentication Service Active Directory Service Stakeholders User Preconditions The client and server computers are configured in a domain. An NFS file share has been created on the file server. The User has located the path to the file on the NFS file share and has determined the desired open type (for example, "create a new file" or "open existing file"). Main Success Scenario Trigger: Based on the User interaction, the Application determines whether to open or create a file in a target directory. The Application resolves the target directory using a set of LOOKUP requests as described in [RFC1094] section 2.2.5 or [RFC1813] section 2.5.3 to resolve each component of the path. The Application directs the file client to send a request to NFS File Service in order to accomplish one of the following options, depending upon the requested operation type. Each operation returns a file handle to the Application. (Create) Creation of the new file using the CREATE request as described in [RFC1094] section 2.2.10 or [RFC1813] section 3.3.8. (Open) Resolution of the file name (final path component) using the LOOKUP request as described in [RFC1094] section 2.2.5 or [RFC1813] section 3.3. The NFS File Service performs the create operation and returns a file handle to the Application. Post Condition A file is created or opened in an NFS network share directory. Extensions
Index A Access a file in a domain 23 23 Access a file in a workgroup 20 20 Access a remote file using webdav 27 27 40 14 Architecture ( 9, 9) 19 C 39 58 40 40 17 18 18 18 Concepts ( 9, 9) 39 Considerations 40 40 D Dependencies 18 18 Design intent 23 20 27 20 25 E 17 Error handling 39 40 40 41 Extensibility 57 39 57 18 F 9 Functional architecture ( 9, 9) 9 G 6 I 57 40 6 19 40 5 M 57 O Overview 41 16 14 9 P 19 57 9 R 6 Requirements 40 9 19 40 S 40 14 System architecture ( 9, 9) 40 17 18 18 System overview 5 14 9 System use cases 23 20 27 20