<?xml version="1.0"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<rfc category="info" ipr="noModificationTrust200902" docName="draft-ivancic-scf-testing-requirements-01">
<?rfc toc="yes"?>
<?rfc strict="yes"?>
<?rfc tocompact="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc tocdepth="2"?>
<?rfc symrefs="yes"?>
<?rfc comments="yes" ?>
<!--<?rfc rfcedstyle="yes"?>-->
<?rfc sortrefs="yes" ?>
<?rfc text-list-symbols="****"?>

  <front>
     <title abbrev="SCF Testing Requirements">Store, Carry and Forward Testing Requirements</title>
     
     <author initials="W." surname="Ivancic" fullname="William Ivancic">
        <organization abbrev="NASA GRC">NASA Glenn Research Center</organization>
        <address>
          <postal>
             <street>21000 Brookpark Road</street>
             <city>Cleveland</city><region>Ohio</region>
             <code>44135</code>
             <country>United States</country>
          </postal>
            <phone>+1-216-433-3494</phone>
            <email>william.d.ivancic@nasa.gov</email>
        </address>
      </author>

    <author initials="W. M." surname="Eddy" fullname="Wesley M. Eddy">
      <organization abbrev="MTI Systems">MTI Systems</organization>
      <address>
      <email>wes@mti-systems.com</email>
      </address>
    </author>

      <author initials="A." surname="Hylton" fullname="Alan G. Hylton">
        <organization abbrev="NASA GRC">NASA Glenn Research Center</organization>
        <address>
          <postal>
             <street>21000 Brookpark Road</street>
             <city>Cleveland</city><region>Ohio</region>
             <code>44135</code>
             <country>United States</country>
          </postal>
            <phone>+1-216-433-6045</phone>
            <email>alan.g.hylton@nasa.gov</email>
        </address>
      </author>
      
           <author initials="D. C." surname="Iannicca" fullname="Dennis C. Iannicca">
        <organization abbrev="NASA GRC">NASA Glenn Research Center</organization>
        <address>
          <postal>
             <street>21000 Brookpark Road</street>
             <city>Cleveland</city><region>Ohio</region>
             <code>44135</code>
             <country>United States</country>
          </postal>
            <phone>+1-216-433-6493</phone>
            <email>dennis.c.iannicca@nasa.gov</email>
        </address>
      </author>
      
           <author initials="J. A." surname="Ishac" fullname="Joseph A. Ishac">
        <organization abbrev="NASA GRC">NASA Glenn Research Center</organization>
        <address>
          <postal>
             <street>21000 Brookpark Road</street>
             <city>Cleveland</city><region>Ohio</region>
             <code>44135</code>
             <country>United States</country>
          </postal>
            <phone>+1-216-433-6587</phone>
            <email>jishac@nasa.gov</email>
        </address>
      </author>
  

    <date year="2013" />
    <area>individual</area>
    <keyword>store carry and forward</keyword>
    <keyword>SCF</keyword>
    <keyword>disconnected networking</keyword>


        
       

    <keyword>modem</keyword>
    <keyword>SCA</keyword>

    <abstract>

<t> 
This document provides guidelines and requirements for testing Store, Carry and Forward (SCF) systems and protocols.
</t>

<t>
The Testing Requirements document is one of three that fully describe the SCF system. The other two are the SCF Problem Statement and the SCF Requirements and Expectations document. <!-- insert refs here? L. -->
</t>

<t>This initial document is currently just a skeletal outline, published so the other two SCF documents can reference it.
</t>
    </abstract>

  </front>
  
  
  
  <middle>

	<section title="Terminology"> 

<!--  Informative Document, RFC 2119 does not apply
 <t>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 
document are to be interpreted as described in RFC 2119 <xref target="RFC2119" />.
</t>
-->


<t>
Detailed terminology is given in the SCF Requirements and Expectations document
<xref target= "I-D.ivancic-scf-requirements-expectations"/>
and will not be repeated here. </t>


	</section>





	<section title="Introduction">

<t>
As background, the SCF Problem Statement <!--xref target= 
"I-D.ivancic-scf-problem-statment"/> --> and SCF Requirements and Expectations documents are suggested reading. 
The SCF Problem Statement describes the core SCF problem and gives an assessment of the
ability to use existing technologies as solutions. In addition, it provides a number of SCF deployment scenarios.
</t>

