[pim] Please review our new draft and give us feedback. Thanks.

"janardhan kulkarni" <janardhan.kulkarni@gmail.com> Mon, 09 July 2007 05:01 UTC

Return-path: <pim-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7lNO-0000E5-9O; Mon, 09 Jul 2007 01:01:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7lNN-0000Dy-0c for pim@ietf.org; Mon, 09 Jul 2007 01:01:33 -0400
Received: from wa-out-1112.google.com ([209.85.146.182]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7lNI-0003EQ-Lp for pim@ietf.org; Mon, 09 Jul 2007 01:01:32 -0400
Received: by wa-out-1112.google.com with SMTP id k17so1366648waf for <pim@ietf.org>; Sun, 08 Jul 2007 22:01:28 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=GPvuo1rWxSCcVfnKzh9yDck4F+xj49lArjOUFuY+rScJiaHMWTmuG30H3RTFNlI80S5Ea/4xVfSDiWrRhF4VKasagixX9b4dgU/mAml0cRlRLHLmt7RftgNsQW54SRGCVLV0PKPlkdimrXGNPv31/8j4tlR9JnXdq0+K3qa1NrI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=QhUq4W6ewWicUfM0yP8vM1eCRtf/QYPoyYlFlY72im/kfdB8PpMfSOrHe1n8A+naJOWLRKt3imglYV+1yMddYGYxaAZhCh0o5ba1P3BOt6bQEsKpPBZobqeehBAa6HAtUp7ZpwiXXekvo1V6AUAw1yb8A1nu8I4RSJ9KLcXZdIQ=
Received: by 10.114.106.1 with SMTP id e1mr2768162wac.1183957287947; Sun, 08 Jul 2007 22:01:27 -0700 (PDT)
Received: by 10.114.108.5 with HTTP; Sun, 8 Jul 2007 22:01:27 -0700 (PDT)
Message-ID: <100ba11b0707082201w69d002ddo68334716a4efa432@mail.gmail.com>
Date: Mon, 09 Jul 2007 10:31:27 +0530
From: janardhan kulkarni <janardhan.kulkarni@gmail.com>
To: pim@ietf.org, Stig Venaas <stig.venaas@uninett.no>, Benoît HILT <benoit.hilt@uha.fr>, Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: Archana Patel <archana.jpatel@gmail.com>
Subject: [pim] Please review our new draft and give us feedback. Thanks.
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
Errors-To: pim-bounces@ietf.org

Hi,

In our new draft we are proposing some extensions to PIM so that,
troubleshooting becomes easy. Below is link and extract from our work.
Kindly review this and give us feedback about the utility of this.

http://www.ietf.org/internet-drafts/draft-archana-pimwg-pim-ping-00.txt

Brief Introduction:-
********************
Multicast technology has been around for quite some time now. But
widespread deployment of multicasting has just begun. All these days,
multicasting technology was revolving around developing efficient,
scalable routing protocols. Now that, multicast routing protocols are
matured, PIMSSM and PIMSM have established themselves as principal
multicast routing protocols, since many applications are using
multicasting as their base technology, it is the time to address
other aspects like debugging, trouble shooting and error reporting.
Most of the work that has been done so far in these areas, either
depend on multicast tree being set up or support from IP, and MIBS.
But it is our opinion that, multicast routing protocols should in
themselves embed necessary mechanisms to address these issues, even if
it means protocol implementations needs to be tweaked. Also, we
should note that, most of multicast routing protocols which use PULL
model like PIMSM, PIMSSM will create a multicast tree only if there
are some receivers join the tree. So, to get information about the
reachability or to trace the path of multicast data, even before
creating the tree it is necessary to extend the protocols. In this
draft we want to present some extensions to PIM, which help in trouble
shooting PIM related issues.
-- 
Bye,
Janardhan.
"I have never been hurt by what I have not said."
  -Calvin Coolidge

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim