Re: draft-ietf-ipngwg-icmp-v3-06.txt and affect on RFC3542
JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp> Thu, 21 April 2005 14:52 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOd2V-0004Hf-DQ; Thu, 21 Apr 2005 10:52:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DOd2T-0004HU-8j for ipv6@megatron.ietf.org; Thu, 21 Apr 2005 10:52:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06667 for <ipv6@ietf.org>; Thu, 21 Apr 2005 10:52:19 -0400 (EDT)
Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOdDs-0001Qs-Fg for ipv6@ietf.org; Thu, 21 Apr 2005 11:04:11 -0400
Received: from ocean.jinmei.org (unknown [2001:200:0:8002:dc71:e81b:9816:9a48]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id A704315263; Thu, 21 Apr 2005 23:54:32 +0900 (JST)
Date: Thu, 21 Apr 2005 23:53:05 +0900
Message-ID: <y7vbr88kwq6.wl@ocean.jinmei.org>
From: JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>
To: Kristine Adamson <adamson@us.ibm.com>
In-Reply-To: <OF5F34DE98.7F123361-ON87256FDD.0048B1F9-85256FDD.0049BABE@us.ibm.com>
References: <200504060104.j3614Bau005456@cichlid.raleigh.ibm.com> <OF5F34DE98.7F123361-ON87256FDD.0048B1F9-85256FDD.0049BABE@us.ibm.com>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: ipv6@ietf.org, Nicholas Carbone <pizza@us.ibm.com>
Subject: Re: draft-ietf-ipngwg-icmp-v3-06.txt and affect on RFC3542
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org
>>>>> On Fri, 8 Apr 2005 07:24:25 -0600, >>>>> Kristine Adamson <adamson@us.ibm.com> said: >> Suggestion: >> 1) Set up an issue tracker for this (and perhaps every IPv6 RFC for >> which there are some known errors/omissions?) that keeps track of >> these sorts of things. That way folk will be able to more easily >> find the list of outstanding issues (and their likely resolution), >> and we (the IETF community) won't lose track of them. >> >> 2) Although it may be overkill in this case, one could easily publish >> a (very!) short RFC just listing the additional code points, so >> that they are documened in the RFC series, and folk looking at the >> older RFC can find the new RFC via the "updated by" tag. > Besides adding the programming names of the new ICMPv6 code points to > RFC3542, the following documents an old, minor problem with RFC3542, that > was listed in the errata. This problem could also be resolved with a new, > short RFC that updates RFC3542. Since there are 2 problems that could be > resolved with a new RFC, do we now have sufficient reasons to publish a > new RFC? Thanks! Opinions may vary, but I personally still do *not* think the followings are enough for even a "very short RFC": - the minor correction recorded at the RFC errata page - macro names for the two new ICMPv6 codes I personally think it makes more sense to file the issues at an issue tracker (suggestion 1 from Thomas). With future possible issues/corrections/additions in that page, we'll probably reach the point where most of us can agree on the need for an updating RFC. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
- draft-ietf-ipngwg-icmp-v3-06.txt and affect on RF… Kristine Adamson
- RE: draft-ietf-ipngwg-icmp-v3-06.txt and affect o… Mukesh.K.Gupta
- Re: draft-ietf-ipngwg-icmp-v3-06.txt and affect o… JINMEI Tatuya / 神明達哉
- Re: draft-ietf-ipngwg-icmp-v3-06.txt and affect o… Kristine Adamson
- Re: draft-ietf-ipngwg-icmp-v3-06.txt and affect o… JINMEI Tatuya / 神明達哉
- Re: draft-ietf-ipngwg-icmp-v3-06.txt and affect o… Thomas Narten
- Re: draft-ietf-ipngwg-icmp-v3-06.txt and affect o… Tom Petch
- Re: draft-ietf-ipngwg-icmp-v3-06.txt and affect o… Pekka Savola
- Re: draft-ietf-ipngwg-icmp-v3-06.txt and affect o… Kristine Adamson
- Re: draft-ietf-ipngwg-icmp-v3-06.txt and affect o… JINMEI Tatuya / 神明達哉
- Original intent of M/O bits [was Re: IPv6 WG Last… Thomas Narten
- Re: Original intent of M/O bits JINMEI Tatuya / 神明達哉
- Re: [dhcwg] Re: Original intent of M/O bits Ralph Droms
- Re: [dhcwg] Re: Original intent of M/O bits JINMEI Tatuya / 神明達哉