One document matched: draft-even-clue-sdp-clue-relation-00.txt

CLUE WG                                                          R. Even
Internet-Draft                                                    Huawei
Intended status: Informational                          October 15, 2012
Expires: April 18, 2013


                Signalling of CLUE and SDP offer/answer
                draft-even-clue-sdp-clue-relation-00.txt

Abstract

   This document describes the relation between the different CLUE
   attributes as specified in the CLUE framework and the SDP attrbutes.
   The document will discuss the issues with the CLUE call signalling in
   order to keep the consisyency bewteen the Offer/answer state and the
   CLUE state.

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 April 18, 2013.

Copyright Notice

   Copyright (c) 2012 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.



Even                     Expires April 18, 2013                 [Page 1]

Internet-Draft     SDP offer/answer and CLUE relation       October 2012


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Capture attributes  . . . . . . . . . . . . . . . . . . . . . . 3
   3.  Encoding parameters . . . . . . . . . . . . . . . . . . . . . . 3
   4.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 3
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
   7.  Security Considerations . . . . . . . . . . . . . . . . . . . . 3
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 4
     8.1.  Normative References  . . . . . . . . . . . . . . . . . . . 4
     8.2.  Informative References  . . . . . . . . . . . . . . . . . . 4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 4






































Even                     Expires April 18, 2013                 [Page 2]

Internet-Draft     SDP offer/answer and CLUE relation       October 2012


1.  Introduction

   The CLUE framework[I-D.ietf-clue-framework] is used to specify the
   infirmation needed for creating a Telepresence call.  The model
   includes the Media capture information providing information about
   content of the streams and can provide information about the spatial
   information between streams based on the capture point and area of
   capture.  A capture scene includes media captures that are part of a
   same scene e.g. room capture or presentation.

   The other infprmation defined in the framework is the Encoding
   information providing information about the abilities of the
   providers to send streams allowing a consumer to configure a capture
   to a specific encoding.

   The next sections will look at the capture attributes and the
   encoding parameter and decsribe the realtion to SDP [RFC4566].


2.  Capture attributes


3.  Encoding parameters


4.  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 RFC2119[RFC2119] and
   indicate requirement levels for compliant RTP implementations.


5.  Acknowledgements

   place holder


6.  IANA Considerations

   TBD


7.  Security Considerations

   TBD.





Even                     Expires April 18, 2013                 [Page 3]

Internet-Draft     SDP offer/answer and CLUE relation       October 2012


8.  References

8.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC3264]  Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
              with Session Description Protocol (SDP)", RFC 3264,
              June 2002.

   [RFC4566]  Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
              Description Protocol", RFC 4566, July 2006.

8.2.  Informative References

   [I-D.ietf-clue-framework]
              Romanow, A., Duckworth, M., Pepperell, A., and B. Baldino,
              "Framework for Telepresence Multi-Streams",
              draft-ietf-clue-framework-06 (work in progress),
              July 2012.


Author's Address

   Roni Even
   Huawei
   Tel Aviv,
   Israel

   Email: roni.even@mail01.huawei.com




















Even                     Expires April 18, 2013                 [Page 4]