IETF Logo Mail Archive

[Taps] TAPS Transports and ICMP

"Pal Martinsen (palmarti)" <palmarti@cisco.com> Thu, 04 June 2015 10:48 UTC

Return-Path: <palmarti@cisco.com>
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 280ED1A88E0 for <taps@ietfa.amsl.com>; Thu, 4 Jun 2015 03:48:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 Phj-OY4AwJXS for <taps@ietfa.amsl.com>; Thu, 4 Jun 2015 03:48:03 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEDC71A00CF for <taps@ietf.org>; Thu, 4 Jun 2015 03:48:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=596; q=dns/txt; s=iport; t=1433414883; x=1434624483; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=WilZWJ42HjyPW7LqAiY3W3LfFCZBW0xfFu/3qdX8noo=; b=OykcvL5au7fEEt00og52ivMMTm9NVFaTpJlEJnD7G2Ly1ggJP07WDtrr uf5Ac9oIvTl9VLmzN2Ubh51anc/rBrybs0VoVN4z/36O3N0SbIYBHEohj PcUHdwoZt2er7M48ksFX7dnCIZskx653N5+DuKh3H9Lmek1HaZRuxBua0 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AaBQBzLHBV/4MNJK1bgxCBOIMYuy2Hb4EbOhIBAQEBAQEBgQqEKSMRVwEiAiYCBDAVEgSIQKctj1+jbQEBAQEBBQEBAQEBAQEBGoEhkhcvgRYFkxqLJJdQJGGDFoI1gQEBAQE
X-IronPort-AV: E=Sophos;i="5.13,552,1427760000"; d="scan'208";a="156360809"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-6.cisco.com with ESMTP; 04 Jun 2015 10:48:01 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t54Am1f4011194 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <taps@ietf.org>; Thu, 4 Jun 2015 10:48:01 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.183]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0195.001; Thu, 4 Jun 2015 05:48:01 -0500
From: "Pal Martinsen (palmarti)" <palmarti@cisco.com>
To: "taps@ietf.org" <taps@ietf.org>
Thread-Topic: TAPS Transports and ICMP
Thread-Index: AQHQnrPtkK68ApcbdEG/b2ediao1lg==
Date: Thu, 04 Jun 2015 10:48:01 +0000
Message-ID: <00597CB8-D128-408A-8F35-BA98CDF45A62@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.72.232]
Content-Type: text/plain; charset="utf-8"
Content-ID: <4DA52AFB6534334CA08AD31F6DBED547@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/WHI7XIWn5v7W_N3yUNy1joFZpcM>
Subject: [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 10:48:04 -0000

Hi,

I was wondering…

Today app developers actively need to listen for ICMP messages and do smart things (tm) if they receive them. ICMP also offers a nice set of tools to do a few neat tricks. Application developers rarely bothers to care about that. 

Does it make sense for the TAPS transports draft to add ICMP? ICMP feedback can possibly influence how the other transport protocols in the draft behave.

 .-.
Pål-Erik

v2.23.0 | Report a Bug | By Email