[clue] Requirements are now an RFC!!
Paul Kyzivat <pkyzivat@alum.mit.edu> Fri, 18 April 2014 02:56 UTC
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D92C31A01E8 for <clue@ietfa.amsl.com>; Thu, 17 Apr 2014 19:56:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AMOI0sPBX13t for <clue@ietfa.amsl.com>; Thu, 17 Apr 2014 19:56:02 -0700 (PDT)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:211]) by ietfa.amsl.com (Postfix) with ESMTP id C81331A001E for <clue@ietf.org>; Thu, 17 Apr 2014 19:56:01 -0700 (PDT)
Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by QMTA11.westchester.pa.mail.comcast.net with comcast id rEey1n0060vyq2s5BEvxPk; Fri, 18 Apr 2014 02:55:57 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta05.westchester.pa.mail.comcast.net with comcast id rEvx1n00R3ZTu2S3REvxkE; Fri, 18 Apr 2014 02:55:57 +0000
Message-ID: <5350943D.6080600@alum.mit.edu>
Date: Thu, 17 Apr 2014 22:55:57 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: clue@ietf.org
References: <20140417230301.5294A18000C@rfc-editor.org>
In-Reply-To: <20140417230301.5294A18000C@rfc-editor.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1397789757; bh=EvU+K/oL9TPAC4qhDnWHOuwPOwgJQG5ixNdgCr1O7Pw=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=egeUY3e2C6Grf/HiYvDsLvpzWE9bpRV1hp87/TN6ymd8zXELynX2Z5BLVXd2WaVfc H0IVtimHSjeGLMpUnGqcfgK2QpoG71MRzjG+iNOPWgzqrs3ApPV97V7DfNxKJh4P+x ZB0YrC88hmPxNhTbNGVzMFL0+ITWc0bGZGwHjTevzrz6jxL1koj/8iL5uS2iysIZWq Iuqaj4WePLfFGI2VZv8eGSzZp5drAm9smYpIW/aKw8EPRoe8WmxIj79RMyUXQMDLmf 3pNiWY7uo5dVzzImT3HD4TNvh9JE3KYSrdx8Pqf/d/Dlb6Z+iH5K7y5wRY6ivxASCL IG/UWNG1xu+aA==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/F7yTh0hD0i3mCFbtSFxqRE-qBkY
Subject: [clue] Requirements are now an RFC!!
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 02:56:06 -0000
On 4/17/14 7:03 PM, rfc-editor@rfc-editor.org wrote: > A new Request for Comments is now available in online RFC libraries. > > > RFC 7205 > > Title: Use Cases for Telepresence Multistreams > Author: A. Romanow, S. Botzko, > M. Duckworth, R. Even, Ed. > Status: Informational > Stream: IETF > Date: April 2014 > Mailbox: allyn@cisco.com, > stephen.botzko@polycom.com, > mark.duckworth@polycom.com, > roni.even@mail01.huawei.com > Pages: 17 > Characters: 42087 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-ietf-clue-telepresence-use-cases-09.txt > > URL: http://www.rfc-editor.org/rfc/rfc7205.txt > > Telepresence conferencing systems seek to create an environment that > gives users (or user groups) that are not co-located a feeling of > co-located presence through multimedia communication that includes at > least audio and video signals of high fidelity. A number of > techniques for handling audio and video streams are used to create > this experience. When these techniques are not similar, > interoperability between different systems is difficult at best, and > often not possible. Conveying information about the relationships > between multiple streams of media would enable senders and receivers > to make choices to allow telepresence systems to interwork. This > memo describes the most typical and important use cases for sending > multiple streams in a telepresence conference. > > This document is a product of the ControLling mUltiple streams for tElepresence Working Group of the IETF. > > > INFORMATIONAL: This memo provides information for the Internet community. > It does not specify an Internet standard of any kind. Distribution of > this memo is unlimited. > > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > http://www.ietf.org/mailman/listinfo/ietf-announce > http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > > For searching the RFC series, see http://www.rfc-editor.org/search > For downloading RFCs, see http://www.rfc-editor.org/rfc.html > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > > The RFC Editor Team > Association Management Solutions, LLC > > > _______________________________________________ > clue mailing list > clue@ietf.org > https://www.ietf.org/mailman/listinfo/clue >
- [clue] RFC 7205 on Use Cases for Telepresence Mul… rfc-editor
- [clue] Requirements are now an RFC!! Paul Kyzivat
- Re: [clue] Requirements are now an RFC!! Mary Barnes
- Re: [clue] Requirements are now an RFC!! Paul Kyzivat