From owner-idmr@cs.ucl.ac.uk  Mon Aug  2 14:49:04 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 OAA02515
	for <idmr-archive@lists.ietf.org>; Mon, 2 Aug 1999 14:49:02 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.14618-0@pan2.cs.ucl.ac.uk>;
          Mon, 2 Aug 1999 16:59:20 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.14612-0@pan2.cs.ucl.ac.uk>; Mon, 2 Aug 1999 16:59:15 +0100
Received: from mx.sprintlabs.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.02253-0@bells.cs.ucl.ac.uk>; Mon, 2 Aug 1999 16:59:42 +0100
Received: from sprintlabs.com (ip199-2-54-117.sprintlabs.com [199.2.54.117]) 
          by mailman.sprintlabs.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) 
          id P60ZAK1M; Mon, 2 Aug 1999 08:59:40 -0700
Message-ID: <37A5C07E.9482F819@sprintlabs.com>
Date: Mon, 02 Aug 1999 08:59:58 -0700
From: christophe diot <cdiot@sprintlabs.com>
Organization: SPRINT ATL
X-Mailer: Mozilla 4.05 [en] (Win95; I)
MIME-Version: 1.0
To: David Oran <oran@cisco.com>
CC: maddogs@ietf.org, idmr@cs.ucl.ac.uk, idr@merit.edu,
        msdp@network-services.uoregon.edu, pim@catarina.usc.edu,
        mboned@network-services.uoregon.edu, malloc@catarina.usc.edu,
        rmt@lbl.gov
Subject: Re: Maestro BoF Results
References: <NBBBIFCAKKOPNMMKHHEFGEBGFFAA.oran@cisco.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

David Oran wrote:
> 
> The Routing Area held a BoF at the Oslo IETF whose purpose was to discuss
> potential refinements to the IP multicast model in two areas:
>   1) Enhanced two-part multicast addressing to ease scalability and
> deployment
>      headaches,
>   2) Optimizations to exploit the single-sender case
> 
> The BoF announcement, along with its scope and agenda, may be found at:
> http://www.ietf.org/ietf/99jul/maestro-agenda-99jul.txt.
> 
> I am sending this message to who I think are all the relevant WG mailing
> lists, and it will also be sent out via IETF-announce, so please let me know
> directly if I've missed a relevant group rather than risk clogging peoples'
> mailboxes with multiple forwards.
> 
> The minutes of BoF are attached below. One of the conclusions from the BoF
> was to continue discussions on these subjects to ascertain if there is a
> critical mass of support to charter one or more Working Groups to pursue
> IETF standards (or other outputs) in these areas. We are therefore
> resurrecting a moribund Routing Area mailing list for this purpose:
>         routing-discussion@ietf.org
> Subscription is via majordomo@ietf.org
> 
> Thanks to all who participated in the BoF and in advance for useful
> low-flamability discussion on the mailing list.
> 
> Regards, Dave Oran (routing co-area director)
> 
> MAESTRO BOF, Dave Oran
> ----------------------
> 
> AGENDA
> 
> History - modify multicast model, do we need a working group
> on this?
> 
> A number of people think if we simplify the multicast model
> there are significant benefits in reducing complexity.
> changes: addressing model, assume single sender.
> 
> We want to look at the problems today and see how proposed
> simplications might help.
> 
> Ground rules: talk about problems and how they map to the
> proposed simplifications.  from two perspectives, isp's
> and architectural view.
> 
> Bryan Lyles, Sprint Deployment Strategy
> ---------------------------------------
> Today, multicast enabled, working with vendors and customers to make
> it work.  built on PIM-SM, MSDP, MBGP, IGMPV2, GLOP.
> 
> Short Term - push current protocols, work in ietf to enhance base.
> 
> Certain kinds of applications want single server (radio station,
> politician giving speech, dont want opposition heckling him)

If I remember well, this is not exactly what we said ... 
What we "also" sayed is that we 
encouter problems with providing stable and robust multicast service, 
and that we are not really satisfied with the current protocol
architecture 
and with its implementation (difficult to know if the architecture or
the implementation is broken).

The conslusion of the talk was that Sprint would like IETF to consider 
a protocol architecture that would be stable, more simple, and more
scalable.

> Hugh Holbrook, Stanford/Cisco
> -----------------------------
> Some multicast applications work well with unicast
> others its impossible, high data rates, many receivers
> questions to isp's - how do you bill for it.  make billing reflect
> cost.  so charge by size of group.
> 
>         dmm - if i am a source, receivers on same isp are onnet,
>         other receivers are offnet. want to billed for offnet folks.
> 
>         brad cain - bill by bandwidth, can isp's break even on multicast.
> 
> Queries flow down tree, counts flow back up, somehow gather data
> to bill src.  access control for large groups, restrict senders
> in advance (pirates on tv station), important for commercial
> applications too.
> 
>         kevin almeroth - why does it work with radia, lawyers are
>         the answers, no one owns a multicast address, if they did
>         you could sue someone for using yours without permission.
> 
> security - source provides passwd to receivers
> 
> www.dsg.stanford.edu/hollbrook/express
> 
> Jeremy Hall, uunet
> ------------------
> Problems - scalability, single source model ok, hard to implement.
> you are trying to restrict something that is not restrictable.
> lots of protocols running as ships in the night, ok when it works,
> never know which one is not working correctly.  way too much ad hoc
> stuff going on. which protocol is broken.  nice to be able to trace
> a problem from the sender, to the receiver.  receiver says i'm not
> receiving this content.  have to figure out from that info, where
> the source is and what the problem is.
> 
> Some applications hide the group, so you cant figure out where
> to troubleshoot.  people dont understand how it works, so they
> cant help you debug.  need education.
> 
> Billing problems, counting receivers might be nice but is hard
> as groups get big.  onnet vs offnet.  tried to employ things
> that are parallel to unicast.  unicast routing tries to dump traffic
> asap, mulitcast wants to keep as long as possible.  current model
> doesnt scale.  anyone can source to any group and thats a security
> problem.  there are a lot of security issues with multicast.
> 
> Mark Handley, ACIRI
> -------------------
> Internet Standard Multicast, where it came from and why it had
> nice properties.  direct extension of the unicast model, host
> sends packets to destination address, it gets there.  nice
> architecure, senders dont need to know about receivers.
> recievers dont need to know who senders are.  distributed binding
> is useful resource.  senders and receivers dont need to know about
> topology, robust, route around failures etc.  hosts dont need to
> knows about routing protocool.  need distinction between service
> model and its implementation in the network.  separates what
> the application wants and how the network achieves it.  clean
> separation of routing and transport/application layer.
> 
> What can we do with it:
> 
> Regular one to many applications - video distribution, data distribution
> many to many applications - conferening, games, dont know members in
> advance, distributed binding is very robust, changes the way you design
> applications (eg wb)
> 
> Many to few applications - server discovery
> 
> Scoping, used to have ttl scoping, poor for traffic engineering,
> great for self organizing applications, expanding ring search,
> we lost the ttl in pim, admin scoping getting it back, mzap
> 
> Security - can only restrict traffic safely with encryption.
> content providers want authentication, have the mechanisms already.
> 
> problems:
> 
>         forwarding table size, aggregation helps some;
>         how can isp's make money;
>         lack of scalable routing protocol, bgmp, hierarchical pim,
>           bi-direction pim with grib, bgmp will probably work,
>           hierarchical pim too;
>         lack or good network management and diagnostic tools.
> 
> serious growing pains, transition from dvmrp painful
> 
> distributed binding a key - wb, sdr, mimaze applications
> 
> important to avoid constraining network mechanisms to support only one
>   to many applications
> 
> Bryan - lots of differences of opionion in the community.
> Hugh  - avoid overly commplicating things for futures applications
>         when we have existing applications that need support now.
> 
> jon crowcroft, ucl, www.cs.ucl.ac.uk/research/rama
> --------------------------------------------------
> Enhancing deering multicast, enhancing the addressing scheme.
> class D address is a channel, not really an ip address.
> Anonymously names a group of receivers, allows anyone to send to it.
> alternatives, allow end systems to be explicit
> DCM/connectionless multicast - add list of addresses,
> transparency and fault tolerance
> 
> David Oran - Final Questions
> ----------------------------
> we have 5 minutes, where should we go with this?
> 
> Brian Whetten - wishes had heard more from isps about problems.
> 
> TODO - decide which problems are of deployment and which are based
> on what we are deploying.
> 
> Scott Petrak - 3 things: think about low bandwidth hosts at the end,
>   like wireless; thing 2 i missed; small number of senders a worthy
>   optimization.
> 
> Dorian Kim - deployment problems have been maturity of implementation issues
> and how to make all the hacks play together.  havent tried running native
> multicast at scales we want.  will find more answers as we deploy and ramp
> up, at this point probably not worth limiting model.
> 
> Hum votes
>         create a mailing list   2/3 hum
>         no mailing list         1/3 hum

-- 
=======================================================

christophe Diot         | tel: 1(650)375.4539
Sprint ATL              | fax: 1(650)375.4490
1 Adrian Court          | cdiot@sprintlabs.com
Burlingame CA 94010     | www.sprintlabs.com
USA                     |


From owner-idmr@cs.ucl.ac.uk  Mon Aug  2 14:51: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 OAA02663
	for <idmr-archive@lists.ietf.org>; Mon, 2 Aug 1999 14:51:51 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.14596-0@pan2.cs.ucl.ac.uk>;
          Mon, 2 Aug 1999 16:18:30 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.14590-0@pan2.cs.ucl.ac.uk>; Mon, 2 Aug 1999 16:18:26 +0100
Received: from hubbub.cisco.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.29820-0@bells.cs.ucl.ac.uk>; Mon, 2 Aug 1999 16:18:47 +0100
Received: from OranLT ([171.69.210.9]) 
          by hubbub.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.GATE.1.1) 
          with SMTP id IAA04139; Mon, 2 Aug 1999 08:18:09 -0700 (PDT)
From: David Oran <oran@cisco.com>
To: maddogs <maddogs@ietf.org>, idmr <idmr@cs.ucl.ac.uk>, idr <idr@merit.edu>,
        msdp <msdp@network-services.uoregon.edu>, pim <pim@catarina.usc.edu>,
        mboned <mboned@network-services.uoregon.edu>,
        malloc <malloc@catarina.usc.edu>, rmt <rmt@lbl.gov>
Subject: Maestro BoF Results
Date: Mon, 2 Aug 1999 11:17:41 -0400
Message-ID: <NBBBIFCAKKOPNMMKHHEFGEBGFFAA.oran@cisco.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 IMO, Build 9.0.2416 (9.0.2910.0)
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 Routing Area held a BoF at the Oslo IETF whose purpose was to discuss
potential refinements to the IP multicast model in two areas:
  1) Enhanced two-part multicast addressing to ease scalability and
deployment
     headaches,
  2) Optimizations to exploit the single-sender case

The BoF announcement, along with its scope and agenda, may be found at:
http://www.ietf.org/ietf/99jul/maestro-agenda-99jul.txt.

I am sending this message to who I think are all the relevant WG mailing
lists, and it will also be sent out via IETF-announce, so please let me know
directly if I've missed a relevant group rather than risk clogging peoples'
mailboxes with multiple forwards.

The minutes of BoF are attached below. One of the conclusions from the BoF
was to continue discussions on these subjects to ascertain if there is a
critical mass of support to charter one or more Working Groups to pursue
IETF standards (or other outputs) in these areas. We are therefore
resurrecting a moribund Routing Area mailing list for this purpose:
	routing-discussion@ietf.org
Subscription is via majordomo@ietf.org

