Re: [nfsv4] Barry Leiba's Discuss on draft-ietf-nfsv4-lfs-registry-04: (with DISCUSS and COMMENT)

Tom Haynes <thomas.haynes@primarydata.com> Thu, 09 April 2015 01:21 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 49A9F1ACD89 for <nfsv4@ietfa.amsl.com>; Wed, 8 Apr 2015 18:21:16 -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=unavailable
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 tGplAajboxCc for <nfsv4@ietfa.amsl.com>; Wed, 8 Apr 2015 18:21:12 -0700 (PDT)
Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 023E31ACD88 for <nfsv4@ietf.org>; Wed, 8 Apr 2015 18:21:09 -0700 (PDT)
Received: by pdea3 with SMTP id a3so134253506pde.3 for <nfsv4@ietf.org>; Wed, 08 Apr 2015 18:21: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:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=YFmvs3jkPBNggolfrrbaZwrgIVFJRZZLB5NqvCC+TvU=; b=Ks5g0xN2qxKCEzalRmncIG/Xw5hHplHGHRg/38oDGOL6/LCUawboEaX319RZwsWmXJ tE6g8PkZZ2xyk7slgJLWtMz9s4vE2vpMDUdOaSQMgSov3GlwfZVoADmO6Lqi3oTkXG1p PpP7K+Tk3LIM9OvmiXccIYT+buNl0l3K+89fJH9VxN4PJpC/NcUfF2pFhPl+9ao9PIaQ AiRfnV8aDR4dvYVXNmNmFQxkYIUrkqCklg7qvLEUE7qcySaGWvPr0Lak6if2TR9UhpZL CYlInv8VJiPR3HzI4DIjSZkI5NXzGaeR/5IMA9IZPlRLw8qKwYJxO0fP/QYC1fEGXHMX 5zLw==
X-Gm-Message-State: ALoCoQl2qqaIhOUVnlc5gCYs+ItFRBPrNkNkIrVwnvGn2/BH0+kV1Z7WXSPnjIH63IggRQZJWiwc
X-Received: by 10.68.136.66 with SMTP id py2mr50874087pbb.29.1428542468643; Wed, 08 Apr 2015 18:21:08 -0700 (PDT)
Received: from [10.30.8.5] ([50.242.95.105]) by mx.google.com with ESMTPSA id vl9sm11038185pbc.73.2015.04.08.18.21.07 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 Apr 2015 18:21:08 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Tom Haynes <thomas.haynes@primarydata.com>
In-Reply-To: <ED37251F-453E-4379-9E9B-6D8E75BC9E99@gmail.com>
Date: Wed, 08 Apr 2015 18:21:06 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF1E4044-7D42-4715-891F-4D32B8A0F4F9@primarydata.com>
References: <20150407154310.383.14870.idtracker@ietfa.amsl.com> <CAD39596-FC66-492E-9E5B-1C2866632295@primarydata.com> <D94C6AB3-D072-4D76-9A43-0362BDA83B18@primarydata.com> <ED37251F-453E-4379-9E9B-6D8E75BC9E99@gmail.com>
To: RJ Atkinson <rja.lists@gmail.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/nfsv4/MWQZWDso27EvtZBK0nCMnbT8-6I>
Cc: Barry Leiba <barryleiba@computer.org>, The IESG <iesg@ietf.org>, NFSv4 <nfsv4@ietf.org>
Subject: Re: [nfsv4] Barry Leiba's Discuss on draft-ietf-nfsv4-lfs-registry-04: (with DISCUSS and COMMENT)
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: Thu, 09 Apr 2015 01:21:16 -0000

> On Apr 8, 2015, at 6:00 PM, RJ Atkinson <rja.lists@gmail.com> wrote:
> 
>> 
>> A new paragraph to be added after the one in Section 5.2:
>> 
>> In reviewing the published label format specification, the Designated Expert
>> should consider whether or not the specification provides sufficient
>> semantics for the object and subject labels to enforce the MAC model
>> and policy administration when deployed within an organization. Another
>> consideration is if the label format allows the given protocol to
>> process and enforce labels as a policy administration mechanism.
> 
> For the above proposal, I would suggest:
> 
>  s/the given protocol/a correct and complete implementation of the protocol/
> 
> This new paragraph probably also should say something about any
> proposed new label format specification having clearly defined 
> both the syntax & semantics of the proposed new label, not only
> the semantics of the label.  Without clear syntax rules, one could
> have interoperability issues.  (Been there, done that, and didn’t like
> the outcome with the several variants of CIPSO from the original 
> CIPSO I-D.)
> 
> Yours,
> 
> Ran
> 


Hi Ran,

Thanks for your comments, I was hoping you would have some suggestions
based on experience. :-)

Tom

New paragraph:

In reviewing the published label format specification, the Designated Expert
should consider whether or not the specification provides sufficient
semantics for the object and subject labels to enforce the MAC model
and policy administration when deployed within an organization. Another
consideration is if the label format allows a correct and complete
implementation of the protocol to process and enforce labels as a
policy administration mechanism. Finally, to reduce interoperability
issues, the review must determine if the new label format specification
has clearly defined syntax and semantics for the proposed new labels.