<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.29 (Ruby 2.6.10) -->
<?rfc docmapping="yes"?>
<?rfc comments="yes"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-nfsv4-uncacheable-directories-13" category="std" consensus="true" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.31.0 -->
  <front>
    <title abbrev="Uncacheable Dirent Metadata">Adding an Uncacheable Dirent Metadata Attribute to NFSv4.2</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-nfsv4-uncacheable-directories-13"/>
    <author initials="T." surname="Haynes" fullname="Thomas Haynes">
      <organization>Hammerspace</organization>
      <address>
        <email>loghyr@gmail.com</email>
      </address>
    </author>
    <date/>
    <area>General</area>
    <workgroup>Network File System Version 4</workgroup>
    <keyword>Internet-Draft</keyword>
    <abstract>
      <?line 42?>

<t>Network File System version 4.2 (NFSv4.2) clients may cache the
file attributes returned by READDIR alongside each directory
entry.  Such a cache is not invalidated by the directory's change
attribute, which reflects changes to the directory and its entries
but not writes to the files those entries name, so it can become
stale when another client changes one of those files.  In some
deployments this produces incorrect size and modification times often
enough to be a problem.  This document introduces an
uncacheable dirent metadata attribute for NFSv4.2 that allows a
server to identify a directory for which an honoring client
enumerates by READDIR and reports each entry's attributes as that
READDIR returned them, rather than from a value it held earlier.</t>
    </abstract>
    <note>
      <name>Note to Readers</name>
      <?line 57?>

<t>Note to RFC Editor: please remove this section prior to publication.</t>
      <t>Discussion of this draft takes place
on the NFSv4 working group mailing list (nfsv4@ietf.org),
which is archived at
<eref target="https://mailarchive.ietf.org/arch/search/?email_list=nfsv4"/>. Source
code and issues list for this draft can be found at
<eref target="https://github.com/ietf-wg-nfsv4/uncacheable-directories"/>.</t>
      <t>Working Group information can be found at <eref target="https://github.com/ietf-wg-nfsv4"/>.</t>
    </note>
  </front>
  <middle>
    <?line 70?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>Clients of remote filesystems may cache the file attributes returned
by READDIR alongside each directory entry, to reduce the volume of
follow-on GETATTR traffic for entries the client has already seen.
This caching is inherently best-effort -- writes to the underlying
files can change those attributes at any time, and the directory's
change attribute does not track such writes.  In some deployments
the cost of that staleness is high enough to be a problem; the
conditions are described in <xref target="deployment-motivation"/>.</t>
      <t>In this document, the term directory is used to describe the
context in which directory entries are retrieved.  The uncacheable
dirent metadata attribute applies to dirent metadata -- the file
object attributes, such as size and timestamps, returned alongside each
entry -- and to what an honoring client reports of it.  It does not
prohibit caching of the directory object itself, nor does it affect
caching of file data.</t>
      <t>When this best-effort caching returns stale size and timestamp
information for concurrently modified files, it also undermines the
effectiveness of uncacheable file data semantics
(<xref target="I-D.ietf-nfsv4-uncacheable-files"/>) in the same deployment:
applications can observe inconsistent metadata and data views even
when file data caching is disabled.</t>
      <t>This document introduces the uncacheable dirent metadata attribute
to NFSv4.2 to allow servers to identify the directories for which an
honoring client reports each entry's attributes as the READDIR that
returned the entry supplied them, rather than from a value it held
earlier.
Using the process described in <xref target="RFC8178"/> Section 6, this document
extends NFSv4.2 <xref target="RFC7862"/>; as that section provides, it does not
update <xref target="RFC7862"/>, which remains a valid description of the base
variant of the minor version.  The revisions are built on top of the
external data representation (XDR) <xref target="RFC4506"/> generated from
<xref target="RFC7863"/>.</t>
    </section>
    <section anchor="deployment-motivation">
      <name>Deployment Motivation</name>
      <t>A class of deployment uses NFSv4.2 to serve a shared directory to
many concurrent NFSv4.2 client writers, each writing files within
the directory.  Workloads of this kind are typical of
High-Performance Computing (HPC) environments, where a single
output directory may receive results from hundreds or thousands of
compute nodes simultaneously, and of large-scale data-ingest
pipelines where many producers append to a common landing
directory.  The files within such a directory have their attributes
-- size and time_modify in particular, and more generally the
write-affected class defined in <xref target="sec_definitions"/> --
modified at a high rate by clients other than the one performing
READDIR.</t>
      <t><xref target="RFC8881"/> Section 10.6 permits a client that requested the full set
of attributes to be cached in a READDIR to cache what it returned on
the same basis as attributes obtained by GETATTR:
cached per file, bounded by an upper time boundary, and revalidated
against that file's change attribute.  In a directory receiving writes
from thousands of compute nodes, any nonzero cache lifetime yields stale
size and time_modify for most entries most of the time, and revalidating
each entry individually costs one GETATTR per entry -- the very traffic
that requesting attributes in READDIR exists to avoid.  NFSv4.2 gives a
server no in-band way to tell a client that the file attributes it holds
for the children of a particular directory should be refreshed each time
the directory is enumerated; mount options shorten attribute cache
lifetimes out of band and per client, not per directory.</t>
      <t>Nor can a client work out for itself which directories those are.  The
directory's change attribute is the only per-directory signal it has,
and that attribute does not move when a file the directory names is
written, so it reads the same for a directory receiving writes from a
thousand nodes and for one nobody is touching.  Lacking any basis for
a per-directory choice, a client is left applying one attribute-cache
policy across the whole mount.</t>
      <t>The staleness has correctness consequences, not merely cosmetic ones.
An incremental backup or a directory-tree synchronization pass that
decides what to copy from the size and time_modify reported for each
entry will silently skip a file whose cached metadata predates a
concurrent write, leaving data uncopied.  This attribute lets a server mark the directories where that
outcome is likely, so that an honoring client fetches current metadata
on each enumeration.</t>
      <t>The fattr4_uncacheable_dirent_metadata attribute is the server's
mechanism to identify a directory for which this risk is high
enough that client-side caching is not safe.  When the server sets
the attribute on a directory, an honoring client goes to the server
for each enumeration and does not report an entry's attributes from a
value it held before that READDIR.</t>
    </section>
    <section anchor="sec_definitions">
      <name>Definitions</name>
      <dl>
        <dt>readdir</dt>
        <dd>
          <t>A directory-read request made by an application, however the client's
interface batches entries.  Written in lower case throughout this
document to distinguish it from READDIR, the NFSv4.2 operation
(<xref target="RFC8881"/> Section 18.23).</t>
        </dd>
        <dt>enumeration</dt>
        <dd>
          <t>One pass over a directory: the readdirs of that pass and the READDIRs
the client issues to satisfy them.  A READDIR ordinarily supplies enough
entries for many readdirs, so a requirement scoped to an enumeration
does not imply a READDIR per readdir.</t>
        </dd>
        <dt>dirent</dt>
        <dd>
          <t>A directory entry -- the (name, fileid) pair that names a file or
subdirectory within a directory.  This is what a client maintains for
an entry, whatever a given READDIR response carries on the wire; it is
the pair POSIX exposes as d_name and d_ino.  A dirent itself does not
include the file attributes returned alongside it.</t>
        </dd>
        <dt>dirent metadata</dt>
        <dd>
          <t>The file attributes a READDIR response can return alongside each
dirent that a write to the file can affect, whether or not a particular
response carried them.  The class includes change, size, time_modify,
time_metadata, and space_used.  It is not limited to those: a write by
an unprivileged process clears the set-user-ID and set-group-ID bits of
mode, and archive turns on whether the file has been modified since it
was last archived.  It does not include an attribute a write cannot
affect, such as time_access, which <xref target="RFC8881"/> Section 5.8.2.37 has
updated by READ and READDIR rather than by the operations that modify
content, or fileid and type, which do not change at all.  These
attributes belong to the underlying file object, not to the directory,
and a write to the file does not move the directory's change
attribute.
The term "dirent metadata" in this document is a naming convenience
for this class of attributes.  It names the class rather than the
subset a given response happened to return, and it does not assert that
those attributes inherit the directory's cache-coherence semantics.</t>
        </dd>
        <dt>dirent caching</dt>
        <dd>
          <t>A client-side cache of the dirents themselves -- the (name, fileid)
pairs -- used to avoid repeated READDIR traffic.  Whether such a cache
remains valid is governed by the directory's change attribute: the
directory changes when an entry is created, removed, or renamed, and a
fileid is stable for as long as its entry names the same object.  A
fileid is therefore cached with the name rather than with the file
attributes: writes to a file change its size and timestamps without
touching either the name or the fileid.  This document does not change
what a client may hold in this cache or how it validates it; for a
directory on which the attribute is set, however, each enumeration is
satisfied by a READDIR, so for that directory the cache no longer
avoids that traffic.</t>
        </dd>
        <dt>dirent metadata caching</dt>
        <dd>
          <t>A client-side cache of the dirent metadata returned alongside those
entries, used to avoid repeated GETATTR traffic.  Because those file
attributes are not invalidated by the directory's change attribute
(only by writes to the underlying files), this caching is inherently
best-effort and subject to staleness whenever the underlying files are
modified.  This is the caching whose results the attribute defined in
this document constrains: for a directory on which the attribute is
set, <xref target="sec_dirents"/> limits what an honoring client may report for an
entry, however the client structures the cache the value comes from.</t>
        </dd>
        <dt>uncacheable dirent metadata attribute</dt>
        <dd>
          <t>An NFSv4.2 file attribute that advises clients not to report dirent
metadata, such as size and timestamps, from a value held before the
READDIR that most recently returned the entry it describes.</t>
        </dd>
        <dt>revalidation</dt>
        <dd>
          <t>The procedure of <xref target="RFC8881"/> Section 10.3.1 by which a client
determines whether something it holds in a cache is still current: the
client fetches the change attribute of the object from the server,
compares it with the value it cached, and, if they differ, treats what
it cached as invalid.  A client validates when it fetches from the
server; it revalidates before reusing what it cached.  For a cached
directory the attribute compared is the directory's own
(<xref target="RFC8881"/> Section 10.8.2).</t>
        </dd>
        <dt>honoring client</dt>
        <dd>
          <t>A client that implements this attribute and enforces the