Thanks to all who participated in the BoF and in advance for useful
low-flamability discussion on the mailing list.

Regards, Dave Oran (routing co-area director)




MAESTRO BOF, Dave Oran
----------------------

AGENDA

History - modify multicast model, do we need a working group
on this?

A number of people think if we simplify the multicast model
there are significant benefits in reducing complexity.
changes: addressing model, assume single sender.

We want to look at the problems today and see how proposed
simplications might help.

Ground rules: talk about problems and how they map to the
proposed simplifications.  from two perspectives, isp's
and architectural view.


Bryan Lyles, Sprint Deployment Strategy
---------------------------------------
Today, multicast enabled, working with vendors and customers to make
it work.  built on PIM-SM, MSDP, MBGP, IGMPV2, GLOP.

Short Term - push current protocols, work in ietf to enhance base.

Certain kinds of applications want single server (radio station,
politician giving speech, dont want opposition heckling him)


Hugh Holbrook, Stanford/Cisco
-----------------------------
Some multicast applications work well with unicast
others its impossible, high data rates, many receivers
questions to isp's - how do you bill for it.  make billing reflect
cost.  so charge by size of group.

	dmm - if i am a source, receivers on same isp are onnet,
	other receivers are offnet. want to billed for offnet folks.

	brad cain - bill by bandwidth, can isp's break even on multicast.

Queries flow down tree, counts flow back up, somehow gather data
to bill src.  access control for large groups, restrict senders
in advance (pirates on tv station), important for commercial
applications too.

	kevin almeroth - why does it work with radia, lawyers are
	the answers, no one owns a multicast address, if they did
	you could sue someone for using yours without permission.

security - source provides passwd to receivers

www.dsg.stanford.edu/hollbrook/express


Jeremy Hall, uunet
------------------
Problems - scalability, single source model ok, hard to implement.
you are trying to restrict something that is not restrictable.
lots of protocols running as ships in the night, ok when it works,
never know which one is not working correctly.  way too much ad hoc
stuff going on. which protocol is broken.  nice to be able to trace
a problem from the sender, to the receiver.  receiver says i'm not
receiving this content.  have to figure out from that info, where
the source is and what the problem is.

Some applications hide the group, so you cant figure out where
to troubleshoot.  people dont understand how it works, so they
cant help you debug.  need education.

Billing problems, counting receivers might be nice but is hard
as groups get big.  onnet vs offnet.  tried to employ things
that are parallel to unicast.  unicast routing tries to dump traffic
asap, mulitcast wants to keep as long as possible.  current model
doesnt scale.  anyone can source to any group and thats a security
problem.  there are a lot of security issues with multicast.


Mark Handley, ACIRI
-------------------
Internet Standard Multicast, where it came from and why it had
nice properties.  direct extension of the unicast model, host
sends packets to destination address, it gets there.  nice
architecure, senders dont need to know about receivers.
recievers dont need to know who senders are.  distributed binding
is useful resource.  senders and receivers dont need to know about
topology, robust, route around failures etc.  hosts dont need to
knows about routing protocool.  need distinction between service
model and its implementation in the network.  separates what
the application wants and how the network achieves it.  clean
separation of routing and transport/application layer.

What can we do with it:

Regular one to many applications - video distribution, data distribution
many to many applications - conferening, games, dont know members in
advance, distributed binding is very robust, changes the way you design
applications (eg wb)

Many to few applications - server discovery

Scoping, used to have ttl scoping, poor for traffic engineering,
great for self organizing applications, expanding ring search,
we lost the ttl in pim, admin scoping getting it back, mzap

Security - can only restrict traffic safely with encryption.
content providers want authentication, have the mechanisms already.

problems:

	forwarding table size, aggregation helps some;
	how can isp's make money;
	lack of scalable routing protocol, bgmp, hierarchical pim,
	  bi-direction pim with grib, bgmp will probably work,
	  hierarchical pim too;
	lack or good network management and diagnostic tools.

serious growing pains, transition from dvmrp painful

distributed binding a key - wb, sdr, mimaze applications

important to avoid constraining network mechanisms to support only one
  to many applications


Bryan - lots of differences of opionion in the community.
Hugh  - avoid overly commplicating things for futures applications
	when we have existing applications that need support now.


jon crowcroft, ucl, www.cs.ucl.ac.uk/research/rama
--------------------------------------------------
Enhancing deering multicast, enhancing the addressing scheme.
class D address is a channel, not really an ip address.
Anonymously names a group of receivers, allows anyone to send to it.
alternatives, allow end systems to be explicit
DCM/connectionless multicast - add list of addresses,
transparency and fault tolerance


David Oran - Final Questions
----------------------------
we have 5 minutes, where should we go with this?

Brian Whetten - wishes had heard more from isps about problems.

TODO - decide which problems are of deployment and which are based
on what we are deploying.

Scott Petrak - 3 things: think about low bandwidth hosts at the end,
  like wireless; thing 2 i missed; small number of senders a worthy
  optimization.

Dorian Kim - deployment problems have been maturity of implementation issues
and how to make all the hacks play together.  havent tried running native
multicast at scales we want.  will find more answers as we deploy and ramp
up, at this point probably not worth limiting model.

Hum votes
	create a mailing list   2/3 hum
	no mailing list 	1/3 hum







From owner-idmr@cs.ucl.ac.uk  Wed Aug 11 16:19:17 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 QAA06308
	for <idmr-archive@lists.ietf.org>; Wed, 11 Aug 1999 16:19:16 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.15782-0@pan2.cs.ucl.ac.uk>;
          Wed, 11 Aug 1999 17:49:30 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.15776-0@pan2.cs.ucl.ac.uk>; Wed, 11 Aug 1999 17:49:26 +0100
Received: from mailsrv.acc.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.27755-0@bells.cs.ucl.ac.uk>; Wed, 11 Aug 1999 17:46:20 +0100
Received: from opal.acc.com.acc (opal.acc.com [129.192.64.71]) 
          by mailsrv.acc.com (8.9.3/8.9.1) with SMTP id JAA04986 
          for <idmr@cs.ucl.ac.uk>; Wed, 11 Aug 1999 09:47:39 -0700 (PDT)
From: Ajit Bapat <ajitb@mailsrv.acc.com>
Message-Id: <199908111647.JAA04986@mailsrv.acc.com>
Subject: Questions on IGMP
To: idmr@cs.ucl.ac.uk
Date: Wed, 11 Aug 1999 10:15:38 -0700 (PDT)
X-Mailer: ELM [version 2.4 PL22]
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


Hello ,

    I have a couple of questions on IGMP, as I am reading RFC 2236.

1. In RFC 2236, the term 'interface' seems to point to a physical interface
   of a router.  The igmpCacheTable in <draft-ietf-idmr-igmp-mib-10.txt>
   also seems to index entries with {igmpCacheAddress, igmpCacheIfIndex}. 

     I am thinking of a case when there are multiple IP subnets configured on 
   a physical interface.  
   - Should IGMP run separately on each subnet ?  
   - Do all IP subnets on a physical interface share/use the same multicast 
     router ? 
   - Is it possible / useful for each subnet to use a different multicast 
     router ?
   - Does IGMP ignore sender's IP address in all its received packets ?

2. How does IGMPv2 use Router Alert option ? - RFC 2113 says it uses.


	Thanks for your time.

Ajit Bapat
ajitb@acc.com



From owner-idmr@cs.ucl.ac.uk  Wed Aug 11 21:11: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 VAA09145
	for <idmr-archive@lists.ietf.org>; Wed, 11 Aug 1999 21:11:01 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.15896-0@pan2.cs.ucl.ac.uk>;
          Thu, 12 Aug 1999 00:24:07 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.15890-0@pan2.cs.ucl.ac.uk>; Thu, 12 Aug 1999 00:24:03 +0100
Received: from mail-blue.research.att.com by bells.cs.ucl.ac.uk 
          with Internet SMTP id <g.14706-0@bells.cs.ucl.ac.uk>;
          Thu, 12 Aug 1999 00:24:41 +0100
Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) 
          by mail-blue.research.att.com (Postfix) with ESMTP id 9B3544CE0E;
          Wed, 11 Aug 1999 19:24:39 -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 TAA13413;
          Wed, 11 Aug 1999 19:24:37 -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 QAA02682; Wed, 11 Aug 1999 16:24:37 -0700 (PDT)
Message-Id: <199908112324.QAA02682@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: ajitb@mailsrv.acc.com
Subject: Re: Questions on IGMP
Cc: idmr@cs.ucl.ac.uk
Date: Wed, 11 Aug 1999 16:24:37 -0700
Versions: dmail (solaris) 2.2c/makemail 2.8t
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk


>   - Should IGMP run separately on each subnet ?  

No.

>   - Do all IP subnets on a physical interface share/use the same multicast 
>     router ? 

Yes.

>   - Is it possible / useful for each subnet to use a different multicast 
>     router ?

Without complex coordination, that would result in multiple copies
of the same packet when there are group members of the same group on
different subnets on the same wire.

>   - Does IGMP ignore sender's IP address in all its received packets ?

No, it's suggested to ensure that the sender's IP address belongs
to one of the subnets associated with the reception interface.

>2. How does IGMPv2 use Router Alert option ? - RFC 2113 says it uses.

As RFC2236 says, all messages described in the document contain a
Router Alert option in the IP header.  The option is useful mostly for
Report messages, which are addressed to the group being reported but
should be received by routers.

  Bill


From owner-idmr@cs.ucl.ac.uk  Thu Aug 12 21:15: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 VAA24543
	for <idmr-archive@lists.ietf.org>; Thu, 12 Aug 1999 21:15:42 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.16158-0@pan2.cs.ucl.ac.uk>;
          Thu, 12 Aug 1999 23:14:47 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.16152-0@pan2.cs.ucl.ac.uk>; Thu, 12 Aug 1999 23:14:43 +0100
Received: from rhine.cisco.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.12566-0@bells.cs.ucl.ac.uk>; Thu, 12 Aug 1999 23:15:21 +0100
Received: from kouvelas-u10.cisco.com (kouvelas-u10.cisco.com [171.69.55.73]) 
          by rhine.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP 
          id PAA12565; Thu, 12 Aug 1999 15:15:20 -0700 (PDT)
Received: from localhost (kouvelas@localhost) 
          by kouvelas-u10.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.WS.1.2) 
          with ESMTP id PAA25254; Thu, 12 Aug 1999 15:15:19 -0700 (PDT)
Message-Id: <199908122215.PAA25254@kouvelas-u10.cisco.com>
X-Authentication-Warning: kouvelas-u10.cisco.com: kouvelas owned process doing 
                          -bs
To: Brad Cain <bcain@nortelnetworks.com>
cc: idmr@cs.ucl.ac.uk, kouvelas@cisco.com
Subject: IGMPv3 draft questions
Date: Thu, 12 Aug 1999 15:15:19 -0700
From: Isidor Kouvelas <kouvelas@cisco.com>
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk


I am reading the router behavior section in the IGMPv3 draft and I have
spotted a couple of things that I think may be wrong.

In the table in section 5.2.4 I think the following two entries are the
wrong way round:
  Group
  Filter-Mode      Source Timer Value        Action
  -----------      ------------------        ------
  EXCLUDE          TIMER > 0                 Don't forward source
  EXCLUDE          TIMER == 0                Start forwarding source

As is stated in the second paragraph of section 5.2.3.3:
  "If a source timer expires with the group in EXCLUSION filter-mode,
   the router stops forwarding traffic from this source onto the
   interface, but does not delete its record."

The second problem I have is with the last entry in the table in section
5.2.5.1:

  Router State   Report Rec'd  New Router State         Actions
  ------------   ------------  ----------------         -------
  EXCLUDE (X,Y)  IS_EX (B)     EXCLUDE (X*B,Y-B)        Group Timer = TQ
                                            ^^^

I think the entry should read:
  EXCLUDE (X,Y)  IS_EX (B)     EXCLUDE (X*B,Y*B)        Group Timer = TQ
                                            ^^^

Can you please verify these two points.

thanks
Isidor


From owner-idmr@cs.ucl.ac.uk  Fri Aug 13 01:35:54 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 BAA02318
	for <idmr-archive@lists.ietf.org>; Fri, 13 Aug 1999 01:35:53 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.16279-0@pan2.cs.ucl.ac.uk>;
          Fri, 13 Aug 1999 05:17:46 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.16270-0@pan2.cs.ucl.ac.uk>; Fri, 13 Aug 1999 05:17:36 +0100
Received: from sdn-ar-004carcorP333.dialsprint.net by bells.cs.ucl.ac.uk 
          with Internet SMTP id <g.23832-0@bells.cs.ucl.ac.uk>;
          Fri, 13 Aug 1999 05:18:13 +0100
From: channel54 <channel54@suissemail.ch>
Subject: Free Web Site Analysis
Date: Wed, 11 Aug 1999 10:41:26
Message-Id: <445.647860.828848@bikkle.iac.co.jp>
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Apparently-To: idmr-pp

Email Removal Answering Service call Monday - Friday 8am-5pm 
Pacific time 877-855-2003. Sender/Site Owner is Traffic 
Accelerator. Removal no cost.
==================================================

** IMMEDIATELY INCREASE YOUR SITES EXPOSURE **


          FREE Web Site Analysis

         FREE Meta Tag Generator

        FREE Search Engine Checker

      FREE Search Engine Submissions


     100% Free - No Strings Attached
    No Obligation To Purchase Anything
        Use As Often As You Like


Why do we provide these Free services? It's 
our way of introducing ourselves to you and
to let you see our other web site promotion
products as well.

We are one of the largest web site submission
firms on the net today.  With over 3 1/2 years
of service we look forward to helping you 
make your site more profitable and productive.


       Mon - Fri 8am-5pm Pacific Time

                USA / Canada  
           Toll Free (877) 855-2003
              All Other Countries
             Direct (916) 771-4756


 ** IMMEDIATELY INCREASE YOUR SITES EXPOSURE **


To use these services there is no software
to download.  We provide the tools online 
from our web site. You operate them over the
internet from your home or office.  Just type
in a little information and you'll see the
results immediately.


FREE COMPREHENSIVE WEB SITE ANALYSIS:  

Obtain your comprehensive yet easy-to-read
web site analysis designed to provide you with 
valuable information.  Tired of not being found
in the search engines?  This online analysis
can help.  It takes less then 30 seconds.

FREE SEARCH ENGINE SUBMISSIONS:

We will submit your web site to 5 of the hottest
search engines with absolutely no obligation.

FREE SEARCH ENGINE CHECKER:

This FREE service checks to see if your web site
is in the top 12 search engines. It's fast,
accurate, and FREE.

FREE META TAG GENERATOR:

This FREE service provides you with an easy-to-use
program that will ask you a few simple questions
and provide you with all you need to know to
get Meta Tags in your web site.  

Remember - These services are FREE with No Strings 
Attached.  You are under No Obligation to purchase 
any of our other services.

If you want to obtain more exposure for your web site
then don't miss out on this valuable opportunity.  
Call NOW.


        Mon - Fri 8am-5pm Pacific Time
                USA / Canada  
           Toll Free (877) 855-2003
              All Other Countries
             Direct (916) 771-4756
 
 
 
 
 
 
 
 
 


From owner-idmr@cs.ucl.ac.uk  Fri Aug 13 01:36:02 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 BAA02353
	for <idmr-archive@lists.ietf.org>; Fri, 13 Aug 1999 01:36:01 -0400 (EDT)
Message-Id: <199908130536.BAA02353@ietf.org>
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.16242-0@pan2.cs.ucl.ac.uk>;
          Fri, 13 Aug 1999 04:41:38 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.16233-0@pan2.cs.ucl.ac.uk>; Fri, 13 Aug 1999 04:41:33 +0100
Received: from ABD6E502.ipt.aol.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.23022-0@bells.cs.ucl.ac.uk>; Fri, 13 Aug 1999 04:42:10 +0100
From: hifiber7 <hifiber7@compuserve.com>
Subject: AD:Family Reunion T Shirts & More
Date: Thu, 12 Aug 1999 19:47:10
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Apparently-To: idmr-pp

Message sent by:  Kuppler Graphics, 32 West Main Street, Maple Shade, New Jersey, 08052,
1-800-810-4330.   This list will NOT be sold.  All addresses 
are automatically added to our remove list.

Hello.  My name is Bill from Kuppler Graphics.  We do screenprinting on T Shirts, Sweatshirts,
Jackets, Hats, Tote Bags and more!

Do you or someone you know have a Family Reunion coming up?  Kuppler Graphics would like to
provide you with some great looking T Shirts for your Reunion.

Kuppler Graphics can also provide you with custom T's and promotional items such as imprinted
magnets, keychains, pens, mugs, hats, etc. for your business or any fundraising activity
(church, school, business etc.) We also can provide you with quality embroidery. 

We are a family owned company with over 15 years of experience.  

All work is done at this location.  No middle man.  Our prices are great!

Click reply to email us or call 1-800-810-4330 for more info


Bill
Kuppler Graphics
 
 
 
 
 
 
 
 
 
 


From owner-idmr@cs.ucl.ac.uk  Wed Aug 18 10:38:27 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 KAA13189
	for <idmr-archive@lists.ietf.org>; Wed, 18 Aug 1999 10:38:27 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.17402-0@pan2.cs.ucl.ac.uk>;
          Wed, 18 Aug 1999 11:53:33 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.17393-0@pan2.cs.ucl.ac.uk>; Wed, 18 Aug 1999 11:53:24 +0100
Received: from 1Cust115.tnt1.west-palm-beach.fl.da.uu.net by bells.cs.ucl.ac.uk 
          with Internet SMTP id <g.15109-0@bells.cs.ucl.ac.uk>;
          Wed, 18 Aug 1999 11:54:02 +0100
From: juniorhoster <juniorhoster@telkom.net>
Subject: GET YOUR OWN WEB SITE NOW FOR ONLY $9.95 PER MONTH!
Date: Fri, 20 Aug 1999 00:59:06
Message-Id: <315.689604.786821@mail.webster6245.com>
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Apparently-To: idmr-pp


                     LIMTIED TIME SPECIALS

 BUY ONE 5 meg WEBSITE AT OUR REGULAR PRICE AND GET THE OTHER ONE 
FOR FREE!

BUY ONE 100 meg website for only $40.00 per month and get 
16 months of service at one LOW PRICE!
_________________________________________________________________


Are You Paying TOO MUCH for Webspace???




STOP PAYING $20 OR MORE PER MONTH FOR YOUR WEB SPACE ...

You can CUT Your Web Charges IN HALF ...TODAY!

GET YOUR OWN WEB DOMAIN HOSTED(www.yourcompany.com) for JUST 
$9.95 PER MONTH!

Your new domain includes the latest server technology, multiple 
high-speed OC - 12 redundant backbone connnections, and 
personalized customer support!

Every domain includes ...

- 5 MB WEB STORAGE
- FRONT PAGE 98
- CYBER CASH*
- SECURE SERVER*
- ECOMMERCE ENABLING*
   (ACCEPT CREDIT CARDS)
- CGI-BIN FOR CUSTOM SCRIPTS
- REAL AUDIO/streaming audio*
- AUTOMATED SEARCH ENG. SUBMISSION*
- AND MUCH, MUCH MORE ...

.. All for just $9.95 per month!
*these features carry extra surcharges.

Simply transfer your domain and upload your data and you're all 
set to go.
We guarantee 1 hour SETUP with a simple phone call to our 
offices.

Why overpay a server when you can enjoy the features and 
performance of one of the countrys' largest webhosting 
organizations ... for less?  Reserve your space today!

Call 1 877 213 7949 for further information.




All web sites are pre-paid annually with a 90 day money back 
guarantee! A $40 setup fee applies to new customers.

Thank you for subscribing to our mailing list. If you wish no 
further mailings, just email juniorhoster@telkom.net with the 
word "UNSUBSCRIBE" typed in the subject line.




 
 
 
 
 
 
 
 
 
 
 


From owner-idmr@cs.ucl.ac.uk  Wed Aug 18 10:40:00 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 KAA13300
	for <idmr-archive@lists.ietf.org>; Wed, 18 Aug 1999 10:39:59 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.17446-0@pan2.cs.ucl.ac.uk>;
          Wed, 18 Aug 1999 12:51:07 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.17440-0@pan2.cs.ucl.ac.uk>; Wed, 18 Aug 1999 12:51:03 +0100
Received: from nscolmar.colmar.uha.fr by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.18832-0@bells.cs.ucl.ac.uk>; Wed, 18 Aug 1999 12:50:46 +0100
Received: by gate.colmar.uha.fr; (8.8.8/1.3/10May95) id NAA06885;
          Wed, 18 Aug 1999 13:27:27 +0200 (MET DST)
From: conf <conf@colmar.uha.fr>
Original-Received: from somewhere by smtpxd
PP-warning: Illegal Received field on preceding line
Message-Id: <3.0.5.32.19990818153130.009167b0@colmar.colmar.uha.fr>
X-Sender: conf@colmar.colmar.uha.fr
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Wed, 18 Aug 1999 15:31:30 +0200
To: conf@colmar.colmar.uha.fr
Subject: ECUMN'2000
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
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 KAA13300

Please feel free to circulate the CFP to interested colleagues. 
Accept our sincere apologies if you receive multiple copies of this CFP.

----------------------------------------------------------------------------
---

 	 	PRELIMINARY CALL FOR PAPERS

1st IEEE European Conference on Universal Multiservice Networks
IP Networks Versus Conventional Switched Networks
ECUMN'2000
October 16-18, 2000 - CREF, Colmar, France


URL: http://iutsun1.colmar.uha.fr/ECUMN2000.html

Sponsors are the following national scientific societies in Europe, which
cooperate under the roof of: EUREL, Brussels, Belgium: AEI, Milano (Italy),
IEE, London (UK), ÖVE/GIT, Vienna (Austria), SEE, Paris (France), SEV/ITG,
Fehraltorf, (Switzerland), VDE/ITG, Frankfurt (Germany) as well as the IEEE
Communications and Computer.

Supported by:
France Telecom
Alcatel
Newbridge
Other Supporters pending:


Conference Scope:

This conference follows the two successful ATM conferences events held in
Colmar, France in 1998 and 1999. The conference scope has been extended to
deal with the different topics related to Multiservice Network
Architectures, and Implementation, including among others, protocols,
signaling, traffic flow, addressing schemes, …

Fundamental questions still have to find an answer, such as:

How will the Internet, symbol of freedom, compete with the world of
traditional carrier networks or cooperate with it? 
Will alternate Technologies be needed to meet high level quality of service
requirements. 
What restrictions, if any, will result on the desired degree of freedom. 

Emphasis shall be put upon network convergence, including fixed/mobile
convergence  satisfying the needs of person to person communications, as
well as  Information and Entertainment applications 

With such a variety of problems to be solved, and such high economical
interests at stake there is a definite interest to exchange ideas,
technical results and proposals between the academic and industrial
communities and this is the major goal of the conference.

The scope of ECUMN'2000 encompasses but is not limited to:

Evolution of Telecommunication Networks Architecture:
	*	Core network
	*	Access networks
	*	CPN (Customer Premise Networks including home networks)
	*	Multiservice mobile networks
	*	Interoperability issues, Interfaces and Reference points
Packet, frame and cell protocols:
	*	Addressing
	*	Multicasting
	*	Switching and routing
	*	Signaling
	*	Traffic control and QOS
Network management and control:
	*	Network design - Migration strategies
	*	Active networks versus Intelligent networks
Service impact (multimedia, VPN, ...) on network architecture:
	*	Fixed-Mobile Convergence
	*	Packetized voice
	*	Experimentation and fields trials

Instructions for Authors

Mail four paper versions or E-mail preferably in Word 6 format, or
alternately a postscript version of a 2000-word extended abstract
summarizing an original work. All the manuscripts must be written in
English. The top of the first page of each paper should include the title
of the paper, authors' name, position, address, telephone and fax numbers,
Email of the author responsible for correspondence and a list of four
keywords at least. 

Authors of accepted papers will be invited to submit full-length
manuscripts for inclusion in the proceedings. All submitted papers should
be sent to the following address: 

Pascal LORENZ 
University of Haute Alsace 
IUT - Department GTR 
34 rue du Grillenbreit 
68008 Colmar, France 
Phone: 33 (0)389202366 Fax: 33 (0)389202359 Mobile: 33 (0)603658042 
E-mail: lorenz@colmar.uha.fr 

Important Deadlines:

Extended abstract due: January 10, 2000
Notification of acceptance: April 20, 2000
Camera-ready full papers due (2 columns, 8 pages max): June 20, 2000

Best papers will be forwarded for consideration in a special issue of the
journal "Annals of telecommunications".

TUTORIALS AND WORKSHOPS

Tutorials and workshops provide overviews of current high interest topics.
Proposals for half of full day tutorials are due by January 10, 2000.


Conference Committees

Organizing Committee

General Chair: Pascal Lorenz University of Haute Alsace France
Technical Program Chair: Annie Gravey, France Telecom CNET
Tutorials Chair: To be defined
Learned Societies Liaison Chair: Renato Israel SEE
Prosper Chemouil (France) - France Telecom CNET
Michel Levy (France) -. Alcatel
Jean-Louis Pernin (France) - Consultant
Guy Pujolle (France) - University of Versailles-Saint-Quentin
Sylvie Ritzenthaler (France) - Newbridge
Pierre Rolin (France) - France Telecom CNET

Scientific Program Committee:

H. Afifi (France) - ENST Bretagne
E. Biersack (France) - Eurecom
M. Boari (Italy) - University of Bologna
D. Bonjour (France) - France Telecom CNET 
T. Braun (Switzerland) - University of Berne
P. Brown (France) - France Telecom CNET
P. Chemouil (France) - France Telecom CNET
G. Colombo (Italy) - CSELT
J.P. Coudreuse (France) - Mitsubishi
W. Dabbous (France) - INRIA
A. Danthine (Belgium) - University libre of Liège
M . Diaz (France) - LAAS
M. Erradi (Morocco) - ENSIAS 
S. Fdida (France) - LIP6
G. Fiche (France) - Alcatel CIT
A. Gravey (France) - France Telecom CNET
S.J. Halme (Finland) - Helsinki University of Technology
G. Hébuterne (France) - INT
H.G. Hegering (Germany) - University of Munich
D. Hutchinson (UK) - Lancaster
R. Israel (France) - SEE 
A. Jajszczyk (Poland) - University of Mining & Metallurgy
M. Joubert (France) - Cegetel
F. Kamoun (Tunisia) - ENSI 
M. Karpov (Russia) - St Petersburg University
P. Key (UK) - Microsoft
D. Kofman (France) - ENST Paris
U. Korner (Sweden) - University of Lund
U . Krieger (Germany) - Deutsche Telecom
P. Kuhn (Germany) - University of Stuttgart
G.S. Kuo (Taiwan) - National Central University
M. Labetoulle (France) - Institut Eurecom Sophia-Antipolis
M. Le Boudec (Switzerland) - EPFL
F. Le Faucheur (France) - Cisco
G. Leduc (Belgium) - University of Liege
Y. Legrand (France) - Bouygues
M. Levy (France) - Alcatel
P. Lorenz (France) - University of Haute Alsace 
M. Loukola (Finland) - Helsinki University of Technology
B. Maglaris (Greece) - National Technical University Athens
H. Maher (Switzerland) - EPFL
Z. Mammeri (France) - University of Toulouse 
S. Martignoni (Switzerland) - Ascom TechLtd
N. Mastorakis (Greece) - Military Institutions of University Education
U. Mocci (Italy) - FUB
M. Nunes (Portugal) - IST/INESC
J.J. Pansiot (France) - University of Strasbourg
J.L. Pernin (France) - Consultant
G. Petit (Belgium) - Alcatel Anvers
M. Potts (Switzerland) - Martel 
G. Pujolle (France) - University of Versailles-Saint-Quentin
S. Rao (Switzerland) - Ascom 
M. Renaldo (France) - SAGEM
M. Riguidel (France) - Thomson
S. Ritzenthaler (France) - Newbridge 
J. Roberts (France) - France Telecom CNET
P. Rolin (France) - France Telecom CNET 
R. Schutz (France) - CS Telecom
H. Tobiet (France) - Clemessy 
S. Tohme (France) - ENST Paris
L. Toutain (France) - ENST Bretagne
P. Tran Gia (Germany) - University of Würzburg
P. Van Heck (The Netherlands) - Erasmus University
P. VanMieghem (The Netherlands) - University of Delft
E. Vazquez Gallo (Spain) - University of Madrid 
V.A. Villagra (Spain) - University of Madrid
M. Villen (Spain) - Telefonica I+D







From owner-idmr@cs.ucl.ac.uk  Fri Aug 20 17:29: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 RAA13230
	for <idmr-archive@lists.ietf.org>; Fri, 20 Aug 1999 17:29:42 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.00278-0@pan2.cs.ucl.ac.uk>;
          Fri, 20 Aug 1999 18:58:28 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.00272-0@pan2.cs.ucl.ac.uk>; Fri, 20 Aug 1999 18:58:23 +0100
Received: from cactus.fi.uba.ar by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.21802-0@bells.cs.ucl.ac.uk>; Fri, 20 Aug 1999 18:58:12 +0100
Received: from puna.fi.uba.ar (puna.fi.uba.ar [157.92.49.106]) 
          by cactus.fi.uba.ar (8.9.2/8.9.2) with ESMTP id OAA61711 
          for <idmr@cs.ucl.ac.uk>;
          Fri, 20 Aug 1999 14:58:52 -0300 (ART) (envelope-from ihameli@cactus.fi.uba.ar)
Date: Fri, 20 Aug 1999 14:56:44 -0300 (ART)
From: =?ISO-8859-1?Q?Jos=E9_Ignacio_ALVAREZ_HAMELIN_?= <ihameli@cactus.fi.uba.ar>
X-Sender: ihameli@puna.fi.uba.ar
To: idmr@cs.ucl.ac.uk
Subject: YAM question
Message-ID: <Pine.BSF.4.05.9908201453470.6769-100000@puna.fi.uba.ar>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
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 RAA13230


Hello, it is possible to obtain a description of YAM in a postscript
format?

Tank you in advance
                   
	
	Ing. José Ignacio ALVAREZ HAMELIN
______________________________________________________________

Laboratoire de Recherche en Informatique, LRI, Bâtiment 490, 
Université Paris Sud (XI), 91405-ORSAY Cedex , France
Tél:(33)01.69.15.64.09 Fax:01.69.15.65.86
e-mail: ihameli@lri.fr
_______________________________________________________________

 _______________________________________________
|                                               |
| Laboratorio de Tecnología y 			|
| Arquitectura de Sistemas Informáticos 	|
| Departamento de Electrónica 			|
| Facultad de Ingeniería 			|
| Universidad de Buenos Aires			|
|						|
| e-mail: ihameli@cactus.fi.uba.ar		|
|						|
| Paseo Colon 850 				|
| (C.P. 1063) Ciudad de Buenos Aires		|
| República Argentina				|
|_______________________________________________|




From owner-idmr@cs.ucl.ac.uk  Fri Aug 20 17:30:10 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 RAA13247
	for <idmr-archive@lists.ietf.org>; Fri, 20 Aug 1999 17:29:56 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.00346-0@pan2.cs.ucl.ac.uk>;
          Fri, 20 Aug 1999 21:30:32 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.00340-0@pan2.cs.ucl.ac.uk>; Fri, 20 Aug 1999 21:30:28 +0100
Received: from ns.time.saic.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.28701-0@bells.cs.ucl.ac.uk>; Fri, 20 Aug 1999 21:30:25 +0100
Received: from degas.time.saic.com (degas.time.saic.com [205.153.241.32]) 
          by prima.time.saic.com (8.9.3/8.8.5) with ESMTP id QAA04858 
          for <idmr@cs.ucl.ac.uk>; Fri, 20 Aug 1999 16:27:49 -0400 (EDT)
Message-Id: <199908202027.QAA04858@prima.time.saic.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: idmr@cs.ucl.ac.uk
Subject: YAM question
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 20 Aug 1999 16:30:10 -0400
From: Ken Carlberg <carlberg@time.saic.com>
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk


oops.  meant to send the previous message privately.  info on YAM can
be found in  <http://www.time.saic.com/~carlberg>

-ken




From owner-idmr@cs.ucl.ac.uk  Fri Aug 20 17:30: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 RAA13270
	for <idmr-archive@lists.ietf.org>; Fri, 20 Aug 1999 17:30:45 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.00321-0@pan2.cs.ucl.ac.uk>;
          Fri, 20 Aug 1999 21:02:16 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.00315-0@pan2.cs.ucl.ac.uk>; Fri, 20 Aug 1999 21:02:12 +0100
Received: from time.saic.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.26909-0@bells.cs.ucl.ac.uk>; Fri, 20 Aug 1999 21:02:10 +0100
Received: from degas.time.saic.com (degas.time.saic.com [205.153.241.32]) 
          by prima.time.saic.com (8.9.3/8.8.5) with ESMTP id PAA04781;
          Fri, 20 Aug 1999 15:53:11 -0400 (EDT)
Message-Id: <199908201953.PAA04781@prima.time.saic.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: =?ISO-8859-1?Q?Jos=E9_Ignacio_ALVAREZ_HAMELIN_?= <ihameli@cactus.fi.uba.ar>
cc: idmr@cs.ucl.ac.uk
Subject: Re: YAM question
In-Reply-To: Your message of "Fri, 20 Aug 1999 14:56:44 -0300." <Pine.BSF.4.05.9908201453470.6769-100000@puna.fi.uba.ar>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 20 Aug 1999 15:55:31 -0400
From: Ken Carlberg <carlberg@time.saic.com>
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk


Hola Jose,

Tu puedes obtenir varios articulos en revistas en estos indicatores:

	http://www.cs.ucl.ac.uk/staff/K.Carlberg/
  o
	http://www.time.saic.com/~carlberg/

Un articulo describe la arquitectura sobre YAM, un otro descibe la 
especificacion (pero es viajo), y el ultimo describe unos resultados 
de simulacion

Que disfrutas,

-ken




From owner-idmr@cs.ucl.ac.uk  Mon Aug 23 06:02: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 GAA07577
	for <idmr-archive@lists.ietf.org>; Mon, 23 Aug 1999 06:02:21 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.01168-0@pan2.cs.ucl.ac.uk>;
          Mon, 23 Aug 1999 08:10:36 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.01162-0@pan2.cs.ucl.ac.uk>; Mon, 23 Aug 1999 08:10:32 +0100
