Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard

Stewart Bryant <stbryant@cisco.com> Mon, 27 January 2014 16:40 UTC

Return-Path: <stbryant@cisco.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 09B911A0276; Mon, 27 Jan 2014 08:40:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level:
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, 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 MUYC7CJ9KC9D; Mon, 27 Jan 2014 08:40:56 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id C017E1A029C; Mon, 27 Jan 2014 08:40:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=822; q=dns/txt; s=iport; t=1390840854; x=1392050454; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=iaxdndm+s+9xAew4nIrH3Gjx/fIspLkrns2aB9rsCwM=; b=Hpug268PCSHkRhvtUcpntgjdTLXFk18GSvKLCfh88PMtvRi8DhV3YCHA DxKmvlRkLlsQoGdjV2dgZ90TtHo3r3STD1dXNMICmstmf4BWy6H5JEqYN jKM9psrBv3cSNHW3pBfk4g1syqnwbvuSrZXQd16X+3/FF5f6n4/ScUr2L E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAPyK5lKQ/khR/2dsb2JhbABZDoJ+OL0vgRUWdIIlAQEBBDhAARALGAkWBAsJAwIBAgFFBgEMAQcBAQWHfA3HEReOPAEBTweEOAEDmCeSHoFvfz+BcQ
X-IronPort-AV: E=Sophos;i="4.95,729,1384300800"; d="scan'208";a="4256365"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-1.cisco.com with ESMTP; 27 Jan 2014 16:40:53 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0RGeq4x018651 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Jan 2014 16:40:52 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s0RGeou7025359; Mon, 27 Jan 2014 16:40:51 GMT
Message-ID: <52E68C12.2050308@cisco.com>
Date: Mon, 27 Jan 2014 16:40:50 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>, curtis@ipv6.occnc.com
References: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.com> <52E2BBC0.2030203@isi.edu>
In-Reply-To: <52E2BBC0.2030203@isi.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.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: Mon, 27 Jan 2014 16:40:58 -0000

On 24/01/2014 19:15, Joe Touch wrote:
>
>> This eliminates the "expands the reach of MPLS argument".
>>
>> First UDP checksums:
>>
>>    The UDP checksum is at the beginning of the payload.  Please see
>> http://www.ietf.org/mail-archive/web/mpls/current/msg11279.html
>>    This makes filling in a new UDP checksum infeasible on most high end
>>    hardware.
>
> That argument would make sense if most hardware wasn't 
> store-and-forward on a per-packet basis.
They may be store and forward, but most of the high end designs
use multiple grades of memory putting the packet in "slow memory"
and providing a snapshot of the header in "fast memory" to the
forwarder. Thus although the whole packet is in the system, it
it is not accessible to the engine that would need to calculate the
c/s.

Stewart