[shara] Problem statement

[Magnus Westerlund <[e-mail]>]

Hi,

I would like to see a better Problem Statement for SHARA. I already
gotten questions about the problem statement. I can kind of guess having
been involved in the discussion of the related work. But I think there
is need for a collected problem statement for SHARA.

This also relates to a question that needs to be answered i a good way
to enable chartering. Why the problem scope and intended solution
proposed? I interpreted Pierre Levis' comments that there clearly are
other solutions and what about them. From my perspective as an AD I
don't think "let all flowers bloom" is the answer to the IPv4-Ipv6
coexistence and migration issues. We are here to provide recommended
solutions within a reasonable time frame so that it actually can impact
the market. We don't have forever here, and that is why dual-stack lite
was chartered, what appeared to be a reasonable solution and one which
we can think IETF can finish documenting this year.

So is what SHARA proposes necessary, a sufficient improvement, resolve
previously non-handled issues? Should we do it now or focus on first
completing the already chartered items in Softwire and Behave?

For your knowledge, I need most of these answers quickly. The IESG and
IAB have their call to discuss the BOFs next Thursday. By then I need to
know as much as possible to have the right discussion about this BOF
proposal's approval or not.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  [phone]
Färögatan 6                | Mobile [phone]
SE-164 80 Stockholm, Sweden| mailto: [e-mail]
----------------------------------------------------------------------
_______________________________________________
shara mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/shara