Re: [core] Using CoAP for P2P

Abhijan Bhattacharyya <abhijan.bhattacharyya@gmail.com> Mon, 06 April 2020 20:02 UTC

Return-Path: <abhijan.bhattacharyya@gmail.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8221F3A0E37 for <core@ietfa.amsl.com>; Mon, 6 Apr 2020 13:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 mjdBeUCPAJSh for <core@ietfa.amsl.com>; Mon, 6 Apr 2020 13:02:02 -0700 (PDT)
Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (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 753993A0E47 for <core@ietf.org>; Mon, 6 Apr 2020 13:02:02 -0700 (PDT)
Received: by mail-ed1-x533.google.com with SMTP id o1so1118248edv.1 for <core@ietf.org>; Mon, 06 Apr 2020 13:02:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7d1kdr0mw1wWHWKLMVwyNmGjEesPjLyBMnOFXCBCM2A=; b=stRarxaKcw8qGhSielOnZOIeMXeNNtJlNeKQ8kX0cDoklWWjs30HbqKtsD4mncqVSx 89/PELlHVoCh2tYz28NvWf2YAe93+oAyJqgETMwG48qNY0oTugKqpLulLNOIPYSGiieU JLq1fth9zRgSL/rYe+mOJDgvk0euF04UL2o0r/1yTiq/ZKCyMf56CKpmCgsQM6dFIDsR FmrDef+l96sHViM617To+MncKMtKW7cQHreJqv9CkAI7oALIugfMHUvK5SG+B4Ut8i8A XWI9zisGOuuTvnV0SnNooLT6kxMDdYAU92Ab3DQd/jpdlsEIESUexpaY1ASM6e7wxH2p G5MQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7d1kdr0mw1wWHWKLMVwyNmGjEesPjLyBMnOFXCBCM2A=; b=Hbc09E4ooXbWNerhmfaJdogzNapXRCerEj+jeT6goJ2RtYk/8CdehhQbDehrVpmg4+ 2XKxrb/rM0kpD/FA5vAg0H8icGTc1mBwO5zy1urEpnYn6NE84+2GmF33swoMtJx2+SDt 5qmg8/zH7FYObB5dCosS8dssbacLyGZ8WspNuMrKrVmY2TCWlVlTTwF/M3kYDIo1uudp WIo3Rev23ws8hm08H2rESoV/Lpd05FSLkZCxenu8yXwYZkHHmNb5dkYg5jmMd6UjHjv8 mj8T0+PdUnoEAlhlkg//eQXqUON8JFSRrqYMYgg82f6hm3z/NAv2UMqBbNIbyYKnR7DT wvAg==
X-Gm-Message-State: AGi0PuZuKrRHHd65T5xkdLDDjercAkMIapKZNb40h4seplx+8fIjRPZ1 KmNqg7bfwRYdId5jyfuQkBjxbb96dAiroM73u/QjXGyz
X-Google-Smtp-Source: APiQypIZcDBy8DpqKn3ksbtPcmUl/VT707gsTZV2v4HSkoaP/TBTUzjYUBHyQbVB4yxBdeyysuH5eBl+jbmNwrkpaf4=
X-Received: by 2002:a17:906:7804:: with SMTP id u4mr1147990ejm.328.1586203320833; Mon, 06 Apr 2020 13:02:00 -0700 (PDT)
MIME-Version: 1.0
References: <CAEW_hyzh3FAvHi1eTkbyGn99o4nFgcH1xP90FdQ6N9sHsAJVYQ@mail.gmail.com> <A8E6E9AA-2E34-439E-8761-53385086CDB9@arm.com> <CAEW_hyy+0fViN8dMWiCi_QHjeD5J4DUAnoRUg5MAKS6fQ3DzcQ@mail.gmail.com> <7B20E77F-CFF4-4735-A0C2-99121CD352D3@ericsson.com> <CAEW_hyzbtq6VbQMq5PhfAQjf6LLz-7t_9He-C_kaU5jztsf20A@mail.gmail.com> <CF1E6A23-243F-47A3-9DFB-BB244E96302B@ericsson.com> <CAEW_hyzsq8T9uXQYUacZ5VzWf7JsJ1xAzKEMaA-XemOWW06fBQ@mail.gmail.com> <F11ABE2A-89A9-4512-8708-B692B0AABB65@tzi.org> <8012E8F3-F21D-455E-B888-24C996D9C509@ericsson.com> <99FAF8E8-D93B-4AAC-919D-BEC9F614ED28@tzi.org> <CAEW_hywLqNcU4DD5tbXLqPO4WGH9g=mDWqH051dmXpYs53TFDw@mail.gmail.com> <e452414c-0266-be43-26ae-50f30a4ed6db@gmx.net>
In-Reply-To: <e452414c-0266-be43-26ae-50f30a4ed6db@gmx.net>
From: Abhijan Bhattacharyya <abhijan.bhattacharyya@gmail.com>
Date: Tue, 7 Apr 2020 01:31:49 +0530
Message-ID: <CAEW_hyzdYs=k49uOFDwEZFdCvZcW=3FRpxkvwoJqmNszE9ZuBA@mail.gmail.com>
To: Achim Kraus <achimkraus@gmx.net>
Cc: core <core@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007addda05a2a4bd9e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/EnKyDLfy3HSMMHSs3Af9wK2WlK0>
Subject: Re: [core] Using CoAP for P2P
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2020 20:02:04 -0000

Hi Achim,
I think we can put it this way:
When we consider a purely Client/Server mode, there is this inherent
assumption that usually the server will have the implicit responsibility to
make itself available through a known accessible path. This does not hold
as a general consideration when we want to do a P2P that should not depend
only on a given assumption about the path to reach the peers.

The peers may both be publicly addressable; one or both may be behind NAT/
Firewall; they may be in a home network where filtering rules are relaxed;
they may be in an enterprise network with stricter rules (at times you may
need the local infra admin to intervene to open specific ports -- let's
keep that out of consideration here). So, any possible standardization
effort should propose a mechanism that will allow the peers to access each
other agnostic of the intermediate topology and the back haul.


Thanks.

On Mon, Apr 6, 2020 at 7:07 PM Achim Kraus <achimkraus@gmx.net> wrote:

> Hi Abhijan,
>
> in my experience it's not about IPv4 or IPv6 (and the feature assumed to
> be included with both technologies).
>
> It's about the nature of the network you use for your peers to
> communicate. CoAP over UDP (also over DTLS/UDP) works without the need
> of additional parts, if your peers can exchange messages using UDP.
>
> So, is that network your peers are using fully under your control? As a
> home-network maybe considered. So, you know, if your peers have static
> or mainly static addresses. And there is nothing on the path between
> your peers, which may block or modify your traffic? Then you have a very
> good chance, that you don't need something additionally.
>
> But, if your peers can't reach each other without additional parts, e.g.
> because both in "their home network" and so communicate over a path,
> which uses a "public internet link", then you need more.
>
> Therefore, please try to describe first the network(s) and the
> communication paths you plan to use for your peers.
>
> best regards
> Achim
>
> Am 06.04.20 um 14:31 schrieb Abhijan Bhattacharyya:
> > Hi Carsten,
> > Considering the practical deployment possibilities, I think we are quite
> > far from expecting a clean IPv6 path. My home broadband service provider
> > still serves IPv4 only. :)
> > Apart from that there may always be some firewall in place considering
> > enterprise use cases and we would need to punch a hole.
> > Thanks.
> >
> > On Mon, Apr 6, 2020 at 5:43 PM Carsten Bormann <cabo@tzi.org
> > <mailto:cabo@tzi.org>> wrote:
> >
> >
> >     On 2020-04-06, at 13:52, Christer Holmberg
> >     <christer.holmberg@ericsson.com
> >     <mailto:christer.holmberg@ericsson.com>> wrote:
> >      >
> >      > I am not going to get involved in a discussion about that,
> >     because it is not CORE specific, but IPv6 is *NOT* going to remove
> >     the need for NATs :)
> >
> >     Of course not, IPv6 is not removing IPv4… :-)
> >
> >     (That’s why I talked about a “clean” environment.)
> >
> >     Grüße, Carsten
> >
> >
> >
> > --
> > Regards,
> > Abhijan Bhattacharyya,
> > /Technologist by profession [IoT| Internet Protocols| 5G]/
> >
> > _______________________________________________
> > core mailing list
> > core@ietf.org
> > https://www.ietf.org/mailman/listinfo/core
> >
>
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
>


-- 
Regards,
Abhijan Bhattacharyya,
*Technologist by profession [IoT| Internet Protocols| 5G]*