always-refetch behavior it defines for a directory on which the
attribute is set.  The attribute is advisory: a client that does not
implement it, or that declines to enforce it, is non-honoring and may
continue to report dirent metadata it held beforehand.</t>
        </dd>
      </dl>
      <t>This document assumes familiarity with NFSv4.2 operations, attributes,
and error handling as defined in <xref target="RFC8881"/> and <xref target="RFC7862"/>.</t>
    </section>
    <section anchor="requirements-language">
      <name>Requirements Language</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      <?line -18?>

</section>
    <section anchor="caching-of-dirent-metadata">
      <name>Caching of Dirent Metadata</name>
      <t>The uncacheable dirent metadata attribute constrains what an honoring
client may report for the entries of a particular directory.  If both
the client and the server support this attribute, and the attribute is
set on a directory, an honoring client goes to the server for each
enumeration and does not report an entry's attributes from a value it
held before that READDIR.  <xref target="sec_dirents"/> states the requirement
normatively.</t>
      <t>That requirement has two halves.  Each enumeration of such a directory
is satisfied by a READDIR rather than from the results of an earlier
one, and what the client reports for an entry that READDIR returned is
what that READDIR supplied, rather than a value held beforehand.  The
first half is the one that
changes what a client may do today: <xref target="RFC8881"/> Section 10.8.2 lets a
client answer an application readdir from a cached snapshot validated
by the directory's change attribute, with no READDIR on the wire at
all, and that change attribute does not move when a file the directory
names is written.  The second half alone would not close the gap,
since a client could satisfy it by sending a READDIR with a minimal
attr_request and reporting the entries' attributes from what it
already held.</t>
      <t>It adds no constraint on the objects the entries name: an honoring
client may continue to hold the dirents themselves, validated by the
directory's change attribute as it would be for any other directory.
Clients typically hold a single cache of a file object's attributes,
populated by whichever operation last returned them; the requirement is
on what the client reports, not on how it structures that cache.</t>
      <t>A server sets it on the directories where it knows the staleness of
cached READDIR attributes is particularly likely and particularly
damaging.  It is a <bcp14>RECOMMENDED</bcp14> attribute for NFSv4.2, in the
attribute-category sense of <xref target="RFC8881"/> Section 5.2 and <xref target="RFC7862"/>
Section 12 rather than the BCP 14 sense; a server is not required to
support it.</t>
      <t>Because the attribute governs what an honoring client reports for the
entries of one directory, rather than the objects those entries name,
it makes no claim about those objects.  A file reached
through a directory on which the attribute is not set is unaffected,
including where the same file is linked into both a directory on which
it is set and one on which it is not.</t>
      <t>This document specifies the required observable behavior rather
than mandating a particular internal implementation strategy.
Clients <bcp14>MAY</bcp14> employ more sophisticated mechanisms, such as
time-limited caches that revalidate against the server on each
READDIR, provided that the externally visible behavior satisfies
<xref target="sec_dirents"/>.</t>
      <t>A client can determine whether the uncacheable dirent metadata attribute
is supported for a given directory by examining the supported_attrs
attribute for that directory's filesystem or by probing support using
the procedures described in <xref target="RFC8178"/>.</t>
      <t>A change to the attribute while a directory is in use may not be
reflected in client behavior immediately.  A client that has cached the
directory's attributes <bcp14>MAY</bcp14> continue to behave as it did before the
change and is not required to act on a value it has not yet observed.
Two ordinary mechanisms bound that delay: the client's cached
attributes for the directory expire under the upper time boundary
described in <xref target="RFC8881"/> Section 10.6, and a client revalidating a
cached directory inspects the directory's change attribute
(<xref target="RFC8881"/> Section 10.8.2), and that attribute changes whenever the
object it describes is modified (<xref target="RFC8881"/> Section 5.8.1.4),
including by a SETATTR of this one.  Clients are expected to observe the change through those
mechanisms and to apply the rule in <xref target="sec_dirents"/> to subsequent
enumerations.</t>
      <t>The uncacheable dirent metadata attribute governs what an honoring
client may report for a directory's entries.  It does NOT govern:</t>
      <ul spacing="normal">
        <li>
          <t>How long a value remains reportable between enumerations.  Attributes
a client obtains for an individual entry at other times, by a direct
GETATTR following a LOOKUP for example, remain governed between
enumerations by the attribute-cache mechanisms already defined by
NFSv4.2 and are subject to the same staleness from concurrent writes.
The rule in <xref target="sec_dirents"/> applies at each enumeration and is
indifferent to which operation last supplied a value.</t>
        </li>
        <li>
          <t>The directory's own attribute cache.  The directory object's own
attributes (mode, owner, etc.) can be cached normally and
revalidated via the directory's change attribute as usual.</t>
        </li>
        <li>
          <t>Operations that do not return file attributes in their response
(for example, LOOKUP without a following GETATTR, ACCESS).  These
are unaffected.</t>
        </li>
      </ul>
      <t>The uncacheable dirent metadata attribute addresses a different
aspect of client-side caching than fattr4_uncacheable_file_data
(<xref target="I-D.ietf-nfsv4-uncacheable-files"/>).  The file data attribute
governs caching of file contents, while the dirent metadata
attribute governs what a client reports for the entries of a
directory it enumerates.
The attributes are independent and may be used separately.</t>
      <t>This attribute follows the same pattern as
fattr4_uncacheable_file_data (<xref target="I-D.ietf-nfsv4-uncacheable-files"/>)
applied at the file-data layer.  In both cases:</t>
      <ul spacing="normal">
        <li>
          <t>The underlying NFSv4.2 protocol permits client-side caching that
can become stale.</t>
        </li>
        <li>
          <t>Client caching of the relevant data is widely implemented in
practice and reduces network traffic for stable objects.</t>
        </li>
        <li>
          <t>For specific objects where the deployment knows the caching will
produce incorrect results, the server requires a mechanism to
instruct an honoring client not to rely on it for those specific
objects.</t>
        </li>
        <li>
          <t>The attribute does not redefine the legality of caching in the
general case.  It is a per-object server-side signal that the
caching is known to be unsuitable for that object.</t>
        </li>
      </ul>
      <t>The attribute does NOT make dirent metadata caching reliable for
directories where it is not set.  Clients <bcp14>MUST NOT</bcp14> interpret the
absence of fattr4_uncacheable_dirent_metadata, or its value being
false, as a guarantee that cached READDIR attributes are
authoritative.  As stated in <xref target="RFC8881"/> Section 10.6, all
client-cached attributes are subject to staleness; the attribute
defined in this document only identifies directories for which
staleness is particularly likely and particularly damaging.  The base
specification separates the two concerns this attribute is often accused
of conflating: <xref target="RFC8881"/> Section 10.8.2 governs caching of the
directory entries themselves, while Section 10.6 governs caching of the
file attributes that arrive alongside them.  This attribute leaves what
a client may hold under either unchanged; it requires a READDIR for each
enumeration and constrains what may be reported for an entry, as
<xref target="sec_dirents"/> states.</t>
      <t>This attribute does not define behavior for positive or negative
name caching, nor for LOOKUP results other than the file attributes
it constrains an honoring client from reporting for an entry.</t>
      <t>A directory delegation (<xref target="RFC8881"/> Section 10.9) lets a client cache a
directory's entries and the directory's own attributes until the server
recalls the delegation.  It is not recalled when the attributes of an
entry within the directory change (<xref target="RFC8881"/> Sections 10.9.2 and
10.9.4), so a directory delegation does not, by itself, keep the file
attributes returned by READDIR fresh.  NOTIFY4_CHANGE_CHILD_ATTRS,
requested through GET_DIR_DELEGATION, can deliver changed child
attributes to a delegated client, but it is not a substitute for this
attribute in the deployments of <xref target="deployment-motivation"/>:
GET_DIR_DELEGATION is <bcp14>OPTIONAL</bcp14> and is not implemented by the clients and
servers those deployments use; notification cost scales with the number
of delegated clients times the number of changes, which a directory
written by thousands of clients makes prohibitive (and <xref target="RFC8881"/>
Section 10.9.4 permits a server that finds a directory is causing too
many notifications to decline to delegate it); and the
dirent_notif_delay attribute lets a server bound or refuse
child-attribute notification, so a client cannot rely on notification
for freshness.</t>
      <section anchor="sec_dirents">
        <name>Uncacheable Dirent Metadata</name>
        <t>The fattr4_uncacheable_dirent_metadata attribute is a read-write boolean
attribute that applies to directory objects.
Authorization to query or modify this attribute is governed by
existing NFSv4.2 authorization mechanisms.  <xref target="tab_attr"/> summarizes
the attribute using the columns of <xref target="RFC7862"/> Section 12.1, where
"R W" indicates that GETATTR may retrieve the attribute and SETATTR
may set it.</t>
        <table anchor="tab_attr">
          <name>New RECOMMENDED Attribute</name>
          <thead>
            <tr>
              <th align="left">Name</th>
              <th align="left">Id</th>
              <th align="left">Data Type</th>
              <th align="left">Acc</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">uncacheable_dirent_metadata</td>
              <td align="left">88</td>
              <td align="left">bool</td>
              <td align="left">R W</td>
            </tr>
          </tbody>
        </table>
        <t>The attribute applies only to directory objects.  A server that
receives a GETATTR requesting fattr4_uncacheable_dirent_metadata on an
object that is not a directory <bcp14>MUST</bcp14> return FALSE: support for an
attribute is advertised per file system (<xref target="RFC8881"/> Section 5.8.1.1),
so a server that supports this attribute supports it for every object
in that file system and owes a value for each (<xref target="RFC8881"/> Section
18.7.3).  As with rawdev (<xref target="RFC8881"/> Section 5.8.2.31), the value is
not useful for an object the attribute does not describe.  A server that receives a SETATTR requesting
fattr4_uncacheable_dirent_metadata on an object that is not a directory
<bcp14>MUST</bcp14> return NFS4ERR_WRONG_TYPE (<xref target="RFC8881"/> Section 15.1.2.9).</t>
        <t>Whether a SETATTR of the attribute is permitted at all is subject to
