IETF Logo Mail Archive

Re: draft-ietf-ipngwg-icmp-v3-06.txt and affect on RFC3542

Pekka Savola <pekkas@netcore.fi> Mon, 04 April 2005 15:01 UTC

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 LAA15750 for <ipv6-web-archive@ietf.org>; Mon, 4 Apr 2005 11:01:13 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DITCg-000145-V0 for ipv6-web-archive@ietf.org; Mon, 04 Apr 2005 11:09:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DIT2q-0003mI-2S; Mon, 04 Apr 2005 10:59:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DIT2n-0003mA-Nd for ipv6@megatron.ietf.org; Mon, 04 Apr 2005 10:59:14 -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 KAA15597 for <ipv6@ietf.org>; Mon, 4 Apr 2005 10:59:10 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DITAi-00011Z-BL for ipv6@ietf.org; Mon, 04 Apr 2005 11:07:25 -0400
Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id j34EwiQ31540; Mon, 4 Apr 2005 17:58:44 +0300
Date: Mon, 04 Apr 2005 17:58:44 +0300
From: Pekka Savola <pekkas@netcore.fi>
To: JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>
In-Reply-To: <y7vfyy7i77o.wl@ocean.jinmei.org>
Message-ID: <Pine.LNX.4.61.0504041757410.31462@netcore.fi>
References: <y7vr7hvjjnj.wl@ocean.jinmei.org> <OF8DDF5407.BE291018-ON87256FD6.0048182D-85256FD6.0048A2C7@us.ibm.com> <y7vfyy7i77o.wl@ocean.jinmei.org>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="1589707168-1583352436-1112626724=:31462"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: Kristine Adamson <adamson@us.ibm.com>, ipv6@ietf.org
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb

On Mon, 4 Apr 2005, JINMEI Tatuya / [ISO-2022-JP] ¿ÀÌÀãºÈ wrote:
> As someone else in this thread pointed out, this type of issue can
> always happen when the IETF standardizes any new ICMP types/codes,
> extension header identifier (the number of the "next header" field"),
> whatever.  Clearly, we cannot update the API specification every time
> we see this type of event, so we need to make a consensus on how
> serious the related portability issue is.  If others agree on the
> severity, I won't oppose to the conclusion.

The new values could also be defined at the appendix of icmp-v3, but 
then we'd have to agree on the proper names now, and there could be 
confusion between the revision of the advanced api and icmp-v3...

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email