From owner-pim@catarina.usc.edu Tue Oct 3 09:51:40 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA11272 for ; Tue, 3 Oct 2000 09:51:40 -0400 (EDT) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id GAA04988 for pim-list; Tue, 3 Oct 2000 06:33:22 -0700 (PDT) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-pim@catarina.usc.edu using -f Received: from usc.edu (root@usc.edu [128.125.253.136]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id GAA04983 for ; Tue, 3 Oct 2000 06:33:20 -0700 (PDT) Received: from exchange01.iirltd.co.uk ([193.133.64.178]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id GAA25122 for ; Tue, 3 Oct 2000 06:33:19 -0700 (PDT) Received: by exchange01.iirltd.co.uk with Internet Mail Service (5.5.2650.21) id <4F3DVM5R>; Tue, 3 Oct 2000 14:27:18 +0100 Message-ID: From: Claire Tranah To: "'ctranah@iir-conferences.com'" Cc: "'ctranah@iir-conferences.com'" Subject: IP QoS Research Date: Tue, 3 Oct 2000 14:27:13 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-pim@catarina.usc.edu Precedence: bulk As a member of the MPLS working group I thought that you might be interested in some on going research into IP QoS. A number of experts will be presenting their findings at this event and full details can be found at www.telecomstransmission.com/ipqos. Please do not hesitate to contact me should you have any questions. Kind Regards Claire Tranah Telecoms and Technology IIR Ltd email: ctranah@iir-conferences.com ********************************** see my latest conference at www.iir-conferences.com/ipmobile ********************************** From owner-pim@catarina.usc.edu Wed Oct 4 12:37:19 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA25567 for ; Wed, 4 Oct 2000 12:37:15 -0400 (EDT) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id JAA29935 for pim-list; Wed, 4 Oct 2000 09:21:00 -0700 (PDT) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-pim@catarina.usc.edu using -f Received: from rumi.usc.edu (rumi.usc.edu [128.125.51.41]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id JAA29930 for ; Wed, 4 Oct 2000 09:20:59 -0700 (PDT) Received: (from pavlin@localhost) by rumi.usc.edu (8.9.3/8.9.3) id JAA40128 for pim@catarina.usc.edu; Wed, 4 Oct 2000 09:20:59 -0700 (PDT) Received: from usc.edu (root@usc.edu [128.125.253.136]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id IAA29453 for ; Wed, 4 Oct 2000 08:28:24 -0700 (PDT) Received: from phobos.talarian.com (mailhost.talarian.com [207.5.32.17]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id IAA06866 for ; Wed, 4 Oct 2000 08:28:02 -0700 (PDT) Received: from VAIO (ta037.talarian.com [204.147.187.37]) by phobos.talarian.com (8.9.0/8.9.0) with SMTP id IAA02291; Wed, 4 Oct 2000 08:26:20 -0700 (PDT) From: "Phil Farrar" To: Subject: Seminar: Catch the Vision of IP Multicast Date: Wed, 4 Oct 2000 10:17:15 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" 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.2919.6700 Sender: owner-pim@catarina.usc.edu Precedence: bulk X-MIME-Autoconverted: from 8bit to quoted-printable by catarina.usc.edu id JAA29935 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA25567 Learn first hand about the latest advances in IP multicast technology in a half-day seminar. (Registration is filling fast! Reserve your seat now!) Get expert advice on creating efficient one-to-many communications from industry leaders Talarian, Nortel Networks and SkyStream. Join us for registration and continental breakfast beginning at 8:00 am. The seminar program runs from 9 am – 12 noon. Talarian, a leader in real-time publish-subscribe messaging and reliable multicast is hosting the seminar series. Seating is limited so register now! www.talarian.com/seminar or call 800-543-8096 If you're a software developer, network architect, CIO, CTO or Director of MIS, this seminar is for you. Hear presentations about: · New developments in IP multicast technology · How to know when to use reliable multicast technology · Applications enabled by IP and reliable multicast · What multicast is doing for customers today · Where multicast needs to go in the future Learn how to: · Optimize satellite uplink/downlink throughput using PGM forward error correction · Re-architect your network to stream audio and video content to client applications · Reduce overhead of global data distribution and software updates · Instantly transfer financial data to wireless devices in real-time · Easily and effectively scale the distribution of data · Ensure your network infrastructure (e.g., routers) is multicast enabled Attend and you could win a TiVo with a 1-year subscription! This series of Talarian Seminars are being held in the following cities: New York, NY Wednesday, October 18 Marriott World Trade Center Richardson, TX Tuesday, October 24 Omni Richardson Hotel Denver, CO Wednesday, October 25 Hilton Denver Tech South Redwood City, CA Tuesday, October 31 Hotel Sofitel To attend a seminar or obtain information regarding other seminars in your area, please register at www.talarian.com/seminars or call 800-543-8096. To learn more about Talarian and their reliable multicasting and real-time publish-subscribe messaging products, visit www.talarian.com. From owner-pim@catarina.usc.edu Wed Oct 4 19:36:29 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA04336 for ; Wed, 4 Oct 2000 19:36:29 -0400 (EDT) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id QAA34121 for pim-list; Wed, 4 Oct 2000 16:23:00 -0700 (PDT) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-pim@catarina.usc.edu using -f Received: from usc.edu (root@usc.edu [128.125.253.136]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id QAA34116 for ; Wed, 4 Oct 2000 16:22:58 -0700 (PDT) Received: from smtprch1.nortel.com (smtprch1.nortelnetworks.com [192.135.215.14]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id QAA00974 for ; Wed, 4 Oct 2000 16:22:57 -0700 (PDT) Received: from zsc4c000.corpwest.baynetworks.com by smtprch1.nortel.com; Wed, 4 Oct 2000 18:14:13 -0500 Received: by zsc4c000.corpwest.baynetworks.com with Internet Mail Service (5.5.2652.35) id ; Wed, 4 Oct 2000 16:14:00 -0700 Message-ID: <5D630265EF50D311ABB60008C7917DB60320ED45@zsc4c004.corpwest.baynetworks.com> From: "Sundeep Singatwaria" To: pim@catarina.usc.edu Subject: DVMRP - PIM interop Date: Wed, 4 Oct 2000 16:13:53 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.35) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C02E58.C3113B20" Sender: owner-pim@catarina.usc.edu Precedence: bulk This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C02E58.C3113B20 Content-Type: text/plain; charset="iso-8859-1" Folks, I have a question regarding DVMRP - PIM interop Consider the following scenario (RP) DVMRP ------------ MBR ------------ PIM | | (Sender) Receiver The sender is on DVMRP domain and the receiver is on PIM domain. The RP is on PIM router (in above figure) The receiver goes away - we send a prune upstream to the DVMRP router. The interface connecting DVMRP to MBR is pruned for approximately two hours (based on DVMRP prune life time). Also the (S,G) entry on PIM router is cleaned up in less than two hours. If the receiver comes back before prune life time for DVMRP - how do we send a join upstream towards the DVMRP so that the tree is healed. Should the (S,G) entry created on RP be kept for greater than the prune life time for a DVMRP intf. - so that we can send join towards the source, if the receiver comes back. If there is some other mechanism do let me know. Thanks. Sundeep ------_=_NextPart_001_01C02E58.C3113B20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable DVMRP - PIM interop

Folks,
I have a question regarding DVMRP - PIM = interop

Consider the following scenario

          &nb= sp;           &nb= sp;           &nb= sp;      (RP)
     DVMRP ------------ MBR = ------------ PIM
      = |            = ;            = ;           |
     = (Sender)          &nbs= p;           &nbs= p;     Receiver

The sender is on DVMRP domain and the receiver is on = PIM domain. The RP is on PIM router (in above figure)

The receiver goes away - we send a prune upstream to = the DVMRP router. The interface connecting DVMRP to MBR is pruned for = approximately two hours (based on DVMRP prune life time). Also the = (S,G) entry on PIM router is cleaned up in less than two hours. If the = receiver comes back before prune life time for DVMRP - how do we send a = join upstream towards the DVMRP so that the tree is healed.

Should the (S,G) entry created on RP be kept for = greater than the prune life time for a DVMRP intf. - so that we can = send join towards the source, if the receiver comes back. If there is = some other mechanism do let me know.

Thanks.
Sundeep

------_=_NextPart_001_01C02E58.C3113B20-- From owner-pim@catarina.usc.edu Wed Oct 4 20:10:25 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA05010 for ; Wed, 4 Oct 2000 20:10:23 -0400 (EDT) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id QAA34529 for pim-list; Wed, 4 Oct 2000 16:58:26 -0700 (PDT) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-pim@catarina.usc.edu using -f Received: from usc.edu (root@usc.edu [128.125.253.136] (may be forged)) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id QAA34522 for ; Wed, 4 Oct 2000 16:58:25 -0700 (PDT) Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id QAA05725 for ; Wed, 4 Oct 2000 16:58:24 -0700 (PDT) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id 63CBF4CE2B; Wed, 4 Oct 2000 19:55:50 -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 TAA03793; Wed, 4 Oct 2000 19:55:49 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id QAA16685; Wed, 4 Oct 2000 16:55:49 -0700 (PDT) Message-Id: <200010042355.QAA16685@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: ssingatw@nortelnetworks.com Subject: Re: DVMRP - PIM interop Cc: pim@catarina.usc.edu Date: Wed, 4 Oct 2000 16:55:48 -0700 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-pim@catarina.usc.edu Precedence: bulk >The receiver goes away - we send a prune upstream to the DVMRP router. The >interface connecting DVMRP to MBR is pruned for approximately two hours >(based on DVMRP prune life time). MBR's should only prune for the PIM prune lifetime. Bill From owner-pim@catarina.usc.edu Fri Oct 6 03:33:18 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA26344 for ; Fri, 6 Oct 2000 03:33:18 -0400 (EDT) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id AAA48649 for pim-list; Fri, 6 Oct 2000 00:05:56 -0700 (PDT) Received: from usc.edu (root@usc.edu [128.125.253.136]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id AAA48644 for ; Fri, 6 Oct 2000 00:05:55 -0700 (PDT) Received: from ra.inria.fr (IDENT:root@ra.inria.fr [138.96.32.72]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id AAA10932 for ; Fri, 6 Oct 2000 00:05:53 -0700 (PDT) Received: from sophia.inria.fr by ra.inria.fr (8.10.0/8.10.0) with ESMTP id e9675nt01929 for ; Fri, 6 Oct 2000 09:05:49 +0200 X-Authentication-Warning: ra.inria.fr: Host localhost [127.0.0.1] claimed to be sophia.inria.fr Message-ID: <39DD79CA.32EC4179@sophia.inria.fr> Date: Fri, 06 Oct 2000 07:05:46 +0000 From: Fethi Filali Organization: INRIA Sophia-Antipolis X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.2.14 i586) X-Accept-Language: en MIME-Version: 1.0 To: pim@catarina.usc.edu Subject: Switching btw RPT and SPT in PIM-SM Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-pim@catarina.usc.edu Precedence: bulk Content-Transfer-Encoding: 7bit hi all, I have the following question about PIM-SM. The recommended switching (btw RPT and SPT) policy in PIM-SM specification is to initiate the switch to the SPT after receiving a significant number of data packets during a specified time interval from a particular source. I believe that this heuristic for determining when to migrate from the RPT to the SPT, and vise versa, is far from being sufficient. Are there other works or links concerning the switching mechanisms in PIM-SM. Thanks, -- FF From owner-pim@catarina.usc.edu Fri Oct 6 05:29:48 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA26976 for ; Fri, 6 Oct 2000 05:29:47 -0400 (EDT) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id CAA50294 for pim-list; Fri, 6 Oct 2000 02:05:26 -0700 (PDT) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-pim@catarina.usc.edu using -f Received: from usc.edu (root@usc.edu [128.125.253.136]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id CAA50287 for ; Fri, 6 Oct 2000 02:05:21 -0700 (PDT) Received: from relay1.alcatel.be (alc119.alcatel.be [195.207.101.119]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id CAA24000 for ; Fri, 6 Oct 2000 02:05:18 -0700 (PDT) Received: from bemail04.net.alcatel.be (localhost [127.0.0.1]) by relay1.alcatel.be (8.10.1/8.10.1) with SMTP id e9691vP25397; Fri, 6 Oct 2000 11:02:00 +0200 (MET DST) Received: from alcatel.be ([138.203.65.10]) by bemail04.net.alcatel.be (Lotus SMTP MTA v4.6.6 (890.1 7-16-1999)) with SMTP id C1256970.0031859C; Fri, 6 Oct 2000 11:00:54 +0200 Message-ID: <39DD9495.6600394A@alcatel.be> Date: Fri, 06 Oct 2000 11:00:05 +0200 From: Dirk Ooms X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Fethi Filali CC: pim@catarina.usc.edu Subject: Re: Switching btw RPT and SPT in PIM-SM References: <39DD79CA.32EC4179@sophia.inria.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-pim@catarina.usc.edu Precedence: bulk Content-Transfer-Encoding: 7bit > The recommended switching (btw RPT and SPT) policy in PIM-SM > specification is to initiate the switch to the SPT after receiving a > significant number of data packets during a specified time interval from > a particular source. > > I believe that this heuristic for determining when to migrate from the > RPT to the SPT, and vise versa, is far from being sufficient. > There is no vise versa. In practice the switch-over is made immediately (configured to a low bitrate). The RP only functions as a method for receivers to discover sources. dirk From owner-pim@catarina.usc.edu Fri Oct 6 05:40:22 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA27050 for ; Fri, 6 Oct 2000 05:40:22 -0400 (EDT) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id CAA50415 for pim-list; Fri, 6 Oct 2000 02:13:18 -0700 (PDT) Received: from usc.edu (root@usc.edu [128.125.253.136] (may be forged)) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id CAA50409 for ; Fri, 6 Oct 2000 02:13:17 -0700 (PDT) Received: from ra.inria.fr (IDENT:root@ra.inria.fr [138.96.32.72]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id CAA25927 for ; Fri, 6 Oct 2000 02:13:16 -0700 (PDT) Received: from sophia.inria.fr by ra.inria.fr (8.10.0/8.10.0) with ESMTP id e969BFt03474; Fri, 6 Oct 2000 11:11:21 +0200 X-Authentication-Warning: ra.inria.fr: Host localhost [127.0.0.1] claimed to be sophia.inria.fr Message-ID: <39DD9731.F98DC73F@sophia.inria.fr> Date: Fri, 06 Oct 2000 09:11:13 +0000 From: Fethi Filali Organization: INRIA Sophia-Antipolis X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.2.14 i586) X-Accept-Language: en MIME-Version: 1.0 To: Dirk Ooms CC: pim@catarina.usc.edu Subject: Re: Switching btw RPT and SPT in PIM-SM References: <39DD79CA.32EC4179@sophia.inria.fr> <39DD945A.8BFF88EF@alcatel.be> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-pim@catarina.usc.edu Precedence: bulk Content-Transfer-Encoding: 7bit Dirk Ooms wrote: > > > The recommended switching (btw RPT and SPT) policy in PIM-SM > > specification is to initiate the switch to the SPT after receiving a > > significant number of data packets during a specified time interval from > > a particular source. > > > > I believe that this heuristic for determining when to migrate from the > > RPT to the SPT, and vise versa, is far from being sufficient. > > There is no vise versa. Yes, in the RFC there is no provision to the vise versa but I think that it should be also possible ... > In practice the switch-over is made immediately (configured to a low > bitrate). The RP only functions as a method for receivers to discover > sources. I believe that the rate will not the only criteria to switch to the SPT and it depends of multicast applications ... Switching immediately to the SPT as you said eliminates the only advantage of PIM-SM comparing to CBT ... Fethi. From owner-pim@catarina.usc.edu Mon Oct 9 16:29:29 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA09768 for ; Mon, 9 Oct 2000 16:29:29 -0400 (EDT) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id NAA87946 for pim-list; Mon, 9 Oct 2000 13:05:53 -0700 (PDT) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-pim@catarina.usc.edu using -f Received: from usc.edu (root@usc.edu [128.125.253.136] (may be forged)) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id NAA87941 for ; Mon, 9 Oct 2000 13:05:52 -0700 (PDT) Received: from ferret.cs.fiu.edu (IDENT:root@ferret.cs.fiu.edu [131.94.125.231]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id NAA14625 for ; Mon, 9 Oct 2000 13:05:31 -0700 (PDT) Received: from cs.fiu.edu (IDENT:esj@heaven.cs.fiu.edu [131.94.133.12]) by ferret.cs.fiu.edu (8.9.3/FIU-CS-1.2) with ESMTP id QAA22375 for ; Mon, 9 Oct 2000 16:05:20 -0400 Message-Id: <200010092005.QAA22375@ferret.cs.fiu.edu> X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.27 To: pim@catarina.usc.edu Subject: pimd-2.1.0-alpha28 + solaris 8 = kernel panic X-image-url: http://www.cs.fiu.edu/~esj/ejthumb.gif Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Oct 2000 20:05:20 +0000 From: "Eric S. Johnson" Sender: owner-pim@catarina.usc.edu Precedence: bulk pimd-2.1.0-alpha28 Solaris 5.8 Generic_108528-02 sun4m sparc SUNW,SPARCstation-5 I finally got a sol8 machine in a gateway position and wanted to see if I could get pimd up and inter-operating with our cisco's. A couple minor changes to get the source to compile (I sent those to Pavlin in an earlier message this summer). Once I got it up and running I also found I had to change ADVANCE in routesock.c to ROUNDUP(16) to deal with the standard sockaddr size. And the BROKEN_CISCO_CHECKSUM. But that was it. And it kinda sorta worked. Till the kernel panic. (below from syslogs) A little more investigating and I found that the problem comes from k_chg_mfc and specifically the setsockopt(socket, IPPROTO_IP, MRT_ADD_MFC, (char *)&mc,sizeof(mc)) will crash the system *everytime* mc.mfcc_parent (ie iif) = 0. vif 0 is my "downstream of RP net" and vif 1 is "upstream to RP net". So changing the "if" so that setsockopt only gets called if iff!=0: if (iif && setsockopt(socket, IPPROTO_IP, MRT_ADD_MFC, .... and I am happily listening to KWAX over mbone again... (just in time for the cursed pledge drives... ;) And no crashes. But no traffic is getting out (no MFC adds from the downstream network) This is a sub optimal solution.. Any thoughts? I am still kind of shaky about how the MRT sock options work. (and docs.sun.com doesn't give much info to a search for MRT) E ----- unix: [ID 836849 kern.notice] panic[cpu0]/thread=f6539000: unix: [ID 641622 kern.notice] BAD TRAP: type=9 (Data fault) rp=fc02e574 addr=0 mmu_fsr=3a6 rw=2 occurred in module "ip" due to a NULL pointer dereference unix: [ID 100000 kern.notice] unix: [ID 839527 kern.notice] pimd: unix: [ID 702911 kern.notice] Data fault unix: [ID 189141 kern.notice] kernel write fault at addr=0x0, pme=0x0 unix: [ID 901159 kern.notice] MMU sfsr=3a6: unix: [ID 164009 kern.notice] Invalid Address unix: [ID 490779 kern.notice] on supv data store at level 3 unix: [ID 100000 kern.notice] unix: [ID 546445 kern.notice] pte addr = 0xf66a3b00, level = 3 unix: [ID 913234 kern.notice] pid=637, pc=0xf5a9a644, sp=0xfc02e5c0, psr=0x48010c7, context=75 unix: [ID 655124 kern.notice] g1-g7: f5aad000, 0, f5aad1b8, 45000014, f66cd918, f0041000, f6539000 unix: [ID 100000 kern.notice] genunix: [ID 872817 kern.notice] fc02e3f0 unix:die+b8 (9, f024c9a4, f024c800, 3a6, 2, 3a6) genunix: [ID 645206 kern.notice] %l0-7: fc02e574 00000000 fc02e574 00000020 00000000 f600f000 00000000 f5ab4000 genunix: [ID 872817 kern.notice] fc02e470 unix:trap+774 (0, 1, f0000000, f66a70a8, f66cd918, 0) genunix: [ID 645206 kern.notice] %l0-7: 00000000 00000000 fc02e574 00000009 000003a6 00000002 00000000 f0269800 genunix: [ID 872817 kern.notice] fc02e518 unix:fault+84 (f648b560, f648b560, f5dfb900, 0, f00451c8, 0) genunix: [ID 645206 kern.notice] %l0-7: 048010c7 f5a9a644 f5a9a648 00000008 00000009 00000080 f024fbb8 fc02e518 genunix: [ID 872817 kern.notice] fc02e5c0 ip:register_send+b8 (f5aacc00, f674e400, f5dfb900, f600e8b0, 0, f5914c40) genunix: [ID 645206 kern.notice] %l0-7: 044010c0 f00987a0 f00987a4 00000001 00000000 f5ab37bc 00000000 00000003 genunix: [ID 872817 kern.notice] fc02e620 ip:ip_mdq+2cc (2, f5aad1d0, f5ab3260, 40, f5ab321c, 40) genunix: [ID 645206 kern.notice] %l0-7: 00000000 00000000 f600e8b0 f5dfb900 f5a0f518 f64f1074 e002f60d 00000003 genunix: [ID 872817 kern.notice] fc02e680 ip:add_mfc+2a8 (0, f5aacc24, f5ab385c, 28, f67417e4, 68) genunix: [ID 645206 kern.notice] %l0-7: 00000001 f64f1074 f6704cd4 00000004 00000000 00000030 00000000 f5aae2e0 genunix: [ID 872817 kern.notice] fc02e6e8 ip:ip_opt_set+760 (f67417e4, 30, 0, 1, f67417e0, f67417e4) genunix: [ID 645206 kern.notice] %l0-7: f653c4f0 00000000 f67417e4 00000008 00000000 00000030 00000000 f5b0c7e8 genunix: [ID 872817 kern.notice] fc02e760 ip:svr4_optcom_req+608 (f6741814, f5a6943c, f6741814, f6744ac0, f5a68588, f67417c8) genunix: [ID 645206 kern.notice] %l0-7: 00000000 00000031 f5aad208 f67417c8 f6741814 f672a80c f6741814 00000001 genunix: [ID 872817 kern.notice] fc02e7d0 unix:putnext+1c4 (f672a6ac, f6744ac0, f5a72568, 0, 0, f672a80c) genunix: [ID 645206 kern.notice] %l0-7: f5c6ff78 f672a6ac 00000000 f67417c8 f6741814 f672a6ac f6741814 00000001 genunix: [ID 872817 kern.notice] fc02e830 icmp:icmp_wput+488 (f672a6ac, f6744ac0, 20, f5b0c9fc, 0, f656bb80) genunix: [ID 645206 kern.notice] %l0-7: 044010c6 f6744ac0 f672a6ac 00000001 00000002 00000002 00000007 f6557514 genunix: [ID 872817 kern.notice] fc02e898 unix:putnext+1c4 (f672a96c, f6744ac0, f5b3ae24, 0, 0, f672a6ac) genunix: [ID 645206 kern.notice] %l0-7: f5c6f9c8 f672a96c 00000000 fc02ead0 fc02ea0c ffffffff 00000000 00000000 genunix: [ID 872817 kern.notice] fc02e8f8 genunix:strput+210 (0, 2c4, f672a96c, fc02ead0, 0, 0) genunix: [ID 645206 kern.notice] %l0-7: f6744ac0 00000000 00000000 00000000 00000000 00000000 00000000 00000000 genunix: [ID 872817 kern.notice] fc02ea10 genunix:kstrputmsg+2d0 (f66afd40, 200, c0, 40, 80, f672a96c) genunix: [ID 645206 kern.notice] %l0-7: 00000000 00000000 00000000 f66ac74c 000002c4 00000000 f66ac700 00000000 genunix: [ID 872817 kern.notice] fc02ea80 sockfs:sosetsockopt+140 (ffff, f66afd88, 0, 0, 30, f66afd40) genunix: [ID 645206 kern.notice] %l0-7: 00000068 f65240c0 00000000 00000000 00000000 00000000 00000000 00000000 genunix: [ID 872817 kern.notice] fc02eb18 sockfs:setsockopt+b0 (f66afd40, 30, f65240c0, effff488, 68, 0) genunix: [ID 645206 kern.notice] %l0-7: 00000003 00000030 ef6968bc f0064400 00000000 f024ac00 f024fbb8 fc02eb80 unix: [ID 100000 kern.notice] genunix: [ID 672855 kern.notice] syncing file systems... unix: [ID 836849 kern.notice] panic[cpu0]/thread=f6539000: unix: [ID 849363 kern.notice] BAD TRAP: type=7 (Memory address alignment) rp=f0257ac4 addr=0 mmu_fsr=0 rw=0 unix: [ID 100000 kern.notice] genunix: [ID 353387 kern.notice] dumping to /dev/dsk/c0t3d0s4, offset 26935296 genunix: [ID 904073 kern.notice] done genunix: [ID 409368 kern.notice] 100% done: 3943 pages dumped, compression ratio 2.28, genunix: [ID 851671 kern.notice] dump succeeded From owner-pim@catarina.usc.edu Mon Oct 9 17:52:55 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA10373 for ; Mon, 9 Oct 2000 17:52:55 -0400 (EDT) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id OAA88738 for pim-list; Mon, 9 Oct 2000 14:33:51 -0700 (PDT) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-pim@catarina.usc.edu using -f Received: from usc.edu (root@usc.edu [128.125.253.136]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id OAA88733 for ; Mon, 9 Oct 2000 14:33:50 -0700 (PDT) Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id OAA04322 for ; Mon, 9 Oct 2000 14:33:48 -0700 (PDT) Received: from engmail2.Eng.Sun.COM ([129.146.1.25]) by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA25688; Mon, 9 Oct 2000 15:33:39 -0600 (MDT) Received: from nasnfs.eng.sun.com (nasnfs.Eng.Sun.COM [10.6.84.20]) by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA10790; Mon, 9 Oct 2000 14:33:38 -0700 (PDT) Received: from valathar (valathar [129.146.122.176]) by nasnfs.eng.sun.com (8.9.3+Sun/8.9.1) with SMTP id OAA27714; Mon, 9 Oct 2000 14:33:33 -0700 (PDT) Date: Mon, 9 Oct 2000 14:33:34 -0700 (PDT) From: "Michael F. Speer" Reply-To: "Michael F. Speer" Subject: Re: pimd-2.1.0-alpha28 + solaris 8 = kernel panic To: "Eric S. Johnson" Cc: pim@catarina.usc.edu In-Reply-To: "Your message with ID" <200010092005.QAA22375@ferret.cs.fiu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-pim@catarina.usc.edu Precedence: bulk Eric: There is bug that has a fix for this. Don't know where the patch is. I will check for you. Michael > > pimd-2.1.0-alpha28 > Solaris 5.8 Generic_108528-02 sun4m sparc SUNW,SPARCstation-5 > > I finally got a sol8 machine in a gateway position and wanted to see if > I could get pimd up and inter-operating with our cisco's. > > A couple minor changes to get the source to compile (I sent those > to Pavlin in an earlier message this summer). > > Once I got it up and running I also found I had to change ADVANCE in > routesock.c to ROUNDUP(16) to deal with the standard sockaddr size. > And the BROKEN_CISCO_CHECKSUM. But that was it. And it kinda sorta worked. > > Till the kernel panic. (below from syslogs) > > A little more investigating and I found that the problem comes from > k_chg_mfc and specifically the > > setsockopt(socket, IPPROTO_IP, MRT_ADD_MFC, (char *)&mc,sizeof(mc)) > > will crash the system *everytime* mc.mfcc_parent (ie iif) = 0. > > vif 0 is my "downstream of RP net" and vif 1 is "upstream to RP net". > > So changing the "if" so that setsockopt only gets called if iff!=0: > > if (iif && setsockopt(socket, IPPROTO_IP, MRT_ADD_MFC, .... > > and I am happily listening to KWAX over mbone again... (just in time > for the cursed pledge drives... ;) And no crashes. > > But no traffic is getting out (no MFC adds from the downstream network) > This is a sub optimal solution.. > > > > Any thoughts? I am still kind of shaky about how the MRT sock options > work. (and docs.sun.com doesn't give much info to a search for MRT) > > E > > ----- > > > unix: [ID 836849 kern.notice] > panic[cpu0]/thread=f6539000: > unix: [ID 641622 kern.notice] BAD TRAP: type=9 (Data fault) rp=fc02e574 > addr=0 mmu_fsr=3a6 rw=2 occurred in module "ip" due to a NULL pointer > dereference unix: [ID 100000 kern.notice] > unix: [ID 839527 kern.notice] pimd: > unix: [ID 702911 kern.notice] Data fault > unix: [ID 189141 kern.notice] kernel write fault at addr=0x0, pme=0x0 > unix: [ID 901159 kern.notice] MMU sfsr=3a6: > unix: [ID 164009 kern.notice] Invalid Address > unix: [ID 490779 kern.notice] on supv data store at level 3 > unix: [ID 100000 kern.notice] > unix: [ID 546445 kern.notice] pte addr = 0xf66a3b00, level = 3 > unix: [ID 913234 kern.notice] pid=637, pc=0xf5a9a644, sp=0xfc02e5c0, > psr=0x48010c7, context=75 unix: [ID 655124 kern.notice] g1-g7: f5aad000, 0, > f5aad1b8, 45000014, f66cd918, f0041000, f6539000 unix: [ID 100000 > kern.notice] genunix: [ID 872817 kern.notice] fc02e3f0 unix:die+b8 (9, > f024c9a4, f024c800, 3a6, 2, 3a6) genunix: [ID 645206 kern.notice] %l0-7: > fc02e574 00000000 fc02e574 00000020 00000000 f600f000 00000000 f5ab4000 > genunix: [ID 872817 kern.notice] fc02e470 unix:trap+774 (0, 1, f0000000, > f66a70a8, f66cd918, 0) genunix: [ID 645206 kern.notice] %l0-7: 00000000 > 00000000 fc02e574 00000009 000003a6 00000002 00000000 f0269800 genunix: [ID > 872817 kern.notice] fc02e518 unix:fault+84 (f648b560, f648b560, f5dfb900, 0, > f00451c8, 0) genunix: [ID 645206 kern.notice] %l0-7: 048010c7 f5a9a644 > f5a9a648 00000008 00000009 00000080 f024fbb8 fc02e518 genunix: [ID 872817 > kern.notice] fc02e5c0 ip:register_send+b8 (f5aacc00, f674e400, f5dfb900, > f600e8b0, 0, f5914c40) genunix: [ID 645206 kern.notice] %l0-7: 044010c0 > f00987a0 f00987a4 00000001 00000000 f5ab37bc 00000000 00000003 genunix: [ID > 872817 kern.notice] fc02e620 ip:ip_mdq+2cc (2, f5aad1d0, f5ab3260, 40, > f5ab321c, 40) genunix: [ID 645206 kern.notice] %l0-7: 00000000 00000000 > f600e8b0 f5dfb900 f5a0f518 f64f1074 e002f60d 00000003 genunix: [ID 872817 > kern.notice] fc02e680 ip:add_mfc+2a8 (0, f5aacc24, f5ab385c, 28, f67417e4, > 68) genunix: [ID 645206 kern.notice] %l0-7: 00000001 f64f1074 f6704cd4 > 00000004 00000000 00000030 00000000 f5aae2e0 genunix: [ID 872817 > kern.notice] fc02e6e8 ip:ip_opt_set+760 (f67417e4, 30, 0, 1, f67417e0, > f67417e4) genunix: [ID 645206 kern.notice] %l0-7: f653c4f0 00000000 > f67417e4 00000008 00000000 00000030 00000000 f5b0c7e8 genunix: [ID 872817 > kern.notice] fc02e760 ip:svr4_optcom_req+608 (f6741814, f5a6943c, f6741814, > f6744ac0, f5a68588, f67417c8) genunix: [ID 645206 kern.notice] %l0-7: > 00000000 00000031 f5aad208 f67417c8 f6741814 f672a80c f6741814 00000001 > genunix: [ID 872817 kern.notice] fc02e7d0 unix:putnext+1c4 (f672a6ac, > f6744ac0, f5a72568, 0, 0, f672a80c) genunix: [ID 645206 kern.notice] > %l0-7: f5c6ff78 f672a6ac 00000000 f67417c8 f6741814 f672a6ac f6741814 > 00000001 genunix: [ID 872817 kern.notice] fc02e830 icmp:icmp_wput+488 > (f672a6ac, f6744ac0, 20, f5b0c9fc, 0, f656bb80) genunix: [ID 645206 > kern.notice] %l0-7: 044010c6 f6744ac0 f672a6ac 00000001 00000002 00000002 > 00000007 f6557514 genunix: [ID 872817 kern.notice] fc02e898 unix:putnext+1c4 > (f672a96c, f6744ac0, f5b3ae24, 0, 0, f672a6ac) genunix: [ID 645206 > kern.notice] %l0-7: f5c6f9c8 f672a96c 00000000 fc02ead0 fc02ea0c ffffffff > 00000000 00000000 genunix: [ID 872817 kern.notice] fc02e8f8 > genunix:strput+210 (0, 2c4, f672a96c, fc02ead0, 0, 0) genunix: [ID 645206 > kern.notice] %l0-7: f6744ac0 00000000 00000000 00000000 00000000 00000000 > 00000000 00000000 genunix: [ID 872817 kern.notice] fc02ea10 > genunix:kstrputmsg+2d0 (f66afd40, 200, c0, 40, 80, f672a96c) genunix: [ID > 645206 kern.notice] %l0-7: 00000000 00000000 00000000 f66ac74c 000002c4 > 00000000 f66ac700 00000000 genunix: [ID 872817 kern.notice] fc02ea80 > sockfs:sosetsockopt+140 (ffff, f66afd88, 0, 0, 30, f66afd40) genunix: [ID > 645206 kern.notice] %l0-7: 00000068 f65240c0 00000000 00000000 00000000 > 00000000 00000000 00000000 genunix: [ID 872817 kern.notice] fc02eb18 > sockfs:setsockopt+b0 (f66afd40, 30, f65240c0, effff488, 68, 0) genunix: [ID > 645206 kern.notice] %l0-7: 00000003 00000030 ef6968bc f0064400 00000000 > f024ac00 f024fbb8 fc02eb80 unix: [ID 100000 kern.notice] > genunix: [ID 672855 kern.notice] syncing file systems... > unix: [ID 836849 kern.notice] > panic[cpu0]/thread=f6539000: > unix: [ID 849363 kern.notice] BAD TRAP: type=7 (Memory address alignment) > rp=f0257ac4 addr=0 mmu_fsr=0 rw=0 unix: [ID 100000 kern.notice] > genunix: [ID 353387 kern.notice] dumping to /dev/dsk/c0t3d0s4, offset > 26935296 genunix: [ID 904073 kern.notice] done > genunix: [ID 409368 kern.notice] 100% done: 3943 pages dumped, compression > ratio 2.28, genunix: [ID 851671 kern.notice] dump succeeded > > From owner-pim@catarina.usc.edu Tue Oct 10 02:23:39 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA29012 for ; Tue, 10 Oct 2000 02:23:38 -0400 (EDT) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id XAA92881 for pim-list; Mon, 9 Oct 2000 23:09:12 -0700 (PDT) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-pim@catarina.usc.edu using -f Received: from usc.edu (root@usc.edu [128.125.253.136]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id XAA92876 for ; Mon, 9 Oct 2000 23:09:10 -0700 (PDT) Received: from cindy.yamato.ibm.co.jp (cindy.yamato.ibm.co.jp [203.141.89.10]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id XAA27063 for ; Mon, 9 Oct 2000 23:09:10 -0700 (PDT) Received: from kyoto.yamato.ibm.com (kyoto3.yamato.ibm.com [9.68.3.1]) by cindy.yamato.ibm.co.jp (8.9.3/3.7W/GW3.3) with ESMTP id PAA11032; Tue, 10 Oct 2000 15:07:34 +0900 Received: from localhost (ymtlogin1.yamato.ibm.com [9.68.80.207]) by kyoto.yamato.ibm.com (8.8.8/MS2.00) with ESMTP id PAA42700; Tue, 10 Oct 2000 15:07:51 +0900 To: esj@cs.fiu.edu Cc: pim@catarina.usc.edu Subject: Re: pimd-2.1.0-alpha28 + solaris 8 = kernel panic In-Reply-To: Your message of "Mon, 09 Oct 2000 20:05:20 +0000" <200010092005.QAA22375@ferret.cs.fiu.edu> References: <200010092005.QAA22375@ferret.cs.fiu.edu> X-Mailer: Mew version 1.93 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20001010150751R.asaeda@yamato.ibm.com> Date: Tue, 10 Oct 2000 15:07:51 +0900 (JST) From: Hitoshi Asaeda X-Dispatcher: imput version 980905(IM100) Lines: 10 Sender: owner-pim@catarina.usc.edu Precedence: bulk Content-Transfer-Encoding: 7bit > pimd-2.1.0-alpha28 > Solaris 5.8 Generic_108528-02 sun4m sparc SUNW,SPARCstation-5 Unfortunately, pimd-2.1.0-alpha28 doesn't work on solaris8. I'll tell you the on going fix toward alpha29 or 2.2.0 if you can be an alpha tester.:) Regards. -- Hitoshi Asaeda From owner-pim@catarina.usc.edu Sun Oct 22 23:02:49 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA02129 for ; Sun, 22 Oct 2000 23:02:48 -0400 (EDT) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id TAA32540 for pim-list; Sun, 22 Oct 2000 19:46:22 -0700 (PDT) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-pim@catarina.usc.edu using -f Received: from usc.edu (root@usc.edu [128.125.253.136]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id TAA32535 for ; Sun, 22 Oct 2000 19:46:20 -0700 (PDT) Received: from hotmail.com (f316.law10.hotmail.com [64.4.14.191]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id TAA21463 for ; Sun, 22 Oct 2000 19:46:20 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 22 Oct 2000 19:44:41 -0700 Received: from 209.58.11.227 by lw10fd.law10.hotmail.msn.com with HTTP; Mon, 23 Oct 2000 02:44:41 GMT X-Originating-IP: [209.58.11.227] From: "vikram pim" To: pim@catarina.usc.edu Subject: Question about the DR going down Date: Mon, 23 Oct 2000 02:44:41 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 23 Oct 2000 02:44:41.0640 (UTC) FILETIME=[319DDA80:01C03C9B] Sender: owner-pim@catarina.usc.edu Precedence: bulk Hello everyone, I have a question on the last hop router (DR) which goes down and another candidate DR takes over. In this case if the DR is part of the SPT, will the newbie-DR join the SPT directly rather than do the RPT join first and then fall back to SPT ? Any pointers would be highly appreciated. Vikram _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. From owner-pim@catarina.usc.edu Wed Oct 25 23:55:26 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA04453 for ; Wed, 25 Oct 2000 23:55:25 -0400 (EDT) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id UAA03561 for pim-list; Wed, 25 Oct 2000 20:29:19 -0700 (PDT) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-pim@catarina.usc.edu using -f Received: from usc.edu (root@usc.edu [128.125.253.136]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id UAA03556 for ; Wed, 25 Oct 2000 20:29:18 -0700 (PDT) Received: from labsun2.iss.comsat.com (labsun2.iss.comsat.com [134.133.12.62]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id UAA10165 for ; Wed, 25 Oct 2000 20:29:15 -0700 (PDT) Received: from castor.ntd.comsat.com (castor.ntd.comsat.com [134.133.80.100]) by labsun2.iss.comsat.com (8.10.2/8.10.2) with ESMTP id e9Q3P3e28255 for ; Wed, 25 Oct 2000 23:25:03 -0400 (EDT) Received: from punn (punn.ntd.comsat.com [134.133.79.242]) by castor.ntd.comsat.com (8.10.2/8.10.2) with SMTP id e9Q3P2D19920 for ; Wed, 25 Oct 2000 23:25:02 -0400 (EDT) Message-ID: <038301c03efc$94fc5760$f24f8586@ntd.comsat.com> From: "karim Zamani" To: "pim-list" Subject: Holdtime in Hello Message Date: Wed, 25 Oct 2000 23:26:51 -0400 Organization: Comsat Corp. MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0380_01C03EDB.0DAC27C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-pim@catarina.usc.edu Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0380_01C03EDB.0DAC27C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I'm getting a bit confused about the Holdtime included in the Hello = messages.=20 In the actual PIM-SM RFC, it says that the Hello packet includes a = Holdtime set to [Hello-Holdtime]. The neighbor uses it to time out its = neighbor's state. However, in the new re-written spec I noticed that it says that the = router can use either the Holdtime sent by the neighbor or the local = [Hello-Holdtime] in case the Hello packet didn't have the Holdtime. What = if the local [Hello-Holdtime] is different from the neighbor's? Is it mandatory that Hello packets carry the Holdtime? Do PIM implementations ignore Hello packets with no Holdtime? Thanks. -- Karim. ------=_NextPart_000_0380_01C03EDB.0DAC27C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
I'm getting a bit confused about = the Holdtime=20 included in the Hello messages.
 
In the actual PIM-SM RFC, it says that = the Hello=20 packet includes a Holdtime set to [Hello-Holdtime]. The neighbor uses it = to time=20 out its neighbor's state.
 
However, in the new re-written spec I = noticed that=20 it says that the router can use either the Holdtime sent by the = neighbor or=20 the local [Hello-Holdtime] in case the Hello packet didn't have the = Holdtime.=20 What if the local [Hello-Holdtime] is different from the=20 neighbor's?
 
Is it mandatory that Hello packets = carry the=20 Holdtime?
 
Do PIM implementations ignore Hello = packets with no=20 Holdtime?
 
 
Thanks.
--
Karim.
------=_NextPart_000_0380_01C03EDB.0DAC27C0-- From owner-pim@catarina.usc.edu Mon Oct 30 08:18:59 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA19260 for ; Mon, 30 Oct 2000 08:18:59 -0500 (EST) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id EAA25346 for pim-list; Mon, 30 Oct 2000 04:47:42 -0800 (PST) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-pim@catarina.usc.edu using -f Received: from usc.edu (root@usc.edu [128.125.253.136]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id EAA25341 for ; Mon, 30 Oct 2000 04:47:41 -0800 (PST) Received: from exchange01.iirltd.co.uk (groupwise.iirltd.co.uk [193.133.64.177]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id EAA23078 for ; Mon, 30 Oct 2000 04:47:40 -0800 (PST) Received: by exchange01.iirltd.co.uk with Internet Mail Service (5.5.2650.21) id ; Mon, 30 Oct 2000 12:41:56 -0000 Message-ID: From: Rohan Marwaha To: Rohan Marwaha Subject: Important News! Date: Mon, 30 Oct 2000 12:41:52 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-pim@catarina.usc.edu Precedence: bulk I thought you might be interested to know that due to the vast success of the MPLS conference in September IIR will be repeating this event in January. Check out the website for further details: www.telecomstransmission.com/mpls/ If you wish to be kept informed about this event and other transmission events then please reply to me with 'add' in the subject box and I will add you to my personal distribution list. Kind regards, Rohan Marwaha Telecoms & Technology Marketing Fax: +44 (0) 20 7915 5001 email: rmarwaha@iir-conferences.com ******************************************** Seen our relaunched web site yet? Log on now at www.iir-telecoms.com