On Fri, Jun 22, 2018 at 8:06 AM, Luca Muscariello < luca.muscarie...@gmail.com> wrote:
> I answered to 3. Please dig into the reply for the full answer. In short > it is no, it does not. > And BTW, I am aware I'm not providing any analysis and that I'm not trying > to resolve any big thing > in an email thread discussion, I never said I was. > The objective is to answer to clarification questions from list members > about recently posted drafts. > Luca > > #3 is the wrong question to ask. The right question is "Does the new transport protocol disrupt TCP?". Of particular interest, how does the protocol interact with TCP on wire? What is the congestion control of the new transport protocol? How is it "TCP friendly"? As Behcet mentioned, these are not things that can be answered in a few sentences on an email thread. The draft posted seems bereft of any details about the new transport protocol; will another draft be coming that specifies the transport protocol and answers questions like this? Tom > > >>>> >>>> >> > >>>> >> > Back to your questions that I understand this way: >>>> >> > 1) What is the hICN socket API? >>>> >> > 2) Does hICN imply that all hosts have to change transport stack? >>>> >> > 3) Does hICN disrupt the TCP/IP stack in an end host? >>>> >>> >> What about 3) here, I don't see any answer to that in the mail. >> >> Also let me state that the analysis you are giving here involves so many >> things like CCN/NDN, Id-Loc, transport layer, network layer >> and so on, let me state that you can not resolve anything about such big >> things within a few sentences. >> >> Behcet >> >>> >>>> >> > _______________________________________________ > Int-area mailing list > Int-area@ietf.org > https://www.ietf.org/mailman/listinfo/int-area > >
_______________________________________________ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
