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 the current
document first identify components and then discuss features. In any case this
document will not define a new interface.
I'd also say that this is not the flag ship document (as stated by Joe). The
flagship document probably is the third item on the charter which then will
probably also talk about the interface in more detail (charter says on the third
doc: "This document will explain how to select and engage an appropriate
protocol ...").
Mirja
On 01.06.2015 21:12, Michael Welzl wrote:
About one bit in particular:
That’s to bad. Maybe we should state this more explicitly in the intro…? According
to our charter, while taps itself is chartered to describe "an (abstract)
interface for applications
to make use of Transport Services“, this first document is only used to
"identifying the
[components] provided by existing IETF protocols“ as a starting point. Further
we would like to add some discussion in section 4 which of the identified
components should/can be exposed as a transport feature that the app should
see. [Note that the terminology changed and whenever services is written in the
charter it should basically be component.]
This confuses me.
draft-ietf-taps-transports-04 defines a "Transport Protocol Component" as "an
implementation of a transport service feature within a protocol."
I'm fine with that definition but I can't see why this should replace "service"
in the charter. The first document should list the services provided by existing IETF
protocols, that's how to get started. Additionally listing components is probably fine if
that helps explaining how services are constructed, but the focus is on what transports
provide - services.
Cheers,
Michael
_______________________________________________
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps
