From owner-freebsd-current@FreeBSD.ORG Mon Apr 16 07:35:11 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7138C16A401 for ; Mon, 16 Apr 2007 07:35:11 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id 20F9113C48A for ; Mon, 16 Apr 2007 07:35:11 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 3DF171FFEB3; Mon, 16 Apr 2007 09:35:09 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 33B9E1FFE9A; Mon, 16 Apr 2007 09:35:05 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 3A9D0444885; Mon, 16 Apr 2007 07:32:59 +0000 (UTC) Date: Mon, 16 Apr 2007 07:32:58 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Lars Erik Gullerud In-Reply-To: <20070416085609.G442@electra.nolink.net> Message-ID: <20070416071812.V36917@maildrop.int.zabbadoz.net> References: <20070411191450.GE815@turion.vk2pj.dyndns.org> <20070412210957.GA31864@heff.fud.org.nz> <461FB498.4030407@freebsd.org> <61b573980704150428u5e376d60k6fbe66409493c3bb@mail.gmail.com> <20070416085609.G442@electra.nolink.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: Shteryana Shopova , freebsd-current@freebsd.org, Andrew Thompson Subject: Re: CFT: new trunk(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Apr 2007 07:35:11 -0000 On Mon, 16 Apr 2007, Lars Erik Gullerud wrote: Hi, > On Sun, 15 Apr 2007, Shteryana Shopova wrote: > >> LACP == Link Aggregation Control Protocol - dynamic trunking - one of >> the modes trunk(4) supports. And it's Cisco vs the rest of the world >> where Cisco calls a trunk multiple VLANs over single physical >> interface and the rest of the world calls a trunk multiple physical >> interafces bundled together. We don't have to necessarily agree with >> Cisco. Please keep the current name. You have been assimilated;-) > I beg to differ. The terms "trunk" and "trunk-style link" are used throughout > IEEE 802.1Q-2005 in examples and illustrations to demonstrate the concept of > carrying multiple tagged vlans over a single link, as opposed to an > "access-style link" carrying a single untagged vlan. ... That, and in addition, I think, 802.3 (section 3) does not talk about 'trunk' at all. > I'd tend to prefer bond(4) so Linux users will feel familiar, although > aggr(4) would be equally good. I have seen the p4 submits and while I am not worrying about another OpenBSD vs. Linux (vs. FreeBSD) bikeshed, what really worries me is substituting one non-standard name for another. It is called "Link Aggregation" in the IEEE standards, so why would we want to call it 'bond'? The term "bonding" is not used in 802.3 (section 3) either (when related to link aggregation). So if we are about to rename trunk(4) we should do the right thing and use something short for "link aggregation" like aggr, laggr (my prefered version), linkag, linkaggr or similar. Just my 0.002ct. /bz -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT