[16NG] ARP over IEEE 802.16 IPvCS (was 16NG] 68-IETF minutes)
"Syam Madanapalli" <smadanapalli@gmail.com> Fri, 04 May 2007 05:37 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 1HjqTm-0002hS-OY; Fri, 04 May 2007 01:37:18 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
id 1HjqTm-0002hJ-9G
for 16ng-confirm+ok@megatron.ietf.org; Fri, 04 May 2007 01:37:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1HjqTk-0002hB-Ig
for 16ng@ietf.org; Fri, 04 May 2007 01:37:16 -0400
Received: from wr-out-0506.google.com ([64.233.184.224])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HjqTk-0006I1-6V
for 16ng@ietf.org; Fri, 04 May 2007 01:37:16 -0400
Received: by wr-out-0506.google.com with SMTP id 71so785335wri
for <16ng@ietf.org>; Thu, 03 May 2007 22:37:16 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;
b=KQqOR0TS+iQBytOwv2P8QG/EkTpKkH8sZm16DUGTnNG+metGzY8Lzur+zfp81lcEdJg/qzqQfIXJAh7rXZdjv8gUGmqJKIOKucl1wkI5q6YlnvaFP+nHT2BXGOs2M+HjcUXK3hBCqKL/78kL5s9hLx1ZZ+y9wEHhGLWeR1KJrhY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
h=received:message-id:date:from:to:subject:mime-version:content-type;
b=eK+mDJS5Nqck/5oju3n0TeHgtUhIBTHXs1BLep3TBpAK5TllCtps+Lcz657zwxbFm5CMHn1HEHmQYLM3YnFqRX0NTLg9BCfRKAgOLvM1Iu5Vy/+Sm3iQh8p4zmpegfAY5mPTvR5ZNqEEFAyUd4Ek8VMT2jTSEx55CXrkHS956os=
Received: by 10.115.46.9 with SMTP id y9mr986371waj.1178257035429;
Thu, 03 May 2007 22:37:15 -0700 (PDT)
Received: by 10.115.109.20 with HTTP; Thu, 3 May 2007 22:37:15 -0700 (PDT)
Message-ID: <10e14db20705032237n5295930sd4a308168b4a8d32@mail.gmail.com>
Date: Fri, 4 May 2007 11:07:15 +0530
From: "Syam Madanapalli" <smadanapalli@gmail.com>
To: 16ng@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Subject: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] 68-IETF minutes)
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="===============0844381445=="
Errors-To: 16ng-bounces@ietf.org
>From 16ng minutes: .... Bernard Aboba: if Ethernet exposes an Ethernet interface then DNA triggered. then DHCP, so ARP is sent, then you figure out what to do Bernard Aboba: problem dropping ARPs - you wont get an address if you do that, because in DNA you don't dhcp. no connectivity if dropping the arp. In any operating system you'll have no address Dave Thaler: respond to any MAC address, sounds as if what you're proposing, manufcature ARP response... ARP goes on wire Bernard Aboba: not get DHCP but get (MAC) address .... These minutes are recorded for the presentation of the ID draft-madanapalli-16ng-over-802-dot-16-ipcs-00 I did not understand these comments, especially Ethernet in the IPv4CS context, Sorry I was not present at the meeting. The proposal is: As IP is run directly over 802.16 in case of IPv4 and destination MAC address is not required for sending the frames, there is no need for ARP. Also, ARP frame does not has a IP header, so IPv4CS cannot map these onto any CID. Or did I miss something? Thank you, Syam ---------- Forwarded message ---------- From: Daniel Park <soohongp@gmail.com> Date: Apr 17, 2007 12:22 AM Subject: [16NG] 68-IETF minutes To: "16ng@ietf.org" <16ng@ietf.org> Can be found at: http://www3.ietf.org/proceedings/07mar/minutes/16ng.txt Let me know if you see any bugs in there. -- Daniel Park _______________________________________________ 16NG mailing list 16NG@ietf.org https://www1.ietf.org/mailman/listinfo/16ng
_______________________________________________ 16NG mailing list 16NG@ietf.org https://www1.ietf.org/mailman/listinfo/16ng
- [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] 68-I… Syam Madanapalli
- RE: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] … Samita Chakrabarti
- RE: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] … Bernard Aboba
- Re: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] … Daniel Park
- Re: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] … Syam Madanapalli
- RE: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] … Bernard Aboba
- Re: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] … Qiang Zhang
- RE: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] … John.zhao
- RE: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] … Bernard Aboba
- Re: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] … Qiang Zhang
- RE: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] … Samita Chakrabarti
- RE: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] … John.zhao
- RE: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] … Samita Chakrabarti
- Re: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] … Syam Madanapalli
- RE: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] … Premec, Domagoj
- Re: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] … Syam Madanapalli