-----Page 1-----

      IPng Requirements Capture Report

                    Us

              March 29, 1994


1   Introduction

[not reporting on decisions process, just on requirements process]


-----Page 2-----


2   Background

    a.  Internet Growth:  More, or Better?

    b.  What Hwere IPv4 requirements:-) ?

    c.  IETF attitude:  Better leads to more anyhow!


-----Page 3-----


3   History

    a.  Craig and Frank started, in the fall of 92, to start  
        collecting and trying to formalize the requirements for 
        an IPng

    b.  Formed IPng area and directorate

    c.  wrote rfc1550 to solict white papers, and they got about 
        15 of them.

    d.  req's draft revived from the graveyard brought in by the 
        directorate as a base document.


    been reviewed and revised per the directorate


    And  Frank  and  Craig's  impression  of  the  real
    requirements of the white papers.


    This version of the document is the current ID.


-----Page 4-----


4   Future Process

    a.  white papers reviewed by the IPng directorate and
        external reviewboard

    b.  white papers internet-draftized

    c.  white papers informational rfc-ized

    d.  At some point in the future, Scott and Allison want to 
        respond to the white papers { describing how we think 
        that we meet the wp's needs.


    also,  req's  document  is  looked  at  by  the  review
    board  and  by  the  directorate  {  with  changes,
    etc, as appropriate.



-----Page 5-----


5   Requirements Draft - Contents

    a.  Principles

        IArchitectural  Simplicity

        One  Protocol  to  Bind  Them  All

        Live  Long

        Live  Long  AND  Prosper

        Co-operative  Anarchy


-----Page 6-----


    b.  Criteria

        IScale,  Topological  Flexibility, 

          Performance,  Robust  Service

        Transition,  Extensibility
  
        Media  Independence, 

          Unreliable  Datagram  Service, 

          Configuration,  OAM

        Allow  Secure  Operation

        Unique  Naming,  Access,

            Multicast  Addressing

        Network  Service,

            Support  for  Mobility

        Tunneling

        Control Protocol


-----Page 7-----



    c.  Non Goals

        IFragmentation

        IPv4/IP:ng  Communication

        Firewalls

        Network  Management

        Accounting


-----Page 8-----


6   Conclusions

    a. Chasing Exponential Growth is hard

    b. Politics and Religion has given way to technical
       process

    c. The IETF way...  Go to the BOF, thursday morning, 0930-1200