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

William Allen Simpson <william.allen.simpson@gmail.com> Mon, 24 January 2011 17:49 UTC

Return-Path: <william.allen.simpson@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 0664728C0EE for <pppext@core3.amsl.com>; Mon, 24 Jan 2011 09:49:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 nPAR8cncN4Z5 for <pppext@core3.amsl.com>; Mon, 24 Jan 2011 09:49:48 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id 212BC28C0E7 for <pppext@ietf.org>; Mon, 24 Jan 2011 09:49:48 -0800 (PST)
Received: by gxk27 with SMTP id 27so1611987gxk.31 for <pppext@ietf.org>; Mon, 24 Jan 2011 09:52:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=56GCUV6unX7OLegdTvw/Mshif8905rrbWrlnrD/+5oM=; b=o7Wm5KIwidiPjERr9AtZCSBd7Pcg4fe4XY1EOIMB3B6kwH5qfqq6g72iC2MzQajnGe suTqvXHb9IXIf2ty/wuEmf/d7WAX00pvT0dbeICOo84uYJ3Xv2mA1rB5lXXZKQ3f7g2J MccKj0TAINindN9RdOcaF1P0igQ1zSi6TpjQA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=r7YAqyTMJPucPqmtNObsXKHmIcnVld3nsmEPV6BmFrPaBv1RwjQIaHvyhJ7R2WTiip 6EJgleOq2yjmpKGVIZihVGLW28KN3ObB804K7BXYwCK36XMPQmcrvXTYj1VVihNtRLpY p/lMnqhI66P8cElVyhDQGV119wrwiVeGttsVU=
Received: by 10.42.166.200 with SMTP id p8mr5215887icy.87.1295891562881; Mon, 24 Jan 2011 09:52:42 -0800 (PST)
Received: from Wastrel.local (c-68-40-194-239.hsd1.mi.comcast.net [68.40.194.239]) by mx.google.com with ESMTPS id g4sm9170627ick.23.2011.01.24.09.52.38 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 24 Jan 2011 09:52:39 -0800 (PST)
Message-ID: <4D3DBC64.3070308@gmail.com>
Date: Mon, 24 Jan 2011 12:52:36 -0500
From: William Allen Simpson <william.allen.simpson@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: pppext@ietf.org
References: <20110106154501.15655.20204.idtracker@localhost> <4D334595.3030507@workingcode.com> <4D3DADF9.4040009@gmail.com>
In-Reply-To: <4D3DADF9.4040009@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: rbridge@postel.org
Subject: Re: [Pppext] 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: Mon, 24 Jan 2011 17:49:50 -0000

On 1/24/11 11:51 AM, William Allen Simpson wrote:
> IIRC, IETF now has an OUI. Back in the day, we'd use something in the
> CF0000 series (see [RFC-2153]). Either should work OK.
>
> PPP has a Magic Number, guaranteed to be unique between PPP interfaces on
> the same device. You should combine it with the OUI. Simply require it
> during LCP negotiation, as so many other PPP RFCs do already.

Upon further reflection, the IETF OUI won't work, because that would
require either truncating the Magic Number (rendering it less likely to be
unique), or using a EUI-64 form to make enough room for the full 32 bits.

But I don't see any ability in the TRILL draft to use the EUI-64 format.

So, you'd have to use the CF0000 series.  AFAICT, the TRILL protocol never
uses that System ID as the next hop destination (please correct me).  It
uses its own multicast value, so there should be no conflict.

I'd recommend registering the CFFFxx series to add a Magic Number.

The CF0000 series was not originally intended to be used outside of PPP
Vendor Extensions, and thus never appears over an actual Ethernet link....
This would be a first.