RE: RFC 2490 on IP Multicast with RSVP

"Osama Aboul-Magd" <osama@nortelnetworks.com> Sun, 31 January 1999 22:18 UTC

Received: from ns.newbridge.com (ns.newbridge.com [192.75.23.67]) by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA05709 for <qosr-archive@odin.ietf.org>; Sun, 31 Jan 1999 17:18:11 -0500 (EST)
Received: (from smtpd@localhost) by ns.newbridge.com (8.8.8/8.6.12) id RAA05415 for qosr-archive@odin.ietf.org; Sun, 31 Jan 1999 17:18:04 -0500 (EST)
Received: from kanata-gw1.newbridge.com(192.75.23.72), claiming to be "kanata-gw1.ca.newbridge.com" via SMTP by ns.newbridge.com, id smtpdXJAa03198; Sun Jan 31 17:16:38 1999
Received: from qmaster.ca.newbridge.com by kanata-mh1.ca.newbridge.com with ESMTP; Sun, 31 Jan 1999 17:13:57 -0500
Received: (from majordom@localhost) by qmaster.ca.newbridge.com. (8.8.8/8.8.8) id RAA14540 for qosr-outgoing; Sun, 31 Jan 1999 17:04:11 -0500 (EST)
Received: from kanata-mh1.ca.newbridge.com (kanata-mh1.ca.newbridge.com [138.120.118.18]) by qmaster.ca.newbridge.com. (8.8.8/8.8.8) with ESMTP id NAA06170 for <qosr@qmaster.ca.newbridge.com>; Thu, 28 Jan 1999 13:26:25 -0500 (EST)
Received: from [138.120.118.69] by kanata-mh1.ca.newbridge.com; Thu, 28 Jan 1999 13:26:23 -0500
Received: from ns.ca.newbridge.com ([192.75.23.67]) by p0rtal-int.ca.newbridge.com via smtpd (for [138.120.118.18]) with SMTP; 28 Jan 1999 18:24:07 UT
Received: (from smtpd@localhost) by ns.newbridge.com (8.8.8/8.6.12) id NAA17748 for qosr@newbridge.com; Thu, 28 Jan 1999 13:26:21 -0500 (EST)
Received: from smtprich.nortel.com(192.135.215.8) via SMTP by ns.newbridge.com, id smtpdAAAa17712; Thu Jan 28 13:26:11 1999
Received: from zrtpd004.us.nortel.com (actually nrtpd004) by smtprich.nortel.com; Thu, 28 Jan 1999 12:24:36 -0600
Received: by zrtpd004.us.nortel.com with Internet Mail Service (5.0.1460.8) id <DZX1W9AG>; Thu, 28 Jan 1999 13:23:59 -0500
Message-Id: <C51ED84B6F47D211917A0000F8BCBD11ADEADC@zcard00g.ca.nortel.com>
From: "Osama Aboul-Magd" <osama@nortelnetworks.com>
To: Mark Pullen <mpullen@bacon.gmu.edu>, qosr@newbridge.com
Subject: RE: RFC 2490 on IP Multicast with RSVP
Date: Thu, 28 Jan 1999 13:23:57 -0500
X-Mailer: Internet Mail Service (5.0.1460.8)
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Sender: qosr-owner@newbridge.com
Precedence: bulk

Mark,

Is there a version of the document where the figures are included.

Regards;

Osama.

		-----Original Message-----
		From:	Mark Pullen [mailto:mpullen@bacon.gmu.edu]
		Sent:	Thursday, January 28, 1999 12:36 PM
		To:	qosr@newbridge.com
		Subject:	RFC 2490 on IP Multicast with RSVP

		----------
		X-Sun-Data-Type: text
		X-Sun-Data-Description: text
		X-Sun-Data-Name: text
		X-Sun-Charset: us-ascii
		X-Sun-Content-Lines: 82


		----- Begin Included Message -----

		From adm@ietf.org Wed Jan 27 19:08:17 1999
		To: IETF-Announce: ;
		Subject: RFC 2490 on IP Multicast with RSVP
		Cc: rfc-ed@ISI.EDU
		Mime-Version: 1.0
		Date: Wed, 27 Jan 1999 14:21:26 -0800
		From: RFC Editor <rfc-ed@ISI.EDU>


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


		        RFC 2490:

		        Title:	    A Simulation Model for IP Multicast with
RSVP
			Author(s):  M. Pullen, R. Malghan, L. Lavu, G. Duan,
J. Ma,
				    H. Nah
			Status:     Informational
			Date:       January 1999
		        Mailbox:    mpullen@gmu.edu, rmalghan@bacon.gmu.edu,

				    llavu@bacon.gmu.edu,
gduan@us.oracle.com,
				    jma@newbridge.com, hnah@bacon.gmu.edu
			Pages:      31
		        Characters: 74936
		        Updates/Obsoletes/See Also: None    
		        I-D Tag:    draft-pullen-ipv4-rsvp-04.txt


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


		This document describes a detailed model of IPv4 multicast
with RSVP
		that has been developed using the OPNET simulation package
[4], with
		protocol procedures defined in the C language.  The model
was
		developed to allow investigation of performance constraints
on routing
		but should have wide applicability in the Internet
multicast/resource
		reservation community.  We are making this model publicly
available
		with the intention that it can be used to provide expanded
studies of
		resource-reserved multicasting.

		This memo provides information for the Internet community.
It 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@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.


		Joyce K. Reynolds and Alegre Ramos
		USC/Information Sciences Institute

		...

		Below is the data which will enable a MIME compliant Mail
Reader 
		implementation to automatically retrieve the ASCII version
		of the RFCs.

		----- End Included Message -----

		----------
		X-Sun-Data-Type: Multipart
		X-Sun-Charset: us-ascii
		X-Sun-Content-Lines: 22

		--OtherAccess
		Content-Type:  Message/External-body;
		        access-type="mail-server";
		        server="RFC-INFO@RFC-EDITOR.ORG"

		Content-Type: text/plain
		Content-ID: <990127141940.RFC@RFC-EDITOR.ORG>

		RETRIEVE: rfc
		DOC-ID: rfc2490

		--OtherAccess
		Content-Type:   Message/External-body;
		        name="rfc2490.txt";
		        site="ftp.isi.edu";
		        access-type="anon-ftp";
		        directory="in-notes"

		Content-Type: text/plain
		Content-ID: <990127141940.RFC@RFC-EDITOR.ORG>

		--OtherAccess--