CLUE Definitions
draft-wenger-clue-definitions-02.txt

Abstract

This document collects terminology and definitions to be used consistently among documents produced in the CLUE working group.

Status of this Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on May 03, 2012.

Copyright Notice

Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

• 1. Introduction
• 2. Terminology
• 3. Definitions
• 4. Acknowledgements
• 5. IANA Considerations
• 6. Security Considerations
• 7. References
• Appendix A. Draft History
• Author's Address

1. Introduction

This document collects terminology and definitions to be used consistently among documents produced in the CLUE working group. The draft is intended to be a living document, to be updated as the working group discussions progress. It is not intended for publication as an RFC; instead, it is expected that definitions and terminology defined herein are going to be replicated in other CLUE documents.

All defined terms herein are captitalized. It is recommended that authors of other CLUE document follow this conventions when using definitions from this document.

It should be understood that the definitions herein are not to be interpreted as antedating design decisions to be made later. It's entierly reasonable that design choices conflicting with definitions in this draft may become necessary. In such cases, CLUE document authors can either request the definition be updated, or can simply avoid the use of a definition of this document. However, an author should never use a capitzalied definition as set forth herein with a different meaning in a different CLUE document.

2. Terminology

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].

3. Definitions

4. Acknowledgements

Most of this stuff is copied from the CLUE requirements and framework draft. Go there to look at dignitaries.

5. IANA Considerations

None

6. Security Considerations

None

7. References

Appendix A. Draft History

01: removed "stage direction" in "left" "right". Replaced with "to be interpreted in context".

clarified "local" to mean "in the same room" per J. Polk email 6/14/11

Consistently refer to "loudspeaker" per Christer's email 6/13/11

Added "keyboard" to listed caputure devices per Christer's email 6/13/11

Rendering device: changed "optical" to "visual". Hope Christer finds this OK. Per Christer's email 6/13/11

Note: the other changes proposed by Christer in his 6/13 email appear to change more than just words but semantics. Not included here as such semantic changes are best handled in the requirement and other docs.

Edt. Note: there have been lengthily discussions about the term "Participant". One camp wanted the word to refer to human users of telepresence equipment so to use intuitive language, the other (as this document) suggests to use the word in the RFC

Participant defined as per RFC 4353. I think this is what we arrived at on the mailing list, right?

Added "Telepresence Extensions" per long "solutions" thread.

00: Initial version; mostly copy-past from requirements-02.

Removed "session". Editors are advised to be specific about SIP, RTP, or whatever else sessions.

Made clear that Layout refers to rendering, not capturing.

added Left, Right, in stage direction, w/ Wikipedia reference

Author's Address