From owner-idmr@cs.ucl.ac.uk  Fri Jun  4 14:40:50 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA09577
	for <idmr-archive@ietf.org>; Fri, 4 Jun 1999 14:40:50 -0400 (EDT)
Message-Id: <199906041840.OAA09577@ietf.org>
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.27020-0@pan2.cs.ucl.ac.uk>;
          Fri, 4 Jun 1999 19:40:25 +0100
To: idmr-archive@ietf.org
From: majordomo@cs.ucl.ac.uk
Subject: Welcome to idmr
Reply-To: majordomo@cs.ucl.ac.uk
Date: Fri, 4 Jun 1999 19:40:25 +0100
Sender: owner-idmr@cs.ucl.ac.uk

--

Welcome to the idmr mailing list!

Please save this message for future reference.  Thank you.

If you ever want to remove yourself from this mailing list,
send the following command in email to
<idmr-request@cs.ucl.ac.uk>:

    unsubscribe

Or you can send mail to <majordomo@cs.ucl.ac.uk> with the following
command in the body of your email message:

    unsubscribe idmr

or from another account, besides idmr-archive@ietf.org:

    unsubscribe idmr idmr-archive@ietf.org

If you ever need to get in contact with the owner of the list,
(if you have trouble unsubscribing, or have questions about the
list itself) send email to <owner-idmr@cs.ucl.ac.uk> .
This is the general rule for most mailing lists when you need
to contact a human.


Description
===========
 
This list is for discussion of InterDomain Multicast Routing.



From owner-majordomo@cs.ucl.ac.uk  Fri Jun  4 14:40:51 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA09581
	for <idmr-archive@ietf.org>; Fri, 4 Jun 1999 14:40:51 -0400 (EDT)
Message-Id: <199906041840.OAA09581@ietf.org>
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.27018-0@pan2.cs.ucl.ac.uk>;
          Fri, 4 Jun 1999 19:40:19 +0100
To: idmr-archive@ietf.org
From: majordomo@cs.ucl.ac.uk
Subject: Majordomo results
Reply-To: majordomo@cs.ucl.ac.uk
Date: Fri, 4 Jun 1999 19:40:19 +0100
Sender: owner-majordomo@cs.ucl.ac.uk

--

>>>> subscribe idmr
Succeeded.


From fenner@mango.attlabs.att.com  Fri Jun  4 16:22:42 1999
Received: from mango.attlabs.att.com (gate.ipo.att.com [135.197.57.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10653
	for <idmr-archive@ietf.org>; Fri, 4 Jun 1999 16:22:40 -0400 (EDT)
Received: (from fenner@localhost)
	by mango.attlabs.att.com (8.9.3/8.9.3) id NAA75007
	for idmr-archive@ietf.org; Fri, 4 Jun 1999 13:22:13 -0700 (PDT)
	(envelope-from fenner)
Date: Fri, 4 Jun 1999 13:22:13 -0700 (PDT)
From: Bill Fenner <fenner@research.att.com>
Message-Id: <199906042022.NAA75007@mango.attlabs.att.com>
To: idmr-archive@ietf.org
Subject: test

Don't you just love reading test messages at the beginning
of mailing list archives?

  Bill


From owner-idmr@cs.ucl.ac.uk  Fri Jun  4 18:43:21 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA12378
	for <idmr-archive@lists.ietf.org>; Fri, 4 Jun 1999 18:43:20 -0400 (EDT)
Message-Id: <199906042243.SAA12378@ietf.org>
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.27138-0@pan2.cs.ucl.ac.uk>;
          Fri, 4 Jun 1999 23:42:53 +0100
To: idmr-archive@ietf.org
From: majordomo@cs.ucl.ac.uk
Subject: Welcome to idmr
Reply-To: majordomo@cs.ucl.ac.uk
Date: Fri, 4 Jun 1999 23:42:53 +0100
Sender: owner-idmr@cs.ucl.ac.uk

--

Welcome to the idmr mailing list!

Please save this message for future reference.  Thank you.

If you ever want to remove yourself from this mailing list,
send the following command in email to
<idmr-request@cs.ucl.ac.uk>:

    unsubscribe

Or you can send mail to <majordomo@cs.ucl.ac.uk> with the following
command in the body of your email message:

    unsubscribe idmr

or from another account, besides idmr-archive@lists.ietf.org:

    unsubscribe idmr idmr-archive@lists.ietf.org

If you ever need to get in contact with the owner of the list,
(if you have trouble unsubscribing, or have questions about the
list itself) send email to <owner-idmr@cs.ucl.ac.uk> .
This is the general rule for most mailing lists when you need
to contact a human.


Description
===========
 
This list is for discussion of InterDomain Multicast Routing.



From owner-majordomo@cs.ucl.ac.uk  Fri Jun  4 18:43:22 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA12380
	for <idmr-archive@lists.ietf.org>; Fri, 4 Jun 1999 18:43:21 -0400 (EDT)
Message-Id: <199906042243.SAA12380@ietf.org>
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.27136-0@pan2.cs.ucl.ac.uk>;
          Fri, 4 Jun 1999 23:42:48 +0100
To: idmr-archive@ietf.org
From: majordomo@cs.ucl.ac.uk
Subject: Majordomo results
Reply-To: majordomo@cs.ucl.ac.uk
Date: Fri, 4 Jun 1999 23:42:48 +0100
Sender: owner-majordomo@cs.ucl.ac.uk

--

>>>> subscribe idmr
Succeeded.


From owner-idmr@cs.ucl.ac.uk  Fri Jun  4 21:00:14 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA13481
	for <idmr-archive@ietf.org>; Fri, 4 Jun 1999 21:00:13 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.27116-0@pan2.cs.ucl.ac.uk>;
          Fri, 4 Jun 1999 23:41:27 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.27110-0@pan2.cs.ucl.ac.uk>; Fri, 4 Jun 1999 23:41:23 +0100
Received: from H-135-207-30-103.research.att.com by bells.cs.ucl.ac.uk 
          with Internet SMTP id <g.24325-0@bells.cs.ucl.ac.uk>;
          Fri, 4 Jun 1999 23:41:38 +0100
Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) 
          by mail-green.research.att.com (Postfix) with ESMTP id 286B81E00E 
          for <idmr@cs.ucl.ac.uk>; Fri, 4 Jun 1999 18:41:35 -0400 (EDT)
Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) 
          by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id SAA10988 
          for <idmr@cs.ucl.ac.uk>; Fri, 4 Jun 1999 18:41:34 -0400 (EDT)
From: Bill Fenner <fenner@research.att.com>
Received: (from fenner@localhost) by windsor.research.att.com (8.8.7/8.8.5) 
          id SAA04957; Fri, 4 Jun 1999 18:41:33 -0400 (EDT)
Message-Id: <199906042241.SAA04957@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=19701020; charset=US-ASCII
To: idmr@cs.ucl.ac.uk
Subject: IDMR at the 45th IETF in Oslo
Date: Fri, 4 Jun 1999 15:41:33 -0700
Versions: dmail (solaris) 2.2c/makemail 2.8t
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk


--19701020
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline


IDMR is tenatively scheduled as follows:

	Tuesday, July 13 at 1545-1645
		other groups scheduled at that time: otp, nat, policy

If you would like to present, please send me email.

Please note the new IDMR charter, attached to this message.  It was
agreed to in spirit at the 44th IETF meeting; here's something concrete.

  Bill


--19701020
Content-Type: text/plain; name="idmr-charter"; x-unix-mode=0644
Content-Disposition: attachment; filename="idmr-charter"

Internet-Draft Multicast Remnants (idmr)

Chair:

Bill Fenner <fenner@research.att.com>

Routing Area Director(s): 

David Oran <oran@cisco.com>
Rob Coltun <rcoltun@lightera.com>

Routing Area Advisor: 

Rob Coltun <rcoltun@lightera.com>

Mailing Lists: 

General Discussion:idmr@cs.ucl.ac.uk 
To Subscribe: idmr-request@cs.ucl.ac.uk 
Archive: http://www.jnx.com/~pusateri/idmr

Description of Working Group:

The Internet-Draft Multicast Remnants (idmr) working group is
chartered to finish certain parts of the work started in the
Inter-Domain Multicast Routing (idmr) working group.  The group is
expected to live only long enough to see the existing work items
progress through the standards track, and is not expected to take
on new work items.

The specific work items are:
DVMRP
DVMRP MIB
Domain Wide Reports
IGMP MIB
IGMP Proxying
IGMPv2
IGMPv3
Multicast Interop
Multicast Router Discovery
Multicast Routing MIB
Multicast Traceroute

Goals and Milestones:

July 1999:	First WG meeting with new charter.  Recruit authors
		to help speed specs along.

November 1999:	All specs to at least Proposed Standard.  MIBs may
		lag.

March 2000:	All MIBs to at least Proposed.

July 2000:	Address any spec issues; all documents to Draft if no
		major problems.

November 2000:	All documents to Standard if no major problems.
		Disband WG.

--19701020--


From owner-idmr@cs.ucl.ac.uk  Mon Jun  7 03:10:22 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA17271
	for <idmr-archive@ietf.org>; Mon, 7 Jun 1999 03:10:21 -0400 (EDT)
Message-Id: <199906070710.DAA17271@ietf.org>
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.27539-0@pan2.cs.ucl.ac.uk>;
          Mon, 7 Jun 1999 04:29:37 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.27530-0@pan2.cs.ucl.ac.uk>; Mon, 7 Jun 1999 04:29:32 +0100
Received: from 1Cust186.tnt1.west-palm-beach.fl.da.uu.net by bells.cs.ucl.ac.uk 
          with Internet SMTP id <g.29874-0@bells.cs.ucl.ac.uk>;
          Mon, 7 Jun 1999 04:29:46 +0100
From: web5678 <web5678@pmail.net>
Subject: IF YOU WANT TO EXPLORE A NEW OPPORTUNITY THEN READ THIS AD
Date: Mon, 7 Jun 1999 01:48:36
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Apparently-To: idmr-pp

Have you been DOWNSIZED, RIGHTSIZED or just plain CAPSIZED?

Would an opportunity that allows you to start your own business, 
be your own boss, work your own hours, take part in the growth of 
a dynamic health care product manufacturer be of interest to you?

Let me show you how others like myself have brought balance into 
their lives.

For free information please contact:

Jim

Whelan Industries
1800 636 6773 ext 6834

to be removed e mail web567@pmail.net
 
 
 
 
 
 
 
 
 
 
 


From owner-idmr@cs.ucl.ac.uk  Mon Jun  7 03:10:35 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA17285
	for <idmr-archive@lists.ietf.org>; Mon, 7 Jun 1999 03:10:35 -0400 (EDT)
Message-Id: <199906070710.DAA17285@ietf.org>
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.27539-0@pan2.cs.ucl.ac.uk>;
          Mon, 7 Jun 1999 04:29:37 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.27530-0@pan2.cs.ucl.ac.uk>; Mon, 7 Jun 1999 04:29:32 +0100
Received: from 1Cust186.tnt1.west-palm-beach.fl.da.uu.net by bells.cs.ucl.ac.uk 
          with Internet SMTP id <g.29874-0@bells.cs.ucl.ac.uk>;
          Mon, 7 Jun 1999 04:29:46 +0100
From: web5678 <web5678@pmail.net>
Subject: IF YOU WANT TO EXPLORE A NEW OPPORTUNITY THEN READ THIS AD
Date: Mon, 7 Jun 1999 01:48:36
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Apparently-To: idmr-pp

Have you been DOWNSIZED, RIGHTSIZED or just plain CAPSIZED?

Would an opportunity that allows you to start your own business, 
be your own boss, work your own hours, take part in the growth of 
a dynamic health care product manufacturer be of interest to you?

Let me show you how others like myself have brought balance into 
their lives.

For free information please contact:

Jim

Whelan Industries
1800 636 6773 ext 6834

to be removed e mail web567@pmail.net
 
 
 
 
 
 
 
 
 
 
 


From owner-idmr@cs.ucl.ac.uk  Tue Jun  8 22:56:15 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA06502
	for <idmr-archive@ietf.org>; Tue, 8 Jun 1999 22:56:14 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.27861-0@pan2.cs.ucl.ac.uk>;
          Wed, 9 Jun 1999 01:09:54 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.27855-0@pan2.cs.ucl.ac.uk>; Wed, 9 Jun 1999 01:09:50 +0100
Received: from 131.107.1.30 by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.01285-0@bells.cs.ucl.ac.uk>; Wed, 9 Jun 1999 01:10:04 +0100
Received: (from dthaler@localhost) by dthaler.microsoft.com (8.8.7/8.8.7) 
          id SAA20538;
          Tue, 8 Jun 1999 18:53:58 -0700 (PDT) (envelope-from dthaler)
From: Dave Thaler <dthaler@dthaler.microsoft.com>
Message-Id: <199906090153.SAA20538@dthaler.microsoft.com>
Subject: IGMP MIB draft -09
To: idmr@cs.ucl.ac.uk
Date: Tue, 8 Jun 1999 18:53:58 -0700 (PDT)
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

I just submitted draft -09 to address the lastest comments received.
The new version is available at
http://www.eecs.umich.edu/~thalerd/draft-ietf-idmr-igmp-mib-09.txt
Changes are listed below.

-Dave



Changes that affect an existing implementation under the experimental
OID space:

   NONE.  Draft -08 and higher do not apply to the experimental OID space.

Changes that affect an implementation under the future (unassigned) OID space:

1) Fixed DEFVAL of igmpInterfaceQueryMaxResponseTime (pointed out
   by several people)
2) Changed SYNTAX of igmpInterfaceVersion1QuerierTimer, 
   igmpInterfaceQuerierUpTime, igmpInterfaceQuerierExpiryTime, and
   igmpCacheVersion1HostTimer from Integer32 (seconds) to
   TimeTicks (hundredths of a second).  (comment from Bill Fenner)
   
Cosmetic changes that do not affect implementations:

1) Changed SYNTAX of *IfIndex objects from Integer32 to InterfaceIndex
   (comment from Hiroto Shibuya)
2) Clarified DESCRIPTION of igmpCacheExpiryTime to talk about case
   where the router itself is the only member (comment from Mike Tracy)
3) Fixed order of igmpInterfaceLastMembQueryIntvl and
   igmpInterfaceProxyIfIndex in the SEQUENCE to match their OID values,
   previously were listed backwards in the sequence.  (comment from
   Lokesh Srinivas)
4) Mention that value of igmpInterfaceLastMembQueryIntvl is irrelevant
   if igmpInterfaceVersion is version1 (comment from Bill Fenner)
5) Fix DESCRIPTION of igmpInterfaceProxyIfIndex regarding router
   interfaces (also from Bill Fenner)
6) Fix DESCRIPTION of igmpCacheUpTime to say what the object actually
   does (also from Bill Fenner)


From owner-idmr@cs.ucl.ac.uk  Tue Jun  8 22:56:26 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA06513
	for <idmr-archive@lists.ietf.org>; Tue, 8 Jun 1999 22:56:25 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.27861-0@pan2.cs.ucl.ac.uk>;
          Wed, 9 Jun 1999 01:09:54 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.27855-0@pan2.cs.ucl.ac.uk>; Wed, 9 Jun 1999 01:09:50 +0100
Received: from 131.107.1.30 by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.01285-0@bells.cs.ucl.ac.uk>; Wed, 9 Jun 1999 01:10:04 +0100
Received: (from dthaler@localhost) by dthaler.microsoft.com (8.8.7/8.8.7) 
          id SAA20538;
          Tue, 8 Jun 1999 18:53:58 -0700 (PDT) (envelope-from dthaler)
From: Dave Thaler <dthaler@dthaler.microsoft.com>
Message-Id: <199906090153.SAA20538@dthaler.microsoft.com>
Subject: IGMP MIB draft -09
To: idmr@cs.ucl.ac.uk
Date: Tue, 8 Jun 1999 18:53:58 -0700 (PDT)
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

I just submitted draft -09 to address the lastest comments received.
The new version is available at
http://www.eecs.umich.edu/~thalerd/draft-ietf-idmr-igmp-mib-09.txt
Changes are listed below.

-Dave



Changes that affect an existing implementation under the experimental
OID space:

   NONE.  Draft -08 and higher do not apply to the experimental OID space.

Changes that affect an implementation under the future (unassigned) OID space:

1) Fixed DEFVAL of igmpInterfaceQueryMaxResponseTime (pointed out
   by several people)
2) Changed SYNTAX of igmpInterfaceVersion1QuerierTimer, 
   igmpInterfaceQuerierUpTime, igmpInterfaceQuerierExpiryTime, and
   igmpCacheVersion1HostTimer from Integer32 (seconds) to
   TimeTicks (hundredths of a second).  (comment from Bill Fenner)
   
Cosmetic changes that do not affect implementations:

1) Changed SYNTAX of *IfIndex objects from Integer32 to InterfaceIndex
   (comment from Hiroto Shibuya)
2) Clarified DESCRIPTION of igmpCacheExpiryTime to talk about case
   where the router itself is the only member (comment from Mike Tracy)
3) Fixed order of igmpInterfaceLastMembQueryIntvl and
   igmpInterfaceProxyIfIndex in the SEQUENCE to match their OID values,
   previously were listed backwards in the sequence.  (comment from
   Lokesh Srinivas)
4) Mention that value of igmpInterfaceLastMembQueryIntvl is irrelevant
   if igmpInterfaceVersion is version1 (comment from Bill Fenner)
5) Fix DESCRIPTION of igmpInterfaceProxyIfIndex regarding router
   interfaces (also from Bill Fenner)
6) Fix DESCRIPTION of igmpCacheUpTime to say what the object actually
   does (also from Bill Fenner)


From owner-idmr@cs.ucl.ac.uk  Thu Jun 10 00:34:08 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA10741
	for <idmr-archive@ietf.org>; Thu, 10 Jun 1999 00:34:06 -0400 (EDT)
Message-Id: <199906100434.AAA10741@ietf.org>
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.28021-0@pan2.cs.ucl.ac.uk>;
          Thu, 10 Jun 1999 02:14:15 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.28015-0@pan2.cs.ucl.ac.uk>; Thu, 10 Jun 1999 02:14:11 +0100
Received: from 06-064.015.popsite.net by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.03387-0@bells.cs.ucl.ac.uk>; Thu, 10 Jun 1999 02:14:26 +0100
From: search-engine <search-engine@kincom.com>
Subject: Search Engine Insurance
Date: Wed, 9 Jun 1999 14:33:37
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Apparently-To: idmr-pp

"Search Engine Insurance" is now "Search Engine Loss Prevention"

Search engines are beginning their move to give larger business 
an advantage over smaller businesses on their front positions. It 
was just a matter of time until greed and big money took over the 
major search engines. Small businesses and new business will 
suffer dramatic drops in their positions as the new search 
engine's selection system goes into full operation. "Search 
Engine Loss Prevention" can protect you from the new Search 
Engine's Attack on Small Businesses top placement. 

Only "SEARCH ENGINE LOSS PREVENTION" can help small business 
survive. (Continued) 

***********************************************
THIS IS INTENDED TO BE A SINGLE TIME HIGHLY SELECTIVE SENDING by 
our server.
We apologize to any Washington State Resident or Business 
receiving this letter. We will remove Washington addresses as 
fast as we find or receive them. See bottom for removals.
************************************************

"SEARCH ENGINE LOSS PREVENTION" (Continued)

You, as a small business owner, should know that many search 
engines are now favoring large businesses for their first, 
second, and third page positions. They are rapidly switching to 
"popularity rating" as their method of choice for top positions. 
Only "Search Engine Loss Prevention" can help protect you from 
potentially loosing your Internet business in the future.

A quote by David Pritchard director of HotBot tells the sad 
truth: "Direct Hit is a system that measures what pages users 
select from search results and roughly how long they spend 
visiting these pages. In a very simplistic explanation, the more 
"popular" pages as measured by these factors rise to the top of 
the list. HotBot had allowed users to view Direct Hit results in 
the form of a "Top 10" option that was presented along with 
Inktomi-powered results". 

This method of choosing the first positions will soon be applied 
universally by all the major search engines. Yahoo just announced 
a new policy of charging for "submission inspections" with no 
guarantee of any position placement. 

In light of these methods of choosing the businesses placed in 
the search engine's best positions by giving an unfair advantage 
to the major businesses, you can be certain that all small 
businesses will suffer drastically. Many will loose their 
business and income. 

"Search Engine Loss Prevention" can help protect your investment 
by keeping your hits up via our satellite sites. Twenty-four 
satellite sites assigned to your business will shoot hits 
directly at your site to increase your "popularity rating" 
dramatically. The higher your "popularity rating" the higher your 
search engine ranking and the better your search engine position. 
As an added benefit, the extra hits from our satellites should 
rapidly increase your sales.

If the search engines new "popularity rating" method of choosing 
priority positions gives big money and big business the advantage 
then what will become of the small businesses on the internet? 
Newspapers, radio and television charge big bucks for their ads. 
The search engines are now following suit. Only "Search Engine 
Loss Prevention" can help you survive this attack against your 
security. In fact, with "Search Engine Loss Prevention" on your 
side, you may actually benefit from the new search engine changes 
because your competition will most likely slowly disappear 
leaving you with a larger share of the market. 

"Search Engine Loss Prevention" is now offering 3 months of Loss 
Prevention absolutely FREE to show you the value of a high 
"popularity rating". (You pay only the set-up costs.) After the 3 
months, you will pay only a low monthly premium to protect your 
business from this unfair attack against you, the small business 
owner. 

Openings are extremely limited. The Loss Prevention is Free for 3 
months. You pay only the setup cost. Call today to find out more 
about an essential service that you can not afford to be without. 
That is if you want to excel in this onslaught by the search 
engines. 
 
 FOLLOW THESE THREE STEPS TO RECEIVE FREEE "SEARCH ENGINE LOSS 
PREVENTION" for 3 months. (you pay only the set-up costs)

STEP ONE: CALL Search Engine Loss Prevention at: 805 647 9275, 
fax to 805 647 6871 or e-mail to search-engine@ 
internationalcommerce.com. The phone is the preferred method 
because e-mail may fail due to circumstances beyond our control. 
Be prepared to give your name, URL, E-mail address and phone 
number.

STEP TWO: We will evaluate your site. We do this at no charge of 
course. We reserve the right to refuse service for any reason 
including but not limited to selling any product or service that 
we consider damaging to our reputation.

STEP THREE: We will call you back with our evaluation of your 
site and discuss how we can protect and benefit you.

CALL "SEARCH ENGINE LOSS PREVENTION" TODAY and BE PROTECTED 
TOMMORROW!! 
805 647 9275

We will guard your site like the "Marines" guard our country.

Call 805 647 9275. 

********************SENT BY "OUR SERVER"******************** 
Remove: Call 805 647 9275, fax to 805 647-6871, or write remove 
and e-mail to search-engine@internationalcommerce.com, or fax to 
805 647-6871. Fax or phone is the preferred method. Electronic 
mail sometimes fails due to conditions beyond our control. The 
purpose of this letter is to offer " first page search engine 
Loss Prevention". 1672 San Joaquin, Ventura, CA.  93004
 ------------------------------------------------


 
 
 
 
 
 
 
 
 
 


From owner-idmr@cs.ucl.ac.uk  Thu Jun 10 00:34:23 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA10753
	for <idmr-archive@lists.ietf.org>; Thu, 10 Jun 1999 00:34:21 -0400 (EDT)
Message-Id: <199906100434.AAA10753@ietf.org>
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.28021-0@pan2.cs.ucl.ac.uk>;
          Thu, 10 Jun 1999 02:14:15 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.28015-0@pan2.cs.ucl.ac.uk>; Thu, 10 Jun 1999 02:14:11 +0100
Received: from 06-064.015.popsite.net by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.03387-0@bells.cs.ucl.ac.uk>; Thu, 10 Jun 1999 02:14:26 +0100
From: search-engine <search-engine@kincom.com>
Subject: Search Engine Insurance
Date: Wed, 9 Jun 1999 14:33:37
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Apparently-To: idmr-pp

"Search Engine Insurance" is now "Search Engine Loss Prevention"

Search engines are beginning their move to give larger business 
an advantage over smaller businesses on their front positions. It 
was just a matter of time until greed and big money took over the 
major search engines. Small businesses and new business will 
suffer dramatic drops in their positions as the new search 
engine's selection system goes into full operation. "Search 
Engine Loss Prevention" can protect you from the new Search 
Engine's Attack on Small Businesses top placement. 

Only "SEARCH ENGINE LOSS PREVENTION" can help small business 
survive. (Continued) 

***********************************************
THIS IS INTENDED TO BE A SINGLE TIME HIGHLY SELECTIVE SENDING by 
our server.
We apologize to any Washington State Resident or Business 
receiving this letter. We will remove Washington addresses as 
fast as we find or receive them. See bottom for removals.
************************************************

"SEARCH ENGINE LOSS PREVENTION" (Continued)

