IETF Logo Mail Archive

Re: [MMUSIC] draft-4572-update: Spec contains references to a number of obsoleted RFCs

Martin Thomson <martin.thomson@gmail.com> Sun, 01 January 2017 10:49 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74EA11294F0 for <mmusic@ietfa.amsl.com>; Sun, 1 Jan 2017 02:49:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 hjRD7WLIhlKZ for <mmusic@ietfa.amsl.com>; Sun, 1 Jan 2017 02:49:17 -0800 (PST)
Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::235]) (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 D19A61294BC for <mmusic@ietf.org>; Sun, 1 Jan 2017 02:49:16 -0800 (PST)
Received: by mail-qt0-x235.google.com with SMTP id d45so202481052qta.1 for <mmusic@ietf.org>; Sun, 01 Jan 2017 02:49:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=s5ui/yFiIC57U3Uw290hYEXq3Opfq+0pqT38tdEHXCw=; b=hhlEeCwxZqXU3IArJ1zrfZQOeHsMFFXb4HQiCPaIK92Xx08Uur9XOg6qmGs0wWN0PV e8sr4SXYWzMf7xk891Foyh8Z7ZGmDKmjXSUfKbYe8h8zygez+5nz9tBOoQ4N7Qk+Lxba MqzaA8s2/dmsp5Y7JC+jgITwDlwV7+FsA83lpG66dwse+/Vs19pY+KiSgw1KuguoxXxG JuNBQOb+W/TJlyDdfr9UQ64UZlQWLUxLFbBgpKNgEDxq2qgyXOU7xvUno1V40HLY4NNc aY3b+SuBE8k3vtPkuxE8Y+1kS/Ty2jrxLrt8cF9PpEegsCnLU6/DghwWlanmLozIgXgN HmWA==
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:content-transfer-encoding; bh=s5ui/yFiIC57U3Uw290hYEXq3Opfq+0pqT38tdEHXCw=; b=Z2lySmhAD/6ohVtkzPnJ1dYvzKlsrmqXg3xmXeMXsOLMDLO/lou1Zxv5LlllNZl3Hb 0VYBKGZ5ZyCyF1llQv7xyPbqWRBZU44/VbFjVt6buzTV9w28SDO/z50GjYENA5cgiCVI CUyv6nVAeWl9xBMqgS9J0NBme5ItS+fMigieO8AIz1AGI8BycEFmGZF+JZzkYVXzfL9L nXsPHXJdS8rLmb4tASPN0cc2VC5WGGQ6Er2k/fczo975I6jfKisiwaAT/uGCbINrS/Ok l9/0FgaTE0TiGaMpRufVECT/4/X+ruAt5a2FGLosmp/GnrAWrUMf+Cvy6xVejKiCXi2/ Nmhw==
X-Gm-Message-State: AIkVDXKHe4CV0C14rkrYJPsxLJQKfXVH+8AT5YdwDLrFJvu0iJvaSs7c2RFD0ffWE7DTpWtH7IzTVZWMfvF5ig==
X-Received: by 10.200.35.14 with SMTP id a14mr48887832qta.159.1483267755947; Sun, 01 Jan 2017 02:49:15 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.38.233 with HTTP; Sun, 1 Jan 2017 02:49:15 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BF50DF5@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B4BF50A9B@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B4BF50DF5@ESESSMB209.ericsson.se>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Sun, 01 Jan 2017 21:49:15 +1100
Message-ID: <CABkgnnWLw7QPLd6qtgN1C-Pg+UHim6s=QK0EFgkYViQy8Ad2oQ@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/jKvFP_Y5SqwOLN2Et97a5KFYdPg>
Cc: "Jonathan Lennox (jonathan@vidyo.com)" <jonathan@vidyo.com>, "mmusic@ietf.org" <mmusic@ietf.org>, "Cullen Jennings (fluffy@iii.ca)" <fluffy@iii.ca>
Subject: Re: [MMUSIC] draft-4572-update: Spec contains references to a number of obsoleted RFCs
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Jan 2017 10:49:18 -0000

We can remove MD2.  MD5 is dead, SHA-1 is in its death throes, but MD2
is merely a (bad) memory.

On 30 December 2016 at 22:27, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> Hi,
>
>
>
> Please note the following:
>
>
>
> RFC 6149, which obsoletes RFC 1319, makes MD2 historic. Do people have a
> problem with that? I assume we’ll end up in trouble with the security folks
> if we keep the old RFC…
>
>
>
> And, considering MD2 is historic, do we even need to mention it in
> draft-4572-update anymore?
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
>
>
> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmberg
> Sent: 30 December 2016 11:42
> To: mmusic@ietf.org
> Cc: Jonathan Lennox (jonathan@vidyo.com) <jonathan@vidyo.com>; Cullen
> Jennings (fluffy@iii.ca) <fluffy@iii.ca>
> Subject: [MMUSIC] draft-4572-update: Spec contains references to a number of
> obsoleted RFCs
>
>
>
> Hi,
>
>
>
> The idnits check returns the following for draft-4572-update.
>
>
>
> ** Obsolete normative reference: RFC 1319 (ref. '3') (Obsoleted by RFC 6149)
>
>
>
>   ** Downref: Normative reference to an Informational RFC: RFC 1321 (ref.
> '4')
>
>
>
>   ** Obsolete normative reference: RFC 3280 (ref. '8') (Obsoleted by RFC
> 5280)
>
>
>
>   ** Obsolete normative reference: RFC 4234 (ref. '11') (Obsoleted by RFC
>
>      5234)
>
>
>
>   ** Obsolete normative reference: RFC 4288 (ref. '12') (Obsoleted by RFC
>
>      6838)
>
>
>
>   ** Obsolete normative reference: RFC 4346 (ref. '13') (Obsoleted by RFC
>
>      5246)
>
>
>
>   -- Obsolete informational reference (is this intentional?): RFC 2617 (ref.
>
>      '15') (Obsoleted by RFC 7235, RFC 7615, RFC 7616, RFC 7617)
>
>
>
>   -- Obsolete informational reference (is this intentional?): RFC 3525 (ref.
>
>      '20') (Obsoleted by RFC 5125)
>
>
>
>   -- Obsolete informational reference (is this intentional?): RFC 3851 (ref.
>
>      '22') (Obsoleted by RFC 5751)
>
>
>
> The reason for this is that we used RFC 4572 as base, and did not
> change/update the references.
>
>
>
> I had a look, and I don’t think there should be any issues in replacing the
> current RFCs with the new ones. But, please indicate if you see any issues.
>
>
>
> Regards,
>
>
>
> Christer

v2.23.0 | Report a Bug | By Email