RE: [16NG] Fw:I-DACTION:draft-madanapalli-16ng-ipv4-over-802-dot-16-ipcs-00.txt

"Narvaez, Paolo \(Paolo\)" <paolo@alcatel-lucent.com> Mon, 12 February 2007 20:06 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HGhRe-0006bR-2m; Mon, 12 Feb 2007 15:06:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HGhRd-0006bC-J6 for 16ng@ietf.org; Mon, 12 Feb 2007 15:06:37 -0500
Received: from ihemail1.lucent.com ([135.245.0.33]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGhRb-0008P2-V4 for 16ng@ietf.org; Mon, 12 Feb 2007 15:06:37 -0500
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l1CK6QLX024389; Mon, 12 Feb 2007 14:06:27 -0600 (CST)
Received: from ILEXC2U02.ndc.lucent.com ([135.3.39.9]) by ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 12 Feb 2007 14:06:26 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [16NG] Fw:I-DACTION:draft-madanapalli-16ng-ipv4-over-802-dot-16-ipcs-00.txt
Date: Mon, 12 Feb 2007 14:06:26 -0600
Message-ID: <61B0DCC9767CDC4C91769592B12CCDD136EB4A@ILEXC2U02.ndc.lucent.com>
In-Reply-To: <583400.71141.qm@web60323.mail.yahoo.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [16NG] Fw:I-DACTION:draft-madanapalli-16ng-ipv4-over-802-dot-16-ipcs-00.txt
Thread-Index: AcdO2tpZFEK2z8YXRCCYHLOgT5+lZwAAqLdQ
References: <583400.71141.qm@web60323.mail.yahoo.com>
From: "Narvaez, Paolo \(Paolo\)" <paolo@alcatel-lucent.com>
To: "Behcet Sarikaya" <sarikaya@ieee.org>, "Syam Madanapalli" <smadanapalli@gmail.com>
X-OriginalArrivalTime: 12 Feb 2007 20:06:26.0856 (UTC) FILETIME=[46F72A80:01C74EE1]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 1094b1c84fa6e846d476f39271f5074f
Cc: 16ng@ietf.org
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="===============0015834325=="
Errors-To: 16ng-bounces@ietf.org

 
How can the MS and AR send ARP requests and responses to each other?
These ARP messages have to go over IPCS and there is no IP packet in
this case.
 
If there is concern for a legacy IPv4 stack at the MS sending ARP
requests and perhaps even requiring ARP responses, why not recommend a
shim layer between the IPv4 stack and the 802.16 IPCS layer at the MS.
This layer would filter ARP requests arriving from the IPv4 stack and
respond with any MAC address. The IPCS classifier should never see ARP
messages, and they should never be sent over the air.
 
Regards,
Paolo


________________________________

	From: Behcet Sarikaya [mailto:behcetsarikaya@yahoo.com] 
	Sent: Monday, February 12, 2007 2:19 PM
	To: Syam Madanapalli
	Cc: 16ng@ietf.org
	Subject: Re: [16NG]
Fw:I-DACTION:draft-madanapalli-16ng-ipv4-over-802-dot-16-ipcs-00.txt
	
	
	Hi Syam,
	  You mentioned P2P link here in this message but I could not
see any text on this in the draft. Maybe a section should be added on
the address and subnet mask assignment given the P2P nature of the link
and the fact that such assignments are not commonly used.
	  You recommended AR to ignore ARP Requests from MS, I am not
sure if this is OK or a Reply would be needed according to ARP?
	 
	Regards,
	 
	Behcet
	
	
	----- Original Message ----
	From: Syam Madanapalli <smadanapalli@gmail.com>
	To: "Narvaez, Paolo (Paolo)" <paolo@alcatel-lucent.com>
	Cc: 16ng@ietf.org
	Sent: Saturday, February 10, 2007 12:34:46 AM
	Subject: Re: [16NG] Fw:
I-DACTION:draft-madanapalli-16ng-ipv4-over-802-dot-16-ipcs-00.txt
	
	
	Hi Paolo,
	
	On 2/10/07, Narvaez, Paolo (Paolo) <paolo@alcatel-lucent.com>
wrote:
	>
	> I have two general comments on this draft.
	>
	> 1. Section 7 assumes that ARP messages sent by the MS are
received by
	> the AR. The section states that ARP messages should be dropped
by the
	> AR. However, since ARP runs directly over Ethernet (there is
no IP
	> header) how can the 802.16 IPCS carry this type of packet over
the air?
	
	As mentioned the draft, ARP is not required for 802.16 because
of the fact
	that the MAC address is not required for identifying the
destination.
	There was a concern that an unmodified host may send ARP without
knowing
	that the underlying interface is 802.16, because of this I added
the
	above statement.
	
	If we think there is no such possibility, then I will remove
this text.
	
	>
	> 2. What is the subnet assignment? Can two MSs be on the same
subnet? Or
	> do we need to introduce some restrictions as in the
IPv6-over-802.16
	> draft.
	
	The draft assumes the p2p link, so no two MSs can be on the same
subnet.
	
	Thanks,
	Syam
	
	>
	> Regards,
	> Paolo
	>
	>
	>
	>
	> > -----Original Message-----
	> > From: Daniel Park [mailto:soohong.park@samsung.com]
	> > Sent: Thursday, February 08, 2007 7:17 PM
	> > To: 16ng@ietf.org
	> > Subject: [16NG] Fw:
	> >
I-DACTION:draft-madanapalli-16ng-ipv4-over-802-dot-16-ipcs-00.txt
	> >
	> > IPv4CS document is now available at:
	> >
http://www.ietf.org/internet-drafts/draft-madanapalli-16ng-ipv
	> > 4-over-802-dot-16-ipcs-00.txt
	> >
	> > Daniel (Soohong Daniel Park)
	> > Mobile Convergence Laboratory, SAMSUNG Electronics.
	> >
	> > _______________________________________________
	> > 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 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