[TLS] Typo error in TLS Working Group charter

Mohit Batra <mohit4677@gmail.com> Tue, 21 February 2017 10:04 UTC

Return-Path: <mohit4677@gmail.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 465761298B5; Tue, 21 Feb 2017 02:04:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 sz0NZiZtRsWQ; Tue, 21 Feb 2017 02:04:13 -0800 (PST)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (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 E2B2F1298AB; Tue, 21 Feb 2017 02:04:12 -0800 (PST)
Received: by mail-it0-x236.google.com with SMTP id d9so31825138itc.0; Tue, 21 Feb 2017 02:04:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=dGhzq6gcGwHTF8vvXcEPs29ex7PUOjv2Hqeh7W7Z3+s=; b=hDrWywlxmIHEsawCqU7bbcZQbzNQJMH6S9fJszbCc/npmSKuGcVaajdEoOsOgVEiE+ qR7ZR5XSnrkP8HNPs2KJ2d1nqV8jz2gy/hxc3jO49gjqW+1JVPyS84i6N9ftEwxdP9Pd 8y/ZxxuLxqNH3R0ugLkNj+ZKUzkg2tiYUhmX/YACTkRPiTaMEswiIpkwql2USVdl3awg 7JnHtn8ekhU2AmayV578jhnRsgL3xI9tZE3t1U/23hSG5HjJhTghfDmWkUiz3IwsEp9x GqWp4p7dpvIffUHK/w8YQByEfJmGCnWVz/kknCXAY4fuWdrEutt6dp4mxJSXb+bQsrti bcrQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=dGhzq6gcGwHTF8vvXcEPs29ex7PUOjv2Hqeh7W7Z3+s=; b=BdAdQiVC5xguQfWX8NuWYORU1fhFqj/BMoS9pEKCArYqGw9wHAbvaZW3RA7kxDtDzM c50wZ4z3FvHr4L2Qk086+SLp0hJWx56vC67GPd4gqXVFNxP66iUP+8mZ9e/FlWdiMgI+ 6M5Kzi4cK9aZ1WPTnqWLSxQBHdrcKuZRUzSxkSrdX7lBMo7c6MVUX6TBW0Bm+qOm42bP UuedQMaLGUaJg6+S0aOgT+88RePnzbTiX6ius8LvSUW+uhZgqE8X2sDKlb3SsEezNJYj UvTLqF1ouv5lyGRuXq7FbgDZM37isqlX3px5RwqBYpnpptZdwhBOTHxGYmfVdUO57X6i dB0A==
X-Gm-Message-State: AMke39m4rGjInx3fKwBdHv6MX7uJcNz5EwqMOVnl3Qpn5vmuJG4XuDPR8mFO5tFnCsGlazhvzKNeiXC2NSiR9A==
X-Received: by 10.107.138.96 with SMTP id m93mr23326879iod.22.1487671451916; Tue, 21 Feb 2017 02:04:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.79.28.203 with HTTP; Tue, 21 Feb 2017 02:03:31 -0800 (PST)
From: Mohit Batra <mohit4677@gmail.com>
Date: Tue, 21 Feb 2017 15:33:31 +0530
Message-ID: <CAAZqyN5ZE7634F+tAxs8xxk6A6NWFciLLDXSsCc6_C-QGrOTCg@mail.gmail.com>
To: tls-chairs@ietf.org
Content-Type: multipart/alternative; boundary="001a113f19e26f1e7d054907807b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/nKDYBBrGWgCxrDGTMTxfzwkurfk>
Cc: tls@ietf.org
Subject: [TLS] Typo error in TLS Working Group charter
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 21 Feb 2017 10:04:14 -0000

Hello,

I just noticed a Typo error in TLS Working Group charter at
https://datatracker.ietf.org/wg/tls/charter/

The RFC number for TLS 1.2 is mentioned as:  RFC5346

However, the correct RFC number is:  RFC5246


Request to please correct the same.

-- 
Thanks & Regards,
Mohit Batra
IETF 95/98 fellow