From: "Christian Hoene" <hoene@uni-tuebingen.de>
To: "'BlueZ development'" <bluez-devel@lists.sourceforge.net>,
<ekiga-devel-list@gnome.org>
Cc: Frans de Bont <frans.de.bont@philips.com>
Subject: [Bluez-devel] Talk on SBC at the next IETF meeting in Minneapolis
Date: Wed, 5 Nov 2008 10:02:18 +0100 [thread overview]
Message-ID: <00f401c93f25$38ac0ff0$aa042fd0$@de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2303 bytes --]
Hello,
I just like to inform you that I am going to present the Bluetooth SBC codec
at the next IETF conference. I will also talk about BlueZ open source
implementation and its Ekiga plugin.
With best regards,
Christian
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Roni
Even
Sent: Tuesday, November 04, 2008 6:58 PM
To: avt@ietf.org
Cc: 'Tom Taylor'
Subject: [AVT] Draft agenda for Minneapolis
Hi,
I prepared a draft agenda and will submit it tomorrow afternoon
See if you have comments
Roni Even
Audio/Video Transport (AVT) Working Group
=========================================
CHAIRS: Tom Taylor <tom.taylor@rogers.com>
Roni Even <ron.even.tlv@gmail.com>
AGENDA
Monday, 17 November 2008 at 15:20-17:20 (Salon AB)
--------------------------------------------------
15:20 Introduction and Status Update (Chairs, 15)
15:35 RTP Payload Format for SVC Video (Schierl, 15)
draft-ietf-avt-rtp-svc-15
15:50 RTP Payload Format for H.264 Video (Ye-Kui, 10)
draft-ietf-avt-rtp-rfc3984bis-01
16:00 Multi-Session and Multi-source transmission (Schierl, 10)
draft-schierl-avt-rtp-multi-session-transmission-00
16:10 Rapid Synchronisation of RTP Flows (Even, 10)
draft-perkins-avt-rapid-rtp-sync-00
16:20 Rapid Synchronization with RTP Multicast Sessions(Ver Steeg, 15)
draft-versteeg-avt-rapid-synchronization-for-rtp-01
16:35 RTCP Feedback Mechanism for Burst Streaming (Levin, 15)
draft-levin-avt-rtcp-burst-00
16:50 RTP Payload Format for Bluetooth's SBC audio codec (Hoene, 10)
draft-hoene-avt-rtp-sbc-00
17:00 End
Tuesday, 18 November 2008 at 17:10-18:10 (Salon AB)
---------------------------------------------------
17:10 RTCP XR (Clarck, 20)
draft-ietf-avt-rtcp-xr-*
17:30 RTP Payload format for Application and Desktop Sharing(Boyaci, 20)
draft-boyaci-avt-app-sharing-00
17:50 SRTP Store and Forward (Blom, 10)
draft-mattsson-srtp-store-and-forward-01
18:00 End
[-- Attachment #1.2: Type: text/html, Size: 10122 bytes --]
[-- Attachment #2: ATT00208.txt --]
[-- Type: text/plain, Size: 139 bytes --]
_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt
[-- Attachment #3: Type: text/plain, Size: 363 bytes --]
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
[-- Attachment #4: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
reply other threads:[~2008-11-05 9:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00f401c93f25$38ac0ff0$aa042fd0$@de' \
--to=hoene@uni-tuebingen.de \
--cc=bluez-devel@lists.sourceforge.net \
--cc=ekiga-devel-list@gnome.org \
--cc=frans.de.bont@philips.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox