Title of Document

Status of This Document

This document provides information to the Grid community [topic]. [for non-recommendations track documents, add: It does not define any standards or technical recommendations.] Distribution is unlimited.

Obsoletes

This document obsoletes GFD-xxx [REFERENCE]. [If applicable]

Copyright Notice

Copyright © Open Grid Forum (applicable years). All Rights Reserved.

Abstract

Informative document abstract. Include an overview of the topic, the main issues addressed, and outcomes presented.

Contents

Abstract	1

1.	Introduction	2

2.	Notational Conventions	2

1.1	Header Level Two	2

3.	Security Considerations	2

4.	Contributors	2

5.	Glossary	2

6.	Intellectual Property Statement	2

7.	Disclaimer	3

8.	Full Copyright Notice	3

9.	References	3

Introduction

An overview of the document.

Notational Conventions

Only include this section if applicable.

The key words ‘MUST,” “MUST NOT,” “REQUIRED,” “SHALL,” “SHALL NOT,” “SHOULD,” “SHOULD NOT,” “RECOMMENDED,” “MAY,” and “OPTIONAL” are to be interpreted as described in RFC 2119 [BRADNER1]

Header Level Two

Header Level Three

Security Considerations

Please refer to RFC 3552 [RESCORLA] for guidance on writing a security considerations section. This section is required in all documents, and should not just say “there are no security considerations.” Quoting from the RFC:

“Most people speak of security as if it were a single monolithic property of a protocol or system, however, upon reflection, one realizes that it is clearly not true. Rather, security is a series of related but somewhat independent properties. Not all of these properties are required for every application.

We can loosely divide security goals into those related to protecting communications (COMMUNICATION SECURITY, also known as COMSEC) and those relating to protecting systems (ADMINISTRATIVE SECURITY or SYSTEM SECURITY). Since communications are carried out by systems and access to systems is through communications channels, these goals obviously interlock, but they can also be independently provided.”

Contributors

Contact information for authors. You can also use this section to recognize contributions by people who are not listed on the title page, but made a useful contribution (it’s OK to mention the nature of the contribution).

The actual Authors (or Editors) listed on the title page are those committed to taking permanent stewardship for this document – receiving communication in the future and otherwise being responsive to its content. The GFSG recommends at most three Author/Editors be listed on the title page, unless there are compelling reasons to list more.

Glossary

Recommended but not required.

Intellectual Property Statement

The OGF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the OGF Secretariat.

The OGF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this recommendation. Please address the information to the OGF Executive Director.

Disclaimer

This document and the information contained herein is provided on an “As Is” basis and the OGF disclaims all warranties, express or implied, including but not limited to any warranty that the use of the information herein will not infringe any rights or any implied warranties of merchantability or fitness for a particular purpose.

Full Copyright Notice

Copyright (C) Open Grid Forum (applicable years). All Rights Reserved.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the OGF or other organizations, except as needed for the purpose of developing Grid Recommendations in which case the procedures for copyrights defined in the OGF Document process must be followed, or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by the OGF or its successors or assignees.

References

Note that only permanent documents should be cited as references. Other items, such as Web pages or working groups, should be cited inline (i.e., see the Open Grid Forum, http://www.ogf.org). References should conform to a standard such as used by IEEE/ACM, MLA, Chicago or similar. Include an author, year, title, publisher, place of publication. For online materials, also add a URL. It is acceptable to separate out “normative references,” as IETF documents typically do. Some sample citations:

[BRADNER1] Bradner, S. Key Words for Use in RFCs to Indicate Requirement Levels, RFC 2119. March 1997.

[BRADNER2] Bradner, S. The Internet Standards Process – Revision 3, RFC 2026. October 1996.

[CATLETT] Catlett, C. GFD-1: Grid Forum Documents and Recommendations: Process and Requirements. Lemont, Illinois: Global Grid Forum. April 2002.

[RESCORLA] Rescorla, E. Guidelines for Writing RFC Text on Security Considerations. RFC 3552. July 2003.

GWD-TYPE	Author-1, Institution

Category: TYPE	Author-2, Institution

NAME_OF_WG_OR_RG	DATE

[if applicable: Revised DATE]

author@email.address	1

GWD-R, GWD-I or GWD-C	Author1, Institution

WG or RG or CG name	Author2, Institution

July 1, 2006
Updated: September 10, 2006

GWD-R, GWD-I or GWD-C	1 January 1970

example-wg@ogf.org	3

GGF Document Template

Charlie Catlett; Gregory B. Newby

2006-09-10

Greg Newby