You, as a small business owner, should know that many search 
engines are now favoring large businesses for their first, 
second, and third page positions. They are rapidly switching to 
"popularity rating" as their method of choice for top positions. 
Only "Search Engine Loss Prevention" can help protect you from 
potentially loosing your Internet business in the future.

A quote by David Pritchard director of HotBot tells the sad 
truth: "Direct Hit is a system that measures what pages users 
select from search results and roughly how long they spend 
visiting these pages. In a very simplistic explanation, the more 
"popular" pages as measured by these factors rise to the top of 
the list. HotBot had allowed users to view Direct Hit results in 
the form of a "Top 10" option that was presented along with 
Inktomi-powered results". 

This method of choosing the first positions will soon be applied 
universally by all the major search engines. Yahoo just announced 
a new policy of charging for "submission inspections" with no 
guarantee of any position placement. 

In light of these methods of choosing the businesses placed in 
the search engine's best positions by giving an unfair advantage 
to the major businesses, you can be certain that all small 
businesses will suffer drastically. Many will loose their 
business and income. 

"Search Engine Loss Prevention" can help protect your investment 
by keeping your hits up via our satellite sites. Twenty-four 
satellite sites assigned to your business will shoot hits 
directly at your site to increase your "popularity rating" 
dramatically. The higher your "popularity rating" the higher your 
search engine ranking and the better your search engine position. 
As an added benefit, the extra hits from our satellites should 
rapidly increase your sales.

If the search engines new "popularity rating" method of choosing 
priority positions gives big money and big business the advantage 
then what will become of the small businesses on the internet? 
Newspapers, radio and television charge big bucks for their ads. 
The search engines are now following suit. Only "Search Engine 
Loss Prevention" can help you survive this attack against your 
security. In fact, with "Search Engine Loss Prevention" on your 
side, you may actually benefit from the new search engine changes 
because your competition will most likely slowly disappear 
leaving you with a larger share of the market. 

"Search Engine Loss Prevention" is now offering 3 months of Loss 
Prevention absolutely FREE to show you the value of a high 
"popularity rating". (You pay only the set-up costs.) After the 3 
months, you will pay only a low monthly premium to protect your 
business from this unfair attack against you, the small business 
owner. 

Openings are extremely limited. The Loss Prevention is Free for 3 
months. You pay only the setup cost. Call today to find out more 
about an essential service that you can not afford to be without. 
That is if you want to excel in this onslaught by the search 
engines. 
 
 FOLLOW THESE THREE STEPS TO RECEIVE FREEE "SEARCH ENGINE LOSS 
PREVENTION" for 3 months. (you pay only the set-up costs)

STEP ONE: CALL Search Engine Loss Prevention at: 805 647 9275, 
fax to 805 647 6871 or e-mail to search-engine@ 
internationalcommerce.com. The phone is the preferred method 
because e-mail may fail due to circumstances beyond our control. 
Be prepared to give your name, URL, E-mail address and phone 
number.

STEP TWO: We will evaluate your site. We do this at no charge of 
course. We reserve the right to refuse service for any reason 
including but not limited to selling any product or service that 
we consider damaging to our reputation.

STEP THREE: We will call you back with our evaluation of your 
site and discuss how we can protect and benefit you.

CALL "SEARCH ENGINE LOSS PREVENTION" TODAY and BE PROTECTED 
TOMMORROW!! 
805 647 9275

We will guard your site like the "Marines" guard our country.

Call 805 647 9275. 

********************SENT BY "OUR SERVER"******************** 
Remove: Call 805 647 9275, fax to 805 647-6871, or write remove 
and e-mail to search-engine@internationalcommerce.com, or fax to 
805 647-6871. Fax or phone is the preferred method. Electronic 
mail sometimes fails due to conditions beyond our control. The 
purpose of this letter is to offer " first page search engine 
Loss Prevention". 1672 San Joaquin, Ventura, CA.  93004
 ------------------------------------------------


 
 
 
 
 
 
 
 
 
 


From owner-idmr@cs.ucl.ac.uk  Thu Jun 10 11:09:07 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA29483
	for <idmr-archive@ietf.org>; Thu, 10 Jun 1999 11:09:04 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.28152-0@pan2.cs.ucl.ac.uk>;
          Thu, 10 Jun 1999 12:20:12 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.28146-0@pan2.cs.ucl.ac.uk>; Thu, 10 Jun 1999 12:20:08 +0100
Received: from odin.ietf.org by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.16107-0@bells.cs.ucl.ac.uk>; Thu, 10 Jun 1999 12:20:22 +0100
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) 
          by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25836;
          Thu, 10 Jun 1999 07:20:18 -0400 (EDT)
Message-Id: <199906101120.HAA25836@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
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-igmp-mib-09.txt
Date: Thu, 10 Jun 1999 07:20:17 -0400
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

--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		: Internet Group Management Protocol MIB
	Author(s)	: K. McCloghrie, D. Farinacci, D. Thaler
	Filename	: draft-ietf-idmr-igmp-mib-09.txt
	Pages		: 21
	Date		: 09-Jun-99
	
This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.  In
particular, it describes objects used for managing the Internet Group
Management Protocol (IGMP).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idmr-igmp-mib-09.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-igmp-mib-09.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-igmp-mib-09.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
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<19990609084246.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idmr-igmp-mib-09.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-idmr-igmp-mib-09.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990609084246.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-idmr@cs.ucl.ac.uk  Thu Jun 10 11:09:42 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA29501
	for <idmr-archive@lists.ietf.org>; Thu, 10 Jun 1999 11:09:39 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.28152-0@pan2.cs.ucl.ac.uk>;
          Thu, 10 Jun 1999 12:20:12 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.28146-0@pan2.cs.ucl.ac.uk>; Thu, 10 Jun 1999 12:20:08 +0100
Received: from odin.ietf.org by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.16107-0@bells.cs.ucl.ac.uk>; Thu, 10 Jun 1999 12:20:22 +0100
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) 
          by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25836;
          Thu, 10 Jun 1999 07:20:18 -0400 (EDT)
Message-Id: <199906101120.HAA25836@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
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-igmp-mib-09.txt
Date: Thu, 10 Jun 1999 07:20:17 -0400
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

--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		: Internet Group Management Protocol MIB
	Author(s)	: K. McCloghrie, D. Farinacci, D. Thaler
	Filename	: draft-ietf-idmr-igmp-mib-09.txt
	Pages		: 21
	Date		: 09-Jun-99
	
This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.  In
particular, it describes objects used for managing the Internet Group
Management Protocol (IGMP).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idmr-igmp-mib-09.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-igmp-mib-09.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-igmp-mib-09.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
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<19990609084246.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idmr-igmp-mib-09.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-idmr-igmp-mib-09.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990609084246.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-idmr@cs.ucl.ac.uk  Fri Jun 11 14:51:39 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA05728
	for <idmr-archive@ietf.org>; Fri, 11 Jun 1999 14:51:37 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.28365-0@pan2.cs.ucl.ac.uk>;
          Fri, 11 Jun 1999 16:50:00 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.28359-0@pan2.cs.ucl.ac.uk>; Fri, 11 Jun 1999 16:49:56 +0100
Received: from mail2.cai.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.04628-0@bells.cs.ucl.ac.uk>; Fri, 11 Jun 1999 16:50:12 +0100
Received: by usilms18.cai.com with Internet Mail Service (5.5.2232.9) 
          id <M37D04R0>; Fri, 11 Jun 1999 11:49:55 -0400
Message-ID: <63710DFC8A24D111BD8B00805F85CA6C02D8F19A@usilmsp1.cai.com>
From: "Ho, Hsin" <Hsin.Ho@CAI.COM>
To: idmr@cs.ucl.ac.uk
Subject: CBT 3 examples
Date: Fri, 11 Jun 1999 11:49:55 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

Hi all, I am just confuse about an example in the CBT v3.01 protocol specs.
I need some help getting it clear.

	core
	  |
	  |
	  R
	  |
	  |
	 BR

"Assume in figure 2 BR has instantiated a priori (*, Core) state between
itself and the core. It subsequently wishes to prune (*, G) from (*, Core)
so sends a (*, G) QUIT_NOTIFICATION upstream. When the quit (prune) reaches
router R, R already has less specific state (i.e. (*, Core)), but this quit
message results in its only child interface (leading to BR) being marked as
pruned under newly instan- tiated (*, G) state. Since router R has no other
child under either (*, Core) or (*, G) states, R can forward the received
(*, G) quit. " 
......
"Returning to the example used with figure 2 above, when router R receives
the (*, G) quit sent by BR and instantiates the correspond- ing state, R can
send a (*, G) quit upstream since there are no less specific entries with
_other_ non-pruned children. However, the (*, G) state in R cannot be
removed despite all (*, G) children being pruned (in this e.g. there is only
one child) because a less specific (i.e. (*, Core)) cache entry exists with
a non-pruned child."

1) What about the only child in the (*, Core) ? I thought each entry is
independent even though (*, G) copied the child interface from (*, Core).
(*, Core) child interface entry is non-pruned in its forwarding entry, even
if  (*, G) marked its child interface as pruned. (*, G) quit should not be
forwarded in the first place since (*, Core) is less specific and has a
non-pruned child, right? 

2) If the entries are not independent then the second example " because a
less specific (i.e. (*, Core)) cache entry exists with a non-pruned child."
is kind of confusing. I thought that in the first example it said that the
child was pruned "R has no other child under either (*, Core) or (*, G)
states".  In the second it said that the child was not pruned, so a less
specific entry still exist with a non-pruned child why forward the quit msg?
So is the forwarding cache

a. (*, Core) pointing to BR 
b. (*, G) pointing to BR (pruned)

Bunches of thanks in advance.


From owner-idmr@cs.ucl.ac.uk  Fri Jun 11 14:51:59 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA05744
	for <idmr-archive@lists.ietf.org>; Fri, 11 Jun 1999 14:51:57 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.28365-0@pan2.cs.ucl.ac.uk>;
          Fri, 11 Jun 1999 16:50:00 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.28359-0@pan2.cs.ucl.ac.uk>; Fri, 11 Jun 1999 16:49:56 +0100
Received: from mail2.cai.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.04628-0@bells.cs.ucl.ac.uk>; Fri, 11 Jun 1999 16:50:12 +0100
Received: by usilms18.cai.com with Internet Mail Service (5.5.2232.9) 
          id <M37D04R0>; Fri, 11 Jun 1999 11:49:55 -0400
Message-ID: <63710DFC8A24D111BD8B00805F85CA6C02D8F19A@usilmsp1.cai.com>
From: "Ho, Hsin" <Hsin.Ho@CAI.COM>
To: idmr@cs.ucl.ac.uk
Subject: CBT 3 examples
Date: Fri, 11 Jun 1999 11:49:55 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

Hi all, I am just confuse about an example in the CBT v3.01 protocol specs.
I need some help getting it clear.

	core
	  |
	  |
	  R
	  |
	  |
	 BR

"Assume in figure 2 BR has instantiated a priori (*, Core) state between
itself and the core. It subsequently wishes to prune (*, G) from (*, Core)
so sends a (*, G) QUIT_NOTIFICATION upstream. When the quit (prune) reaches
router R, R already has less specific state (i.e. (*, Core)), but this quit
message results in its only child interface (leading to BR) being marked as
pruned under newly instan- tiated (*, G) state. Since router R has no other
child under either (*, Core) or (*, G) states, R can forward the received
(*, G) quit. " 
......
"Returning to the example used with figure 2 above, when router R receives
the (*, G) quit sent by BR and instantiates the correspond- ing state, R can
send a (*, G) quit upstream since there are no less specific entries with
_other_ non-pruned children. However, the (*, G) state in R cannot be
removed despite all (*, G) children being pruned (in this e.g. there is only
one child) because a less specific (i.e. (*, Core)) cache entry exists with
a non-pruned child."

1) What about the only child in the (*, Core) ? I thought each entry is
independent even though (*, G) copied the child interface from (*, Core).
(*, Core) child interface entry is non-pruned in its forwarding entry, even
if  (*, G) marked its child interface as pruned. (*, G) quit should not be
forwarded in the first place since (*, Core) is less specific and has a
non-pruned child, right? 

2) If the entries are not independent then the second example " because a
less specific (i.e. (*, Core)) cache entry exists with a non-pruned child."
is kind of confusing. I thought that in the first example it said that the
child was pruned "R has no other child under either (*, Core) or (*, G)
states".  In the second it said that the child was not pruned, so a less
specific entry still exist with a non-pruned child why forward the quit msg?
So is the forwarding cache

a. (*, Core) pointing to BR 
b. (*, G) pointing to BR (pruned)

Bunches of thanks in advance.


From owner-idmr@cs.ucl.ac.uk  Fri Jun 11 14:52:29 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA05755
	for <idmr-archive@lists.ietf.org>; Fri, 11 Jun 1999 14:52:27 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.28402-0@pan2.cs.ucl.ac.uk>;
          Fri, 11 Jun 1999 19:30:04 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.28396-0@pan2.cs.ucl.ac.uk>; Fri, 11 Jun 1999 19:30:00 +0100
Received: from shultz.argon.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.14210-0@bells.cs.ucl.ac.uk>; Fri, 11 Jun 1999 19:30:11 +0100
Received: from zeppo (zeppo [208.234.161.96]) by shultz.argon.com (8.8.6/8.8.6) 
          with ESMTP id OAA01158; Fri, 11 Jun 1999 14:30:09 -0400 (EDT)
Received: (from zzhang@localhost) by zeppo (SMI-8.6/8.7.2) id OAA18897;
          Fri, 11 Jun 1999 14:30:09 -0400
Date: Fri, 11 Jun 1999 14:30:09 -0400
Message-Id: <199906111830.OAA18897@zeppo>
From: Jeffrey Zhang <zzhang@argon.com>
To: Hsin.Ho@CAI.COM
CC: idmr@cs.ucl.ac.uk
In-reply-to: <63710DFC8A24D111BD8B00805F85CA6C02D8F19A@usilmsp1.cai.com> (Hsin.Ho@CAI.COM)
Subject: Re: CBT 3 examples
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk


> 
> Hi all, I am just confuse about an example in the CBT v3.01 protocol specs.
> I need some help getting it clear.
> 
> 	core
> 	  |
> 	  |
> 	  R
> 	  |
> 	  |
> 	 BR
> 
> "Assume in figure 2 BR has instantiated a priori (*, Core) state between
> itself and the core. It subsequently wishes to prune (*, G) from (*, Core)
> so sends a (*, G) QUIT_NOTIFICATION upstream. When the quit (prune) reaches
> router R, R already has less specific state (i.e. (*, Core)), but this quit
> message results in its only child interface (leading to BR) being marked as
> pruned under newly instan- tiated (*, G) state. Since router R has no other
> child under either (*, Core) or (*, G) states, R can forward the received
> (*, G) quit. " 
> ......
> "Returning to the example used with figure 2 above, when router R receives
> the (*, G) quit sent by BR and instantiates the correspond- ing state, R can
> send a (*, G) quit upstream since there are no less specific entries with
> _other_ non-pruned children. However, the (*, G) state in R cannot be
> removed despite all (*, G) children being pruned (in this e.g. there is only
> one child) because a less specific (i.e. (*, Core)) cache entry exists with
> a non-pruned child."
> 
> 1) What about the only child in the (*, Core) ? I thought each entry is
> independent even though (*, G) copied the child interface from (*, Core).
> (*, Core) child interface entry is non-pruned in its forwarding entry, even
> if  (*, G) marked its child interface as pruned. (*, G) quit should not be
> forwarded in the first place since (*, Core) is less specific and has a
> non-pruned child, right? 

The only child in the (*, core) entry is BR.

The fact that R received the (*, G) quit from BR, and the fact that the
(*, core) entry on R only has one child BR indicate that there is
no receiver for group G beyond R. Therefore, R can forward
the quit notification further upstream. If, however, R has another child
BR2 in its (*, core) entry, then it should not forward the (*, G) quit,
otherwise BR2 will not get (*, G) traffic.

> 
> 2) If the entries are not independent then the second example " because a
> less specific (i.e. (*, Core)) cache entry exists with a non-pruned
> child."

note the entry is (*, core) - it indeed has a non-pruned child BR.

> is kind of confusing. I thought that in the first example it said that the
> child was pruned "R has no other child under either (*, Core) or (*,
> G)

note for (*, G), the child is indeed pruned.

> states".  In the second it said that the child was not pruned, so a less
> specific entry still exist with a non-pruned child why forward the quit msg?

the quit message if for (*, G), not for the less specific (*, core).

> So is the forwarding cache
> 
> a. (*, Core) pointing to BR 
> b. (*, G) pointing to BR (pruned)

Yes.

> 
> Bunches of thanks in advance.
> 


Jeffrey


From owner-idmr@cs.ucl.ac.uk  Fri Jun 11 14:52:56 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA05777
	for <idmr-archive@ietf.org>; Fri, 11 Jun 1999 14:52:53 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.28402-0@pan2.cs.ucl.ac.uk>;
          Fri, 11 Jun 1999 19:30:04 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.28396-0@pan2.cs.ucl.ac.uk>; Fri, 11 Jun 1999 19:30:00 +0100
Received: from shultz.argon.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.14210-0@bells.cs.ucl.ac.uk>; Fri, 11 Jun 1999 19:30:11 +0100
Received: from zeppo (zeppo [208.234.161.96]) by shultz.argon.com (8.8.6/8.8.6) 
          with ESMTP id OAA01158; Fri, 11 Jun 1999 14:30:09 -0400 (EDT)
Received: (from zzhang@localhost) by zeppo (SMI-8.6/8.7.2) id OAA18897;
          Fri, 11 Jun 1999 14:30:09 -0400
Date: Fri, 11 Jun 1999 14:30:09 -0400
Message-Id: <199906111830.OAA18897@zeppo>
From: Jeffrey Zhang <zzhang@argon.com>
To: Hsin.Ho@CAI.COM
CC: idmr@cs.ucl.ac.uk
In-reply-to: <63710DFC8A24D111BD8B00805F85CA6C02D8F19A@usilmsp1.cai.com> (Hsin.Ho@CAI.COM)
Subject: Re: CBT 3 examples
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk


> 
> Hi all, I am just confuse about an example in the CBT v3.01 protocol specs.
> I need some help getting it clear.
> 
> 	core
> 	  |
> 	  |
> 	  R
> 	  |
> 	  |
> 	 BR
> 
> "Assume in figure 2 BR has instantiated a priori (*, Core) state between
> itself and the core. It subsequently wishes to prune (*, G) from (*, Core)
> so sends a (*, G) QUIT_NOTIFICATION upstream. When the quit (prune) reaches
> router R, R already has less specific state (i.e. (*, Core)), but this quit
> message results in its only child interface (leading to BR) being marked as
> pruned under newly instan- tiated (*, G) state. Since router R has no other
> child under either (*, Core) or (*, G) states, R can forward the received
> (*, G) quit. " 
> ......
> "Returning to the example used with figure 2 above, when router R receives
> the (*, G) quit sent by BR and instantiates the correspond- ing state, R can
> send a (*, G) quit upstream since there are no less specific entries with
> _other_ non-pruned children. However, the (*, G) state in R cannot be
> removed despite all (*, G) children being pruned (in this e.g. there is only
> one child) because a less specific (i.e. (*, Core)) cache entry exists with
> a non-pruned child."
> 
> 1) What about the only child in the (*, Core) ? I thought each entry is
> independent even though (*, G) copied the child interface from (*, Core).
> (*, Core) child interface entry is non-pruned in its forwarding entry, even
> if  (*, G) marked its child interface as pruned. (*, G) quit should not be
> forwarded in the first place since (*, Core) is less specific and has a
> non-pruned child, right? 

The only child in the (*, core) entry is BR.

The fact that R received the (*, G) quit from BR, and the fact that the
(*, core) entry on R only has one child BR indicate that there is
no receiver for group G beyond R. Therefore, R can forward
the quit notification further upstream. If, however, R has another child
BR2 in its (*, core) entry, then it should not forward the (*, G) quit,
otherwise BR2 will not get (*, G) traffic.

> 
> 2) If the entries are not independent then the second example " because a
> less specific (i.e. (*, Core)) cache entry exists with a non-pruned
> child."

note the entry is (*, core) - it indeed has a non-pruned child BR.

> is kind of confusing. I thought that in the first example it said that the
> child was pruned "R has no other child under either (*, Core) or (*,
> G)

note for (*, G), the child is indeed pruned.

> states".  In the second it said that the child was not pruned, so a less
> specific entry still exist with a non-pruned child why forward the quit msg?

the quit message if for (*, G), not for the less specific (*, core).

> So is the forwarding cache
> 
> a. (*, Core) pointing to BR 
> b. (*, G) pointing to BR (pruned)

Yes.

> 
> Bunches of thanks in advance.
> 


Jeffrey


From owner-idmr@cs.ucl.ac.uk  Mon Jun 14 16:32:31 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA22092
	for <idmr-archive@ietf.org>; Mon, 14 Jun 1999 16:32:29 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.28904-0@pan2.cs.ucl.ac.uk>;
          Mon, 14 Jun 1999 21:09:50 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.28898-0@pan2.cs.ucl.ac.uk>; Mon, 14 Jun 1999 21:09:46 +0100
Received: from host-209-214-128-184.jax.bellsouth.net by bells.cs.ucl.ac.uk 
          with Internet SMTP id <g.17814-0@bells.cs.ucl.ac.uk>;
          Mon, 14 Jun 1999 21:10:01 +0100
From: knowhowtodo <knowhowtodo@rocketmail.com>
Subject: A gentle invitation
Date: Tue, 15 Jun 1999 00:34:34
Message-Id: <368.639817.368138@smtp.callus4more.net.fr>
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Apparently-To: idmr-pp


   LET US DO YOUR BULK E-MAIL ADVERTISING!!!

TIRED OF THE "IN YOUR FACE ADS" (BANNERS)  STATISTICS SHOW 
THEY ARE NOT WORKING.  PEOPLE ARE TIRED OF THE FORCEFUL ADS
EACH AND EVERYTIME THEY CLICK ONTO A SITE.  PUT YOUR AD 
DIRECTLY INTO THEIR MAILBOX, WHERE THEY CAN READ IT AT THEIR
LEISURE.  OUR CLIENTS FIND INDIVIDUAL ADS WORK AND BRING
TRAFFIC TO THEIR SITE MORE THAN ANYTHING ELSE.

THE WAY OF THE FUTURE FOR SUCCESS IN YOUR BUSINESS TODAY!
     **BEST BUY**NON-TARGETED MAILINGS** (WORLD-WIDE)
		  100,000 - $175
        	  1/2 million - $450
		  1 million - $800
		  2 million - $1200		

Let our company do mailing for your product/service, 
newsletter/report, seminar, convention or client list.

Over 71 million addresses on file and NONE were purchased
from other CD's.  We extract our own addresses 7/24.  

     ***Targeted mailings: ***
Why pay $.01 per addresses save LOTS OF $$$, we will mail 
your ad or you can purchase the addresses and do your own 
mailing at your convience: 

$250 - 50,000 addresses extracted and we mail for you
$150 - 25,000 addresses extracted and we mail for you

Purchase the addresses, do your own mailing and save an 
additional 20% off any of our prices.

***SPECIAL*** 1/2 million mailed to .net and .com (US 
addresses only)$750.  A savings of $1250.  

Only fresh addresses are sent.  We extract when an order 
is placed.  We DO NOT use addresses extracted prior to your 
order.

We can extract by country, occupation, organizations, 
associations, product, website/domain, state or megatags 
(keywords).  If we can not search and extract what 
you need, then nobody can.  No one can target your 
mailing for less. 

For the fastest service, cheapest prices and cleanest
mailings call our processing and new accounts department
at 904-282-0945, Monday - Friday.  We have been serving our 
clients since February, 1997.

Unlike other bulk mailers, you get what you pay for.  Many
other bulk mailers DO NOT send out the amount of emails
you pay, but we send 10% more than ordered.  If you want a
copy of the addresses, they can be purchased for an additional
$50.  Then if you want to follow up with another mailing, you
can do it yourself.  Or if you want us to do a 2nd mailing to
the same addresses, the cost is 1/2 of the original cost.  
Give us a call for more details.


====================================================
Under Bill s.1618 TITLE III by the 105th U.S. Congress committee
this letter can not be considered spam as long as we include:
Contact information & a Remove Link
To have your name removed please go to bring_info@usa.net.
====================================================
Sender does not accept registered mail.
GWH 
950-23 Blanding Boulevard, Suite 113
Orange Park, Florida 32065
 
 
 
 
 
 
 
 


From owner-idmr@cs.ucl.ac.uk  Mon Jun 14 16:32:48 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA22112
	for <idmr-archive@lists.ietf.org>; Mon, 14 Jun 1999 16:32:46 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.28904-0@pan2.cs.ucl.ac.uk>;
          Mon, 14 Jun 1999 21:09:50 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.28898-0@pan2.cs.ucl.ac.uk>; Mon, 14 Jun 1999 21:09:46 +0100