server policy: the server decides, on grounds such as administrative
configuration, export policy, or access control.  A request that is
not permitted <bcp14>MUST</bcp14> be rejected with NFS4ERR_ACCESS (<xref target="RFC8881"/> Section
15.1.6.1) or, where the refusal is because the requester is neither the
owner nor a privileged user, NFS4ERR_PERM (<xref target="RFC8881"/> Section
15.1.6.2).  A server that supports the attribute <bcp14>MUST NOT</bcp14> refuse such a
request with NFS4ERR_INVAL: <xref target="RFC8178"/> Section 4.4.3 reserves that
response to a SETATTR of the attribute for a server with no knowledge
of it, and a client probing for support would take the refusal as
ignorance.</t>
        <t>This document does not require a server to implement any particular
policy, nor any particular means of configuring one.  A server that
always permits, or always refuses, requests to set or clear the
attribute conforms to this document; what the protocol requires is
only the error returned when a request is refused.</t>
        <t>A client may also request the attribute in the createattrs of a CREATE
whose type is NF4DIR (<xref target="RFC8881"/> Section 18.4), so that a directory is
marked when it is created rather than by a SETATTR afterwards.  The
same server policy governs that request, and a server that does not
permit it returns the same errors.</t>
        <t>This attribute is set per directory.  This document does not define
propagation of the attribute to subdirectories created within a
directory on which it is set; any such inheritance is a matter of
local server policy.</t>
        <t>If a directory object has the uncacheable dirent metadata attribute
set, an honoring client <bcp14>MUST NOT</bcp14> satisfy a readdir of that directory
from READDIR results obtained during a different enumeration, and <bcp14>MUST
NOT</bcp14> report, for an entry, a value of a dirent metadata attribute that
it received before the READDIR that most recently returned that entry,
whatever operation supplied that value.</t>
        <t>A client holding an OPEN_DELEGATE_WRITE delegation on a file the
directory names may hold a size or change value more current than the
server's, which the server obtains from it by CB_GETATTR (<xref target="RFC8881"/>
Section 10.4.3).  The requirement above is directed at values older
than what the server would return, and does not require such a client
to replace its own values with older ones.</t>
        <t>An honoring client therefore either names the attributes it will report
in that READDIR's attr_request, or obtains them afterwards; a value it
held beforehand is not usable for that entry.  An honoring client
<bcp14>SHOULD</bcp14> name them in attr_request.  For a listing or a
directory-tree synchronization pass, which reads the size and
time_modify of every entry, obtaining them afterwards instead costs
one GETATTR per entry, which is the traffic the deployments of
<xref target="deployment-motivation"/> use this attribute to avoid.  A client that
knows no such read will follow may still obtain them afterwards, at
that cost where one does.</t>
        <t>Entries carried by the READDIRs of a single enumeration <bcp14>MAY</bcp14> be
retained until that enumeration completes, and their metadata <bcp14>MAY</bcp14> be
retained after it: what bounds the reporting of that metadata is the
next enumeration, under the rule above, and the attribute-cache
mechanisms of <xref target="RFC8881"/> Section 10.6 until then.  <xref target="RFC8881"/> Section
10.8.2 requires such a cache to be a consistent snapshot of directory
contents, validated by the directory's change attribute; because that
attribute does not move when a file the directory names is written, it
provides no corresponding guarantee for the entries' file attributes,
which are as of the READDIR that carried them.</t>
        <t>The uncacheable dirent metadata attribute does not modify the
semantics of the NFSv4.2 change attribute, and does not make any
change attribute the trigger for the rule above: the event that
renders a held value unreportable for an entry is the enumeration that
returns that entry, whatever any change attribute does.  Clients <bcp14>MUST</bcp14>
continue to use the change attribute to detect directory modifications
and to determine when directory contents may have changed, even for a
directory on which this attribute is set.  Constraining what an
honoring client may report for an entry does not remove the need for
change-based validation.</t>
        <t>This attribute is advisory, so servers <bcp14>SHOULD NOT</bcp14> rely on it for
correctness: a client that does not implement it, or that declines to
enforce it, may continue to report dirent metadata from a value it
held before the READDIR that most recently returned the entry.  A
server cannot distinguish those clients from honoring ones.  Observing
a GETATTR or a SETATTR of the attribute shows only that a client knows
the attribute exists, not that it enforces the rule of
<xref target="sec_dirents"/>, so such a request is not a basis for assuming it
does.</t>
        <t>A directory delegation would let a client serve dirent
metadata from its cache without refetching, which is incompatible with
the always-refetch rule this attribute defines.  Accordingly, if a
directory has the uncacheable dirent metadata attribute set and an
outstanding directory delegation, the server <bcp14>MUST</bcp14> recall the
delegation, after which the client is subject to <xref target="sec_dirents"/> on
each subsequent enumeration.  A server <bcp14>MUST NOT</bcp14> grant a new directory
delegation on a directory while the uncacheable dirent metadata
attribute is set on that directory.</t>
      </section>
      <section anchor="sec_pnfs">
        <name>Parallel NFS</name>
        <t>The uncacheable dirent metadata attribute is an attribute of the
directory, and a pNFS client (<xref target="RFC8881"/> Section 12) obtains it, and
the entries it governs, from the metadata server.  A storage device
serves data, not attributes: the file layout, for example, admits only
READ, WRITE, COMMIT and housekeeping operations on a data server
(<xref target="RFC8881"/> Section 13.6), and a layout whose storage protocol is not
NFS has no GETATTR or READDIR to send.  Whether the files an entry names are read
or written through a layout therefore does not change what
<xref target="sec_dirents"/> requires of an honoring client.</t>
        <t>What those values reflect is a separate question, and one the layout
type answers.  Where a client writes to a storage device and the
metadata server learns the resulting size and time_modify only on
LAYOUTCOMMIT (<xref target="RFC8881"/> Section 12.5.4), a READDIR issued before
that LAYOUTCOMMIT returns the earlier values, and an honoring client
reports them.  The attribute removes the staleness a client's own
cache introduces; it does not make the metadata server report what it
has not yet been told.</t>
      </section>
    </section>
    <section anchor="example-directory-enumeration-with-and-without-dirent-metadata-caching">
      <name>Example: Directory Enumeration With and Without Dirent Metadata Caching</name>
      <t>This example illustrates the difference in client-visible behavior when
dirent metadata caching is enabled versus when the uncacheable
dirent metadata attribute is set on a directory.  In both scenarios
each readdir("/dir") is a separate enumeration -- the application opens
the directory, reads it to end-of-file and closes it, and opens it
again for the second.  The set of entries does not change between the
two; an attribute value of one entry is updated at the server between
them.  The difference is whether the stat after the second readdir
observes the updated value.</t>
      <section anchor="classic-directory-enumeration-dirent-metadata-cached">
        <name>Classic Directory Enumeration (Dirent Metadata Cached)</name>
        <t>In this scenario, the client caches dirent metadata obtained from the
server and reuses it after a second readdir.</t>
        <figure anchor="fig-cached-dirents">
          <name>Dirent Metadata Cached</name>
          <artwork><![CDATA[
Application             NFSv4.2 Client        NFSv4.2 Server
-----------             --------------        --------------
readdir("/dir")
   |
   |                     READDIR, size and
   |                     time_modify requested
   |-------------------->------------------------>
   |                     entries:
   |                       a (size=100)
   |                       b (size=200)
   |<--------------------<------------------------
   |<-- names a, b
                        (attributes retained per
                         entry, bounded by the
                         attribute cache lifetime)

                                        (concurrent writer extends
                                         a from size=100 to
                                         size=500)

readdir("/dir")
   |                     (served from the cached
   |                      READDIR result; no
   |                      network traffic)
   |<-- names a, b

stat("/dir/a")
   |                     (served from the retained
   |                      READDIR attributes)
   |<-- size=100
]]></artwork>
        </figure>
        <t>In this case, <xref target="fig-cached-dirents"/> shows a second readdir satisfied
from the cached result of the first.  No READDIR reaches the server, so
nothing refreshes what the client holds for entry a, and the stat that
follows reports the size as it was at the time of the first READDIR --
not the update the server took between the two.  This behavior
maximizes performance and is what <xref target="RFC8881"/> Sections 10.6 and 10.8.2
permit, but for the duration of the cache lifetime it can result in
applications observing dirent attribute values that do not reflect the
current state of the files the entries name.</t>
      </section>
      <section anchor="directory-enumeration-with-uncacheable-dirent-metadata">
        <name>Directory Enumeration With Uncacheable Dirent Metadata</name>
        <t>In this scenario, the directory has the uncacheable dirent metadata
attribute set.  The client retrieves dirent metadata from
the server on each READDIR.</t>
        <figure anchor="fig-uncached-dirents">
          <name>Dirent Metadata Not Cached</name>
          <artwork><![CDATA[
Application             NFSv4.2 Client        NFSv4.2 Server
-----------             --------------        --------------
readdir("/dir")
   |
   |                     READDIR, size and
   |                     time_modify requested
   |-------------------->------------------------>
   |                     entries:
   |                       a (size=100)
   |                       b (size=200)
   |<--------------------<------------------------
   |<-- names a, b

                                        (concurrent writer extends
                                         a from size=100 to
                                         size=500)

readdir("/dir")
   |
   |                     READDIR, size and
   |                     time_modify requested
   |                     (cached result not used)
   |-------------------->------------------------>
   |                     entries:
   |                       a (size=500)
   |                       b (size=200)
   |<--------------------<------------------------
   |<-- names a, b

stat("/dir/a")
   |<-- size=500
]]></artwork>
        </figure>
        <t>In this case, <xref target="fig-uncached-dirents"/> shows the second readdir going
to the server, and the stat that follows reporting what that READDIR
returned.  The set of entries is unchanged between the two calls; only
the attribute value differs.  The client may still cache other
information, provided it reports no value for these entries that it
received before the READDIR that most recently returned them.</t>
      </section>
      <section anchor="discussion">
        <name>Discussion</name>
        <t>This example demonstrates that the uncacheable dirent metadata
attribute does not mandate a particular client implementation, but
it does require the always-refetch behavior specified in
<xref target="sec_dirents"/>.  The attribute ensures that an honoring client's report
of an entry's attributes reflects the server's state as of the
enumeration that returned it, in deployments where staleness of
READDIR-returned attributes is known to be a recurring problem.</t>
      </section>
    </section>
    <section anchor="implementation-status">
      <name>Implementation Status</name>
      <t>Note to RFC Editor: please remove this section prior to publication.</t>
      <t>There is a prototype Hammerspace server which implements the
