IETF Logo Mail Archive

RE: [lisp] [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)

<l.wood@surrey.ac.uk> Mon, 13 January 2014 00:48 UTC

Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18EEE1ACCD9; Sun, 12 Jan 2014 16:48:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] 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 zu0P8HFOgrYa; Sun, 12 Jan 2014 16:48:02 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.153]) by ietfa.amsl.com (Postfix) with ESMTP id D3F281ACC91; Sun, 12 Jan 2014 16:48:01 -0800 (PST)
Received: from [195.245.231.67:64589] by server-17.bemta-5.messagelabs.com id 32/F2-19152-6B733D25; Mon, 13 Jan 2014 00:47:50 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-9.tower-82.messagelabs.com!1389574069!29061545!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received:
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27567 invoked from network); 13 Jan 2014 00:47:49 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-9.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 13 Jan 2014 00:47:49 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Mon, 13 Jan 2014 00:47:48 +0000
From: l.wood@surrey.ac.uk
To: farinacci@gmail.com
Date: Mon, 13 Jan 2014 00:45:52 +0000
Subject: RE: [lisp] [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Thread-Topic: [lisp] [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Thread-Index: Ac8P3nEsYE8Z6DG8TdaYBKdC9S/GqwAGl7Nt
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346BF@EXMB01CMS.surrey.ac.uk>
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <012801cf0d24$9b80b180$d2821480$@olddog.co.uk> <290E20B455C66743BE178C5C84F1240847E63346BA@EXMB01CMS.surrey.ac.uk> <201401121426.23719.mark.tinka@seacom.mu> <290E20B455C66743BE178C5C84F1240847E63346BE@EXMB01CMS.surrey.ac.uk>, <C03C9145-2F11-47F4-80DC-A387E4987DDD@gmail.com>
In-Reply-To: <C03C9145-2F11-47F4-80DC-A387E4987DDD@gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 13 Jan 2014 07:12:20 -0800
Cc: mark.tinka@seacom.mu, mpls@ietf.org, ietf@ietf.org, lisp@ietf.org, gorry@erg.abdn.ac.uk, david.black@emc.com, jnc@mit.edu, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 00:48:05 -0000

Really, you'd want to expose the pseudoheader check at endhosts; a well-instrumented Linux box could tell you a lot
about checksum failures.

But in this case, a router would be decapping UDP/MPLS tunnels as an endpoint, so could report on checksum failures -
if the checksum wasn't zero.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Dino Farinacci [farinacci@gmail.com]
Sent: 12 January 2014 21:37
To: Wood L  Dr (Electronic Eng)
Cc: <mark.tinka@seacom.mu>; <mpls@ietf.org>; gorry@erg.abdn.ac.uk; lisp@ietf.org; david.black@emc.com; randy@psg.com; tsvwg@ietf.org; jnc@mit.edu; ietf@ietf.org
Subject: Re: [lisp] [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)

> Do any routers count TCP/UDP checksum failures, much less
> expose the count via SNMP?

Typically they do but only for packets destined to them. Much like hosts would check the header checksum.

Dino

v2.23.0 | Report a Bug | By Email