Re: Re: 232-Addresses not only for current SSM model

[Hugh Holbrook <holbrook@cisco.com>]

> Doron,
> Can you point out the draft(s) that discuss the Reverse-IGMP?
> 
> Thanks,
> Nagesh

Here you go.

-Hugh

----------------------------------------------------------------
Message-Id: <200102281158.GAA02972@ietf.org>
To: IETF-Announce: ;
Cc: idmr@cs.ucl.ac.uk
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-idmr-msnip-00.txt,.ps
Date: Wed, 28 Feb 2001 06:58:48 -0500

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts
directories.  This draft is a work item of the Inter-Domain Multicast
Routing Working Group of the IETF.

	Title		: Multicast Source Notification of Interest Protocol 
                          (MSNIP)
	Author(s)	: B. Fenner ET AL.
	Filename	: draft-ietf-idmr-msnip-00.txt,.ps
	Pages		: 18
	Date		: 27-Feb-01
	
This document discusses the Multicast Source Interest Notification
Protocol (MSNIP).  MSNIP is an extension to IGMPv3 [1] that provides
membership notification services for sources of multicast traffic.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idmr-msnip-00.txt

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-idmr-msnip-00.txt".

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-idmr-msnip-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.