IETF Logo Mail Archive

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

Burcak Beser <Burcak.Beser@telsima.com> Fri, 07 September 2007 23:17 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 1ITn4Q-0000Ca-3G; Fri, 07 Sep 2007 19:17:02 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43) id 1ITn4O-0000CU-UE for 16ng-confirm+ok@megatron.ietf.org; Fri, 07 Sep 2007 19:17:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ITn4O-0000CM-KX for 16ng@ietf.org; Fri, 07 Sep 2007 19:17:00 -0400
Received: from 207.47.36.226.static.nextweb.net ([207.47.36.226] helo=USEXCH1.us.telsima.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ITn4N-0007QW-E1 for 16ng@ietf.org; Fri, 07 Sep 2007 19:17:00 -0400
Received: from USEXCH1.us.telsima.com ([192.168.200.40]) by USEXCH1.us.telsima.com ([192.168.200.40]) with mapi; Fri, 7 Sep 2007 16:16:58 -0700
From: Burcak Beser <Burcak.Beser@telsima.com>
To: "Riegel, Maximilian" <maximilian.riegel@nsn.com>, "16ng@ietf.org" <16ng@ietf.org>
Date: Fri, 7 Sep 2007 16:16:52 -0700
Thread-Topic: [aged entries] draft-ietf-16ng-ip-over-ethernet-over-802.16-02
Thread-Index: Acff0ahIca1oWq5DTmKkOruXdo/evwPlGbqAAFEHRKAAF0qW0AAjJ7iQAAPzurA=
Message-ID: <C82F1C69BB1FD44D9E8C6ECB0DDD571E022A2040AF@USEXCH1.us.telsima.com>
References: <0JMU0043LTOFT3@mmp2.samsung.com> <0JNV004TFJKQF3@mmp2.samsung.com><C82F1C69BB1FD44D9E8C6ECB0DDD571E022A203F3B@USEXCH1.us.telsima.com> <C82F1C69BB1FD44D9E8C6ECB0DDD571E022A203FE0@USEXCH1.us.telsima.com> <7F5DE213D76BA54CBF56258675D8D3E12CE7F9@MCHP7I7A.ww002.siemens.net>
In-Reply-To: <7F5DE213D76BA54CBF56258675D8D3E12CE7F9@MCHP7I7A.ww002.siemens.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc:
Subject: [16NG] [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

[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