On 5. jun. 2015, at 10.12, Mirja Kühlewind mirja.kuehlew...@tik.ee.ethz.ch
wrote:
Okay, just to quickly clarify. In the charter only the word service is used.
We defined later on the words component and feature which are currently not
reflected in the charter. The part I've cited below,
Sorry for sending an extra email - I just had an extra thought and think this
is important to add:
Below:
On 5. jun. 2015, at 11.05, Michael Welzl mich...@ifi.uio.no wrote:
On 5. jun. 2015, at 10.12, Mirja Kühlewind mirja.kuehlew...@tik.ee.ethz.ch
wrote:
Okay, just to quickly
Am 04.06.2015 um 23:20 schrieb Joe Touch:
On 6/3/2015 10:45 PM, Marie-Jose Montpetit wrote:
In my presentation in Dallas I had suggested adding RTP (and even HTTP)
because as both Mirja and Christian mention some 'applications' are
requesting functionalities that are got given elsewhere.
On 05 Jun 2015, at 15:52, Michael Tuexen michael.tue...@lurchi.franken.de
wrote:
On 05 Jun 2015, at 15:39, Michael Welzl mich...@ifi.uio.no wrote:
On 05 Jun 2015, at 12:35, Michael Tuexen michael.tue...@lurchi.franken.de
wrote:
On 05 Jun 2015, at 11:05, Michael Welzl
On Friday, June 5, 2015 6:40 AM, Michael Welzl wrote:
...
Just for clarification: this wasn't about whether the level of protection
against
bit errors as such is important or not: I think the level of protection is a
less
important item to cover in the first document because, given
On 05 Jun 2015, at 16:03, Michael Welzl mich...@ifi.uio.no wrote:
On 05 Jun 2015, at 15:52, Michael Tuexen michael.tue...@lurchi.franken.de
wrote:
On 05 Jun 2015, at 15:39, Michael Welzl mich...@ifi.uio.no wrote:
On 05 Jun 2015, at 12:35, Michael Tuexen
On 6/5/2015 5:11 AM, Helge Backhaus wrote:
Am 04.06.2015 um 23:20 schrieb Joe Touch:
...
There are many services built on top of HTTP, at which point HTTP is just
another part of what this document calls a transport service.
As a result, unless you'll be describing every possible stack
On 6/5/2015 4:29 AM, Mirja Kühlewind wrote:
I do have the feeling that parts of what Joe wants to discuss should
however be in the third doc. And therefore I think that the current
first doc is not the taps flagship doc because for me a flagship doc
(and we probably need to define this term
I agree, the discussion should be better structured ...
On Fri, Jun 5, 2015 at 10:21 PM, Joe Touch to...@isi.edu wrote:
On 6/5/2015 12:53 PM, Mohamed Oulmahdi wrote:
On Thu, Jun 4, 2015 at 11:12 PM, Joe Touch to...@isi.edu
mailto:to...@isi.edu wrote:
On 6/3/2015 2:26 PM,
On 6/5/2015 12:53 PM, Mohamed Oulmahdi wrote:
On Thu, Jun 4, 2015 at 11:12 PM, Joe Touch to...@isi.edu
mailto:to...@isi.edu wrote:
On 6/3/2015 2:26 PM, Mohamed Oulmahdi wrote:
I think that speaking specifically about any protocol in this document
will not be in the
On Thu, Jun 4, 2015 at 11:12 PM, Joe Touch to...@isi.edu wrote:
On 6/3/2015 2:26 PM, Mohamed Oulmahdi wrote:
I think that speaking specifically about any protocol in this document
will not be in the sens of an abstract interface for the Transport
layer, because abstraction means that
On 5. jun. 2015, at 19.52, Michael Tuexen michael.tue...@lurchi.franken.de
wrote:
On 05 Jun 2015, at 16:03, Michael Welzl mich...@ifi.uio.no wrote:
On 05 Jun 2015, at 15:52, Michael Tuexen michael.tue...@lurchi.franken.de
wrote:
On 05 Jun 2015, at 15:39, Michael Welzl
On 2015-06-05 22:17, Michael Welzl wrote:
On 5. jun. 2015, at 19.52, Michael Tuexen michael.tue...@lurchi.franken.de
wrote:
On 05 Jun 2015, at 16:03, Michael Welzl mich...@ifi.uio.no wrote:
On 05 Jun 2015, at 15:52, Michael Tuexen michael.tue...@lurchi.franken.de
wrote:
On 05 Jun 2015,
I completely agree.
Marie-Jose Montpetit, Ph.D.
mari...@mit.edu
@SocialTVMIT
On Jun 6, 2015, at 12:12 AM, Anna Brunstrom anna.brunst...@kau.se wrote:
On 2015-06-05 22:17, Michael Welzl wrote:
On 5. jun. 2015, at 19.52, Michael Tuexen
michael.tue...@lurchi.franken.de wrote:
On 05 Jun
14 matches
Mail list logo
