Re: [pim] I-D ACTION:draft-ietf-pim-group-rp-mapping-01.txt

Leonard Giuliano <lenny@juniper.net> Wed, 01 July 2009 19:54 UTC

Return-Path: <lenny@juniper.net>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E25C23A6821 for <pim@core3.amsl.com>; Wed, 1 Jul 2009 12:54:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CRsLl4Jppr4p for <pim@core3.amsl.com>; Wed, 1 Jul 2009 12:54:26 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by core3.amsl.com (Postfix) with ESMTP id 0E8723A69F7 for <pim@ietf.org>; Wed, 1 Jul 2009 12:54:22 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKSku+6sz9ODVYp0wHG/j+f/3zHZ+w7qB6@postini.com; Wed, 01 Jul 2009 12:54:45 PDT
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.375.2; Wed, 1 Jul 2009 12:47:10 -0700
Received: from p-emlb02-sac.jnpr.net ([66.129.254.47]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 1 Jul 2009 12:47:11 -0700
Received: from emailsmtp56.jnpr.net ([172.24.60.77]) by p-emlb02-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 1 Jul 2009 12:47:10 -0700
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 1 Jul 2009 12:47:09 -0700
Received: from zircon.juniper.net (zircon.juniper.net [172.17.28.113]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id n61Jl9L79834; Wed, 1 Jul 2009 12:47:09 -0700 (PDT) (envelope-from lenny@juniper.net)
Received: from zircon.juniper.net (localhost [127.0.0.1]) by zircon.juniper.net (8.12.11/8.12.3) with ESMTP id n61Jl9Xq035794; Wed, 1 Jul 2009 12:47:09 -0700 (PDT) (envelope-from lenny@juniper.net)
Received: from localhost (lenny@localhost) by zircon.juniper.net (8.12.11/8.12.3/Submit) with ESMTP id n61Jl9o0035791; Wed, 1 Jul 2009 12:47:09 -0700 (PDT)
X-Authentication-Warning: zircon.juniper.net: lenny owned process doing -bs
Date: Wed, 01 Jul 2009 12:47:09 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: "Andy Kessler (kessler)" <kessler@cisco.com>
In-Reply-To: <65B900A32A86DB4EBF57C0D07F9B2A9E016581EB@xmb-sjc-215.amer.cisco.com>
Message-ID: <20090701124258.Q34799@zircon.juniper.net>
References: <20090625174502.0FEDC3A6DE0@core3.amsl.com> <F35F8210-74BB-40B6-9389-054B2254A7A9@cisco.com> <65B900A32A86DB4EBF57C0D07F9B2A9E016581EB@xmb-sjc-215.amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-OriginalArrivalTime: 01 Jul 2009 19:47:09.0812 (UTC) FILETIME=[B8B2C340:01C9FA84]
Cc: pim@ietf.org
Subject: Re: [pim] I-D ACTION:draft-ietf-pim-group-rp-mapping-01.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jul 2009 19:54:27 -0000

On Mon, 29 Jun 2009, Andy Kessler (kessler) wrote:

-) John> Since the hash is the very last thing, I'd prefer that it not be
-) removed since its already
-) 
-) there.  Rather change it to a "MAY" requirement.  I'd hate to see it
-) removed only to 
-) 
-) find it has to be added back in again.
-) 
-)  
-) 
-) Andy>- The hash can't be a 'MAY' because different implementations need
-) to be compatible. 
-) 
-)  We asked in several forums if anyone was using the hash and didn't find
-) anyone that wanted
-) 
-)  to continue using it. We also received support for removing the hash
-) when this was discussed
-) 
-)  on this list previously. It will not come back if this draft is
-) accepted. 
-) 

Why again should the hash be deprecated?  Of all of the objectional 
things about BSR, the hash seems pretty low on the list.  Is it worth 
breaking backward-compatibility just to remove this fairly innocuous 
mechanism?

-Lenny