Network Working Group D. Heagerty
Request for Comments: 1670
Category: Informational August 1994
Input to IPng Engineering Considerations
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 IETF 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 firstname.lastname@example.org mailing list.
This white paper expresses some personal opinions on IPng engineering
considerations, based on experience with DECnet Phase V transition.
It suggests breaking down the IPng decisions and transition tasks
into smaller parts so they can be tackled early by the relevant
In order to allow key decisions to be taken early, I would like to
see IPng decisions and timescales broken down into into smaller
parts, for example:
- address structure and allocation mechanism
- name service changes
- host software and programming interface changes
- routing protocol changes
Although interrelated, not all details need to be defined by the same
date. Identify which decisions will be hard to change and which can
be allowed to evolve. All changes should be worked on in parallel,
but the above list indicates a feeling for urgency of a decision.
Our experience has been that administrative changes (as may be
required for addressing changes) need the greatest elapse time for
implementation, whereas routing protocol changes need the least.