Checking for objections - adding an IANA registry to draft-ietf-nfsv4-rpcsec-gssv3

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Fri, 21 October 2016 19:54 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6503A129967; Fri, 21 Oct 2016 12:54:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 UzTNMjICRyUm; Fri, 21 Oct 2016 12:54:14 -0700 (PDT)
Received: from mail-yb0-x22e.google.com (mail-yb0-x22e.google.com [IPv6:2607:f8b0:4002:c09::22e]) (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 DF157129962; Fri, 21 Oct 2016 12:54:13 -0700 (PDT)
Received: by mail-yb0-x22e.google.com with SMTP id f97so42912915ybi.1; Fri, 21 Oct 2016 12:54:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc; bh=gVaQcwNKg17XZHz5n7LDeTelM/nP8B3C5zoBq/WVz0E=; b=EXxrXytL/hqQ+PSRi8dQXw+6gY7dRFmkB44NKUYKFzPS8qQlHgsGHbfbzqJPh6tvlu ZCOtZhVPTX+NXOJ0grLnRttmcYL5KQhQfgICNIyP/hZ8CQVN9Xu3lQUdycIRNFUb+t2F zO14CsbJkpZ9x6jLVBMxY81tJBG+nNICeAGskTkvLIlXTSrP9tPGuqQnFyhBLnS7NNXu 8fVXsTcysvDRIFxgJ0Azscv4H6aKrbUUnElfCGdmh2frgnnHVIzwG+ZAvl0NlanZzPBy gOt8QdnUutgHYmy9/UIgi31TKIKKUJoYmOWcsWoliCOssURxqPUbhI1WzHupYnHRakh9 9aQQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=gVaQcwNKg17XZHz5n7LDeTelM/nP8B3C5zoBq/WVz0E=; b=UYBtigJ4UNH+3nz2Kt0nFrKzM2rWdltvCQQql1yc1KE34Jz4AehoJcCToycweRsddV UX5HFMs386kiTbDaR8+OnDC53kruzbrSCdmllE4U7HvqncIn7JrQPmULBg2GiOdaJKhu CNZFZwh6UHqXZMQGMtElO7GYBO/nsT80to7ptS+1fY/jX4xHfvRgagpQgj5zvLSrzsXR jplSqGwRUFaI3hmdirbdpld2pE4BetS06+XokaCZRvsobSICrm/U7RWZmKkPij817t0F jpcHrcn9wshVa3CnbvC4YQYubeC25JUaf/g+nFN5vlbhanBfEL3yYdJMt67ILEZ/jvnL AbWg==
X-Gm-Message-State: ABUngveqpZZ4NpKdLM3+fiIlkdL1FSsRUtNLq0evCnjZa7/KuYDyeRZnticjUe5yIG9FkhcKRZDwB31Voa4uGA==
X-Received: by 10.37.29.133 with SMTP id d127mr2819231ybd.58.1477079652953; Fri, 21 Oct 2016 12:54:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.47.215 with HTTP; Fri, 21 Oct 2016 12:54:12 -0700 (PDT)
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 21 Oct 2016 14:54:12 -0500
Message-ID: <CAKKJt-e9pvZRmTUwFBN+YQjWuSvqcm0agESje1JkwFPCjJ_dsg@mail.gmail.com>
Subject: Checking for objections - adding an IANA registry to draft-ietf-nfsv4-rpcsec-gssv3
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a1142775005168f053f65681c
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/w4tr7tMaawIk1ZQEsqlWbVkBRqs>
Cc: "iesg@ietf.org" <iesg@ietf.org>, nfsv4-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Oct 2016 19:54:15 -0000

To the IETF community,

draft-ietf-nfsv4-rpcsec-gssv3 is in the RFC Editor queue, in AUTH48.

During AUTH48 discussions between the authors, they convinced each other,
the document shepherd, and me, that this document needed a new registry for
"RPCSEC_GSS Structured Privilege Names" that were being defined in the
document, and they added one, as Section 5.2.

Here's the diff that shows you the new Section 5.2:

    https://www.rfc-editor.org/authors/rfc7861-lastdiff.html

The working group has seen the change, and the working group chairs believe
the working group has consensus to make the change.

IANA has reviewed the proposed registry instructions and provided comments,
and now has no more questions.

I believe this is the Right Thing To Do.

This is a post-IESG evaluation technical change to
draft-ietf-nfsv4-rpcsec-gssv3, so I've discussed this with the rest of the
IESG, and they agreed that that IETF community should see this change
before publication as an RFC.

I plan to approve this document with the RFC Editor on October 28, one week
from today, unless I hear objections from the community.

Feedback can be sent to iesg@ietf.org, or directly to me.

Spencer