IETF Logo Mail Archive

Re: [Int-area] [DMM] New draft posted: Anchorless mobility management through hICN (hICN-AMM): Deployment options

Tom Herbert <tom@herbertland.com> Fri, 22 June 2018 15:39 UTC

Return-Path: <tom@herbertland.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 475E7130E9E for <int-area@ietfa.amsl.com>; Fri, 22 Jun 2018 08:39:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Chll9mHjpOjZ for <int-area@ietfa.amsl.com>; Fri, 22 Jun 2018 08:39:17 -0700 (PDT)
Received: from mail-qt0-x232.google.com (mail-qt0-x232.google.com [IPv6:2607:f8b0:400d:c0d::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 105B0130E96 for <int-area@ietf.org>; Fri, 22 Jun 2018 08:39:17 -0700 (PDT)
Received: by mail-qt0-x232.google.com with SMTP id z6-v6so6279003qti.2 for <int-area@ietf.org>; Fri, 22 Jun 2018 08:39:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tauRackIM34CdB12KjiiQchBBZnza+LovGkS4ZdyXmM=; b=BmtsukLpFfSgC1Tugf8cEjby12jCBC9yOeXdBV3VCq0aboC6zmzNcYUSwsqR2Tx/r/ F5RFgSrztFjmDh+9eKmvhO/W5zqsbJeDNjVUvrlmm0HdhL54g41Zb/eui7EuwCNvlSjJ N1DjaFRThPt4SwaWbhiFsCQv0BlJreBwuVl+LyDVsG/dvlIzIuqSSI/ff3bzNgPQLLA8 hlWGUoPDKcWA9xj5LPcsX8XhkelZVsowlzXYQ91w8KzS9/lNNieY69NABCWmPrQprwlh zpLGAZExjx9byZGnn+8sDwCwl1u25tkuWmxYh5vZlRs7E/GdT7FKOGz5iFvmmepOwvEm EFDA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tauRackIM34CdB12KjiiQchBBZnza+LovGkS4ZdyXmM=; b=r0DgYYt0inLYCa1DAl2QPR1+schemgb/pebEKwLcysh1w2thxghlpl5v0+A1+Cz0CA jQi1SBL4jP65gbMTMAUzoiHaPmSZgtKZBOjdWiM81cae7Jal9MubZyJxKypc1dw0bXwi qYHSYFgLgNL6+S4YdwiyKTWBU8n+FEzgEkBP6gzBElco7JrBFn0r0j4+eMEm1yPS4YRY 1dO1AfGjXBphLtbCpGWSWaIYbRlvTl0rOO8Q7rLfqYzKjHZE/CBTR7411DvR/Tl/hk8F dqYaxrokX1TQxnqm2MyqcPow4aZWSPHevn4Ct9+QNl8YnPL9dQccJWhpYG7f7E/d4VPK CryQ==
X-Gm-Message-State: APt69E383T+DTuWZKP/0kIYU8YVFai7TDRGUTUZ2H500Wg5FERShVQOP Y/Z5xRV8SzBRRVzZgfyDsWor6d6P3DFgS/P6m1uLZQ==
X-Google-Smtp-Source: AAOMgpfezGcHpMwzCiICkhD7ldYSpPjtpLL+LtZq5i8rBQ7Kqil0kmN71sXkhoezmJahlWND/vb50HvfpASH0pleQ7E=
X-Received: by 2002:a0c:c584:: with SMTP id a4-v6mr1881118qvj.11.1529681955792; Fri, 22 Jun 2018 08:39:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:aed:33a2:0:0:0:0:0 with HTTP; Fri, 22 Jun 2018 08:39:14 -0700 (PDT)
In-Reply-To: <CAHx=1M5Kw3TpHh=bAPiP61TxDAPvfUW4qmjw_SLNFBBfmu=Z7w@mail.gmail.com>
References: <CAHx=1M5MFsR6xBvetXEgcjsLJ8rmuLLBWMf9iXSQDguTwMh4Gg@mail.gmail.com> <CAPDqMeonj=E8B9MT3_9zBSzQGgkiqEoMt3a+TX+68OFDeusC7Q@mail.gmail.com> <CAHx=1M7BsPwBbO7UwcCdZfQu4XoiCvLjiuh3pAO_-DV_s_TyBg@mail.gmail.com> <CAPDqMeomQdDEb0uh1fS2vxvDJzg3+47m-bhz5Ah_O=ay5LFOhQ@mail.gmail.com> <CAHx=1M5DizvHPxSxxruS9iJA177GOWuQvv+tOWBwT+QXTZt3GA@mail.gmail.com> <CAC8QAceg0-_41iSC6eBun+uNZ+UA1kn1euf1yWvZ4byRRGOu9w@mail.gmail.com> <1529505221125.58728@cisco.com> <CAHx=1M7kWTy_4ZevVS-9X1Utu52oFVmyin4U6FssSsqnOnrEBA@mail.gmail.com> <CAPDqMeqBkoqC55dS-4RJ5OtO7hhUviqP420hLEmz2dZ8NM2-Aw@mail.gmail.com> <CAHx=1M6-tUXNq1NefGtrp7a-DLxRkykcfTC0qCHyM+DzM9Griw@mail.gmail.com> <CAPDqMepL6cRxxjMaw8Phj0tZXuG64-yEZyu+SJYvjm-owmpe9g@mail.gmail.com> <CAHx=1M4Z5zaoyezVDAPyRcVOMstW2OraTB4Gj6T02KvU=L=WRQ@mail.gmail.com> <CAPDqMeoOkR8E=Xw8ZgPtbzX5qTGe4Wfy=L1sUoicvDjRBaNczA@mail.gmail.com> <CAHx=1M6W_HSgOBF18PTT5qvu=4eR4rpSGCa6qcSCSv4T8dzJAQ@mail.gmail.com> <CAC8QAcd=ZPJ0QF2eubpfxm1jMn1_sqPJ-vfSD479YXGrK4Tg-w@mail.gmail.com> <CAHx=1M5Kw3TpHh=bAPiP61TxDAPvfUW4qmjw_SLNFBBfmu=Z7w@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
Date: Fri, 22 Jun 2018 08:39:14 -0700
Message-ID: <CALx6S37TQZmxBwBrHuXfbd-iVhoE6BcZGzE14RN+FP3RE=a0yg@mail.gmail.com>
To: Luca Muscariello <luca.muscariello@gmail.com>
Cc: Behcet Sarikaya <sarikaya@ieee.org>, int-area <int-area@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000983c6e056f3cd523"
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/lG5OftHEHFzeMC88S1BfuRlauVg>
Subject: Re: [Int-area] [DMM] New draft posted: Anchorless mobility management through hICN (hICN-AMM): Deployment options
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2018 15:39:23 -0000

On Fri, Jun 22, 2018 at 8:06 AM, Luca Muscariello <
luca.muscariello@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
>
>

v2.23.0 | Report a Bug | By Email