A new Request for Comments is now available in online RFC libraries.


        RFC 1686:

        Title:      IPng Requirements: A Cable Television Industry
                    Viewpoint 
        Author:     M. Vecchi
        Mailbox:    mpvecchi@twcable.com
        Pages:      14
        Characters: 39,052
        Updates/Obsoletes:  none


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.  The statements in this paper
are intended as input to the technical discussions within IETF, and do
not represent any endorsement or commitment on the part of the cable
television industry or any of its companies.  Comments should be
submitted to the big-internet@munnari.oz.au mailing list.

This RFC provides comments on topics related to the IPng requirements
and selection criteria from a cable television industry viewpoint.
The perspective taken is to position IPng as a potential
internetworking technology to support the global requirements of the
future integrated broadband networks that the cable industry is
designing and deploying.  The paper includes a section describing the
cable television industry and outlining the network architectures to
support the delivery of entertainment programming and interactive
multimedia digital services, as well as telecommunication and data
communication services.

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 announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute