Re: [Pppext] [rbridge] working group last call for PPP TRILL protocol control protocol [was Re: I-D Action:draft-ietf-pppext-trill-protocol-02.txt]

Donald Eastlake <d3e3e3@gmail.com> Thu, 27 January 2011 14:30 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C9AE63A684E for <pppext@core3.amsl.com>; Thu, 27 Jan 2011 06:30:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.4
X-Spam-Level:
X-Spam-Status: No, score=-103.4 tagged_above=-999 required=5 tests=[AWL=0.199, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 bINscCZPyeoV for <pppext@core3.amsl.com>; Thu, 27 Jan 2011 06:30:56 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 708FB3A67EF for <pppext@ietf.org>; Thu, 27 Jan 2011 06:30:55 -0800 (PST)
Received: by wwa36 with SMTP id 36so2456967wwa.13 for <pppext@ietf.org>; Thu, 27 Jan 2011 06:33:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=Ut2LDRXrky8PsLrdx34e+Ba9JPhDrS18rp69C2yifiI=; b=mfIT9HjStQyvN2be6eWgDNvGby8I9XaVQVm2Bf+b+jWzYNrI9nHLcADAr9DXSF0UxN RbmxlVmvBy1m1oHcxHDsNHuxq3Yza49sTkFfdHpFkQge4zLWyzq9BwgP5sANQM5s3nPH QNvTBVVjdmoDAVQhvw0acaYYclNsT79S1IeQM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=vdEXwSDyAL2GZNpg9NU0ATLIrSVSsJ3egtSAv/qjqH85U4hIlkaoHvn4WHaPXI5b9P tc3XUG5Ew0sjCnq1kypZS+WauSiBjsJ6qj8VUL0LVChuMC0ptj1E0uLkQAXYc3/K8eU4 SRqjAvc8YfYpAUlvm8DIzIPAS6BsBKybZ+UV0=
Received: by 10.227.145.139 with SMTP id d11mr1160163wbv.8.1296138838512; Thu, 27 Jan 2011 06:33:58 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Thu, 27 Jan 2011 06:33:34 -0800 (PST)
In-Reply-To: <4D40945C.1070906@workingcode.com>
References: <20110106154501.15655.20204.idtracker@localhost> <4D334595.3030507@workingcode.com> <4D3DADF9.4040009@gmail.com> <4D3DB16B.5080803@workingcode.com> <4D3DC516.1000105@gmail.com> <4D3DCD97.7040005@gmail.com> <4D3DE413.80908@workingcode.com> <4D3E00B9.7050509@gmail.com> <4D3E247D.9090201@workingcode.com> <AANLkTi=+K-Kzsc+kahrmBoj1oC0WBzj7DYquS5ySCpP6@mail.gmail.com> <4D3F13B3.9070706@workingcode.com> <AANLkTikJjMcc1es7qyabddcXBFS93sRwcRO7XvPQzbe2@mail.gmail.com> <4D3F1EAD.5040901@workingcode.com> <4D4065F2.3080305@gmail.com> <AANLkTimi5vsYbGb0QXhyg_jdE2aCPKkUL9Y_Qj=g0Jpo@mail.gmail.com> <4D40945C.1070906@workingcode.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 27 Jan 2011 09:33:34 -0500
Message-ID: <AANLkTi=RTh8YWh4Ck8P97Qv7YugbtoVOncko=mhA5ahN@mail.gmail.com>
To: James Carlson <carlsonj@workingcode.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: pppext@ietf.org, rbridge@postel.org
Subject: Re: [Pppext] [rbridge] working group last call for PPP TRILL protocol control protocol [was Re: I-D Action:draft-ietf-pppext-trill-protocol-02.txt]
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jan 2011 14:30:56 -0000

Hi James,

On Wed, Jan 26, 2011 at 4:38 PM, James Carlson <carlsonj@workingcode.com> wrote:
> Donald Eastlake wrote:
>> I don't understand why you say that. Seem to me that TRILL over PPP
>> just involves the formats, code points, and PPP procedures. Anyway, it
>> isn't clear to me that anyone will build a practical RBridge that
>> doesn't have a MAC address Ethernet interface even if it is just a
>> virtual internal interface for a virtual internal end station. If that
>> doesn't exist, you can't really address the RBridge for management or
>> maintenance.
>
> Sure, you could.  It would just have to be addressed via IP (e.g., via
> SNMP, ssh, or even TELNET) rather than by something locked into Ethernet.

Really? RBridge don't route on IP addresses. They route based on
nickname and, on ingress, they convert to nickname from MAC/VLAN. How
are you going to get an RBridge to route on an IP address?

Thanks,
Donald

> One could imagine a large TRILL bridge designed for telecom applications
> exclusively on the interior of the cloud, where the only possible links
> are point-to-point; no Ethernet need apply.
>
> Whether anyone ever builds that beast -- and, if so, whether it lacks
> any built-in mechanism for automatic System ID assignment -- is a
> different question.
>
> What we're really discussing is whether failing to cover this case with
> some sort of automatic resolution is a hole in the specification (as I
> think Mr. Simpson is contending), or whether it's just an unlikely
> corner that implementors should be warned away from (as I believe).
>
> --
> James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>