Received: from H-135-207-30-103.research.att.com by bells.cs.ucl.ac.uk 
          with Internet SMTP id <g.05520-0@bells.cs.ucl.ac.uk>;
          Mon, 23 Aug 1999 08:10:08 +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 296101E00E 
          for <idmr@cs.ucl.ac.uk>; Sun, 22 Aug 1999 16:45:16 -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 QAA02685 
          for <idmr@cs.ucl.ac.uk>; Sun, 22 Aug 1999 16:45:15 -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 NAA24691; Sun, 22 Aug 1999 13:45:14 -0700 (PDT)
Message-Id: <199908222045.NAA24691@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: idmr@cs.ucl.ac.uk
Subject: Open issues in draft-ietf-idmr-membership-reports-03.txt
Date: Sun, 22 Aug 1999 13:45:14 -0700
Versions: dmail (solaris) 2.2d/makemail 2.8u
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk


There are two open issues in draft-ietf-idmr-membership-reports-03.txt
which I would like to have a WG discussion on:

1. Should the source UDP port be restricted to 644 also, to raise the bar
on forging DWR's?  My take is no, because it's generally an unprivileged
operation to join a multicast group, so it's easy enough to cause DWR's
for a given group anyway.  In addition, the Security Considerations
section addresses forged messages anyway.

2. Should a Reporter Election mechanism be specified?  This is necessary
only when using Unicast replies for the case where the Domain-Wide Querier
cannot handle the implosion of the replies.  I think it's additional
complexity that should not be necessary, so my inclination is to not
include it.

Thanks for any feedback,
  Bill


From owner-idmr@cs.ucl.ac.uk  Tue Aug 24 20:35: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 UAA28132
	for <idmr-archive@lists.ietf.org>; Tue, 24 Aug 1999 20:35:34 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.01501-0@pan2.cs.ucl.ac.uk>;
          Tue, 24 Aug 1999 19:47:14 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.01495-0@pan2.cs.ucl.ac.uk>; Tue, 24 Aug 1999 19:47:10 +0100
Received: from motgate.mot.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.15260-0@bells.cs.ucl.ac.uk>; Tue, 24 Aug 1999 19:47:08 +0100
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) 
          by motgate.mot.com (MOT-motgate 1.0) with ESMTP id NAA26364 
          for <idmr@cs.ucl.ac.uk>; Tue, 24 Aug 1999 13:47:07 -0500 (CDT)]
Received: [from s-il02-d.comm.mot.com (s-il02-d.comm.mot.com [145.1.204.14]) 
          by pobox.mot.com (MOT-pobox 2.0) with ESMTP id NAA01064 
          for <idmr@cs.ucl.ac.uk>; Tue, 24 Aug 1999 13:47:07 -0500 (CDT)]
Received: by s-il02-d.comm.mot.com with Internet Mail Service (5.5.2580.0) 
          id <RF1YM07G>; Tue, 24 Aug 1999 13:47:07 -0500
Message-ID: <0F762B016151D2118F8900805FA795AF0216CC84@s-il02-n.comm.mot.com>
From: Narayanan Vidya-CVN065 <CVN065@lmpsil02.comm.mot.com>
To: "'idmr'" <idmr@cs.ucl.ac.uk>, "'pim'" <pim@catarina.usc.edu>
Subject: PIM-SMv2 functional clarification - join latency
Date: Tue, 24 Aug 1999 13:47:04 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2580.0)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

Hi,
I have a question about Join Latency for new receivers in PIM-SM. The 5th
point in Section 3.8.4 in RFC 2362 talks about the register suppression
timer. There is a line in it that says "A lower value means more frequesnt
register bursts at RP, while a higher value means longer join latency for
new receivers." This leads me to believe that if there is a DR sending a
PIM-Join message to the RP after the source-specific tree has been pruned by
the RP due to no members being present earlier, the time after which data
actually starts flowing to the DR will be dependent on the register
suppression timer value in the sender's DR. 