<t>
In RFC760, one can find what has become know as Postel's Law or the Robustness Principle, "In general, an implementation should be conservative in its sending behavior, and liberal in its receiving behavior." This rule was originally targeting protocol implementation.  A corresponding rule for testing may be, "If you claim the protocol can do it, you have to prove it - test it."
</t>

<t>
Conversely, being able to simply ping an end system does not indicate the network is fully functional. It just means that there is connectivity and the potential for the network to be fully functional. </t>

<t>
The primary motivation for developing this document is to establish thorough, repeatable, tests that will fully exercise a SCF system. Past experience has shown that testing of SCF systems is too often inadequate.
<!-- wait - the other doc defined SCP as 5th-gen and said it didn't exist
yet. So of course testing of something that doesn't exist is inadequate! L. -->
 For example, tests have been performed on SCF systems in fully-connected, high-bandwidth networks where only forwarding would be exercised, or the traffic would be so minimal as to never tax the storage or queueing. Such tests are valid as a starting point, but insufficient to determine that a protocol or implementation will working properly in a reasonably-scaled deployment.
</t>

<t>
A secondary motivation is to improve implementations by providing a known test environment. Knowing some possible ways that the protocol and system will be evaluated may help establish how the code is developed, as well as identifying hooks for monitoring particular processes.
</t>
 
</section>
	
	<section anchor="TestSys" title="Test System">
<t>	
<xref target= "testsys"/> illustrates a generic testbed for testing may aspects of the SCF protocol. The systems consists of 12 SCF agents and 16 links.  Any or all of the links may be disconnected at any given time.  Even though the system is simple, some complexity is necessary because the system must accommodate testing of aggregation, deaggregation, and fragmentation with multiple container flows of various sizes and priorities.
</t>




<t>
<figure align="center" anchor="testsys">

  <artwork align="center"><![CDATA[
  
 +------+                     +------+                      +------+
 |SCF-1 |                    /|SCF-5 |`.                  ./|SCF-10|
 +------+\                  / +------+  \              .-' /+------+
          \                /             `.  +------+.'   /
           `.            .'                `.|SCF-8 |`.  /
             \          /                  .'+------+\ `+.
 +------+     \+------+/      +------+  .-'           \/  `.+------+
 |SCF-2 |......|SCF-4 |.......|SCF-6 |::              |\    |SCF-11|
 +------+     /+------+\      +------+  \             / | .'+------+
             /          \                `.  +------+/ .+'
            /            \                 ::|SCF-9 |.'  \
          .'              `.              /  +------+`.   \
 +------+/                  \ +------+  .'             `-. \+------+
 |SCF-3 |                    \|SCF-7 |.'                  `.|SCF-12|
 +------+                     +------+                      +------+

 ]]></artwork>

  <postamble>SCF Test Network/postamble</postamble>
  </figure>
</t>

	</section>	
	
    <section anchor="TestReq" title="Test Requirements">

<t>
List requirements and test for each of the protocol requirements in the "SCF Requirements and Expectations" document
<!--xref target= "I-D.ivancic-scf-requirements-expectations"/> -->.
</t>
	</section>


	
    <section anchor="sec-con" title="Security Considerations">
<t>
This document is informative and provides guidelines and Requirements for testing SCF systems and protocols.  There are no security considerations.
<!-- if informative, you will need to remove the standards RFC2119 language
at top. L. -->
</t>
    </section>
	
	      
    <section title="IANA Considerations">
<t>
This document neither creates nor updates any registries or codepoints, so there are no IANA Considerations.
</t>
    </section>

    <section title="Acknowledgements">

<t>
Work on this document at NASA's Glenn Research Center was funded by the NASA
Glenn Research Center Innovation Funds. 
</t>
 
    </section>

</middle>


  <back>
<!-- <references title="Normative References">
      <?rfc include="reference.RFC.2119" ?>
     <?rfc include="reference.RFC.0768" ?>
    </references> -->
	

    <references title="Informative References">
		<?rfc include="reference.RFC.4838" ?>  
		<?rfc include="reference.RFC.5050" ?> 
        <?rfc include="reference.I-D.ivancic-scf-problem-statement" ?>
        <?rfc include="reference.I-D.ivancic-scf-requirements-expectations" ?>
  
    </references>



  </back>
</rfc>
