[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

I-D ACTION:draft-ietf-mboned-glop-update-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the MBONE Deployment Working Group of the IETF.

	Title		: GLOP Addressing in 233/8
	Author(s)	: D. Meyer, P. Lothberg
	Filename	: draft-ietf-mboned-glop-update-00.txt
	Pages		: 5
	Date		: 13-Aug-01
This describes a policy for use of the class D address space using
233/8 as the statically assigned subset of the class D address space.
This space is generally to be utilized for many to many applications,
such as non-broadcast applications.  This allocation is in addition
to those described on [IANA] (e.g. [RFC2365]). The IANA has allocated
223/8 as per RFC 2770 [RFC2770]. This document updates RFC 2770.
This memo is a product of the Multicast  Deployment Working Group
(MBONED) in the Operations and Management Area of the Internet
Engineering Task Force. Submit comments to <mboned@ns.uoregon.edu> or
the author.

A URL for this Internet-Draft is:

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-mboned-glop-update-00.txt".

A list of Internet-Drafts directories can be found in
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
In the body type:
	"FILE /internet-drafts/draft-ietf-mboned-glop-update-00.txt".
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Content-type: text/plain