[ssm] I-D ACTION:draft-ietf-ssm-arch-03.txt

Internet-Drafts@ietf.org Thu, 08 May 2003 19:42 UTC

Received: from www1.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06472 for <ssm-archive@odin.ietf.org>; Thu, 8 May 2003 15:42:25 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h48Jq1E12065 for ssm-archive@odin.ietf.org; Thu, 8 May 2003 15:52:01 -0400
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h48Jq1812062 for <ssm-web-archive@optimus.ietf.org>; Thu, 8 May 2003 15:52:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06441 for <ssm-web-archive@ietf.org>; Thu, 8 May 2003 15:41:54 -0400 (EDT)
Received: from ietf-mx ([]) by ietf-mx with esmtp (Exim 4.12) id 19DrJ7-0005Pg-00 for ssm-web-archive@ietf.org; Thu, 08 May 2003 15:43:57 -0400
Received: from ietf.org ([] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19DrJ7-0005Pd-00 for ssm-web-archive@ietf.org; Thu, 08 May 2003 15:43:57 -0400
Received: from www1.ietf.org (localhost.localdomain []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h48JkS811697; Thu, 8 May 2003 15:46:28 -0400
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h48JjM811660 for <ssm@optimus.ietf.org>; Thu, 8 May 2003 15:45:22 -0400
Received: from CNRI.Reston.VA.US (localhost []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06175; Thu, 8 May 2003 15:35:16 -0400 (EDT)
Message-Id: <200305081935.PAA06175@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: ssm@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Thu, 08 May 2003 15:35:15 -0400
Subject: [ssm] I-D ACTION:draft-ietf-ssm-arch-03.txt
Sender: ssm-admin@ietf.org
Errors-To: ssm-admin@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>, <mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>, <mailto:ssm-request@ietf.org?subject=subscribe>

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

	Title		: Source-Specific Multicast for IP
	Author(s)	: H. Holbrook, B. Cain
	Filename	: draft-ietf-ssm-arch-03.txt
	Pages		: 17
	Date		: 2003-5-8
IP addresses in the 232/8 ( to range are
designated as source-specific multicast (SSM) destination addresses and
are reserved for use by source-specific applications and protocols.  
For IP version 6 (IPv6), the address prefix FF3x::/32 is reserved for
source-specific multicast use.  It defines an extension to the Internet
network service that applies to datagrams sent to SSM addresses and
defines the host and router requirements to support this extension.

A URL for this Internet-Draft is:

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-ssm-arch-03.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-ssm-arch-03.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