[nfsv4] Fwd: New Version Notification for draft-quigley-nfsv4-labeled-04.txt
"Haynes, Tom" <Tom.Haynes@netapp.com> Thu, 27 October 2011 04:08 UTC
Return-Path: <Tom.Haynes@netapp.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C9C421F8AA9 for <nfsv4@ietfa.amsl.com>; Wed, 26 Oct 2011 21:08:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.948
X-Spam-Level:
X-Spam-Status: No, score=-9.948 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IG7ZxyOOWIYC for <nfsv4@ietfa.amsl.com>; Wed, 26 Oct 2011 21:08:08 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id D36DE21F8A64 for <nfsv4@ietf.org>; Wed, 26 Oct 2011 21:07:56 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="4.69,412,1315206000"; d="scan'208,217"; a="592669451"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 26 Oct 2011 21:07:56 -0700
Received: from sacrsexc2-prd.hq.netapp.com (sacrsexc2-prd.hq.netapp.com [10.99.115.28]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id p9R47u0M005514 for <nfsv4@ietf.org>; Wed, 26 Oct 2011 21:07:56 -0700 (PDT)
Received: from VMWEXCEHT03-PRD.hq.netapp.com ([10.106.76.241]) by sacrsexc2-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 26 Oct 2011 21:07:52 -0700
Received: from SACEXCMBX04-PRD.hq.netapp.com ([169.254.6.15]) by vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) with mapi id 14.01.0289.001; Wed, 26 Oct 2011 21:07:46 -0700
From: "Haynes, Tom" <Tom.Haynes@netapp.com>
To: "nfsv4@ietf.org" <nfsv4@ietf.org>
Thread-Topic: New Version Notification for draft-quigley-nfsv4-labeled-04.txt
Thread-Index: AQHMlF2iLPendtDCX0COpTNmHS59Lg==
Date: Thu, 27 Oct 2011 04:07:45 +0000
Message-ID: <9A5C483F-F997-4663-8CAA-0F158273AF38@netapp.com>
References: <20111027040507.26666.85838.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.106.53.51]
Content-Type: multipart/alternative; boundary="_000_9A5C483FF99746638CAA0F158273AF38netappcom_"
MIME-Version: 1.0
X-OriginalArrivalTime: 27 Oct 2011 04:07:52.0227 (UTC) FILETIME=[FF41BF30:01CC945D]
Subject: [nfsv4] Fwd: New Version Notification for draft-quigley-nfsv4-labeled-04.txt
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 27 Oct 2011 04:08:09 -0000
FYI - an update of the document. Begin forwarded message: From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>> Date: October 26, 2011 11:05:07 PM CDT To: <thomas@netapp.com<mailto:thomas@netapp.com>> Cc: <thomas@netapp.com<mailto:thomas@netapp.com>>, <jarrett.lu@oracle.com<mailto:jarrett.lu@oracle.com>>, <sds@tycho.nsa.gov<mailto:sds@tycho.nsa.gov>>, <jmorris@namei.org<mailto:jmorris@namei.org>> Subject: New Version Notification for draft-quigley-nfsv4-labeled-04.txt A new version of I-D, draft-quigley-nfsv4-labeled-04.txt has been successfully submitted by Thomas Haynes and posted to the IETF repository. Filename: draft-quigley-nfsv4-labeled Revision: 04 Title: Labeled NFS Creation date: 2011-10-26 WG ID: Individual Submission Number of pages: 20 Abstract: This Internet-Draft describes additions to NFSv4 to support Mandatory Access Control systems. The current draft describes the mechanism for transporting a MAC security label using the NFSv4 protocol and the semantics required for that label. In addition to this it describes an example system of using this label in a fully MAC aware environment. The IETF Secretariat