[AFS3-std] Fwd: I-D Action: draft-tkeiser-afs3-volser-tlv-04.txt

[Tom Keiser]

Hi all,

As some of you may know, this document has been on ice (pending
stabilization of afs3-xdr-union, and afs3-capabilities).  Now that
I've finally brought afs3-capabilities up to a point where draft -00
is ready, I am finally releasing afs3-volser-tlv-04.  In addition to
updating the document to have normative references against
afs3-capabilities and afs3-xdr-union, I've additionally incorporated
many small changes since -03.  The change list is included below for
your reference.

Regards,

-Tom


v04 2012-09-11 TEK - add underscores to new volser error code symbolic names
to improve code point readability
- remove Rx epoch-based tag namespace cache invalidation
language, as this is a layering violation
- introduce a monotonic tag namespace version (TSV) ordinal
as a replacement tag namespace cache coherence mechanism
- add TSV OUT parameters to each TLV RPC
- add a TSV IN parameter to the AFSVolSetVolumeTLV RPC for
purposes of asserting desired TSV for a set operation
- define which RPCs are OPTIONAL for-/REQUIRED of- a
compliant implementation
- change xml2rfc anchor names to not include colons since new
versions of the parser appear to consider that a reserved
character...
- change document titles to no longer include ampersands
since new versions of the xml2rfc parser appear to consider that
a special character, even inside of quoted strings
- change TLV language to reference
I-D.keiser-afs3-xdr-union
- change time language to reference
draft-deason-afs3-type-time-03
- add AFSVOL_TLV_FLAG_OBJ_NOT_SUPP to distinguish between
read errors resulting from I/O problems, and read errors
caused by the metadata for a given object (e.g., volume)
not supporting a specific tag
- clarification of the text describing when use of
AFSVOL_TLV_TYPE_OPAQUE may be acceptable
- add a VOLSER_TRANS_INVALID error code so that we stop
using ENOENT on the wire for this error case
- update SetVolumeTLV list of acceptable error codes
- add a section defining each new VOLS error table code
- implement Andrew's suggestion to merge the partid and volid
vectors in GetVolumesTLV to improve encoding efficiency of filters
- fix private assignment ranges, as per Andrew
- refer to RxOSD as "the RxOSD protocol suite"
- as per Andrew, make it clear that allowance of rxnull connections
to AFSVol introspection interfaces is not prescribed in any
protocol specification; it is merely convention
- as per Steven, split AFSVolGetCapabilities out into a new i-d,
and add it as normative reference: draft-keiser-afs3-capabilities
- VOLSER_TAG_DECODE_FAILED: s/could set/could not set/
- convert a bunch of things over to our m4 macro library
- utilize our bibxml library to simplify references
- add Andrew as an editor so he can resurrect the document after
my departure


On Wed, Sep 12, 2012 at 10:57 AM, Jeffrey Altman
<jaltman@your-file-system.com> wrote:
>
>
>
> -------- Original Message --------
> Subject: I-D Action: draft-tkeiser-afs3-volser-tlv-04.txt
> Date: Tue, 11 Sep 2012 15:05:53 -0700
> From: internet-drafts@ietf.org
> Reply-To: internet-drafts@ietf.org
> To: i-d-announce@ietf.org
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>         Title           : AFSVol Tag-Length-Value Remote Procedure Call Extensions
>         Author(s)       : Thomas Keiser
>                           Steven Jenkins
>                           Andrew Deason
>         Filename        : draft-tkeiser-afs3-volser-tlv-04.txt
>         Pages           : 60
>         Date            : 2012-09-11
>
> Abstract:
>    AFS-3 is a distributed file system based upon prototypes developed at
>    Carnegie Mellon University during the 1980s.  AFS-3 heavily leverages
>    Remote Procedure Calls (RPCs) as the foundation for its distributed
>    architecture.  This memo extends the volume management interface to
>    support getting and setting of AFS volume attributes via an
>    extensible Tag-Length-Value (TLV) encoding, which is based upon AFS-3
>    extensible discriminated unions.  TLV-based get and set RPCs are
>    specified, along with a tag enumeration RPC.
>
>    In addition, tags are allocated for existing volume and transaction
>    metadata, and implementation-private tags are allocated for metadata
>    related to the OpenAFS Demand Attach File Server, and the RxOSD
>    protocol suite.
>
> Internet Draft Comments
>
>    Comments regarding this draft are solicited.  Please include the
>    AFS-3 protocol standardization mailing list
>    (afs3-standardization@openafs.org) as a recipient of any comments.
>
> AFS-3 Document State
>
>    This document is in state "draft", as per the document state
>    definitions set forth in [I-D.wilkinson-afs3-standardisation].
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-tkeiser-afs3-volser-tlv
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-tkeiser-afs3-volser-tlv-04
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-tkeiser-afs3-volser-tlv-04
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>