uncacheable dirent metadata attribute and a prototype Linux client
which treats the attribute as an indication to satisfy each
enumeration of such a directory with a READDIR that requests the
entries' attributes, rather than from its readdir cache.</t>
      <t>In the prototype, directories whose contents change at the server
at a rate exceeding typical client cache lifetimes are marked with
the fattr4_uncacheable_dirent_metadata attribute.</t>
      <t>The Linux client decodes the attribute in fs/nfs/nfs4xdr.c into a
per-inode flag (nfsi-&gt;uncacheable_dirent_metadata, declared in
include/linux/nfs_fs.h).  The readdir path in fs/nfs/dir.c consults
this flag to skip the readdir cache and refetch from the
server on each readdir call that is not already at end of directory.
It also forces the client onto its attribute-returning READDIR path for
such a directory, where the server has been found capable of it: a
READDIR that returns only names would refresh the
entries but leave their attributes to the client's attribute caches, and
the
cache-bypassing path above never accrues the cache usage that would
otherwise select that path for the continuation READDIRs of a large
directory.  Clients may employ more sophisticated
mechanisms, such as time-limited caches that revalidate against the
server on each READDIR, provided that the externally observable
behavior satisfies <xref target="sec_dirents"/>.</t>
      <t>The Linux client implementation encodes this attribute as a flag
