RE: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] 68-IETF minutes)

Bernard Aboba <bernarda@windows.microsoft.com> Wed, 09 May 2007 17:24 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 1HlpuN-0002IF-AR; Wed, 09 May 2007 13:24:59 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43) id 1HlpuM-0002I9-6x for 16ng-confirm+ok@megatron.ietf.org; Wed, 09 May 2007 13:24:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlpuL-0002I1-Tc for 16ng@ietf.org; Wed, 09 May 2007 13:24:57 -0400
Received: from smtp.microsoft.com ([131.107.115.215]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HlpuJ-0001bw-Qz for 16ng@ietf.org; Wed, 09 May 2007 13:24:56 -0400
Received: from tk1-exhub-c103.redmond.corp.microsoft.com (157.56.116.114) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.0.685.24; Wed, 9 May 2007 10:24:55 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com (157.54.69.169) by tk1-exhub-c103.redmond.corp.microsoft.com (157.56.116.114) with Microsoft SMTP Server id 8.0.685.25; Wed, 9 May 2007 10:24:54 -0700
Received: from WIN-MSG-20.wingroup.windeploy.ntdev.microsoft.com ([157.54.62.26]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 9 May 2007 10:24:53 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] 68-IETF minutes)
Date: Wed, 9 May 2007 10:23:41 -0700
Message-ID: <0C7B902B470A264FA64D66CBF76FB8210358C672@WIN-MSG-20.wingroup.windeploy.ntdev.microsoft.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] 68-IETF minutes)
thread-index: AceSUz+crUz8BCbVTialRgAZ9un2xAAC4o1N
References: <D4AE20519DDD544A98B3AE9235C8A4C2A7B21A@moe.corp.azairenet.com><0C7B902B470A264FA64D66CBF76FB8210358C66A@WIN-MSG-20.wingroup.windeploy.ntdev.microsoft.com> <10e14db20705090900j598cd8awd363971f5de37485@mail.gmail.com>
From: Bernard Aboba <bernarda@windows.microsoft.com>
To: Syam Madanapalli <smadanapalli@gmail.com>
X-OriginalArrivalTime: 09 May 2007 17:24:53.0764 (UTC) FILETIME=[F4F53440:01C7925E]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 52f402fbded34a6df606921f56b8bdd8
Cc: Samita Chakrabarti <Samita.Chakrabarti@azairenet.com>, 16ng@ietf.org, Dave Thaler <dthaler@windows.microsoft.com>
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="===============2123036606=="
Errors-To: 16ng-bounces@ietf.org

Yes, producing ARP response within the device. 
 
If the device is made to look like Ethernet (as many WiMAX NICs are doing), then ARP requests will be received, so it is not possible to avoid receiving ARPs. 

________________________________

From: Syam Madanapalli [mailto:smadanapalli@gmail.com]
Sent: Wed 5/9/2007 9:00 AM
To: Bernard Aboba
Cc: Samita Chakrabarti; 16ng@ietf.org; Dave Thaler
Subject: Re: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] 68-IETF minutes)


Did you mean producing ARP response within the device?
Which I think is fine, but the best is not to send ARP at all.

Thanks,
Syam
 


On 5/9/07, Bernard Aboba <bernarda@windows.microsoft.com> wrote: 

	I think that the issue is resolved by enabling a unicast ARP response to be synthesized in response to a unicast ARP request (e.g. NUD).  Of course, it is also necessary to respond to broadcast ARPs as well. 
	
	
	
	-----Original Message-----
	From: Samita Chakrabarti [ mailto:Samita.Chakrabarti@AzaireNet.com <mailto:Samita.Chakrabarti@AzaireNet.com> ]
	Sent: Tue 5/8/2007 6:59 PM
	To: Syam Madanapalli; 16ng@ietf.org
	Cc: Bernard Aboba; Dave Thaler
	Subject: RE: [16NG] ARP over IEEE 802.16 IPvCS (was 16NG] 68-IETF minutes)
	
	Hi ,
	
	
	
	I also am not clear on the issues with ARP comments in IPv4CS  document
	as Syam mentioned below. 
	
	
	
	Can someone please clarify ? Please see in-line.
	
	
	
	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
	
	[SC>]
	
	Is the concern with DNAv4 running on a mobile node ? I assume the node
	tries to do autoconf with IPv4 link-local address  by sending a unicast
	packet to the default router and for that it needs to ARP for the MAC 
	address of the router?
	
	Is the concern on dropping ARP on the receiver side or not being able to
	send an ARP at all or both?
	
	
	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
	
	[SC>]
	
	Can DNA of a mobile get a hint from the link layer that it is now in
	Wimax (802.16e ) link and then it should try to get its address assigned
	according to the Wimax network (DHCP)? (Assuming the node has moved from
	Wifi to Wimax network, for example).  The DHCP address is assigned
	usually by the ASN network.  So if the concern is in initial IP-address 
	allocation, that might be handled by Wimax network.  But, if there is no
	address resolution, then how does a node send a packet to its logical
	neighboring node ? It looks like the ASN-GW or default-router in the 
	network or some central body needs to do the mapping between an
	IP-address to CID of  the destination node.  Thus ARP request could be
	directly sent to the default GW which will act as a proxy and send back
	a reply with a CID of the corresponding IP-address(assuming the default 
	gw has a cache of all nodes attached to it).  The model is similar to
	what is described in:
	
	http://www.ietf.org/internet-drafts/draft-chakrabarti-6lowpan-ipv6-nd-03
	.txt
	
	
	
	Comments?
	
	
	
	Thanks,
	
	-Samita
	....
	
	
	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 <mailto: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