Re: "RFC4941bis" and draft-gont-6man-non-stable-iids

Fernando Gont <fgont@si6networks.com> Thu, 20 July 2017 11:16 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88A1712EAF0 for <ipv6@ietfa.amsl.com>; Thu, 20 Jul 2017 04:16:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 GJZvaEzdwuIZ for <ipv6@ietfa.amsl.com>; Thu, 20 Jul 2017 04:16:08 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF59E131687 for <6man@ietf.org>; Thu, 20 Jul 2017 04:16:01 -0700 (PDT)
Received: from [192.168.0.25] (unknown [46.13.174.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 03C2D80D4E; Thu, 20 Jul 2017 13:17:30 +0200 (CEST)
Subject: Re: "RFC4941bis" and draft-gont-6man-non-stable-iids
To: Francis Dupont <Francis.Dupont@fdupont.fr>
Cc: "6man@ietf.org" <6man@ietf.org>
References: <201707191117.v6JBH9nN037512@givry.fdupont.fr>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <b41e29c0-3ca7-bf3b-5887-c9affaedca81@si6networks.com>
Date: Thu, 20 Jul 2017 14:16:28 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <201707191117.v6JBH9nN037512@givry.fdupont.fr>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/LtonTMWtQqgrvwLntiDdy6DQ32A>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 11:16:10 -0000

Hello, Francis,

On 07/19/2017 02:17 PM, Francis Dupont wrote:
>>  Among the list of RFCs to be progressed to full std is/was RFC4941
>>  ("Privacy Extensions for Stateless Address Autoconfiguration in IPv6").
> 
> => I even published a document explaining what I thought about the
> whole idea (and I didn't change my mind).

COuld you please provide a reference?



>>  As it stands, RFC4941 has a number of issues:
>>  * Using MD5 as opposed to something better
> 
> => for this use MD5 is not bad. Just consider it as a not crypto hash.
> 
> Now RFC4941bis is currently heavily deployed so it is far too soon
> to try to obsolete it.

I'm not necessarily thinking about obsoleting it. This is, say, an open
question. I do think that you cannot move RFC4941 to STD, though.



> When I went to the mic at a previous IETF meeting some years ago
> to ask the IPv6 specs to be raise to full standard with at first
> the IPv6 protocol itself (done, THANKS!!!). If the RFC4941 is left
> at the border of the road I shan't be sad...

I don't think RFC4941 meet the criteria for elevating a document to STD,
though.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492