IETF Logo Mail Archive

Re: [Taps] TAPS Transports and ICMP

Joe Touch <touch@isi.edu> Thu, 04 June 2015 15:43 UTC

Return-Path: <touch@isi.edu>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E77FB1A8A68 for <taps@ietfa.amsl.com>; Thu, 4 Jun 2015 08:43:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 H-09INeG5CX0 for <taps@ietfa.amsl.com>; Thu, 4 Jun 2015 08:43:56 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 203021A8A65 for <taps@ietf.org>; Thu, 4 Jun 2015 08:43:56 -0700 (PDT)
Received: from [192.168.1.5] (pool-71-103-148-202.lsanca.dsl-w.verizon.net [71.103.148.202]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id t54FhEdh020520 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 4 Jun 2015 08:43:24 -0700 (PDT)
Message-ID: <55707211.8010609@isi.edu>
Date: Thu, 04 Jun 2015 08:43:13 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: "Pal Martinsen (palmarti)" <palmarti@cisco.com>, "taps@ietf.org" <taps@ietf.org>
References: <00597CB8-D128-408A-8F35-BA98CDF45A62@cisco.com>
In-Reply-To: <00597CB8-D128-408A-8F35-BA98CDF45A62@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: t54FhEdh020520
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/GZQo5L6KxC6atRTSMEXStWsbS9Q>
Subject: Re: [Taps] TAPS Transports and ICMP
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2015 15:43:57 -0000


On 6/4/2015 3:48 AM, Pal Martinsen (palmarti) wrote:
...
> Does it make sense for the TAPS transports draft to add ICMP?

ICMP is not a transport protocol.

The ways in which transport protocols either terminate or pass-through
ICMP messages is part of the transport protocol abstract API.

E.g., for UDP and TCP see RFC1122.

UDP passes all ICMP messages to the app.

TCP passes only dest unreachable types 0, 1, and 5, time exceeded and
parameter problem. All others it interprets or ignores internally and
it's not clear it should pass up to the app.

Joe

v2.23.0 | Report a Bug | By Email