Re: [Ips] Data Segment Padding

<Black_David@emc.com> Fri, 09 October 2009 06:45 UTC

Return-Path: <Black_David@emc.com>
X-Original-To: ips@core3.amsl.com
Delivered-To: ips@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B31CC3A68E6 for <ips@core3.amsl.com>; Thu, 8 Oct 2009 23:45:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.659
X-Spam-Level:
X-Spam-Status: No, score=-5.659 tagged_above=-999 required=5 tests=[AWL=-0.920, BAYES_20=-0.74, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W7ULIFbeE5sh for <ips@core3.amsl.com>; Thu, 8 Oct 2009 23:45:22 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id B76603A683C for <ips@ietf.org>; Thu, 8 Oct 2009 23:45:22 -0700 (PDT)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.3.2/Switch-3.1.7) with ESMTP id n996l4ZI017593 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Oct 2009 02:47:04 -0400
Received: from mailhub.lss.emc.com (nagas.lss.emc.com [10.254.144.15]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Fri, 9 Oct 2009 02:47:01 -0400
Received: from corpussmtp4.corp.emc.com (corpussmtp4.corp.emc.com [10.254.169.197]) by mailhub.lss.emc.com (Switch-3.3.2mp/Switch-3.3.2mp) with ESMTP id n996l0h5028420; Fri, 9 Oct 2009 02:47:01 -0400
Received: from CORPUSMX80A.corp.emc.com ([10.254.89.202]) by corpussmtp4.corp.emc.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 9 Oct 2009 02:47:00 -0400
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA48AC.4DA416C6"
Date: Fri, 9 Oct 2009 02:46:58 -0400
Message-ID: <9FA859626025B64FBC2AF149D97C944A03FE28E7@CORPUSMX80A.corp.emc.com>
In-Reply-To: <298d852f0910082033o49276d2diedf0a5b78d07da4b@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Ips] Data Segment Padding
Thread-Index: AcpIkVwQRr+UaQJiRaqASDoKIALnggAGjNxw
References: <298d852f0910082033o49276d2diedf0a5b78d07da4b@mail.gmail.com>
From: <Black_David@emc.com>
To: <yusunn@gmail.com>, <ips@ietf.org>
X-OriginalArrivalTime: 09 Oct 2009 06:47:00.0637 (UTC) FILETIME=[4D907CD0:01CA48AC]
X-EMM-EM: Active
Subject: Re: [Ips] Data Segment Padding
X-BeenThere: ips@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IP Storage <ips.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ips>
List-Post: <mailto:ips@ietf.org>
List-Help: <mailto:ips-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Oct 2009 06:45:23 -0000

No, padding is not supported (e.g., breaks data digests).
 
RFC 3720 has this to say in Section 10.7.7 which strongly
recommends 4-byte alignment of data segment boundaries:
The Data Segments of Data-In and Data-Out PDUs SHOULD be filled to the
integer number of 4 byte words (real payload) unless the F bit is set to
1.

Thanks,
--David

----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
black_david@emc.com        Mobile: +1 (978) 394-7754
----------------------------------------------------

________________________________

	From: ips-bounces@ietf.org [mailto:ips-bounces@ietf.org] On
Behalf Of yushang
	Sent: Thursday, October 08, 2009 11:34 PM
	To: ips@ietf.org
	Subject: [Ips] Data Segment Padding
	
	
	Hi , is it possible to send the middle part of a sequence of
DATA-OUT with data segment padding to 4 bytes boundary ? Many thanks.