Re: RFC 4861 missing updated-by

Suresh Krishnan <suresh.krishnan@gmail.com> Fri, 11 August 2017 02:52 UTC

Return-Path: <suresh.krishnan@gmail.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 E71D8129AD3 for <ipv6@ietfa.amsl.com>; Thu, 10 Aug 2017 19:52:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_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 SzDqzSvCyOpN for <ipv6@ietfa.amsl.com>; Thu, 10 Aug 2017 19:52:40 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::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 6308C129A92 for <ipv6@ietf.org>; Thu, 10 Aug 2017 19:52:40 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id p68so15566829ywg.0 for <ipv6@ietf.org>; Thu, 10 Aug 2017 19:52:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=0YtuSB8gJhwemqWemNyGgmAVoS8oyAnPTHye2KUcEpE=; b=C+lnFAoRdwRLwo7c6Md3IBdR2Nq0iI3ZtNcFVW1g5iwlJGl0Agk4CUz4PRgnV6IbLY uXfZdRMNLtw21QhEjxAcNFV/z123N9WpCXiLBa3BEgzQka1c1FiHZdjeMf7Di1aIFlHL WwrjFD+v1RP+TSOmx/4g/AR+hTW5sBmdWUTR9BbF7HJGTLegz//lc7kbOT8YiQhGgKxq 5brbb7V4c17pT3+OVifHgHOWNcV3E/iTkhwQz6PT8Jzo9WMkbPit7SoY38oq3yY9t229 OSiYur0WUnXm82G2BU40u+KjyMBkaLtNK5ewvMKDWpe92tCsHv8lyTdC7o0uG2inY+B+ Stqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=0YtuSB8gJhwemqWemNyGgmAVoS8oyAnPTHye2KUcEpE=; b=Pt+zWUsEQdWxcOEzFUEQ+9iaM4NHW/HtuCR3VclNa8GRwWfkEMtt/dZryrAGBjsYEV kSvH8+ONRiE8ljLhy5iCi1sB7S8gDDvwk8BddFgi38dIHGLodGekZW/XdrZ+ejwGe7Re n+OgZmopKbxYBqZ/4DL5FGPrMg+8+d9WBUzkdOLnt3xommJzfzbvNG/xX41D30MOmTiC JkSn2mhx9k4NlnvrEn/v1v+lo15jk7Y+tm34kP8q2rY3ksf31KJCwwT11SVjJnhjjPbH 5YeqHwHkwYoXLlVgeJa+PQBsMiJNyfFVRWU+pseJWAZEeRJnKVkqXeb9BCuJ9qaDvjwm tuLA==
X-Gm-Message-State: AHYfb5gGIfZtRAKSDiRgElva8LcvQ0V8WRzHYmsbnih428rbv2B1QKn3 ZtQ0q99vAPCdIw==
X-Received: by 10.129.156.74 with SMTP id t71mr11996089ywg.350.1502419959630; Thu, 10 Aug 2017 19:52:39 -0700 (PDT)
Received: from [10.0.0.5] (45-19-110-76.lightspeed.tukrga.sbcglobal.net. [45.19.110.76]) by smtp.gmail.com with ESMTPSA id i71sm2723022ywg.47.2017.08.10.19.52.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 Aug 2017 19:52:38 -0700 (PDT)
From: Suresh Krishnan <suresh.krishnan@gmail.com>
Message-Id: <2664CA78-2291-46C7-ACF9-460AA3A51706@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_6F75BE95-0796-4E8B-A24C-D2056843660C"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: RFC 4861 missing updated-by
Date: Thu, 10 Aug 2017 22:52:36 -0400
In-Reply-To: <826ee900-0edf-2bb4-ed35-3824b6ad8bba@gmail.com>
Cc: ipv6@ietf.org
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <alpine.DEB.2.02.1708100947130.2261@uplift.swm.pp.se> <8447.1502388439@obiwan.sandelman.ca> <a3ed97e2-e907-6a20-0d00-6de532784f0c@nostrum.com> <826ee900-0edf-2bb4-ed35-3824b6ad8bba@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/jmTk-b_vLZGDUMSGzlaQiUrwYCU>
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: Fri, 11 Aug 2017 02:52:43 -0000

Hi all,
  I had a short chat with Mikael about this during the Prague IETF. One of the major issues I have encountered is that we do not, as a community, have a common understanding of what the “Updates:” tag means (or even what it is supposed to mean). Until that gets resolved, there will be no clear indication on when to mark a document as updated and when not to. As for this Erratum, I will hold onto it until we have a better idea on how to proceed. As an example another document in this category is RFC4191 that I personally think should update RFC2461/RFC4861 because of changing the RA flag bits. Similarly, should RFC4389 update RFC4861 for the same reason as well?

Thanks
Suresh

> On Aug 10, 2017, at 4:06 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> On 11/08/2017 06:38, Robert Sparks wrote:
>> This is a question for the IESG (it's more a question of policy than it 
>> is tool capability).
> 
> I would say it's a question for the RFC Editor, who would ask for advice
> from the IESG since these are IETF stream documents. (It's the RFC Editor
> who maintains the metatdata for RFCs.)
> 
>    Brian
> 
>> 
>> I'm pretty sure the question's been asked before (and the discussion led 
>> to a "no, if you want to fix this, do it with an RFC").
>> 
>> RjS
>> 
>> 
>> On 8/10/17 1:07 PM, Michael Richardson wrote:
>>> Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>>>> FYI. I decided to raise an errata against RFC6275 that seems to update
>>>> RFC4861 without this being noted anywhere in either document.
>>> 
>>> Are we able to update the metadata on RFC4861 in response to this errata?
>>> I realize we can't re-issue 6275.
>>> 
>>> Since the Updates is to make sure that readers of 4861 know about new things,
>>> the metadata 4861->6275 (which shows up in the tools page and datatracker for
>>> the old documents) is really the important direction.
>>> 
>>> --
>>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>>>  -= IPv6 IoT consulting =-
>>> 
>>> 
>>> 
>> 
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>> .
>> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org <mailto:ipv6@ietf.org>
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 <https://www.ietf.org/mailman/listinfo/ipv6>
> --------------------------------------------------------------------