A Direction for IPng
RFC 1719

Document Type RFC - Informational (December 1994; No errata)
Author Phillip Gross 
Last updated 2013-03-02
Stream Legacy
Formats plain text html pdf htmlized bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 1719 (Informational)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           P. Gross
Request for Comments: 1719                                           MCI
Category: Informational                                    December 1994

                          A Direction for IPng

Status of this Memo

   This memo provides information for the Internet community.  This memo
   does not specify an Internet standard of any kind.  Distribution of
   this memo is unlimited.


   This document was submitted to the IPng Area in response to RFC 1550.
   Publication of this document does not imply acceptance by the IPng
   Area of any ideas expressed within.  Comments should be submitted to
   the big-internet@munnari.oz.au mailing list.  This RFC specifies
   criteria related to mobility for consideration in design and
   selection of the Next Generation of IP.

Table of Contents

   1.   Introduction . . . . . . . . . . . . . . . . . . . . . . . . 1
   2.   A Direction for IPng . . . . . . . . . . . . . . . . . . . . 2
   3.   Issues Toward IPng Resolution. . . . . . . . . . . . . . . . 3
   4.   Security Considerations. . . . . . . . . . . . . . . . . . . 5
   5.   Author's Address . . . . . . . . . . . . . . . . . . . . . . 5

1. Introduction

   At the Amsterdam IETF meeting, we held a BOF, entitled the "IPDecide
   BOF", on the process and progress of the IPng activities.

   ("IPng" stands for "IP, the next generation".   The IPDecide BOF was
   chaired by Brian Carpenter.  Minutes are available in the IETF
   directories, with the file name </ietf/93jul/ipdecide-minutes-

   The IPDecide BOF explored several facets of the IPng process, such

      "What is the basis for choosing the next generation IP (i.e., what
      are the technical requirements and decision criteria)."

Gross                                                           [Page 1]
RFC 1719                  A Direction for IPng             December 1994

      "With the advent of CIDR and new, more stringent address
      assignment policies, are we comfortable that we truly understand
      the level of urgency?"

      "Should the IETF or the marketplace make the final IPng decision".

   The BOF was held in a productive atmosphere, but did not achieve what
   could be called a clear consensus among the assembled attendees.  In
   fact, despite its generally productive spirit, it did more to
   highlight the lack of a firm direction than to create it.

   The IPDecide BOF was followed the next evening by the open IESG
   plenary. During this session, the IESG and the assembled attendees
   discussed the IPng issues and seemed to arrive at a consensus based
   on the following set of bullets presented by the IETF chair:

      "The IETF needs to move toward closure on IPng."  That is, the
      IETF should take active steps toward a technical decision, rather
      than waiting for the "marketplace" to decide.

      "The IESG has the responsibility for developing an IPng
      recommendation for the Internet community."  That is, the IESG
      should provide leadership and take specific actions to help move
      the IETF toward a technical decision.

      "The procedures of the recommendation-making process should be
      open and published well in advance by the IESG."

      "As a part of the process, the IPng WGs may be given new
      milestones and other guidance to aid the IESG."

      "There should be ample opportunity for community comment prior to
      final IESG recommendation (e.g., there will be an extended Last

2. A Direction For IPng

   Building on this consensus, I'd like to announce a set of specific
   directions in the IESG that I hope will move us toward timely
   resolution of many of the key IPng issues.

   The IESG will establish a temporary, ad hoc, "area" to deal
   specifically with IPng  issues.  The charter for this new IESG area
   is to develop a recommendation on which, if any, of the current
   proposals should be adopted as the "next IP".  This recommendation
   will be submitted to the IESG and to the Internet community for
   review.  Following an adequate period of review to surface any
   community concerns, the IESG will issue a final IPng recommendation.

Gross                                                           [Page 2]
RFC 1719                  A Direction for IPng             December 1994

   All of the current IPng-related working groups will be moved
   immediately into this new area.

   This new area will be headed by two co-Area Directors from within the
   IESG. I have asked Allison Mankin (NRL), current Transport Services
   AD, and Scott Bradner (Harvard), current Operational Requirements AD,
   to serve as co-AD's for this temporary area.  I am very pleased to
   report that they have agreed to take this important assignment.
   (Because this is expected to be a temporary assignment, Scott and
   Allison will also continue to serve in their current IESG positions
Show full document text