> > Does anyone know what the current state of play with IPng is?
> >
> > Christopher.
[I blabbed on about a few things]
Nothing like a bit of curiosity to stir me up, here's your answer:
--- forwarded message ---
Date: Sun, 31 Jul 94 17:31:45 -0400
From: The@nospam.cs.mu.OZ.AU, IPng@nospam.cs.mu.OZ.AU, Area@nospam.cs.mu.OZ.AU,
Directors@nospam.hsdndev.harvard.edu
Subject: IPng recommendation
Apparently-To: big-internet@nospam.munnari.OZ.AU
Dear IETFers:
The IPng Area Directors made their recommendation last week during the
Monday morning plenary session at the Toronto IETF meeting. Here
is a brief summary announcement, for those who weren't present in
person or by MBONE.
The recommendation specifies a new IPng protocol which simplifies the basic
packet format, generalizes a number of the basic processing mechanisms, and
provides a powerful extension facility to allow further evolution of the
protocol's capabilities in a transparent manner. The new IPng design
provides for a 16-byte address, which, along with address format design
and address plan development, will provide the Internet with needed
addressing flexibility and scale. Support for ubiquitous multimedia and
mobility is offered by the new design as well.
The IPng design also explicitly addresses two significant operational
concerns, network autoconfiguration and network security. The security and
autoconfiguration features are integral to the design of IPng and reflect a
strong, new focus within the IETF on expanding network security and
improving the ease-of-ownership for IP-based networks.
IPng autoconfiguration provides for both server-less plug-and-play
popularized by Apple Macintosh networking as well as centrally-administered
server-based autoconfiguration typified by Novell's IPX and the IETF
Dynamic Host Configuration Protocol used with IPv4.
The network security functions of IPng provide for authentication and
privacy at the IPng datagram delivery level, thereby offering protection to
all protocols riding above IPng. In the existing Internet, security is
largely viewed as an application concern and is not addressed in a truly
unified manner. While IPng does not immediately dictate a comprehensive
security architecture for the entire global Internet, the features in IPng
provide the mechanisms for implementing local and regional security models.
Deploying a global Internet security architecture must await resolution of
larger policy issues beyond the scope of providing sufficient technology
within IPng.
The path forward will follow the existing IETF standards process. A new
IPng working group will be created chaired by Ross Callon of Wellfleet and
Steve Deering of Xerox PARC, with Bob Hinden of SUN Microsystems serving as
document editor. Additional working groups targeting the autoconfiguration
and transition requirements will also be formed. Dave Clark of MIT has
agreed to review the proposal details and to help coordinate the
multi-prong effort. The working groups will complete and finalize the
protocol specification documents and submit them for Proposed Standard
status. The baseline protocol documents for the working groups include:
S. Deering - Simple Internet Protocol Plus (SIPP) Spec. (16-byte
address version)
P. Francis et. al. - SIPP Addressing Architecture
Y. Rekhter & T. Li - An Architecture for SIPP-16 Address Allocation
R. Gilligan - Simple SIPP Transition (SST) Overview
R. Atkinson - SIPP Security Architecture
R. Atkinson - SIPP Authentication Header
P. Ford et. al. - SDRP Routing Header Format for SIPP-16
The target schedule for this work is:
August 1994 - First test implementations derived from existing
SIPP-8 development
Date TBD - Mid-month MBONE meeting to walk through IPng design
September 1994 - Protocol documents available as Internet Drafts for review
December 1994 - Protocol documents submitted as proposed standards
July 1995 - First beta versions of release-quality software
December 1995 - Initial scaling tests and field trials complete
December 1995 - First production software releases
While this is clearly an aggressive schedule, the talents of the world-wide
IETF community are now sharply focused on one IPng protocol design, its
implementation and rapid deployment. To this end, significant multi-
national governmental, institutional, and commercial support has already
been pledged to help ensure that work required for deployment moves
forward as quickly as possible.
Text and PostScript copies of the Toronto presentation are available from
hsdndev.harvard.edu in pub/ipng/presentations.
The full recommendation will be published as an Internet-Draft soon.
Scott & Allison
sob@nospam.harvard.edu
mankin@nospam.itd.nrl.navy.mil
(PS. Our thanks to Mike O'Dell for taking the time to put together this
announcement while we started to catch up on our sleep.)
--- forwarded message ---
-- Matthew Gream <M.Gream@nospam.uts.edu.au> -- Consent Technologies, (02) 821-2043 Disclaimer: From? \notin speaking_for(Organization?)