IETF Logo Mail Archive

[16NG] RE: [aged entries] draft-ietf-16ng-ip-over-ethernet-over-802.16-02

"Riegel, Maximilian" <maximilian.riegel@nsn.com> Mon, 10 September 2007 15:42 UTC

Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IUlOm-0006MX-Kw; Mon, 10 Sep 2007 11:42:04 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43) id 1IUlOk-0006MH-Dd for 16ng-confirm+ok@megatron.ietf.org; Mon, 10 Sep 2007 11:42:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IUlOg-0006KB-5c for 16ng@ietf.org; Mon, 10 Sep 2007 11:41:58 -0400
Received: from gecko.sbs.de ([194.138.37.40]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IUlOe-0001Fn-IC for 16ng@ietf.org; Mon, 10 Sep 2007 11:41:58 -0400
Received: from mail2.sbs.de (localhost [127.0.0.1]) by gecko.sbs.de (8.12.6/8.12.6) with ESMTP id l8AFft2E025899; Mon, 10 Sep 2007 17:41:55 +0200
Received: from fthw9xoa.ww002.siemens.net (fthw9xoa.ww002.siemens.net [157.163.133.201]) by mail2.sbs.de (8.12.6/8.12.6) with ESMTP id l8AFfoua002789; Mon, 10 Sep 2007 17:41:54 +0200
Received: from MCHP7I7A.ww002.siemens.net ([139.25.131.138]) by fthw9xoa.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.1830); Mon, 10 Sep 2007 17:41:40 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 10 Sep 2007 17:45:42 +0200
Message-ID: <7F5DE213D76BA54CBF56258675D8D3E12FB9BD@MCHP7I7A.ww002.siemens.net>
In-Reply-To: <C82F1C69BB1FD44D9E8C6ECB0DDD571E022A2040AF@USEXCH1.us.telsima.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [aged entries] draft-ietf-16ng-ip-over-ethernet-over-802.16-02
Thread-Index: Acff0ahIca1oWq5DTmKkOruXdo/evwPlGbqAAFEHRKAAF0qW0AAjJ7iQAAPzurAAhskHAA==
References: <0JMU0043LTOFT3@mmp2.samsung.com><0JNV004TFJKQF3@mmp2.samsung.com><C82F1C69BB1FD44D9E8C6ECB0DDD571E022A203F3B@USEXCH1.us.telsima.com><C82F1C69BB1FD44D9E8C6ECB0DDD571E022A203FE0@USEXCH1.us.telsima.com> <7F5DE213D76BA54CBF56258675D8D3E12CE7F9@MCHP7I7A.ww002.siemens.net> <C82F1C69BB1FD44D9E8C6ECB0DDD571E022A2040AF@USEXCH1.us.telsima.com>
From: "Riegel, Maximilian" <maximilian.riegel@nsn.com>
To: "Burcak Beser" <Burcak.Beser@telsima.com>, <16ng@ietf.org>
X-OriginalArrivalTime: 10 Sep 2007 15:41:40.0788 (UTC) FILETIME=[14E10F40:01C7F3C1]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc:
Subject: [16NG] RE: [aged entries] draft-ietf-16ng-ip-over-ethernet-over-802.16-02
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org

The comment is valid. There may be hosts attached to bridges behind the
MS/SSs which are not visible to the bridge in the network when the MS/SS
connects, and further more, the hosts behind the MS/SSs may move to
another MS/SSs without giving notice to the bridge in the network.

This usually cant be handled by static configuration of the bridge table
entries but requires dynamic entries which are learned from the packets
going through the particular ports.
Some enhancements are possible, when the port behavior of the bridge
behind the BS can be switched from static to dynamic on the fly, or when
the hosts on the bridge behind the SS/MSs are authenticated by
IEEE802.1X.

Text will be added in the next revision to address this case more
thoroughly.

Bye
Max

-----Original Message-----
From: Burcak Beser [mailto:Burcak.Beser@telsima.com] 
Sent: Saturday, September 08, 2007 1:17 AM
To: Riegel, Maximilian; 16ng@ietf.org
Subject: [aged entries] draft-ietf-16ng-ip-over-ethernet-over-802.16-02

[Sorry for dividing the discussion into pieces but othervise valuable
information will be lost]

> From: Riegel, Maximilian [mailto:maximilian.riegel@nsn.com]
>
> As defined in 802.1D the bridge may have static as well as dynamic
entries.
> Static entries are made by  configuration, e.g. when a new port is
established
> as result of a network entry and a successful authentication of a new
MS.
> Static entries do not age, while dynamic entries will be learned by
inspecting
> the packets going through the port.

How does BS know all the host entries upon creation of the air-link?

Please keep in mind that the hosts does not need to be connected when
the SS is connected to the bridge. At the same time it is possible and
highly probable for enterprise scenarios that the host may disconnect
from one SS and connect another SS attached to the same BS.

> What is missing in the description in the I-D?

The description you provided above :)

Kind Regards,
-burcak


_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng

v2.8.7 | Report a Bug | By Email