Received: from host-209-214-128-184.jax.bellsouth.net by bells.cs.ucl.ac.uk 
          with Internet SMTP id <g.17814-0@bells.cs.ucl.ac.uk>;
          Mon, 14 Jun 1999 21:10:01 +0100
From: knowhowtodo <knowhowtodo@rocketmail.com>
Subject: A gentle invitation
Date: Tue, 15 Jun 1999 00:34:34
Message-Id: <368.639817.368138@smtp.callus4more.net.fr>
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Apparently-To: idmr-pp


   LET US DO YOUR BULK E-MAIL ADVERTISING!!!

TIRED OF THE "IN YOUR FACE ADS" (BANNERS)  STATISTICS SHOW 
THEY ARE NOT WORKING.  PEOPLE ARE TIRED OF THE FORCEFUL ADS
EACH AND EVERYTIME THEY CLICK ONTO A SITE.  PUT YOUR AD 
DIRECTLY INTO THEIR MAILBOX, WHERE THEY CAN READ IT AT THEIR
LEISURE.  OUR CLIENTS FIND INDIVIDUAL ADS WORK AND BRING
TRAFFIC TO THEIR SITE MORE THAN ANYTHING ELSE.

THE WAY OF THE FUTURE FOR SUCCESS IN YOUR BUSINESS TODAY!
     **BEST BUY**NON-TARGETED MAILINGS** (WORLD-WIDE)
		  100,000 - $175
        	  1/2 million - $450
		  1 million - $800
		  2 million - $1200		

Let our company do mailing for your product/service, 
newsletter/report, seminar, convention or client list.

Over 71 million addresses on file and NONE were purchased
from other CD's.  We extract our own addresses 7/24.  

     ***Targeted mailings: ***
Why pay $.01 per addresses save LOTS OF $$$, we will mail 
your ad or you can purchase the addresses and do your own 
mailing at your convience: 

$250 - 50,000 addresses extracted and we mail for you
$150 - 25,000 addresses extracted and we mail for you

Purchase the addresses, do your own mailing and save an 
additional 20% off any of our prices.

***SPECIAL*** 1/2 million mailed to .net and .com (US 
addresses only)$750.  A savings of $1250.  

Only fresh addresses are sent.  We extract when an order 
is placed.  We DO NOT use addresses extracted prior to your 
order.

We can extract by country, occupation, organizations, 
associations, product, website/domain, state or megatags 
(keywords).  If we can not search and extract what 
you need, then nobody can.  No one can target your 
mailing for less. 

For the fastest service, cheapest prices and cleanest
mailings call our processing and new accounts department
at 904-282-0945, Monday - Friday.  We have been serving our 
clients since February, 1997.

Unlike other bulk mailers, you get what you pay for.  Many
other bulk mailers DO NOT send out the amount of emails
you pay, but we send 10% more than ordered.  If you want a
copy of the addresses, they can be purchased for an additional
$50.  Then if you want to follow up with another mailing, you
can do it yourself.  Or if you want us to do a 2nd mailing to
the same addresses, the cost is 1/2 of the original cost.  
Give us a call for more details.


====================================================
Under Bill s.1618 TITLE III by the 105th U.S. Congress committee
this letter can not be considered spam as long as we include:
Contact information & a Remove Link
To have your name removed please go to bring_info@usa.net.
====================================================
Sender does not accept registered mail.
GWH 
950-23 Blanding Boulevard, Suite 113
Orange Park, Florida 32065
 
 
 
 
 
 
 
 


From owner-idmr@cs.ucl.ac.uk  Mon Jun 14 16:32:55 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA22124
	for <idmr-archive@ietf.org>; Mon, 14 Jun 1999 16:32:51 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.28854-0@pan2.cs.ucl.ac.uk>;
          Mon, 14 Jun 1999 18:47:30 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.28848-0@pan2.cs.ucl.ac.uk>; Mon, 14 Jun 1999 18:47:26 +0100
Received: from labinfo.iet.unipi.it by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.11202-0@bells.cs.ucl.ac.uk>; Mon, 14 Jun 1999 18:47:33 +0100
Received: from localhost (luigi@localhost) 
          by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA09910;
          Mon, 14 Jun 1999 17:18:06 +0200
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Message-Id: <199906141518.RAA09910@labinfo.iet.unipi.it>
Subject: CfP: First Intl. Workshop on Networked Group Communication
To: luigi@labinfo.iet.unipi.it (Luigi Rizzo)
Date: Mon, 14 Jun 1999 17:18:05 +0200 (MET DST)
In-Reply-To: <199904011510.RAA16046@labinfo.iet.unipi.it> from "Luigi Rizzo" at Apr 1, 99 05:09:56 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

Just a brief reminder -- the deadline (July 1st) for submissions to the

First International Workshop on Networked Group Communication (NGC99)
		  http://www.iet.unipi.it/~luigi/ngc99/

is approaching. Please note that in addition to regular contributions
we will also select a few "student contributions", authored by
students only.

See the online call for papers at the above URL for detailed info.

	cheers
	luigi
-----------------------------------+-------------------------------------
  Luigi RIZZO, luigi@iet.unipi.it  . Dip. di Ing. dell'Informazione
  http://www.iet.unipi.it/~luigi/  . Universita` di Pisa
  TEL/FAX: +39-050-568.533/522     . via Diotisalvi 2, 56126 PISA (Italy)

		  http://www.iet.unipi.it/~luigi/ngc99/
====  First International Workshop on Networked Group Communication  ====
-----------------------------------+-------------------------------------





From owner-idmr@cs.ucl.ac.uk  Mon Jun 14 16:33:40 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA22143
	for <idmr-archive@lists.ietf.org>; Mon, 14 Jun 1999 16:33:39 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.28854-0@pan2.cs.ucl.ac.uk>;
          Mon, 14 Jun 1999 18:47:30 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.28848-0@pan2.cs.ucl.ac.uk>; Mon, 14 Jun 1999 18:47:26 +0100
Received: from labinfo.iet.unipi.it by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.11202-0@bells.cs.ucl.ac.uk>; Mon, 14 Jun 1999 18:47:33 +0100
Received: from localhost (luigi@localhost) 
          by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA09910;
          Mon, 14 Jun 1999 17:18:06 +0200
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Message-Id: <199906141518.RAA09910@labinfo.iet.unipi.it>
Subject: CfP: First Intl. Workshop on Networked Group Communication
To: luigi@labinfo.iet.unipi.it (Luigi Rizzo)
Date: Mon, 14 Jun 1999 17:18:05 +0200 (MET DST)
In-Reply-To: <199904011510.RAA16046@labinfo.iet.unipi.it> from "Luigi Rizzo" at Apr 1, 99 05:09:56 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

Just a brief reminder -- the deadline (July 1st) for submissions to the

First International Workshop on Networked Group Communication (NGC99)
		  http://www.iet.unipi.it/~luigi/ngc99/

is approaching. Please note that in addition to regular contributions
we will also select a few "student contributions", authored by
students only.

See the online call for papers at the above URL for detailed info.

	cheers
	luigi
-----------------------------------+-------------------------------------
  Luigi RIZZO, luigi@iet.unipi.it  . Dip. di Ing. dell'Informazione
  http://www.iet.unipi.it/~luigi/  . Universita` di Pisa
  TEL/FAX: +39-050-568.533/522     . via Diotisalvi 2, 56126 PISA (Italy)

		  http://www.iet.unipi.it/~luigi/ngc99/
====  First International Workshop on Networked Group Communication  ====
-----------------------------------+-------------------------------------





From owner-majordomo@cs.ucl.ac.uk  Tue Jun 15 17:26:46 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA01025
	for <idmr-archive@ietf.org>; Tue, 15 Jun 1999 17:26:45 -0400 (EDT)
Message-Id: <199906152126.RAA01025@ietf.org>
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.29081-0@pan2.cs.ucl.ac.uk>;
          Tue, 15 Jun 1999 21:47:11 +0100
To: idmr-archive@ietf.org
From: majordomo@cs.ucl.ac.uk
Subject: Majordomo results
Reply-To: majordomo@cs.ucl.ac.uk
Date: Tue, 15 Jun 1999 21:47:11 +0100
Sender: owner-majordomo@cs.ucl.ac.uk

--

>>>> unsubscribe idmr
Succeeded.
>>>> end
END OF COMMANDS


From owner-idmr@cs.ucl.ac.uk  Thu Jun 17 07:56:26 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA26719
	for <idmr-archive@lists.ietf.org>; Thu, 17 Jun 1999 07:56:25 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.29423-0@pan2.cs.ucl.ac.uk>;
          Thu, 17 Jun 1999 09:24:45 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.29417-0@pan2.cs.ucl.ac.uk>; Thu, 17 Jun 1999 09:24:41 +0100
Received: from shuttle.wide.toshiba.co.jp by bells.cs.ucl.ac.uk 
          with Internet SMTP id <g.05356-0@bells.cs.ucl.ac.uk>;
          Thu, 17 Jun 1999 09:24:56 +0100
Received: from localhost (condor.v6.kame.net [3ffe:501:4819:2000:2a0:24ff:fe66:1350]) 
          by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.0) with ESMTP 
          id RAA20209 for <idmr@cs.ucl.ac.uk>;
          Thu, 17 Jun 1999 17:17:32 +0900 (JST)
Date: Thu, 17 Jun 1999 17:27:01 +0900
Message-ID: <14184.45397.190835.4322Q@condor.isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To: idmr@cs.ucl.ac.uk
Subject: PIM SM hash value for IPv6 RP
User-Agent: Wanderlust/2.0.0 (Mmmbop) Emacs/20.3 Mule/4.0 (HANANOEN)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai")
Content-Type: text/plain; charset=US-ASCII
X-Dispatcher: imput version 980905(IM100)
Lines: 30
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

I have a question about hash value calculation for PIM sparse mode.

In section 3.7 of RFC 2362, there is a paragraph about hash value
calculation for IPv6 addresses:

        For address families other than IPv4, a 32-bit digest to be used
        as C_i must first be derived from the actual RP address. Such a
        digest method must be used consistently throughout the PIM
        domain. For IPv6 addresses, we recommend using the equivalent
        IPv4 address for an IPv4-compatible address, and the CRC-32
        checksum [7] of all other IPv6 addresses.

I guess that the above should be applied not only for C_i but for G
and M, right? And if so, we should calculate the CRC checksum after
masking G by M, right? That is, IMO, the hash value for an IPv6
address should be:

   Value(G,M,C(i))=
   (1103515245 * ((1103515245 * crc((G&M))+12345) XOR crc(C(i))) + 12345) mod 2^31

Whether this is correct or not, the specification seems to me a bit
ambiguous on this point. I hope it would be more specific in the next
version.

Thanks,

					JINMEI, Tatuya
					Communication Platform Laboratory
					Corporate R&D Center, Toshiba
					jinmei@isl.rdc.toshiba.co.jp


From owner-idmr@cs.ucl.ac.uk  Thu Jun 17 12:17:01 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA00055
	for <idmr-archive@lists.ietf.org>; Thu, 17 Jun 1999 12:16:59 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.29524-0@pan2.cs.ucl.ac.uk>;
          Thu, 17 Jun 1999 14:24:35 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.29518-0@pan2.cs.ucl.ac.uk>; Thu, 17 Jun 1999 14:24:31 +0100
Received: from maile.surrey.ac.uk by bells.cs.ucl.ac.uk with UK SMTP 
          id <g.22444-0@bells.cs.ucl.ac.uk>; Thu, 17 Jun 1999 14:24:47 +0100
Received: from petra.ee.surrey.ac.uk by maile.surrey.ac.uk with SMTP (PP);
          Thu, 17 Jun 1999 14:24:05 +0100
Date: Thu, 17 Jun 1999 14:24:34 +0100 (BST)
From: Lloyd Wood <L.Wood@surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@surrey.ac.uk>
To: liwen wu <liwenwu@netscape.net>
cc: mpls@UU.NET, idmr@cs.ucl.ac.uk, te-wg@avici.com
Subject: Re: MPLS Multicast Traffic Engineering
In-Reply-To: <19990617131754.1951.qmail@www0l.netaddress.usa.net>
Message-ID: <Pine.SOL.4.02.9906171423100.22094-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-URL: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

Correct URL is:

ftp://ftp.ietf.org/internet-drafts/draft-wu-mpls-multicast-te-00.txt

(if www.ietf.org's Apache was using mod_speling the plural would have
 been caught automagically.)

L.

On 17 Jun 1999, liwen wu wrote:

> Hello,
> 
>    I have just submitted an internet draft
>  
> 
>             MPLS Multicast Traffic Engineering
>             draft-wu-mpls-multicast-te-00.txt
>  
> Abstract
>  
>    In a core ISP backbone network, when there are a lot of multicast
>    traffic which belongs to huge number of multicast groups, providing
>    differentiated services to different kind of multicast traffic
>    through this core network becomes a very difficult task. Also, how to
>    use network resources in an efficient and optimized way to support
>    differentiated multicast service is very difficult.
>  
>    This draft introduces one method, MPLS multicast traffic engineering,
>    which can be used to manage multicast traffic in a core ISP backbone
>    network.
>  
>    This draft starts with introducing the MPLS multicast traffic
>    engineering concept. Then it describes 2 ways of building a multicast
>    traffic engineering tree: sender-initiated tree and receiver-
>    initiated tree. Finally, it provides an appendix, which defines the
>    extensions to CR-LDP to support MPLS multicast traffic engineering.
> 
> It is available:
> 
> ftp::/ftp.ietf.org/internet-draft/draft-wu-mpls-multicast-te-00.txt
> 
> Best Regards,
> Liwen--
> 
> ____________________________________________________________________
> Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com.
> 

<L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>



From owner-idmr@cs.ucl.ac.uk  Thu Jun 17 12:18:19 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA00077
	for <idmr-archive@lists.ietf.org>; Thu, 17 Jun 1999 12:18:17 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.29505-0@pan2.cs.ucl.ac.uk>;
          Thu, 17 Jun 1999 14:17:44 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.29499-0@pan2.cs.ucl.ac.uk>; Thu, 17 Jun 1999 14:17:40 +0100
Received: from www0l.netaddress.usa.net by bells.cs.ucl.ac.uk 
          with Internet SMTP id <g.21925-0@bells.cs.ucl.ac.uk>;
          Thu, 17 Jun 1999 14:17:57 +0100
Received: (qmail 1952 invoked by uid 60001); 17 Jun 1999 13:17:54 -0000
Message-ID: <19990617131754.1951.qmail@www0l.netaddress.usa.net>
Original-Received: from 204.68.24.41 by www0l via web-mailer(M3.2.0.17) on Thu 
                   Jun 17 13:17:54 GMT 1999
PP-warning: Illegal Received field on preceding line
Date: 17 Jun 99 06:17:54 PDT
From: liwen wu <liwenwu@netscape.net>
To: mpls@UU.NET
Subject: MPLS Multicast Traffic Engineering
CC: idmr@cs.ucl.ac.uk, te-wg@avici.com
X-Mailer: USANET web-mailer (M3.2.0.17)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA00077

Hello,

   I have just submitted an internet draft
 

            MPLS Multicast Traffic Engineering
            draft-wu-mpls-multicast-te-00.txt
 
Abstract
 
   In a core ISP backbone network, when there are a lot of multicast
   traffic which belongs to huge number of multicast groups, providing
   differentiated services to different kind of multicast traffic
   through this core network becomes a very difficult task. Also, how to
   use network resources in an efficient and optimized way to support
   differentiated multicast service is very difficult.
 
   This draft introduces one method, MPLS multicast traffic engineering,
   which can be used to manage multicast traffic in a core ISP backbone
   network.
 
   This draft starts with introducing the MPLS multicast traffic
   engineering concept. Then it describes 2 ways of building a multicast
   traffic engineering tree: sender-initiated tree and receiver-
   initiated tree. Finally, it provides an appendix, which defines the
   extensions to CR-LDP to support MPLS multicast traffic engineering.

It is available:

ftp::/ftp.ietf.org/internet-draft/draft-wu-mpls-multicast-te-00.txt

Best Regards,
Liwen--

____________________________________________________________________
Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com.


From owner-idmr@cs.ucl.ac.uk  Thu Jun 17 16:17:34 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA02324
	for <idmr-archive@lists.ietf.org>; Thu, 17 Jun 1999 16:17:33 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.00134-0@pan2.cs.ucl.ac.uk>;
          Thu, 17 Jun 1999 19:34:35 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.00128-0@pan2.cs.ucl.ac.uk>; Thu, 17 Jun 1999 19:34:31 +0100
Received: from postman.adn.alcatel.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.11093-0@bells.cs.ucl.ac.uk>; Thu, 17 Jun 1999 19:34:48 +0100
Received: from postal.adn.alcatel.com (postal [198.205.32.56]) 
          by adn.alcatel.com with ESMTP (8.7.6/8.7.1) id OAA08448 
          for <idmr@cs.ucl.ac.uk>; Thu, 17 Jun 1999 14:29:43 -0400 (EDT)
Received: from adn.alcatel.com ([198.205.34.70]) 
          by postal.adn.alcatel.com (Netscape Messaging Server 3.6) with ESMTP 
          id AAA12FA; Thu, 17 Jun 1999 14:36:20 -0400
Message-ID: <3769414D.C3860DB@adn.alcatel.com>
Date: Thu, 17 Jun 1999 14:41:18 -0400
From: Ben Abarbanel <Benjamin.Abarbanel@adn.alcatel.com>
X-Mailer: Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Bora Akyol <akyol@pluris.com>
CC: LiWen Wu <liwen.wu@adn.alcatel.com>, liwen wu <liwenwu@netscape.net>,
        mpls@UU.NET, te-wg@avici.com, idmr@cs.ucl.ac.uk
Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
References: <003601beb8ec$145ec3a0$963710ac@pluris.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit



Bora Akyol wrote:

> The point that you are missing is the fact that the point-to-point MPLS
> tunnels implement an arbitrary IP topology that includes multicast traffic.
> The MPLS topology of the network is optimized according to the traffic that
> runs on top of the physical links including IP multicast. Therefore one does
> not need to add an MPLS multicast tree.
>
> I believe that this draft confuses MPLS multicast with IP multicast while
> implying that one needs to build an MPLS multicast tree to efficiently
> perform IP multicast which is untrue. MPLS tunnels when designed take into
> account IP multicast traffic as well.

Perhaps multicast traffic can be traffic engineered over the point to point MPLS
tunnels to be
regulated as to traffic type of service (QOS). This should solve the traffic
congestion issue being addressed in this spec.

Even intermediate nodes that makeup the point to point MPLS tunnels are not
aware of multicast addresses/routes. So that is covered sufficient enough to not
require the multicast
tree contstruction in the transit (core) network.

Regards,
Ben

>
>
> Regards
>
> Bora
>
> > -----Original Message-----
> > From: liwenwu@adn.alcatel.com [mailto:liwenwu@adn.alcatel.com]On Behalf
> > Of LiWen Wu
> > Sent: Thursday, June 17, 1999 10:57 AM
> > To: Bora Akyol
> > Cc: liwen wu; mpls@UU.NET; te-wg@avici.com; idmr@cs.ucl.ac.uk
> > Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
> >
> >
> > Bora Akyol wrote:
> >
> > > Comments:
> > >
> > > 1) Is the multicast traffic included in the statistics that are used to
> > > create the traffic matrix which in turn is used to create the
> > desired MPLS
> > > topology?
> >
> > Yes. But as  I am aware of today, all traffic engineereing
> > related drafts only
> > deal with
> > point-to-point MPLS tunnel.
> >
> > This paper propose building a point-to-multipoint MPLS tree to carry the
> > multicast traffic through the core network.
> >
> > These trees are traffic engineered to avoid congested node and
> > links . They
> > also can be engineered to meet certain QOS requirement.
> >
> > There is another big advantage by using this concept that:
> >
> > 1)  All the routers inside a core ISP domain DOES NOT need to be
> > aware of all the multicast groups and sources. (Similar to a core router
> > only aware of OSPF routes, but does not need to know all the BGP routes)
> >
> > 2) Only border routers(root and receivers) need to know all the
> > multicast groups and sources , mappings from multicast group and sources
> > to MPLS point-to-multipoint TREEs.
> >
> > best regards,
> > Liwen--
> >
> > >
> > >
> > > If the answer to this is *yes*, then ordinary traffic engineering will
> > > optimize the traffic flows such that you will *get* a good
> > distribution of
> > > the multicast flows over the existing physical topology. So the
> > procedures
> > > proposed in this draft are not needed.
> > >
> > > If the answer is *no* then the solution may be covered in this draft.
> > >
> > > I personally don't see a need for this draft or the methods
> > proposed in it.
> > > In most cases, the traffic matrix will actually include the multicast
> > > traffic and will optimize the MPLS topology accordingly.
> > Otherwise, you will
> > > end up with one multicast topology and one unicast topology and
> > yet another
> > > network to manage.
> > >
> > > If we want to make multicast routing more efficient, we should
> > follow along
> > > the lines **-omp drafts and create a multicast routing
> > algorithm that runs
> > > within an area and
> > > is sensitive to network utilization.
> > >
> > > Bora
> >
> > --
> > --------------------------------------------------------------------------
> > Liwen Wu                                     Phone: (703) 724-2619
> > Alcatel U.S.A                                FAX:   (703) 724-2005
> > 44983 Knoll Square                  Inet:  liwen.wu@adn.alcatel.com
> > Ashburn, Va. 20147
> > USA
> > ------------------------------------------------------------------
> > ----------
> >
> >
> >
> >



From owner-idmr@cs.ucl.ac.uk  Thu Jun 17 16:18:34 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA02335
	for <idmr-archive@lists.ietf.org>; Thu, 17 Jun 1999 16:18:32 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.29956-0@pan2.cs.ucl.ac.uk>;
          Thu, 17 Jun 1999 18:56:25 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.29950-0@pan2.cs.ucl.ac.uk>; Thu, 17 Jun 1999 18:56:21 +0100
Received: from 198.205.32.33 by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.09117-0@bells.cs.ucl.ac.uk>; Thu, 17 Jun 1999 18:56:38 +0100
Received: from postal.adn.alcatel.com (postal [198.205.32.56]) 
          by adn.alcatel.com with ESMTP (8.7.6/8.7.1) id NAA06886 
          for <idmr@cs.ucl.ac.uk>; Thu, 17 Jun 1999 13:51:28 -0400 (EDT)
Received: from adn.alcatel.com ([198.205.52.65]) 
          by postal.adn.alcatel.com (Netscape Messaging Server 3.6) with ESMTP 
          id AAAE12; Thu, 17 Jun 1999 13:58:04 -0400
Message-ID: <376936D4.EBAE86E2@adn.alcatel.com>
Date: Thu, 17 Jun 1999 13:56:37 -0400
From: LiWen Wu <liwen.wu@adn.alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 4.1.3_U1 sun4m)
X-Accept-Language: en
MIME-Version: 1.0
To: Bora Akyol <akyol@pluris.com>
CC: liwen wu <liwenwu@netscape.net>, mpls@UU.NET, te-wg@avici.com,
        idmr@cs.ucl.ac.uk
Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
References: <002701beb8df$b5595160$963710ac@pluris.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bora Akyol wrote:

> Comments:
>
> 1) Is the multicast traffic included in the statistics that are used to
> create the traffic matrix which in turn is used to create the desired MPLS
> topology?

Yes. But as  I am aware of today, all traffic engineereing related drafts only
deal with
point-to-point MPLS tunnel.

This paper propose building a point-to-multipoint MPLS tree to carry the
multicast traffic through the core network.

These trees are traffic engineered to avoid congested node and links . They
also can be engineered to meet certain QOS requirement.

There is another big advantage by using this concept that:

1)  All the routers inside a core ISP domain DOES NOT need to be
aware of all the multicast groups and sources. (Similar to a core router
only aware of OSPF routes, but does not need to know all the BGP routes)

2) Only border routers(root and receivers) need to know all the
multicast groups and sources , mappings from multicast group and sources
to MPLS point-to-multipoint TREEs.

best regards,
Liwen--

>
>
> If the answer to this is *yes*, then ordinary traffic engineering will
> optimize the traffic flows such that you will *get* a good distribution of
> the multicast flows over the existing physical topology. So the procedures
> proposed in this draft are not needed.
>
> If the answer is *no* then the solution may be covered in this draft.
>
> I personally don't see a need for this draft or the methods proposed in it.
> In most cases, the traffic matrix will actually include the multicast
> traffic and will optimize the MPLS topology accordingly. Otherwise, you will
> end up with one multicast topology and one unicast topology and yet another
> network to manage.
>
> If we want to make multicast routing more efficient, we should follow along
> the lines **-omp drafts and create a multicast routing algorithm that runs
> within an area and
> is sensitive to network utilization.
>
> Bora

