P. Internet Protocol (pip) -------------------------- Charter Chair(s): Paul Francis Internet Area Director(s) Stev Knowles David Piscitello Mailing lists: General Discussion:pip@thumper.bellcore.com To Subscribe: pip-request@thumper.bellcore.com Archive: thumper.bellcore.com:~/pub/tsuchiya/pip-archive Description of Working Group: The PIP Working Group is chartered to develop an IPv7 proposal using the basic ideas of Pip as described in the Pip overview. Pip is designed on one hand to be very general, being able to handle many routing/addressing/flow paradigms, but on the other hand to allow for relatively fast forwarding. Pip has the potential to allow for better evolution of the internet. In particular, it is hoped that we will be able to advance routing, addressing, and flow techniques without necessarily having to change hosts (once hosts are running Pip). While the Pip overview demonstrates a number of powerful mechanisms, much work remains to be done to bring Pip to a full specification. This work includes, but is not limited to: specifying the header format; specifying a basic set of error messages (PCMP messages); specifying the Pip forwarding rules; specifying host interface messages (particularly the directory service query response); specifying rules for host Pip header construction; specifying modifications to existing protocols for use with Pip (BGP IV, OSPF, ARP, DNS, etc.); specifying Pip MAX MTU Discovery techniques; and specifying a transition strategy for Pip. Over the near-term, the goal of the PIP Working Group will be to produce these specifications and supporting documentation. Over the long-term, up to the point where Pip is definitively rejected as IPv7, it is expected that the PIP Working Group will oversee implementations and testing of the Pip specifications. Except to the extent that the PIP Working Group modifies existing protocols for operation with Pip, and to the extent that the PIP Working Group must be aware of routing/addressing/flow architectures to really make Pip general, the PIP Working Group will not work on routing/addresing/flow architectures. Goals and Milestones: Done Review and approval of the Charter for the PIP Working Group. Done Post as an Internet-Draft a description of the Pip Packet Format and Forwarding Engine, the Pip Control Message Protocol (PCMP), the Pip Host Interface Message Protocol, and the Pip MTU Discovery Protocol. Oct 92 Post as an Internet-Draft a description of the modifications to BGP IV for Pip, the Modifications to OSPF for Pip, the modifications to DNS for Pip, the modifications to ARP for Pip, the Address assignment in Pip, and the Pip transition strategy. Done Presentation and review of the PIP specification by the IESG. If acceptable, the first Working Group meeting will be held. Internet Drafts: Posted Revised I-D Title ------ ------- ------------------------------------------ Oct 92 Feb 93 Pip Header Processing Nov 92 New The EIPIP Protocol: a Pip engine with an EIP shell Nov 92 New Transition to the Future Internet Protocol a comparison of three transition schemes Nov 92 Jan 93 Pip Identifiers Nov 92 New IPv7 Criteria Analysis for EIPIP Jan 93 New Use of DNS with Pip Feb 93 New Pip Near-term Architecture Mar 93 New On the Assignment of Provider Rooted Addresses Apr 93 New The Multi-Level Path Vector Routing Scheme Request For Comments: None to date.