[nfsv4] [FedFS] meeting agenda (10/28)

James Lentini <jlentini@netapp.com> Wed, 27 October 2010 20:18 UTC

Return-Path: <jlentini@netapp.com>
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5853A3A6939 for <nfsv4@core3.amsl.com>; Wed, 27 Oct 2010 13:18:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.97
X-Spam-Level:
X-Spam-Status: No, score=-7.97 tagged_above=-999 required=5 tests=[AWL=2.629, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kN1crYYN42mx for <nfsv4@core3.amsl.com>; Wed, 27 Oct 2010 13:18:56 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by core3.amsl.com (Postfix) with ESMTP id 5F3C23A6910 for <nfsv4@ietf.org>; Wed, 27 Oct 2010 13:18:56 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.58,247,1286175600"; d="scan'208";a="473888772"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 27 Oct 2010 13:20:46 -0700
Received: from jlentini-linux.hq.netapp.com (jlentini-linux.hq.netapp.com [10.97.16.21]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id o9RKKkQ6022246 for <nfsv4@ietf.org>; Wed, 27 Oct 2010 13:20:46 -0700 (PDT)
Date: Wed, 27 Oct 2010 16:20:46 -0400
From: James Lentini <jlentini@netapp.com>
X-X-Sender: jlentini@jlentini-linux.nane.netapp.com
To: nfsv4@ietf.org
Message-ID: <alpine.LFD.2.00.1010271616240.32513@jlentini-linux.nane.netapp.com>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Subject: [nfsv4] [FedFS] meeting agenda (10/28)
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 27 Oct 2010 20:18:57 -0000

Tomorrow's proposed agenda is below. Please let me know if you would
like to add additional topics.

    Time: Thursdays 1:30-2:30 PM EST/10:30-11:30 AM PST
 Dial-in: 1-888-765-3653 (us)
          303-218-2659 (international)
      Id: 2354843

Proposed Agenda
---------------

+ IETF Note Well Agreement

  This is a reminder that our discussions are governed by the 
  IETF Note Well Agreement. See:

    http://www.ietf.org/NOTEWELL.html

  We will start each week's meeting with this announcement.

+ NSDB Last Call Wrap-up

  Issues raised during last call on draft-ietf-nfsv4-federated-fs-protocol-09:

  1. Format of the fedfsAnnotation attribute (Section 4.2.1.12)
  http://www.ietf.org/mail-archive/web/nfsv4/current/msg08670.html

  2. Interpretation of zero-length components (Section 4.2.1.14)
  http://www.ietf.org/mail-archive/web/nfsv4/current/msg08632.html

  3. Description of the fedfsUuid attribute (Section 4.2.1.1)
    a. Remove support for "debugging" strings?
    b. Informative text about the UUID algorithm.
       Revise second paragraph of Section 4.2.1.1 as follows?

   To minimize the probability of two UUIDs colliding, a consistent
   procedure for generating UUIDs SHOULD be used throughout a
   federation.  Within a federation, UUIDs SHOULD be generated using the
   procedure described for version 1 of the UUID variant specified in
   [RFC4122]. This is a time-based UUID variant provided by many
   UUID programming libraries (e.g., the OSF DCE uuid_generate_time(1)
   API).

+ Admin Last Call

  Any issues?

+ Discuss draft-adamson-nfsv4-multi-domain-access-03.txt

  Draft here:
  http://tools.ietf.org/html/draft-adamson-nfsv4-multi-domain-access-03

  See questions here:
  http://www.ietf.org/mail-archive/web/nfsv4/current/msg08684.html

+ Meeting schedule