distinct from the companion file-data attribute defined in
<xref target="I-D.ietf-nfsv4-uncacheable-files"/>; the two attributes are separated
as the two documents specify.  That implementation is posted to
linux-nfs (patches 4-6 of
<eref target="https://lore.kernel.org/linux-nfs/cover.1785140181.git.snitzer@kernel.org/">https://lore.kernel.org/linux-nfs/cover.1785140181.git.snitzer@kernel.org/</eref>).</t>
      <t>Experience with the prototype indicates that the attribute enables
servers to identify directories whose contents change faster than
typical NFSv4.2 client cache lifetimes can track, while remaining
compatible with existing NFSv4.2 semantics.</t>
    </section>
    <section anchor="xdr-for-the-uncacheable-dirent-metadata-attribute">
      <name>XDR for the Uncacheable Dirent Metadata Attribute</name>
      <sourcecode type="xdr"><![CDATA[
///
/// typedef bool            fattr4_uncacheable_dirent_metadata;
///
/// const FATTR4_UNCACHEABLE_DIRENT_METADATA   = 88;
///
]]></sourcecode>
    </section>
    <section anchor="extraction-of-xdr">
      <name>Extraction of XDR</name>
      <t>This document contains the external data representation (XDR)
<xref target="RFC4506"/> description of the uncacheable dirent metadata attribute.  The XDR
description is presented in a manner that facilitates easy extraction
into a ready-to-compile format. To extract the machine-readable XDR
description, use the following shell script, which relies on the sh, grep,
and sed utilities as specified by <xref target="POSIX"/>:</t>
      <sourcecode type="shell"><![CDATA[
#!/bin/sh
grep '^ *///' $* | sed 's?^ */// ??' | sed 's?^ *///$??'
]]></sourcecode>
      <t>For example, if the script is named 'extract.sh' and this document is
named 'spec.txt', execute the following command:</t>
      <sourcecode type="shell"><![CDATA[
sh extract.sh < spec.txt > uncacheable_prot.x
]]></sourcecode>
      <t>This script removes leading blank spaces and the sentinel sequence '///'
from each line. XDR descriptions with the sentinel sequence are embedded
throughout the document.</t>
      <t>Note that the XDR code contained in this document depends on types from
the NFSv4.2 nfs4_prot.x file (generated from <xref target="RFC7863"/>).  This includes
both nfs types that end with a 4, such as offset4, length4, etc., as
well as more generic types such as uint32_t and uint64_t.</t>
      <t>While the XDR can be appended to that from <xref target="RFC7863"/>, the code snippets
should be placed in their appropriate sections within the existing XDR.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>This attribute is not a security mechanism.  It addresses correctness
of client-side caching when client-cached dirent metadata
can become stale relative to the current state of the directory at
the server.  It does not change NFSv4.2 authentication or authorization
semantics, and it does not impose access controls on the entries it
describes.</t>
      <t>Authorization to set or modify the fattr4_uncacheable_dirent_metadata
attribute is governed by existing NFSv4.2 authorization mechanisms.
<xref target="sec_dirents"/> states what a server returns for a request its policy
refuses.  This document does not define a new authorization model.</t>
      <t>Because the attribute is visible to and affects the caching behavior
of all honoring clients, servers should consider the implications of
allowing unprivileged users to set or clear it.  Setting the attribute
on a directory forces honoring clients to abandon READDIR caching and
refetch dirent metadata on every enumeration, which can
increase load on the server and on other clients.</t>
      <t>This attribute does not change the semantics of sec_label or the
enforcement of MAC security policies.  A client's obligations under
Labeled NFS (see <xref target="RFC7204"/> for background, and <xref target="RFC7862"/> Section 9
for the NFSv4.2 mechanism) are the same whether dirent metadata is
refetched or served from a cache.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions.</t>
      <t>NFSv4.2 attribute numbers are assigned by working group coordination
rather than through an IANA registry.  This document uses attribute
number 88, chosen alongside attribute number 87 in
<xref target="I-D.ietf-nfsv4-uncacheable-files"/>.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC4506">
          <front>
            <title>XDR: External Data Representation Standard</title>
            <author fullname="M. Eisler" initials="M." role="editor" surname="Eisler"/>
            <date month="May" year="2006"/>
            <abstract>
              <t>This document describes the External Data Representation Standard (XDR) protocol as it is currently deployed and accepted. This document obsoletes RFC 1832. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="67"/>
          <seriesInfo name="RFC" value="4506"/>
          <seriesInfo name="DOI" value="10.17487/RFC4506"/>
        </reference>
        <reference anchor="RFC7862">
          <front>
            <title>Network File System (NFS) Version 4 Minor Version 2 Protocol</title>
            <author fullname="T. Haynes" initials="T." surname="Haynes"/>
            <date month="November" year="2016"/>
            <abstract>
              <t>This document describes NFS version 4 minor version 2; it describes the protocol extensions made from NFS version 4 minor version 1. Major extensions introduced in NFS version 4 minor version 2 include the following: Server-Side Copy, Application Input/Output (I/O) Advise, Space Reservations, Sparse Files, Application Data Blocks, and Labeled NFS.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7862"/>
          <seriesInfo name="DOI" value="10.17487/RFC7862"/>
        </reference>
        <reference anchor="RFC7863">
          <front>
            <title>Network File System (NFS) Version 4 Minor Version 2 External Data Representation Standard (XDR) Description</title>
            <author fullname="T. Haynes" initials="T." surname="Haynes"/>
            <date month="November" year="2016"/>
            <abstract>
              <t>This document provides the External Data Representation (XDR) description for NFS version 4 minor version 2.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7863"/>
          <seriesInfo name="DOI" value="10.17487/RFC7863"/>
        </reference>
        <reference anchor="RFC8178">
          <front>
            <title>Rules for NFSv4 Extensions and Minor Versions</title>
            <author fullname="D. Noveck" initials="D." surname="Noveck"/>
            <date month="July" year="2017"/>
            <abstract>
              <t>This document describes the rules relating to the extension of the NFSv4 family of protocols. It covers the creation of minor versions, the addition of optional features to existing minor versions, and the correction of flaws in features already published as Proposed Standards. The rules relating to the construction of minor versions and the interaction of minor version implementations that appear in this document supersede the minor versioning rules in RFC 5661 and other RFCs defining minor versions.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8178"/>
          <seriesInfo name="DOI" value="10.17487/RFC8178"/>
        </reference>
        <reference anchor="RFC8881">
          <front>
            <title>Network File System (NFS) Version 4 Minor Version 1 Protocol</title>
            <author fullname="D. Noveck" initials="D." role="editor" surname="Noveck"/>
            <author fullname="C. Lever" initials="C." surname="Lever"/>
            <date month="August" year="2020"/>
            <abstract>
              <t>This document describes the Network File System (NFS) version 4 minor version 1, including features retained from the base protocol (NFS version 4 minor version 0, which is specified in RFC 7530) and protocol extensions made subsequently. The later minor version has no dependencies on NFS version 4 minor version 0, and is considered a separate protocol.</t>
              <t>This document obsoletes RFC 5661. It substantially revises the treatment of features relating to multi-server namespace, superseding the description of those features appearing in RFC 5661.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8881"/>
          <seriesInfo name="DOI" value="10.17487/RFC8881"/>
        </reference>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="POSIX" target="https://standards.ieee.org/ieee/1003.1/7700/">
          <front>
            <title>IEEE Standard for Information Technology--Portable Operating System Interface (POSIX) Base Specifications, Issue 8</title>
            <author>
              <organization>IEEE</organization>
            </author>
            <author>
              <organization>The Open Group</organization>
            </author>
            <date year="2024"/>
          </front>
          <seriesInfo name="IEEE" value="Std 1003.1-2024"/>
        </reference>
        <reference anchor="I-D.ietf-nfsv4-uncacheable-files">
          <front>
            <title>Adding an Uncacheable File Data Attribute to NFSv4.2</title>
            <author fullname="Thomas Haynes" initials="T." surname="Haynes">
              <organization>Hammerspace</organization>
            </author>
            <date day="17" month="September" year="2026"/>
            <abstract>
              <t>   Network File System version 4.2 (NFSv4.2) clients commonly perform
   client-side caching of file data in order to improve performance.  On
   some systems, applications may influence client data caching
   behavior, but there is no standardized mechanism for a server or
   administrator to indicate that particular file data should not be
   cached by clients for reasons of performance or correctness.  This
   document introduces a new file data caching attribute for NFSv4.2.
   Files marked with this attribute are intended to be accessed with
   client-side caching of file data suppressed, in order to support
   workloads that require predictable data visibility.  This document
   extends NFSv4.2.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-nfsv4-uncacheable-files-16"/>
        </reference>
        <reference anchor="RFC7204">
          <front>
            <title>Requirements for Labeled NFS</title>
            <author fullname="T. Haynes" initials="T." surname="Haynes"/>
            <date month="April" year="2014"/>
            <abstract>
              <t>This memo outlines high-level requirements for the integration of flexible Mandatory Access Control (MAC) functionality into the Network File System (NFS) version 4.2 (NFSv4.2). It describes the level of protections that should be provided over protocol components and the basic structure of the proposed system. The intent here is not to present the protocol changes but to describe the environment in which they reside.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7204"/>
          <seriesInfo name="DOI" value="10.17487/RFC7204"/>
        </reference>
      </references>
    </references>
    <?line 823?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>Trond Myklebust, Mike Snitzer, Jon Flynn, Keith Mannthey, and Thomas
Haynes all worked on the prototype at Hammerspace.</t>
      <t>Rick Macklem, Chuck Lever, Dave Noveck, Sorin Faibish, Christoph
Hellwig, Jeff Layton, and Jamie Koehl reviewed the document.</t>
      <t>Chris Inacio, Brian Pawlowski, Chuck Lever, Zahed Sarker, and
Gorry Fairhurst helped guide this process.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAPiI/GoAA+196XLbSJrg/3yKHHsiLHWQlGWrXGqpjlZJclnTvtZSTXVt
R68CJJJkjkCAiwQls13uZ9ln2Sfb78oDICjLHbsxERPrCNsUBeTx5XdfORwO
VWObwhzpkzy35Uxnpf6lnGSTucnGhdFntjZlo9+YJsuzJtMnTVPb8aoxuqn0
25eXtwejZyobj2tze3TfiyqvJmW2gHnyOps2Q2ua6bCcutuD4Sq+NczhrUlT
1da44f5zNckaM6vq9ZF2Ta5gHHj/09nJ1flnNalKZ0q3cke6qVdG2WVNn1zz
7OnTPz6FRdUmO9I/m9LUWaHuqvpmVler5ZF+axr8Sb+0sMzLtWvMQv+7qZ2t
Sn2gbswafpsf6YuyMXVpmuEZLlgp12Rlfp0VVQmLWBunlvZI/7WpJgPtqrqp
zdTBp/WCP8B2F9lyCRAd6Em1WAAs3N+UylbNvKqPlB4qDX9sCcu/GulX2bqE
EfErBtLVvFpkLv2+qmdZaf+eNbDMI/gFDFm7ZTYx9FuzyGxxpItqNl/Xf5rh
TyOYVqmyqhfwzq2BOfWHl6cH3zx9IR+/PXzxLH58Lh8P97899B8PD/ePlLLl
NB3k/bvLi78c0ayCOY8uzs/P9SXCJ6tzDU8D8OQdgOmVmczLCpa2Hg7fA6QI
Pd4t4VgaRDg5AQL3FPajd2iGXf1T5uB8lmZip3ZCQwFcL5xbGX34iOYP0IQ/
Q4QQnBosJf35ak5zlfpnPHz6jTOIXrgrflPTS0ewgVzvP336fLQ/fPb02QH9
jlEu/Nhk9cw0R3reNEt3tLfnZM9uZI0xI5hxDz/s8TB733779OkevHgxPBtt
QfgpIKHzp/Ds6cGRGg6HOhu7ps4mgHV9yHrrkXX0TO8IDe7qSWERyfQiW2sa
Xzdzo3B8nXmidbo2zQqwOtfjtf5wfnJ2dvFBI07PnM2NNvCe9jS4VjBevR5p
fbmCrzMZ1TpdVg2g7m1WWIQPjQVzxRefOD2ZZ+XMqDDzQN/NLYwC1FHAQ/4B
h2yk9S4woFxbeAAnh3NS8DZNeFfbJj5PcINPFeCIPEmkg8QIr8NaSz02QAIG
CRdgcDcHJMhgoLmpBVZhDUDSuprKaDQybPqihKHg9dwsi2pNBAxPwO6XdZWv
JvCaLSdVjcvWzv7d0MIXVR6wFchjgYNPG1MCKKvVbI6rH8OTOAac/gKmucIh
gVuscAYYsvGjZ6VKEIUABA8sPCMOkCV6EyyABWYNnGdR3cEACjAdcAUnhcMt
GzsF6CaQxhf5VABY8wpYBdIjwwYWDCsCEoWVpKgCe6zNEqjYMbIQisB5JyiW
OVqG8u8ElAPQLwYaxsQjgEdKPa2rBSwJMAmIGk5tboocxq1hCfVIESnAiZnr
t/hPU11/MFkOyA9kUbEEAqrR57mF7RzpZWGQY9RmUd0aPioHO8WTWNa2Ijgs
V+NCjgfGP7NusnJES3T8eBLI7IHOb2AjywLZKx4kIBxBWCMtIpBIlGhks/hT
YV2jd4i4/4R0joxgd6AYtjBoVk/mwD1zgJL66992PPfA1+VXI//aHn6x5wz9
9yOx9Wsc/nsafXekL6tVDauaVDljnEWG6HgJeKDJLpgG4NtV2Z16Zpv5aowi
Yo8Y092MedPeFmG8C9D6VfZOnFTbhMN3JtIPmGhXjndh87wwSj1GAUCojyMq
dSrcDM4FD7QRuiQG2OFxehuPUw/gcYzAA8SN2iDh0Yi3VQHYD5OraYXENIRN
/nx+dXJ19QF0jGwKJE7A9pwH3xGeMgf0zwrQPfI1oJ8BNCMKx9Ui8CyyDcB/
eLRYA9BcMzRTGKrRAIw2iwNgmrpYw1uKuR2CmVmWsKqU6IDsyzWxnAHhRYch
K3kxso28MszJUdLcaIc8nhcQmZ9OmJ+iTVaAZkQrMCExVtBPHO5qbmfIDfq4
3DFJIlDYgFBRigM94MhuAisBorCl/vQpTjSE07a3hFifPwOWXJSC08IjB7Q1
UBYWySnC71cOWUwVBvaTNuYj8lXhdO2Dx7PDxQDGwGegUGLICPpABWo74wX9
rrB8Xt2H4DA9Zqpq/B8oI+JhDRjYgChBbpCoaLLFEn4Z+GUbZ1ka48j0QgUb
okPvcu7An+GYbINn2YSzVnAiczsm+cj4SGeZil9ZLUhgU0wH8FLNb8M7gPfw
K5W8SpSHG0b2gAKWTirFav8wb8oxzvTsW6X8BEkLTm6yqoVOWKwCSIgQBrSY
AgQ9kcjClkyCytACgZ0SUsL6UgEa1gpkuchAGk6c2vn06Uu62efPu4g9CCSX
tSjiSBECiGpK1FmNSeSSZlA6YMltzIEN04dba0A+A76VitSSuLSETeTW4Spy
AO1WHaFp4+p2JUFFaw1RhzQEzeqBa+kHKTIgbqc6gtqGafdqAibwYNIKUm2A
3wFqIEJ6qIKggoLwi8PF4ECA1xM88w5XEXvm82d9KZrAi0GbmyjgDqbMXYAO
vYSm0efPx16VSfSI6hZAxRgYiGq1RDU4fTNquyDAkeFpUpZlecsmaBxGj0Fn
UbdZbQEl/XeA0QB2UfOFJYGBbV3gnuOVLeBxwMtqKW/RTuoyKxiT4GxqAxZy
wyS185ezD7u8RDQBASIzsoxRfUcgK7/658R0H+uzgOf6TWDI+tPjfkat1Akg
RcZUFx9BpuxSxGPyABKcwy7yhO00lVqgAItkH14TZCPZVAPoCdvwJzx8lox3
oGXYUrU4GcANNZaiynIX1DtQYHICYLNeAuUWKOJfgeQavgfjE/lPCRrAabVY
rmj0nVfvT3cBS29tXZUkBfFkQXrjFuAB5O6rBh5OdoK6CXw2wIbgf7cqgEAI
jefArWDTsBhE7mrlspJWBkIK5zOAS4AfMO4C3slKA08UaxbmsPwCTc+hm2TC
KoYWTRfg6HZpCuKAvDCCopgoQNvAogyLi4z8EHCGBYyISkUKqatgUjEoRUIl
25pnpFQbWycUDipcm5dfE6deI/Utsxp47ArWPRDTCFbHSFcUxGgUHemQxQpg
AyNQbqa29AQMhHdNX7DmAGg7HKogDVD+seKBiIx2ijeCq8hCECnQwFvyCePO
hSEBnjOLODzcT1jE/tPRC3x6gVZo5tGP+EBt/ico241wr+mqKACjGwXHk3A9
1n6IKdMussgAK9FaSXTbJor6ipGXJAxwBEu8MxmzGjeZFbNdFNEjJVPAUuns
BnqMCjg/BBsHroowsDgk/iKrBZuAlXjTXWUzZFCyPRwl2O5xetYHU2Rg/EYK
YY1REYKnSK1bSD0g5bSsyr+b2sOgsFNDi1tbYOqiGahebEIhtEDN0+tsi6CG
mkTlDfvCM44yCc4gh8XmK8I71GDZ4vcKPUIp6Fak/RtkSKzmq/TcyT8aDwXO
1p+s+WhxWCSz28qiGum51wz4QGKLlyBry+EYl3uXrUnVN4BFbTTrM2pQ+FUA
J8VGHiDY3BbAT0iQZAm1Jcfk4EDAoB4jI5oCL0JsIbggzNrcEjWOYPLnxwDh
FcqjJes2MFDdoP8k6L50hsqfIQB0RQdCG8O/y+BlGZCRgT9HhoMGfE0aU9g4
eblwFNwfa58dld0Ghw8wcOZZatPllKzROiF+OHaYf5gAxs5QUFoy1waK7aWs
6bOOyJnAziM+kzbY0OeE9g/xMgCR9z+hAeii1oibuo+ARNFRnoREFuAnfBXR
tazGVU7n1FQr0hIBBq/BdGOv/Vr4Bjyuss52J/PKTpBIPLDhucJMG7Jg1qTL
lwnghny4ywqUW+Akk7pyvJU7wEDDqEFaqUlMQLR7xR1GP5N/HqgGBKpjFADc
MkyAoJ+CAQ1zupE6KVFbBkUJVZUCNjG5WS11G1zDpjYw17qczEEOixMcUN6J
pyk3E9TKmK0ik62Way0syfQLKFZdDYM3Ma/uLPJ0OGeyO9yNXfpzvyPUE54b
NGxQsnJykmUqUV3oUAcA44zOmJ4EPb1aWjExbcLd4TESNMIhFhkQQlcNZ9lO
mwUaQbcmnaG9MagiuErQd9MYBPqEBcNxyMr8wtGtJSySiZ49YqQH4MoOrhO7
4prtiuseG1hojNf+xKmFQTK0bvEAryNpZLV1N95/ELykuBnewJDs38QsQkxy
2RQZgFicfnYUxeyliMurWnJr0AehWRVdLjyQ8jiRAoetN88VGH1wuB6zR2i5
7dUcm2klR6ij/oF6dtBuQLvu6jtKISOBDSh1pE8SisCvvVgClMmNCP3EJB3A
Vu8MOYCDewpOyIZAyzhj3BCpihBlJoaSDQxEZOHoUW2A6uBYkDnjkalgiZLj
g8Tiyro5bpW2LtsbRL8pyMFqKYBEo7tH6TocPXuOTsEE5Ljnd6i5kV2BG0nO
8ohGF+i44JOiZ73/SxYirivP+shfirYITOLY5EVH/EkQ5lUN+jFYZEUwTZ14
tpRXQEgjQabrF0BEmNGJWGZm2gG9s0uK0CRuK2CRXQD7TfRDFJIyIECCia5z
8G1NZYdDHsifbL4Lm7c1g4HFknAukAhuNY5DiIqf6bYFYMmPx14lDy00Xxsy
YUmulN5dik8ZPhFUcKIiBFrGEjk/YE5NkBL3+R1MdYwYYvk0aKkU6APdaVk5
9hbk17hwJrVrMILpWMSpITpBsLpBahSr/H4PcOJCs00AaWSC6ihYPi2/Rd92
Shm165aTMZkBM+dPg1Ss5ZCJQ7YjGSZVTeefqm2qA7nc4+UV4S6itezYazoD
kmyDVKwNFP8g+2O1mKLE1+geZWegMNHCgoHD+Ela1VFY/XiNJ70qlzWoKIWZ
oY0h/pUJiLTas/xmCIPWw4szngZ+prAIfjG25IBEU02Ucwl0aHYDVmWARQAU
ahBjA7gU7DswsSd4cuoOfgUgaEIkpe3W9JAhBhjds7IdOADEF38G3vdKkMom
uC3vruljTN+MgDONnn+LyxNPTwie0sYCqiRuKwmIBp4nbiQ+JHZKo2Jc1UK6
zLHWyxAmzSvaV1Bp0WPHuOCSoCrCC5FxM2IghE++XNa+unFW1nr7ELat+n4p
sDsinYHc8Y865PWIHact3yUSF9A4yd+qBM5hUUNUIXIVnEhxk3zWzNGaQAwp
uNGXABwOMDDwo0BNc/KAMJ4zAQ8kxBw3CuOZmklYbURWKFxjm01AoHY0nFQU
zJmY6FWOfEbUFmbhXX3GpL53Di6bBbA4NBd72btCnkm/86EOsjVRFzGElcHN
wKYra0gEJZcE8JV3SrJLEmA+Q9la3hfHj/AgsatS04JD6BJe9xY3vFjTogYS
j80J22GjsKNcOIIS5Ldk/JOPHvV+IHXE6cyFNIB1cvpkTjFio3RIxsCdspIl
SjrKOXqHhEqKMOE3FKCJh32UhOBEeAoAcCk90RoaCRQj5W0ybWzgajRtFTmc
zTfi/QEFhay60ndNRn+gI8GbGjU7xGDvx0FQHTP0krOpyqBod8xioJSgHQ42
VV2Q0awcWXEmRZUOtBym1Sz1eRJZ0trKik4PlGhCTmF8HiM3JPBXkUh8q0e+
E916/WywjUQ6QVw4j5/MJFs5H1Ht4AO5ih+c7ZKEW3bI6QBPbgvpsrd1dxDP
dSM6rNI4GknYFcfmUHcNdjcSXlDyu+Pj+oO7NFHy/HmRA4I27j3VbVSJvljV
5uNo3QMMKX+t69vYinaK0E6cusz0QNCSHuK2RjPZnU7WFk1UKlFBN40bgEq9
mgBmGJdgJHn0yBRDs5mtM0DEh4XNEC3LYMO09URR+fJbi9qr9zyLrJUliw6v
dVTJ7o39tuJdbbsRE/3SSBo7QdGRRK6KnrgaijiJh6FQiu5RNq2ufNwsB4gh
pW1xhj8f7RMmcxTQ5wflpvGhV6/JYcZAw3gszkp2f4e8MTAVi8K7IliSdNwU
7Njs+PGECUhkOvp1yFgfUPgkq9lFGhh7ML5ZFpDEGWhLI63hWEAZBM7XoJBi
3FPhWZI8TO9kf8gSI68lWWfjov2KxMd7zP6/+LwcYW1WjgmOnf88G0zxkgiI
f1Rtppo4XHmXXtK12E91t82qforaK5rV3fSuhN8yNqEtapIst0SPBhw1GJ2X
iLPKirts7YYgbBEAsL15dmvJaysMw93LE1RXFImR0/qayIrM/LZrPJp/fr0w
7UAHkWQmHAwDEpQ10+/J5imHAQoUkMpYFbflymyQbGQGbQcO4OZmRB70xxWx
FlBsC5sBy2cje9P5gZGQmAdCKripaxTo8JFyybJOBCweKj6cxJjJe/Qh+huc
fg10s8pAiyCV/AbwHDOZnX705pfLq0cD/l+/fUefP5z/t18uPpyf4efLVyev
X4cPSp64fPXul9dn8VN88/Tdmzfnb8/4ZfhWt75Sj96c/PaIdbxH795fXbx7
e/K6xxagMCzFysgltQQORsSnWkH8n07f/+//tX8AO/8X2Pqz/f0/Aij4h8P9
bw/gByRHCZOi0OUfkcwxPwPMVWJCyHeypQWxiUdAEY07EDYgagGOf/grQuZv
R/q78WS5f/CDfIEbbn3pYdb6kmC2+c3GywzEnq96pgnQbH3fgXR7vSe/tX72
cE++/O5HJA093D/88QeFyHMaE3m62fqqkwV1T/ppVAU2ZLjql+FeQpF7aFvw
Cq2+qR5XzTz13nnPnvf4rpY0aptjxQS4rvbxz/mD0xjBP+8PDiJJbfUH6w3l
CPSCRsRi4lqMWf3FmpiRhCi95xE9Kc1dBf+jNQnDnnc1fAB7N8KvkBn3av2b
GTm8HtYY8QRLn7SrqlLAf+cDmZ1cIVbiRENJdx81GIym8dvJb32SUDs/qEdV
Ig7N0cEp2MsIjWIaY4ESRYl2a9fgyuHoqzwDybNdokrIRgWsdOgsb7vfvSfX
H78oF67MlsB8oj5BaapfMigGLE/AugpO6uhXxdxeYHAe7bNmU4V6YDhT+XCm
lnCmiGZAygrGJkhSBQxIFowsk+VaVI6HmWXLgWKfXYDohJ7zrnaQpWNMiy25
1ChshjaXYd6TXWQFKQjXPrgRU859spfwjicbNCaalfL5t4gVmEGKWnqO+4/M
qvEAZK3StZgS1+BsYWSpykDGeb8PZ6C7FuP9weqM9VcfsGcyWUsiSxI594nR
ksBUiIfA5yNFuzlLfYAthjRQy2oJ3FaWRooZmVJBTWFnaytx/7jLhJBMSa3r
pXN2Olal91S0TLNMlN8Rpo0lwTt8UI5lM/gJv7spsa6hacWdMX+KKSukeie+
O5fIFgAVB0w5QSH5XuXZIptxRP1CnJSJoO2vtRhIWmhUZ4e+XA0x3G01qb4B
/tHR5VRgL8+6jk1UgDToPzTkcQwTWy946EDQ16G8NKRQR/RrpFjGrr7t1nbK
pXFviZhGqk8kZ3eZkY42SnLQtFpQRQVSYJFZYIdjjibis/Im2VqEsrVhU0ji
jg9zLnBg2NDprUqfUzaQMBHbXRxD9ykZOBUF0csbUjVRF62a/ukURa5ofFY0
TVyJ9SGVDbvAcfFaW4DnkiVMalWwnRicisC5wKIyTjZKVSPSkiltxZs+TKvI
0ADvEt4AyqA2C0zC5Kw7Vy3nGKedEMmHEH1MRKew0dBHhIiehE6jHatjqlhQ
jCSJQAX3oCTIihginipZqUB2mMDa2rRXN5zq6D0jzidlCQIQCc6GVtToYS4c
PDYmDMn28CGCeMrABM1HDEp4CRNeuMZxnGozgLbzE1hrLE1BQ3RM+ZdjHMtT
JBn+HPf0Dpftucq8eanzqDqIDiiHPqh24ha8j6SO0gmpYIw+fiqz47EFkNFO
XyxMbuFIi3Xq4KBtURoP89OuyEr4KiJYKgdpaC/DctvyWnlJR7VKXZ6ls4ko
5TFbIuOn1qiucz49CPErUGclLr9OMJgzG73tX2SSFuCTHbxTJVUUxABJIuof
l6hEke+U8WozcVL1HNZm1qjENSIzjfmIqCwyWJOTK5FBNJv+nE138j3OnUTt
S4yyJCzjvaQqlHZEtyAeSQi39s6C8c/90cFuyknJOLgUV7pPrQaeCNjkWRAa
9wBYxkE4Z18ZkTj4PHtnz31yplLfQslpzDlXyKrLDesIHeEY9sM0syY1ztzo
ayzYbUJxi/matc4qJs/4gDSa6TzkkVJ/0K9AAeKAluC4j7/xkCIGmjuMfLe2
oGOxPZaAB7TiXOBgScXsVjGqYBOS/oyO5QGfFi8ZhvEREC5sYyHz+t27P//y
ns1c4INLzCXmVSaxQV4ijJAu0gdDOrmDKYV6Zdx7tcZrFbNjM0nHT0IbQUBH
HY+U+256HZyxVEZswQ5fngXw6E3msghVhB76giWdiSV6Rw8O9Slygugxopk7
PthueqwYT93aKnHY6pSh7nCiBHxPAblmMtr1VZXCNsjkL1h5hXeTHG6Qq9kX
WQjy5pUDJKHFv+skJki6gSS4bKQek4Zn6xBUh/l3WsgiCCTBUDQ9AnYJvg30
yenp+eXlbshi0HTwUVX7KpIFew4WQ1lDOhygyoifUvZ5T/Iguy82kxtxu9fk
9XpYOVhSLqE7uobnJN0SOcn44ESTxOhOc5G28aMtqnnLg5ZEDWwT87gdJ2d0
4pmA8gaLQrw/Ddkb4BlFTJ0BhZM1A1FmU9WH68oDgS7hdwYTopy6D6z6YWDl
ajqu6vAR8yG9D2Ld1FyEQAo6JiW6I0+ESczTcxVQsppqUhWhimMLOiA/jI0C
mOEQfZx61bNVJFmbAqgOo/YUF8Dgf47mZNDHOVKqYX5Qa+zEiO+Ca/VK6eSQ
1g9L2oO3gHBqDAaJ3TAJRlU0XZLaqmgNh1CuLQqanqp/kv4E4qsbpLq7aGFI
QWnSLvFEttb7DMQQ3izIOLLeo4uGnF82DJHuqB3bSVymLBFoTYWZATtr1kS7
PhheStRTiobo3BMLHXPcRaXhLfH5Sm6/N0DoiEN0HWFWStRhVbqVjXkn9IIk
lijVs2iU62jGbrClWONaWD+c6nVgRDM1UZV8qCGGQditAIoNutKQh3wxI5si
YIjprGKMDVWNZ4UzFO0Ak2cFdA3jm8T90usywYwB7qtiG3Ixox7i2BH9JeUX
sE8ozUdS25ynL4HhuK0/qCT41Q4XUXBHMsoRqL1VqqpVk/4Q349OfD946FSP
6dKuM4EpMrGhYx11EWLRnVCplXYfYNZMkJ8qKoQqpwXZAPd6lHtERzvTysRe
A8HFyNKkVbi2ZZyuTGd7oa4xJTNNook9SdL6hOxWXOVqMzeJ7SZJewIUJcUj
lyB4YDEe07aGUrphJJFKrTqNmH+cbbgMJFSyKbYCwxF2E8xgHHFZOYtIThm5
wIPwMznBPfy4Ah4fFR0nhD3a7q8OfCmbIO6orzADddro1063Rw6AePAgY2hl
WMW7BYH+uOuLSCZRcplUL4iWSl93iLb2ig60xhaJsFDwJFC3WKphPa18Yn4E
0+58WUZavzgNmTs+/bxthIu+2rdBRztkY0HRR7BGOd2+F0j+wMny8X0MboxZ
hoNK/QF9DZGoVg5r+N5dXbz87eD69NXJ25/P4b+L12fXqM1eDlRaCsp2LGi6
1/D29dn56/OfTzD8OhDnVWFR4AplcOFeugRKNpQNUBksl81h46MoMzIydRvb
RC+UTR1THqJJtyLyP29prHGkNpeLU/m4ceqvSfUbsfd8thMeSWgjQEpAuoAV
eqxhhMhKqX8IFTG7JD1ztRhj6HC6AQQnPZTiU6QgsHPD50qnMUwJW/Ey02rU
0ByLGvtIFwwk/J3gimesUylZjQ6SQmDfTYkrZXHgjhsOHe6kWVZSzJ5unduE
cHoKf+StwhHvHnualPTIa3rxmhxaW+vE2PNFSbVTALQitBrGp9PJhVyiR5UJ
lnW49EFKxCb0RxmKKSaP720HKBVLwoT/ufqxjCKlQ6k9qCoQN2WC2Cyp2q1W
UnMaawhZX5G6QHgGSBN/X0vGfY+YTnKeFRXvpvZD1hov+jIoQA8aI3mFUeSs
FosMnjPdsrNVaEwxwU5CpQuxII73RN79bLQvLQXUow/610fkkJhkQUR7dw37
oLhLTccljLgjzjiFj1EQBHXY3/VblGRb/vyuL3L45wzP42q9NPD5ZDLRv6vf
h/f9+T38k34xhNf0fSf+uz48hH/weP30sF2Y7dORfuxByg0Fv3/01ty14m/B
D/boc1cz94hB2mEvdqCHOyFdJb0ZEO88cJPy7gcgLyks3pnKuXOeRcfZSakX
f8rLk9eX50chGCBprN10NwOKgEvK+bVEFO7xyu7vDhQRdsqaZJoN3TR8Lzab
oTJ33oYi6SEdAPzEFOi6My44LkNZZN+S1P7h6NvR8102F4i319ldbm63b+DZ
6Pn+Ltuk4v13CuEI3Gy6KrxKFADda0V6T3b3mHVyzJcbx9znr+g9Zn3/Mav0
mIF7HJx/+HD964d3b3++vvrt/fkWfe0bOLpnoLNx0yTSIzvu9E5ok2VQIx0v
ioJCkcGW8q0FuF77KLXxpTB6gJvB2iwUWj7/OMsx4EXBQ1R60Uyxs1Ut8gKL
8gBXeUyyLrlUilxZdVUQvH2KhkBHSaG/rJVgQyr8f3AYwKdEEpTYHbgFlRBC
LwC9Yd5B4vwgSZfR9sdJeNurYhwUjwUYityppMBjoXYoZsOqtUFYyPvzD2/u
Xcaz3Q3kSmgsPapgybNIFlB7VbG9/4u3/37y+qi3R9HB6GD0HA0NnNF5riX1
TKQsbkUWjk/IUn3KEDo9QDGfGUUtwTpRKh+rJH+UsChOQ8EuiC24g9VlZwBO
7JKzEexOHDtk9SVsqYoqJCW1JFWPHsFKyXdJ4t0L0AOklQijpjQq2ODonI/s
NTVGVv6Kz4F6qtERcN0vBhZrLmVsJ3DQTFW9kPy/ZHfHMc8lOBeDdUuJMBKq
4mzeYFRIppXHAOuXlKcRbhTa1M4s0lOLAbBmzwVVFI/m9J5TMFeuzhXXb2Dx
IA7/9uUBWjDbaqzFcpJi1VR7Vdh3wK+YzQ4p4epWNkb0y6ZAdHfU/5YT7jhu
k7Kj4I9I+6h4DExJKraoo2OM3XEShzMBt8fEl8yMdo+RraVW7AfAVnjLbBbS
Idsw58hi6mLywPDF0311ViFJ5JhwmchfygepsRQpuwvymmPeUlFhB6oWuDBb
bdrOQGE2P8++ptsbFdr0OB0Cg/IJeVnIUvQF9FG2pbX80e3hGxHlTI9J+CUN
sPEJ43SK+SGylUHXiSNiv/I77o/1NFKdIRI9TS54YEFM1siUKtStxxBf0n0u
a0KALxAn+rikL/q79+dvvbl8DmL+4uo89TtUaU5lgh6cUxn8ZRlX/lTeISBA
oEQdH+CMVa3SV2OQZD353BsfBsZj4sTK05+uvUq7s8WkPWAV7aqTy5eNMS/U
eq8qaxq0MDjyIveZSYEJeglDciItq92QAr70lMtOuMwC++qStxrdTjILCSua
ShrDYGeYLv42ocRTpHysC223SqI2Lox1QbcVXJFMluvAi6oIS/R/JlzteEvW
9jxxjqxcO4JgpGf25uqVpPuTe5FmsmVrKaEUqBB7tF3Pub0LTmw3GJoOSXGZ
SnveAJ2x0i/0x7sWSzXdN0WAsMEINctSvc2y/JySWO2jWps+KLXVB6VZgWux
8qSDVisxSXG0q6wYoaj9CR0yRyWJvLi8jHfV3RLW3XAvL3JBsU5JKY0VIdu5
OEd98wXxc/kOIsyjJMU2dV1jJhTlWwlb9J7TrMUOqXqrMA13QsslnB54XXcQ
Wjbg3BET3JgVd9bEvMPY8+tYp8TFWSW2u21x4pjYRJkSROo9JRLS9SnJ3Nhe
EvgieohLcor0KM8c1ghKUlqCHhoEJ11SQ148ugGDDIqB86+qvz1O7ANUEP/p
tl46tPWy1DyXun9yInnNKjkJhxhd60Tnn3QDA74rOIbDMucVj5YYa/X/+Jqk
iGRz4vVCASJdCfxUoavmRoVBi31ToBOUmM2+0UztdjaTwpg2YrH5ia1tG2+4
IPqh4kMMlNnpqkySn1oVIdZn4kfaSdrGulSYJ01oynV/yUMnytoq9/PW4+YG
K8o3nbSaeiZ9/Z2SBLVWVmqaT+qxloU+ZkaK739AkLmvUL9Hr8VN+FBSqB/t
6ca7USktIE1EcujoURoOqcnxDjHqmetYH9yrY/uaTDIhvNc/1rB1kgJU0g1u
WxWn/mIVp0qrOLvlF1sqNu+vt3qo0miiKPceFnGcpz2vOOjhwwvc59WfC+kx
Wr+j1Ef0OkWPY3WvyweLE71Ls5UDREKw42vm1pPS5EVKi9NyXSZOksOtgCmf
InPlxD5lD1foJci1rVzTrURWbglOsjJYmGS9nPMpRfDt86G0HG6GKlljUk9M
QdegW2AOy2IJEyCnwCd59+0KZNphh3akEhmPbzKhzOEZtsqz7WyprzKrQvo/
un9XDV3+Qu39eqDRSrURLyHGR9k2SB5jWR+1+9ihMcmW6Ma6Qb6SIzZmv7b6
+CUOkmDxzVBAYfMdc5fI1675kjQJC4lq98Bmo5RbC79u9fp8/Fi/z7DrrylQ
/EjQaFlOfcToYdC3rt3fqZsh4b0KS5xDwNjvB3m2GzR+cYepNKPONt5rMYjl
jmFBDFiGMUybzRDXbu1EjDWnOR+H6ChpLBOSBIpsDcgzaGfbojO2YZKnYoqB
JvNyoDEIcnFFO8N4psE4NvGWmMHJBxeXtiVb/Pnoxa4HEa9BWn/4XQTHFnMB
hWDkZPyUbSW9jLGOL2ky5HfoouiRNnQ1N+pTmKUjAdpY2yNriaZdpycO5510
KSDolVx+2pGF5FnPfIGRWJhSE8FeGJ/TozkkUIUKcslHo0Up8qpxdafjndZJ
bWPaK6iNCiGe28EaTKXxHi32qFCVSF+DUuL+QOevT35798uVoMEWdB59Q469
mGVDTQ69zGOzpzVO6lmTyl2BkmDIpvHq00+b2JUukiJrFt3SPA8oSXiWNiDh
9oLjVg+uhXc2d0EmQt7XdqblIdQtrqmoyPOxPmdiOqIgNTOx80SN/JVqTGFz
v4q86cayT30rItJ8hDQ1mJQrrrDydRrs7qL8Sp9YulHZhArhtl5H3GqZ7nag
Hv8rF1NmHnbxSOS17R6OPkHWgTaT1bZyLCXExbfzaA/+fbTbIYBU1Za+Y2kV
MzCa0rV7RQ/E0WAbbrORD6vpkO0cTOQqqJujjzPQ+1SUi+VjwWLgiuJQXkxm
n+e/XQbgqyOQoJq76rgtBoIPEWk3GBG+U1/bX+WLGBIkTs8ztrIRRG5EPMcV
e2AqKWgR9UFm895DkHin2KXOTrYg404f8pl8N153489wkGoFUpnXxYzglO10
opH84xWfh+wl6+wElvuPf/xDnSRnnv7x9qKkRHe+vWSJk6QDtF5upw70f6s6
6IkX7f1O//SmLcROZN7FtfXRdr9nSdeix/sSG37YlvHww/YZBGOPtj+BdTs7
uNTv958+3b3vubE898w/913fYnq/JDDKK17mDvRYbZlJ77Tz3xh3QKHY+oK3
uJMLBpq52f54pxAm9PoH/N76TneN3XqfWstVLQ8eQoup4cHP2e0P/EMvfYNn
0Yug/WvmasWoNEr54dYXOuEVTJa75+FOBcFu35FjAnTDK93LvmqtHhEesNqI
PnENHsjETDCpZ2pnkgY+DN0ROL2nn/dhbs9F6HOIieufPm2OgVlXZB132Vjs
XaI64BfgejObmoJgcmeVQN9XPIeuYmAcYzqD5PXz5QlOd5sdcJMzfxPcWmfR
r0rSg1xXvm4m0aCEeXGogm76YLeaXZjWMsMKgb7ZvveyJpVqTVXdpEISU9R9
+NNrJGqRfbQLTFXzF6FQRFICGbSvbam3L+gp9udKdJaTU0Mp7apuhVE793vI
bZxyCrZsX5tVee+Il2odyd6tUGMdHrmP5w6U+B3BVpjNZh4sku/RC++7uXiL
SP4qJ4JqORFCV2cp7OK0vk25ThczpSE/6dkf+8f/f8n9X1Ny/1cRk/+PsaH3
8Z0225eMwnz3Pw1/vvlPwJ8eNSBI6W86Ulr41hfl9FuA5P2yujtSkNabBpSe
VdQTo2pJ3Q3pqdvSM8Q/0oh+uFOw35ykhjC++KIjJjWVtRyz463tV2e7ks1D
1+bYMdgs3ZbQZkxvsEwaodhYuVtWSSJtg0XQSVEXezf++RwXihWSkPN3Gncc
GblZcBQp5JY/XGYlXpqSe8GkiXreZd1qS0MqgvIeHp8N0uO8j91gpFsOFdF2
G8J0PU6mdLGZ1Ka76olHGCXt6Ta78oWbyCP+PZE6xxiZVd1AZNKlrqEOUGmy
A2cVtHpTyeENY8fqVneqtB4VwzDIynEX/n5wuhi53e7nEv5f/V+7AvuKS1Op
nhb9v+TxfJUtYNN0b0TI9OGATNok1jzwfnLxyofRX9ty9dG7FSXwwX142wSY
Od/ewt+nHu9s2Sgh7Glo6LvKtegnJoLG7lZpI7me60fRMe+Zlm9bdsEcJGxq
0GlYRkFBHwWOtzhEVFMU1mMH3MeJMRRI8pdStor44h1rGV3vyFmaPhL2NcU2
kkyQwh9DrXTTWBv06KhzeyX/PfiY16MJN8jK0AAYWrydTE+LbEa3ntvhD/eW
JmM4l1sXl/7Wlr0CF4GjX0/daB5T0hjMSziDZBHopZpQsgjmIHIrcpodMQKv
6GqSd6X0kSQNc5iuV8yr0fGNQlJ2fPxTWpZQqkHeykgZUTfBgtvg+wirb8yC
EKJasZBTw2SPZxvu+MGtTelKnja6ponustBwIwrfrD7JltwuYEq5QZnqYLa/
WqXwgRefnkfma4rxZL5RWa9uOld6+hYsgY92fDkuxMvYoT8crzEFjZgWbo0z
CbnpUDaZ1CsPIzqWlctmUtJFi1MkOu8shqFMESotPJD4TY74M523E7LoUtTW
RaY+3QNF9NYWaKqnBZr+yhZoXWR6WAu02PpNbXZB64Z5++i10/vNlJ582y27
6e4noBDFuQpp23SKp5d0zXbosNENm4sI/nLXjuOgSHVL/SW8kKssls37XGwn
sp6TtLONXWHJS8W1tZUiToEr0DtLubDsYPgCZet386ZZuqO9vQJOeHSD9XzF
qKpne+GVvQnGcUf73x5+s3/wdP9wfzSzzciVtvm7qf+UvPEDFuOcfwTmRvfR
xNrUKLY6hXmdJAyK57hYC5tcfvdlyTDNXCMiR3kZ0Ln9uCsL0KMCutzkxjcB
4H5N1LWqnTChN8ob05tqHuu/nH0IpHZfqWcowiOvgwahoPb29vAvFR8A4iTV
ffzny8LpOIxB1fL6JYaZD65/eXt6cvrq/OSn1+dYo3z+9ur6zfnVydnJ1QkM
+70+POQX0YqhyF9DHVdYD4ANdWtTEOA+wVd/+Z5sld6T3XNn94P0HhFpuJp0
CMRtntDfDgyHUYa64mxiC8tNn0GVw+Z0fmuKBTBJrfWwqYZ4zpbz58DqGOmr
yj/NcVSKNhq6KZBW2lnJIGTAxWZNbo6X0fIjMam4SO5xc/OBngHMuHc9Jo2t
GlwxNRZwiQ4/XgM7owvesNicUIZGV4//ZW9syz03VziOfvI/9B/gKJ/of/0D
GMg44BP3I3+nf/zxSfe7f4Xv+NhfpvkTfLGDrJzEON4zpJ8IQEZu/kRsy/Zt
VEqew3WPmo/NE6x8Ay286UIG786GAVo7cXMdx9ffaT+I/qFVCossZPSRF33F
fkRapQ+agxzmrnpFVt7wbW2xSQMiCpwilonwZar6CUKLfdwkeDBTbkRUnBxu
Ul2/OQL15luMTZ7HJquSghFgM/IGhud1OAHKGk9LfS1auK8U4wqwBBcdmJ71
oDopAOFsmJ32NfShSPq5b7Rl4713ioLbKAl4dMkFzb2ifxCFeTWdOtMc4BWs
5ayZH3BPNeobckf3LbvkPnJMW6cB/dsrILXnz6452Qt/eHFwzTklPieKoMH9
2fiGdX+RXtZs7EMiuAg7kDzwNKiw8WZmKobIY481GK6uwFjLyFU8iYcpZWCB
m8MSiH9fotGIrZMwSRSEjqQF9SVwSh8J/0LQgriPR+yplmRuqi3N1Chjod3s
p+s+6HbWQk5CtaZBxexz4EfzjRL2vS7cufBPBGdasI9o7nMW6nYJf8yC3rz7
DVQPuvCtVd0a2F1MCVPpVTobDQekpjAmXj9A9rWT59JL2B7ekGBLFxzfOi6k
0LBpwNWhIdmzcVJ1pqRO8ks1c5I+2FkNIHaxteE0jOaTY+gi1Fzuwmw3LgtR
KtTqgTw73hzU0kWxEsKZCK7TKKg9xnjSFHvhM9NuXWGJVb+b9Z8WgzGXpgnN
5WMRXSchUuy97tJoW3jteTROwrbQUPJG6EbORhmKcZJaDRa5QDmKLsVGZ05R
ZXmQvjGtA9GcHBWyjnsaH4V+q8klheQwAcwpsjGIhtDtmzbJ7bam+s3JaWQW
hCnc6PQkyesaF3YmkKc6E/UaBwRwY/bgjjNGOOGzp3hVCyIg3vDNteiDbhv0
kNL2x3DLvaeAgPO7fG/MXEpCfcJOF7wg2gXyhpqkpNHuLLhxHuuLk7cn/Zwz
EIHkQNKTrIohsANpxoYr1KDGSWkHtqGT/vpVTXe00+WogLncxpj4UruJumRE
ljxVbWZYnb9ZyErpPBFNpS/O4eEA73l3Jr2gtrs4ffjtQy072OJwOKTTQjid
THwVORlw6tMRj2jy7x9RnzlqzVGjg//N+qYw4xWW1r2xN0Zfsrk10P8GJ/uy
WJeA53/G+j39BjRfAIBk7l7NqwXI51fZGlP/kQ0g5ExA/miKAW9LXJSw0g92
cgOjTWDixUCfzlfw42u+3PAMnRxvgbmiqXSJpKtfZnZsUZE9ndcA4mo5V69A
KbizM1ijmU7162zd+IzQf8sW1ug/V2aOBYW31txJdUCiKdE4+qIE5b0a6J9A
eJf6fXaHcYsb21nPf88QIy/RjcfxDvUzSNs1Lqqer+i+ElPgvdGzFXdkI4OB
bt8dqf8D7/v5pK+XAAA=

-->

</rfc>