--
--------------------------------------------------------------------------
Liwen Wu                                     Phone: (703) 724-2619
Alcatel U.S.A                                FAX:   (703) 724-2005
44983 Knoll Square                  Inet:  liwen.wu@adn.alcatel.com
Ashburn, Va. 20147
USA
----------------------------------------------------------------------------





From owner-idmr@cs.ucl.ac.uk  Thu Jun 17 16:18:52 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA02352
	for <idmr-archive@lists.ietf.org>; Thu, 17 Jun 1999 16:18:51 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.00113-0@pan2.cs.ucl.ac.uk>;
          Thu, 17 Jun 1999 19:28:13 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.00102-0@pan2.cs.ucl.ac.uk>; Thu, 17 Jun 1999 19:28:07 +0100
Received: from postman.adn.alcatel.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.10649-0@bells.cs.ucl.ac.uk>; Thu, 17 Jun 1999 19:28:10 +0100
Received: from postal.adn.alcatel.com (postal [198.205.32.56]) 
          by adn.alcatel.com with ESMTP (8.7.6/8.7.1) id OAA08211 
          for <idmr@cs.ucl.ac.uk>; Thu, 17 Jun 1999 14:22:59 -0400 (EDT)
Received: from adn.alcatel.com ([198.205.52.65]) 
          by postal.adn.alcatel.com (Netscape Messaging Server 3.6) with ESMTP 
          id AAA123B; Thu, 17 Jun 1999 14:29:36 -0400
Message-ID: <37693E37.4E1007CD@adn.alcatel.com>
Date: Thu, 17 Jun 1999 14:28:08 -0400
From: LiWen Wu <liwen.wu@adn.alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 4.1.3_U1 sun4m)
X-Accept-Language: en
MIME-Version: 1.0
To: Bora Akyol <akyol@pluris.com>
CC: liwen wu <liwenwu@netscape.net>, mpls@UU.NET, te-wg@avici.com,
        idmr@cs.ucl.ac.uk
Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
References: <003601beb8ec$145ec3a0$963710ac@pluris.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bora Akyol wrote:

> The point that you are missing is the fact that the point-to-point MPLS
> tunnels implement an arbitrary IP topology that includes multicast traffic.
> The MPLS topology of the network is optimized according to the traffic that
> runs on top of the physical links including IP multicast. Therefore one does
> not need to add an MPLS multicast tree.

Bora, I agree with you that you could use point-to-point tunnel to carry
multicast traffic. Similarily, I could  also argue why not duplicate the packet
at source
and unicast them  one by one to all the receivers.

But I would think sending a packet through a point-to-multipoint tree is more
efficient than duplicating the packet at ingress and send them through the
MULTIPLE point-to-point MPLS tunnels.

>
>
> I believe that this draft confuses MPLS multicast with IP multicast while
> implying that one needs to build an MPLS multicast tree to efficiently
> perform IP multicast which is untrue. MPLS tunnels when designed take into
> account IP multicast traffic as well.
>

This draft provides only ONE method on how to manage multicast traffic
in a core network.  It proposes using MPLS point-to-multipoint tree
to transport multicast traffic through a core ISP network.

best regars,
Liwen--

>
> Regards
>
> Bora
>
> > -----Original Message-----
> > From: liwenwu@adn.alcatel.com [mailto:liwenwu@adn.alcatel.com]On Behalf
> > Of LiWen Wu
> > Sent: Thursday, June 17, 1999 10:57 AM
> > To: Bora Akyol
> > Cc: liwen wu; mpls@UU.NET; te-wg@avici.com; idmr@cs.ucl.ac.uk
> > Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
> >
> >
> > Bora Akyol wrote:
> >
> > > Comments:
> > >
> > > 1) Is the multicast traffic included in the statistics that are used to
> > > create the traffic matrix which in turn is used to create the
> > desired MPLS
> > > topology?
> >
> > Yes. But as  I am aware of today, all traffic engineereing
> > related drafts only
> > deal with
> > point-to-point MPLS tunnel.
> >
> > This paper propose building a point-to-multipoint MPLS tree to carry the
> > multicast traffic through the core network.
> >
> > These trees are traffic engineered to avoid congested node and
> > links . They
> > also can be engineered to meet certain QOS requirement.
> >
> > There is another big advantage by using this concept that:
> >
> > 1)  All the routers inside a core ISP domain DOES NOT need to be
> > aware of all the multicast groups and sources. (Similar to a core router
> > only aware of OSPF routes, but does not need to know all the BGP routes)
> >
> > 2) Only border routers(root and receivers) need to know all the
> > multicast groups and sources , mappings from multicast group and sources
> > to MPLS point-to-multipoint TREEs.
> >
> > best regards,
> > Liwen--
> >
> > >
> > >
> > > If the answer to this is *yes*, then ordinary traffic engineering will
> > > optimize the traffic flows such that you will *get* a good
> > distribution of
> > > the multicast flows over the existing physical topology. So the
> > procedures
> > > proposed in this draft are not needed.
> > >
> > > If the answer is *no* then the solution may be covered in this draft.
> > >
> > > I personally don't see a need for this draft or the methods
> > proposed in it.
> > > In most cases, the traffic matrix will actually include the multicast
> > > traffic and will optimize the MPLS topology accordingly.
> > Otherwise, you will
> > > end up with one multicast topology and one unicast topology and
> > yet another
> > > network to manage.
> > >
> > > If we want to make multicast routing more efficient, we should
> > follow along
> > > the lines **-omp drafts and create a multicast routing
> > algorithm that runs
> > > within an area and
> > > is sensitive to network utilization.
> > >
> > > Bora
> >
> > --
> > --------------------------------------------------------------------------
> > Liwen Wu                                     Phone: (703) 724-2619
> > Alcatel U.S.A                                FAX:   (703) 724-2005
> > 44983 Knoll Square                  Inet:  liwen.wu@adn.alcatel.com
> > Ashburn, Va. 20147
> > USA
> > ------------------------------------------------------------------
> > ----------
> >
> >
> >
> >

--
--------------------------------------------------------------------------
Liwen Wu                                     Phone: (703) 724-2619
Alcatel U.S.A                                FAX:   (703) 724-2005
44983 Knoll Square                  Inet:  liwen.wu@adn.alcatel.com
Ashburn, Va. 20147
USA
----------------------------------------------------------------------------





From owner-idmr@cs.ucl.ac.uk  Thu Jun 17 16:19:03 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA02365
	for <idmr-archive@lists.ietf.org>; Thu, 17 Jun 1999 16:19:01 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.29978-0@pan2.cs.ucl.ac.uk>;
          Thu, 17 Jun 1999 19:05:11 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.29972-0@pan2.cs.ucl.ac.uk>; Thu, 17 Jun 1999 19:05:07 +0100
Received: from host66.pluris.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.09549-0@bells.cs.ucl.ac.uk>; Thu, 17 Jun 1999 19:05:23 +0100
Received: from akyol ([172.16.55.150]) by yarilo.pluris.com (8.9.2/8.9.1) 
          with SMTP id LAA07279; Thu, 17 Jun 1999 11:04:44 -0700 (PDT)
From: Bora Akyol <akyol@pluris.com>
To: LiWen Wu <liwen.wu@adn.alcatel.com>
Cc: liwen wu <liwenwu@netscape.net>, mpls <mpls@UU.NET>,
        te-wg <te-wg@avici.com>, idmr <idmr@cs.ucl.ac.uk>
Subject: RE: Question on draft-wu-mpls-multicast-te-00.txt
Date: Thu, 17 Jun 1999 11:06:10 -0700
Message-ID: <003601beb8ec$145ec3a0$963710ac@pluris.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
In-Reply-To: <376936D4.EBAE86E2@adn.alcatel.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

The point that you are missing is the fact that the point-to-point MPLS
tunnels implement an arbitrary IP topology that includes multicast traffic.
The MPLS topology of the network is optimized according to the traffic that
runs on top of the physical links including IP multicast. Therefore one does
not need to add an MPLS multicast tree.

I believe that this draft confuses MPLS multicast with IP multicast while
implying that one needs to build an MPLS multicast tree to efficiently
perform IP multicast which is untrue. MPLS tunnels when designed take into
account IP multicast traffic as well.

Regards

Bora


> -----Original Message-----
> From: liwenwu@adn.alcatel.com [mailto:liwenwu@adn.alcatel.com]On Behalf
> Of LiWen Wu
> Sent: Thursday, June 17, 1999 10:57 AM
> To: Bora Akyol
> Cc: liwen wu; mpls@UU.NET; te-wg@avici.com; idmr@cs.ucl.ac.uk
> Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
>
>
> Bora Akyol wrote:
>
> > Comments:
> >
> > 1) Is the multicast traffic included in the statistics that are used to
> > create the traffic matrix which in turn is used to create the
> desired MPLS
> > topology?
>
> Yes. But as  I am aware of today, all traffic engineereing
> related drafts only
> deal with
> point-to-point MPLS tunnel.
>
> This paper propose building a point-to-multipoint MPLS tree to carry the
> multicast traffic through the core network.
>
> These trees are traffic engineered to avoid congested node and
> links . They
> also can be engineered to meet certain QOS requirement.
>
> There is another big advantage by using this concept that:
>
> 1)  All the routers inside a core ISP domain DOES NOT need to be
> aware of all the multicast groups and sources. (Similar to a core router
> only aware of OSPF routes, but does not need to know all the BGP routes)
>
> 2) Only border routers(root and receivers) need to know all the
> multicast groups and sources , mappings from multicast group and sources
> to MPLS point-to-multipoint TREEs.
>
> best regards,
> Liwen--
>
> >
> >
> > If the answer to this is *yes*, then ordinary traffic engineering will
> > optimize the traffic flows such that you will *get* a good
> distribution of
> > the multicast flows over the existing physical topology. So the
> procedures
> > proposed in this draft are not needed.
> >
> > If the answer is *no* then the solution may be covered in this draft.
> >
> > I personally don't see a need for this draft or the methods
> proposed in it.
> > In most cases, the traffic matrix will actually include the multicast
> > traffic and will optimize the MPLS topology accordingly.
> Otherwise, you will
> > end up with one multicast topology and one unicast topology and
> yet another
> > network to manage.
> >
> > If we want to make multicast routing more efficient, we should
> follow along
> > the lines **-omp drafts and create a multicast routing
> algorithm that runs
> > within an area and
> > is sensitive to network utilization.
> >
> > Bora
>
> --
> --------------------------------------------------------------------------
> Liwen Wu                                     Phone: (703) 724-2619
> Alcatel U.S.A                                FAX:   (703) 724-2005
> 44983 Knoll Square                  Inet:  liwen.wu@adn.alcatel.com
> Ashburn, Va. 20147
> USA
> ------------------------------------------------------------------
> ----------
>
>
>
>



From owner-idmr@cs.ucl.ac.uk  Thu Jun 17 17:22:48 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA02808
	for <idmr-archive@lists.ietf.org>; Thu, 17 Jun 1999 17:22:47 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.00729-0@pan2.cs.ucl.ac.uk>;
          Thu, 17 Jun 1999 21:18:44 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.00716-0@pan2.cs.ucl.ac.uk>; Thu, 17 Jun 1999 21:18:23 +0100
Received: from postman.adn.alcatel.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.16489-0@bells.cs.ucl.ac.uk>; Thu, 17 Jun 1999 21:18:39 +0100
Received: from postal.adn.alcatel.com (postal [198.205.32.56]) 
          by adn.alcatel.com with ESMTP (8.7.6/8.7.1) id QAA13054 
          for <idmr@cs.ucl.ac.uk>; Thu, 17 Jun 1999 16:13:34 -0400 (EDT)
Received: from adn.alcatel.com ([198.205.34.70]) 
          by postal.adn.alcatel.com (Netscape Messaging Server 3.6) with ESMTP 
          id AAA2074; Thu, 17 Jun 1999 16:20:10 -0400
Message-ID: <376959A3.3A8F2098@adn.alcatel.com>
Date: Thu, 17 Jun 1999 16:25:08 -0400
From: Ben Abarbanel <Benjamin.Abarbanel@adn.alcatel.com>
X-Mailer: Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: LiWen Wu <liwen.wu@adn.alcatel.com>
CC: Bora Akyol <akyol@pluris.com>, liwen wu <liwenwu@netscape.net>,
        mpls@UU.NET, te-wg@avici.com, idmr@cs.ucl.ac.uk
Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
References: <003601beb8ec$145ec3a0$963710ac@pluris.com> <37693E37.4E1007CD@adn.alcatel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit



LiWen Wu wrote:

> Bora Akyol wrote:
>
> > The point that you are missing is the fact that the point-to-point MPLS
> > tunnels implement an arbitrary IP topology that includes multicast traffic.
> > The MPLS topology of the network is optimized according to the traffic that
> > runs on top of the physical links including IP multicast. Therefore one does
> > not need to add an MPLS multicast tree.
>
> Bora, I agree with you that you could use point-to-point tunnel to carry
> multicast traffic. Similarily, I could  also argue why not duplicate the packet
> at source
> and unicast them  one by one to all the receivers.
>
> But I would think sending a packet through a point-to-multipoint tree is more
> efficient than duplicating the packet at ingress and send them through the
> MULTIPLE point-to-point MPLS tunnels.

Bora, Liwen:
  One additional improvement I see by this design approach, is that with a point to
multipoint multicast tree structure. All nodes are MPLS capable and know at time of
tunnel creation where the juncture at which packets are to be broadcast to EGRESS
points. This implies that we never leave level 2 processing during multicast packet
forwardin thru the point to multipoint tunnels. In a similar topology without a
braodcast label swapping function, we would have to leave level 2 to enter level 3
forwarding to do a multicast forwarding lookup function to seek the individual
egress tunnels and reenter level 2 label switching again. As shown below.

                                 Multicast Tree Point to Multipoint forwarding

                                                                     |  Ingress
Point (level 3 to level 2 transitioning)
                                                             SRC RTR
                                                                     |
                                                                     |     Label
Switching (level 2)
                                                                     |
                                                          JUNCTURE RTR
                                                                 /    |    \
                                                               /      |      \
Broadcast Label Switching  (level 2)
                                                             /        |        \
                                                        dst1    dst2     dst3
(Egress points) (transition to level 3)


                                 Conventional  Point to Point Multicast Forwarding

                                                                     |  Ingress
Point (level 3 to level 2 transitioning)
                                                             SRC RTR
                                                                     |
                                                                     |     Label
Switching (level 2)
                                                                     |
                                                          JUNCTURE RTR  (transition
to level 3 to do multicast lookup)
                                                                 /    |    \
(then broadcast to individual tunnels at level 2)
                                                               /      |      \
Label Switching again (level 2)
                                                             /        |        \
                                                        dst1    dst2     dst3
(Egress Point) (transition to level 3)

     Regards,
     Ben

>
>
> >
> >
> > I believe that this draft confuses MPLS multicast with IP multicast while
> > implying that one needs to build an MPLS multicast tree to efficiently
> > perform IP multicast which is untrue. MPLS tunnels when designed take into
> > account IP multicast traffic as well.
> >
>
> This draft provides only ONE method on how to manage multicast traffic
> in a core network.  It proposes using MPLS point-to-multipoint tree
> to transport multicast traffic through a core ISP network.
>
> best regars,
> Liwen--
>
> >
> > Regards
> >
> > Bora
> >
> > > -----Original Message-----
> > > From: liwenwu@adn.alcatel.com [mailto:liwenwu@adn.alcatel.com]On Behalf
> > > Of LiWen Wu
> > > Sent: Thursday, June 17, 1999 10:57 AM
> > > To: Bora Akyol
> > > Cc: liwen wu; mpls@UU.NET; te-wg@avici.com; idmr@cs.ucl.ac.uk
> > > Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
> > >
> > >
> > > Bora Akyol wrote:
> > >
> > > > Comments:
> > > >
> > > > 1) Is the multicast traffic included in the statistics that are used to
> > > > create the traffic matrix which in turn is used to create the
> > > desired MPLS
> > > > topology?
> > >
> > > Yes. But as  I am aware of today, all traffic engineereing
> > > related drafts only
> > > deal with
> > > point-to-point MPLS tunnel.
> > >
> > > This paper propose building a point-to-multipoint MPLS tree to carry the
> > > multicast traffic through the core network.
> > >
> > > These trees are traffic engineered to avoid congested node and
> > > links . They
> > > also can be engineered to meet certain QOS requirement.
> > >
> > > There is another big advantage by using this concept that:
> > >
> > > 1)  All the routers inside a core ISP domain DOES NOT need to be
> > > aware of all the multicast groups and sources. (Similar to a core router
> > > only aware of OSPF routes, but does not need to know all the BGP routes)
> > >
> > > 2) Only border routers(root and receivers) need to know all the
> > > multicast groups and sources , mappings from multicast group and sources
> > > to MPLS point-to-multipoint TREEs.
> > >
> > > best regards,
> > > Liwen--
> > >
> > > >
> > > >
> > > > If the answer to this is *yes*, then ordinary traffic engineering will
> > > > optimize the traffic flows such that you will *get* a good
> > > distribution of
> > > > the multicast flows over the existing physical topology. So the
> > > procedures
> > > > proposed in this draft are not needed.
> > > >
> > > > If the answer is *no* then the solution may be covered in this draft.
> > > >
> > > > I personally don't see a need for this draft or the methods
> > > proposed in it.
> > > > In most cases, the traffic matrix will actually include the multicast
> > > > traffic and will optimize the MPLS topology accordingly.
> > > Otherwise, you will
> > > > end up with one multicast topology and one unicast topology and
> > > yet another
> > > > network to manage.
> > > >
> > > > If we want to make multicast routing more efficient, we should
> > > follow along
> > > > the lines **-omp drafts and create a multicast routing
> > > algorithm that runs
> > > > within an area and
> > > > is sensitive to network utilization.
> > > >
> > > > Bora
> > >
> > > --
> > > --------------------------------------------------------------------------
> > > Liwen Wu                                     Phone: (703) 724-2619
> > > Alcatel U.S.A                                FAX:   (703) 724-2005
> > > 44983 Knoll Square                  Inet:  liwen.wu@adn.alcatel.com
> > > Ashburn, Va. 20147
> > > USA
> > > ------------------------------------------------------------------
> > > ----------
> > >
> > >
> > >
> > >
>
> --
> --------------------------------------------------------------------------
> Liwen Wu                                     Phone: (703) 724-2619
> Alcatel U.S.A                                FAX:   (703) 724-2005
> 44983 Knoll Square                  Inet:  liwen.wu@adn.alcatel.com
> Ashburn, Va. 20147
> USA
> ----------------------------------------------------------------------------



From owner-idmr@cs.ucl.ac.uk  Thu Jun 17 17:23:59 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA02841
	for <idmr-archive@lists.ietf.org>; Thu, 17 Jun 1999 17:23:59 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.01087-0@pan2.cs.ucl.ac.uk>;
          Thu, 17 Jun 1999 22:12:46 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.01081-0@pan2.cs.ucl.ac.uk>; Thu, 17 Jun 1999 22:12:40 +0100
Received: from hermes.ccrl.nj.nec.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.19554-0@bells.cs.ucl.ac.uk>; Thu, 17 Jun 1999 22:12:49 +0100
Received: from ccrl.nj.nec.com (pc2-braja.ccrl.nj.nec.com [138.15.100.11]) 
          by hermes.ccrl.nj.nec.com (1.00/LJF980616) with ESMTP id RAA27778;
          Thu, 17 Jun 1999 17:12:24 -0400 (EDT)
Message-ID: <37696504.51C4253A@ccrl.nj.nec.com>
Date: Thu, 17 Jun 1999 17:13:40 -0400
From: Bala Rajagopalan <braja@ccrl.nj.nec.com>
Reply-To: braja@ccrl.nj.nec.com
Organization: NEC
X-Mailer: Mozilla 4.05 [en] (Win95; U)
MIME-Version: 1.0
To: Bora Akyol <akyol@pluris.com>
CC: LiWen Wu <liwen.wu@adn.alcatel.com>, mpls@UU.NET, te-wg@avici.com,
        idmr@cs.ucl.ac.uk
Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
References: <005501beb8f9$2e29a040$963710ac@pluris.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit



Bora Akyol wrote:

> Liwen,
>
> Let me try explaing this again:
>
> 1. There is an IP network consisting of N nodes (N>=2).
> 2. There is an MPLS topology over which the IP packets flow over including
> multicast packets.
> 3. There is a statistics collection process that collects a traffic matrix
> (NxN) for all of IP traffic that is flowing between the nodes of an area
> like you will find in a backbone topology.
> 4. The optimization process uses 1 and 3 to produce 2 and in the meantime
> configures the network such that all data flow demands are satisfied
> optimally (including MPLS packets).

What's not clear to me is how you'd implement (4). I assume that
you're suggesting that
the MPLS topology has been constructed to take into account some coarse
estimate of the multicast demands. Now, you still have to ensure that the
multicast (and unicast) paths in the network for the data packets are as
intended.

I would take Wu's draft as proposing a mechanism for actually establishing
specific
paths for multicast (which perhaps were derived in step (4) above).

>
>
> Moreover, as multicast traffic is dynamic and can change rapidly, I don't
> see the point of *multicast* traffic engineering which is assumed to be
> quasi-static.

I agree with this. But the assumption of dynamism also works against your steps
for traffic engineering (steps 1-4 above), since you have also assumed that
multicast traffic can be estimated meaningfully for  input to the topology
design process (in step 3).

Regards,

--


Bala Rajagopalan
NEC USA, C&C Research Labs
4 Independence Way
Princeton, NJ 08540
U.S.A

Ph: +1-609-951-2969
Fax: +1-609-951-2499
Email: braja@ccrl.nj.nec.com




From owner-idmr@cs.ucl.ac.uk  Thu Jun 17 17:24:09 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA02852
	for <idmr-archive@lists.ietf.org>; Thu, 17 Jun 1999 17:24:08 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.00864-0@pan2.cs.ucl.ac.uk>;
          Thu, 17 Jun 1999 21:36:05 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.00853-0@pan2.cs.ucl.ac.uk>; Thu, 17 Jun 1999 21:35:51 +0100
Received: from postman.adn.alcatel.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.17506-0@bells.cs.ucl.ac.uk>; Thu, 17 Jun 1999 21:36:06 +0100
Received: from postal.adn.alcatel.com (postal [198.205.32.56]) 
          by adn.alcatel.com with ESMTP (8.7.6/8.7.1) id QAA13804 
          for <idmr@cs.ucl.ac.uk>; Thu, 17 Jun 1999 16:31:01 -0400 (EDT)
Received: from adn.alcatel.com ([198.205.52.65]) 
          by postal.adn.alcatel.com (Netscape Messaging Server 3.6) with ESMTP 
          id AAA22CE; Thu, 17 Jun 1999 16:37:38 -0400
Message-ID: <37695C35.A5CBC5DD@adn.alcatel.com>
Date: Thu, 17 Jun 1999 16:36:10 -0400
From: LiWen Wu <liwen.wu@adn.alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 4.1.3_U1 sun4m)
X-Accept-Language: en
MIME-Version: 1.0
To: Bora Akyol <akyol@pluris.com>
CC: mpls@UU.NET, te-wg@avici.com, idmr@cs.ucl.ac.uk
Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
References: <005501beb8f9$2e29a040$963710ac@pluris.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello Bora,

   Let me try to explain with one following simple example:

A--->B---->C
                |
                D---->E

A,C,E are border routers, B,D are core routers.

I could build:

1) Tunnel 1- {A,B,C} to carry the unicast traffic
which enters the network from A and exit the
network through C

2) Tunnel 2 - {A,B,D,E} to carry the  unicast traffic
which enters the network  from A and exit the
network through E

3) Tree1 - {A,{B, C}, {B,D,E}} to carry the multicast traffic
which enters the network from A and exit the
network through C and E.

For a multicast flow which enters the network from A and
exits from the network through E and C, I would think
put it through Tree1 is more efficient than
duplicate it at A and sent them through Tunnel1 and Tunnel2.

best regards,
Liwen--




Bora Akyol wrote:

> Liwen,
>
> Let me try explaing this again:
>
> 1. There is an IP network consisting of N nodes (N>=2).
> 2. There is an MPLS topology over which the IP packets flow over including
> multicast packets.
> 3. There is a statistics collection process that collects a traffic matrix
> (NxN) for all of IP traffic that is flowing between the nodes of an area
> like you will find in a backbone topology.
> 4. The optimization process uses 1 and 3 to produce 2 and in the meantime
> configures the network such that all data flow demands are satisfied
> optimally (including MPLS packets).
>
> What is being suggested in this draft results in another version of the MPLS
> topology in addition to (2) but in fact it does *NOT* optimize significantly
> better than the current traffic engineering approaches but results in two
> (overlay) networks.
>
> Nowhere in my email, do I suggest that you abandon IP level multicast and
> use unicast, so I don't understand the last comment that you are making.
> What I am suggesting is that IP Multicast traffic can flow over the traffic
> engineered network just as well as the unicast traffic. This is *especially*
> true in a backbone network.
>
> Moreover, as multicast traffic is dynamic and can change rapidly, I don't
> see the point of *multicast* traffic engineering which is assumed to be
> quasi-static.
>
> What this ID sounds like is a way of doing MPLS multicast as you would see
> in an ATM network which is fine, but is not related to traffic engineering.
>
> Regards
>
> Bora
>
> > -----Original Message-----
> > From: liwenwu@adn.alcatel.com [mailto:liwenwu@adn.alcatel.com]On Behalf
> > Of LiWen Wu
> > Sent: Thursday, June 17, 1999 11:28 AM
> > To: Bora Akyol
> > Cc: liwen wu; mpls@UU.NET; te-wg@avici.com; idmr@cs.ucl.ac.uk
> > Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
> >
> >
> > Bora Akyol wrote:
> >
> > > The point that you are missing is the fact that the point-to-point MPLS
> > > tunnels implement an arbitrary IP topology that includes
> > multicast traffic.
> > > The MPLS topology of the network is optimized according to the
> > traffic that
> > > runs on top of the physical links including IP multicast.
> > Therefore one does
> > > not need to add an MPLS multicast tree.
> >
> > Bora, I agree with you that you could use point-to-point tunnel to carry
> > multicast traffic. Similarily, I could  also argue why not
> > duplicate the packet
> > at source
> > and unicast them  one by one to all the receivers.
> >
> > But I would think sending a packet through a point-to-multipoint
> > tree is more
> > efficient than duplicating the packet at ingress and send them through the
> > MULTIPLE point-to-point MPLS tunnels.
> >
> > >
> > >
> > > I believe that this draft confuses MPLS multicast with IP
> > multicast while
> > > implying that one needs to build an MPLS multicast tree to efficiently
> > > perform IP multicast which is untrue. MPLS tunnels when
> > designed take into
> > > account IP multicast traffic as well.
> > >
> >
> > This draft provides only ONE method on how to manage multicast traffic
> > in a core network.  It proposes using MPLS point-to-multipoint tree
> > to transport multicast traffic through a core ISP network.
> >
> > best regars,
> > Liwen--
> >
> > >
> > > Regards
> > >
> > > Bora
> > >
> > > > -----Original Message-----
> > > > From: liwenwu@adn.alcatel.com
> > [mailto:liwenwu@adn.alcatel.com]On Behalf
> > > > Of LiWen Wu
> > > > Sent: Thursday, June 17, 1999 10:57 AM
> > > > To: Bora Akyol
> > > > Cc: liwen wu; mpls@UU.NET; te-wg@avici.com; idmr@cs.ucl.ac.uk
> > > > Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
> > > >
> > > >
> > > > Bora Akyol wrote:
> > > >
> > > > > Comments:
> > > > >
> > > > > 1) Is the multicast traffic included in the statistics that
> > are used to
> > > > > create the traffic matrix which in turn is used to create the
> > > > desired MPLS
> > > > > topology?
> > > >
> > > > Yes. But as  I am aware of today, all traffic engineereing
> > > > related drafts only
> > > > deal with
> > > > point-to-point MPLS tunnel.
> > > >
> > > > This paper propose building a point-to-multipoint MPLS tree
> > to carry the
> > > > multicast traffic through the core network.
> > > >
> > > > These trees are traffic engineered to avoid congested node and
> > > > links . They
> > > > also can be engineered to meet certain QOS requirement.
> > > >
> > > > There is another big advantage by using this concept that:
> > > >
> > > > 1)  All the routers inside a core ISP domain DOES NOT need to be
> > > > aware of all the multicast groups and sources. (Similar to a
> > core router
> > > > only aware of OSPF routes, but does not need to know all the
> > BGP routes)
> > > >
> > > > 2) Only border routers(root and receivers) need to know all the
> > > > multicast groups and sources , mappings from multicast group
> > and sources
> > > > to MPLS point-to-multipoint TREEs.
> > > >
> > > > best regards,
> > > > Liwen--
> > > >
> > > > >
> > > > >
> > > > > If the answer to this is *yes*, then ordinary traffic
> > engineering will
> > > > > optimize the traffic flows such that you will *get* a good
> > > > distribution of
> > > > > the multicast flows over the existing physical topology. So the
> > > > procedures
> > > > > proposed in this draft are not needed.
> > > > >
> > > > > If the answer is *no* then the solution may be covered in
> > this draft.
> > > > >
> > > > > I personally don't see a need for this draft or the methods
> > > > proposed in it.
> > > > > In most cases, the traffic matrix will actually include the
> > multicast
> > > > > traffic and will optimize the MPLS topology accordingly.
> > > > Otherwise, you will
> > > > > end up with one multicast topology and one unicast topology and
> > > > yet another
> > > > > network to manage.
> > > > >
> > > > > If we want to make multicast routing more efficient, we should
> > > > follow along
> > > > > the lines **-omp drafts and create a multicast routing
> > > > algorithm that runs
> > > > > within an area and
> > > > > is sensitive to network utilization.
> > > > >
> > > > > Bora
> > > >
> > > > --
> > > >
> > --------------------------------------------------------------------------
> > > > Liwen Wu                                     Phone: (703) 724-2619
> > > > Alcatel U.S.A                                FAX:   (703) 724-2005
> > > > 44983 Knoll Square                  Inet:  liwen.wu@adn.alcatel.com
> > > > Ashburn, Va. 20147
> > > > USA
> > > > ------------------------------------------------------------------
> > > > ----------
> > > >
> > > >
> > > >
> > > >
> >
> > --
> > --------------------------------------------------------------------------
> > Liwen Wu                                     Phone: (703) 724-2619
> > Alcatel U.S.A                                FAX:   (703) 724-2005
> > 44983 Knoll Square                  Inet:  liwen.wu@adn.alcatel.com
> > Ashburn, Va. 20147
> > USA
> > ------------------------------------------------------------------
> > ----------
> >
> >
> >
> >

--
--------------------------------------------------------------------------
Liwen Wu                                     Phone: (703) 724-2619
Alcatel U.S.A                                FAX:   (703) 724-2005
44983 Knoll Square                  Inet:  liwen.wu@adn.alcatel.com
Ashburn, Va. 20147
USA
----------------------------------------------------------------------------





From owner-idmr@cs.ucl.ac.uk  Thu Jun 17 17:24:25 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA02863
	for <idmr-archive@lists.ietf.org>; Thu, 17 Jun 1999 17:24:25 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.00531-0@pan2.cs.ucl.ac.uk>;
          Thu, 17 Jun 1999 20:39:01 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.00525-0@pan2.cs.ucl.ac.uk>; Thu, 17 Jun 1999 20:38:56 +0100
Received: from host66.pluris.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.14486-0@bells.cs.ucl.ac.uk>; Thu, 17 Jun 1999 20:39:14 +0100
Received: from akyol ([172.16.55.150]) by yarilo.pluris.com (8.9.2/8.9.1) 
          with SMTP id MAA10026; Thu, 17 Jun 1999 12:38:33 -0700 (PDT)
From: Bora Akyol <akyol@pluris.com>
To: LiWen Wu <liwen.wu@adn.alcatel.com>
Cc: Bora Akyol <akyol@pluris.com>, mpls <mpls@UU.NET>, te-wg <te-wg@avici.com>,
        idmr <idmr@cs.ucl.ac.uk>
Subject: RE: Question on draft-wu-mpls-multicast-te-00.txt
Date: Thu, 17 Jun 1999 12:39:57 -0700
Message-ID: <005501beb8f9$2e29a040$963710ac@pluris.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
In-Reply-To: <37693E37.4E1007CD@adn.alcatel.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

Liwen,

Let me try explaing this again:

1. There is an IP network consisting of N nodes (N>=2).
2. There is an MPLS topology over which the IP packets flow over including
multicast packets.
3. There is a statistics collection process that collects a traffic matrix
(NxN) for all of IP traffic that is flowing between the nodes of an area
like you will find in a backbone topology.
4. The optimization process uses 1 and 3 to produce 2 and in the meantime
configures the network such that all data flow demands are satisfied
optimally (including MPLS packets).

What is being suggested in this draft results in another version of the MPLS
topology in addition to (2) but in fact it does *NOT* optimize significantly
better than the current traffic engineering approaches but results in two
(overlay) networks.

Nowhere in my email, do I suggest that you abandon IP level multicast and
use unicast, so I don't understand the last comment that you are making.
What I am suggesting is that IP Multicast traffic can flow over the traffic
engineered network just as well as the unicast traffic. This is *especially*
true in a backbone network.

Moreover, as multicast traffic is dynamic and can change rapidly, I don't
see the point of *multicast* traffic engineering which is assumed to be
quasi-static.

What this ID sounds like is a way of doing MPLS multicast as you would see
in an ATM network which is fine, but is not related to traffic engineering.

Regards

Bora



> -----Original Message-----
> From: liwenwu@adn.alcatel.com [mailto:liwenwu@adn.alcatel.com]On Behalf
> Of LiWen Wu
> Sent: Thursday, June 17, 1999 11:28 AM
> To: Bora Akyol
> Cc: liwen wu; mpls@UU.NET; te-wg@avici.com; idmr@cs.ucl.ac.uk
> Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
>
>
> Bora Akyol wrote:
>
> > The point that you are missing is the fact that the point-to-point MPLS
> > tunnels implement an arbitrary IP topology that includes
> multicast traffic.
> > The MPLS topology of the network is optimized according to the
> traffic that
> > runs on top of the physical links including IP multicast.
> Therefore one does
> > not need to add an MPLS multicast tree.
>
> Bora, I agree with you that you could use point-to-point tunnel to carry
> multicast traffic. Similarily, I could  also argue why not
> duplicate the packet
> at source
> and unicast them  one by one to all the receivers.
>
> But I would think sending a packet through a point-to-multipoint
> tree is more
> efficient than duplicating the packet at ingress and send them through the
> MULTIPLE point-to-point MPLS tunnels.
>
> >
> >
> > I believe that this draft confuses MPLS multicast with IP
> multicast while
> > implying that one needs to build an MPLS multicast tree to efficiently
> > perform IP multicast which is untrue. MPLS tunnels when
> designed take into
> > account IP multicast traffic as well.
> >
>
> This draft provides only ONE method on how to manage multicast traffic
> in a core network.  It proposes using MPLS point-to-multipoint tree
> to transport multicast traffic through a core ISP network.
>
> best regars,
> Liwen--
>
> >
> > Regards
> >
> > Bora
> >
> > > -----Original Message-----
> > > From: liwenwu@adn.alcatel.com
> [mailto:liwenwu@adn.alcatel.com]On Behalf
> > > Of LiWen Wu
> > > Sent: Thursday, June 17, 1999 10:57 AM
> > > To: Bora Akyol
> > > Cc: liwen wu; mpls@UU.NET; te-wg@avici.com; idmr@cs.ucl.ac.uk
> > > Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
> > >
> > >
> > > Bora Akyol wrote:
> > >
> > > > Comments:
> > > >
> > > > 1) Is the multicast traffic included in the statistics that
> are used to
> > > > create the traffic matrix which in turn is used to create the
> > > desired MPLS
> > > > topology?
> > >
> > > Yes. But as  I am aware of today, all traffic engineereing
> > > related drafts only
> > > deal with
> > > point-to-point MPLS tunnel.
> > >
> > > This paper propose building a point-to-multipoint MPLS tree
> to carry the
> > > multicast traffic through the core network.
> > >
> > > These trees are traffic engineered to avoid congested node and
> > > links . They
> > > also can be engineered to meet certain QOS requirement.
> > >
> > > There is another big advantage by using this concept that:
> > >
> > > 1)  All the routers inside a core ISP domain DOES NOT need to be
> > > aware of all the multicast groups and sources. (Similar to a
> core router
> > > only aware of OSPF routes, but does not need to know all the
> BGP routes)
> > >
> > > 2) Only border routers(root and receivers) need to know all the
> > > multicast groups and sources , mappings from multicast group
> and sources
> > > to MPLS point-to-multipoint TREEs.
> > >
> > > best regards,
> > > Liwen--
> > >
> > > >
> > > >
> > > > If the answer to this is *yes*, then ordinary traffic
> engineering will
> > > > optimize the traffic flows such that you will *get* a good
> > > distribution of
> > > > the multicast flows over the existing physical topology. So the
> > > procedures
> > > > proposed in this draft are not needed.
> > > >
> > > > If the answer is *no* then the solution may be covered in
> this draft.
> > > >
> > > > I personally don't see a need for this draft or the methods
> > > proposed in it.
> > > > In most cases, the traffic matrix will actually include the
> multicast
> > > > traffic and will optimize the MPLS topology accordingly.
> > > Otherwise, you will
> > > > end up with one multicast topology and one unicast topology and
> > > yet another
> > > > network to manage.
> > > >
> > > > If we want to make multicast routing more efficient, we should
> > > follow along
> > > > the lines **-omp drafts and create a multicast routing
> > > algorithm that runs
> > > > within an area and
> > > > is sensitive to network utilization.
> > > >
> > > > Bora
> > >
> > > --
> > >
> --------------------------------------------------------------------------
> > > Liwen Wu                                     Phone: (703) 724-2619
> > > Alcatel U.S.A                                FAX:   (703) 724-2005
> > > 44983 Knoll Square                  Inet:  liwen.wu@adn.alcatel.com
> > > Ashburn, Va. 20147
> > > USA
> > > ------------------------------------------------------------------
> > > ----------
> > >
> > >
> > >
> > >
>
> --
> --------------------------------------------------------------------------
> Liwen Wu                                     Phone: (703) 724-2619
> Alcatel U.S.A                                FAX:   (703) 724-2005
> 44983 Knoll Square                  Inet:  liwen.wu@adn.alcatel.com
> Ashburn, Va. 20147
> USA
> ------------------------------------------------------------------
> ----------
>
>
>
>



From owner-idmr@cs.ucl.ac.uk  Thu Jun 17 17:25:28 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA02875
	for <idmr-archive@lists.ietf.org>; Thu, 17 Jun 1999 17:25:27 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.01076-0@pan2.cs.ucl.ac.uk>;
          Thu, 17 Jun 1999 22:12:28 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.01070-0@pan2.cs.ucl.ac.uk>; Thu, 17 Jun 1999 22:12:23 +0100
Received: from host66.pluris.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.19543-0@bells.cs.ucl.ac.uk>; Thu, 17 Jun 1999 22:12:40 +0100
Received: from akyol ([172.16.55.150]) by yarilo.pluris.com (8.9.2/8.9.1) 
          with SMTP id OAA13691; Thu, 17 Jun 1999 14:11:53 -0700 (PDT)
From: Bora Akyol <akyol@pluris.com>
To: LiWen Wu <liwen.wu@adn.alcatel.com>
Cc: mpls <mpls@UU.NET>, te-wg <te-wg@avici.com>, idmr <idmr@cs.ucl.ac.uk>
Subject: RE: Question on draft-wu-mpls-multicast-te-00.txt
Date: Thu, 17 Jun 1999 14:13:14 -0700
Message-ID: <001101beb906$36bc3940$963710ac@pluris.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
In-Reply-To: <37695C35.A5CBC5DD@adn.alcatel.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

There are some comments later in this email, but I believe that this ID is
trying to address the following:

1) How to do multicast in MPLS networks.
2) How to provide QoS to an aggregated set of multicast flows. (Why not use
Diffserv PHBs)

This ID should solve both (1) and (2) but it solves (1) and does not show
*how* multicast flows are aggregated into a small number of MPLS multicast
trees. Moreover, MPLS being designed for tag switching does not provide a
natural method or representation for multicast.

Finally, a multicast routing algorithm such as PIM or a new one (that is
network utilization sensitive) can achieve (2) when Diffserv marking is used
thereby pre-empting the need to do 1.


Now specific comments:
----------------------

If B&D are core routers  and A,C and E are border routers than one would
assume that they have direct connectivity.
So the picture would look like:

---B----D
  / \    \
 A  C     E

If a multicast packet is traversing the network as you mention, I would
agree with you that the multicast scheme is more efficient, but, this is
solving the MPLS multicast problem not a traffic engineering problem. The
efficiency is not a property associated with traffic engineering but in
general associated with multicast.

In this case, it is much easier to let IP routers do **routing** and not
associate the multicast with MPLS tunnels. As an added bonus you have only
one multicast routing algorithm to use instead of an IP and an MPLS
algorithm.

Again, multicast is dynamic and should not be associated with MPLS tunnels
which are intended for quasi-static situations.

Finally, maybe the title of the ID should be changed to:

Multicast in MPLS networks

Thanks

Bora


> -----Original Message-----
> From: liwenwu@adn.alcatel.com [mailto:liwenwu@adn.alcatel.com]On Behalf
> Of LiWen Wu
> Sent: Thursday, June 17, 1999 1:36 PM
> To: Bora Akyol
> Cc: mpls@UU.NET; te-wg@avici.com; idmr@cs.ucl.ac.uk
> Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
>
>
> Hello Bora,
>
>    Let me try to explain with one following simple example:
>
> A--->B---->C
>                 |
>                 D---->E
>
> A,C,E are border routers, B,D are core routers.
>
> I could build:
>
> 1) Tunnel 1- {A,B,C} to carry the unicast traffic
> which enters the network from A and exit the
> network through C
>
> 2) Tunnel 2 - {A,B,D,E} to carry the  unicast traffic
> which enters the network  from A and exit the
> network through E
>
> 3) Tree1 - {A,{B, C}, {B,D,E}} to carry the multicast traffic
> which enters the network from A and exit the
> network through C and E.
>
> For a multicast flow which enters the network from A and
> exits from the network through E and C, I would think
> put it through Tree1 is more efficient than
> duplicate it at A and sent them through Tunnel1 and Tunnel2.
>
> best regards,
> Liwen--
>
>
>
>
> Bora Akyol wrote:
>
> > Liwen,
> >
> > Let me try explaing this again:
> >
> > 1. There is an IP network consisting of N nodes (N>=2).
> > 2. There is an MPLS topology over which the IP packets flow
> over including
> > multicast packets.
> > 3. There is a statistics collection process that collects a
> traffic matrix
> > (NxN) for all of IP traffic that is flowing between the nodes of an area
> > like you will find in a backbone topology.
> > 4. The optimization process uses 1 and 3 to produce 2 and in
> the meantime
> > configures the network such that all data flow demands are satisfied
> > optimally (including MPLS packets).
> >
> > What is being suggested in this draft results in another
> version of the MPLS
> > topology in addition to (2) but in fact it does *NOT* optimize
> significantly
> > better than the current traffic engineering approaches but
> results in two
> > (overlay) networks.
> >
> > Nowhere in my email, do I suggest that you abandon IP level
> multicast and
> > use unicast, so I don't understand the last comment that you are making.
> > What I am suggesting is that IP Multicast traffic can flow over
> the traffic
> > engineered network just as well as the unicast traffic. This is
> *especially*
> > true in a backbone network.
> >
> > Moreover, as multicast traffic is dynamic and can change
> rapidly, I don't
> > see the point of *multicast* traffic engineering which is assumed to be
> > quasi-static.
> >
> > What this ID sounds like is a way of doing MPLS multicast as
> you would see
> > in an ATM network which is fine, but is not related to traffic
> engineering.
> >
> > Regards
> >
> > Bora
> >
> > > -----Original Message-----
> > > From: liwenwu@adn.alcatel.com
> [mailto:liwenwu@adn.alcatel.com]On Behalf
> > > Of LiWen Wu
> > > Sent: Thursday, June 17, 1999 11:28 AM
> > > To: Bora Akyol
> > > Cc: liwen wu; mpls@UU.NET; te-wg@avici.com; idmr@cs.ucl.ac.uk
> > > Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
> > >
> > >
> > > Bora Akyol wrote:
> > >
> > > > The point that you are missing is the fact that the
> point-to-point MPLS
> > > > tunnels implement an arbitrary IP topology that includes
> > > multicast traffic.
> > > > The MPLS topology of the network is optimized according to the
> > > traffic that
> > > > runs on top of the physical links including IP multicast.
> > > Therefore one does
> > > > not need to add an MPLS multicast tree.
> > >
> > > Bora, I agree with you that you could use point-to-point
> tunnel to carry
> > > multicast traffic. Similarily, I could  also argue why not
> > > duplicate the packet
> > > at source
> > > and unicast them  one by one to all the receivers.
> > >
> > > But I would think sending a packet through a point-to-multipoint
> > > tree is more
> > > efficient than duplicating the packet at ingress and send
> them through the
> > > MULTIPLE point-to-point MPLS tunnels.
> > >
> > > >
> > > >
> > > > I believe that this draft confuses MPLS multicast with IP
> > > multicast while
> > > > implying that one needs to build an MPLS multicast tree to
> efficiently
> > > > perform IP multicast which is untrue. MPLS tunnels when
> > > designed take into
> > > > account IP multicast traffic as well.
> > > >
> > >
> > > This draft provides only ONE method on how to manage multicast traffic
> > > in a core network.  It proposes using MPLS point-to-multipoint tree
> > > to transport multicast traffic through a core ISP network.
> > >
> > > best regars,
> > > Liwen--
> > >
> > > >
> > > > Regards
> > > >
> > > > Bora
> > > >
> > > > > -----Original Message-----
> > > > > From: liwenwu@adn.alcatel.com
> > > [mailto:liwenwu@adn.alcatel.com]On Behalf
> > > > > Of LiWen Wu
> > > > > Sent: Thursday, June 17, 1999 10:57 AM
> > > > > To: Bora Akyol
> > > > > Cc: liwen wu; mpls@UU.NET; te-wg@avici.com; idmr@cs.ucl.ac.uk
> > > > > Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
> > > > >
> > > > >
> > > > > Bora Akyol wrote:
> > > > >
> > > > > > Comments:
> > > > > >
> > > > > > 1) Is the multicast traffic included in the statistics that
> > > are used to
> > > > > > create the traffic matrix which in turn is used to create the
> > > > > desired MPLS
> > > > > > topology?
> > > > >
> > > > > Yes. But as  I am aware of today, all traffic engineereing
> > > > > related drafts only
> > > > > deal with
> > > > > point-to-point MPLS tunnel.
> > > > >
> > > > > This paper propose building a point-to-multipoint MPLS tree
> > > to carry the
> > > > > multicast traffic through the core network.
> > > > >
> > > > > These trees are traffic engineered to avoid congested node and
> > > > > links . They
> > > > > also can be engineered to meet certain QOS requirement.
> > > > >
> > > > > There is another big advantage by using this concept that:
> > > > >
> > > > > 1)  All the routers inside a core ISP domain DOES NOT need to be
> > > > > aware of all the multicast groups and sources. (Similar to a
> > > core router
> > > > > only aware of OSPF routes, but does not need to know all the
> > > BGP routes)
> > > > >
> > > > > 2) Only border routers(root and receivers) need to know all the
> > > > > multicast groups and sources , mappings from multicast group
> > > and sources
> > > > > to MPLS point-to-multipoint TREEs.
> > > > >
> > > > > best regards,
> > > > > Liwen--
> > > > >
> > > > > >
> > > > > >
> > > > > > If the answer to this is *yes*, then ordinary traffic
> > > engineering will
> > > > > > optimize the traffic flows such that you will *get* a good
> > > > > distribution of
> > > > > > the multicast flows over the existing physical topology. So the
> > > > > procedures
> > > > > > proposed in this draft are not needed.
> > > > > >
> > > > > > If the answer is *no* then the solution may be covered in
> > > this draft.
> > > > > >
> > > > > > I personally don't see a need for this draft or the methods
> > > > > proposed in it.
> > > > > > In most cases, the traffic matrix will actually include the
> > > multicast
> > > > > > traffic and will optimize the MPLS topology accordingly.
> > > > > Otherwise, you will
> > > > > > end up with one multicast topology and one unicast topology and
> > > > > yet another
> > > > > > network to manage.
> > > > > >
> > > > > > If we want to make multicast routing more efficient, we should
> > > > > follow along
> > > > > > the lines **-omp drafts and create a multicast routing
> > > > > algorithm that runs
> > > > > > within an area and
> > > > > > is sensitive to network utilization.
> > > > > >
> > > > > > Bora
> > > > >
> > > > > --
> > > > >
> > >
> --------------------------------------------------------------------------
> > > > > Liwen Wu                                     Phone: (703) 724-2619
> > > > > Alcatel U.S.A                                FAX:   (703) 724-2005
> > > > > 44983 Knoll Square                  Inet:
> liwen.wu@adn.alcatel.com
> > > > > Ashburn, Va. 20147
> > > > > USA
> > > > > ------------------------------------------------------------------
> > > > > ----------
> > > > >
> > > > >
> > > > >
> > > > >
> > >
> > > --
> > >
> --------------------------------------------------------------------------
> > > Liwen Wu                                     Phone: (703) 724-2619
> > > Alcatel U.S.A                                FAX:   (703) 724-2005
> > > 44983 Knoll Square                  Inet:  liwen.wu@adn.alcatel.com
> > > Ashburn, Va. 20147
> > > USA
> > > ------------------------------------------------------------------
> > > ----------
> > >
> > >
> > >
> > >
>
> --
> --------------------------------------------------------------------------
> Liwen Wu                                     Phone: (703) 724-2619
> Alcatel U.S.A                                FAX:   (703) 724-2005
> 44983 Knoll Square                  Inet:  liwen.wu@adn.alcatel.com
> Ashburn, Va. 20147
> USA
> ------------------------------------------------------------------
> ----------
>
>
>
>