Let us consider the following scenario with 3 routers, SDR (Source's DR),
RDR (Receiver's DR), and the RP. Let the SDR and the RDR be directly
connected to the RP and not connected with each other. Let us assume that
the sourcing host and the receiving host are connected to the LAN ports of
the SDR and RDR respectively. Now, the scenario is like this:

1. Source starts sending data.
2. SDR register encapsulates the data packet(s) to the RP.
3. RP realizes that it has no downstream members. So, it prunes the
multicast tree back to the SDR. So, the RP must have an (S,G) entry with a
pruned flag.
4. Receiver joins the multicast group.
5. RDR sends a PIM Join to the RP for the same group for which the RP has a
pruned state.

In the above case, when would the receiver start receiving data? Would it
have to wait till the register suppression timer expires in the SDR and it
again sends data to the RP? In that case, if the register suppression timer
is set to the default, the join latency would be anywhere between 30 to 90
seconds. This seems like an awfully long join latency. Should not the PIM
Join message reaching the RP from the RDR trigger the RP to join again on
the earlier pruned tree? 

I am not sure if I am mistaking or missing something here. If this is
explained anywhere in the RFC, can anyone point me to it? If someone could
clarify how this is supposed to work, I would greatly appreciate that.

Thanks!
Vidya


From owner-idmr@cs.ucl.ac.uk  Tue Aug 24 20: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 UAA28142
	for <idmr-archive@lists.ietf.org>; Tue, 24 Aug 1999 20:35:40 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.01557-0@pan2.cs.ucl.ac.uk>;
          Tue, 24 Aug 1999 21:46:34 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.01551-0@pan2.cs.ucl.ac.uk>; Tue, 24 Aug 1999 21:46:28 +0100
Received: from mailhost.iprg.nokia.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.21168-0@bells.cs.ucl.ac.uk>; Tue, 24 Aug 1999 21:46:27 +0100
Received: from agni.iprg.nokia.com (agni.iprg.nokia.com [205.226.8.100]) 
          by mailhost.iprg.nokia.com (8.8.8/8.6.10) with ESMTP id NAA15137;
          Tue, 24 Aug 1999 13:45:39 -0700 (PDT)
Received: from agni.iprg.nokia.com (localhost [127.0.0.1]) 
          by agni.iprg.nokia.com (8.8.8/8.6.12) with ESMTP id NAA08005;
          Tue, 24 Aug 1999 13:45:37 -0700 (PDT)
Message-Id: <199908242045.NAA08005@agni.iprg.nokia.com>
To: Narayanan Vidya-CVN065 <CVN065@lmpsil02.comm.mot.com>
cc: "'idmr'" <idmr@cs.ucl.ac.uk>, "'pim'" <pim@catarina.usc.edu>
Subject: Re: PIM-SMv2 functional clarification - join latency
In-reply-to: Your message of "Tue, 24 Aug 1999 13:47:04 CDT." <0F762B016151D2118F8900805FA795AF0216CC84@s-il02-n.comm.mot.com>
Date: Tue, 24 Aug 1999 13:45:37 -0700
From: Ravi <ravi@iprg.nokia.com>
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

Narayanan Vidya-CVN065 writes:

| I have a question about Join Latency for new receivers in PIM-SM. The 5th
| point in Section 3.8.4 in RFC 2362 talks about the register suppression
| timer. There is a line in it that says "A lower value means more frequesnt
| register bursts at RP, while a higher value means longer join latency for
| new receivers." This leads me to believe that if there is a DR sending a
| PIM-Join message to the RP after the source-specific tree has been pruned by
| the RP due to no members being present earlier, the time after which data
| actually starts flowing to the DR will be dependent on the register
| suppression timer value in the sender's DR. 
| 
| Let us consider the following scenario with 3 routers, SDR (Source's DR),
| RDR (Receiver's DR), and the RP. Let the SDR and the RDR be directly
| connected to the RP and not connected with each other. Let us assume that
| the sourcing host and the receiving host are connected to the LAN ports of
| the SDR and RDR respectively. Now, the scenario is like this:
| 
| 1. Source starts sending data.
2. SDR register encapsulates the data packet(s) to the RP.
| 3. RP realizes that it has no downstream members. So, it prunes the
| multicast tree back to the SDR. So, the RP must have an (S,G) entry with a
| pruned flag.
| 4. Receiver joins the multicast group.
| 5. RDR sends a PIM Join to the RP for the same group for which the RP has a
| pruned state.
| 
| In the above case, when would the receiver start receiving data? Would it
| have to wait till the register suppression timer expires in the SDR and it
| again sends data to the RP? In that case, if the register suppression timer
| is set to the default, the join latency would be anywhere between 30 to 90
| seconds. This seems like an awfully long join latency. Should not the PIM
| Join message reaching the RP from the RDR trigger the RP to join again on
| the earlier pruned tree? 
| 
| I am not sure if I am mistaking or missing something here. If this is
| explained anywhere in the RFC, can anyone point me to it? If someone could
| clarify how this is supposed to work, I would greatly appreciate that.

When the <*,G> join is received by the RP from the RDR, it triggers
a join/prune message to the source. 

Refer Section 3.2.1 Sending join/prune Messages. The triggered
join/prune messages paragraph Case 2.3


      2 Receipt of a Join/Prune message for (S,G), (*,G) or
        (*,*,RP) will cause building or modifying corresponding state,
        and subsequent triggering of upstream Join/Prune messages, in
        the following cases:


           3 When there exists a (S,G)RPT-bit with null oif list,
             and an (*,G) Join/Prune message is received, the arriving
             interface is added to the oif list and a (*,G) Join/Prune
             message is triggered upstream.

cheers,
Ravi


From owner-idmr@cs.ucl.ac.uk  Tue Aug 24 20:36:05 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 UAA28153
	for <idmr-archive@lists.ietf.org>; Tue, 24 Aug 1999 20:36:03 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.01571-0@pan2.cs.ucl.ac.uk>;
          Tue, 24 Aug 1999 21:47:16 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.01565-0@pan2.cs.ucl.ac.uk>; Tue, 24 Aug 1999 21:47:03 +0100
Received: from 131.107.152.20 by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.21191-0@bells.cs.ucl.ac.uk>; Tue, 24 Aug 1999 21:47:03 +0100
Received: (from dthaler@localhost) by dthaler.microsoft.com (8.8.7/8.8.7) 
          id PAA14445;
          Tue, 24 Aug 1999 15:31:30 -0700 (PDT) (envelope-from dthaler)
From: Dave Thaler <dthaler@dthaler.microsoft.com>
Message-Id: <199908242231.PAA14445@dthaler.microsoft.com>
Subject: Re: PIM-SMv2 functional clarification - join latency
In-Reply-To: <0F762B016151D2118F8900805FA795AF0216CC84@s-il02-n.comm.mot.com> from Narayanan Vidya-CVN065 at "Aug 24, 1999 1:47: 4 pm"
To: CVN065@lmpsil02.comm.mot.com (Narayanan Vidya-CVN065)
Date: Tue, 24 Aug 1999 15:31:30 -0700 (PDT)
Cc: idmr@cs.ucl.ac.uk, pim@catarina.usc.edu
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

Vidya writes:
> I have a question about Join Latency for new receivers in PIM-SM. The 5th
> point in Section 3.8.4 in RFC 2362 talks about the register suppression
> timer. There is a line in it that says "A lower value means more frequesnt
> register bursts at RP, while a higher value means longer join latency for
> new receivers." This leads me to believe that if there is a DR sending a
> PIM-Join message to the RP after the source-specific tree has been pruned by
> the RP due to no members being present earlier, the time after which data
> actually starts flowing to the DR will be dependent on the register
> suppression timer value in the sender's DR. 
> 
> Let us consider the following scenario with 3 routers, SDR (Source's DR),
> RDR (Receiver's DR), and the RP. Let the SDR and the RDR be directly
> connected to the RP and not connected with each other. Let us assume that
> the sourcing host and the receiving host are connected to the LAN ports of
> the SDR and RDR respectively. Now, the scenario is like this:
> 
> 1. Source starts sending data.
> 2. SDR register encapsulates the data packet(s) to the RP.
> 3. RP realizes that it has no downstream members. So, it prunes the
> multicast tree back to the SDR. So, the RP must have an (S,G) entry with a
> pruned flag.
> 4. Receiver joins the multicast group.
> 5. RDR sends a PIM Join to the RP for the same group for which the RP has a
> pruned state.
> 
> In the above case, when would the receiver start receiving data? Would it
> have to wait till the register suppression timer expires in the SDR and it
> again sends data to the RP? 

Yes.

> In that case, if the register suppression timer
> is set to the default, the join latency would be anywhere between 30 to 90
> seconds. This seems like an awfully long join latency. Should not the PIM
> Join message reaching the RP from the RDR trigger the RP to join again on
> the earlier pruned tree? 

The RP is not required to keep per-sender state.  (If there are
100's of senders each sending 1 packet every 5 minutes, it may be
a bad idea to keep per-sender state.)  Hence, the RP doesn't know
what to do until the next register arrives.

-Dave


From owner-idmr@cs.ucl.ac.uk  Tue Aug 24 20:36: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 UAA28166
	for <idmr-archive@lists.ietf.org>; Tue, 24 Aug 1999 20:36:10 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.01646-0@pan2.cs.ucl.ac.uk>;
          Tue, 24 Aug 1999 22:14:36 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.01640-0@pan2.cs.ucl.ac.uk>; Tue, 24 Aug 1999 22:14:29 +0100
Received: from motgate2.mot.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.22672-0@bells.cs.ucl.ac.uk>; Tue, 24 Aug 1999 22:14:27 +0100
Received: [from pobox2.mot.com (pobox2.mot.com [129.188.137.195]) 
          by motgate2.mot.com (MOT-motgate2 1.0) with ESMTP id QAA21590 
          for <idmr@cs.ucl.ac.uk>; Tue, 24 Aug 1999 16:15:05 -0500 (CDT)]
Received: [from s-il02-d.comm.mot.com (s-il02-d.comm.mot.com [145.1.204.14]) 
          by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id QAA15290 
          for <idmr@cs.ucl.ac.uk>; Tue, 24 Aug 1999 16:14:24 -0500 (CDT)]
Received: by s-il02-d.comm.mot.com with Internet Mail Service (5.5.2580.0) 
          id <RF1YN1Z6>; Tue, 24 Aug 1999 16:14:24 -0500
Message-ID: <0F762B016151D2118F8900805FA795AF0216CC86@s-il02-n.comm.mot.com>
From: Narayanan Vidya-CVN065 <CVN065@lmpsil02.comm.mot.com>
To: "'Liming Wei'" <lwei@cisco.com>
Cc: cs-ipmulticast@cisco.com, "'idmr'" <idmr@cs.ucl.ac.uk>,
        "'pim'" <pim@catarina.usc.edu>
Subject: RE: PIM-SMv2 functional clarification - join latency
Date: Tue, 24 Aug 1999 16:14:21 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2580.0)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

Yes, I do know that on Cisco routers, the RP triggers the (S,G) join when
the new member joins. However, that is not how I interpreted it from the
spec. I am a little confused as to what the behavior is expected to be,
strictly according to the spec. Is this point stated anywhere in the spec
that the RP must trigger an (S,G) join on receiving a new PIM Join from a
DR? 

I am not sure if what I see on the Cisco routers is something specific to
the Cisco implementation of PIM-SM or is it more general than that.

Please clarify. I appreciate your input.

Thanks,
Vidya

> -----Original Message-----
> From: Liming Wei [mailto:lwei@cisco.com]
> Sent: Tuesday, August 24, 1999 3:57 PM
> To: CVN065@lmpsil02.comm.mot.com
> Cc: cs-ipmulticast@cisco.com
> Subject: Re: PIM-SMv2 functional clarification - join latency
> 
> 
> Vidya,
> 
> If you have a cisco testbed for this scenario, you will find the RP
> triggering the (S,G) join after the new member joins.
> 
> Or is this only based on your reading of the spec ?
> 
> -Liming
> ---------
> > From: Narayanan Vidya-CVN065 <CVN065@lmpsil02.comm.mot.com>
> > Date: Tue, 24 Aug 1999 13:47:04 -0500
> > CC: idmr@cs.ucl.ac.uk,pim@catarina.usc.edu
> > Sender: owner-pim-implementors@catarina.usc.edu
> > 
> > Hi,
> > I have a question about Join Latency for new receivers in 
> PIM-SM. The 5th
> > point in Section 3.8.4 in RFC 2362 talks about the register 
> suppression
> > timer. There is a line in it that says "A lower value means 
> more frequesnt
> > register bursts at RP, while a higher value means longer 
> join latency for
> > new receivers." This leads me to believe that if there is a 
> DR sending a
> > PIM-Join message to the RP after the source-specific tree 
> has been pruned by
> > the RP due to no members being present earlier, the time 
> after which data
> > actually starts flowing to the DR will be dependent on the register
> > suppression timer value in the sender's DR. 
> > 
> > Let us consider the following scenario with 3 routers, SDR 
> (Source's DR),
> > RDR (Receiver's DR), and the RP. Let the SDR and the RDR be directly
> > connected to the RP and not connected with each other. Let 
> us assume that
> > the sourcing host and the receiving host are connected to 
> the LAN ports of
> > the SDR and RDR respectively. Now, the scenario is like this:
> > 
> > 1. Source starts sending data.
> > 2. SDR register encapsulates the data packet(s) to the RP.
> > 3. RP realizes that it has no downstream members. So, it prunes the
> > multicast tree back to the SDR. So, the RP must have an 
> (S,G) entry with a
> > pruned flag.
> > 4. Receiver joins the multicast group.
> > 5. RDR sends a PIM Join to the RP for the same group for 
> which the RP has a
> > pruned state.
> > 
> > In the above case, when would the receiver start receiving 
> data? Would it
> > have to wait till the register suppression timer expires in 
> the SDR and it
> > again sends data to the RP? In that case, if the register 
> suppression timer
> > is set to the default, the join latency would be anywhere 
> between 30 to 90
> > seconds. This seems like an awfully long join latency. 
> Should not the PIM
> > Join message reaching the RP from the RDR trigger the RP to 
> join again on
> > the earlier pruned tree? 
> > 
> > I am not sure if I am mistaking or missing something here. 
> If this is
> > explained anywhere in the RFC, can anyone point me to it? 
> If someone could
> > clarify how this is supposed to work, I would greatly 
> appreciate that.
> > 
> > Thanks!
> > Vidya
> > 
> 


From owner-idmr@cs.ucl.ac.uk  Tue Aug 24 20: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 UAA28176
	for <idmr-archive@lists.ietf.org>; Tue, 24 Aug 1999 20:36:16 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.01716-0@pan2.cs.ucl.ac.uk>;
          Tue, 24 Aug 1999 22:25:38 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.01710-0@pan2.cs.ucl.ac.uk>; Tue, 24 Aug 1999 22:25:32 +0100
Received: from flipper.cisco.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.23425-0@bells.cs.ucl.ac.uk>; Tue, 24 Aug 1999 22:25:31 +0100
Received: (lwei@localhost) 
          by flipper.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) 
          id OAA01682; Tue, 24 Aug 1999 14:24:43 -0700 (PDT)
Date: Tue, 24 Aug 1999 14:24:43 -0700 (PDT)
Message-Id: <199908242124.OAA01682@flipper.cisco.com>
From: Liming Wei <lwei@cisco.com>
To: CVN065@lmpsil02.comm.mot.com
CC: cs-ipmulticast@cisco.com, idmr@cs.ucl.ac.uk, pim@catarina.usc.edu
In-reply-to: <0F762B016151D2118F8900805FA795AF0216CC86@s-il02-n.comm.mot.com> (message from Narayanan Vidya-CVN065 on Tue, 24 Aug 1999 16:14:21 -0500)
Subject: Re: PIM-SMv2 functional clarification - join latency
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: text/plain; charset=US-ASCII
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

> From: Narayanan Vidya-CVN065 <CVN065@lmpsil02.comm.mot.com>
> 
> Yes, I do know that on Cisco routers, the RP triggers the (S,G) join when
> the new member joins. However, that is not how I interpreted it from the
> spec. I am a little confused as to what the behavior is expected to be,
> strictly according to the spec. Is this point stated anywhere in the spec
> that the RP must trigger an (S,G) join on receiving a new PIM Join from a
> DR? 
> 
> I am not sure if what I see on the Cisco routers is something specific to
> the Cisco implementation of PIM-SM or is it more general than that.
> 
> Please clarify. I appreciate your input.


See messages from Dave and Ravi, this is not specific to cisco's
implementation.


-Liming


From owner-idmr@cs.ucl.ac.uk  Tue Aug 24 20:36: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 UAA28190
	for <idmr-archive@lists.ietf.org>; Tue, 24 Aug 1999 20:36:21 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.01898-0@pan2.cs.ucl.ac.uk>;
          Tue, 24 Aug 1999 22:47:23 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.01892-0@pan2.cs.ucl.ac.uk>; Tue, 24 Aug 1999 22:47:18 +0100
Received: from flipper.cisco.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.24913-0@bells.cs.ucl.ac.uk>; Tue, 24 Aug 1999 22:47:17 +0100
Received: (lwei@localhost) 
          by flipper.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) 
          id OAA03299; Tue, 24 Aug 1999 14:44:54 -0700 (PDT)
Date: Tue, 24 Aug 1999 14:44:54 -0700 (PDT)
Message-Id: <199908242144.OAA03299@flipper.cisco.com>
From: Liming Wei <lwei@cisco.com>
To: CVN065@lmpsil02.comm.mot.com
CC: cs-ipmulticast@cisco.com, idmr@cs.ucl.ac.uk, pim@catarina.usc.edu
In-reply-to: <0F762B016151D2118F8900805FA795AF0216CC88@s-il02-n.comm.mot.com> (message from Narayanan Vidya-CVN065 on Tue, 24 Aug 1999 16:37:51 -0500)
Subject: Re: PIM-SMv2 functional clarification - join latency
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: text/plain; charset=US-ASCII
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

> From: Narayanan Vidya-CVN065 <CVN065@lmpsil02.comm.mot.com>
> 
> I understood Dave's and Ravi's messages as contradicting each other. Maybe I
> am missing something here. It seemed like Dave said yes, you have to wait
> till the register suppression timer expires, while Ravi said that in section
> 3.2.1 of RFC 2362, it states that the RP sends a join/prune message in
> response to a (*,G) join that it receives. Please see my response to Ravi's
> mail that I sent before this one. 
> 
> So, I'm still not sure how this is supposed to work.

Here is what they said in English:

 1) If the RP has lost (S,G) state (due to any number of reasons including
    operator clearing state), the RP has to wait until the next
    (null) register to set up (S,G) state, and join again; (Dave)

 2) If the RP has not yet lost the (S,G) state, it should trigger a join
    to the source when the first member shows up. (Ravi)

-Liming


> 
> Vidya
> 
> 
> > See messages from Dave and Ravi, this is not specific to cisco's
> > implementation.
> > 
> > 
> > -Liming
> > 
> 


From owner-idmr@cs.ucl.ac.uk  Tue Aug 24 20:36: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 UAA28202
	for <idmr-archive@lists.ietf.org>; Tue, 24 Aug 1999 20:36:30 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.01996-0@pan2.cs.ucl.ac.uk>;
          Tue, 24 Aug 1999 22:56:19 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.01990-0@pan2.cs.ucl.ac.uk>; Tue, 24 Aug 1999 22:56:09 +0100
Received: from dip.eecs.umich.edu by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.25452-0@bells.cs.ucl.ac.uk>; Tue, 24 Aug 1999 22:56:08 +0100
Received: (from thalerd@localhost) by dip.eecs.umich.edu (8.9.2/8.9.2) 
          id RAA08131; Tue, 24 Aug 1999 17:56:01 -0400 (EDT)
From: Dave Thaler <thalerd@eecs.umich.edu>
Message-Id: <199908242156.RAA08131@dip.eecs.umich.edu>
Subject: Re: PIM-SMv2 functional clarification - join latency
To: lwei@cisco.com (Liming Wei)
Date: Tue, 24 Aug 1999 17:56:01 -0400 (EDT)
Cc: CVN065@lmpsil02.comm.mot.com, cs-ipmulticast@cisco.com, idmr@cs.ucl.ac.uk,
        pim@catarina.usc.edu
In-Reply-To: <199908242144.OAA03299@flipper.cisco.com> from "Liming Wei" at Aug 24, 99 02:44:54 pm
X-Mailer: ELM [version 2.4 PL23]
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

> Here is what they said in English:
> 
>  1) If the RP has lost (S,G) state (due to any number of reasons including
>     operator clearing state), the RP has to wait until the next
>     (null) register to set up (S,G) state, and join again; (Dave)
> 
>  2) If the RP has not yet lost the (S,G) state, it should trigger a join
>     to the source when the first member shows up. (Ravi)

I agree, and the other part of my point was:
   
   3) The spec does not require that the RP keep (S,G) state for every 
      source, if it does not join back to the source.
      Hence, if the RP implementation decides not to keep such state for
      low data-rate sources, then (1) is the usual behavior.  If the RP 
      implementation always creates (S,G) state at the RP, then (2) 
      may be the usual behavior.  Obviously the RP implementor has a 
      tradeoff to make between state and join latency.

