IETF Logo Mail Archive

Re: [Ace] draft-ietf-ace-mqtt-tls-profile connections

Cigdem Sengul <cigdem.sengul@gmail.com> Thu, 23 May 2019 08:33 UTC

Return-Path: <cigdem.sengul@gmail.com>
X-Original-To: ace@ietfa.amsl.com
Delivered-To: ace@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BA6412016B for <ace@ietfa.amsl.com>; Thu, 23 May 2019 01:33:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 oBo4cjUvwmfB for <ace@ietfa.amsl.com>; Thu, 23 May 2019 01:33:56 -0700 (PDT)
Received: from mail-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) (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 98EF012008A for <ace@ietf.org>; Thu, 23 May 2019 01:33:56 -0700 (PDT)
Received: by mail-qt1-x833.google.com with SMTP id m32so5776603qtf.0 for <ace@ietf.org>; Thu, 23 May 2019 01:33:56 -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=FJRq71JJK5xSfydswQpswBXYAQvCFoUp1mczBEuMDfs=; b=Uc9060ocSqkDEd/Cl5yMjhSTlPku5ThcFT3I3UTpQ0YD+bnH65GmPP/ElLGf4ME5Z7 g7JEY9S6LBzQpIDfJO4aNHooG8UfHPxoRM236Ar72rVFLqNHmaN8fzU1qNt0NKnsQDoj 4kK7ihX9W+02AIVcPUP7Y5Jw6dPT026Y5EpJuHQ/d7BCGPjy3VQa/1OcTNhRmzZ/5crJ 0Tj0+ht9P9BCBuhSP+cBu8z+9XouoIJvP+ryzmS8Eb2lH9Uk2vOtHYK1+qmASlwwKDAo J+6p95Jfpvt1PpsjFLyZO4M6E8/osEn/T0gcScnxuM1rwrhpJVgQNjS/bGJzkFRMHlsR UW1g==
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=FJRq71JJK5xSfydswQpswBXYAQvCFoUp1mczBEuMDfs=; b=CiPO26m59RdlU7gaUSRrb9fqqH5yRaxItjrKnl9SGm89YgbeVrFCZ1T7PztWMk0HZS nM0sEYWlYnzy20j7Vc7KD+zuEqF0T8Byg0KxVtTY3LE/Gtt+6VhjH+0A03/w5rZMSmoi ihyngRq7UyosNyIgGje3vave0TpPVDSJLfkA0l3UqkyPaf8NdfKnaE3Gt8AtIabJvZDw XvuibzyqqkyRooN597WJAtXc8zl5DOivBftaI7tae+MTiIrkn6yXTEiiSiUA+7F/gqvt wBPXB07IE2ER3Eeao5czbDiWjEg/R6tjVW55a+6641pOyMeLVAJ8dFJPzGYLgmA3eiGS yn/g==
X-Gm-Message-State: APjAAAVPkLrHteGqpH3c0WG4+Wp4IyhHyGDcdk8xpz8H62dBFpeUZVB3 bRSSzJgEFYD6jzyhsDxqb3+9qEiO5zwpZn4Yk1A=
X-Google-Smtp-Source: APXvYqxA/nySvy3MQgtHl4+pb0izw59r0ohm0qqfb2H+EVJ8zMHdpi5PSurdkdHETNODKiT0/Uh6Y2q1S8G/bT9xp7c=
X-Received: by 2002:a0c:f350:: with SMTP id e16mr76442899qvm.72.1558600435771; Thu, 23 May 2019 01:33:55 -0700 (PDT)
MIME-Version: 1.0
References: <001901d50e05$74847200$5d8d5600$@augustcellars.com> <CAA7SwCPXLnpt7TbQTsx7emY9OdDVx50nssatYkhLGgOVwujyaw@mail.gmail.com> <1438cd8c-0322-a83b-4635-cbf8ea85102a@ri.se>
In-Reply-To: <1438cd8c-0322-a83b-4635-cbf8ea85102a@ri.se>
From: Cigdem Sengul <cigdem.sengul@gmail.com>
Date: Thu, 23 May 2019 09:33:44 +0100
Message-ID: <CAA7SwCPXDNnPxPXm8nk9CeonSYrXv0WPOo2LZWHZxKJeektbaQ@mail.gmail.com>
To: Ludwig Seitz <ludwig.seitz@ri.se>
Cc: ace@ietf.org
Content-Type: multipart/alternative; boundary="000000000000522bfe058989f125"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/U6m59N558e10XDlqPUBuwRrvLCo>
Subject: Re: [Ace] draft-ietf-ace-mqtt-tls-profile connections
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <ace.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ace>, <mailto:ace-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ace/>
List-Post: <mailto:ace@ietf.org>
List-Help: <mailto:ace-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ace>, <mailto:ace-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2019 08:33:59 -0000

Hello Ludwig,

This was MQTT-SN-over-DTLS was on our agenda when first we started out.
However, at that time there was not much take-up of MQTT-SN  in practice
(not sure that changed). If there is sufficient interest in the group,
would make sense to do that as well, and theoretically, it would be a more
natural fit to ACE.
Thanks,
--Cigdem

On Thu, May 23, 2019 at 7:29 AM Ludwig Seitz <ludwig.seitz@ri.se> wrote:

> On 21/05/2019 22:35, Cigdem Sengul wrote:
> > Thank you for your comments.  I see that we tried to cover too many
> > options in the draft, and things got mixed up.I tried to clarify inline.
> >
> >     * So as a client I get a token from the AS.  For the first run,
> >     assume that
> >     it has a RPK in it.
> >     * I now connect to the server using TLS.
> >              Question #1 - Am I doing client authentication at this
> >     point in TLS?
> >     This is what is happening for all of the current profiles, but it is
> not
> >     clear that this is happening for this profile.  The answer appears
> to be
> >     both yes and no.
> >
> > The basic method we were thinking:
> >
> >
> >  1. We have not assumed client-side certificates for authenticating
> >     clients during TLS handshake. RS uses a server-side certificate.
>
>
>
> One quick question: If I understand it correctly there is a variant of
> MQTT using UDP (MQTT-SN). Since TLS and TCP are not exactly
> "constrained-friendly", would it make sense to look at that as well to
> define a "MQTT-SN-over-DTLS-based" profile?
>
> /Ludwig
>
>
> --
> Ludwig Seitz, PhD
> Security Lab, RISE
> Phone +46(0)70-349 92 51
>
> _______________________________________________
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
>

v2.23.0 | Report a Bug | By Email