One document matched: draft-ietf-mboned-glop-addressing-02.txt

Differences from draft-ietf-mboned-glop-addressing-01.txt

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


        RFC 2770

        Title:      GLOP Addressing in 233/8
        Author(s):  D. Meyer, P. Lothberg
        Status:     Experimental
        Date:       February 2000
        Mailbox:    dmm@cisco.com, roll@sprint.net
        Pages:      5
        Characters: 8988
        Updates/Obsoletes/See Also: None    
        I-D Tag:    draft-ietf-mboned-glop-addressing-02.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2770.txt


This describes an experimental policy for use of the class D address
space using 233/8 as the experimental statically assigned subset of
the class D address space. This new experimental allocation is in
addition to those described on [IANA] (e.g. [RFC2365]).
 
This document is a product of the MBONE Deployment Working Group of
the IETF.

This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind.  Discussion and
suggestions for improvement are requested.  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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

        To: rfc-info@RFC-EDITOR.ORG
        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 RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.