Re: Advancing the Protocol and Morin Drafts

IJsbrand Wijnands <ice@cisco.com> Wed, 22 October 2008 15:02 UTC

Return-Path: <l3vpn-bounces@ietf.org>
X-Original-To: l3vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l3vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8184828C134; Wed, 22 Oct 2008 08:02:29 -0700 (PDT)
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA39C3A68D8 for <l3vpn@core3.amsl.com>; Wed, 22 Oct 2008 08:02:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 gv8MMOcs5OmV for <l3vpn@core3.amsl.com>; Wed, 22 Oct 2008 08:02:27 -0700 (PDT)
Received: from av-tac-bru.cisco.com (odd-brew.cisco.com [144.254.15.119]) by core3.amsl.com (Postfix) with ESMTP id C0E173A689A for <l3vpn@ietf.org>; Wed, 22 Oct 2008 08:02:26 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1]) by av-tac-bru.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id m9MF35t01241; Wed, 22 Oct 2008 17:03:05 +0200 (CEST)
Received: from [10.55.191.152] (ams-iwijnand-8717.cisco.com [10.55.191.152]) by strange-brew.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id m9MF34G01215; Wed, 22 Oct 2008 17:03:04 +0200 (CEST)
In-Reply-To: <1224687111.20832.82.camel@l-at11168.FTRD>
References: <0E3033029745FB4C8BE6F1A3752FAE59E791DF@misout7msgusr7b.ugd.att.com> <1224680522.20832.74.camel@l-at11168.FTRD> <2B7BA8FF-2819-451D-B018-5EB9DFFE764B@cisco.com> <1224687111.20832.82.camel@l-at11168.FTRD>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <A83F0692-7169-4BBE-B57D-9AA23AA88B52@cisco.com>
Content-Transfer-Encoding: 7bit
From: IJsbrand Wijnands <ice@cisco.com>
Subject: Re: Advancing the Protocol and Morin Drafts
Date: Wed, 22 Oct 2008 17:03:04 +0200
To: Thomas Morin <thomas.morin@orange-ftgroup.com>
X-Mailer: Apple Mail (2.753.1)
Cc: Ross Callon <rcallon@juniper.net>, L3VPN <l3vpn@ietf.org>
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hi Thomas,

>
> For many operators its not "the vendor" but multiple vendors, and  
> that's
> why many operators (and apparently other IETF contributors too) see an
> interest in standardizing one solution, with options where needed, and
> not multiple profiles.

In your last email you say "..Misunderstanding: the draft says "MUST"  
for both PIM-based and BGP-based C-multicast routing."

How is that going to help you standardizing one solution? I also  
pointed out earlier that the Morin draft does not say which core tree  
building protocol needs to be used. This also does not help in  
getting an interoperable solution.

Thx,

Ice.