From owner-idmr@cs.ucl.ac.uk  Thu Jun 17 21:35:56 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA04165
	for <idmr-archive@lists.ietf.org>; Thu, 17 Jun 1999 21:35:55 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.02000-0@pan2.cs.ucl.ac.uk>;
          Fri, 18 Jun 1999 00:07:10 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.01994-0@pan2.cs.ucl.ac.uk>; Fri, 18 Jun 1999 00:07:02 +0100
Received: from host66.pluris.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.29459-0@bells.cs.ucl.ac.uk>; Fri, 18 Jun 1999 00:07:20 +0100
Received: from akyol (akyol.pluris.com [172.16.50.115]) 
          by yarilo.pluris.com (8.9.2/8.9.1) with SMTP id QAA20585;
          Thu, 17 Jun 1999 16:06:27 -0700 (PDT)
From: Bora Akyol <akyol@pluris.com>
To: Indra Widjaja <iwidjaja@tddny.fujitsu.com>
Cc: LiWen Wu <liwen.wu@adn.alcatel.com>, mpls <mpls@UU.NET>,
        te-wg <te-wg@avici.com>, idmr <idmr@cs.ucl.ac.uk>
Subject: RE: Question on draft-wu-mpls-multicast-te-00.txt
Date: Thu, 17 Jun 1999 16:07:52 -0700
Message-ID: <000301beb916$3a0b7100$733210ac@pluris.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
In-Reply-To: <37697E38.EFAA140A@tddny.fujitsu.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

That is a primary purpose of having an MPLS-based network.
You may want to check out the slides from MPLS' 98 workshop.

You can the statistics by the LSP groups that are going between the border
LSRs in a traffic-engineered MPLS network.

Regards

Bora


> -----Original Message-----
> From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Indra
> Widjaja
> Sent: Thursday, June 17, 1999 4:01 PM
> To: Bora Akyol
> Cc: LiWen Wu; mpls@UU.NET; te-wg@avici.com; idmr@cs.ucl.ac.uk
> Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
>
>
> Bora Akyol wrote:
>
> > Liwen,
> >
> > Let me try explaing this again:
> >
> > 1. There is an IP network consisting of N nodes (N>=2).
> > 2. There is an MPLS topology over which the IP packets flow
> over including
> > multicast packets.
> > 3. There is a statistics collection process that collects a
> traffic matrix
> > (NxN) for all of IP traffic that is flowing between the nodes of an area
> > like you will find in a backbone topology.
>
> Bora:
> If I understand your point on number 3, you assume that you can
> collect the
> current
> traffic statistics for every ingress-egress pair (for a given class of
> service).
> How do you propose to do this?
>
> indra
>
>
> >
> > 4. The optimization process uses 1 and 3 to produce 2 and in
> the meantime
> > configures the network such that all data flow demands are satisfied
> > optimally (including MPLS packets).
> >
> > What is being suggested in this draft results in another
> version of the MPLS
> > topology in addition to (2) but in fact it does *NOT* optimize
> significantly
> > better than the current traffic engineering approaches but
> results in two
> > (overlay) networks.
> >
> > Nowhere in my email, do I suggest that you abandon IP level
> multicast and
> > use unicast, so I don't understand the last comment that you are making.
> > What I am suggesting is that IP Multicast traffic can flow over
> the traffic
> > engineered network just as well as the unicast traffic. This is
> *especially*
> > true in a backbone network.
> >
> > Moreover, as multicast traffic is dynamic and can change
> rapidly, I don't
> > see the point of *multicast* traffic engineering which is assumed to be
> > quasi-static.
> >
> > What this ID sounds like is a way of doing MPLS multicast as
> you would see
> > in an ATM network which is fine, but is not related to traffic
> engineering.
> >
> > Regards
> >
> > Bora
> >
> >
>
>



From owner-idmr@cs.ucl.ac.uk  Thu Jun 17 21:36:09 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA04176
	for <idmr-archive@lists.ietf.org>; Thu, 17 Jun 1999 21:36:09 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.02314-0@pan2.cs.ucl.ac.uk>;
          Fri, 18 Jun 1999 00:35:13 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.02308-0@pan2.cs.ucl.ac.uk>; Fri, 18 Jun 1999 00:35:06 +0100
Received: from host66.pluris.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.01239-0@bells.cs.ucl.ac.uk>; Fri, 18 Jun 1999 00:35:24 +0100
Received: from akyol (akyol.pluris.com [172.16.50.115]) 
          by yarilo.pluris.com (8.9.2/8.9.1) with SMTP id QAA22000;
          Thu, 17 Jun 1999 16:34:47 -0700 (PDT)
From: Bora Akyol <akyol@pluris.com>
To: Indra Widjaja <iwidjaja@tddny.fujitsu.com>
Cc: LiWen Wu <liwen.wu@adn.alcatel.com>, mpls <mpls@UU.NET>,
        te-wg <te-wg@avici.com>, idmr <idmr@cs.ucl.ac.uk>
Subject: RE: Question on draft-wu-mpls-multicast-te-00.txt
Date: Thu, 17 Jun 1999 16:36:13 -0700
Message-ID: <000401beb91a$2f9d9fa0$733210ac@pluris.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
In-Reply-To: <376984DA.6F380D2A@tddny.fujitsu.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

In a backbone traffic engineered network, my assumption was that
there are only explicitly routed LSPs so my statement is correct if this
assumption is satisfied.

Anyone planning on running plain LDP in the backbone in addition to RSVP or
CR-LDP?

Bora


> -----Original Message-----
> From: Indra Widjaja [mailto:Indra.Widjaja@tddny.fujitsu.com]On Behalf Of
> Indra Widjaja
> Sent: Thursday, June 17, 1999 4:30 PM
> To: Bora Akyol
> Cc: LiWen Wu; mpls@UU.NET; te-wg@avici.com; idmr@cs.ucl.ac.uk
> Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
>
>
> Bora:
>
>
> > That is a primary purpose of having an MPLS-based network.
> > You may want to check out the slides from MPLS' 98 workshop.
>
> I was in that workshop and was not aware about any credible discussion
> pertaining to
> traffic matrix collection.
>
> >
> >
> > You can the statistics by the LSP groups that are going between
> the border
> > LSRs in a traffic-engineered MPLS network.
>
> If you only collect the statistics on traffic engineered LSPs
> between border
> LSRs, then you
> won't see the whole picture (i.e., you won't be able to build the
> NxN traffic
> matrix) since
> there are other traffic flows (e.g., the ones that go through
> hop-by-hop LSPs).
>
> The problem is further compounded if you need to build a traffic
> matrix for
> each class.
>
> indra
>
>
> >
> >
> > Regards
> >
> > Bora
> >
> > > -----Original Message-----
> > > From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Indra
> > > Widjaja
> > > Sent: Thursday, June 17, 1999 4:01 PM
> > > To: Bora Akyol
> > > Cc: LiWen Wu; mpls@UU.NET; te-wg@avici.com; idmr@cs.ucl.ac.uk
> > > Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
> > >
> > >
> > > Bora Akyol wrote:
> > >
> > > > Liwen,
> > > >
> > > > Let me try explaing this again:
> > > >
> > > > 1. There is an IP network consisting of N nodes (N>=2).
> > > > 2. There is an MPLS topology over which the IP packets flow
> > > over including
> > > > multicast packets.
> > > > 3. There is a statistics collection process that collects a
> > > traffic matrix
> > > > (NxN) for all of IP traffic that is flowing between the
> nodes of an area
> > > > like you will find in a backbone topology.
> > >
> > > Bora:
> > > If I understand your point on number 3, you assume that you can
> > > collect the
> > > current
> > > traffic statistics for every ingress-egress pair (for a given class of
> > > service).
> > > How do you propose to do this?
> > >
> > > indra
> > >
> > >
> > > >
> > > > 4. The optimization process uses 1 and 3 to produce 2 and in
> > > the meantime
> > > > configures the network such that all data flow demands are satisfied
> > > > optimally (including MPLS packets).
> > > >
> > > > What is being suggested in this draft results in another
> > > version of the MPLS
> > > > topology in addition to (2) but in fact it does *NOT* optimize
> > > significantly
> > > > better than the current traffic engineering approaches but
> > > results in two
> > > > (overlay) networks.
> > > >
> > > > Nowhere in my email, do I suggest that you abandon IP level
> > > multicast and
> > > > use unicast, so I don't understand the last comment that
> you are making.
> > > > What I am suggesting is that IP Multicast traffic can flow over
> > > the traffic
> > > > engineered network just as well as the unicast traffic. This is
> > > *especially*
> > > > true in a backbone network.
> > > >
> > > > Moreover, as multicast traffic is dynamic and can change
> > > rapidly, I don't
> > > > see the point of *multicast* traffic engineering which is
> assumed to be
> > > > quasi-static.
> > > >
> > > > What this ID sounds like is a way of doing MPLS multicast as
> > > you would see
> > > > in an ATM network which is fine, but is not related to traffic
> > > engineering.
> > > >
> > > > Regards
> > > >
> > > > Bora
> > > >
> > > >
> > >
> > >
>
>



From owner-idmr@cs.ucl.ac.uk  Thu Jun 17 21:36:18 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA04187
	for <idmr-archive@lists.ietf.org>; Thu, 17 Jun 1999 21:36:18 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.01937-0@pan2.cs.ucl.ac.uk>;
          Fri, 18 Jun 1999 00:01:10 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.01931-0@pan2.cs.ucl.ac.uk>; Fri, 18 Jun 1999 00:01:04 +0100
Received: from 167.254.240.105 by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.26726-0@bells.cs.ucl.ac.uk>; Fri, 18 Jun 1999 00:01:20 +0100
Received: from tddny.fujitsu.com ([167.254.240.44]) 
          by java.tddny.fujitsu.com (Netscape Messaging Server 3.6) with ESMTP 
          id AAA7286; Thu, 17 Jun 1999 19:01:09 -0400
Message-ID: <37697E38.EFAA140A@tddny.fujitsu.com>
Date: Thu, 17 Jun 1999 19:01:12 -0400
From: Indra Widjaja <iwidjaja@tddny.fujitsu.com>
Organization: Fujitsu Network Communications
X-Mailer: Mozilla 4.51 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Bora Akyol <akyol@pluris.com>
CC: LiWen Wu <liwen.wu@adn.alcatel.com>, mpls@UU.NET, te-wg@avici.com,
        idmr@cs.ucl.ac.uk
Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
References: <005501beb8f9$2e29a040$963710ac@pluris.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bora Akyol wrote:

> Liwen,
>
> Let me try explaing this again:
>
> 1. There is an IP network consisting of N nodes (N>=2).
> 2. There is an MPLS topology over which the IP packets flow over including
> multicast packets.
> 3. There is a statistics collection process that collects a traffic matrix
> (NxN) for all of IP traffic that is flowing between the nodes of an area
> like you will find in a backbone topology.

Bora:
If I understand your point on number 3, you assume that you can collect the
current
traffic statistics for every ingress-egress pair (for a given class of
service).
How do you propose to do this?

indra


>
> 4. The optimization process uses 1 and 3 to produce 2 and in the meantime
> configures the network such that all data flow demands are satisfied
> optimally (including MPLS packets).
>
> What is being suggested in this draft results in another version of the MPLS
> topology in addition to (2) but in fact it does *NOT* optimize significantly
> better than the current traffic engineering approaches but results in two
> (overlay) networks.
>
> Nowhere in my email, do I suggest that you abandon IP level multicast and
> use unicast, so I don't understand the last comment that you are making.
> What I am suggesting is that IP Multicast traffic can flow over the traffic
> engineered network just as well as the unicast traffic. This is *especially*
> true in a backbone network.
>
> Moreover, as multicast traffic is dynamic and can change rapidly, I don't
> see the point of *multicast* traffic engineering which is assumed to be
> quasi-static.
>
> What this ID sounds like is a way of doing MPLS multicast as you would see
> in an ATM network which is fine, but is not related to traffic engineering.
>
> Regards
>
> Bora
>
>



From owner-idmr@cs.ucl.ac.uk  Thu Jun 17 21:36:26 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA04198
	for <idmr-archive@lists.ietf.org>; Thu, 17 Jun 1999 21:36:25 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.02210-0@pan2.cs.ucl.ac.uk>;
          Fri, 18 Jun 1999 00:31:05 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.02202-0@pan2.cs.ucl.ac.uk>; Fri, 18 Jun 1999 00:30:58 +0100
Received: from postman.adn.alcatel.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.00848-0@bells.cs.ucl.ac.uk>; Fri, 18 Jun 1999 00:31:10 +0100
Received: from localhost (root@localhost) by adn.alcatel.com 
          with SMTP (8.7.6/8.7.1) id TAA20519;
          Thu, 17 Jun 1999 19:25:32 -0400 (EDT)
From: Alex.Mondrus@adn.alcatel.com
X-OpenMail-Hops: 1
Date: Thu, 17 Jun 1999 19:25:20 -0400
Message-Id: <H00005cf01503aec@MHS>
In-Reply-To: <000301beb916$3a0b7100$733210ac@pluris.com>
Subject: RE: Question on draft-wu-mpls-multicast-te-00.txt
MIME-Version: 1.0
TO: akyol@pluris.com
CC: idmr@cs.ucl.ac.uk, iwidjaja@tddny.fujitsu.com, mpls@UU.NET,
        te-wg@avici.com, Liwen.Wu@adn.alcatel.com
Content-Type: text/plain; charset=US-ASCII; name="RE:"
Content-Disposition: inline; filename="RE:"
Content-Transfer-Encoding: 7bit
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

Since you know that, so Can you share it with us ? Can you tell us a
little bit more on this ? I did not quite understand your last message

thank you,
Alex Mondrus 




> That is a primary purpose of having an MPLS-based network.
> You may want to check out the slides from MPLS' 98 workshop.
> 
> You can the statistics by the LSP groups that are going between the
border
> LSRs in a traffic-engineered MPLS network.
> 
> Regards
> 
> Bora
> 
> 
> > -----Original Message-----
> > From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Indra
> > Widjaja
> > Sent: Thursday, June 17, 1999 4:01 PM
> > To: Bora Akyol
> > Cc: LiWen Wu; mpls@UU.NET; te-wg@avici.com; idmr@cs.ucl.ac.uk
> > Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
> >
> >
> > Bora Akyol wrote:
> >
> > > Liwen,
> > >
> > > Let me try explaing this again:
> > >
> > > 1. There is an IP network consisting of N nodes (N>=2).
> > > 2. There is an MPLS topology over which the IP packets flow
> > over including
> > > multicast packets.
> > > 3. There is a statistics collection process that collects a
> > traffic matrix
> > > (NxN) for all of IP traffic that is flowing between the nodes of
an area
> > > like you will find in a backbone topology.
> >
> > Bora:
> > If I understand your point on number 3, you assume that you can
> > collect the
> > current
> > traffic statistics for every ingress-egress pair (for a given class
of
> > service).
> > How do you propose to do this?
> >
> > indra
> >
> >
> > >
> > > 4. The optimization process uses 1 and 3 to produce 2 and in
> > the meantime
> > > configures the network such that all data flow demands are
satisfied
> > > optimally (including MPLS packets).
> > >
> > > What is being suggested in this draft results in another
> > version of the MPLS
> > > topology in addition to (2) but in fact it does *NOT* optimize
> > significantly
> > > better than the current traffic engineering approaches but
> > results in two
> > > (overlay) networks.
> > >
> > > Nowhere in my email, do I suggest that you abandon IP level
> > multicast and
> > > use unicast, so I don't understand the last comment that you are
making.
> > > What I am suggesting is that IP Multicast traffic can flow over
> > the traffic
> > > engineered network just as well as the unicast traffic. This is
> > *especially*
> > > true in a backbone network.
> > >
> > > Moreover, as multicast traffic is dynamic and can change
> > rapidly, I don't
> > > see the point of *multicast* traffic engineering which is assumed
to be
> > > quasi-static.
> > >
> > > What this ID sounds like is a way of doing MPLS multicast as
> > you would see
> > > in an ATM network which is fine, but is not related to traffic
> > engineering.
> > >
> > > Regards
> > >
> > > Bora
> > >
> > >
> >
> >
> 



From owner-idmr@cs.ucl.ac.uk  Thu Jun 17 21:38:21 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA04231
	for <idmr-archive@lists.ietf.org>; Thu, 17 Jun 1999 21:38:20 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.02496-0@pan2.cs.ucl.ac.uk>;
          Fri, 18 Jun 1999 00:46:57 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.02490-0@pan2.cs.ucl.ac.uk>; Fri, 18 Jun 1999 00:46:49 +0100
Received: from 131.112.32.132 by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.01944-0@bells.cs.ucl.ac.uk>; Fri, 18 Jun 1999 00:47:06 +0100
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <199906172333.IAA18050@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1) id IAA18050;
          Fri, 18 Jun 1999 08:33:00 +0900
Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
To: braja@ccrl.nj.nec.com
Date: Fri, 18 Jun 99 8:33:00 JST
Cc: akyol@pluris.com, liwen.wu@adn.alcatel.com, mpls@UU.NET, te-wg@avici.com,
        idmr@cs.ucl.ac.uk
In-Reply-To: <37696504.51C4253A@ccrl.nj.nec.com>; from "Bala Rajagopalan" at Jun 17, 99 5:13 pm
X-Mailer: ELM [version 2.3 PL11]
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

Bala;

> > 1. There is an IP network consisting of N nodes (N>=2).
> > 2. There is an MPLS topology over which the IP packets flow over including
> > multicast packets.
> > 3. There is a statistics collection process that collects a traffic matrix
> > (NxN) for all of IP traffic that is flowing between the nodes of an area
> > like you will find in a backbone topology.
> > 4. The optimization process uses 1 and 3 to produce 2 and in the meantime
> > configures the network such that all data flow demands are satisfied
> > optimally (including MPLS packets).
> 
> What's not clear to me is how you'd implement (4).

????

3 is already wrong.

If it is multicast, the traffic matrix is (Nx2^(N-1)), which is
the number of labels required for MPLS.

That is, multicast with MPLS is with more than 20 nodes is nothing
more than a silly joke.

But, it is not a problem, because best effort unicast MPLS is a
silly joke from the beginning.

							Masataka Ohta


From owner-idmr@cs.ucl.ac.uk  Thu Jun 17 21:38:36 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA04242
	for <idmr-archive@lists.ietf.org>; Thu, 17 Jun 1999 21:38:35 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.02188-0@pan2.cs.ucl.ac.uk>;
          Fri, 18 Jun 1999 00:29:26 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.02179-0@pan2.cs.ucl.ac.uk>; Fri, 18 Jun 1999 00:29:16 +0100
Received: from 167.254.240.105 by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.00763-0@bells.cs.ucl.ac.uk>; Fri, 18 Jun 1999 00:29:33 +0100
Received: from tddny.fujitsu.com ([167.254.240.44]) 
          by java.tddny.fujitsu.com (Netscape Messaging Server 3.6) with ESMTP 
          id AAA1894; Thu, 17 Jun 1999 19:29:28 -0400
Message-ID: <376984DA.6F380D2A@tddny.fujitsu.com>
Date: Thu, 17 Jun 1999 19:29:30 -0400
From: Indra Widjaja <iwidjaja@tddny.fujitsu.com>
Organization: Fujitsu Network Communications
X-Mailer: Mozilla 4.51 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Bora Akyol <akyol@pluris.com>
CC: LiWen Wu <liwen.wu@adn.alcatel.com>, mpls@UU.NET, te-wg@avici.com,
        idmr@cs.ucl.ac.uk
Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
References: <000301beb916$3a0b7100$733210ac@pluris.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bora:


> That is a primary purpose of having an MPLS-based network.
> You may want to check out the slides from MPLS' 98 workshop.

I was in that workshop and was not aware about any credible discussion
pertaining to
traffic matrix collection.

>
>
> You can the statistics by the LSP groups that are going between the border
> LSRs in a traffic-engineered MPLS network.

If you only collect the statistics on traffic engineered LSPs between border
LSRs, then you
won't see the whole picture (i.e., you won't be able to build the NxN traffic
matrix) since
there are other traffic flows (e.g., the ones that go through hop-by-hop LSPs).

The problem is further compounded if you need to build a traffic matrix for
each class.

indra


>
>
> Regards
>
> Bora
>
> > -----Original Message-----
> > From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Indra
> > Widjaja
> > Sent: Thursday, June 17, 1999 4:01 PM
> > To: Bora Akyol
> > Cc: LiWen Wu; mpls@UU.NET; te-wg@avici.com; idmr@cs.ucl.ac.uk
> > Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
> >
> >
> > Bora Akyol wrote:
> >
> > > Liwen,
> > >
> > > Let me try explaing this again:
> > >
> > > 1. There is an IP network consisting of N nodes (N>=2).
> > > 2. There is an MPLS topology over which the IP packets flow
> > over including
> > > multicast packets.
> > > 3. There is a statistics collection process that collects a
> > traffic matrix
> > > (NxN) for all of IP traffic that is flowing between the nodes of an area
> > > like you will find in a backbone topology.
> >
> > Bora:
> > If I understand your point on number 3, you assume that you can
> > collect the
> > current
> > traffic statistics for every ingress-egress pair (for a given class of
> > service).
> > How do you propose to do this?
> >
> > indra
> >
> >
> > >
> > > 4. The optimization process uses 1 and 3 to produce 2 and in
> > the meantime
> > > configures the network such that all data flow demands are satisfied
> > > optimally (including MPLS packets).
> > >
> > > What is being suggested in this draft results in another
> > version of the MPLS
> > > topology in addition to (2) but in fact it does *NOT* optimize
> > significantly
> > > better than the current traffic engineering approaches but
> > results in two
> > > (overlay) networks.
> > >
> > > Nowhere in my email, do I suggest that you abandon IP level
> > multicast and
> > > use unicast, so I don't understand the last comment that you are making.
> > > What I am suggesting is that IP Multicast traffic can flow over
> > the traffic
> > > engineered network just as well as the unicast traffic. This is
> > *especially*
> > > true in a backbone network.
> > >
> > > Moreover, as multicast traffic is dynamic and can change
> > rapidly, I don't
> > > see the point of *multicast* traffic engineering which is assumed to be
> > > quasi-static.
> > >
> > > What this ID sounds like is a way of doing MPLS multicast as
> > you would see
> > > in an ATM network which is fine, but is not related to traffic
> > engineering.
> > >
> > > Regards
> > >
> > > Bora
> > >
> > >
> >
> >



From owner-idmr@cs.ucl.ac.uk  Fri Jun 18 01:44:30 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA13105
	for <idmr-archive@lists.ietf.org>; Fri, 18 Jun 1999 01:44:29 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.04306-0@pan2.cs.ucl.ac.uk>;
          Fri, 18 Jun 1999 03:55:08 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.04300-0@pan2.cs.ucl.ac.uk>; Fri, 18 Jun 1999 03:55:04 +0100
Received: from postman.adn.alcatel.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.10860-0@bells.cs.ucl.ac.uk>; Fri, 18 Jun 1999 03:55:20 +0100
Received: from postal.adn.alcatel.com (postal [198.205.32.56]) 
          by adn.alcatel.com with ESMTP (8.7.6/8.7.1) id WAA26386 
          for <idmr@cs.ucl.ac.uk>; Thu, 17 Jun 1999 22:50:14 -0400 (EDT)
Received: from PC-OK.adn.alcatel.com ([198.205.32.103]) 
          by postal.adn.alcatel.com (Netscape Messaging Server 3.6) with SMTP 
          id AAA4CAC; Thu, 17 Jun 1999 22:56:44 -0400
Message-ID: <3769B676.1D65@adn.alcatel.com>
Date: Thu, 17 Jun 1999 23:01:10 -0400
From: LIWEN WU <liwen.wu@adn.alcatel.com>
X-Mailer: Mozilla 3.01 (Win95; U)
MIME-Version: 1.0
To: Bora Akyol <akyol@pluris.com>
CC: mpls <mpls@UU.NET>, te-wg <te-wg@avici.com>, idmr <idmr@cs.ucl.ac.uk>
Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
References: <001101beb906$36bc3940$963710ac@pluris.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello Bora,

  Please see my comments belows:

Best regards,
Liwen--

