[nfsv4] Sharing same TCP connection for NFSv3 and NFSv4 traffic

"Erasani, Pranoop" <Pranoop.Erasani@netapp.com> Wed, 18 August 2010 03:33 UTC

Return-Path: <Pranoop.Erasani@netapp.com>
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3DF503A65A5 for <nfsv4@core3.amsl.com>; Tue, 17 Aug 2010 20:33:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 T-Amx0QK-5rG for <nfsv4@core3.amsl.com>; Tue, 17 Aug 2010 20:33:34 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by core3.amsl.com (Postfix) with ESMTP id B75A63A6805 for <nfsv4@ietf.org>; Tue, 17 Aug 2010 20:33:31 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="4.56,225,1280732400"; d="scan'208,217"; a="430818365"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 17 Aug 2010 20:33:40 -0700
Received: from svlrsexc2-prd.hq.netapp.com (svlrsexc2-prd.hq.netapp.com [10.57.115.31]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id o7I3Xerq004300 for <nfsv4@ietf.org>; Tue, 17 Aug 2010 20:33:40 -0700 (PDT)
Received: from SACMVEXC3-PRD.hq.netapp.com ([10.99.115.21]) by svlrsexc2-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 17 Aug 2010 20:33:40 -0700
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_01CB3E86.267F18FB"
Date: Tue, 17 Aug 2010 20:33:42 -0700
Message-ID: <43EEF8704A569749804F545E3306FCE3087B2322@SACMVEXC3-PRD.hq.netapp.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Sharing same TCP connection for NFSv3 and NFSv4 traffic
Thread-Index: Acs+hifzTkF3xWBfTRO6UyLCTLIx+A==
From: "Erasani, Pranoop" <Pranoop.Erasani@netapp.com>
To: nfsv4@ietf.org
X-OriginalArrivalTime: 18 Aug 2010 03:33:40.0748 (UTC) FILETIME=[26C9A4C0:01CB3E86]
Subject: [nfsv4] Sharing same TCP connection for NFSv3 and NFSv4 traffic
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nfsv4>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Aug 2010 03:33:41 -0000

Hello,

 

This distribution list is probably not the right one for this kind of
question. I figured I would get the best answer here.

 

Out of curiosity, Do any of the clients that you work on or that you
know of, share the same TCP connection for NFSv3 and NFSv4 traffic?

 

- Pranoop