File Content Provenance for Network File System version 4
draft-ietf-nfsv4-integrity-measurement-03
|
| Document |
Type |
|
Active Internet-Draft (nfsv4 WG)
|
|
Last updated |
|
2018-11-07
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network File System Version 4 C. Lever
Internet-Draft Oracle
Intended status: Standards Track November 7, 2018
Expires: May 11, 2019
File Content Provenance for Network File System version 4
draft-ietf-nfsv4-integrity-measurement-03
Abstract
This document specifies an OPTIONAL extension to NFS version 4 minor
version 2 that enables file provenance information to be conveyed
between NFS version 4.2 servers and clients. File provenance
information authenticates the creator of a file's content and helps
guarantee the content's integrity from creation to use.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 11, 2019.
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Lever Expires May 11, 2019 [Page 1]
Internet-Draft File Provenance for NFS November 2018
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Architecture and Terminology . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4
3. Protocol Extension Considerations . . . . . . . . . . . . . . 4
3.1. XDR Extraction . . . . . . . . . . . . . . . . . . . . . 4
4. Managing File Provenance Information on NFS Files . . . . . . 5
4.1. XDR Definition . . . . . . . . . . . . . . . . . . . . . 5
4.2. Storing File Provenance Information . . . . . . . . . . . 6
4.3. Retrieving File Provenance Information . . . . . . . . . 7
5. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 8
5.2. Instantiating File Provenance Information . . . . . . . . 8
5.2.1. Authorizing Updates to File Provenance Information . 9
5.3. Interaction With Non-Participating Implementations . . . 9
5.4. Performance Cost of Provenance Assessment . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
8.1. Normative References . . . . . . . . . . . . . . . . . . 13
8.2. Informative References . . . . . . . . . . . . . . . . . 14
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 14
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction
The security of software distribution systems is complex and
challenging, especially as software distribution has become
increasingly decentralized. An end administrator needs to trust that
she is running executables just as they are supplied by a software
vendor; in other words, that they have not been modified by malicious
actors, contracted system administration services, or broken hardware
or software. Software vendors want a guarantee that customer-
installed executables that fall under support contracts have
similarly not been modified.
There already exist mechanisms that protect file data during certain
portions of a file's life cycle:
o Whole file system checksumming can verify so-called Golden Master
installation media before it is used to install the software it
contains.
o File or block integrity mechanisms can protect data at rest on
storage servers.
Lever Expires May 11, 2019 [Page 2]
Internet-Draft File Provenance for NFS November 2018
Show full document text