Bora Akyol wrote:
> 
> There are some comments later in this email, but I believe that this ID is
> trying to address the following:
> 
> 1) How to do multicast in MPLS networks.
Yes, this draft propose one alternative on how to transport multicast 
traffic efficiently through a core ISP MPLS capable network.

> 2) How to provide QoS to an aggregated set of multicast flows. (Why not use
> Diffserv PHBs)
Yes, a point-to-multipoint tree can be used to carry an aggregated set
of multicast flow with certain QoS constraints.

DiffServ PHB(Per-Hop-Behavior) defines how a packet can be handle by 
a SINGLE node.

This draft describe one method on how a multicast packet can be handled
by a network. It proposes to 1) build a traffic engineering
point-to-multipoint tree
and 2) then tunnel this multicast packet through this
point-to-multipoint tree.
This point-to-multipoint tree is built to avoid congested nodes
and links, and it is also built to meet certain QoS constraint. 

> 
> This ID should solve both (1) and (2) but it solves (1) and does not show
> *how* multicast flows are aggregated into a small number of MPLS multicast
> trees. 
Similar to unicast traffic engineering, the mapping of a multicast flow
to a MPLS multicast tree (tunnel in unicast) is a local policy decision
of the
root router (or ingress router in unicast).

It can be a result of a multicast traffic related SLS(Service Level
Specification) between the core network and their neighbor networks. It
can also be
a result of inter-domain routing protocols(MBGP/MSDP, BGMP) running at
all the border
routers. I agree with you that they are important. But I would think
they should
be addressed in a different document.

 


Moreover, MPLS being designed for tag switching does not provide a
> natural method or representation for multicast.
> 
> Finally, a multicast routing algorithm such as PIM or a new one (that is
> network utilization sensitive) can achieve (2) when Diffserv marking is used
> thereby pre-empting the need to do 1.
> 
> Now specific comments:
> ----------------------
> 
> If B&D are core routers  and A,C and E are border routers than one would
> assume that they have direct connectivity.
> So the picture would look like:
> 
> ---B----D
>   / \    \
>  A  C     E
> 
> If a multicast packet is traversing the network as you mention, I would
> agree with you that the multicast scheme is more efficient, but, this is
> solving the MPLS multicast problem not a traffic engineering problem. The
> efficiency is not a property associated with traffic engineering but in
> general associated with multicast.
> 
> In this case, it is much easier to let IP routers do **routing** and not
> associate the multicast with MPLS tunnels. As an added bonus you have only
> one multicast routing algorithm to use instead of an IP and an MPLS
> algorithm.

Here are a couple of advantages if MPLS tree is used:
1) The core router B,D are not required to know every internet-wide
multicast
groups and sources.

2) The MPLS tree can be traffic engineered(built) to avoid congested
node 
and links. 

3) If a set of multicast flows share the same ingress root and same set
of
egress  node(leafs), they can be tunnelled through a single
point-to-multipoint
tree. This way,the multicast tree states at core router B and D are 
signaficantly reduced.

best regards,
Liwen--

> 
> Again, multicast is dynamic and should not be associated with MPLS tunnels
> which are intended for quasi-static situations.
>
 
> Finally, maybe the title of the ID should be changed to:
> 
> Multicast in MPLS networks
> 
> Thanks
> 
> Bora
> 
> > -----Original Message-----
> > From: liwenwu@adn.alcatel.com [mailto:liwenwu@adn.alcatel.com]On Behalf
> > Of LiWen Wu
> > Sent: Thursday, June 17, 1999 1:36 PM
> > To: Bora Akyol
> > Cc: mpls@UU.NET; te-wg@avici.com; idmr@cs.ucl.ac.uk
> > Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
> >
> >
> > Hello Bora,
> >
> >    Let me try to explain with one following simple example:
> >
> > A--->B---->C
> >                 |
> >                 D---->E
> >
> > A,C,E are border routers, B,D are core routers.
> >
> > I could build:
> >
> > 1) Tunnel 1- {A,B,C} to carry the unicast traffic
> > which enters the network from A and exit the
> > network through C
> >
> > 2) Tunnel 2 - {A,B,D,E} to carry the  unicast traffic
> > which enters the network  from A and exit the
> > network through E
> >
> > 3) Tree1 - {A,{B, C}, {B,D,E}} to carry the multicast traffic
> > which enters the network from A and exit the
> > network through C and E.
> >
> > For a multicast flow which enters the network from A and
> > exits from the network through E and C, I would think
> > put it through Tree1 is more efficient than
> > duplicate it at A and sent them through Tunnel1 and Tunnel2.
> >
> > best regards,
> > Liwen--
> >
> >
> >
> >
> > Bora Akyol wrote:
> >
> > > Liwen,
> > >
> > > Let me try explaing this again:
> > >
> > > 1. There is an IP network consisting of N nodes (N>=2).
> > > 2. There is an MPLS topology over which the IP packets flow
> > over including
> > > multicast packets.
> > > 3. There is a statistics collection process that collects a
> > traffic matrix
> > > (NxN) for all of IP traffic that is flowing between the nodes of an area
> > > like you will find in a backbone topology.
> > > 4. The optimization process uses 1 and 3 to produce 2 and in
> > the meantime
> > > configures the network such that all data flow demands are satisfied
> > > optimally (including MPLS packets).
> > >
> > > What is being suggested in this draft results in another
> > version of the MPLS
> > > topology in addition to (2) but in fact it does *NOT* optimize
> > significantly
> > > better than the current traffic engineering approaches but
> > results in two
> > > (overlay) networks.
> > >
> > > Nowhere in my email, do I suggest that you abandon IP level
> > multicast and
> > > use unicast, so I don't understand the last comment that you are making.
> > > What I am suggesting is that IP Multicast traffic can flow over
> > the traffic
> > > engineered network just as well as the unicast traffic. This is
> > *especially*
> > > true in a backbone network.
> > >
> > > Moreover, as multicast traffic is dynamic and can change
> > rapidly, I don't
> > > see the point of *multicast* traffic engineering which is assumed to be
> > > quasi-static.
> > >
> > > What this ID sounds like is a way of doing MPLS multicast as
> > you would see
> > > in an ATM network which is fine, but is not related to traffic
> > engineering.
> > >
> > > Regards
> > >
> > > Bora
> > >
> > > > -----Original Message-----
> > > > From: liwenwu@adn.alcatel.com
> > [mailto:liwenwu@adn.alcatel.com]On Behalf
> > > > Of LiWen Wu
> > > > Sent: Thursday, June 17, 1999 11:28 AM
> > > > To: Bora Akyol
> > > > Cc: liwen wu; mpls@UU.NET; te-wg@avici.com; idmr@cs.ucl.ac.uk
> > > > Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
> > > >
> > > >
> > > > Bora Akyol wrote:
> > > >
> > > > > The point that you are missing is the fact that the
> > point-to-point MPLS
> > > > > tunnels implement an arbitrary IP topology that includes
> > > > multicast traffic.
> > > > > The MPLS topology of the network is optimized according to the
> > > > traffic that
> > > > > runs on top of the physical links including IP multicast.
> > > > Therefore one does
> > > > > not need to add an MPLS multicast tree.
> > > >
> > > > Bora, I agree with you that you could use point-to-point
> > tunnel to carry
> > > > multicast traffic. Similarily, I could  also argue why not
> > > > duplicate the packet
> > > > at source
> > > > and unicast them  one by one to all the receivers.
> > > >
> > > > But I would think sending a packet through a point-to-multipoint
> > > > tree is more
> > > > efficient than duplicating the packet at ingress and send
> > them through the
> > > > MULTIPLE point-to-point MPLS tunnels.
> > > >
> > > > >
> > > > >
> > > > > I believe that this draft confuses MPLS multicast with IP
> > > > multicast while
> > > > > implying that one needs to build an MPLS multicast tree to
> > efficiently
> > > > > perform IP multicast which is untrue. MPLS tunnels when
> > > > designed take into
> > > > > account IP multicast traffic as well.
> > > > >
> > > >
> > > > This draft provides only ONE method on how to manage multicast traffic
> > > > in a core network.  It proposes using MPLS point-to-multipoint tree
> > > > to transport multicast traffic through a core ISP network.
> > > >
> > > > best regars,
> > > > Liwen--
> > > >
> > > > >
> > > > > Regards
> > > > >
> > > > > Bora
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: liwenwu@adn.alcatel.com
> > > > [mailto:liwenwu@adn.alcatel.com]On Behalf
> > > > > > Of LiWen Wu
> > > > > > Sent: Thursday, June 17, 1999 10:57 AM
> > > > > > To: Bora Akyol
> > > > > > Cc: liwen wu; mpls@UU.NET; te-wg@avici.com; idmr@cs.ucl.ac.uk
> > > > > > Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
> > > > > >
> > > > > >
> > > > > > Bora Akyol wrote:
> > > > > >
> > > > > > > Comments:
> > > > > > >
> > > > > > > 1) Is the multicast traffic included in the statistics that
> > > > are used to
> > > > > > > create the traffic matrix which in turn is used to create the
> > > > > > desired MPLS
> > > > > > > topology?
> > > > > >
> > > > > > Yes. But as  I am aware of today, all traffic engineereing
> > > > > > related drafts only
> > > > > > deal with
> > > > > > point-to-point MPLS tunnel.
> > > > > >
> > > > > > This paper propose building a point-to-multipoint MPLS tree
> > > > to carry the
> > > > > > multicast traffic through the core network.
> > > > > >
> > > > > > These trees are traffic engineered to avoid congested node and
> > > > > > links . They
> > > > > > also can be engineered to meet certain QOS requirement.
> > > > > >
> > > > > > There is another big advantage by using this concept that:
> > > > > >
> > > > > > 1)  All the routers inside a core ISP domain DOES NOT need to be
> > > > > > aware of all the multicast groups and sources. (Similar to a
> > > > core router
> > > > > > only aware of OSPF routes, but does not need to know all the
> > > > BGP routes)
> > > > > >
> > > > > > 2) Only border routers(root and receivers) need to know all the
> > > > > > multicast groups and sources , mappings from multicast group
> > > > and sources
> > > > > > to MPLS point-to-multipoint TREEs.
> > > > > >
> > > > > > best regards,
> > > > > > Liwen--
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > If the answer to this is *yes*, then ordinary traffic
> > > > engineering will
> > > > > > > optimize the traffic flows such that you will *get* a good
> > > > > > distribution of
> > > > > > > the multicast flows over the existing physical topology. So the
> > > > > > procedures
> > > > > > > proposed in this draft are not needed.
> > > > > > >
> > > > > > > If the answer is *no* then the solution may be covered in
> > > > this draft.
> > > > > > >
> > > > > > > I personally don't see a need for this draft or the methods
> > > > > > proposed in it.
> > > > > > > In most cases, the traffic matrix will actually include the
> > > > multicast
> > > > > > > traffic and will optimize the MPLS topology accordingly.
> > > > > > Otherwise, you will
> > > > > > > end up with one multicast topology and one unicast topology and
> > > > > > yet another
> > > > > > > network to manage.
> > > > > > >
> > > > > > > If we want to make multicast routing more efficient, we should
> > > > > > follow along
> > > > > > > the lines **-omp drafts and create a multicast routing
> > > > > > algorithm that runs
> > > > > > > within an area and
> > > > > > > is sensitive to network utilization.
> > > > > > >
> > > > > > > Bora
> > > > > >
> > > > > > --
> > > > > >
> > > >
> > --------------------------------------------------------------------------
> > > > > > Liwen Wu                                     Phone: (703) 724-2619
> > > > > > Alcatel U.S.A                                FAX:   (703) 724-2005
> > > > > > 44983 Knoll Square                  Inet:
> > liwen.wu@adn.alcatel.com
> > > > > > Ashburn, Va. 20147
> > > > > > USA
> > > > > > ------------------------------------------------------------------
> > > > > > ----------
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > > --
> > > >
> > --------------------------------------------------------------------------
> > > > Liwen Wu                                     Phone: (703) 724-2619
> > > > Alcatel U.S.A                                FAX:   (703) 724-2005
> > > > 44983 Knoll Square                  Inet:  liwen.wu@adn.alcatel.com
> > > > Ashburn, Va. 20147
> > > > USA
> > > > ------------------------------------------------------------------
> > > > ----------
> > > >
> > > >
> > > >
> > > >
> >
> > --
> > --------------------------------------------------------------------------
> > Liwen Wu                                     Phone: (703) 724-2619
> > Alcatel U.S.A                                FAX:   (703) 724-2005
> > 44983 Knoll Square                  Inet:  liwen.wu@adn.alcatel.com
> > Ashburn, Va. 20147
> > USA
> > ------------------------------------------------------------------
> > ----------
> >
> >
> >
> >


From owner-idmr@cs.ucl.ac.uk  Fri Jun 18 05:17:38 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA20938
	for <idmr-archive@lists.ietf.org>; Fri, 18 Jun 1999 05:17:37 -0400 (EDT)
Message-Id: <199906180917.FAA20938@ietf.org>
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.04449-0@pan2.cs.ucl.ac.uk>;
          Fri, 18 Jun 1999 07:25:22 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.04440-0@pan2.cs.ucl.ac.uk>; Fri, 18 Jun 1999 07:25:16 +0100
Received: from dialup-209.245.12.164.Denver1.Level3.net by bells.cs.ucl.ac.uk 
          with Internet SMTP id <g.01597-0@bells.cs.ucl.ac.uk>;
          Fri, 18 Jun 1999 07:25:31 +0100
From: subserve <subserve@gunma.com>
Subject: FREE Search Engine Submissions
Date: Wed, 16 Jun 1999 07:48:57
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Apparently-To: idmr-pp



  FREE - FREE - FREE - FREE - FREE - FREE - FREE - FREE


        IMMEDIATELY INCREASE YOUR SITES EXPOSURE

     We Will Submit Your Web Site Each Month To Over 

       900 Search Engines, Directories, & Indices

                 Absolutely 100% FREE


 READ THIS TESTIMONIAL...
===
 "The day after we received confirmation from you that 
 you had submitted our web site to search engines,
 directories and indices we got a "Niagra" of hits!
 In fact, we doubled and almost tripled our "hits."

 And since then we have had a pattern of hits that has
 doubled the number of hits we averaged for the same 
 period last year.

 For this little country inn, you have developed sales
 for us we never expected to get."
===

 OK - What's the catch... What do I have to do to take
 advantage of the "FREE" submission service.

 It's simple... One of the many services our company
 provides is "Web Site Hosting." All you have to do
 to take advantage of this Fantastic FREE Offer is to
 let us move your web site over to our State-Of-The-Art
 computers and our Web Site Submission Service is 
 yours as a FREE GIFT.

 Now, you might be thinking... "OK, here it comes... 
 You're probably going to charge me some huge amount
 each month for hosting aren't you?"

 NOPE - How about www.yourname.com for just $19.95 a month.
 PLUS we submit your web site each and every month to 
 over 900 search engines and directories absolutely FREE.
 Remember, that's a $259.95* value absolutely FREE.  
 
 Our hosting services are month-to-month. There are
 no long term commitments and "NO SETUP FEE" for our
 standard services either.

 That's why thousands and thousands of businesses 
 world wide both large and small have come to 
 us to utilize one of our services.  Hotels, Motels,
 On-Line Stores, Travel Agents, Colleges, 
 Universities, Governments, Fortune 500 companies,
 Movie Studios, Chambers Of Commerce and many,
 many more.  

 To learn more, just give us a call.


  Monday - Friday, 8am-5pm Pacific Time
          For more information
     Call USA/Canada (800) 771-2003
        or direct (916) 771-4739
  Monday - Friday, 8am-5pm Pacific Time


Submission services are available without hosting
if you prefer.  Call for details.

*$259.95 is an annualized savings figure based upon
our normal annual submission programs price.
 
 
 
 
 


From owner-idmr@cs.ucl.ac.uk  Fri Jun 18 05:24:28 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA20951
	for <idmr-archive@lists.ietf.org>; Fri, 18 Jun 1999 05:24:27 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.04544-0@pan2.cs.ucl.ac.uk>;
          Fri, 18 Jun 1999 10:01:26 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.04537-0@pan2.cs.ucl.ac.uk>; Fri, 18 Jun 1999 10:01:22 +0100
Received: from henry.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.07727-0@bells.cs.ucl.ac.uk>; Fri, 18 Jun 1999 10:01:38 +0100
X-Mailer: exmh version 2.0.2
To: Bora Akyol <akyol@pluris.com>
cc: mpls <mpls@UU.NET>, idmr <idmr@cs.ucl.ac.uk>
Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
In-reply-to: Your message of "Thu, 17 Jun 1999 12:39:57 PDT." <005501beb8f9$2e29a040$963710ac@pluris.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 18 Jun 1999 10:01:37 +0100
Message-ID: <1056.929696497@cs.ucl.ac.uk>
From: Kenneth CARLBERG <K.Carlberg@cs.ucl.ac.uk>
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk


> Moreover, as multicast traffic is dynamic and can change rapidly, 

yes, but "can" does not equate to all -- meaning that both static and 
dynamic spectrums need to be addressed.  there are probably others on 
the rem-conf list that can provide a wider set of examples, but last 
november, i took some samplings of a shuttle mission and if memory 
serves me correctly, nearly 20% of the total number of receivers were 
members of the group for a 24 hour period.  and yes, if you reply that 
mbone info is not a real reflection of the internet or mcast-like traffic 
(in production nets), then consider when single-source TV is eventually 
added to the net.

> I don't
> see the point of *multicast* traffic engineering which is assumed to be
> quasi-static.

perhaps it depends on what one considers important in the area of traffic
enginnering.  traditional items for big-time ISPs focus on load 
concentrations.
but in putting on my 'industry' hat on, i get periodic questions regarding 
dual-homed or multi-access systems that involve combinations of geo/leo 
satcom and terestrial connectivity....begging for a reasonable means of 
having
control in how the branch is grated onto a tree.

-ken




From owner-idmr@cs.ucl.ac.uk  Fri Jun 18 10:54:51 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA24185
	for <idmr-archive@lists.ietf.org>; Fri, 18 Jun 1999 10:54:49 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.04625-0@pan2.cs.ucl.ac.uk>;
          Fri, 18 Jun 1999 13:01:28 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.04619-0@pan2.cs.ucl.ac.uk>; Fri, 18 Jun 1999 13:01:24 +0100
Received: from shortbus.0iq.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.18383-0@bells.cs.ucl.ac.uk>; Fri, 18 Jun 1999 13:01:37 +0100
Received: from localhost (brad@localhost) by shortbus.0iq.com (8.9.1/8.9.1) 
          with ESMTP id IAA18829;
          Fri, 18 Jun 1999 08:02:54 -0400 (EDT) (envelope-from brad@qual.net)
Date: Fri, 18 Jun 1999 08:02:54 -0400 (EDT)
From: Bradley Reynolds <brad@qual.net>
X-Sender: brad@shortbus.0iq.com
To: Kenneth CARLBERG <K.Carlberg@cs.ucl.ac.uk>
cc: Bora Akyol <akyol@pluris.com>, mpls <mpls@UU.NET>,
        idmr <idmr@cs.ucl.ac.uk>
Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
In-Reply-To: <1056.929696497@cs.ucl.ac.uk>
Message-ID: <Pine.BSF.4.05.9906180800520.18815-100000@shortbus.0iq.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

> perhaps it depends on what one considers important in the area of traffic
> enginnering.  traditional items for big-time ISPs focus on load 
> concentrations.

perhaps big-time ISPs will be more apt to concentrate on multicast
traffic engineering when it equates to more than .1% of their aggregate
traffic.  

BR



From owner-idmr@cs.ucl.ac.uk  Fri Jun 18 10:55:07 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA24196
	for <idmr-archive@lists.ietf.org>; Fri, 18 Jun 1999 10:55:05 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.04646-0@pan2.cs.ucl.ac.uk>;
          Fri, 18 Jun 1999 13:06:30 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.04639-0@pan2.cs.ucl.ac.uk>; Fri, 18 Jun 1999 13:06:26 +0100
Received: from waffle.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.18755-0@bells.cs.ucl.ac.uk>; Fri, 18 Jun 1999 13:06:43 +0100
To: Bradley Reynolds <brad@qual.net>
cc: Kenneth CARLBERG <K.Carlberg@cs.ucl.ac.uk>, Bora Akyol <akyol@pluris.com>,
        mpls <mpls@UU.NET>, idmr <idmr@cs.ucl.ac.uk>
Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
In-reply-to: Your message of "Fri, 18 Jun 1999 08:02:54 EDT." <Pine.BSF.4.05.9906180800520.18815-100000@shortbus.0iq.com>
Date: Fri, 18 Jun 1999 13:06:42 +0100
Message-ID: <1685.929707602@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@cs.ucl.ac.uk>
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk


In message <Pine.BSF.4.05.9906180800520.18815-100000@shortbus.0iq.com>, Bradley
 Reynolds typed:

 >>> perhaps it depends on what one considers important in the area of traffic
 >>> enginnering.  traditional items for big-time ISPs focus on load 
 >>> concentrations.

 >>perhaps big-time ISPs will be more apt to concentrate on multicast
 >>traffic engineering when it equates to more than .1% of their aggregate
 >>traffic.  
 
perhaps if they used multicast for cache/mirror prefetch and streaming
then multicast would amount to 40% of the backbone traffic, but 
the backbone would be running at 20% lighter load...:-)

 cheers

   jon



From owner-idmr@cs.ucl.ac.uk  Fri Jun 18 10:58:52 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA24233
	for <idmr-archive@lists.ietf.org>; Fri, 18 Jun 1999 10:58:50 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.04677-0@pan2.cs.ucl.ac.uk>;
          Fri, 18 Jun 1999 13:20:51 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.04671-0@pan2.cs.ucl.ac.uk>; Fri, 18 Jun 1999 13:20:45 +0100
Received: from maile.surrey.ac.uk by bells.cs.ucl.ac.uk with UK SMTP 
          id <g.19582-0@bells.cs.ucl.ac.uk>; Fri, 18 Jun 1999 13:21:03 +0100
Received: from petra.ee.surrey.ac.uk by maile.surrey.ac.uk with SMTP (PP);
          Fri, 18 Jun 1999 13:20:28 +0100
Date: Fri, 18 Jun 1999 13:20:51 +0100 (BST)
From: Lloyd Wood <L.Wood@surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@surrey.ac.uk>
To: Jon Crowcroft <J.Crowcroft@cs.ucl.ac.uk>
cc: Bradley Reynolds <brad@qual.net>,
        Kenneth CARLBERG <K.Carlberg@cs.ucl.ac.uk>,
        Bora Akyol <akyol@pluris.com>, mpls <mpls@UU.NET>,
        idmr <idmr@cs.ucl.ac.uk>
Subject: Re: Question on draft-wu-mpls-multicast-te-00.txt
In-Reply-To: <1685.929707602@cs.ucl.ac.uk>
Message-ID: <Pine.SOL.4.02.9906181313130.24572-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-URL: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

On Fri, 18 Jun 1999, Jon Crowcroft wrote:

>  Bradley Reynolds typed:
> 
>  >>> perhaps it depends on what one considers important in the area of traffic
>  >>> enginnering.  traditional items for big-time ISPs focus on load 
>  >>> concentrations.
> 
>  >>perhaps big-time ISPs will be more apt to concentrate on multicast
>  >>traffic engineering when it equates to more than .1% of their aggregate
>  >>traffic.  
>  
> perhaps if they used multicast for cache/mirror prefetch and streaming
> then multicast would amount to 40% of the backbone traffic, but 
> the backbone would be running at 20% lighter load...:-)

If more people ran Squid with multicast ICP, this might happen.

http://squid.nlanr.net/Squid/FAQ/FAQ-13.html

oh look, they've made multicast question number thirteen. Why could
that possibly be?

L.

traditional items for big-time ISPs focus on billing. Or used to.

<L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>



From owner-idmr@cs.ucl.ac.uk  Mon Jun 21 11:11:31 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA04901
	for <idmr-archive@lists.ietf.org>; Mon, 21 Jun 1999 11:11:30 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.05760-0@pan2.cs.ucl.ac.uk>;
          Mon, 21 Jun 1999 12:19:08 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.05754-0@pan2.cs.ucl.ac.uk>; Mon, 21 Jun 1999 12:19:04 +0100
Received: from 1Cust149.tnt1.west-palm-beach.fl.da.uu.net by bells.cs.ucl.ac.uk 
          with Internet SMTP id <g.15046-0@bells.cs.ucl.ac.uk>;
          Mon, 21 Jun 1999 12:19:12 +0100
From: webhoster23 <webhoster23@eastmail.com>
Subject: PUT YOUR BUSINESS ON THE INTERNET FOR $9.95 PER MONTH! AD
Date: Sun, 20 Jun 1999 16:44:16
Message-Id: <231.714621.287978@mail.webhostUUR86654.com>
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Apparently-To: idmr-pp

GET YOUR OWN 5 MEG WEBSITE FOR ONLY $120.00 PER YEAR TODAY!