Hopefully this helps to explain how the answers are not contradictory.

-Dave


From owner-idmr@cs.ucl.ac.uk  Tue Aug 24 20:36:47 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 UAA28218
	for <idmr-archive@lists.ietf.org>; Tue, 24 Aug 1999 20:36:46 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.02587-0@pan2.cs.ucl.ac.uk>;
          Tue, 24 Aug 1999 23:22:36 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.02577-0@pan2.cs.ucl.ac.uk>; Tue, 24 Aug 1999 23:22:23 +0100
Received: from ftpbox.mot.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.28392-0@bells.cs.ucl.ac.uk>; Tue, 24 Aug 1999 23:22:23 +0100
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) 
          by ftpbox.mot.com (MOT-ftpbox 1.0) with ESMTP id RAA06482 
          for <idmr@cs.ucl.ac.uk>; Tue, 24 Aug 1999 17:22:21 -0500 (CDT)]
Received: [from s-il02-e.comm.mot.com (s-il02-e.comm.mot.com [145.1.204.15]) 
          by pobox.mot.com (MOT-pobox 2.0) with ESMTP id RAA17746 
          for <idmr@cs.ucl.ac.uk>; Tue, 24 Aug 1999 17:22:21 -0500 (CDT)]
Received: by s-il02-e.comm.mot.com with Internet Mail Service (5.5.2580.0) 
          id <RF1XVHT8>; Tue, 24 Aug 1999 17:22:21 -0500
Message-ID: <0F762B016151D2118F8900805FA795AF0216CC8B@s-il02-n.comm.mot.com>
From: Narayanan Vidya-CVN065 <CVN065@lmpsil02.comm.mot.com>
To: "'Liming Wei'" <lwei@cisco.com>
Cc: cs-ipmulticast@cisco.com, idmr@cs.ucl.ac.uk, pim@catarina.usc.edu
Subject: RE: PIM-SMv2 functional clarification - join latency
Date: Tue, 24 Aug 1999 17:22:18 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2580.0)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

> Here is what they said in English:
> 
>  1) If the RP has lost (S,G) state (due to any number of 
> reasons including
>     operator clearing state), the RP has to wait until the next
>     (null) register to set up (S,G) state, and join again; (Dave)
> 

Yes, I agree with this in the event of no (S,G) state in the RP.


>  2) If the RP has not yet lost the (S,G) state, it should 
> trigger a join
>     to the source when the first member shows up. (Ravi)
> 

Here is where I am having a problem relating this to the RFC. The RFC only
seems to talk about (*,G) joins. Isn't it an (S,G) join that needs to go
from the RP to the source?

thanks,
Vidya


From owner-idmr@cs.ucl.ac.uk  Tue Aug 24 20:37:00 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 UAA28234
	for <idmr-archive@lists.ietf.org>; Tue, 24 Aug 1999 20:36:59 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.02836-0@pan2.cs.ucl.ac.uk>;
          Tue, 24 Aug 1999 23:33:07 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.02817-0@pan2.cs.ucl.ac.uk>; Tue, 24 Aug 1999 23:32:48 +0100
Received: from flipper.cisco.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.29461-0@bells.cs.ucl.ac.uk>; Tue, 24 Aug 1999 23:32:47 +0100
Received: (lwei@localhost) 
          by flipper.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) 
          id PAA06650; Tue, 24 Aug 1999 15:32:02 -0700 (PDT)
Date: Tue, 24 Aug 1999 15:32:02 -0700 (PDT)
Message-Id: <199908242232.PAA06650@flipper.cisco.com>
From: Liming Wei <lwei@cisco.com>
To: CVN065@lmpsil02.comm.mot.com
Cc: pim@catarina.usc.edu
In-reply-to: <0F762B016151D2118F8900805FA795AF0216CC8B@s-il02-n.comm.mot.com> (message from Narayanan Vidya-CVN065 on Tue, 24 Aug 1999 17:22:18 -0500)
Subject: Re: PIM-SMv2 functional clarification - join latency
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: text/plain; charset=US-ASCII
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

[Note, Bcc'ed idmr where members may not be interested in such
 details about PIM.]

> From: Narayanan Vidya-CVN065 <CVN065@lmpsil02.comm.mot.com>
> 
> >  2) If the RP has not yet lost the (S,G) state, it should 
> > trigger a join
> >     to the source when the first member shows up. (Ravi)
> > 
> 
> Here is where I am having a problem relating this to the RFC. The RFC only
> seems to talk about (*,G) joins. Isn't it an (S,G) join that needs to go
> >from the RP to the source?


When a (*,G) join is received and the arriving interaface is added to
the (*,G) outgoing interface list, the protocol specification requires
that the same interface is added to the (S,G) entry's outgoing interface
list as well.

The reason you heard the mentioning of (*,G) join, was because that
was the only thing the router connected to the new receiver knew. It
does it only knows G and the RP and how to send a (*,G) join. The RP,
if it has knowledge of (S,G), will know how to trigger (S,G) joins on
receipt of a (*,G) join.

-Liming


From owner-idmr@cs.ucl.ac.uk  Tue Aug 24 20:37: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 UAA28245
	for <idmr-archive@lists.ietf.org>; Tue, 24 Aug 1999 20:37:13 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.01826-0@pan2.cs.ucl.ac.uk>;
          Tue, 24 Aug 1999 22:38:02 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.01820-0@pan2.cs.ucl.ac.uk>; Tue, 24 Aug 1999 22:37:56 +0100
Received: from motgate2.mot.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.24257-0@bells.cs.ucl.ac.uk>; Tue, 24 Aug 1999 22:37:54 +0100
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) 
          by motgate2.mot.com (MOT-motgate2 1.0) with ESMTP id QAA03408 
          for <idmr@cs.ucl.ac.uk>; Tue, 24 Aug 1999 16:38:33 -0500 (CDT)]
Received: [from s-il02-e.comm.mot.com (s-il02-e.comm.mot.com [145.1.204.15]) 
          by pobox.mot.com (MOT-pobox 2.0) with ESMTP id QAA24491 
          for <idmr@cs.ucl.ac.uk>; Tue, 24 Aug 1999 16:37:52 -0500 (CDT)]
Received: by s-il02-e.comm.mot.com with Internet Mail Service (5.5.2580.0) 
          id <RF1XVG39>; Tue, 24 Aug 1999 16:37:52 -0500
Message-ID: <0F762B016151D2118F8900805FA795AF0216CC88@s-il02-n.comm.mot.com>
From: Narayanan Vidya-CVN065 <CVN065@lmpsil02.comm.mot.com>
To: "'Liming Wei'" <lwei@cisco.com>
Cc: cs-ipmulticast@cisco.com, idmr@cs.ucl.ac.uk, pim@catarina.usc.edu
Subject: RE: PIM-SMv2 functional clarification - join latency
Date: Tue, 24 Aug 1999 16:37:51 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2580.0)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

I understood Dave's and Ravi's messages as contradicting each other. Maybe I
am missing something here. It seemed like Dave said yes, you have to wait
till the register suppression timer expires, while Ravi said that in section
3.2.1 of RFC 2362, it states that the RP sends a join/prune message in
response to a (*,G) join that it receives. Please see my response to Ravi's
mail that I sent before this one. 

So, I'm still not sure how this is supposed to work.

Vidya


> See messages from Dave and Ravi, this is not specific to cisco's
> implementation.
> 
> 
> -Liming
> 


From owner-idmr@cs.ucl.ac.uk  Tue Aug 24 20:38:27 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 UAA28255
	for <idmr-archive@lists.ietf.org>; Tue, 24 Aug 1999 20:37:21 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.01778-0@pan2.cs.ucl.ac.uk>;
          Tue, 24 Aug 1999 22:31:19 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.01770-0@pan2.cs.ucl.ac.uk>; Tue, 24 Aug 1999 22:31:00 +0100
Received: from ftpbox.mot.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.23842-0@bells.cs.ucl.ac.uk>; Tue, 24 Aug 1999 22:30:59 +0100
Received: [from pobox2.mot.com (pobox2.mot.com [129.188.137.195]) 
          by ftpbox.mot.com (MOT-ftpbox 1.0) with ESMTP id QAA02252 
          for <idmr@cs.ucl.ac.uk>; Tue, 24 Aug 1999 16:30:47 -0500 (CDT)]
Received: [from s-il02-d.comm.mot.com (s-il02-d.comm.mot.com [145.1.204.14]) 
          by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id QAA23849 
          for <idmr@cs.ucl.ac.uk>; Tue, 24 Aug 1999 16:30:45 -0500 (CDT)]
Received: by s-il02-d.comm.mot.com with Internet Mail Service (5.5.2580.0) 
          id <RF1YNFHV>; Tue, 24 Aug 1999 16:30:44 -0500
Message-ID: <0F762B016151D2118F8900805FA795AF0216CC87@s-il02-n.comm.mot.com>
From: Narayanan Vidya-CVN065 <CVN065@lmpsil02.comm.mot.com>
To: "'Ravi'" <ravi@iprg.nokia.com>, "'Liming Wei'" <lwei@cisco.com>
Cc: "'idmr'" <idmr@cs.ucl.ac.uk>, "'pim'" <pim@catarina.usc.edu>
Subject: RE: PIM-SMv2 functional clarification - join latency
Date: Tue, 24 Aug 1999 16:30:42 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2580.0)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

