[nfsv4] Can we make draft-quigley-nfsv4-lfs-registry-00 a WG item?

Thomas Haynes <thomas.haynes@primarydata.com> Wed, 30 April 2014 20:27 UTC

Return-Path: <thomas.haynes@primarydata.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D01FC1A0973 for <nfsv4@ietfa.amsl.com>; Wed, 30 Apr 2014 13:27:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 Nj6IfJHa6Up6 for <nfsv4@ietfa.amsl.com>; Wed, 30 Apr 2014 13:27:10 -0700 (PDT)
Received: from mail-pa0-f49.google.com (mail-pa0-f49.google.com [209.85.220.49]) by ietfa.amsl.com (Postfix) with ESMTP id 1BB411A0916 for <nfsv4@ietf.org>; Wed, 30 Apr 2014 13:27:10 -0700 (PDT)
Received: by mail-pa0-f49.google.com with SMTP id kq14so2606918pab.8 for <nfsv4@ietf.org>; Wed, 30 Apr 2014 13:27:08 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:content-transfer-encoding :subject:message-id:date:to:mime-version; bh=b7IoRyiEfvXUii4DmEX1qmw7QKwToKtX1vh8Ul6kfI0=; b=mni6GE00UI0wNLn39BeKGfv4JG/m8z23Azi9RpBwOUydrb8duRSLJ0JWw7Zt6Z8+/O kTprXQsPrNrjjsgjcy+1EkkBGC07K9xjlNg/v614/8YoGKkC9ondNuZhfNnfRteefQpm eG5rVHskerJvZzuEYsJZBZhKlSIjEp2XoVa/x92SvergzHdENv017hrCdMD/X3QaCOxb qWA3u3ynsAmnS0AlIzQxx3EcR+XULrkaChDFBulSG4679n+FVV2bdjmnh8XwyyxtxquY 7IKow7lsL2R2tMAdD5UHmytr6PyQUmAXjwsEd+4j90HQxIVxwDvemLXEZZOU8e+OIuQN fQEQ==
X-Gm-Message-State: ALoCoQnHZktPEURM9dPCD1OXVXYSNo0NqmLMYWxzXukep6AMucwZq45rFXPg+mVhZEgy+aD3dlk3
X-Received: by 10.66.148.70 with SMTP id tq6mr12769729pab.56.1398889628302; Wed, 30 Apr 2014 13:27:08 -0700 (PDT)
Received: from loghyr.internal.excfb.com (c-76-126-118-221.hsd1.ca.comcast.net. [76.126.118.221]) by mx.google.com with ESMTPSA id yv7sm142758173pac.33.2014.04.30.13.27.07 for <nfsv4@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 30 Apr 2014 13:27:07 -0700 (PDT)
From: Thomas Haynes <thomas.haynes@primarydata.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <6A71A3B1-A1FC-4AD7-B86F-E445CFC78C72@primarydata.com>
Date: Wed, 30 Apr 2014 13:27:06 -0700
To: "nfsv4 list (nfsv4@ietf.org)" <nfsv4@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/nfsv4/tDDq5eGbkOGe0eiKWnyXGKiaADM
Subject: [nfsv4] Can we make draft-quigley-nfsv4-lfs-registry-00 a WG item?
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 30 Apr 2014 20:27:11 -0000

Hi Spencer,

Can we make this a WG item and proceed into WG Last Call?

Registry Specification for Mandatory Access Control (MAC) Security Label Formats

Abstract

   In the past Mandatory Access Control (MAC) systems have used very
   rigid policies which were hardcoded into the particular protocol and
   platform.  As MAC systems are more widely deployed additional
   flexibility in mechanism and policy is required.  Where traditional
   trusted systems implemented Multi-Level Security (MLS) and integrity
   models, modern systems have expanded to include technologies such as
   type enforcement.  Due to the wide range of policies and mechanisms
   it has proven through past efforts to be virtually impossible to
   accomodate all parties in one security label format and model.

   To allow multiple MAC mechanisms and label formats in a network, this
   document proposes a registry of label format specifications.  This
   registry contains several identifiers to accomodate both integer and
   string preferences and associates those identifiers with an extensive
   document outlining the exact syntax and use of the particular label
   format.

This was draft-quigley-label-format-registry-02, where it languished out
of sight. 

The document is pretty short and is mainly a call for IANA to establish
a new registry.

Thanks,
Tom