Re: [dtn] [EXTERNAL] BPbis consensus status

Marc Blanchet <marc.blanchet@viagenie.ca> Fri, 18 September 2020 14:07 UTC

Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: dtn@ietfa.amsl.com
Delivered-To: dtn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 379E03A0A9E for <dtn@ietfa.amsl.com>; Fri, 18 Sep 2020 07:07:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=viagenie-ca.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 ww20TaiJr28n for <dtn@ietfa.amsl.com>; Fri, 18 Sep 2020 07:07:50 -0700 (PDT)
Received: from mail-qv1-xf2b.google.com (mail-qv1-xf2b.google.com [IPv6:2607:f8b0:4864:20::f2b]) (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 6F6CE3A0A66 for <dtn@ietf.org>; Fri, 18 Sep 2020 07:07:47 -0700 (PDT)
Received: by mail-qv1-xf2b.google.com with SMTP id db4so2910105qvb.4 for <dtn@ietf.org>; Fri, 18 Sep 2020 07:07:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=viagenie-ca.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=EdM56Wqau03e0+nQmOkS/LC2yQtJ7NNsl0ej+3kzU4I=; b=qZe64Jp4v/0GpHxO7DjUJqxQiic2Upt6kgK/+r5um9X106/2ewI8mayQDAZMjp+vJa qjJs1EBBZghiuuSJL12XaYkHVOWttIS5q4kQCI2+itTu1kNJio31yOhCdJkThtw2faqe ZgO42yVzJPlb7rX0AHpVuxy6HQiUIC/ewKSx5JR06m+yVf9HCjIdAAUwm82LKKSOT+IM 2rPt8HW60PSPrcYeFTyJDQWJiw98ogPLs+MC4U//oa64hntS11QIgCbQbBT8tPr8Tm5v IESmcppwhVqG22SUqc9UYnXMpr/2yC0b5S+mcT39AWOVYt39NcrlkPPTqUBGQxalCfZM 7gMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=EdM56Wqau03e0+nQmOkS/LC2yQtJ7NNsl0ej+3kzU4I=; b=B/I4IV0oy1jNrWaMQTuLpqS2HFljUHAQw60Vo9yXJXJCJBTShGFAfE+PyaylvIdgo5 I40By3tQQhQSGcR4SjSMJ3dq29ugq8H7NHJbVhm7CFLiF/k+5W8izsKpohJqsDtzZAru uIt2NeWCRU2NZYH8aL59eGgGo9vD7WnHU5aabtswIag2DLo9jq/gAmzMaRHMf8LGZOR0 2JheTjEnrm73ALYFY/FatLrQJXIIl9UdPayWByjoRI45OidcBvMSKRwCyTnf6RPMSvU7 JNH0jjMVyqX/DFoCR8UY5yB4RbSO5ha2sQXRauP7j7OxTJ4Xe5ki2sztwA7YUZFZ3GYC Fhxg==
X-Gm-Message-State: AOAM532wwe1ffMIhijOD5NrA+fSE74fzUb+T1z0b5LAEenK5SAybMcjS PdCy8j7yj+3RjOUcDnz3teZ25ybQcFM1qw==
X-Google-Smtp-Source: ABdhPJwKRrdzsjF+cHoit9JI5vmJ51wP1u+9Ly3CGmlJ/KQ0nyedNnSpM8UeuI1t5PnB44RmwuhZ6Q==
X-Received: by 2002:a0c:9d03:: with SMTP id m3mr17017865qvf.54.1600438066439; Fri, 18 Sep 2020 07:07:46 -0700 (PDT)
Received: from [206.123.31.195] (modemcable016.82-162-184.mc.videotron.ca. [184.162.82.16]) by smtp.gmail.com with ESMTPSA id f24sm2090908qka.5.2020.09.18.07.07.45 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 Sep 2020 07:07:45 -0700 (PDT)
From: Marc Blanchet <marc.blanchet@viagenie.ca>
To: Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org>
Cc: rja.lists@gmail.com, dtn@ietf.org
Date: Fri, 18 Sep 2020 10:07:44 -0400
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <FCE5B100-AD3B-4D97-BDA6-BEBD1EE0212A@viagenie.ca>
In-Reply-To: <e8d3d3bfb224df27042a229c1e13074483600bdf.camel@ericsson.com>
References: <34a7886b09d946faa816acbd26700d65@jpl.nasa.gov> <F2B67324-D3F5-4F28-8CC3-207EB607E6EA@viagenie.ca> <ED9CEA8D-3B22-4623-A7F7-F9ACA4C3A071@gmail.com> <CEBD7985-410F-4AF4-B367-1B08C99CB38A@viagenie.ca> <d2eb737bc35b46019bdb5c5e82e96126@jpl.nasa.gov> <A2CD01A8-EDBE-4840-8CFC-5A3732AA28D2@viagenie.ca> <5B167E21-175E-4F87-8D67-59FBA0CB4A28@gmail.com> <e8d3d3bfb224df27042a229c1e13074483600bdf.camel@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/6v8fh574z8q2zxSt4Mx3j0nBJec>
Subject: Re: [dtn] [EXTERNAL] BPbis consensus status
X-BeenThere: dtn@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Delay Tolerant Networking \(DTN\) discussion list at the IETF." <dtn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtn>, <mailto:dtn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtn/>
List-Post: <mailto:dtn@ietf.org>
List-Help: <mailto:dtn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtn>, <mailto:dtn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Sep 2020 14:07:58 -0000

On 18 Sep 2020, at 10:03, Magnus Westerlund wrote:

> Hi,
>
> Personal opinions below.
>
> Marc, I think comparing BPSec with IP and IPsec is wrong for several 
> reasons. I
> think one of the more significant ones are related to the 
> identification of the
> peer entitity and who you are and establishing security between these 
> two
> entities end-to-end. IPSec is to low level for that to work in the 
> Internet as
> endpoint or possibly whole networks (due to NATs) exist under the 
> umbrella of an
> IP address. However, I don't see that being the case for BP. Here BP 
> can address
> the applicaiton specifically and create security association 
> end-to-end between
> the application entities on different nodes. Becasue the BP agent can 
> provide
> unique DTN addresses for each application and establish different 
> BPSec security
> contexts to prevent this missmatch. So BPSec has all the chance of 
> being the
> basic security layer end-to-end that IPsec never succed as.

well, I personally disagree and still stand. However, as I wrote some 
emails ago, it seems that I’m the only one in this email list on that 
side, so I’m loosing and it is fine. We shall just proceed with the 
concensus of the group. No issues for me to proceed the way the group 
wants

Regards, Marc.

>
> Yes, there are hurdle to get the details for security contexts 
> (security
> profile) and its key-management done. But without this I don't see how 
> DTN will
> even become more that narrow nichese where it is used ontop of a 
> private
> network. There are some utility in that, but far from the promise of 
> the network
> and networks for delay tolerant applications that could use a 
> interwork layer. I
> think BP can succeed, but not without a security solution that work 
> and are
> generally available and supported.
>
> Cheers
>
> Magnus
>
>
>
>
> On Thu, 2020-09-17 at 18:46 -0400, R. Atkinson wrote:
>>> On Sep 16, 2020, at 23:25, Marc Blanchet <marc.blanchet@viagenie.ca> 
>>> wrote:
>>> ... as current Internet deployment tells us, the applications need 
>>> to be
>>> aware
>>> of security services ...
>>
>> Marc,
>>
>> Your words above - to the extent they are true — are a reason
>> to have a well documented BPsec API which applications can use
>> if/when appropriate.
>>
>> Such an API probably should be documented in an Informational RFC.
>> Is that something you might want to undertake — since you are so
>> passionate about it ??
>>
>> From a logic perspective, those words quoted above are really NOT a 
>> reason
>> for  BPsec to be optional to implement.
>>
>> Yours,
>>
>> Ran
>>
>> _______________________________________________
>> dtn mailing list
>> dtn@ietf.org
>> https://www.ietf.org/mailman/listinfo/dtn
> -- 
> Cheers
>
> Magnus Westerlund
>
>
> ----------------------------------------------------------------------
> Networks, Ericsson Research
> ----------------------------------------------------------------------
> Ericsson AB                 | Mobile +46 73 0949079
> Torshamnsgatan 23           |
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
>
> _______________________________________________
> dtn mailing list
> dtn@ietf.org
> https://www.ietf.org/mailman/listinfo/dtn