Re: [Taps] I-D Action: draft-ietf-taps-transports-04.txt

I completely agree. Marie-Jose Montpetit, Ph.D. mari...@mit.edu @SocialTVMIT > On Jun 6, 2015, at 12:12 AM, Anna Brunstrom wrote: > > > On 2015-06-05 22:17, Michael Welzl wrote: >>> On 5. jun. 2015, at 19.52, Michael Tuexen >>> wrote: >>> On 05 Jun 2015, at 16:03, Michael Welzl wrote:

Re: [Taps] I-D Action: draft-ietf-taps-transports-04.txt

On 2015-06-05 22:17, Michael Welzl wrote: On 5. jun. 2015, at 19.52, Michael Tuexen wrote: On 05 Jun 2015, at 16:03, Michael Welzl wrote: On 05 Jun 2015, at 15:52, Michael Tuexen wrote: On 05 Jun 2015, at 15:39, Michael Welzl wrote: On 05 Jun 2015, at 12:35, Michael Tuexen wrot

Re: [Taps] I-D Action: draft-ietf-taps-transports-04.txt

> On 05 Jun 2015, at 22:17, Michael Welzl wrote: > > >> On 5. jun. 2015, at 19.52, Michael Tuexen >> wrote: >> >>> On 05 Jun 2015, at 16:03, Michael Welzl wrote: >>> >>> On 05 Jun 2015, at 15:52, Michael Tuexen wrote: > On 05 Jun 2015, at 15:39, Michael Welzl wrote:

Re: [Taps] A proposal to throw out RTP

I agree, the discussion should be better structured ... On Fri, Jun 5, 2015 at 10:21 PM, Joe Touch wrote: > > > On 6/5/2015 12:53 PM, Mohamed Oulmahdi wrote: > > > > > > On Thu, Jun 4, 2015 at 11:12 PM, Joe Touch > > wrote: > > > > > > > > On 6/3/2015 2:26 PM, Mohamed

Re: [Taps] A proposal to throw out RTP

On 6/5/2015 12:53 PM, Mohamed Oulmahdi wrote: > > > On Thu, Jun 4, 2015 at 11:12 PM, Joe Touch > 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 se

Re: [Taps] I-D Action: draft-ietf-taps-transports-04.txt

> On 5. jun. 2015, at 19.52, Michael Tuexen > wrote: > >> On 05 Jun 2015, at 16:03, Michael Welzl wrote: >> >> >>> On 05 Jun 2015, at 15:52, Michael Tuexen >>> wrote: >>> On 05 Jun 2015, at 15:39, Michael Welzl wrote: > On 05 Jun 2015, at 12:35, Michael Tuexen >

Re: [Taps] A proposal to throw out RTP

On Thu, Jun 4, 2015 at 11:12 PM, Joe Touch 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 applic

Re: [Taps] I-D Action: draft-ietf-taps-transports-04.txt

> On 05 Jun 2015, at 16:03, Michael Welzl wrote: > > >> On 05 Jun 2015, at 15:52, Michael Tuexen >> wrote: >> >>> On 05 Jun 2015, at 15:39, Michael Welzl wrote: >>> >>> On 05 Jun 2015, at 12:35, Michael Tuexen wrote: > On 05 Jun 2015, at 11:05, Michael Welzl wrote: >

Re: [Taps] I-D Action: draft-ietf-taps-transports-04.txt

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, giv

Re: [Taps] A proposal to throw out RTP

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

Re: [Taps] I-D Action: draft-ietf-taps-transports-04.txt

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 te

Re: [Taps] TAPS Transports and ICMP

On 6/5/2015 12:25 AM, Pal Martinsen (palmarti) wrote: > >> On 04 Jun 2015, at 22:56, Joe Touch > > wrote: >> >> >> >> On 6/4/2015 12:51 PM, Pal Martinsen (palmarti) wrote: >>> On 04 Jun 2015, at 21:17, Joe Touch >>> > wrote: On

Re: [Taps] I-D Action: draft-ietf-taps-transports-04.txt

> On 05 Jun 2015, at 15:52, Michael Tuexen > wrote: > >> On 05 Jun 2015, at 15:39, Michael Welzl wrote: >> >> >>> On 05 Jun 2015, at 12:35, Michael Tuexen >>> wrote: >>> On 05 Jun 2015, at 11:05, Michael Welzl wrote: > On 5. jun. 2015, at 10.12, Mirja Kühlewind

Re: [Taps] I-D Action: draft-ietf-taps-transports-04.txt

> On 05 Jun 2015, at 15:39, Michael Welzl wrote: > > >> On 05 Jun 2015, at 12:35, Michael Tuexen >> wrote: >> >>> On 05 Jun 2015, at 11:05, Michael Welzl wrote: >>> >>> On 5. jun. 2015, at 10.12, Mirja Kühlewind wrote: Okay, just to quickly clarify. In the charter on

Re: [Taps] I-D Action: draft-ietf-taps-transports-04.txt

> On 05 Jun 2015, at 12:35, Michael Tuexen > wrote: > >> On 05 Jun 2015, at 11:05, Michael Welzl wrote: >> >> >>> On 5. jun. 2015, at 10.12, Mirja Kühlewind >>> wrote: >>> >>> Okay, just to quickly clarify. In the charter only the word service is >>> used. We defined later on the words c

Re: [Taps] I-D Action: draft-ietf-taps-transports-04.txt

> On 05 Jun 2015, at 13:29, Mirja Kühlewind > wrote: > > Hi Michael, > > see below. > > > On 05.06.2015 11:05, Michael Welzl wrote: >> >>> On 5. jun. 2015, at 10.12, Mirja Kühlewind >>> wrote: >>> >>> Okay, just to quickly clarify. In the charter only the word service is >>> used. We de

Re: [Taps] A proposal to throw out RTP

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. The

Re: [Taps] I-D Action: draft-ietf-taps-transports-04.txt

Hi Michael, see below. On 05.06.2015 11:05, Michael Welzl wrote: On 5. jun. 2015, at 10.12, Mirja Kühlewind 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 ch

Re: [Taps] I-D Action: draft-ietf-taps-transports-04.txt

> On 05 Jun 2015, at 11:05, Michael Welzl wrote: > > >> On 5. jun. 2015, at 10.12, Mirja Kühlewind >> 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

Re: [Taps] I-D Action: draft-ietf-taps-transports-04.txt

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 wrote: > > >> On 5. jun. 2015, at 10.12, Mirja Kühlewind >> wrote: >> >> Okay, just to quickly clarify. In the charter only the word service

Re: [Taps] I-D Action: draft-ietf-taps-transports-04.txt

> On 5. jun. 2015, at 10.12, Mirja Kühlewind > 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, I think, it should say >

Re: [Taps] I-D Action: draft-ietf-taps-transports-04.txt

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, I think, it should say components. However, it does not really matter because we will in t

Re: [Taps] TAPS Transports and ICMP

On 04 Jun 2015, at 22:56, Joe Touch mailto:to...@isi.edu>> wrote: On 6/4/2015 12:51 PM, Pal Martinsen (palmarti) wrote: On 04 Jun 2015, at 21:17, Joe Touch mailto:to...@isi.edu>> wrote: On 6/4/2015 12:08 PM, Pal Martinsen (palmarti) wrote: ... UDP passes all ICMP messages to the app. If the