*** draft-ietf-nfsv4-minorversion1-PAv7.xml.new	2009-10-29 15:54:08.000000000 -0700
--- PAv8.d/draft-ietf-nfsv4-minorversion1-PAv8.xml	2009-12-06 01:16:49.000000000 -0800
***************
*** 57,63 ****
  <rfc
      category="std"
      ipr="trust200811"
!     docName="draft-ietf-nfsv4-minorversion1-PAv7.txt" >
  
  <!-- 	$Id: nfsv41_front.xml,v 1.26 2009/10/28 23:33:05 shepler.mre Exp $	 -->
  <!-- Copyright (C) The IETF Trust (2007) -->
--- 57,63 ----
  <rfc
      category="std"
      ipr="trust200811"
!     docName="draft-ietf-nfsv4-minorversion1-PAv8.txt" >
  
  <!-- 	$Id: nfsv41_front.xml,v 1.26 2009/10/28 23:33:05 shepler.mre Exp $	 -->
  <!-- Copyright (C) The IETF Trust (2007) -->
***************
*** 119,125 ****
      </author>
  
  
!     <date year="2009" month="October" day="29"/>
  
      <area>Transport</area>
      <workgroup>NFSv4</workgroup>
--- 119,125 ----
      </author>
  
  
!     <date year="2009" month="December" day="06"/>
  
      <area>Transport</area>
      <workgroup>NFSv4</workgroup>
***************
*** 14334,14340 ****
  
    </section>
  </section>
! <!-- 	$Id: nfsv41_middle_multi_server_ns.xml,v 1.48 2009/06/20 19:42:43 mre Exp $	 -->
  <!-- Copyright (C) The IETF Trust (2007-2008) -->
  <!-- Copyright (C) The Internet Society (2006) -->
  <section anchor="multi_server_namespace" title="Multi-Server Namespace">
--- 14334,14340 ----
  
    </section>
  </section>
! <!-- 	$Id: nfsv41_middle_multi_server_ns.xml,v 1.49 2009/12/06 08:42:55 shepler.mre Exp $	 -->
  <!-- Copyright (C) The IETF Trust (2007-2008) -->
  <!-- Copyright (C) The Internet Society (2006) -->
  <section anchor="multi_server_namespace" title="Multi-Server Namespace">
***************
*** 16644,16650 ****
         <list style='symbols'>
          <t>    
            An indication of file system up-to-date-ness (fls_currency) in
!           terms of approximate seconds before the present.  This value
            is relative to the master copy.  A negative
            value indicates that the server is unable to give any
            reasonably useful value here.  A zero indicates that
--- 16644,16650 ----
         <list style='symbols'>
          <t>    
            An indication of file system up-to-date-ness (fls_currency) in
!           seconds.  This value
            is relative to the master copy.  A negative
            value indicates that the server is unable to give any
            reasonably useful value here.  A zero indicates that
***************
*** 16653,16659 ****
            out-of-date this copy can normally be before it is considered for
            update.  Such a value is not a guarantee that such updates
            will always be performed on the required schedule but instead
!           serve as a hint about how far the copy of the data would be
            expected to be behind the most up-to-date copy.
          </t>    
          <t>    
--- 16653,16659 ----
            out-of-date this copy can normally be before it is considered for
            update.  Such a value is not a guarantee that such updates
            will always be performed on the required schedule but instead
!           serves as a hint about how far the copy of the data would be
            expected to be behind the most up-to-date copy.
          </t>    
          <t>    
***************
*** 16889,16895 ****
          The following fields specify the file system's class numbers
          for the equivalence relations used in determining the nature of
          file system transitions.  See 
!         <xref target='effecting_transitions' /> for details about how
          this information is to be used.  Servers may assign these values
          as they wish, so long as file system instances that share the 
          same value have the specified relationship to one another,
--- 16889,16896 ----
          The following fields specify the file system's class numbers
          for the equivalence relations used in determining the nature of
          file system transitions.  See 
!         <xref target='effecting_transitions' />  and its various subsections
!         for details about how
          this information is to be used.  Servers may assign these values
          as they wish, so long as file system instances that share the 
          same value have the specified relationship to one another,
***************
*** 16900,16906 ****
          bears the specified relationship, that entry's class value can
          be copied to the new entry.  When no such previous entry exists,
          a new value for that byte index, not previously used can be 
!         selected, most likely by increment the value of the last class
          value assigned for that index. 
        </t>
        <t>
--- 16901,16907 ----
          bears the specified relationship, that entry's class value can
          be copied to the new entry.  When no such previous entry exists,
          a new value for that byte index, not previously used can be 
!         selected, most likely by incrementing the value of the last class
          value assigned for that index. 
        </t>
        <t>
***************
*** 42137,42143 ****
     Those who provided miscellaneous comments include:
  
     Andy Adamson, Sunil Bhargo, Alex Burlyga, Pranoop Erasani,
!    Vadim Finkelstein, Jason Goldschmidt, Vijay
     K. Gurbani, Sergey Klyushin, Ricardo Labiaga, James Lentini, Anshul
     Madan, Daniel Muntz, Daniel Picken, Archana Ramani, Jim Rees, Mahesh
     Siddheshwar, Tom Talpey, and Peter Varga.
--- 42138,42144 ----
     Those who provided miscellaneous comments include:
  
     Andy Adamson, Sunil Bhargo, Alex Burlyga, Pranoop Erasani,
!    Bruce Fields, Vadim Finkelstein, Jason Goldschmidt, Vijay
     K. Gurbani, Sergey Klyushin, Ricardo Labiaga, James Lentini, Anshul
     Madan, Daniel Muntz, Daniel Picken, Archana Ramani, Jim Rees, Mahesh
     Siddheshwar, Tom Talpey, and Peter Varga.