[16NG] RE: review of draft-ietf-16ng-ip-over-ethernet-over-802.16-00
"Riegel, Maximilian" <maximilian.riegel@siemens.com> Tue, 30 January 2007 18:56 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1HBy9I-0008LY-5G; Tue, 30 Jan 2007 13:56:08 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1HBy9G-0008LD-Kq
for 16ng@ietf.org; Tue, 30 Jan 2007 13:56:06 -0500
Received: from lizzard.sbs.de ([194.138.37.39])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBy8s-0001us-DX
for 16ng@ietf.org; Tue, 30 Jan 2007 13:56:06 -0500
Received: from mail1.sbs.de (localhost [127.0.0.1])
by lizzard.sbs.de (8.12.6/8.12.6) with ESMTP id l0UItYh6008059;
Tue, 30 Jan 2007 19:55:34 +0100
Received: from fthw9xpa.ww002.siemens.net (fthw9xpa.ww002.siemens.net
[157.163.133.222])
by mail1.sbs.de (8.12.6/8.12.6) with ESMTP id l0UItY20002415;
Tue, 30 Jan 2007 19:55:34 +0100
Received: from MCHP7I6A.ww002.siemens.net ([139.25.131.137]) by
fthw9xpa.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.1830);
Tue, 30 Jan 2007 19:55:33 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 30 Jan 2007 19:55:33 +0100
Message-ID: <4BB931F00625F54DA8B8563E5A5CA25A01347208@MCHP7I6A.ww002.siemens.net>
In-Reply-To: <004a01c74443$6cd207f0$6520790a@china.huawei.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: review of draft-ietf-16ng-ip-over-ethernet-over-802.16-00
Thread-Index: AcdEQ2xWVR4qvH0PQ2WzdkPSro1SKQAW1m7Q
From: "Riegel, Maximilian" <maximilian.riegel@siemens.com>
To: <john.zhao@huawei.com>
X-OriginalArrivalTime: 30 Jan 2007 18:55:33.0875 (UTC)
FILETIME=[389F0430:01C744A0]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 089da5e32269fece1072c9ff54523f20
Cc: 16ng@ietf.org
Subject: [16NG] RE: review of draft-ietf-16ng-ip-over-ethernet-over-802.16-00
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>
Content-Type: multipart/mixed; boundary="===============2099657250=="
Errors-To: 16ng-bounces@ietf.org
Hi John.zhao, ProxyARP must know about the IP addresses being used by the SS/MSs. The information can be retrieved by intercepting the DHCP message exchange or just looking at the source IP addresses of upstream packets. With this information Proxy ARP can respond to ARP messages instead of broadcasting the message to all the SS/MSs. Bye Max ________________________________ From: John.zhao [mailto:john.zhao@huawei.com] Sent: Tuesday, January 30, 2007 8:51 AM To: Riegel, Maximilian Cc: 16ng@ietf.org Subject: review of draft-ietf-16ng-ip-over-ethernet-over-802.16-00 Hi Max, In section 7.3, there is a sentence that 'The unicast IPv4 addresses can be learned by examining the source address of packets or DHCP Response message.' But why this operation is needed? And if we will need the layer-3 operation in this place? Best Rgds, Thanks, John.zhao
_______________________________________________ 16NG mailing list 16NG@ietf.org https://www1.ietf.org/mailman/listinfo/16ng
- [16NG] review of draft-ietf-16ng-ip-over-ethernet… John.zhao
- [16NG] RE: review of draft-ietf-16ng-ip-over-ethe… Riegel, Maximilian
- [16NG] RE: review of draft-ietf-16ng-ip-over-ethe… John.zhao