STOP PAYING $19.95 or more PER MONTH OR MORE TODAY for your web 
site!

DO YOU ALREADY HAVE A WEBSITE? ALL YOU HAVE TO DO IS TRANSFER THE 
DOMAIN TO OUR SERVERS AND UPLOAD YOUR DATA AND YOUR READY TO GO!

ALL OUR WEBSITES USE FRONT PAGE AND YOU CAN CHANGE YOUR SITE AS 
MUCH AS YOU WANT!

WE OFFER ALL THE LATEST FEATURES LIKE REAL AUDIO,CYBERCASH, 
SECURE SERVERS, SEARCH ENGINE SUBMISSION and MERCHANT INTERNET 
CREDIT CARD PROCESSING ACCOUNTS. WITH COMPLETE WEB DESIGN AT 
REASONABLE RATES.

SET UP FEE OF $40.00 APPLIES for FIRST TIME CUSTOMERS.

FOR DETAILS CALL 1800 636 6773 ext 4692

THANK YOU

to be removed email webhoster23@eastmail.com
 
 
 
 
 
 
 
 
 
 
 
 
 


From owner-idmr@cs.ucl.ac.uk  Mon Jun 21 19:08:41 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA12065
	for <idmr-archive@lists.ietf.org>; Mon, 21 Jun 1999 19:08:41 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.05877-0@pan2.cs.ucl.ac.uk>;
          Mon, 21 Jun 1999 21:43:34 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.05871-0@pan2.cs.ucl.ac.uk>; Mon, 21 Jun 1999 21:43:30 +0100
Received: from cronus.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.17252-0@bells.cs.ucl.ac.uk>; Mon, 21 Jun 1999 21:43:43 +0100
X-Mailer: exmh version 2.0.2
To: idmr@cs.ucl.ac.uk
Subject: idmr IETF slides
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 21 Jun 1999 21:43:41 +0100
Message-ID: <1026.929997821@cs.ucl.ac.uk>
From: Paul WHITE <P.White@cs.ucl.ac.uk>
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

Hi folks,

as maintainer of the idmr web page at http://www.cs.ucl.ac.uk/ietf/idmr/gen-inf
o.html I would be grateful to receive slides from the following IETF IDMR 
meetings so that I can put them on the page

- August 1998
- All idmr IETFs meetings post Dec 1998

 regards,

Paul

-------------------------------------------------------------------------------
Paul White
Department of Computer Science, University College London, Tel: (0171) 419 3701
Gower Street, WC1E 6BT, London, England                    Fax: (0171) 387 1397
           
Mobile: 0956 675801
-------------------------------------------------------------------------------




From owner-idmr@cs.ucl.ac.uk  Tue Jun 22 15:23:45 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA14191
	for <idmr-archive@lists.ietf.org>; Tue, 22 Jun 1999 15:23:44 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.06276-0@pan2.cs.ucl.ac.uk>;
          Tue, 22 Jun 1999 16:56:56 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.06270-0@pan2.cs.ucl.ac.uk>; Tue, 22 Jun 1999 16:56:52 +0100
Received: from smtprich.nortel.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.04025-0@bells.cs.ucl.ac.uk>; Tue, 22 Jun 1999 16:57:10 +0100
Received: from zcard00n.ca.nortel.com (actually zcard00n) 
          by smtprich.nortel.com; Tue, 22 Jun 1999 10:39:41 -0500
Received: from zcard00p.ca.nortel.com ([47.141.0.104]) 
          by zcard00n.ca.nortel.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) 
          id N2F43FJK; Tue, 22 Jun 1999 11:39:40 -0400
Received: from nortel.com (zcars02x.ca.nortel.com [47.23.81.10]) 
          by zcard00p.ca.nortel.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) 
          id L22KRCBY; Tue, 22 Jun 1999 11:39:38 -0400
Message-ID: <376FAE3B.A161EBF0@nortel.com>
Date: Tue, 22 Jun 1999 11:39:39 -0400
From: Cheng-Yin Lee <leecy@nortelnetworks.com>
X-Mailer: Mozilla 4.06 [en] (X11; I; SunOS 5.6 sun4u)
MIME-Version: 1.0
To: "sm-interest@cs.ucl.ac.uk" <sm-interest@cs.ucl.ac.uk>
CC: "idmr@cs.ucl.ac.uk" <idmr@cs.ucl.ac.uk>
Subject: WG Proposal - RAMA
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

FYI,
We have submitted the proposed RAMA WG charter to the ADs/IESG.

cheers,
cyl

=====================================================
Proposed WG:
Root Addressed Multicast Architecture (RAMA)

Co-chairs
Jon Crowcroft <J.Crowcroft@cs.ucl.ac.uk>
Christophe Diot <cdiot@sprintlabs.com>
Cheng-Yin Lee <leecy@nortelnetworks.com>

Description of Working Group:

The primary goal of the group is to develop specifications that will ease  the
scaling (in the longer term) of current multicast routing protocols  targeted for
these type of applications:

* Internet wide information distribution (eg 'webcast', content
subscription/distribution)
* Internet wide interactive information exchange (eg  conferencing/discussion,
games).

The approach taken will allow the root (source or core) of the multicast
distribution tree to allocate logical  addresses that can be used to address
multicast groups. Since address management is local to the root, it  will not
require Internet wide coordination and will also facilitate applications to use the
address space in a creative and application specific manner (eg content
filtering/naming, layered data) where  applicable.

The scope of work is as follows:

* extend the current multicast API to use this new addressing
 - the group multicast address will consist of both the root (source or  core) of
the multicast tree and   multicast address.

* extend the current multicast data forwarding to forward based on  <root, multicast
address>.
The address encoding should allow :

- routers which do not understand this new addressing to forward packets non
natively (unicast)
- current hardware to forward packet with this new addressing when the  root is the
source of the multicast  group in the initial implementation and deployment,
- for hardware to be upgraded to forward packet with the core as root.

* changes to control messages will be defined generically in TLV format.
The group will coordinate with the respective WGs for these extensions to be
implemented in PIM/CBT/BGMP and expect to liase with the respective WGs on the
following documents:
- PIM with RAMA extensions
- BGMP with RAMA extensions
- CBT with RAMA extensions

* migration/interoperability issues related to the above. (Please see
http://www.cs.ucl.ac.uk/research/rama/interop.txt for more details)

Goals and Milestones:

    Jul 99  Specify goals and deliverables
    Oct 99  Issue first Internet-Drafts (Host API, IGMP change, RAMA routing) on
extensions to
                 IP multicast
    Dec 99  Achieve concensus on the extensions
    Mar 00  Issue detailed specifications on host and router extensions
    Apr  00  Liason work with other WGs
    Nov  00  Submit specifications to IESG as proposed standards

Internet-Drafts:

* "Multicast Requirements for the Definition of New IP Multicast Services"
  Christophe Diot, Bryan Lyles, Brian Neil Levine (Consultant),  Sprint ATL,
  Ramanan Shanmugam, Amir Tabdili, Hassan Kassem, Sprintlink
* Simple Multicast, draft-perlman-simple-multicast-02.txt, Perlman et al.
* Express , H Holbrook, D. Cheriton, Sigcomm Paper



From owner-idmr@cs.ucl.ac.uk  Wed Jun 23 16:11:15 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA13203
	for <idmr-archive@lists.ietf.org>; Wed, 23 Jun 1999 16:11:14 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.06655-0@pan2.cs.ucl.ac.uk>;
          Wed, 23 Jun 1999 18:10:18 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.06649-0@pan2.cs.ucl.ac.uk>; Wed, 23 Jun 1999 18:10:15 +0100
Received: from odin.ietf.org by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.11354-0@bells.cs.ucl.ac.uk>; Wed, 23 Jun 1999 18:10:30 +0100
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) 
          by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05990;
          Wed, 23 Jun 1999 13:10:26 -0400 (EDT)
Message-Id: <199906231710.NAA05990@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
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-membership-reports-03.txt,.ps
Date: Wed, 23 Jun 1999 13:10:26 -0400
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

--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		: Domain Wide Multicast Group Membership Reports
	Author(s)	: B. Fenner
	Filename	: draft-ietf-idmr-membership-reports-03.txt,.ps
	Pages		: 16
	Date		: 22-Jun-99
	
When running a multi-level multicast routing protocol, upper levels
need to know about group memberships in lower levels in a protocol-
independent fashion.  Domain Wide Multicast Group Membership
Reports allow this information to be learned in a fashion similar
to IGMP[Fenn97] at the domain level.
 
This document is a product of the IDMR working group within the Internet
Engineering Task Force.  Comments are solicited and should be addressed
to the working group's mailing list at idmr@cs.ucl.ac.uk and/or the
author.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idmr-membership-reports-03.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-membership-reports-03.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-membership-reports-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
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<19990622132242.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idmr-membership-reports-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-idmr-membership-reports-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990622132242.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-idmr@cs.ucl.ac.uk  Wed Jun 23 16:12:11 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA13226
	for <idmr-archive@lists.ietf.org>; Wed, 23 Jun 1999 16:12:09 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.06724-0@pan2.cs.ucl.ac.uk>;
          Wed, 23 Jun 1999 19:26:46 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.06718-0@pan2.cs.ucl.ac.uk>; Wed, 23 Jun 1999 19:26:41 +0100
Received: from cheetah.safari.net by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.15669-0@bells.cs.ucl.ac.uk>; Wed, 23 Jun 1999 19:27:00 +0100
Received: (qmail 15794 invoked from network); 23 Jun 1999 18:26:51 -0000
Received: from rhino.safari.net (HELO noc) (qmailr@208.235.96.54) 
          by smtp.safari.net with SMTP; 23 Jun 1999 18:26:51 -0000
Received: (qmail 27848 invoked by uid 500); 23 Jun 1999 18:26:42 -0000
From: xs-dated-56ad8d9e155693f9@rhino.safari.net
Delivered-To: xs@rhino.safari.net
Received: (qmail 27836 invoked from network); 23 Jun 1999 18:26:40 -0000
Received: from katanga.safari.net (HELO mail1.safari.net) (qmailr@206.96.248.4) 
          by rhino.safari.net with SMTP; 23 Jun 1999 18:26:40 -0000
Received: (qmail 32611 invoked by uid 2600); 23 Jun 1999 18:25:42 -0000
Delivered-To: xs@SAFARI.NET
Received: (qmail 32598 invoked from network); 23 Jun 1999 18:25:35 -0000
Received: from loki.ietf.org (132.151.1.177) by mail1.safari.net with SMTP;
          23 Jun 1999 18:25:35 -0000
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id NAA05345 
          for ietf-123-outbound.09@ietf.org;
          Wed, 23 Jun 1999 13:25:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) 
          by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id NAA04733 
          for <all-ietf@loki.ietf.org>; Wed, 23 Jun 1999 13:14:25 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) 
          by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05990;
          Wed, 23 Jun 1999 13:10:26 -0400 (EDT)
Message-Id: <199906231710.NAA05990@ietf.org>
Mime-Version: 1.0
X-Security: MIME headers sanitized on rhino See 
            http://www.wolfenet.com/~jhardin/procmail-security.html for 
            details. $Revision: 1.84 $Date: 1999-06-12 12:30:37-07
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: idmr@cs.ucl.ac.uk
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-idmr-membership-reports-03.txt,.ps
Date: Wed, 23 Jun 1999 13:10:26 -0400
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

--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		: Domain Wide Multicast Group Membership Reports
	Author(s)	: B. Fenner
	Filename	: draft-ietf-idmr-membership-reports-03.txt,.ps
	Pages		: 16
	Date		: 22-Jun-99
	
When running a multi-level multicast routing protocol, upper levels
need to know about group memberships in lower levels in a protocol-
independent fashion.  Domain Wide Multicast Group Membership
Reports allow this information to be learned in a fashion similar
to IGMP[Fenn97] at the domain level.
 
This document is a product of the IDMR working group within the Internet
Engineering Task Force.  Comments are solicited and should be addressed
to the working group's mailing list at idmr@cs.ucl.ac.uk and/or the
author.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idmr-membership-reports-03.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-membership-reports-03.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-membership-reports-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
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<19990622132242.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idmr-membership-reports-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-idmr-membership-reports-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990622132242.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-idmr@cs.ucl.ac.uk  Thu Jun 24 15:56:48 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA20921
	for <idmr-archive@lists.ietf.org>; Thu, 24 Jun 1999 15:56:47 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.07130-0@pan2.cs.ucl.ac.uk>;
          Thu, 24 Jun 1999 18:03:38 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.07124-0@pan2.cs.ucl.ac.uk>; Thu, 24 Jun 1999 18:03:34 +0100
Received: from fgwmail3.fujitsu.co.jp by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.06635-0@bells.cs.ucl.ac.uk>; Thu, 24 Jun 1999 18:03:53 +0100
Received: from fdmnews.fujitsu.co.jp 
          by fgwmail3.fujitsu.co.jp (8.9.3/3.7W-MX9904-Fujitsu Gateway) 
          id CAA06750; Fri, 25 Jun 1999 02:03:51 +0900 (JST)
Received: from flabmail.flab.fujitsu.co.jp 
          by fdmnews.fujitsu.co.jp (8.9.3/3.7W-9905-Fujitsu Domain Master) 
          id CAA26204; Fri, 25 Jun 1999 02:03:49 +0900 (JST)
Received: from mailserv.kawasaki.flab.fujitsu.co.jp 
          by flabmail.flab.fujitsu.co.jp (8.6.12+2.5Wb7/3.3W9-MX970225-Fujitsu Labs. Domain Mail Master) 
          id CAA18996; Fri, 25 Jun 1999 02:03:49 +0900
Received: from localhost (gifu.kawasaki.flab.fujitsu.co.jp [10.25.159.35]) 
          by mailserv.kawasaki.flab.fujitsu.co.jp (SMI-8.6/3.5Wbeta96090511) 
          with SMTP id CAA28003 for <idmr@cs.ucl.ac.uk>;
          Fri, 25 Jun 1999 02:03:45 +0900
To: idmr@cs.ucl.ac.uk
Subject: Serious impact for muliticast usage?
Reply-To: kimai@flab.fujitsu.co.jp
X-Mailer: Mew version 1.92.4 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <19990625020302R.kimai@flab.fujitsu.co.jp>
Date: Fri, 25 Jun 1999 02:03:02 +0900
From: IMAI Yuji <kimai@flab.fujitsu.co.jp>
X-Dispatcher: imput version 971024
Lines: 56
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

   I'm new-comer of this area, now studying about the scalability of
multicast routing, and considered how scalability effect on usage of
multicast application.

   SOLA et al described in the paper at INET'98
(http://noc.aic.net/inet98/6d/6d_3.htm) that # of state for multicast
routing at each router has O(g) even if best possible situation. (g is
number of multicast groups that run on the router.)

   I have read that there were hard discussion on this ML, whether
aggregation of multicast routing table is possible or not. Someone did
not give up and believe possibility of aggregation but couldn't find
out how to. (Ohta-san and Sola-san must be sigh again :-)

   For the present, to provide multicast service for customer, ISP
must arrange their border router that enables to hold O(g) multicast
route entries and to handle O(g) control packets, I think.

  It means that ISP must carefully choose which multicast application
to be provided.

  If ISP decide to start a tie-up with Satellite TV (like DirecTV), g
must become several hundreds. To provide video conference service on
the Internet,(ex. www.sprinticc.com) I think they must manage several
thousands of group addresses. In such amount of groups, these may be a
acceptable usage for ISP, because customers may accept pay-per-system
for such kind of special applications.

  Now, imagine the situation that AOL purchases CU-seeme and integrate
it into ICQ using multicast.

  - They "frequently" join and prune.
  - They runs it on very sparse environment.
  - User pays for AOL not for ISP, or fee-free with banner advertisement.

Can national-ISP hold several ten thousands of group entry on border
routers for such purpose in profitable manner?

  I think they couldn't, because it is comparable to the number of
full route entry on typical IXs (40000 ~ 45000).
(http://www.merit.edu/ipma/trends/) and join/prune requests beat a
router seriously. ISP operators hate a instability route very much.

Then questions,

- Is there any techniques to aggregate a multicast routing table?
  I overlooked them? Is it impossible at all?
  (I think it impossible on my heart, but look forward a miracle.)

- If no way exists to aggregate, I had better give up to use multicast
  delivery for casual video-chat frames. Is that right?

-----
IMAI Yuji


From owner-idmr@cs.ucl.ac.uk  Fri Jun 25 03:07:22 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA17402
	for <idmr-archive@lists.ietf.org>; Fri, 25 Jun 1999 03:07:21 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.07325-0@pan2.cs.ucl.ac.uk>;
          Fri, 25 Jun 1999 05:45:04 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.07318-0@pan2.cs.ucl.ac.uk>; Fri, 25 Jun 1999 05:44:59 +0100
Received: from necom830.hpcl.titech.ac.jp by bells.cs.ucl.ac.uk 
          with Internet SMTP id <g.01924-0@bells.cs.ucl.ac.uk>;
          Fri, 25 Jun 1999 05:45:19 +0100
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <199906250432.NAA21346@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1) id NAA21346;
          Fri, 25 Jun 1999 13:32:00 +0900
Subject: Re: Serious impact for muliticast usage?
To: kimai@flab.fujitsu.co.jp
Date: Fri, 25 Jun 99 13:31:59 JST
Cc: idmr@cs.ucl.ac.uk
In-Reply-To: <19990625020302R.kimai@flab.fujitsu.co.jp>; from "IMAI Yuji" at Jun 25, 99 2:03 am
X-Mailer: ELM [version 2.3 PL11]
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

Imai-san;

> Someone did
> not give up and believe possibility of aggregation but couldn't find
> out how to. (Ohta-san and Sola-san must be sigh again :-)

It's a political problem. Such people should be confined in some
political forum such as Internet2.

>    For the present, to provide multicast service for customer, ISP
> must arrange their border router that enables to hold O(g) multicast
> route entries and to handle O(g) control packets, I think.

Yup.

>   It means that ISP must carefully choose which multicast application
> to be provided.

ISPs, instead, should carefully choose routers with a lot of routing
table entries.

> Then questions,
> 
> - Is there any techniques to aggregate a multicast routing table?
>   I overlooked them? Is it impossible at all?
>   (I think it impossible on my heart, but look forward a miracle.)

:-)

> - If no way exists to aggregate, I had better give up to use multicast
>   delivery for casual video-chat frames. Is that right?

Wrong.

Aggregation of QoS-assured unicast is impossible, too, anyway.

It, instead, is trivially easy to have routers with thousands of
elementary forwarding engines, millions of synthesized forwarding
table entries and thousands of join/prune/RSVPng processor.

						Masataka Ohta


From owner-idmr@cs.ucl.ac.uk  Mon Jun 28 11:29:07 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA03562
	for <idmr-archive@lists.ietf.org>; Mon, 28 Jun 1999 11:29:05 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.07835-0@pan2.cs.ucl.ac.uk>;
          Mon, 28 Jun 1999 13:30:44 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.07829-0@pan2.cs.ucl.ac.uk>; Mon, 28 Jun 1999 13:30:40 +0100
Received: from odin.ietf.org by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.20078-0@bells.cs.ucl.ac.uk>; Mon, 28 Jun 1999 13:30:59 +0100
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) 
          by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27317;
          Mon, 28 Jun 1999 08:30:52 -0400 (EDT)
Message-Id: <199906281230.IAA27317@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
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-multicast-routmib-09.txt
Date: Mon, 28 Jun 1999 08:30:51 -0400
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

--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		: IP Multicast Routing MIB
	Author(s)	: K. McCloghrie, D. Farinacci, D. Thaler
	Filename	: draft-ietf-idmr-multicast-routmib-09.txt
	Pages		: 31
	Date		: 25-Jun-99
	
This memo defines an experimental portion of the Management Information
Base (MIB) for use with network management protocols in the Internet
community.  In particular, it describes managed objects used for
managing IP Multicast Routing for IPv4, independent of the specific
multicast routing protocol in use.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idmr-multicast-routmib-09.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-multicast-routmib-09.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-multicast-routmib-09.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
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<19990625140114.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idmr-multicast-routmib-09.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-idmr-multicast-routmib-09.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990625140114.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-idmr@cs.ucl.ac.uk  Mon Jun 28 11:29:12 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA03585
	for <idmr-archive@lists.ietf.org>; Mon, 28 Jun 1999 11:29:11 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.07854-0@pan2.cs.ucl.ac.uk>;
          Mon, 28 Jun 1999 13:31:35 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.07848-0@pan2.cs.ucl.ac.uk>; Mon, 28 Jun 1999 13:31:31 +0100
Received: from odin.ietf.org by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.20159-0@bells.cs.ucl.ac.uk>; Mon, 28 Jun 1999 13:31:52 +0100
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) 
          by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27392;
          Mon, 28 Jun 1999 08:31:46 -0400 (EDT)
Message-Id: <199906281231.IAA27392@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
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-igmp-mib-10.txt
Date: Mon, 28 Jun 1999 08:31:46 -0400
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

--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		: Internet Group Management Protocol MIB
	Author(s)	: K. McCloghrie, D. Farinacci, D. Thaler
	Filename	: draft-ietf-idmr-igmp-mib-10.txt
	Pages		: 21
	Date		: 25-Jun-99
	
This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.  In
particular, it describes objects used for managing the Internet Group
Management Protocol (IGMP).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idmr-igmp-mib-10.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-igmp-mib-10.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-igmp-mib-10.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
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<19990625140124.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idmr-igmp-mib-10.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-idmr-igmp-mib-10.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990625140124.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-idmr@cs.ucl.ac.uk  Mon Jun 28 17:16:43 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA13529
	for <idmr-archive@lists.ietf.org>; Mon, 28 Jun 1999 17:16:42 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.08044-0@pan2.cs.ucl.ac.uk>;
          Mon, 28 Jun 1999 19:39:50 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.08038-0@pan2.cs.ucl.ac.uk>; Mon, 28 Jun 1999 19:39:46 +0100
Received: from H-135-207-30-103.research.att.com by bells.cs.ucl.ac.uk 
          with Internet SMTP id <g.15274-0@bells.cs.ucl.ac.uk>;
          Mon, 28 Jun 1999 19:40:07 +0100
Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) 
          by mail-green.research.att.com (Postfix) with ESMTP id 35E3B1E009;
          Mon, 28 Jun 1999 14:40:06 -0400 (EDT)
Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) 
          by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id OAA09182;
          Mon, 28 Jun 1999 14:40:05 -0400 (EDT)
From: Bill Fenner <fenner@research.att.com>
Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) 
          id LAA24969; Mon, 28 Jun 1999 11:40:04 -0700 (PDT)
Message-Id: <199906281840.LAA24969@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: agenda@ietf.org, idmr@cs.ucl.ac.uk
Subject: IDMR Agenda
Date: Mon, 28 Jun 1999 11:40:03 -0700
Versions: dmail (solaris) 2.2c/makemail 2.8t
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk


	Agenda Bashing		5 minutes
	Document Status		40 minutes
	Charter Bashing		10 minutes


From owner-idmr@cs.ucl.ac.uk  Wed Jun 30 11:38:35 1999
Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA19127
	for <idmr-archive@lists.ietf.org>; Wed, 30 Jun 1999 11:38:34 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.08370-0@pan2.cs.ucl.ac.uk>;
          Wed, 30 Jun 1999 13:40:22 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.08364-0@pan2.cs.ucl.ac.uk>; Wed, 30 Jun 1999 13:40:18 +0100
Received: from odin.ietf.org by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.18337-0@bells.cs.ucl.ac.uk>; Wed, 30 Jun 1999 13:40:39 +0100
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) 
          by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15247;
          Wed, 30 Jun 1999 08:40:32 -0400 (EDT)
Message-Id: <199906301240.IAA15247@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
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-traceroute-ipm-05.txt,.ps
Date: Wed, 30 Jun 1999 08:40:32 -0400
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

--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		: A ''traceroute'' facility for IP Multicast.
	Author(s)	  B. Fenner, S. Casner
	Filename	: draft-ietf-idmr-traceroute-ipm-05.txt,.ps
	Pages		: 22
	Date		: 29-Jun-99
	
This draft describes the IGMP multicast traceroute facility.  As
the deployment of IP multicast has spread, it has become clear that
a method for tracing the route that a multicast IP packet takes
from a source to a particular receiver is absolutely required.
Unlike unicast traceroute, multicast traceroute requires a special
packet type and implementation on the part of routers.  This speci-
fication describes the required functionality.
 
This document is a product of the Inter-Domain Multicast Routing working
group within the Internet Engineering Task Force.  Comments are
solicited and should be addressed to the working group's mailing list at
idmr@cs.ucl.ac.uk and/or the author(s).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idmr-traceroute-ipm-05.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-traceroute-ipm-05.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-traceroute-ipm-05.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
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<19990629143838.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idmr-traceroute-ipm-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-idmr-traceroute-ipm-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990629143838.I-D@ietf.org>

--OtherAccess--

--NextPart--




