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

Curtis Villamizar <curtis@ipv6.occnc.com> Wed, 15 January 2014 20:02 UTC

Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E2231AE1A6; Wed, 15 Jan 2014 12:02:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level:
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-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 BFERJXjAteJ6; Wed, 15 Jan 2014 12:02:28 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 30DF71AE199; Wed, 15 Jan 2014 12:02:28 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0FK28cx022175; Wed, 15 Jan 2014 15:02:08 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401152002.s0FK28cx022175@maildrop2.v6ds.occnc.com>
To: Randy Bush <randy@psg.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Wed, 15 Jan 2014 17:08:09 +0600." <m2a9exmrja.wl%randy@psg.com>
Date: Wed, 15 Jan 2014 15:02:07 -0500
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, lisp@ietf.org, ietf@ietf.org, wes@mti-systems.com, tsvwg@ietf.org, jnc@mit.edu
Subject: Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 20:02:29 -0000

In message <m2a9exmrja.wl%randy@psg.com>
Randy Bush writes:
> 
> [ you insist on cc:ing me, so you get to endure my opinions ]

Not a problem (this time).  :-)

> > it seems that there are no valid statistics for the current Internet
> > to sustain your case.
>  
> as we discussed privately, there seem to be no real measurements to
> sustain any case.  this is all conjecturbation.
>  
> what i do not understand is why, given the lack of solid evidence that
> we are in a safe space, you and others are not willing to spend a few
> euro cents to have a reasonable level of assurance at this layer.
>  
> randy


Randy,

See http://www.ietf.org/mail-archive/web/mpls/current/msg11279.html
for reasons why routers would want to avoid having to fill in a
checksum.  It would have been more feasible for an FCS at the end of
the packet for these cases but the UDP checksum is in the front.

This entire discussion is over putting in a SHOULD rather than a MUST
in two places, UDP checksum and congestion control, plus deferring
defining the congestion control for MPLS over UDP until deployments
show a need for it.

Curtis