Network Database (netdata) -------------------------- Charter Last Modified: 05/10/1994 Current Status: Concluded Working Group Chair(s): Daisy Rose Service Applications Area Director(s): Dave Crocker Service Applications Area Advisor: Dave Crocker Mailing Lists: General Discussion:ietf-ndb@ucdavis.edu To Subscribe: ietf-ndb-request@ucdavis.edu Archive: Description of Working Group: The Network Database Working Group is chartered to define a standard interface among databases on TCP/IP internets. The working group will address the issue of database connectivity in a distributed environment which allows authorized users remote access to databases. It will be designed as a client/server model based on TCP/IP as its communication protocol. Several problems must be resolved that are associated with the network database protocol, such as management of multiple threads between clients and servers, management of multiple servers, management of data buffers, data conversions, and security. Additional related problems will be covered as the discussion goes on. Therefore, the description and the schedule can be revised. This working group is independent from the SQL access group; however, there may be some overlapping interest. The SQL access group is welcome to join IETF's discussions and share information in both directions. If both groups find that merging two efforts into one will speed up the process, the merge can be done in the future. For now, this working group works on issues according to its own schedule and efforts. Goals and Milestones: Done Review and approve the charter, making any changes necessary. Examine needs, resources for this network database protocol and define the scope of work. Begin work on a framework for the solution. Assign writing assignments for first draft of the document. Done First draft to be completed. Done Review first draft document, determine necessary revisions. Discuss problems remained unsolved from the first IETF meeting. Done Continue revisions based on comments received at meeting and e-mail. Start making document an Internet-Draft. MAR 92 Review final draft. If it is OK, give it to IESG for publication as an RFC. JUN 92 Revise document based on implementations. Ask IESG to make the revision a Draft Standard. Internet-Drafts: No Current Internet-Drafts. Request For Comments: None to date.