I would agree with this statement, if 2.3 stated that for both (*,G) and
(S,G) entries. In the case I described, the RP would have to do an (S,G)
join back to the pruned source.


> 
> When the <*,G> join is received by the RP from the RDR, it triggers
> a join/prune message to the source. 
> 
> Refer Section 3.2.1 Sending join/prune Messages. The triggered
> join/prune messages paragraph Case 2.3
> 
> 
>       2 Receipt of a Join/Prune message for (S,G), (*,G) or
>         (*,*,RP) will cause building or modifying corresponding state,
>         and subsequent triggering of upstream Join/Prune messages, in
>         the following cases:
> 
> 
>            3 When there exists a (S,G)RPT-bit with null oif list,
>              and an (*,G) Join/Prune message is received, the arriving
>              interface is added to the oif list and a (*,G) Join/Prune
>              message is triggered upstream.
> 
> cheers,
> Ravi
> 


From owner-idmr@cs.ucl.ac.uk  Tue Aug 24 20: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 UAA28275
	for <idmr-archive@lists.ietf.org>; Tue, 24 Aug 1999 20:38:34 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.02200-0@pan2.cs.ucl.ac.uk>;
          Tue, 24 Aug 1999 23:05:31 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.02185-0@pan2.cs.ucl.ac.uk>; Tue, 24 Aug 1999 23:04:57 +0100
Received: from flipper.cisco.com by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.26334-0@bells.cs.ucl.ac.uk>; Tue, 24 Aug 1999 23:04:56 +0100
Received: (lwei@localhost) 
          by flipper.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) 
          id PAA04559; Tue, 24 Aug 1999 15:03:47 -0700 (PDT)
Date: Tue, 24 Aug 1999 15:03:47 -0700 (PDT)
Message-Id: <199908242203.PAA04559@flipper.cisco.com>
From: Liming Wei <lwei@cisco.com>
To: thalerd@eecs.umich.edu
CC: CVN065@lmpsil02.comm.mot.com, cs-ipmulticast@cisco.com, idmr@cs.ucl.ac.uk,
        pim@catarina.usc.edu
In-reply-to: <199908242156.RAA08131@dip.eecs.umich.edu> (message from Dave Thaler on Tue, 24 Aug 1999 17:56:01 -0400 (EDT))
Subject: Re: PIM-SMv2 functional clarification - join latency
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: text/plain; charset=US-ASCII
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk

> From: Dave Thaler <thalerd@eecs.umich.edu>
> 
> > Here is what they said in English:
> > 
> >  1) If the RP has lost (S,G) state (due to any number of reasons including
> >     operator clearing state), the RP has to wait until the next
> >     (null) register to set up (S,G) state, and join again; (Dave)
> > 
> >  2) If the RP has not yet lost the (S,G) state, it should trigger a join
> >     to the source when the first member shows up. (Ravi)
> 
> I agree, and the other part of my point was:
>    
>    3) The spec does not require that the RP keep (S,G) state for every 
>       source, if it does not join back to the source.
>       Hence, if the RP implementation decides not to keep such state for
>       low data-rate sources, then (1) is the usual behavior.  If the RP 
>       implementation always creates (S,G) state at the RP, then (2) 
>       may be the usual behavior.  Obviously the RP implementor has a 
>       tradeoff to make between state and join latency.
> 
> Hopefully this helps to explain how the answers are not contradictory.
> 


I agree on point 3 too. The implementator's freedom to make a decision
is a feature of the spec in that it accommodates implementations with
different resource constraints and requirements.

-Liming


From owner-idmr@cs.ucl.ac.uk  Fri Aug 27 09:43:16 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 JAA01212
	for <idmr-archive@lists.ietf.org>; Fri, 27 Aug 1999 09:43:15 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.05929-0@pan2.cs.ucl.ac.uk>;
          Fri, 27 Aug 1999 11:56:08 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.05923-0@pan2.cs.ucl.ac.uk>; Fri, 27 Aug 1999 11:56:04 +0100
Received: from odin.ietf.org by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.14913-0@bells.cs.ucl.ac.uk>; Fri, 27 Aug 1999 11:56:05 +0100
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) 
          by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21994;
          Fri, 27 Aug 1999 06:56:03 -0400 (EDT)
Message-Id: <199908271056.GAA21994@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-04.txt,.ps
Date: Fri, 27 Aug 1999 06:56:02 -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-04.txt,.ps
	Pages		: 16
	Date		: 26-Aug-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-04.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-04.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-04.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:	<19990826091429.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




From owner-idmr@cs.ucl.ac.uk  Sun Aug 29 14:54: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 OAA01634
	for <idmr-archive@lists.ietf.org>; Sun, 29 Aug 1999 14:54:38 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.06473-0@pan2.cs.ucl.ac.uk>;
          Sun, 29 Aug 1999 17:28:48 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.06467-0@pan2.cs.ucl.ac.uk>; Sun, 29 Aug 1999 17:28:44 +0100
Received: from 04-207.020.popsite.net by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.12270-0@bells.cs.ucl.ac.uk>; Sun, 29 Aug 1999 17:28:11 +0100
From: dee455 <dee455@eastmail.net>
Subject: save money on web hosting. get your own website for only 9.95 per month
Date: Tue, 31 Aug 1999 04:34:44
Message-Id: <279.349814.161273@mail.webster6245.com>
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Apparently-To: idmr-pp


    
Are You Paying TOO MUCH for Webspace???




STOP PAYING $20 OR MORE PER MONTH FOR YOUR WEB SPACE ...

You can CUT Your Web Charges IN HALF ...TODAY!

GET YOUR OWN WEB DOMAIN HOSTED(www.yourcompany.com) for JUST 
$9.95 PER MONTH!

Your new domain includes the latest server technology, multiple 
high-speed OC - 12 redundant backbone connnections, and 
personalized customer support!

Every domain includes ...

- 5 MB WEB STORAGE
- FRONT PAGE 98
- CYBER CASH*
- SECURE SERVER*
- ECOMMERCE ENABLING*
   (ACCEPT CREDIT CARDS)
- CGI-BIN FOR CUSTOM SCRIPTS
- REAL AUDIO/streaming audio*
- AUTOMATED SEARCH ENG. SUBMISSION*
- AND MUCH, MUCH MORE ...

.. All for just $9.95 per month!
*these features carry extra surcharges.

Simply transfer your domain and upload your data and you're all 
set to go.
We guarantee 1 hour SETUP with a simple phone call to our 
offices.

Why overpay a server when you can enjoy the features and 
performance of one of the countrys' largest webhosting 
organizations ... for less?  Reserve your space today!

Call 1 877 213 7949 for further information.

Outside of the United States please call 416 352 5710 for further 
information.


All web sites are pre-paid annually with a 90 day money back 
guarantee! A $40 setup fee applies to new customers.

Thank you for subscribing to our mailing list. If you wish no 
further mailings, just email webhoster543@yesbox.net with the 
word "UNSUBSCRIBE" typed in the subject line.




 
 
 
 
 


From owner-idmr@cs.ucl.ac.uk  Mon Aug 30 09:44:47 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 JAA28993
	for <idmr-archive@lists.ietf.org>; Mon, 30 Aug 1999 09:44:45 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.06686-0@pan2.cs.ucl.ac.uk>;
          Mon, 30 Aug 1999 12:03:16 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.06680-0@pan2.cs.ucl.ac.uk>; Mon, 30 Aug 1999 12:03:12 +0100
Received: from odin.ietf.org by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.12218-0@bells.cs.ucl.ac.uk>; Mon, 30 Aug 1999 12:03:12 +0100
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) 
          by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19823;
          Mon, 30 Aug 1999 07:03:09 -0400 (EDT)
Message-Id: <199908301103.HAA19823@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-mrdisc-02.txt
Date: Mon, 30 Aug 1999 07:03:09 -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		: IGMP Multicast Router Discovery
	Author(s)	: S. Biswas,  B. Cain, B. Haberman
	Filename	: draft-ietf-idmr-igmp-mrdisc-02.txt
	Pages		: 14
	Date		: 27-Aug-99
	
Companies have been proposing 'IGMP snooping' type schemes for
layer-2 bridging devices.  A method for discovery multicast capable
routers is necessary for these schemes.  An IGMP query message is
inadequate for discoverying multicast routers as one querier is
elected.  In order to 'discover' multicast routers, we introduce
two new types of IGMP messages: Multicast Router Advertisement and
Multicast Router Solicitation.  These two messages can be used by
any device which listens to IGMP to discovery multicast routers.
Multicast ROuter Solicitation messages may be used by any network
device (e.g. layer-2 switch) to solicit discovery messages from
multicast routers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idmr-igmp-mrdisc-02.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-mrdisc-02.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-mrdisc-02.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:	<19990827101657.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idmr-igmp-mrdisc-02.txt

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

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

--OtherAccess--

--NextPart--




From owner-idmr@cs.ucl.ac.uk  Tue Aug 31 11:31: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 LAA21635
	for <idmr-archive@lists.ietf.org>; Tue, 31 Aug 1999 11:31:45 -0400 (EDT)
Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk 
          via Local Delivery channel id <g.06992-0@pan2.cs.ucl.ac.uk>;
          Tue, 31 Aug 1999 13:56:34 +0100
Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP 
          id <g.06986-0@pan2.cs.ucl.ac.uk>; Tue, 31 Aug 1999 13:56:30 +0100
Received: from 05-023.020.popsite.net by bells.cs.ucl.ac.uk with Internet SMTP 
          id <g.20899-0@bells.cs.ucl.ac.uk>; Tue, 31 Aug 1999 13:56:30 +0100
From: dee455 <dee455@eastmail.net>
Subject: save money on web hosting. get your own website for only 9.95 per month
Date: Thu, 2 Sep 1999 01:02:58
Message-Id: <750.397854.724322@mail.webster6245.com>
Sender: owner-idmr@cs.ucl.ac.uk
Precedence: bulk
Apparently-To: idmr-pp


    
Are You Paying TOO MUCH for Webspace???

Call Internet Web Hosting Associates Today AT 1 877 213 7949


STOP PAYING $20 OR MORE PER MONTH FOR YOUR WEB SPACE ...

You can CUT Your Web Charges IN HALF ...TODAY!

GET YOUR OWN WEB DOMAIN HOSTED(www.yourcompany.com) for JUST 
$9.95 PER MONTH!

Your new domain includes the latest server technology, multiple 
high-speed OC - 12 redundant backbone connnections, and 
personalized customer support!

Every domain includes ...

- 5 MB WEB STORAGE
- FRONT PAGE 98
- CYBER CASH*
- SECURE SERVER*
- ECOMMERCE ENABLING*
   (ACCEPT CREDIT CARDS)
- CGI-BIN FOR CUSTOM SCRIPTS
- REAL AUDIO/streaming audio*
- AUTOMATED SEARCH ENG. SUBMISSION*
- AND MUCH, MUCH MORE ...

.. All for just $9.95 per month!
*these features carry extra surcharges.

Simply transfer your domain and upload your data and you're all 
set to go.
We guarantee 1 hour SETUP with a simple phone call to our 
offices.

Why overpay a server when you can enjoy the features and 
performance of one of the countrys' largest webhosting 
organizations ... for less?  Reserve your space today!

Call 1 877 213 7949 for further information.

Outside of the United States please call 416 352 5710 for further 
information.


All web sites are pre-paid annually with a 90 day money back 
guarantee! A $40 setup fee applies to new customers.

Thank you for subscribing to our mailing list. If you wish no 
further mailings, just email webhoster543@yesbox.net with the 
word "UNSUBSCRIBE" typed in the subject line.




 
 
 
 
 
 
 
 
 
 
 


