From owner-freebsd-current@FreeBSD.ORG  Mon Apr 16 08:11:34 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 E317816A402
	for <freebsd-current@freebsd.org>; Mon, 16 Apr 2007 08:11:34 +0000 (UTC)
	(envelope-from thompsa@freebsd.org)
Received: from heff.fud.org.nz (203-109-251-39.static.bliink.ihug.co.nz
	[203.109.251.39])
	by mx1.freebsd.org (Postfix) with ESMTP id 622BE13C455
	for <freebsd-current@freebsd.org>; Mon, 16 Apr 2007 08:11:34 +0000 (UTC)
	(envelope-from thompsa@freebsd.org)
Received: by heff.fud.org.nz (Postfix, from userid 1001)
	id F37981CC58; Mon, 16 Apr 2007 20:11:32 +1200 (NZST)
Date: Mon, 16 Apr 2007 20:11:32 +1200
From: Andrew Thompson <thompsa@freebsd.org>
To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
Message-ID: <20070416081132.GB75226@heff.fud.org.nz>
Mail-Followup-To: Andrew Thompson <thompsa@freebsd.org>,
	"Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>,
	Lars Erik Gullerud <lerik@nolink.net>,
	Shteryana Shopova <syrinx@FreeBSD.org>, freebsd-current@freebsd.org
References: <peterjeremy@optushome.com.au>
	<20070411191450.GE815@turion.vk2pj.dyndns.org>
	<E1Hbs1M-000FWA-7Z@clue.co.za>
	<20070412210957.GA31864@heff.fud.org.nz>
	<461FB498.4030407@freebsd.org>
	<61b573980704150428u5e376d60k6fbe66409493c3bb@mail.gmail.com>
	<20070416085609.G442@electra.nolink.net>
	<20070416071812.V36917@maildrop.int.zabbadoz.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070416071812.V36917@maildrop.int.zabbadoz.net>
User-Agent: Mutt/1.5.13 (2006-08-11)
Cc: Shteryana Shopova <syrinx@FreeBSD.org>, freebsd-current@freebsd.org
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2007 08:11:35 -0000

On Mon, Apr 16, 2007 at 07:32:58AM +0000, Bjoern A. Zeeb wrote:
> On Mon, 16 Apr 2007, Lars Erik Gullerud wrote:
> >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).

I think this is a very good point.

> 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.

Well nothings committed yet. laggr is good, linkag rolls off the tounge
better :)


Andrew