On Thu, Dec 26, 2019 at 1:14 AM Tianran Zhou <[email protected]> wrote:
>
> Working Group,
>
>
>
> Thank you for all of your emails related to draft-song-opsawg-ifit-framework.
>
> It seems there are a lot of interested people. I hope the authors will be
> encouraged by that.
>
> But there were also some strong concerns about the scope of the draft. What
> is it trying to achieve? How does that match the charter? Does it include
> material that is outside its scope? Thanks specially to Frank and Al for
> saying their concerns.
>
> We are going to extend the adoption call for another two weeks to Jan 8. And
> we encourage the inter-working group discussion.
<no hats>
I've just (re)read this, and have some concerns -- I found it somewhat
hard to dig into the actual technical "meat" of the document
(channeling Randy Bush "Where's the protein?") - it feels like it
describes a bunch of benefits and features of a solution, but without
actually describing the solution itself. The Abstract says that in the
document "a high-level framework, In-situ Flow Information Telemetry
(iFIT), is outlined.", but I couldn't really find it. Section 2 ("iFIT
Framework Overview") is so very level that it doesn't really seem to
say much at all.
I assumed that I'd just missed a bunch of other documents which
actually describe some of the details behind ifit, like what exactly
an iFIT node *does*, or what exactly an "On-demand Flow Sketch" is[0].
Basically, if I wanted to implement this myself, how would I do so?
The main thing I found was:
https://www-ctc.huawei.com/ke/press-events/news/2019/6/first-ifit-pilot-5g-transport-network-beijing-unicom-huawei
"In October 2018, Huawei submitted the draft of iFIT — "In-situ Flow
Information Telemetry Framework" — to the Internet Engineering Task
Force (IETF). Huawei's iFIT is the industry's first in-band flow
measurement solution to have been deployed commercially. In June 2019,
Huawei's iFIT solution won the Best of Show Award Special Prize at
Interop Tokyo 2019 — one of the most prestigious events in the
industry." and "Huawei's innovative iFIT solution takes a hardware
approach...", etc.
This, and the general tone of the document, feels like a marketing
driven exercise - the document describes a bunch of features and
benefits of a solution, but without the detail needed to implement it.
Without a full description of iFIT itself and a serious scrubbing of
the marketing tone, I do not think that the document should be
adopted.
W
[0]: "A flow sketch is a compact online data
structure for approximate flow statistics which can be used to
facilitate flow selection. The aforementioned CountMin Sketch is
such an example. Since a sketch consumes data plane resources, it
should only be deployed when needed." -- this doesn't really say
anything. Where is the format for the datastructure defined? How do I
write one, how do I deploy it?.
" iFIT Head Node: A special iFIT node. It is the entry node to an
iFIT domain. Usually the instruction header encapsulation, if
needed, happens here." - this just names something, but does not
describe what it actually *is*, etc.
</no hats>
>
> Please continue to discuss on the mailing list.
>
>
>
> Merry Christmas!
>
> Tianran
>
>
>
> From: OPSAWG [mailto:[email protected]] On Behalf Of Tianran Zhou
> Sent: Monday, December 9, 2019 1:27 PM
> To: [email protected]; [email protected]
> Cc: [email protected]
> Subject: [OPSAWG] WG adoption call for draft-song-opsawg-ifit-framework-09
>
>
>
> Hi WG,
>
>
>
> On IETF 106 meeting, we saw predominant interest and support to this draft,
> especially from operators. The authors then resolved all the open issues.
>
> As requested by the authors, this email starts a 2 weeks working group
> adoption call for draft-song-opsawg-ifit-framework-09.
>
> https://datatracker.ietf.org/doc/draft-song-opsawg-ifit-framework/
>
>
>
> If you support adopting this document please say so, and please give an
> indication of why you think it is important. Also please say if you will be
> willing to review and help the draft.
>
> If you do not support adopting this document as a starting point to work on,
> please say why.
>
> This poll will run until Dec 23..
>
>
>
> Thanks,
>
> Tianran as co-chair
>
> _______________________________________________
> OPSAWG mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/opsawg
--
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
---maf
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg
