IETF Logo Mail Archive

Re: [TLS] Uniqueness of values in lists?

Eric Rescorla <ekr@rtfm.com> Thu, 09 August 2018 14:45 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D235130E1E for <tls@ietfa.amsl.com>; Thu, 9 Aug 2018 07:45:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-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 dA3V50aOufsc for <tls@ietfa.amsl.com>; Thu, 9 Aug 2018 07:45:07 -0700 (PDT)
Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::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 4C9F6130DDB for <tls@ietf.org>; Thu, 9 Aug 2018 07:45:07 -0700 (PDT)
Received: by mail-lj1-x232.google.com with SMTP id q127-v6so4656933ljq.11 for <tls@ietf.org>; Thu, 09 Aug 2018 07:45:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=mhOvQeKZC9N6Yjy2q9U74Lxx2tw9+ycl7km38UQZYjg=; b=gyeTERJ3K7b+xqRJYhSq+W6wxbCCLvEv6C90Av03uAJwJVwVGhlmDB0xVjoyRgWm4S b5sM9xVl/0hcnWKRKo8xjD20Zsx611A7AvHjacKZ7ox/ULmZ191m86KYk+89S8ng6gjU bRFgNtYRRyGdAvdWJvmC6KVCebLx2KSI6mhFreZ2R7KUscT24QyOMnMq05EOIqHT/2GL kmOAo2YATgVaIuzWwRMKxX54GzFoc5BBI7t8QU023uzep3AW/QLgiNYfwjtvGhoucUYz 2B0yCzvZ8i+Zj71XxIBuUmKrDfWnpROrjIWgXk0dQdb2aTNlcvW+FpuJf/SYfxA1+ude 5gWQ==
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=mhOvQeKZC9N6Yjy2q9U74Lxx2tw9+ycl7km38UQZYjg=; b=C5Oox7xedaZyXvEPXSj7kObVFOK2tQEKOmOvIFoW1o0/GzKdSJeta3Y3/UncW07FHm fk0oRgNN8XfF91h5BGREbUQglGzKYeBWYguAFoHrS+i9zFEU/88rgkbjDZWTyiGKOb1Q mniUQtPXY6+TeFZyPGfpR++j/0LxzaWaw3597rHKWadouW3UdgQy2iokTGvO9pCHhj3P xnaOnMsLwzfKsaHLZa9ruWiSSke2qI3rQgiCl3nP4OBWSKEyCcD5xRZ6hyZ5VEXIuf/7 37YAIzGlhMQ/1XAcHkBBHG7lxycAD6BC4L/z5nttCHeHqWc0Dze9llywE9yT95t7GPRp niOA==
X-Gm-Message-State: AOUpUlGcwOTpvDFfLILuATBgvAhPur2EIC2hIU2Dv6rE9+EMk0wOhImq 2nRTxXp68x0LNAH4IlyBEwRcIm98yrPsqBI/3VOlFA==
X-Google-Smtp-Source: AA+uWPxsnq+LGT9C0nJbKt61DNF2TZ6lBj612VfwWGh41tij/9/DhB9c7gPa4VvlBxzRyHoC9UPOUWnv3/FlcF9woaY=
X-Received: by 2002:a2e:2096:: with SMTP id g22-v6mr1871831lji.37.1533825905540; Thu, 09 Aug 2018 07:45:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:ab3:4091:0:0:0:0:0 with HTTP; Thu, 9 Aug 2018 07:44:24 -0700 (PDT)
In-Reply-To: <3096393.3yWAhzPKLF@pintsize.usersys.redhat.com>
References: <3096393.3yWAhzPKLF@pintsize.usersys.redhat.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 09 Aug 2018 07:44:24 -0700
Message-ID: <CABcZeBPiF9oE_e4d=fxY2id=0M_rTcHMg5sZTbpGM=MFzwX4fA@mail.gmail.com>
To: Hubert Kario <hkario@redhat.com>
Cc: "<tls@ietf.org>" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003f5655057301ac7c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/e4FN0WqyuKyBBwW6KQZRugw9wes>
Subject: Re: [TLS] Uniqueness of values in lists?
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2018 14:45:11 -0000

On Thu, Aug 9, 2018 at 7:41 AM, Hubert Kario <hkario@redhat.com> wrote:

> I've noticed that while there is an explicit requirement for extension
> types
> to be unique for any given message:
>
> https://tools.ietf.org/html/draft-ietf-tls-tls13-28#page-43:
>
>    There MUST NOT be more than one extension of the
>    same type in a given extension block.
>
> and for key_shares:
>
> https://tools.ietf.org/html/draft-ietf-tls-tls13-28#page-54
>
>    Clients MUST NOT offer multiple KeyShareEntry values
>    for the same group.
>
> I don't see a similar requirement for other lists of values:
> signature_algorithms, supported_groups, cipher_suites, etc.
>
> Did I miss something?
>

Nope. I don't believe it's a current requirement.

-Ekr

-- 
> Regards,
> Hubert Kario
> Senior Quality Engineer, QE BaseOS Security team
> Web: www.cz.redhat.com
> Red Hat Czech s.r.o., Purkyňova 115, 612 00  Brno, Czech Republic
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>
>

v2.23.0 | Report a Bug | By Email