
From root@core3.amsl.com  Wed Jun  3 08:45:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: 16ng@ietf.org
Delivered-To: 16ng@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id B0C963A6CBB; Wed,  3 Jun 2009 08:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090603154501.B0C963A6CBB@core3.amsl.com>
Date: Wed,  3 Jun 2009 08:45:01 -0700 (PDT)
Cc: 16ng@ietf.org
Subject: [16NG] I-D Action:draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05.txt
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2009 15:45:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IP over IEEE 802.16 Networks Working Group of the IETF.


	Title           : Transmission of IPv4 packets over IEEE 802.16's IP Convergence Sublayer
	Author(s)       : S. Madanapalli, et al.
	Filename        : draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05.txt
	Pages           : 14
	Date            : 2009-06-03

IEEE 802.16 is an air interface specification for wireless broadband
access.  IEEE 802.16 has specified multiple service specific
Convergence Sublayers for transmitting upper layer protocols.  The
packet CS (Packet Convergence Sublayer) is used for the transport of
all packet-based protocols such as Internet Protocol (IP), IEEE 802.3
(Ethernet) and IEEE 802.1Q (VLAN).  The IP-specific part of the
Packet CS enables the transport of IPv4 packets directly over the
IEEE 802.16 MAC.

This document specifies the frame format, the Maximum Transmission
Unit (MTU) and address assignment procedures for transmitting IPv4
packets over the IP-specific part of the Packet Convergence Sublayer
of IEEE 802.16.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-06-03083758.I-D@ietf.org>


--NextPart--

From g_e_montenegro@yahoo.com  Wed Jun  3 10:09:55 2009
Return-Path: <g_e_montenegro@yahoo.com>
X-Original-To: 16ng@core3.amsl.com
Delivered-To: 16ng@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8265F3A6884 for <16ng@core3.amsl.com>; Wed,  3 Jun 2009 10:09:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u9z2WMZPjiLC for <16ng@core3.amsl.com>; Wed,  3 Jun 2009 10:09:53 -0700 (PDT)
Received: from web82606.mail.mud.yahoo.com (web82606.mail.mud.yahoo.com [68.142.201.123]) by core3.amsl.com (Postfix) with SMTP id A56043A6847 for <16ng@ietf.org>; Wed,  3 Jun 2009 10:09:52 -0700 (PDT)
Received: (qmail 22946 invoked by uid 60001); 3 Jun 2009 17:09:52 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1244048992; bh=P7iL8sp8R9M0wDEuC6gaO83XLPTQum8N+IhlJlimiaI=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=aK0m3rcfkM0FPLKlMFknd4E2eyl+cdmEovPO3XXtzSpD8k3DOus1ns0qF+lFudBEnlHS8Al3oPIIoOfRPS9IPxADF/h95wHqFA0LBjRTMQVSq7Zkf7TBkH+vZN+h9q8Q9SD1FLxZh7BhCbkwjj72C15Ty7ySpqfkfz6VpkXIv1U=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=CtgB9lZODs9V5jcIHP0V94qy4KE0YrWJbfNcKYPgwYEGgw6mTvRF2sjXVAzqqymou5yEwlns4fF9a5yXcp0+578/32pNOxwzZTEP0xGpQyYy3ZWSPi1ZxRspS9y4CLY8tBEzf/S16JTikmCnKrpc/jeaNZJTbdNTO1ySOkKAPks=;
Message-ID: <570230.22436.qm@web82606.mail.mud.yahoo.com>
X-YMail-OSG: yLXn2zIVM1lRgW7QDbDnJvmz53gj0tt0uRg4tSZsIcya7Rtb5YFoWri.N7CqZZRj6wCUCxOksZt2bhMNzw.bcANTL8vzmkclAroS_4j384nuXdB4zXwVYOqrhFNweICWl9rkPKioaI8dwaG7B2i7vMJr0.sDL8A9iflbayjiV94Pm4Vd005cVHx.rgYxyCrYZ4PvqMODMMbczRwkVwYk.R.bj.M0f79Q1gxJR8V93UoCholgVut9PbuZn8ezmgSbIqoRKcyJXsLNIpo5zyasIlg393CXdAjIjaOd81RKlfZQyYZfli_eoURZm._6FXyqj6WSX2i0dryGy.BaU9w-
Received: from [24.16.92.42] by web82606.mail.mud.yahoo.com via HTTP; Wed, 03 Jun 2009 10:09:52 PDT
X-Mailer: YahooMailRC/1277.43 YahooMailWebService/0.7.289.10
References: <2828BDE8DC61004E8104C78E82A0B39710B25385F2@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com><BC27158B99D3064A955ADE084783900C01B5CBC8@DEMUEXC014.nsn-intra.net> <Pine.GSO.4.64.0905151247200.12703@tin>, <046201c9d589$267cf8d0$7376ea70$@com> <BAA9BC6C-6B59-4BA6-B63D-E09C26E0194B@mimectl> <BC27158B99D3064A955ADE084783900C020F18E5@DEMUEXC014.nsn-intra.net> <056601c9d7e8$b8be17e0$2a3a47a0$@com> <556994.50253.qm@web82604.mail.mud.yahoo.com> <06ab01c9d8cd$079cc660$16d65320$@com> <BC27158B99D3064A955ADE084783900C020F26B5@DEMUEXC014.nsn-intra.net> <916575.77425.qm@web82607.mail.mud.yahoo.com>
Date: Wed, 3 Jun 2009 10:09:52 -0700 (PDT)
From: gabriel montenegro <g_e_montenegro@yahoo.com>
To: "Riegel, Maximilian \(NSN - DE/Munich\)" <maximilian.riegel@nsn.com>, ext Samita Chakrabarti <samitac@ipinfusion.com>, Wesley George <wgeorge@sprint.net>
In-Reply-To: <916575.77425.qm@web82607.mail.mud.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1809340865-1244048992=:22436"
Cc: ext Alper Yegin <alper.yegin@yegin.org>, 16ng@ietf.org
Subject: Re: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2009 17:09:55 -0000

--0-1809340865-1244048992=:22436
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

The new rev has appeared:=0Ahttp://tools.ietf.org/html/draft-ietf-16ng-ipv4=
-over-802-dot-16-ipcs-05=0A=0AThis is a summary of changes:=0A=0AEditorial =
changes throughout.=0A=0AGot rid of all mention of WiMAX in the main text.=
=0A=0ASection 3 on network architecture: deleted much text, instead referri=
ng to the=0Arelevant sections in IEEE802.16, 5121 and 5154. No need to repe=
at text that appears =0Aelsewhere.=0A=0ASection 4.3 on MTU: simplified to s=
ay not much more than RFC5121 says.=0A=0ASection 6 on handling multicast. G=
ot rid of it. It repeats stuff already in=0Aboth 5.3 and 5.1.=0A=0AAppendix=
 on WiMAX MTU.=0AGot rid of:=0A=A0=A0 The addressing and operation of IPv4 =
CS described in this=0A=A0=A0 document are applicable to the WiMAX networks=
 as well.=A0=0AGot rid of recommendation that WiMAX adopt this specificatio=
n.=0A=0ABut your favorite diff tool is your best bet, e.g.:=0A=0Ahttp://too=
ls.ietf.org/rfcdiff?url2=3Ddraft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05.txt=
=0A=0APlease look it over. Hopefully, the remaining issues are manageable a=
nd less in number.=0A=0Athanks,=0A=0AGabriel=0A=0A=0A=0A___________________=
_____________=0AFrom: gabriel montenegro <g_e_montenegro@yahoo.com>=0ATo: "=
Riegel, Maximilian (NSN - DE/Munich)" <maximilian.riegel@nsn.com>; ext Sami=
ta Chakrabarti <samitac@ipinfusion.com>; Wesley George <wgeorge@sprint.net>=
=0ACc: ext Alper Yegin <alper.yegin@yegin.org>; 16ng@ietf.org=0ASent: Wedne=
sday, May 20, 2009 8:41:46 AM=0ASubject: Re: [16NG] [nwg-chair] NWG feedbac=
k on 16ng's IPv4 CS draft=0A=0A=0ALet's wait till the next version appears =
(ETA: end of this month) as hopefully that version=0Awill require less fixe=
s.=0A=0A=0A=0A=0A________________________________=0AFrom: "Riegel, Maximili=
an (NSN - DE/Munich)" <maximilian.riegel@nsn.com>=0ATo: ext Samita Chakraba=
rti <samitac@ipinfusion.com>; gabriel montenegro <g_e_montenegro@yahoo.com>=
; Wesley George <wgeorge@sprint.net>=0ACc: ext Alper Yegin <alper.yegin@yeg=
in.org>; 16ng@ietf.org=0ASent: Wednesday, May 20, 2009 2:11:31 AM=0ASubject=
: Re: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft=0A=0A=0AMy po=
int is not the MTU size, I am concerned about the quality of the current do=
cument. There are=A0a number of=A0ambiguities and misconceptions, which wou=
ld require some efforts for resolving. I once did an approach to create a s=
ubmission to the mailing list and gave up after an hour seeing that it requ=
ires more=A0text to explain the issues in the document than just rephrasing=
 the text.=0A=A0=0AWould it be possible to held a conference call to discus=
s the readiness of the IPv4-CS I-D?=0A=A0=0ABye=0AMax=0A=0A=0A_____________=
___________________=0AFrom: ext Samita Chakrabarti [mailto:samitac@ipinfusi=
on.com] =0ASent: Tuesday, May 19, 2009 11:59 PM=0ATo: 'gabriel montenegro';=
 Riegel, Maximilian (NSN - DE/Munich); 'Wesley George'=0ACc: 'ext Alper Yeg=
in'; 16ng@ietf.org=0ASubject: RE: [16NG] [nwg-chair] NWG feedback on 16ng's=
 IPv4 CS draft=0A=0A=0AAgreed. =0ADefault MTU is 1500 =A0- if WiMAX does no=
t want to update their SPEC or does not want to conform to this IETF draft,=
 it is SDO business. Thus we can move forward =A0independently.=0A=A0=0ATha=
nks,=0A-Samita=0A=A0=0AFrom:gabriel montenegro [mailto:g_e_montenegro@yahoo=
.com] =0ASent: Tuesday, May 19, 2009 9:39 AM=0ATo: Samita Chakrabarti; Rieg=
el, Maximilian (NSN - DE/Munich); Wesley George=0ACc: ext Alper Yegin; 16ng=
@ietf.org=0ASubject: Re: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS =
draft=0A=A0=0AI think what we need (my intention) is not more details, but =
less. I agree that there is=0Asome overlap with the WiMAX spec. We should s=
imply refer to WiMAX for the WiMAX-specifics, =0Aand drop the recommendatio=
n that WiMAX should adopt this spec. Given the difference in=A0MTU,=0AI won=
't hold my breath for them to do so, but it's really their business. =0A=A0=
=0A=0A________________________________=0A=0AFrom:Samita Chakrabarti <samita=
c@ipinfusion.com>=0ATo: "Riegel, Maximilian (NSN - DE/Munich)" <maximilian.=
riegel@nsn.com>; ext Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>;=
 Wesley George <wgeorge@sprint.net>=0ACc: ext Alper Yegin <alper.yegin@yegi=
n.org>; 16ng@ietf.org=0ASent: Monday, May 18, 2009 11:44:47 AM=0ASubject: R=
e: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft=0AHi Max,=0A=A0=
=0AAs I understand from NWG feedback that they did not like IETF to recomme=
nd 1500 byte MTU size (Appendix section) for future revision of NWG Wimax s=
pecs.=A0 Other than that there are minor editorial changes that we want to =
do to polish the draft. =0A=A0=0AHere is the summary from NWG feedback:=0A>=
 > In particular the influence of tunneling inside the network should be=0A=
> > carefully discussed.=0A> > In addition we would kindly ask to either re=
move whole Appendix C on=0A> > the WiMAX MTU size or revise the text explai=
ning the real issues in=0A> > the WiMAX architecture. In particular the sta=
tements on the=0A> > applicability of the I-D on the WiMAX architecture and=
 the=0A> > recommendation on future modifications in the WiMAX architecture=
 seem=0A> > not to be very appropriate to us.=0AWhat is your suggestion on =
updating Appendix C? =0A=A0=0AThanks,=0A-Samita=0A=A0=0A=A0=0AFrom:Riegel, =
Maximilian (NSN - DE/Munich) [mailto:maximilian.riegel@nsn.com] =0ASent: Mo=
nday, May 18, 2009 12:19 AM=0ATo: ext Gabriel Montenegro; Samita Chakrabart=
i; Wesley George=0ACc: ext Alper Yegin; 16ng@ietf.org=0ASubject: RE: [16NG]=
 [nwg-chair] NWG feedback on 16ng's IPv4 CS draft=0A=A0=0AIs there really a=
 demand to work on an update of the IPv4-CS I-D?=0AWhich details would requ=
ire/qualify for=A0an IETF specification?=0AThe current architectural model =
closely resembles the WiMAX architecture, and WiMAX provides a comprehensiv=
e specification for it.=0A=A0=0ABye=0AMax=0A=A0=0A=0A______________________=
__________=0A=0AFrom:ext Gabriel Montenegro [mailto:Gabriel.Montenegro@micr=
osoft.com] =0ASent: Friday, May 15, 2009 8:21 PM=0ATo: Samita Chakrabarti; =
'Wesley George'; Riegel, Maximilian (NSN - DE/Munich)=0ACc: 'ext Alper Yegi=
n'; 16ng@ietf.org=0ASubject: RE: [16NG] [nwg-chair] NWG feedback on 16ng's =
IPv4 CS draft=0Ayes, I've been delinquently holding to the pen.=0ALets shoo=
t for end of the month at the latest.=0A=0A________________________________=
=0A=0AFrom:Samita Chakrabarti [samitac@ipinfusion.com]=0ASent: Friday, May =
15, 2009 11:15 AM=0ATo: 'Wesley George'; 'Riegel, Maximilian (NSN - DE/Muni=
ch)'=0ACc: 'ext Alper Yegin'; Gabriel Montenegro; 16ng@ietf.org=0ASubject: =
RE: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft=0AHi Wes,=0A=0A=
Yes, there will be an updated draft before Stockholm. Gabriel was working o=
n=0Athe updates.=0A=0AI am expecting that we will soon have a revision to r=
eview.=0A=0AThanks,=0A-Samita=0A=0A> -----Original Message-----=0A> From: 1=
6ng-bounces@ietf.org [mailto:16ng-bounces@ietf.org] On Behalf Of=0A> Wesley=
 George=0A> Sent: Friday, May 15, 2009 9:54 AM=0A> To: Riegel, Maximilian (=
NSN - DE/Munich)=0A> Cc: ext Alper Yegin; ext Gabriel Montenegro; 16ng@ietf=
.org=0A> Subject: Re: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS dra=
ft=0A> =0A> Is someone working on an updated version of this draft to be re=
viewed in=0A> Stockholm since we did not meet in SFO? I believe that one of=
 the first=0A> times that I submitted objections to the MTU language, I pro=
vided a=0Aproposed=0A> text that would cover some of the concerns raised be=
low, not all of which=0A> was included in subsequent drafts.=0A> http://www=
.ietf.org/mail-archive/web/16ng/current/msg00824.html=0A> =0A> Thanks,=0A> =
Wes=0A> =0A> _________________________________________=0A>=A0=A0=A0 Wesley =
George=0A>=A0=A0=A0=A0=A0=A0=A0 Sprint IP Engineering=0A>=A0=A0=A0 703-689-=
7505 (O)=A0 703-864-4902 (PCS)=0A>=A0=A0=A0=A0=A0=A0=A0=A0=A0 http://www.sp=
rint.net/=0A> _________________________________________=0A> =0A> =0A> On Th=
u, 12 Feb 2009, Riegel, Maximilian (NSN - DE/Munich) wrote:=0A> =0A> > Gabr=
iel,=0A> >=0A> > The WiMAX Forum NWG reviewed section 4-3 and Appendix C of=
=0A> > draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-04.txt and would like to=
=0A> > make a couple of remarks on the MTU issue:=0A> >=0A> > - The I-D is =
not very clear about the MTU issues appearing in an IPv4=0A> > over IEEE 80=
2.16 transmission system. The ambiguities mainly result=0A> > out of the va=
gue definition of the IEEE 802.16 link comprising both=0A> > the radio part=
 of the link as well as the part of the link between BS=0A> > and AR, when =
the functions are located in different entities.=0A> >=0A> > - Section 4.3 =
in particular misses the discussion of the dependencies=0A> > between MTU s=
ize and the tunneling protocol deployed between BS and AR.=0A> >=0A> > - Se=
ction 4.3 also misses, that there is no packet loss when the MTU=0A> > size=
 limitation is caused by the encapsulation overhead on the link=0A> > betwe=
en BS and AR. E.g. when GRE is used for the tunnel between BS and=0A> > AR,=
 the transport IP layer can fragment the GRE packets to fit the=0A> > trans=
port MTU on the link between BS and AR. Reassembly in the tunnel=0A> > endp=
oint at the AR will re-establish the original user IP packet.=0A> >=0A> > -=
 Please note that the reason of the WiMAX NWG to limit the MTU going=0A> > =
over IPv4-CS to 1400 Bytes was to avoid fragmentation on the link=0A> > bet=
ween BS and ASN-GW as well as on the link between ASN-GW and CSN=0A> > (MIP=
 tunnel). Fragmentation and re-assembly require considerable=0A> > processi=
ng power in the network elements.=0A> >=0A> > - Appendix C makes statements=
 which would require more detailed review=0A> > of the I-D by WiMAX NWG. In=
 particular 'The addressing and operation=0A> > of IPv4-CS described in thi=
s document are applicable to the WiMAX=0A> > networks as well' has not been=
 verified yet.=0A> > Furthermore 'Thus, WiMAX MS nodes should use this defa=
ult (1400) MTU=0A> > value per the current specification [WMF].=A0 However,=
 due to reasons=0A> > specified in section 4.3 above, it is strongly recomm=
ended that future=0A> > WiMAX MS nodes support a default MTU of 1500 bytes,=
 and that they=0A> > implement MTU negotiation capabilities as mentioned in=
 this document.'=0A> > makes recommendations to WiMAX without understanding=
 the real reasons=0A> > for the limitation of the MTU size in Mobile WiMAX.=
=0A> >=0A> > We would recommend to 16ng to revise the sections on MTU size =
to=0A> > better explain the underlying issues leading to restrictions in th=
e MTU=0A> size.=0A> > In particular the influence of tunneling inside the n=
etwork should be=0A> > carefully discussed.=0A> > In addition we would kind=
ly ask to either remove whole Appendix C on=0A> > the WiMAX MTU size or rev=
ise the text explaining the real issues in=0A> > the WiMAX architecture. In=
 particular the statements on the=0A> > applicability of the I-D on the WiM=
AX architecture and the=0A> > recommendation on future modifications in the=
 WiMAX architecture seem=0A> > not to be very appropriate to us.=0A> >=0A> =
>=0A> > Bye=0A> > Max=0A> > Vize Chair NWG=0A> >=0A> >=0A> > ______________=
__________________=0A> >=0A> > From: ext Gabriel Montenegro [mailto:Gabriel=
.Montenegro@microsoft.com]=0A> > Sent: Monday, November 03, 2008 11:59 AM=
=0A> > To: nwg-chair@list.wimaxforum.org=0A> > Cc: 'Daniel Soohong Park'=0A=
> > Subject: [nwg-chair] NWG feedback on 16ng's IPv4 CS draft=0A> >=0A> >=
=0A> >=0A> > Prakash, Max and Yong Chang,=0A> >=0A> >=0A> > The IETF 16ng W=
G has published a revision of this draft:=0A> >=0A> > "Transmission of IPv4=
 packets over IEEE 802.16's IP Convergence=0A> > Sublayer"=0A> >=0A> > Per =
this announcement:=0A> >=0A> > http://www.ietf.org/mail-archive/web/16ng/cu=
rrent/msg00863.html=0A> > <http://www.ietf.org/mail-archive/web/16ng/curren=
t/msg00863.html>=0A> >=0A> > We understand that this specification currentl=
y is not normative to=0A> > NWG (as opposed to RFC5121 on IPv6 CS). Neverth=
eless, given its=0A> > relevance, and with the hope it may become normative=
 to NWG in some=0A> > future revision, the 16ng WG would like to solicit fe=
edback from NWG=0A> > on this draft.=0A> >=0A> > In particular, please note=
 that this draft specifies a default MTU of=0A> > 1500,=A0 which is differe=
nt from the WiMAX-specified MTU of 1400 (per=0A> > the recently approved R1=
_V1.3.0-Stage-3=A0 NWG specifications).=A0 For MTU=0A> > discussion, please=
 refer to these sections:=0A> >=0A> > http://tools.ietf.org/html/draft-ietf=
-16ng-ipv4-over-802-dot-16-ipcs-0=0A> > 4#=0A> > section-4.3=0A> > <http://=
tools.ietf.org/html/draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-=0A> > 04=0A>=
 > #section-4.3>=0A> > http://tools.ietf.org/html/draft-ietf-16ng-ipv4-over=
-802-dot-16-ipcs-0=0A> > 4#=0A> > appendix-C=0A> > <http://tools.ietf.org/h=
tml/draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-=0A> > 04=0A> > #appendix-C>=
=0A> >=0A> > The 16ng WG will next meet on Nov 18 during the IETF in Minnea=
polis=0A> > (https://datatracker.ietf.org/meeting/73/agenda.html). If at al=
l=0A> > possible, it would be best if comments were received before that da=
te=0A> > in order for the WG to discuss them during the meeting.=0A> >=0A> =
> Please send your comments to the 16ng@ietf.org <mailto:16ng@ietf.org>=0A>=
 > mailing list.=0A> >=0A> > Thanks,=0A> >=0A> > Gabriel and Daniel=0A> > 1=
6ng co-chairs=0A> >=0A> >=0A> >=0A> >=0A> _________________________________=
______________=0A> 16NG mailing list=0A> 16NG@ietf.org=0A> https://www.ietf=
.org/mailman/listinfo/16ng
--0-1809340865-1244048992=:22436
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:Courier New, courier, monaco, monospace,=
 sans-serif;font-size:10pt"><DIV>The new rev has appeared:</DIV>=0A<DIV><A =
href=3D"http://tools.ietf.org/html/draft-ietf-16ng-ipv4-over-802-dot-16-ipc=
s-05">http://tools.ietf.org/html/draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-=
05</A></DIV>=0A<DIV>&nbsp;</DIV>=0A<DIV>This is a summary of changes:</DIV>=
=0A<DIV>&nbsp;</DIV>=0A<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px" dir=3Dltr>=
=0A<DIV>Editorial changes throughout.</DIV>=0A<DIV>&nbsp;</DIV>=0A<DIV>Got =
rid of all mention of WiMAX in the main text.</DIV>=0A<DIV>&nbsp;</DIV>=0A<=
DIV>Section 3 on network architecture: deleted much text, instead referring=
 to the<BR>relevant sections in IEEE802.16, 5121 and 5154. No need to repea=
t text that appears <BR>elsewhere.</DIV>=0A<DIV>&nbsp;</DIV>=0A<DIV>Section=
 4.3 on MTU: simplified to say not much more than RFC5121 says.</DIV>=0A<DI=
V>&nbsp;</DIV>=0A<DIV>Section 6 on handling multicast. Got rid of it. It re=
peats stuff already in<BR>both 5.3 and 5.1.</DIV>=0A<DIV>&nbsp;</DIV>=0A<DI=
V>Appendix on WiMAX MTU.</DIV>=0A<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px" di=
r=3Dltr>=0A<DIV>Got rid of:<BR>&nbsp;&nbsp; The addressing and operation of=
 IPv4 CS described in this<BR>&nbsp;&nbsp; document are applicable to the W=
iMAX networks as well.&nbsp;</DIV>=0A<DIV>Got rid of recommendation that Wi=
MAX adopt this specification.</DIV></BLOCKQUOTE></BLOCKQUOTE>=0A<DIV>&nbsp;=
</DIV>=0A<DIV>But your favorite diff tool is your best bet, e.g.:</DIV>=0A<=
DIV><BR><A href=3D"http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-16ng-ipv=
4-over-802-dot-16-ipcs-05.txt">http://tools.ietf.org/rfcdiff?url2=3Ddraft-i=
etf-16ng-ipv4-over-802-dot-16-ipcs-05.txt</A></DIV>=0A<DIV>&nbsp;</DIV>=0A<=
DIV>Please look it over. Hopefully, the remaining issues are manageable and=
 less in number.</DIV>=0A<DIV>&nbsp;</DIV>=0A<DIV>thanks,</DIV>=0A<DIV>&nbs=
p;</DIV>=0A<DIV>Gabriel</DIV>=0A<DIV style=3D"FONT-FAMILY: Courier New, cou=
rier, monaco, monospace, sans-serif; FONT-SIZE: 10pt"><BR>=0A<DIV style=3D"=
FONT-FAMILY: times new roman, new york, times, serif; FONT-SIZE: 12pt"><FON=
T size=3D2 face=3DTahoma>=0A<HR SIZE=3D1>=0A<B><SPAN style=3D"FONT-WEIGHT: =
bold">From:</SPAN></B> gabriel montenegro &lt;g_e_montenegro@yahoo.com&gt;<=
BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> "Riegel, Maximilian =
(NSN - DE/Munich)" &lt;maximilian.riegel@nsn.com&gt;; ext Samita Chakrabart=
i &lt;samitac@ipinfusion.com&gt;; Wesley George &lt;wgeorge@sprint.net&gt;<=
BR><B><SPAN style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> ext Alper Yegin &lt;=
alper.yegin@yegin.org&gt;; 16ng@ietf.org<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B> Wednesday, May 20, 2009 8:41:46 AM<BR><B><SPAN style=
=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [16NG] [nwg-chair] NWG feedb=
ack on 16ng's IPv4 CS draft<BR></FONT><BR>=0A<DIV style=3D"FONT-FAMILY: Cou=
rier New, courier, monaco, monospace, sans-serif; FONT-SIZE: 10pt">=0A<DIV>=
Let's wait till the next version appears (ETA: end of this month) as hopefu=
lly that version</DIV>=0A<DIV>will require less fixes.<BR></DIV>=0A<DIV sty=
le=3D"FONT-FAMILY: Courier New, courier, monaco, monospace, sans-serif; FON=
T-SIZE: 10pt"><BR>=0A<DIV style=3D"FONT-FAMILY: times new roman, new york, =
times, serif; FONT-SIZE: 12pt"><FONT size=3D2 face=3DTahoma>=0A<HR SIZE=3D1=
>=0A<B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> "Riegel, Maximili=
an (NSN - DE/Munich)" &lt;maximilian.riegel@nsn.com&gt;<BR><B><SPAN style=
=3D"FONT-WEIGHT: bold">To:</SPAN></B> ext Samita Chakrabarti &lt;samitac@ip=
infusion.com&gt;; gabriel montenegro &lt;g_e_montenegro@yahoo.com&gt;; Wesl=
ey George &lt;wgeorge@sprint.net&gt;<BR><B><SPAN style=3D"FONT-WEIGHT: bold=
">Cc:</SPAN></B> ext Alper Yegin &lt;alper.yegin@yegin.org&gt;; 16ng@ietf.o=
rg<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, May =
20, 2009 2:11:31 AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Subject:</SPAN>=
</B> Re: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft<BR></FONT>=
<BR>=0A<STYLE>_filtered {=0Afont-family:Cambria Math;}=0A_filtered {=0Afont=
-family:Calibri;}=0A_filtered {=0Afont-family:Tahoma;}=0A_filtered {margin:=
1.0in 1.0in 1.0in 1.0in;}=0AP.MsoNormal {=0AFONT-SIZE:12pt;MARGIN:0in 0in 0=
pt;FONT-FAMILY:"Times New Roman", "serif";}=0ALI.MsoNormal {=0AFONT-SIZE:12=
pt;MARGIN:0in 0in 0pt;FONT-FAMILY:"Times New Roman", "serif";}=0ADIV.MsoNor=
mal {=0AFONT-SIZE:12pt;MARGIN:0in 0in 0pt;FONT-FAMILY:"Times New Roman", "s=
erif";}=0AA:link {=0ACOLOR:blue;TEXT-DECORATION:underline;}=0ASPAN.MsoHyper=
link {=0ACOLOR:blue;TEXT-DECORATION:underline;}=0AA:visited {=0ACOLOR:purpl=
e;TEXT-DECORATION:underline;}=0ASPAN.MsoHyperlinkFollowed {=0ACOLOR:purple;=
TEXT-DECORATION:underline;}=0AP {=0AFONT-SIZE:12pt;MARGIN:0in 0in 0pt;FONT-=
FAMILY:"Times New Roman", "serif";}=0AP.emailquote {=0AFONT-SIZE:12pt;MARGI=
N:0in 0in 0pt 1pt;FONT-FAMILY:"Times New Roman", "serif";}=0ALI.emailquote =
{=0AFONT-SIZE:12pt;MARGIN:0in 0in 0pt 1pt;FONT-FAMILY:"Times New Roman", "s=
erif";}=0ADIV.emailquote {=0AFONT-SIZE:12pt;MARGIN:0in 0in 0pt 1pt;FONT-FAM=
ILY:"Times New Roman", "serif";}=0AP.msochpdefault {=0AFONT-SIZE:10pt;MARGI=
N:0in 0in 0pt;FONT-FAMILY:"Times New Roman", "serif";}=0ALI.msochpdefault {=
=0AFONT-SIZE:10pt;MARGIN:0in 0in 0pt;FONT-FAMILY:"Times New Roman", "serif"=
;}=0ADIV.msochpdefault {=0AFONT-SIZE:10pt;MARGIN:0in 0in 0pt;FONT-FAMILY:"T=
imes New Roman", "serif";}=0ASPAN.emailstyle19 {=0AVERTICAL-ALIGN:baseline;=
FONT-FAMILY:"Calibri", "sans-serif";TEXT-DECORATION:none;text-shadow:none;}=
=0ASPAN.EmailStyle21 {=0AVERTICAL-ALIGN:baseline;FONT-FAMILY:"Calibri", "sa=
ns-serif";TEXT-DECORATION:none;text-shadow:none;}=0A.MsoChpDefault {=0AFONT=
-SIZE:10pt;}=0ADIV.Section1 {=0A}=0A</STYLE>=0A=0A<DIV dir=3Dltr align=3Dle=
ft><SPAN class=3D031101106-20052009><FONT color=3D#000080 size=3D2 face=3D"=
Courier New">My point is not the MTU size, I am concerned about the quality=
 of the current document. There are&nbsp;a number of&nbsp;ambiguities and m=
isconceptions, which would require some efforts for resolving. I once did a=
n approach to create a submission to the mailing list and gave up after an =
hour seeing that it requires more&nbsp;text to explain the issues in the do=
cument than just rephrasing the text.</FONT></SPAN></DIV>=0A<DIV dir=3Dltr =
align=3Dleft><SPAN class=3D031101106-20052009><FONT color=3D#000080 size=3D=
2 face=3D"Courier New"></FONT></SPAN>&nbsp;</DIV>=0A<DIV dir=3Dltr align=3D=
left><SPAN class=3D031101106-20052009><FONT color=3D#000080 size=3D2 face=
=3D"Courier New">Would it be possible to held a conference call to discuss =
the readiness of the IPv4-CS I-D?</FONT></SPAN></DIV>=0A<DIV dir=3Dltr alig=
n=3Dleft><SPAN class=3D031101106-20052009><FONT color=3D#000080 size=3D2 fa=
ce=3D"Courier New"></FONT></SPAN>&nbsp;</DIV>=0A<DIV dir=3Dltr align=3Dleft=
><SPAN class=3D031101106-20052009><FONT color=3D#000080 size=3D2 face=3D"Co=
urier New">Bye</FONT></SPAN></DIV>=0A<DIV dir=3Dltr align=3Dleft><SPAN clas=
s=3D031101106-20052009><FONT color=3D#000080 size=3D2 face=3D"Courier New">=
Max</FONT></SPAN></DIV><BR>=0A<DIV dir=3Dltr lang=3Den-us class=3DOutlookMe=
ssageHeader align=3Dleft>=0A<HR tabIndex=3D-1>=0A<FONT size=3D2 face=3DTaho=
ma><B>From:</B> ext Samita Chakrabarti [mailto:samitac@ipinfusion.com] <BR>=
<B>Sent:</B> Tuesday, May 19, 2009 11:59 PM<BR><B>To:</B> 'gabriel monteneg=
ro'; Riegel, Maximilian (NSN - DE/Munich); 'Wesley George'<BR><B>Cc:</B> 'e=
xt Alper Yegin'; 16ng@ietf.org<BR><B>Subject:</B> RE: [16NG] [nwg-chair] NW=
G feedback on 16ng's IPv4 CS draft<BR></FONT><BR></DIV>=0A<DIV></DIV>=0A<DI=
V class=3DSection1>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Cal=
ibri', 'sans-serif'; FONT-SIZE: 11pt">Agreed. </SPAN></P>=0A<P class=3DMsoN=
ormal><SPAN style=3D"FONT-FAMILY: 'Calibri', 'sans-serif'; FONT-SIZE: 11pt"=
>Default MTU is 1500 &nbsp;- if WiMAX does not want to update their SPEC or=
 does not want to conform to this IETF draft, it is SDO business. Thus we c=
an move forward &nbsp;independently.</SPAN></P>=0A<P class=3DMsoNormal><SPA=
N style=3D"FONT-FAMILY: 'Calibri', 'sans-serif'; FONT-SIZE: 11pt">&nbsp;</S=
PAN></P>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri', 'san=
s-serif'; FONT-SIZE: 11pt">Thanks,</SPAN></P>=0A<P class=3DMsoNormal><SPAN =
style=3D"FONT-FAMILY: 'Calibri', 'sans-serif'; FONT-SIZE: 11pt">-Samita</SP=
AN></P>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri', 'sans=
-serif'; FONT-SIZE: 11pt">&nbsp;</SPAN></P>=0A<DIV style=3D"BORDER-BOTTOM: =
medium none; BORDER-LEFT: blue 1.5pt solid; PADDING-BOTTOM: 0in; PADDING-LE=
FT: 4pt; PADDING-RIGHT: 0in; BORDER-TOP: medium none; BORDER-RIGHT: medium =
none; PADDING-TOP: 0in">=0A<DIV>=0A<DIV style=3D"BORDER-BOTTOM: medium none=
; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING=
-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADD=
ING-TOP: 3pt">=0A<P class=3DMsoNormal><B><SPAN style=3D"FONT-FAMILY: 'Tahom=
a', 'sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN style=3D"FONT-FAMI=
LY: 'Tahoma', 'sans-serif'; FONT-SIZE: 10pt"> gabriel montenegro [mailto:g_=
e_montenegro@yahoo.com] <BR><B>Sent:</B> Tuesday, May 19, 2009 9:39 AM<BR><=
B>To:</B> Samita Chakrabarti; Riegel, Maximilian (NSN - DE/Munich); Wesley =
George<BR><B>Cc:</B> ext Alper Yegin; 16ng@ietf.org<BR><B>Subject:</B> Re: =
[16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft</SPAN></P></DIV></D=
IV>=0A<P class=3DMsoNormal>&nbsp;</P>=0A<DIV>=0A<DIV>=0A<P class=3DMsoNorma=
l><SPAN style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt">I think what =
we need (my intention) is not more details, but less. I agree that there is=
</SPAN></P></DIV>=0A<DIV>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY=
: 'Courier New'; FONT-SIZE: 10pt">some overlap with the WiMAX spec. We shou=
ld simply refer to WiMAX for the WiMAX-specifics, </SPAN></P></DIV>=0A<DIV>=
=0A<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZ=
E: 10pt">and drop the recommendation that WiMAX should adopt this spec. Giv=
en the difference in&nbsp;MTU,</SPAN></P></DIV>=0A<DIV>=0A<P class=3DMsoNor=
mal><SPAN style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt">I won't hol=
d my breath for them to do so, but it's really their business. </SPAN></P><=
/DIV>=0A<DIV>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Courier N=
ew'; FONT-SIZE: 10pt">&nbsp;</SPAN></P>=0A<DIV>=0A<DIV style=3D"TEXT-ALIGN:=
 center" class=3DMsoNormal align=3Dcenter><SPAN style=3D"FONT-FAMILY: 'Taho=
ma', 'sans-serif'; FONT-SIZE: 10pt">=0A<HR align=3Dcenter SIZE=3D1 width=3D=
"100%">=0A</SPAN></DIV>=0A<P style=3D"MARGIN-BOTTOM: 12pt" class=3DMsoNorma=
l><B><SPAN style=3D"FONT-FAMILY: 'Tahoma', 'sans-serif'; FONT-SIZE: 10pt">F=
rom:</SPAN></B><SPAN style=3D"FONT-FAMILY: 'Tahoma', 'sans-serif'; FONT-SIZ=
E: 10pt"> Samita Chakrabarti &lt;samitac@ipinfusion.com&gt;<BR><B>To:</B> "=
Riegel, Maximilian (NSN - DE/Munich)" &lt;maximilian.riegel@nsn.com&gt;; ex=
t Gabriel Montenegro &lt;Gabriel.Montenegro@microsoft.com&gt;; Wesley Georg=
e &lt;wgeorge@sprint.net&gt;<BR><B>Cc:</B> ext Alper Yegin &lt;alper.yegin@=
yegin.org&gt;; 16ng@ietf.org<BR><B>Sent:</B> Monday, May 18, 2009 11:44:47 =
AM<BR><B>Subject:</B> Re: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS=
 draft</SPAN></P>=0A<DIV>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY=
: 'Calibri', 'sans-serif'; FONT-SIZE: 11pt">Hi Max,</SPAN></P>=0A<P class=
=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri', 'sans-serif'; FONT-SIZE=
: 11pt">&nbsp;</SPAN></P>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY=
: 'Calibri', 'sans-serif'; FONT-SIZE: 11pt">As I understand from NWG feedba=
ck that they did not like IETF to recommend 1500 byte MTU size (Appendix se=
ction) for future revision of NWG Wimax specs.&nbsp; Other than that there =
are minor editorial changes that we want to do to polish the draft. </SPAN>=
</P>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri', 'sans-se=
rif'; FONT-SIZE: 11pt">&nbsp;</SPAN></P>=0A<P class=3DMsoNormal><SPAN style=
=3D"FONT-FAMILY: 'Calibri', 'sans-serif'; FONT-SIZE: 11pt">Here is the summ=
ary from NWG feedback:</SPAN></P>=0A<P style=3D"MARGIN-BOTTOM: 12pt" class=
=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">&gt; &gt; In particular the in=
fluence of tunneling inside the network should be<BR>&gt; &gt; carefully di=
scussed.<BR>&gt; &gt; In addition we would kindly ask to either remove whol=
e Appendix C on<BR>&gt; &gt; the WiMAX MTU size or revise the text explaini=
ng the real issues in<BR>&gt; &gt; the WiMAX architecture. In particular th=
e statements on the<BR>&gt; &gt; applicability of the I-D on the WiMAX arch=
itecture and the<BR>&gt; &gt; recommendation on future modifications in the=
 WiMAX architecture seem<BR>&gt; &gt; not to be very appropriate to us.</SP=
AN></P>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri', 'sans=
-serif'; FONT-SIZE: 11pt">What is your suggestion on updating Appendix C? <=
/SPAN></P>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri', 's=
ans-serif'; FONT-SIZE: 11pt">&nbsp;</SPAN></P>=0A<P class=3DMsoNormal><SPAN=
 style=3D"FONT-FAMILY: 'Calibri', 'sans-serif'; FONT-SIZE: 11pt">Thanks,</S=
PAN></P>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri', 'san=
s-serif'; FONT-SIZE: 11pt">-Samita</SPAN></P>=0A<P class=3DMsoNormal><SPAN =
style=3D"FONT-FAMILY: 'Calibri', 'sans-serif'; FONT-SIZE: 11pt">&nbsp;</SPA=
N></P>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Calibri', 'sans-=
serif'; FONT-SIZE: 11pt">&nbsp;</SPAN></P>=0A<DIV style=3D"BORDER-BOTTOM: m=
edium none; BORDER-LEFT: blue 1.5pt solid; PADDING-BOTTOM: 0in; PADDING-LEF=
T: 4pt; PADDING-RIGHT: 0in; BORDER-TOP: medium none; BORDER-RIGHT: medium n=
one; PADDING-TOP: 0in">=0A<DIV>=0A<DIV style=3D"BORDER-BOTTOM: medium none;=
 BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-=
RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDI=
NG-TOP: 3pt">=0A<P class=3DMsoNormal><B><SPAN style=3D"FONT-FAMILY: 'Tahoma=
', 'sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN style=3D"FONT-FAMIL=
Y: 'Tahoma', 'sans-serif'; FONT-SIZE: 10pt"> Riegel, Maximilian (NSN - DE/M=
unich) [mailto:maximilian.riegel@nsn.com] <BR><B>Sent:</B> Monday, May 18, =
2009 12:19 AM<BR><B>To:</B> ext Gabriel Montenegro; Samita Chakrabarti; Wes=
ley George<BR><B>Cc:</B> ext Alper Yegin; 16ng@ietf.org<BR><B>Subject:</B> =
RE: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft</SPAN></P></DIV=
></DIV>=0A<P class=3DMsoNormal>&nbsp;</P>=0A<P class=3DMsoNormal><SPAN styl=
e=3D"FONT-FAMILY: 'Courier New'; COLOR: navy; FONT-SIZE: 10pt">Is there rea=
lly a demand to work on an update of the IPv4-CS I-D?</SPAN></P>=0A<P class=
=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Courier New'; COLOR: navy; FONT-S=
IZE: 10pt">Which details would require/qualify for&nbsp;an IETF specificati=
on?</SPAN></P>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: 'Courier =
New'; COLOR: navy; FONT-SIZE: 10pt">The current architectural model closely=
 resembles the WiMAX architecture, and WiMAX provides a comprehensive speci=
fication for it.</SPAN></P>=0A<P class=3DMsoNormal>&nbsp;</P>=0A<P class=3D=
MsoNormal><SPAN style=3D"FONT-FAMILY: 'Courier New'; COLOR: navy; FONT-SIZE=
: 10pt">Bye</SPAN></P>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: '=
Courier New'; COLOR: navy; FONT-SIZE: 10pt">Max</SPAN></P>=0A<P class=3DMso=
Normal>&nbsp;</P>=0A<DIV style=3D"TEXT-ALIGN: center" class=3DMsoNormal ali=
gn=3Dcenter>=0A<HR align=3Dcenter SIZE=3D3 width=3D"100%">=0A</DIV>=0A<P st=
yle=3D"MARGIN-BOTTOM: 12pt" class=3DMsoNormal><B><SPAN style=3D"FONT-FAMILY=
: 'Tahoma', 'sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN style=3D"F=
ONT-FAMILY: 'Tahoma', 'sans-serif'; FONT-SIZE: 10pt"> ext Gabriel Montenegr=
o [mailto:Gabriel.Montenegro@microsoft.com] <BR><B>Sent:</B> Friday, May 15=
, 2009 8:21 PM<BR><B>To:</B> Samita Chakrabarti; 'Wesley George'; Riegel, M=
aximilian (NSN - DE/Munich)<BR><B>Cc:</B> 'ext Alper Yegin'; 16ng@ietf.org<=
BR><B>Subject:</B> RE: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS dr=
aft</SPAN></P>=0A<DIV>=0A<P class=3DMsoNormal><SPAN style=3D"FONT-FAMILY: '=
Tahoma', 'sans-serif'; COLOR: black; FONT-SIZE: 10pt">yes, I've been delinq=
uently holding to the pen.</SPAN></P></DIV>=0A<DIV>=0A<P class=3DMsoNormal>=
<SPAN style=3D"FONT-FAMILY: 'Tahoma', 'sans-serif'; FONT-SIZE: 10pt">Lets s=
hoot for end of the month at the latest.</SPAN></P></DIV>=0A<DIV id=3DdivRp=
F184309>=0A<DIV style=3D"TEXT-ALIGN: center" class=3DMsoNormal align=3Dcent=
er>=0A<HR align=3Dcenter SIZE=3D3 width=3D"100%">=0A</DIV>=0A<P style=3D"MA=
RGIN-BOTTOM: 12pt" class=3DMsoNormal><B><SPAN style=3D"FONT-FAMILY: 'Tahoma=
', 'sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN style=3D"FONT-FAMIL=
Y: 'Tahoma', 'sans-serif'; FONT-SIZE: 10pt"> Samita Chakrabarti [samitac@ip=
infusion.com]<BR><B>Sent:</B> Friday, May 15, 2009 11:15 AM<BR><B>To:</B> '=
Wesley George'; 'Riegel, Maximilian (NSN - DE/Munich)'<BR><B>Cc:</B> 'ext A=
lper Yegin'; Gabriel Montenegro; 16ng@ietf.org<BR><B>Subject:</B> RE: [16NG=
] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft</SPAN></P></DIV>=0A<DIV>=
=0A<P style=3D"MARGIN-BOTTOM: 12pt" class=3DMsoNormal><SPAN style=3D"FONT-S=
IZE: 10pt">Hi Wes,<BR><BR>Yes, there will be an updated draft before Stockh=
olm. Gabriel was working on<BR>the updates.<BR><BR>I am expecting that we w=
ill soon have a revision to review.<BR><BR>Thanks,<BR>-Samita<BR><BR>&gt; -=
----Original Message-----<BR>&gt; From: 16ng-bounces@ietf.org [<A href=3D"m=
ailto:16ng-bounces@ietf.org" rel=3Dnofollow target=3D_blank ymailto=3D"mail=
to:16ng-bounces@ietf.org">mailto:16ng-bounces@ietf.org</A>] On Behalf Of<BR=
>&gt; Wesley George<BR>&gt; Sent: Friday, May 15, 2009 9:54 AM<BR>&gt; To: =
Riegel, Maximilian (NSN - DE/Munich)<BR>&gt; Cc: ext Alper Yegin; ext Gabri=
el Montenegro; 16ng@ietf.org<BR>&gt; Subject: Re: [16NG] [nwg-chair] NWG fe=
edback on 16ng's IPv4 CS draft<BR>&gt; <BR>&gt; Is someone working on an up=
dated version of this draft to be reviewed in<BR>&gt; Stockholm since we di=
d not meet in SFO? I believe that one of the first<BR>&gt; times that I sub=
mitted
 objections to the MTU language, I provided a<BR>proposed<BR>&gt; text that=
 would cover some of the concerns raised below, not all of which<BR>&gt; wa=
s included in subsequent drafts.<BR>&gt; http://www.ietf.org/mail-archive/w=
eb/16ng/current/msg00824.html<BR>&gt; <BR>&gt; Thanks,<BR>&gt; Wes<BR>&gt; =
<BR>&gt; _________________________________________<BR>&gt;&nbsp;&nbsp;&nbsp=
; Wesley George<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sprint IP=
 Engineering<BR>&gt;&nbsp;&nbsp;&nbsp; 703-689-7505 (O)&nbsp; 703-864-4902 =
(PCS)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; http://=
www.sprint.net/<BR>&gt; _________________________________________<BR>&gt; <=
BR>&gt; <BR>&gt; On Thu, 12 Feb 2009, Riegel, Maximilian (NSN - DE/Munich) =
wrote:<BR>&gt; <BR>&gt; &gt; Gabriel,<BR>&gt; &gt;<BR>&gt; &gt; The WiMAX F=
orum NWG reviewed section 4-3 and Appendix C of<BR>&gt; &gt; draft-ietf-16n=
g-ipv4-over-802-dot-16-ipcs-04.txt and would like to<BR>&gt; &gt;
 make a couple of remarks on the MTU issue:<BR>&gt; &gt;<BR>&gt; &gt; - The=
 I-D is not very clear about the MTU issues appearing in an IPv4<BR>&gt; &g=
t; over IEEE 802.16 transmission system. The ambiguities mainly result<BR>&=
gt; &gt; out of the vague definition of the IEEE 802.16 link comprising bot=
h<BR>&gt; &gt; the radio part of the link as well as the part of the link b=
etween BS<BR>&gt; &gt; and AR, when the functions are located in different =
entities.<BR>&gt; &gt;<BR>&gt; &gt; - Section 4.3 in particular misses the =
discussion of the dependencies<BR>&gt; &gt; between MTU size and the tunnel=
ing protocol deployed between BS and AR.<BR>&gt; &gt;<BR>&gt; &gt; - Sectio=
n 4.3 also misses, that there is no packet loss when the MTU<BR>&gt; &gt; s=
ize limitation is caused by the encapsulation overhead on the link<BR>&gt; =
&gt; between BS and AR. E.g. when GRE is used for the tunnel between BS and=
<BR>&gt; &gt; AR, the transport IP layer can fragment the GRE
 packets to fit the<BR>&gt; &gt; transport MTU on the link between BS and A=
R. Reassembly in the tunnel<BR>&gt; &gt; endpoint at the AR will re-establi=
sh the original user IP packet.<BR>&gt; &gt;<BR>&gt; &gt; - Please note tha=
t the reason of the WiMAX NWG to limit the MTU going<BR>&gt; &gt; over IPv4=
-CS to 1400 Bytes was to avoid fragmentation on the link<BR>&gt; &gt; betwe=
en BS and ASN-GW as well as on the link between ASN-GW and CSN<BR>&gt; &gt;=
 (MIP tunnel). Fragmentation and re-assembly require considerable<BR>&gt; &=
gt; processing power in the network elements.<BR>&gt; &gt;<BR>&gt; &gt; - A=
ppendix C makes statements which would require more detailed review<BR>&gt;=
 &gt; of the I-D by WiMAX NWG. In particular 'The addressing and operation<=
BR>&gt; &gt; of IPv4-CS described in this document are applicable to the Wi=
MAX<BR>&gt; &gt; networks as well' has not been verified yet.<BR>&gt; &gt; =
Furthermore 'Thus, WiMAX MS nodes should use this default (1400)
 MTU<BR>&gt; &gt; value per the current specification [WMF].&nbsp; However,=
 due to reasons<BR>&gt; &gt; specified in section 4.3 above, it is strongly=
 recommended that future<BR>&gt; &gt; WiMAX MS nodes support a default MTU =
of 1500 bytes, and that they<BR>&gt; &gt; implement MTU negotiation capabil=
ities as mentioned in this document.'<BR>&gt; &gt; makes recommendations to=
 WiMAX without understanding the real reasons<BR>&gt; &gt; for the limitati=
on of the MTU size in Mobile WiMAX.<BR>&gt; &gt;<BR>&gt; &gt; We would reco=
mmend to 16ng to revise the sections on MTU size to<BR>&gt; &gt; better exp=
lain the underlying issues leading to restrictions in the MTU<BR>&gt; size.=
<BR>&gt; &gt; In particular the influence of tunneling inside the network s=
hould be<BR>&gt; &gt; carefully discussed.<BR>&gt; &gt; In addition we woul=
d kindly ask to either remove whole Appendix C on<BR>&gt; &gt; the WiMAX MT=
U size or revise the text explaining the real issues in<BR>&gt; &gt;
 the WiMAX architecture. In particular the statements on the<BR>&gt; &gt; a=
pplicability of the I-D on the WiMAX architecture and the<BR>&gt; &gt; reco=
mmendation on future modifications in the WiMAX architecture seem<BR>&gt; &=
gt; not to be very appropriate to us.<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt=
; Bye<BR>&gt; &gt; Max<BR>&gt; &gt; Vize Chair NWG<BR>&gt; &gt;<BR>&gt; &gt=
;<BR>&gt; &gt; ________________________________<BR>&gt; &gt;<BR>&gt; &gt; F=
rom: ext Gabriel Montenegro [<A href=3D"mailto:Gabriel.Montenegro@microsoft=
.com" rel=3Dnofollow target=3D_blank ymailto=3D"mailto:Gabriel.Montenegro@m=
icrosoft.com">mailto:Gabriel.Montenegro@microsoft.com</A>]<BR>&gt; &gt; Sen=
t: Monday, November 03, 2008 11:59 AM<BR>&gt; &gt; To: nwg-chair@list.wimax=
forum.org<BR>&gt; &gt; Cc: 'Daniel Soohong Park'<BR>&gt; &gt; Subject: [nwg=
-chair] NWG feedback on 16ng's IPv4 CS draft<BR>&gt; &gt;<BR>&gt; &gt;<BR>&=
gt; &gt;<BR>&gt; &gt; Prakash, Max and Yong Chang,<BR>&gt; &gt;<BR>&gt;
 &gt;<BR>&gt; &gt; The IETF 16ng WG has published a revision of this draft:=
<BR>&gt; &gt;<BR>&gt; &gt; "Transmission of IPv4 packets over IEEE 802.16's=
 IP Convergence<BR>&gt; &gt; Sublayer"<BR>&gt; &gt;<BR>&gt; &gt; Per this a=
nnouncement:<BR>&gt; &gt;<BR>&gt; &gt; http://www.ietf.org/mail-archive/web=
/16ng/current/msg00863.html<BR>&gt; &gt; &lt;<A href=3D"http://www.ietf.org=
/mail-archive/web/16ng/current/msg00863.html" rel=3Dnofollow target=3D_blan=
k>http://www.ietf.org/mail-archive/web/16ng/current/msg00863.html</A>&gt;<B=
R>&gt; &gt;<BR>&gt; &gt; We understand that this specification currently is=
 not normative to<BR>&gt; &gt; NWG (as opposed to RFC5121 on IPv6 CS). Neve=
rtheless, given its<BR>&gt; &gt; relevance, and with the hope it may become=
 normative to NWG in some<BR>&gt; &gt; future revision, the 16ng WG would l=
ike to solicit feedback from NWG<BR>&gt; &gt; on this draft.<BR>&gt; &gt;<B=
R>&gt; &gt; In particular, please note that this draft specifies a default
 MTU of<BR>&gt; &gt; 1500,&nbsp; which is different from the WiMAX-specifie=
d MTU of 1400 (per<BR>&gt; &gt; the recently approved R1_V1.3.0-Stage-3&nbs=
p; NWG specifications).&nbsp; For MTU<BR>&gt; &gt; discussion, please refer=
 to these sections:<BR>&gt; &gt;<BR>&gt; &gt; http://tools.ietf.org/html/dr=
aft-ietf-16ng-ipv4-over-802-dot-16-ipcs-0<BR>&gt; &gt; 4#<BR>&gt; &gt; sect=
ion-4.3<BR>&gt; &gt; &lt;http://tools.ietf.org/html/draft-ietf-16ng-ipv4-ov=
er-802-dot-16-ipcs-<BR>&gt; &gt; 04<BR>&gt; &gt; #section-4.3&gt;<BR>&gt; &=
gt; <A href=3D"http://tools.ietf.org/html/draft-ietf-16ng-ipv4-over-802-dot=
-16-ipcs-0" rel=3Dnofollow target=3D_blank>http://tools.ietf.org/html/draft=
-ietf-16ng-ipv4-over-802-dot-16-ipcs-0</A><BR>&gt; &gt; 4#<BR>&gt; &gt; app=
endix-C<BR>&gt; &gt; &lt;<A href=3D"http://tools.ietf.org/html/draft-ietf-1=
6ng-ipv4-over-802-dot-16-ipcs-" rel=3Dnofollow target=3D_blank>http://tools=
.ietf.org/html/draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-</A><BR>&gt; &gt;
 04<BR>&gt; &gt; #appendix-C&gt;<BR>&gt; &gt;<BR>&gt; &gt; The 16ng WG will=
 next meet on Nov 18 during the IETF in Minneapolis<BR>&gt; &gt; (<A href=
=3D"https://datatracker.ietf.org/meeting/73/agenda.html" rel=3Dnofollow tar=
get=3D_blank>https://datatracker.ietf.org/meeting/73/agenda.html</A>). If a=
t all<BR>&gt; &gt; possible, it would be best if comments were received bef=
ore that date<BR>&gt; &gt; in order for the WG to discuss them during the m=
eeting.<BR>&gt; &gt;<BR>&gt; &gt; Please send your comments to the 16ng@iet=
f.org &lt;<A href=3D"mailto:16ng@ietf.org" rel=3Dnofollow target=3D_blank y=
mailto=3D"mailto:16ng@ietf.org">mailto:16ng@ietf.org</A>&gt;<BR>&gt; &gt; m=
ailing list.<BR>&gt; &gt;<BR>&gt; &gt; Thanks,<BR>&gt; &gt;<BR>&gt; &gt; Ga=
briel and Daniel<BR>&gt; &gt; 16ng co-chairs<BR>&gt; &gt;<BR>&gt; &gt;<BR>&=
gt; &gt;<BR>&gt; &gt;<BR>&gt; _____________________________________________=
__<BR>&gt; 16NG mailing list<BR>&gt; 16NG@ietf.org<BR>&gt; <A
 href=3D"https://www.ietf.org/mailman/listinfo/16ng" rel=3Dnofollow target=
=3D_blank>https://www.ietf.org/mailman/listinfo/16ng</A><BR><BR><BR></SPAN>=
</P></DIV></DIV></DIV></DIV></DIV></DIV></DIV></DIV></DIV></DIV></DIV></DIV=
></DIV></div></body></html>
--0-1809340865-1244048992=:22436--

From wgeorge@sprint.net  Thu Jun  4 06:25:34 2009
Return-Path: <wgeorge@sprint.net>
X-Original-To: 16ng@core3.amsl.com
Delivered-To: 16ng@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D4BD228C11B for <16ng@core3.amsl.com>; Thu,  4 Jun 2009 06:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fdce2XeEUxii for <16ng@core3.amsl.com>; Thu,  4 Jun 2009 06:25:32 -0700 (PDT)
Received: from jay.sprintlink.net (jay.sprintlink.net [199.0.233.7]) by core3.amsl.com (Postfix) with ESMTP id D5F5D28C101 for <16ng@ietf.org>; Thu,  4 Jun 2009 06:25:31 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApsEAGRnJ0rHAO3C/2dsb2JhbACODrFhCZAuglaBNgU
X-IronPort-AV: E=Sophos;i="4.41,305,1241409600"; d="scan'208";a="25532205"
Received: from iscone.res.sprintlink.net (HELO tin.res.sprintlink.net) ([199.0.237.194]) by jay.sprintlink.net with ESMTP; 04 Jun 2009 09:17:47 -0400
Received: from tin.res.sprintlink.net (localhost [127.0.0.1]) by tin.res.sprintlink.net (8.13.7+Sun/8.13.7) with ESMTP id n54DOc8s027765; Thu, 4 Jun 2009 09:24:38 -0400 (EDT)
Received: from localhost (wgeorge@localhost) by tin.res.sprintlink.net (8.13.7+Sun/8.13.7/Submit) with ESMTP id n54DObbG027761; Thu, 4 Jun 2009 09:24:37 -0400 (EDT)
X-Authentication-Warning: tin.res.sprintlink.net: wgeorge owned process doing -bs
Date: Thu, 4 Jun 2009 09:24:37 -0400 (EDT)
From: Wesley George <wgeorge@sprint.net>
X-X-Sender: wgeorge@tin
To: gabriel montenegro <g_e_montenegro@yahoo.com>
In-Reply-To: <570230.22436.qm@web82606.mail.mud.yahoo.com>
Message-ID: <Pine.GSO.4.64.0906040915000.16060@tin>
References: <2828BDE8DC61004E8104C78E82A0B39710B25385F2@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com><BC27158B99D3064A955ADE084783900C01B5CBC8@DEMUEXC014.nsn-intra.net> <Pine.GSO.4.64.0905151247200.12703@tin>, <046201c9d589$267cf8d0$7376ea70$@com> <BAA9BC6C-6B59-4BA6-B63D-E09C26E0194B@mimectl> <BC27158B99D3064A955ADE084783900C020F18E5@DEMUEXC014.nsn-intra.net> <056601c9d7e8$b8be17e0$2a3a47a0$@com> <556994.50253.qm@web82604.mail.mud.yahoo.com> <06ab01c9d8cd$079cc660$16d65320$@com> <BC27158B99D3064A955ADE084783900C020F26B5@DEMUEXC014.nsn-intra.net> <916575.77425.qm@web82607.mail.mud.yahoo.com> <570230.22436.qm@web82606.mail.mud.yahoo.com>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-126398554-1244121307=:16060"
Content-ID: <Pine.GSO.4.64.0906040915290.16060@tin>
Cc: ext Alper Yegin <alper.yegin@yegin.org>, 16ng@ietf.org
Subject: Re: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2009 13:25:34 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---559023410-126398554-1244121307=:16060
Content-Type: TEXT/PLAIN; CHARSET=X-UNKNOWN; FORMAT=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-ID: <Pine.GSO.4.64.0906040915291.16060@tin>

Gabriel - this looks good to me. The only point/recommendation I might
make for the MTU section is that currently, it focuses only on solutions
that enable the End Host to determine or be advised of the path MTU. It
would be good to also recommend something regarding the underlying network
between the MS and the BS.
What I mean by this is, if the implementor of the 802.16 network either
knows or has control over the MTU of the transport method between the BS
and the MS, they should be able to either set the MTU on the transport
network so that it is higher than 1500 + any encapsulation overhead, or
ensure that it fragments larger PDUs properly. Obviously, the latter will
not work if the DF bit is set, so perhaps we leave out the discussion of
fragmentation altogether, but I do think it's worth mentioning that
raising the MTU of the transport network is a viable alternative to using
some means to communicate a non-default MTU to the MS.

Perhaps right before "Some of the mechanisms..." you could add
something like this:

With an end host MTU of 1500 bytes, the underlying network between the=20
BS and the MS MUST support an MTU of at least 1500 bytes plus the overhead=
=20
of any chosen encapsulation method between the BS and MS.=20
For ease of standardization, the underlying network SHOULD support an MTU=
=20
of at least 100 bytes larger than the chosen host MTU value, as this is=20
large enough to ensure that there is no dropping or fragmentation of=20
oversize packets regardless of the encapsulation method.
If it is not possible to change the MTU of the network segments between=20
the BS and the MS, then a lower-than-default MTU must be used and=20
communicated to the IPv4 CS host.

(then, "Some of the mechanisms available...")

Thanks,
Wes

_________________________________________
   Wesley George
 =09Sprint IP Engineering
   703-689-7505 (O)  703-864-4902 (PCS)
         http://www.sprint.net
_________________________________________


On Wed, 3 Jun 2009, gabriel montenegro wrote:

> The new rev has appeared:
http://tools.ietf.org/html/draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05

This is a summary of changes:

Editorial changes throughout.

Got rid of all mention of WiMAX in the main text.

Section 3 on network architecture: deleted much text, instead referring to =
the
relevant sections in IEEE802.16, 5121 and 5154. No need to repeat text that=
 appears=20
elsewhere.

Section 4.3 on MTU: simplified to say not much more than RFC5121 says.

Section 6 on handling multicast. Got rid of it. It repeats stuff already in
both 5.3 and 5.1.

Appendix on WiMAX MTU.
Got rid of:
=A0=A0 The addressing and operation of IPv4 CS described in this
=A0=A0 document are applicable to the WiMAX networks as well.=A0
Got rid of recommendation that WiMAX adopt this specification.

But your favorite diff tool is your best bet, e.g.:

http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-16ng-ipv4-over-802-dot-16-i=
pcs-05.txt

Please look it over. Hopefully, the remaining issues are manageable and les=
s in number.

thanks,

Gabriel



________________________________
From: gabriel montenegro <g_e_montenegro@yahoo.com>
To: "Riegel, Maximilian (NSN - DE/Munich)" <maximilian.riegel@nsn.com>; ext=
 Samita Chakrabarti <samitac@ipinfusion.com>; Wesley George <wgeorge@sprint=
=2Enet>
Cc: ext Alper Yegin <alper.yegin@yegin.org>; 16ng@ietf.org
Sent: Wednesday, May 20, 2009 8:41:46 AM
Subject: Re: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft


Let's wait till the next version appears (ETA: end of this month) as hopefu=
lly that version
will require less fixes.




________________________________
From: "Riegel, Maximilian (NSN - DE/Munich)" <maximilian.riegel@nsn.com>
To: ext Samita Chakrabarti <samitac@ipinfusion.com>; gabriel montenegro <g_=
e_montenegro@yahoo.com>; Wesley George <wgeorge@sprint.net>
Cc: ext Alper Yegin <alper.yegin@yegin.org>; 16ng@ietf.org
Sent: Wednesday, May 20, 2009 2:11:31 AM
Subject: Re: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft


My point is not the MTU size, I am concerned about the quality of the curre=
nt document. There are=A0a number of=A0ambiguities and misconceptions, whic=
h would require some efforts for resolving. I once did an approach to creat=
e a submission to the mailing list and gave up after an hour seeing that it=
 requires more=A0text to explain the issues in the document than just rephr=
asing the text.
=A0
Would it be possible to held a conference call to discuss the readiness of =
the IPv4-CS I-D?
=A0
Bye
Max


________________________________
From: ext Samita Chakrabarti [mailto:samitac@ipinfusion.com]=20
Sent: Tuesday, May 19, 2009 11:59 PM
To: 'gabriel montenegro'; Riegel, Maximilian (NSN - DE/Munich); 'Wesley Geo=
rge'
Cc: 'ext Alper Yegin'; 16ng@ietf.org
Subject: RE: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft


Agreed.=20
Default MTU is 1500 =A0- if WiMAX does not want to update their SPEC or doe=
s not want to conform to this IETF draft, it is SDO business. Thus we can m=
ove forward =A0independently.
=A0
Thanks,
-Samita
=A0
From:gabriel montenegro [mailto:g_e_montenegro@yahoo.com]=20
Sent: Tuesday, May 19, 2009 9:39 AM
To: Samita Chakrabarti; Riegel, Maximilian (NSN - DE/Munich); Wesley George
Cc: ext Alper Yegin; 16ng@ietf.org
Subject: Re: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft
=A0
I think what we need (my intention) is not more details, but less. I agree =
that there is
some overlap with the WiMAX spec. We should simply refer to WiMAX for the W=
iMAX-specifics,=20
and drop the recommendation that WiMAX should adopt this spec. Given the di=
fference in=A0MTU,
I won't hold my breath for them to do so, but it's really their business.=
=20
=A0

________________________________

From:Samita Chakrabarti <samitac@ipinfusion.com>
To: "Riegel, Maximilian (NSN - DE/Munich)" <maximilian.riegel@nsn.com>; ext=
 Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>; Wesley George <wgeo=
rge@sprint.net>
Cc: ext Alper Yegin <alper.yegin@yegin.org>; 16ng@ietf.org
Sent: Monday, May 18, 2009 11:44:47 AM
Subject: Re: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft
Hi Max,
=A0
As I understand from NWG feedback that they did not like IETF to recommend =
1500 byte MTU size (Appendix section) for future revision of NWG Wimax spec=
s.=A0 Other than that there are minor editorial changes that we want to do =
to polish the draft.=20
=A0
Here is the summary from NWG feedback:
> > In particular the influence of tunneling inside the network should be
> > carefully discussed.
> > In addition we would kindly ask to either remove whole Appendix C on
> > the WiMAX MTU size or revise the text explaining the real issues in
> > the WiMAX architecture. In particular the statements on the
> > applicability of the I-D on the WiMAX architecture and the
> > recommendation on future modifications in the WiMAX architecture seem
> > not to be very appropriate to us.
What is your suggestion on updating Appendix C?=20
=A0
Thanks,
-Samita
=A0
=A0
From:Riegel, Maximilian (NSN - DE/Munich) [mailto:maximilian.riegel@nsn.com=
]=20
Sent: Monday, May 18, 2009 12:19 AM
To: ext Gabriel Montenegro; Samita Chakrabarti; Wesley George
Cc: ext Alper Yegin; 16ng@ietf.org
Subject: RE: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft
=A0
Is there really a demand to work on an update of the IPv4-CS I-D?
Which details would require/qualify for=A0an IETF specification?
The current architectural model closely resembles the WiMAX architecture, a=
nd WiMAX provides a comprehensive specification for it.
=A0
Bye
Max
=A0

________________________________

From:ext Gabriel Montenegro [mailto:Gabriel.Montenegro@microsoft.com]=20
Sent: Friday, May 15, 2009 8:21 PM
To: Samita Chakrabarti; 'Wesley George'; Riegel, Maximilian (NSN - DE/Munic=
h)
Cc: 'ext Alper Yegin'; 16ng@ietf.org
Subject: RE: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft
yes, I've been delinquently holding to the pen.
Lets shoot for end of the month at the latest.

________________________________

From:Samita Chakrabarti [samitac@ipinfusion.com]
Sent: Friday, May 15, 2009 11:15 AM
To: 'Wesley George'; 'Riegel, Maximilian (NSN - DE/Munich)'
Cc: 'ext Alper Yegin'; Gabriel Montenegro; 16ng@ietf.org
Subject: RE: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft
Hi Wes,

Yes, there will be an updated draft before Stockholm. Gabriel was working o=
n
the updates.

I am expecting that we will soon have a revision to review.

Thanks,
-Samita

> -----Original Message-----
> From: 16ng-bounces@ietf.org [mailto:16ng-bounces@ietf.org] On Behalf Of
> Wesley George
> Sent: Friday, May 15, 2009 9:54 AM
> To: Riegel, Maximilian (NSN - DE/Munich)
> Cc: ext Alper Yegin; ext Gabriel Montenegro; 16ng@ietf.org
> Subject: Re: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft
>=20
> Is someone working on an updated version of this draft to be reviewed in
> Stockholm since we did not meet in SFO? I believe that one of the first
> times that I submitted objections to the MTU language, I provided a
proposed
> text that would cover some of the concerns raised below, not all of which
> was included in subsequent drafts.
> http://www.ietf.org/mail-archive/web/16ng/current/msg00824.html
>=20
> Thanks,
> Wes
>=20
> _________________________________________
>=A0=A0=A0 Wesley George
>=A0=A0=A0=A0=A0=A0=A0 Sprint IP Engineering
>=A0=A0=A0 703-689-7505 (O)=A0 703-864-4902 (PCS)
>=A0=A0=A0=A0=A0=A0=A0=A0=A0 http://www.sprint.net/
> _________________________________________
>=20
>=20
> On Thu, 12 Feb 2009, Riegel, Maximilian (NSN - DE/Munich) wrote:
>=20
> > Gabriel,
> >
> > The WiMAX Forum NWG reviewed section 4-3 and Appendix C of
> > draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-04.txt and would like to
> > make a couple of remarks on the MTU issue:
> >
> > - The I-D is not very clear about the MTU issues appearing in an IPv4
> > over IEEE 802.16 transmission system. The ambiguities mainly result
> > out of the vague definition of the IEEE 802.16 link comprising both
> > the radio part of the link as well as the part of the link between BS
> > and AR, when the functions are located in different entities.
> >
> > - Section 4.3 in particular misses the discussion of the dependencies
> > between MTU size and the tunneling protocol deployed between BS and AR.
> >
> > - Section 4.3 also misses, that there is no packet loss when the MTU
> > size limitation is caused by the encapsulation overhead on the link
> > between BS and AR. E.g. when GRE is used for the tunnel between BS and
> > AR, the transport IP layer can fragment the GRE packets to fit the
> > transport MTU on the link between BS and AR. Reassembly in the tunnel
> > endpoint at the AR will re-establish the original user IP packet.
> >
> > - Please note that the reason of the WiMAX NWG to limit the MTU going
> > over IPv4-CS to 1400 Bytes was to avoid fragmentation on the link
> > between BS and ASN-GW as well as on the link between ASN-GW and CSN
> > (MIP tunnel). Fragmentation and re-assembly require considerable
> > processing power in the network elements.
> >
> > - Appendix C makes statements which would require more detailed review
> > of the I-D by WiMAX NWG. In particular 'The addressing and operation
> > of IPv4-CS described in this document are applicable to the WiMAX
> > networks as well' has not been verified yet.
> > Furthermore 'Thus, WiMAX MS nodes should use this default (1400) MTU
> > value per the current specification [WMF].=A0 However, due to reasons
> > specified in section 4.3 above, it is strongly recommended that future
> > WiMAX MS nodes support a default MTU of 1500 bytes, and that they
> > implement MTU negotiation capabilities as mentioned in this document.'
> > makes recommendations to WiMAX without understanding the real reasons
> > for the limitation of the MTU size in Mobile WiMAX.
> >
> > We would recommend to 16ng to revise the sections on MTU size to
> > better explain the underlying issues leading to restrictions in the MTU
> size.
> > In particular the influence of tunneling inside the network should be
> > carefully discussed.
> > In addition we would kindly ask to either remove whole Appendix C on
> > the WiMAX MTU size or revise the text explaining the real issues in
> > the WiMAX architecture. In particular the statements on the
> > applicability of the I-D on the WiMAX architecture and the
> > recommendation on future modifications in the WiMAX architecture seem
> > not to be very appropriate to us.
> >
> >
> > Bye
> > Max
> > Vize Chair NWG
> >
> >
> > ________________________________
> >
> > From: ext Gabriel Montenegro [mailto:Gabriel.Montenegro@microsoft.com]
> > Sent: Monday, November 03, 2008 11:59 AM
> > To: nwg-chair@list.wimaxforum.org
> > Cc: 'Daniel Soohong Park'
> > Subject: [nwg-chair] NWG feedback on 16ng's IPv4 CS draft
> >
> >
> >
> > Prakash, Max and Yong Chang,
> >
> >
> > The IETF 16ng WG has published a revision of this draft:
> >
> > "Transmission of IPv4 packets over IEEE 802.16's IP Convergence
> > Sublayer"
> >
> > Per this announcement:
> >
> > http://www.ietf.org/mail-archive/web/16ng/current/msg00863.html
> > <http://www.ietf.org/mail-archive/web/16ng/current/msg00863.html>
> >
> > We understand that this specification currently is not normative to
> > NWG (as opposed to RFC5121 on IPv6 CS). Nevertheless, given its
> > relevance, and with the hope it may become normative to NWG in some
> > future revision, the 16ng WG would like to solicit feedback from NWG
> > on this draft.
> >
> > In particular, please note that this draft specifies a default MTU of
> > 1500,=A0 which is different from the WiMAX-specified MTU of 1400 (per
> > the recently approved R1_V1.3.0-Stage-3=A0 NWG specifications).=A0 For =
MTU
> > discussion, please refer to these sections:
> >
> > http://tools.ietf.org/html/draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-0
> > 4#
> > section-4.3
> > <http://tools.ietf.org/html/draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-
> > 04
> > #section-4.3>
> > http://tools.ietf.org/html/draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-0
> > 4#
> > appendix-C
> > <http://tools.ietf.org/html/draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-
> > 04
> > #appendix-C>
> >
> > The 16ng WG will next meet on Nov 18 during the IETF in Minneapolis
> > (https://datatracker.ietf.org/meeting/73/agenda.html). If at all
> > possible, it would be best if comments were received before that date
> > in order for the WG to discuss them during the meeting.
> >
> > Please send your comments to the 16ng@ietf.org <mailto:16ng@ietf.org>
> > mailing list.
> >
> > Thanks,
> >
> > Gabriel and Daniel
> > 16ng co-chairs
> >
> >
> >
> >
> _______________________________________________
> 16NG mailing list
> 16NG@ietf.org
> https://www.ietf.org/mailman/listinfo/16ng
---559023410-126398554-1244121307=:16060--

From maximilian.riegel@nsn.com  Thu Jun  4 15:50:37 2009
Return-Path: <maximilian.riegel@nsn.com>
X-Original-To: 16ng@core3.amsl.com
Delivered-To: 16ng@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E9613A6AE0 for <16ng@core3.amsl.com>; Thu,  4 Jun 2009 15:50:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.799
X-Spam-Level: 
X-Spam-Status: No, score=-4.799 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_43=0.6, J_CHICKENPOX_45=0.6, J_CHICKENPOX_63=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2fFrjoLx0U2R for <16ng@core3.amsl.com>; Thu,  4 Jun 2009 15:50:34 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [217.115.75.233]) by core3.amsl.com (Postfix) with ESMTP id 145293A681C for <16ng@ietf.org>; Thu,  4 Jun 2009 15:50:32 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id n54MoXSX004895 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 5 Jun 2009 00:50:33 +0200
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id n54MoWvW021367; Fri, 5 Jun 2009 00:50:32 +0200
Received: from DEMUEXC014.nsn-intra.net ([10.150.128.25]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 5 Jun 2009 00:50:08 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 5 Jun 2009 00:50:09 +0200
Message-ID: <BC27158B99D3064A955ADE084783900C021E70E1@DEMUEXC014.nsn-intra.net>
In-Reply-To: <20090603154501.B0C963A6CBB@core3.amsl.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [16NG] I-D Action:draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05.txt
Thread-Index: AcnkYn5oQw46mIdPQamkrbG7pFW1sQBAi7vg
References: <20090603154501.B0C963A6CBB@core3.amsl.com>
From: "Riegel, Maximilian (NSN - DE/Munich)" <maximilian.riegel@nsn.com>
To: <16ng@ietf.org>
X-OriginalArrivalTime: 04 Jun 2009 22:50:08.0693 (UTC) FILETIME=[CF77CE50:01C9E566]
Cc: ext Alper Yegin <alper.yegin@yegin.org>, ext gabriel montenegro <g_e_montenegro@yahoo.com>
Subject: Re: [16NG] I-D Action:draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05.txt
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2009 22:50:37 -0000

I went through the document and found a couple of issues, which I would
like to see in a better shape.
Please find my comments inline:

Bye
Max

> 16ng Working Group                                        S.
Madanapalli
> Internet-Draft                                        Ordyn
Technologies
> Intended status: Standards Track                         Soohong D.
Park
> Expires: April 4, 2009                               Samsung
Electronics
>                                                           S.
Chakrabarti
>                                                              IP
Infusion
>                                                            G.
Montenegro
>                                                    Microsoft
Corporation
>                                                             October
2008
>=20
>=20
> Transmission of IPv4 packets over IEEE 802.16's IP Convergence
Sublayer
>             draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05.txt
>=20
> Status of this Memo
>=20
>    By submitting this Internet-Draft, each author represents that any
>    applicable patent or other IPR claims of which he or she is aware
>    have been or will be disclosed, and any of which he or she becomes
>    aware will be disclosed, in accordance with Section 6 of BCP 79.
>=20
>    Internet-Drafts are working documents of the Internet Engineering
>    Task Force (IETF), its areas, and its working groups.  Note that
>    other groups may also distribute working documents as Internet-
>    Drafts.
>=20
>    Internet-Drafts are draft documents valid for a maximum of six
months
>    and may be updated, replaced, or obsoleted by other documents at
any
>    time.  It is inappropriate to use Internet-Drafts as reference
>    material or to cite them other than as "work in progress."
>=20
>    The list of current Internet-Drafts can be accessed at
>    http://www.ietf.org/ietf/1id-abstracts.txt.
>=20
>    The list of Internet-Draft Shadow Directories can be accessed at
>    http://www.ietf.org/shadow.html.
>=20
>    This Internet-Draft will expire on April 4, 2009.
>=20
> Abstract
>=20
>    IEEE 802.16 is an air interface specification for wireless
broadband
>    access.  IEEE 802.16 has specified multiple service specific
>    convergence sublayers for transmitting upper layer protocols.  The
>    packet CS (Packet Convergence Sublayer) is used for the transport
of
>    all packet-based protocols such as Internet Protocol (IP), IEEE
802.3
>    (Ethernet) and IEEE 802.1Q (VLAN).  The IP-specific part of the

Meanwhile the IEEE802.16-2009 (was REV2) specification has been
released.
IEEE802.16-2009 does not know anymore about the IEEE 802.1Q (VLAN) CS.

>    Packet CS enables the transport of IPv4 packets directly over the
>=20
>=20
>=20
> Madanapalli, et al.       Expires April 4, 2009                 [Page
1]
> =0C
> Internet-Draft        IPv4 over IEEE 802.16's IP CS         October
2008
>=20
>=20
>    IEEE 802.16 MAC.
>=20
>    This document specifies the frame format, the Maximum Transmission
>    Unit (MTU) and address assignment procedures for transmitting IPv4
>    packets over the IP-specific part of the Packet Convergence
Sublayer
>    of IEEE 802.16.
>=20
>=20
> Table of Contents
>=20
>    1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .
3
>    2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .
3
>    3.  Typical Network Architecture for IPv4 over IEEE 802.16 . . . .
3
>      3.1.  IEEE 802.16 IPv4 Convergence sub-layer support . . . . . .
3
>    4.  IPv4 CS link in 802.16 Networks  . . . . . . . . . . . . . . .
4
>      4.1.  IPv4 CS link establishment . . . . . . . . . . . . . . . .
4
>      4.2.  Frame Format for IPv4 Packets  . . . . . . . . . . . . . .
4
>      4.3.  Maximum Transmission Unit  . . . . . . . . . . . . . . . .
5
>    5.  Subnet Model and IPv4 Address Assignment . . . . . . . . . . .
7
>      5.1.  IPv4 Unicast Address Assignment and Router Discovery . . .
7
>      5.2.  Address Resolution Protocol  . . . . . . . . . . . . . . .
8
>      5.3.  IP Multicast Address Mapping . . . . . . . . . . . . . . .
8
>    6.  Security Considerations  . . . . . . . . . . . . . . . . . . .
8
>    7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .
8
>    8.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .
8
>    9.  References . . . . . . . . . . . . . . . . . . . . . . . . . .
9
>      9.1.  Normative References . . . . . . . . . . . . . . . . . . .
9
>      9.2.  Informative References . . . . . . . . . . . . . . . . . .
9
>    Appendix A.  Multiple Convergence Layers - Impact on Subnet
>                 Model . . . . . . . . . . . . . . . . . . . . . . . .
10
>    Appendix B.  Sending and Receiving IPv4 Packets  . . . . . . . . .
10
>    Appendix C.  WiMAX IPCS MTU size . . . . . . . . . . . . . . . . .
11
>    Appendix D.  Thoughts on handling multicast-broadcast IP
>                 packets . . . . . . . . . . . . . . . . . . . . . . .
12
>    Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .
12
>    Intellectual Property and Copyright Statements . . . . . . . . . .
14
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> Madanapalli, et al.       Expires April 4, 2009                 [Page
2]
>=20
> Internet-Draft        IPv4 over IEEE 802.16's IP CS         October
2008
>=20
>=20
> 1.  Introduction
>=20
>    IEEE 802.16 [IEEE802_16] is a connection oriented access technology
>    for the last mile.  The IEEE 802.16 specification includes the PHY
>    and MAC layers.  The MAC includes various convergence sublayers
(CS)
>    for transmitting higher layer packets including IPv4 packets
>    [RFC5154].
>=20
>    The scope of this specification is limited to the operation of IPv4
>    over the IP-specific part of the packet CS (referred to as "IPv4
CS"
>    or simply "IP CS" in this document).

IPv4 CS should be used throughout the document to prevent mixing it up
with the IPv6 CS specification. There is nothing like IP CS in the
IEEE802.16 specification, there is only IPv4 CS and IPv6 CS.
BTW: there is now a single ETH CS carrying IPv4 as well as IPv6 payload.

>    This document specifies a method for encapsulating and transmitting
>    IPv4 [RFC0791] packets over the IP CS of IEEE 802.16.  This
document
                                     ^IPv4 CS
>    also specifies the MTU and address assignment method for the IEEE

Which MTU, which address assignment? More concise wording would help.

>    802.16 based networks using IP CS.
                                 ^IPv4 CS
>=20
>    This document also discusses ARP (Address Resolution Protocol) and
>    Multicast Address Mapping whose operation is similar to any other
>    point-to-point link model.

What do you mean with this sentence?

>    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this
>    document are to be interpreted as described in [RFC2119].
>=20
>=20
> 2.  Terminology
>=20
>    The terminology in this document is based on the definitions in
>    [RFC5154].
>=20
>=20
> 3.  Typical Network Architecture for IPv4 over IEEE 802.16
>=20
>    The network architecture follows what is described in [RFC5154] and
>    [RFC5121].  In a nutshell, each MS is attached to an Access Router

Please clarify 'MS'; according to IEEE802.16 it only covers PHY and MAC.
According to IEEE802.16 the MS is not a 'host'.

>    (AR) through a Base Station (BS), a layer 2 entity (from the
>    perspective of the IPv6 link between the MS and access router
(AR)).
                        ^IPv4??? Copy&Paste mistake?
>=20
>    For further information on the typical network architecture, see
>    [RFC5121] section 5.
>=20
> 3.1.  IEEE 802.16 IPv4 Convergence sub-layer support
>=20
>    As described in [RFC5154] section 3.3., an IP specific subpart
>    classifier carries either IPv4 or IPv6 payloads.  In this document,
>    we are focusing on the IPv4 over IP Convergence Sublayer.

Section 3.3 of [RFC5154] is outdated! IEEE802.16-2009 introduced a
refined CS structure. IMHO, we shouldn't make references to outdated
specifications, but base the work on the most recent IEEE802.16
specification.

>=20
>=20
>=20
>=20
> Madanapalli, et al.       Expires April 4, 2009                 [Page
3]
> =0C
> Internet-Draft        IPv4 over IEEE 802.16's IP CS         October
2008
>=20
>=20
>    For further information on the IEEE 802.16 Convergence Sublayer and
>    encapsulation of IP packets, see [RFC5121] section 4 and [RFC5154]
>    section 3.3.

As [RFC5154] is outdated, I would propose to provide an updated section
3.3. as part of the IPv4 CS document.

> 4.  IPv4 CS link in 802.16 Networks
>=20
>    This document defines the IPv4 CS link as a point-to-point link
>    between the MS and the AR using a set of service flows consisting
of

MS is not the host. What is a link between a L2 device (MS) and a L3
device (AR)?

>    MAC transport connections between a MS and BS, and L2 tunnel(s)
>    between between a BS and AR.  It is recommended that a tunnel be
                                                                   ^is
>    established between the AR and a BS based on 'per MS' or 'per
service
>    flow' (An MS can have multiple service flows each of which are

What is a tunnel between BS and AR based on 'per MS'? It seems, some GRE
functionality is assumed here without spelling it out.

>    identified by a unique service flow ID).  Then the tunnel(s) for an
>    MS, in combination with the MS's MAC transport connections, forms a
>    single point-to-point link.  Each MS belongs to a different link
and

How does this work - multiple tunnels between two endpoints forming a
single link? I would assume, that there must be some classification in
place, which is part of the BS according to IEEE802.16, not part of the
AR, like the authors assume in the sentence.

>    is assigned an unique IPv4 address per recommendations in
[RFC4968].
>=20
>    To summarize:
>=20
>    o  IPv4 CS uses the IPv4 header fields to classify the packets and
>       map to the appropriate CID.

The previous text talks about service flows; why 'CID' is mentioned
here?

>    o  A point-to-point link between MS and AR is established.

How do the two statements fit together? How does IPv4 CS establish a p2p
link?

>=20
> 4.1.  IPv4 CS link establishment
>=20
>    In order to enable the sending and receiving of IPv4 packets
between
>    the MS and the AR, the link between the MS and the AR via the BS
>    needs to be established.  This section explains the link
>    establishment procedures following section 6.2 of [RFC5121].  Steps
>    1-4 are same as indicated in 6.2 of [RFC5121].  In step 5, support
>    for IPv4 is indicated.  In step 6, an initial service flow is
created

Initial service flow? [RFC5121] does not specifies further service
flows.

>    that can be used for exchanging IP layer signaling messages, e.g.
>    address assignment procedures using DHCP.
>=20
>    The address assignment procedure depends on the MS mode - i,e.
>    whether it is acting as a Mobile IPv4 client or a Proxy Mobile IP
>    client or a Simple IP client.  In the most common case, the MS
>    requests an IP address using DHCP.

What is the difference between a Proxy MIP client and a Simple IP
client?
Does the 'MS' request an IP address by DHCP in the case of Client-MIP?

>=20
> 4.2.  Frame Format for IPv4 Packets
>=20
>    IPv4 packets are transmitted in Generic IEEE 802.16 MAC frames in
the
>    data payloads of the 802.16 PDU ( see section 3.2 of [RFC5154] ).
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> Madanapalli, et al.       Expires April 4, 2009                 [Page
4]
> =0C
> Internet-Draft        IPv4 over IEEE 802.16's IP CS         October
2008
>=20
>=20
>                         0                   1
>                         0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
>                        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                        |H|E|   TYPE    |R|C|EKS|R|LEN  |
>                        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                        |    LEN LSB    |    CID MSB    |
>                        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                        |    CID LSB    |    HCS        |
>                        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                        |             IPv4              |
>                        +-                             -+
>                        |            header             |
>                        +-                             -+
>                        |             and               |
>                        +-                             -+
>                        /            payload           /
>                        +-                             -+
>                        |                               |
>                        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                        |CRC (optional) |
>                        +-+-+-+-+-+-+-+-+
>=20
>=20
>          Figure 1: IEEE 802.16 MAC Frame Format for  IPv4 Packets
>=20
>       H: Header Type (1 bit).  Shall be set to zero indicating that it
>       is a Generic MAC PDU.
>       E: Encryption Control. 0 =3D Payload is not encrypted; 1 =3D =
Payload
>       is encrypted.
>       R: Reserved.  Shall be set to zero.
>       C: CRC Indicator. 1 =3D CRC is included, 0 =3D 1 No CRC is =
included
>       EKS: Encryption Key Sequence
>       LEN: The Length in bytes of the MAC PDU including the MAC header
>       and the CRC if present (11 bits)
>       CID: Connection Identifier (16 bits)
>       HCS: Header Check Sequence (8 bits)
>       CRC: An optional 8-bit field.  CRC appended to the PDU after
>       encryption.
>       TYPE: This field indicates the subheaders (Mesh subheader,
>       Fragmentation Subheader, Packing subheader etc and special
payload
>       types (ARQ) present in the message payload
>=20
> 4.3.  Maximum Transmission Unit
>=20
>       The MTU value for IPv4 packets on an IEEE 802.16 link is
>    configurable.  The default MTU for IPv4 packets over an IEEE 802.16

'is configurable'?? How, by which means??

>       link SHOULD be 1500 octets.
>=20
>=20
>=20
>=20
> Madanapalli, et al.       Expires April 4, 2009                 [Page
5]
> =0C
> Internet-Draft        IPv4 over IEEE 802.16's IP CS         October
2008
>=20
>=20
>    Per [RFC5121] section 6.3, the IP MTU can vary to be larger or
>    smaller than 1500 octets.
>=20
>    if an MS transmits 1500-octet packets in a deployment with a
smaller
>    MTU, packets from the MS may be dropped at the link-layer silently.
>    Unlike IPv6, in which departures from the default MTU are readily
>    advertised via the MTU option in Neighbor Discovery, there is no
>    similarly reliable mechanism in IPv4, as the legacy IPv4 client
>    implementations do not determine the link MTU by default before
>    sending packets.  Even though there is a DHCP option to accomplish
>    this, DHCP servers are required to provide the MTU information only
>    when requested.
>=20
>    Discovery and configuration of the proper link MTU value ensures
>    adequate usage of the network bandwidth and resources.
Accordingly,
>    deployments should avoid packet loss due to a mismatch between the
>    default MTU and the configured link MTUs.
>=20
>       Some of the mechanisms available for the IPv4 CS host to find
out
>    the link's MTU value and mitigate MTU-related issues are:
>=20
>    o  The IEEE is currently revising 802.16 (see 802.16Rev2

IEEE802.16 has revised the specification. Update the reference.

>       [802_16REV2]) to (among other things) allow providing the
Service
>       Data Unit or MAC MTU in the IEEE 802.16 SBC-REQ/SBC-RSP phase,
>       such that future IEEE 802.16 compliant clients can infer and
>       configure the negotiated MTU size for the IPv4 CS link.
However,
>       the implementation must communicate the negotiated MTU value to
>       the IP layer to adjust the IP Maximum payload size for proper
>       handling of fragmentation.  Note that this method is useful only
>       when MS is directly connected to the BS.
>    o  Configuration and negotiation of MTU size at the network layer
by
>       using the DHCP interface MTU option [RFC2132].
>=20
>    This document recommends that all future implementations of IPv4
and

Why 'future'?

>    IPv4 CS clients SHOULD implement the DHCP interface MTU option
>    [RFC2132] in order to configure its interface MTU accordingly.
>=20
>    In the absence of DHCP MTU configuration, the client node (MS) has
>    two alternatives: 1) use the default MTU (1500 bytes) or 2)
determine
>    the MTU by the methods described in [802_16REV2].

Can MS rely on the IEEE802.16 methods? Mandatory for all IEEE802.16
implementations?

>    Additionally, the clients are encouraged to run PMTU[RFC 1191] or
>    PPMTUD[RFC 4821].  However, the PMTU mechanism has inherent
problems
>    of packet loss due to ICMP messages not reaching the sender and
IPv4
>    routers not fragmenting the packets due to the DF bit being set in
>    the IP packet.  The above mentioned path MTU mechanisms will take
>    care of the MTU size between the MS and its correspondent node
across
>    different flavors of convergence layers in the access networks.
>=20
>=20
>=20
> Madanapalli, et al.       Expires April 4, 2009                 [Page
6]
> =0C
> Internet-Draft        IPv4 over IEEE 802.16's IP CS         October
2008
>=20
>=20
> 5.  Subnet Model and IPv4 Address Assignment
>=20
>    The Subnet Model recommended for IPv4 over IEEE 802.16 using IP CS
is
>    based on the point-to-point link between MS and AR [RFC4968], hence
>    each MS shall be assigned an address with 32bit prefix-length or
>    subnet-mask.  The point-to-point link between MS and AR is achieved
>    using a set of IEEE 802.16 MAC connections (identified by CIDs) and
>    an L2 tunnel (e.g., a GRE tunnel) per MS between BS and AR.  If the
>    AR is co-located with the BS, then the set of IEEE 802.16 MAC
>    connections between the MS and BS/AR represent the point-to- point
>    connection.
>=20
> 5.1.  IPv4 Unicast Address Assignment and Router Discovery
>=20
>    DHCP [RFC2131] SHOULD be used for assigning IPv4 address for the
MS.
>    DHCP messages are transported over the IEEE 802.16 MAC connection
to
>    and from the BS and relayed to the AR.  In case the DHCP server
does
>    not reside in the AR, the AR SHOULD implement DHCP relay Agent
>    [RFC1542].
>=20
>    Although DHCP is the recommended method of address assignment, it
is
>    possible that the MS could be a pure Mobile IPv4 [RFC3344] device
>    which will be offered an IP address from its home network after
>    successful Mobile IP [RFC3344] registration.  In such situations,
the
>    mobile host SHOULD use the default link MTU in order to avoid any
>    link-layer packet loss due to larger than supported packet size in
>    the IP CS link.
>=20
>    Router discovery messages [RFC1256] contain router solicitation and
>    router advertisements.  The Router solicitation messages (multicast
>    or broadcast) from the MS are delivered to the AR via the BS
through
>    the point-to-point link.  The BS SHOULD map the all-routers
multicast
>    nodes or broadcast nodes for router discovery to the AR's IP
address
>    and deliver directly to the AR.  Similarly a router advertisement
to
>    the all-nodes multicast nodes will be either unicast to each MS by
>    the BS separately or put onto a multicast connection to which all
MSs
>    are listening to.  If no multicast connection exists, and the BS
does
>    not have the capability to aggregate and disaggregate the messages
to
>    and from the MS hosts, then the AR implementation must ensure that
>    unicast messages are sent to the corresponding individual MS hosts
>    within the set of broadcast or multicast recipients.  This
>    specification simply assumes that the multicast service is
provided.
>    How the multicast service is implemented in an IEEE 802.16 Packet
CS
>    deployment is out of scope of this document.
>=20
>    The 'Next hop' IP address of the IP CS MS is always the IP address
of
>    the AR, because MS and AR are attached via a point-to-point link.
>=20
>=20
>=20
>=20
> Madanapalli, et al.       Expires April 4, 2009                 [Page
7]
> =0C
> Internet-Draft        IPv4 over IEEE 802.16's IP CS         October
2008
>=20
>=20
> 5.2.  Address Resolution Protocol
>=20
>    The IP CS does not allow for transmission of ARP [RFC0826] packets.
>    Furthermore, in a point-to-point link model, address resolution is
>    not needed.
>=20
> 5.3.  IP Multicast Address Mapping
>=20
>    IPv4 multicast packets are carried over the point-to-point link
>    between the AR and the MS (via the BS).  The IPv4 multicast packets
>    are classified normally at the IP CS if the IEEE 802.16 MAC
>    connection has been set up with a multicast IP address as a
>    classification parameter for the destination IP address.  The IPv4
>    multicast address may be mapped into a multicast CID as defined in
>    the IEEE 802.16 specification.  The mapping mechanism at the BS or
>    the relative efficiency of using a multicast CID as opposed to
>    simulating multicast by generating multiple unicast messages are
out
>    of scope of this document.  For further considerations on the use
of
>    multicast CIDs see [ETHCS].
>=20
>=20
> 6.  Security Considerations
>=20
>    This document specifies transmission of IPv4 packets over IEEE
802.16
>    networks with IPv4 Convergence Sublayer and does not introduce any
>    new vulnerabilities to IPv4 specifications or operation.  The
>    security of the IEEE 802.16 air interface is the subject of
>    [IEEE802_16].  In addition, the security issues of the network
>    architecture spanning beyond the IEEE 802.16 base stations is the
>    subject of the documents defining such architectures, such as WiMAX
>    Network Architecture [WMF].
>=20
>=20
> 7.  IANA Considerations
>=20
>    This document has no actions for IANA.
>=20
>=20
> 8.  Acknowledgements
>=20
>    The authors would like to acknowledge the contributions of Bernard
>    Aboba, Dave Thaler, Jari Arkko, Bachet Sarikaya, Basavaraj Patil,
>    Paolo Narvaez, and Bruno Sousa for their review and comments.  The
>    working group members Burcak Beser, Wesley George, Max Riegel and
DJ
>    Johnston helped shape the MTU discussion for IPv4 CS link.  Thanks
to
>    many other members of the 16ng working group who commented on this
>    document to make it better.
>=20
>=20
>=20
>=20
> Madanapalli, et al.       Expires April 4, 2009                 [Page
8]
> =0C
> Internet-Draft        IPv4 over IEEE 802.16's IP CS         October
2008
>=20
>=20
> 9.  References
>=20
> 9.1.  Normative References
>=20
>    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
>               Requirement Levels", BCP 14, RFC 2119, March 1997.
>=20
>    [RFC0791]  Postel, J., "Internet Protocol", STD 5, RFC 791,
>               September 1981.
>=20
>    [RFC0826]  Plummer, D., "Ethernet Address Resolution Protocol: Or
>               converting network protocol addresses to 48.bit Ethernet
>               address for transmission on Ethernet hardware", STD 37,
>               RFC 826, November 1982.
>=20
>    [RFC2131]  Droms, R., "Dynamic Host Configuration Protocol",
>               RFC 2131, March 1997.
>=20
>    [RFC1542]  Wimer, W., "Clarifications and Extensions for the
>               Bootstrap Protocol", RFC 1542, October 1993.
>=20
>    [RFC5121]  Patil, B., Xia, F., Sarikaya, B., Choi, JH., and S.
>               Madanapalli, "Transmission of IPv6 via the IPv6
>               Convergence Sublayer over IEEE 802.16 Networks", RFC
5121,
>               February 2008.
>=20
>    [RFC5154]  Jee, J., Madanapalli, S., and J. Mandin, "IP over IEEE
>               802.16 Problem Statement and Goals", RFC 5154, April
2008.
>=20
>    [RFC4968]  Madanapalli, S., "Analysis of IPv6 Link Models for
802.16
>               Based Networks", RFC 4968, August 2007.
>=20
> 9.2.  Informative References
>=20
>    [RFC1191]  Mogul, J. and S. Deering, "Path MTU discovery", RFC
1191,
>               November 1990.
>=20
>    [RFC4821]  Mathis, M. and J. Heffner, "Packetization Layer Path MTU
>               Discovery", RFC 4821, March 2007.
>=20
>    [RFC2132]  Alexander, S. and R. Droms, "DHCP Options and BOOTP
Vendor
>               Extensions", RFC 2132, March 1997.
>=20
>    [RFC4840]  Aboba, B., Davies, E., and D. Thaler, "Multiple
>               Encapsulation Methods Considered Harmful", RFC 4840,
>               April 2007.
>=20
>    [RFC3344]  Perkins, C., "IP Mobility Support for IPv4", RFC 3344,
>=20
>=20
>=20
> Madanapalli, et al.       Expires April 4, 2009                 [Page
9]
> =0C
> Internet-Draft        IPv4 over IEEE 802.16's IP CS         October
2008
>=20
>=20
>               August 2002.
>=20
>    [RFC1256]  Deering, S., "ICMP Router Discovery Messages", RFC 1256,
>               September 1991.
>=20
>    [ETHCS]    Jeon, H., Riegel, M., and S. Jeong, "Transmission of IP
>               over Ethernet over IEEE 802.16 Networks", April 2008,
>               <http://www.ietf.org/internet-drafts/
>               draft-ietf-16ng-ip-over-ethernet-over-802.16-06.txt>.
>=20
>    [802_16REV2]
>               Johnston, D., "SDU MTU Capability Declaration",
>               March 2008, <http://www.ieee.org/16>.
>=20
>    [IEEE802_16]
>               "IEEE 802.16e, IEEE standard for Local and metropolitan
>               area networks, Part 16:Air Interface for fixed and
Mobile
>               broadband wireless access systems", October 2005.

IEEE802.16-2009 is released and supersedes 16e as well as REV2.
Why is the IEEE802.16 specification listed under informative?

>    [WMF]      "WiMAX End-to-End Network Systems Architecture Stage 2-3
>               Release 1.2,
>               http://www.wimaxforum.org/technology/documents",
>               January 2008.
>=20
>=20
> Appendix A.  Multiple Convergence Layers - Impact on Subnet Model
>=20
>    Two different MSs using two different convergence sublayers (e.g.
an
>    MS using Ethernet CS only and another MS using IP CS only) cannot
>    communicate at data link layer and requires interworking at IP
layer.
>    For this reason, these two nodes must be configured to be on two
>    different subnets.  For more information refer to [RFC4840].
>=20
>=20
> Appendix B.  Sending and Receiving IPv4 Packets
>=20
>    IEEE 802.16 MAC is a point-to-multipoint connection oriented air-
>    interface, and the process of sending and receiving of IPv4 packets
>    is different from multicast-capable shared medium technologies like
>    Ethernet.
>=20
>    Before any packets are transmitted, a IEEE 802.16 transport
>    connection must be established.  This connection consists of IEEE
>    802.16 MAC transport connection between MS and BS and an L2 tunnel
>    between BS and AR (if these two are not co-located).  This IEEE
>    802.16 transport connection provides a point-to-point link between
>    the MS and AR.  All the packets originated at the MS always reach
the
>    AR before being transmitted to the final destination.
>=20
>=20
>=20
> Madanapalli, et al.       Expires April 4, 2009                [Page
10]
> =0C
> Internet-Draft        IPv4 over IEEE 802.16's IP CS         October
2008
>=20
>=20
>    IPv4 packets are carried directly in the payload of IEEE 802.16
>    frames when the IPv4 CS is used.  IPv4 CS classifies the packet
based
>    on upper layer (IP and transport layers) header fields to place the
>    packet on one of the available connections identified by the CID.
>    The classifiers for the IPv4 CS are source and destination IPv4
>    addresses, source and destinations ports, Type-of-Service and IP
>    protocol field.  The CS may employ Packet Header Suppression (PHS)
>    after the classification.
>=20
>    The BS optionally reconstructs the payload header if PHS is in use.
>    It then tunnels the packet that has been received on a particular
MAC
>    connection to the AR.  Similarly the packets received on a tunnel
>    interface from the AR, would be mapped to a particular CID using
the
>    IPv4 classification mechanism.
>=20
>    AR performs normal routing for the packets that it receives,
>    processing them per its forwarding table.  However, the DHCP relay
>    agent in the AR MUST maintain the tunnel interface on which it
>    receives DHCP requests so that it can relay the DHCP responses to
the
>    correct MS.  One way of doing this is to have a mapping between MAC
>    address and Tunnel Identifier.

Which MAC address?

>=20
> Appendix C.  WiMAX IPCS MTU size
>=20
>    WiMAX (Worldwide Interoperability for Microwave Access) forum has
>    defined a network architecture[WMF].  Furthermore, WiMAX has
>    specified IPv4 CS support for transmission of IPv4 packets between
MS
>    and BS over the IEEE 802.16 link.  The WiMAX IPv4 CS and this
>    specification are similar.  One significant difference, however, is
>    that the WiMAX Forum [WMF] has specified the IP MTU as 1400 octets
>    [WMF] as opposed to 1500 in this specification.
>=20
>    Hence if an IPv4 CS MS configured with an MTU of 1500 octet enters
a
>    WiMAX network, some of the issues mentioned in this specification
may
>    arise.  As mentioned in section 4.3, the possible mechanisms are
not
>    guaranteed to work.  Furthermore, an IPv4 CS client is not capable
of
>    doing ARP probing to find out the link MTU.  On the other hand, it
is
>    imperative for an MS to know the link MTU size.  In practice, MS
>    should be able to sense or deduce the fact that they are operating
>    within a WiMAX network (e.g., given the WiMAX-specific
>    particularities of the authentication and network entry
procedures),
>    and adjust their MTU size accordingly.  This document makes no
>    further assumptions in this respect.

Appendix C should be removed.
Only WiMAX devices will enter WiMAX networks, and WiMAX devices know
about the MTU size in WiMAX networks.

>=20
>=20
>=20
>=20
>=20
>=20
> Madanapalli, et al.       Expires April 4, 2009                [Page
11]
> =0C
> Internet-Draft        IPv4 over IEEE 802.16's IP CS         October
2008
>=20
>=20
> Appendix D.  Thoughts on handling multicast-broadcast IP packets
>=20
>    Although this document does not directly specify details of
multicast
>    or broadcast packet handling, here are some suggestions:
>=20
>    While uplink connections from the MSs to the BS provide only
unicast
>    transmission capabilities, downlink connections can be used for
>    multicast transmission to a group of MSs as well as unicast
>    transmission from the BS to a single MS.  For all-node IP
addresses,
>    the AR or BS should have special mapping and the packets should be
>    distributed to all active point-to-point connections by the AR or
by
>    the BS.  All-router multicast packets and any broadcast packets
from
>    a MS will be forwarded to the AR by the BS.  If BS and MS are co-
>    located, then the first approach is more useful.  If the AR and BS
>    are located separately then the second approach should be
>    implemented.  An initial capability exchange message should be
>    performed between BS and AR (if they are not co-located) to
determine
>    who would perform the distribution of multicast/broadcast packets.
>    Such mechansim should be part of L2 exchange during the connection
>    setup and is out of scope of this document.  In order to save
energy
>    of the wireless end devices in the IEEE 802.16 wireless network, it
>    is recommened that the multicast and broadcast from network side to
>    device side should be reduced.  Only DHCP, IGMP, Router
advertisemnet
>    packets are allowed on the downlink for multicast and broadcast IP
>    addresses.  Other protocols using multicast and broadcast IP
>    addresses should be permitted through local AR/BS configuration.
>=20
>=20
> Authors' Addresses
>=20
>    Syam Madanapalli
>    Ordyn Technologies
>    1st Floor, Creator Building, ITPL
>    Bangalore - 560066
>    India
>=20
>    Email: smadanapalli@gmail.com
>=20
>=20
>    Soohong Daniel Park
>    Samsung Electronics
>    416 Maetan-3dong, Yeongtong-gu
>    Suwon 442-742
>    Korea
>=20
>    Email: soohong.park@samsung.com
>=20
>=20
>=20
>=20
>=20
> Madanapalli, et al.       Expires April 4, 2009                [Page
12]
> =0C
> Internet-Draft        IPv4 over IEEE 802.16's IP CS         October
2008
>=20
>=20
>    Samita Chakrabarti
>    IP Infusion
>    1188 Arques Avenue
>    Sunnyvale, CA
>    USA
>=20
>    Email: samitac@ipinfusion.com
>=20
>=20
>    Gabriel Montenegro
>    Microsoft Corporation
>    Redmond, Washington
>    USA
>=20
>    Email: gabriel.montenegro@microsoft.com
>=20




> -----Original Message-----
> From: 16ng-bounces@ietf.org [mailto:16ng-bounces@ietf.org] On Behalf
Of ext Internet-Drafts@ietf.org
> Sent: Wednesday, June 03, 2009 5:45 PM
> To: i-d-announce@ietf.org
> Cc: 16ng@ietf.org
> Subject: [16NG] I-D
Action:draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05.txt
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> This draft is a work item of the IP over IEEE 802.16 Networks Working
Group of the IETF.
>=20
>=20
> 	Title           : Transmission of IPv4 packets over IEEE
802.16's IP Convergence Sublayer
> 	Author(s)       : S. Madanapalli, et al.
> 	Filename        :
draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05.txt
> 	Pages           : 14
> 	Date            : 2009-06-03
>=20
> IEEE 802.16 is an air interface specification for wireless broadband
> access.  IEEE 802.16 has specified multiple service specific
> Convergence Sublayers for transmitting upper layer protocols.  The
> packet CS (Packet Convergence Sublayer) is used for the transport of
> all packet-based protocols such as Internet Protocol (IP), IEEE 802.3
> (Ethernet) and IEEE 802.1Q (VLAN).  The IP-specific part of the
> Packet CS enables the transport of IPv4 packets directly over the
> IEEE 802.16 MAC.
>=20
> This document specifies the frame format, the Maximum Transmission
> Unit (MTU) and address assignment procedures for transmitting IPv4
> packets over the IP-specific part of the Packet Convergence Sublayer
> of IEEE 802.16.
>=20
> A URL for this Internet-Draft is:
>
http://www.ietf.org/internet-drafts/draft-ietf-16ng-ipv4-over-802-dot-16
-ipcs-05.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.

From maximilian.riegel@nsn.com  Thu Jun  4 15:59:22 2009
Return-Path: <maximilian.riegel@nsn.com>
X-Original-To: 16ng@core3.amsl.com
Delivered-To: 16ng@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 875A03A68EE for <16ng@core3.amsl.com>; Thu,  4 Jun 2009 15:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.799
X-Spam-Level: 
X-Spam-Status: No, score=-4.799 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_43=0.6, J_CHICKENPOX_45=0.6, J_CHICKENPOX_63=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ksiLFyD2-1cB for <16ng@core3.amsl.com>; Thu,  4 Jun 2009 15:59:19 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [217.115.75.233]) by core3.amsl.com (Postfix) with ESMTP id AF1BE3A681C for <16ng@ietf.org>; Thu,  4 Jun 2009 15:59:18 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id n54MxKnH011946 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 5 Jun 2009 00:59:20 +0200
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id n54MxJZE006836; Fri, 5 Jun 2009 00:59:19 +0200
Received: from DEMUEXC014.nsn-intra.net ([10.150.128.25]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 5 Jun 2009 00:58:25 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C9E567.F6FDBBD2"
Date: Fri, 5 Jun 2009 00:58:26 +0200
Message-ID: <BC27158B99D3064A955ADE084783900C021E70E2@DEMUEXC014.nsn-intra.net>
In-Reply-To: <BC27158B99D3064A955ADE084783900C021E70E1@DEMUEXC014.nsn-intra.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [16NG] I-DAction:draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05.txt
Thread-Index: AcnkYn5oQw46mIdPQamkrbG7pFW1sQBAi7vgAAC1qNA=
References: <20090603154501.B0C963A6CBB@core3.amsl.com> <BC27158B99D3064A955ADE084783900C021E70E1@DEMUEXC014.nsn-intra.net>
From: "Riegel, Maximilian (NSN - DE/Munich)" <maximilian.riegel@nsn.com>
To: "Riegel, Maximilian (NSN - DE/Munich)" <maximilian.riegel@nsn.com>, <16ng@ietf.org>
X-OriginalArrivalTime: 04 Jun 2009 22:58:25.0384 (UTC) FILETIME=[F784D680:01C9E567]
Cc: ext Alper Yegin <alper.yegin@yegin.org>, ext gabriel montenegro <g_e_montenegro@yahoo.com>
Subject: Re: [16NG] I-DAction:draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05.txt
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2009 22:59:22 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9E567.F6FDBBD2
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Please find attached the txt document with my comments, in the case your
screen looks as awful as mine (word wrapping did a horrible job)

Bye
Max

-----Original Message-----
From: 16ng-bounces@ietf.org [mailto:16ng-bounces@ietf.org] On Behalf Of
ext Riegel, Maximilian (NSN - DE/Munich)
Sent: Friday, June 05, 2009 12:50 AM
To: 16ng@ietf.org
Cc: ext Alper Yegin; ext gabriel montenegro
Subject: Re: [16NG]
I-DAction:draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05.txt

I went through the document and found a couple of issues, which I would
like to see in a better shape.
Please find my comments inline:

Bye
Max

> 16ng Working Group                                        S.
Madanapalli
> Internet-Draft                                        Ordyn
Technologies
> Intended status: Standards Track                         Soohong D.
Park
> Expires: April 4, 2009                               Samsung

------_=_NextPart_001_01C9E567.F6FDBBD2
Content-Type: text/plain;
	name="draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05-max.txt"
Content-Transfer-Encoding: base64
Content-Description: draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05-max.txt
Content-Disposition: attachment;
	filename="draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05-max.txt"

PiAxNm5nIFdvcmtpbmcgR3JvdXAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgUy4gTWFkYW5hcGFsbGkNCj4gSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgT3JkeW4gVGVjaG5vbG9naWVzDQo+IEludGVuZGVkIHN0YXR1czog
U3RhbmRhcmRzIFRyYWNrICAgICAgICAgICAgICAgICAgICAgICAgIFNvb2hvbmcgRC4gUGFyaw0K
PiBFeHBpcmVzOiBBcHJpbCA0LCAyMDA5ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFNh
bXN1bmcgRWxlY3Ryb25pY3MNCj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIFMuIENoYWtyYWJhcnRpDQo+ICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBJUCBJbmZ1c2lvbg0K
PiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgIEcuIE1vbnRlbmVncm8NCj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgTWljcm9zb2Z0IENvcnBvcmF0aW9uDQo+ICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIE9jdG9iZXIgMjAwOA0K
PiANCj4gDQo+IFRyYW5zbWlzc2lvbiBvZiBJUHY0IHBhY2tldHMgb3ZlciBJRUVFIDgwMi4xNidz
IElQIENvbnZlcmdlbmNlIFN1YmxheWVyDQo+ICAgICAgICAgICAgIGRyYWZ0LWlldGYtMTZuZy1p
cHY0LW92ZXItODAyLWRvdC0xNi1pcGNzLTA1LnR4dA0KPiANCj4gU3RhdHVzIG9mIHRoaXMgTWVt
bw0KPiANCj4gICAgQnkgc3VibWl0dGluZyB0aGlzIEludGVybmV0LURyYWZ0LCBlYWNoIGF1dGhv
ciByZXByZXNlbnRzIHRoYXQgYW55DQo+ICAgIGFwcGxpY2FibGUgcGF0ZW50IG9yIG90aGVyIElQ
UiBjbGFpbXMgb2Ygd2hpY2ggaGUgb3Igc2hlIGlzIGF3YXJlDQo+ICAgIGhhdmUgYmVlbiBvciB3
aWxsIGJlIGRpc2Nsb3NlZCwgYW5kIGFueSBvZiB3aGljaCBoZSBvciBzaGUgYmVjb21lcw0KPiAg
ICBhd2FyZSB3aWxsIGJlIGRpc2Nsb3NlZCwgaW4gYWNjb3JkYW5jZSB3aXRoIFNlY3Rpb24gNiBv
ZiBCQ1AgNzkuDQo+IA0KPiAgICBJbnRlcm5ldC1EcmFmdHMgYXJlIHdvcmtpbmcgZG9jdW1lbnRz
IG9mIHRoZSBJbnRlcm5ldCBFbmdpbmVlcmluZw0KPiAgICBUYXNrIEZvcmNlIChJRVRGKSwgaXRz
IGFyZWFzLCBhbmQgaXRzIHdvcmtpbmcgZ3JvdXBzLiAgTm90ZSB0aGF0DQo+ICAgIG90aGVyIGdy
b3VwcyBtYXkgYWxzbyBkaXN0cmlidXRlIHdvcmtpbmcgZG9jdW1lbnRzIGFzIEludGVybmV0LQ0K
PiAgICBEcmFmdHMuDQo+IA0KPiAgICBJbnRlcm5ldC1EcmFmdHMgYXJlIGRyYWZ0IGRvY3VtZW50
cyB2YWxpZCBmb3IgYSBtYXhpbXVtIG9mIHNpeCBtb250aHMNCj4gICAgYW5kIG1heSBiZSB1cGRh
dGVkLCByZXBsYWNlZCwgb3Igb2Jzb2xldGVkIGJ5IG90aGVyIGRvY3VtZW50cyBhdCBhbnkNCj4g
ICAgdGltZS4gIEl0IGlzIGluYXBwcm9wcmlhdGUgdG8gdXNlIEludGVybmV0LURyYWZ0cyBhcyBy
ZWZlcmVuY2UNCj4gICAgbWF0ZXJpYWwgb3IgdG8gY2l0ZSB0aGVtIG90aGVyIHRoYW4gYXMgIndv
cmsgaW4gcHJvZ3Jlc3MuIg0KPiANCj4gICAgVGhlIGxpc3Qgb2YgY3VycmVudCBJbnRlcm5ldC1E
cmFmdHMgY2FuIGJlIGFjY2Vzc2VkIGF0DQo+ICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvaWV0Zi8x
aWQtYWJzdHJhY3RzLnR4dC4NCj4gDQo+ICAgIFRoZSBsaXN0IG9mIEludGVybmV0LURyYWZ0IFNo
YWRvdyBEaXJlY3RvcmllcyBjYW4gYmUgYWNjZXNzZWQgYXQNCj4gICAgaHR0cDovL3d3dy5pZXRm
Lm9yZy9zaGFkb3cuaHRtbC4NCj4gDQo+ICAgIFRoaXMgSW50ZXJuZXQtRHJhZnQgd2lsbCBleHBp
cmUgb24gQXByaWwgNCwgMjAwOS4NCj4gDQo+IEFic3RyYWN0DQo+IA0KPiAgICBJRUVFIDgwMi4x
NiBpcyBhbiBhaXIgaW50ZXJmYWNlIHNwZWNpZmljYXRpb24gZm9yIHdpcmVsZXNzIGJyb2FkYmFu
ZA0KPiAgICBhY2Nlc3MuICBJRUVFIDgwMi4xNiBoYXMgc3BlY2lmaWVkIG11bHRpcGxlIHNlcnZp
Y2Ugc3BlY2lmaWMNCj4gICAgY29udmVyZ2VuY2Ugc3VibGF5ZXJzIGZvciB0cmFuc21pdHRpbmcg
dXBwZXIgbGF5ZXIgcHJvdG9jb2xzLiAgVGhlDQo+ICAgIHBhY2tldCBDUyAoUGFja2V0IENvbnZl
cmdlbmNlIFN1YmxheWVyKSBpcyB1c2VkIGZvciB0aGUgdHJhbnNwb3J0IG9mDQo+ICAgIGFsbCBw
YWNrZXQtYmFzZWQgcHJvdG9jb2xzIHN1Y2ggYXMgSW50ZXJuZXQgUHJvdG9jb2wgKElQKSwgSUVF
RSA4MDIuMw0KPiAgICAoRXRoZXJuZXQpIGFuZCBJRUVFIDgwMi4xUSAoVkxBTikuICBUaGUgSVAt
c3BlY2lmaWMgcGFydCBvZiB0aGUNCg0KTWVhbndoaWxlIHRoZSBJRUVFODAyLjE2LTIwMDkgKHdh
cyBSRVYyKSBzcGVjaWZpY2F0aW9uIGhhcyBiZWVuIHJlbGVhc2VkLg0KSUVFRTgwMi4xNi0yMDA5
IGRvZXMgbm90IGtub3cgYW55bW9yZSBhYm91dCB0aGUgSUVFRSA4MDIuMVEgKFZMQU4pIENTLg0K
DQo+ICAgIFBhY2tldCBDUyBlbmFibGVzIHRoZSB0cmFuc3BvcnQgb2YgSVB2NCBwYWNrZXRzIGRp
cmVjdGx5IG92ZXIgdGhlDQo+IA0KPiANCj4gDQo+IE1hZGFuYXBhbGxpLCBldCBhbC4gICAgICAg
RXhwaXJlcyBBcHJpbCA0LCAyMDA5ICAgICAgICAgICAgICAgICBbUGFnZSAxXQ0KPiAMDQo+IElu
dGVybmV0LURyYWZ0ICAgICAgICBJUHY0IG92ZXIgSUVFRSA4MDIuMTYncyBJUCBDUyAgICAgICAg
IE9jdG9iZXIgMjAwOA0KPiANCj4gDQo+ICAgIElFRUUgODAyLjE2IE1BQy4NCj4gDQo+ICAgIFRo
aXMgZG9jdW1lbnQgc3BlY2lmaWVzIHRoZSBmcmFtZSBmb3JtYXQsIHRoZSBNYXhpbXVtIFRyYW5z
bWlzc2lvbg0KPiAgICBVbml0IChNVFUpIGFuZCBhZGRyZXNzIGFzc2lnbm1lbnQgcHJvY2VkdXJl
cyBmb3IgdHJhbnNtaXR0aW5nIElQdjQNCj4gICAgcGFja2V0cyBvdmVyIHRoZSBJUC1zcGVjaWZp
YyBwYXJ0IG9mIHRoZSBQYWNrZXQgQ29udmVyZ2VuY2UgU3VibGF5ZXINCj4gICAgb2YgSUVFRSA4
MDIuMTYuDQo+IA0KPiANCj4gVGFibGUgb2YgQ29udGVudHMNCj4gDQo+ICAgIDEuICBJbnRyb2R1
Y3Rpb24gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg
Mw0KPiAgICAyLiAgVGVybWlub2xvZ3kgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gIDMNCj4gICAgMy4gIFR5cGljYWwgTmV0d29yayBBcmNoaXRlY3R1
cmUgZm9yIElQdjQgb3ZlciBJRUVFIDgwMi4xNiAuIC4gLiAuICAzDQo+ICAgICAgMy4xLiAgSUVF
RSA4MDIuMTYgSVB2NCBDb252ZXJnZW5jZSBzdWItbGF5ZXIgc3VwcG9ydCAuIC4gLiAuIC4gLiAg
Mw0KPiAgICA0LiAgSVB2NCBDUyBsaW5rIGluIDgwMi4xNiBOZXR3b3JrcyAgLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gIDQNCj4gICAgICA0LjEuICBJUHY0IENTIGxpbmsgZXN0YWJsaXNo
bWVudCAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA0DQo+ICAgICAgNC4yLiAgRnJh
bWUgRm9ybWF0IGZvciBJUHY0IFBhY2tldHMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg
NA0KPiAgICAgIDQuMy4gIE1heGltdW0gVHJhbnNtaXNzaW9uIFVuaXQgIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gIDUNCj4gICAgNS4gIFN1Ym5ldCBNb2RlbCBhbmQgSVB2NCBBZGRy
ZXNzIEFzc2lnbm1lbnQgLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA3DQo+ICAgICAgNS4xLiAgSVB2
NCBVbmljYXN0IEFkZHJlc3MgQXNzaWdubWVudCBhbmQgUm91dGVyIERpc2NvdmVyeSAuIC4gLiAg
Nw0KPiAgICAgIDUuMi4gIEFkZHJlc3MgUmVzb2x1dGlvbiBQcm90b2NvbCAgLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gIDgNCj4gICAgICA1LjMuICBJUCBNdWx0aWNhc3QgQWRkcmVzcyBN
YXBwaW5nIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA4DQo+ICAgIDYuICBTZWN1cml0
eSBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg
OA0KPiAgICA3LiAgSUFOQSBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gIDgNCj4gICAgOC4gIEFja25vd2xlZGdlbWVudHMgLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA4DQo+ICAgIDkuICBSZWZlcmVu
Y2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg
OQ0KPiAgICAgIDkuMS4gIE5vcm1hdGl2ZSBSZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gIDkNCj4gICAgICA5LjIuICBJbmZvcm1hdGl2ZSBSZWZlcmVuY2Vz
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA5DQo+ICAgIEFwcGVuZGl4IEEu
ICBNdWx0aXBsZSBDb252ZXJnZW5jZSBMYXllcnMgLSBJbXBhY3Qgb24gU3VibmV0DQo+ICAgICAg
ICAgICAgICAgICBNb2RlbCAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAxMA0KPiAgICBBcHBlbmRpeCBCLiAgU2VuZGluZyBhbmQgUmVjZWl2aW5nIElQdjQg
UGFja2V0cyAgLiAuIC4gLiAuIC4gLiAuIC4gMTANCj4gICAgQXBwZW5kaXggQy4gIFdpTUFYIElQ
Q1MgTVRVIHNpemUgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDExDQo+ICAgIEFw
cGVuZGl4IEQuICBUaG91Z2h0cyBvbiBoYW5kbGluZyBtdWx0aWNhc3QtYnJvYWRjYXN0IElQDQo+
ICAgICAgICAgICAgICAgICBwYWNrZXRzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAxMg0KPiAgICBBdXRob3JzJyBBZGRyZXNzZXMgLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTINCj4gICAgSW50ZWxsZWN0dWFsIFBy
b3BlcnR5IGFuZCBDb3B5cmlnaHQgU3RhdGVtZW50cyAuIC4gLiAuIC4gLiAuIC4gLiAuIDE0DQo+
IA0KPiANCj4gDQo+IA0KPiANCj4gDQo+IA0KPiANCj4gDQo+IA0KPiANCj4gDQo+IA0KPiANCj4g
DQo+IE1hZGFuYXBhbGxpLCBldCBhbC4gICAgICAgRXhwaXJlcyBBcHJpbCA0LCAyMDA5ICAgICAg
ICAgICAgICAgICBbUGFnZSAyXQ0KPiANCj4gSW50ZXJuZXQtRHJhZnQgICAgICAgIElQdjQgb3Zl
ciBJRUVFIDgwMi4xNidzIElQIENTICAgICAgICAgT2N0b2JlciAyMDA4DQo+IA0KPiANCj4gMS4g
IEludHJvZHVjdGlvbg0KPiANCj4gICAgSUVFRSA4MDIuMTYgW0lFRUU4MDJfMTZdIGlzIGEgY29u
bmVjdGlvbiBvcmllbnRlZCBhY2Nlc3MgdGVjaG5vbG9neQ0KPiAgICBmb3IgdGhlIGxhc3QgbWls
ZS4gIFRoZSBJRUVFIDgwMi4xNiBzcGVjaWZpY2F0aW9uIGluY2x1ZGVzIHRoZSBQSFkNCj4gICAg
YW5kIE1BQyBsYXllcnMuICBUaGUgTUFDIGluY2x1ZGVzIHZhcmlvdXMgY29udmVyZ2VuY2Ugc3Vi
bGF5ZXJzIChDUykNCj4gICAgZm9yIHRyYW5zbWl0dGluZyBoaWdoZXIgbGF5ZXIgcGFja2V0cyBp
bmNsdWRpbmcgSVB2NCBwYWNrZXRzDQo+ICAgIFtSRkM1MTU0XS4NCj4gDQo+ICAgIFRoZSBzY29w
ZSBvZiB0aGlzIHNwZWNpZmljYXRpb24gaXMgbGltaXRlZCB0byB0aGUgb3BlcmF0aW9uIG9mIElQ
djQNCj4gICAgb3ZlciB0aGUgSVAtc3BlY2lmaWMgcGFydCBvZiB0aGUgcGFja2V0IENTIChyZWZl
cnJlZCB0byBhcyAiSVB2NCBDUyINCj4gICAgb3Igc2ltcGx5ICJJUCBDUyIgaW4gdGhpcyBkb2N1
bWVudCkuDQoNCklQdjQgQ1Mgc2hvdWxkIGJlIHVzZWQgdGhyb3VnaG91dCB0aGUgZG9jdW1lbnQg
dG8gcHJldmVudCBtaXhpbmcgaXQgdXAgd2l0aCB0aGUgSVB2NiBDUyBzcGVjaWZpY2F0aW9uLiBU
aGVyZSBpcyBub3RoaW5nIGxpa2UgSVAgQ1MgaW4gdGhlIElFRUU4MDIuMTYgc3BlY2lmaWNhdGlv
biwgdGhlcmUgaXMgb25seSBJUHY0IENTIGFuZCBJUHY2IENTLg0KQlRXOiB0aGVyZSBpcyBub3cg
YSBzaW5nbGUgRVRIIENTIGNhcnJ5aW5nIElQdjQgYXMgd2VsbCBhcyBJUHY2IHBheWxvYWQuDQoN
Cj4gICAgVGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgYSBtZXRob2QgZm9yIGVuY2Fwc3VsYXRpbmcg
YW5kIHRyYW5zbWl0dGluZw0KPiAgICBJUHY0IFtSRkMwNzkxXSBwYWNrZXRzIG92ZXIgdGhlIElQ
IENTIG9mIElFRUUgODAyLjE2LiAgVGhpcyBkb2N1bWVudA0KICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIF5JUHY0IENTDQo+ICAgIGFsc28gc3BlY2lmaWVzIHRoZSBNVFUgYW5k
IGFkZHJlc3MgYXNzaWdubWVudCBtZXRob2QgZm9yIHRoZSBJRUVFDQoNCldoaWNoIE1UVSwgd2hp
Y2ggYWRkcmVzcyBhc3NpZ25tZW50PyBNb3JlIGNvbmNpc2Ugd29yZGluZyB3b3VsZCBoZWxwLg0K
DQo+ICAgIDgwMi4xNiBiYXNlZCBuZXR3b3JrcyB1c2luZyBJUCBDUy4NCiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIF5JUHY0IENTDQo+IA0KPiAgICBUaGlzIGRvY3VtZW50IGFsc28g
ZGlzY3Vzc2VzIEFSUCAoQWRkcmVzcyBSZXNvbHV0aW9uIFByb3RvY29sKSBhbmQNCj4gICAgTXVs
dGljYXN0IEFkZHJlc3MgTWFwcGluZyB3aG9zZSBvcGVyYXRpb24gaXMgc2ltaWxhciB0byBhbnkg
b3RoZXINCj4gICAgcG9pbnQtdG8tcG9pbnQgbGluayBtb2RlbC4NCg0KV2hhdCBkbyB5b3UgbWVh
biB3aXRoIHRoaXMgc2VudGVuY2U/DQoNCj4gICAgVGhlIGtleSB3b3JkcyAiTVVTVCIsICJNVVNU
IE5PVCIsICJSRVFVSVJFRCIsICJTSEFMTCIsICJTSEFMTCBOT1QiLA0KPiAgICAiU0hPVUxEIiwg
IlNIT1VMRCBOT1QiLCAiUkVDT01NRU5ERUQiLCAiTUFZIiwgYW5kICJPUFRJT05BTCIgaW4gdGhp
cw0KPiAgICBkb2N1bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgYXMgZGVzY3JpYmVkIGluIFtS
RkMyMTE5XS4NCj4gDQo+IA0KPiAyLiAgVGVybWlub2xvZ3kNCj4gDQo+ICAgIFRoZSB0ZXJtaW5v
bG9neSBpbiB0aGlzIGRvY3VtZW50IGlzIGJhc2VkIG9uIHRoZSBkZWZpbml0aW9ucyBpbg0KPiAg
ICBbUkZDNTE1NF0uDQo+IA0KPiANCj4gMy4gIFR5cGljYWwgTmV0d29yayBBcmNoaXRlY3R1cmUg
Zm9yIElQdjQgb3ZlciBJRUVFIDgwMi4xNg0KPiANCj4gICAgVGhlIG5ldHdvcmsgYXJjaGl0ZWN0
dXJlIGZvbGxvd3Mgd2hhdCBpcyBkZXNjcmliZWQgaW4gW1JGQzUxNTRdIGFuZA0KPiAgICBbUkZD
NTEyMV0uICBJbiBhIG51dHNoZWxsLCBlYWNoIE1TIGlzIGF0dGFjaGVkIHRvIGFuIEFjY2VzcyBS
b3V0ZXINCg0KUGxlYXNlIGNsYXJpZnkgJ01TJzsgYWNjb3JkaW5nIHRvIElFRUU4MDIuMTYgaXQg
b25seSBjb3ZlcnMgUEhZIGFuZCBNQUMuDQpBY2NvcmRpbmcgdG8gSUVFRTgwMi4xNiB0aGUgTVMg
aXMgbm90IGEgJ2hvc3QnLg0KDQo+ICAgIChBUikgdGhyb3VnaCBhIEJhc2UgU3RhdGlvbiAoQlMp
LCBhIGxheWVyIDIgZW50aXR5IChmcm9tIHRoZQ0KPiAgICBwZXJzcGVjdGl2ZSBvZiB0aGUgSVB2
NiBsaW5rIGJldHdlZW4gdGhlIE1TIGFuZCBhY2Nlc3Mgcm91dGVyIChBUikpLg0KICAgICAgICAg
ICAgICAgICAgICAgICAgXklQdjQ/Pz8gQ29weSZQYXN0ZSBtaXN0YWtlPw0KPiANCj4gICAgRm9y
IGZ1cnRoZXIgaW5mb3JtYXRpb24gb24gdGhlIHR5cGljYWwgbmV0d29yayBhcmNoaXRlY3R1cmUs
IHNlZQ0KPiAgICBbUkZDNTEyMV0gc2VjdGlvbiA1Lg0KPiANCj4gMy4xLiAgSUVFRSA4MDIuMTYg
SVB2NCBDb252ZXJnZW5jZSBzdWItbGF5ZXIgc3VwcG9ydA0KPiANCj4gICAgQXMgZGVzY3JpYmVk
IGluIFtSRkM1MTU0XSBzZWN0aW9uIDMuMy4sIGFuIElQIHNwZWNpZmljIHN1YnBhcnQNCj4gICAg
Y2xhc3NpZmllciBjYXJyaWVzIGVpdGhlciBJUHY0IG9yIElQdjYgcGF5bG9hZHMuICBJbiB0aGlz
IGRvY3VtZW50LA0KPiAgICB3ZSBhcmUgZm9jdXNpbmcgb24gdGhlIElQdjQgb3ZlciBJUCBDb252
ZXJnZW5jZSBTdWJsYXllci4NCg0KU2VjdGlvbiAzLjMgb2YgW1JGQzUxNTRdIGlzIG91dGRhdGVk
ISBJRUVFODAyLjE2LTIwMDkgaW50cm9kdWNlZCBhIHJlZmluZWQgQ1Mgc3RydWN0dXJlLiBJTUhP
LCB3ZSBzaG91bGRuJ3QgbWFrZSByZWZlcmVuY2VzIHRvIG91dGRhdGVkIHNwZWNpZmljYXRpb25z
LCBidXQgYmFzZSB0aGUgd29yayBvbiB0aGUgbW9zdCByZWNlbnQgSUVFRTgwMi4xNiBzcGVjaWZp
Y2F0aW9uLg0KDQo+IA0KPiANCj4gDQo+IA0KPiBNYWRhbmFwYWxsaSwgZXQgYWwuICAgICAgIEV4
cGlyZXMgQXByaWwgNCwgMjAwOSAgICAgICAgICAgICAgICAgW1BhZ2UgM10NCj4gDA0KPiBJbnRl
cm5ldC1EcmFmdCAgICAgICAgSVB2NCBvdmVyIElFRUUgODAyLjE2J3MgSVAgQ1MgICAgICAgICBP
Y3RvYmVyIDIwMDgNCj4gDQo+IA0KPiAgICBGb3IgZnVydGhlciBpbmZvcm1hdGlvbiBvbiB0aGUg
SUVFRSA4MDIuMTYgQ29udmVyZ2VuY2UgU3VibGF5ZXIgYW5kDQo+ICAgIGVuY2Fwc3VsYXRpb24g
b2YgSVAgcGFja2V0cywgc2VlIFtSRkM1MTIxXSBzZWN0aW9uIDQgYW5kIFtSRkM1MTU0XQ0KPiAg
ICBzZWN0aW9uIDMuMy4NCg0KQXMgW1JGQzUxNTRdIGlzIG91dGRhdGVkLCBJIHdvdWxkIHByb3Bv
c2UgdG8gcHJvdmlkZSBhbiB1cGRhdGVkIHNlY3Rpb24gMy4zLiBhcyBwYXJ0IG9mIHRoZSBJUHY0
IENTIGRvY3VtZW50Lg0KDQo+IDQuICBJUHY0IENTIGxpbmsgaW4gODAyLjE2IE5ldHdvcmtzDQo+
IA0KPiAgICBUaGlzIGRvY3VtZW50IGRlZmluZXMgdGhlIElQdjQgQ1MgbGluayBhcyBhIHBvaW50
LXRvLXBvaW50IGxpbmsNCj4gICAgYmV0d2VlbiB0aGUgTVMgYW5kIHRoZSBBUiB1c2luZyBhIHNl
dCBvZiBzZXJ2aWNlIGZsb3dzIGNvbnNpc3Rpbmcgb2YNCg0KTVMgaXMgbm90IHRoZSBob3N0LiBX
aGF0IGlzIGEgbGluayBiZXR3ZWVuIGEgTDIgZGV2aWNlIChNUykgYW5kIGEgTDMgZGV2aWNlIChB
Uik/DQoNCj4gICAgTUFDIHRyYW5zcG9ydCBjb25uZWN0aW9ucyBiZXR3ZWVuIGEgTVMgYW5kIEJT
LCBhbmQgTDIgdHVubmVsKHMpDQo+ICAgIGJldHdlZW4gYmV0d2VlbiBhIEJTIGFuZCBBUi4gIEl0
IGlzIHJlY29tbWVuZGVkIHRoYXQgYSB0dW5uZWwgYmUNCiAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBeaXMNCj4gICAgZXN0
YWJsaXNoZWQgYmV0d2VlbiB0aGUgQVIgYW5kIGEgQlMgYmFzZWQgb24gJ3BlciBNUycgb3IgJ3Bl
ciBzZXJ2aWNlDQo+ICAgIGZsb3cnIChBbiBNUyBjYW4gaGF2ZSBtdWx0aXBsZSBzZXJ2aWNlIGZs
b3dzIGVhY2ggb2Ygd2hpY2ggYXJlDQoNCldoYXQgaXMgYSB0dW5uZWwgYmV0d2VlbiBCUyBhbmQg
QVIgYmFzZWQgb24gJ3BlciBNUyc/IEl0IHNlZW1zLCBzb21lIEdSRSBmdW5jdGlvbmFsaXR5IGlz
IGFzc3VtZWQgaGVyZSB3aXRob3V0IHNwZWxsaW5nIGl0IG91dC4NCg0KPiAgICBpZGVudGlmaWVk
IGJ5IGEgdW5pcXVlIHNlcnZpY2UgZmxvdyBJRCkuICBUaGVuIHRoZSB0dW5uZWwocykgZm9yIGFu
DQo+ICAgIE1TLCBpbiBjb21iaW5hdGlvbiB3aXRoIHRoZSBNUydzIE1BQyB0cmFuc3BvcnQgY29u
bmVjdGlvbnMsIGZvcm1zIGENCj4gICAgc2luZ2xlIHBvaW50LXRvLXBvaW50IGxpbmsuICBFYWNo
IE1TIGJlbG9uZ3MgdG8gYSBkaWZmZXJlbnQgbGluayBhbmQNCg0KSG93IGRvZXMgdGhpcyB3b3Jr
IC0gbXVsdGlwbGUgdHVubmVscyBiZXR3ZWVuIHR3byBlbmRwb2ludHMgZm9ybWluZyBhIHNpbmds
ZSBsaW5rPyBJIHdvdWxkIGFzc3VtZSwgdGhhdCB0aGVyZSBtdXN0IGJlIHNvbWUgY2xhc3NpZmlj
YXRpb24gaW4gcGxhY2UsIHdoaWNoIGlzIHBhcnQgb2YgdGhlIEJTIGFjY29yZGluZyB0byBJRUVF
ODAyLjE2LCBub3QgcGFydCBvZiB0aGUgQVIsIGxpa2UgdGhlIGF1dGhvcnMgYXNzdW1lIGluIHRo
ZSBzZW50ZW5jZS4NCg0KPiAgICBpcyBhc3NpZ25lZCBhbiB1bmlxdWUgSVB2NCBhZGRyZXNzIHBl
ciByZWNvbW1lbmRhdGlvbnMgaW4gW1JGQzQ5NjhdLg0KPiANCj4gICAgVG8gc3VtbWFyaXplOg0K
PiANCj4gICAgbyAgSVB2NCBDUyB1c2VzIHRoZSBJUHY0IGhlYWRlciBmaWVsZHMgdG8gY2xhc3Np
ZnkgdGhlIHBhY2tldHMgYW5kDQo+ICAgICAgIG1hcCB0byB0aGUgYXBwcm9wcmlhdGUgQ0lELg0K
DQpUaGUgcHJldmlvdXMgdGV4dCB0YWxrcyBhYm91dCBzZXJ2aWNlIGZsb3dzOyB3aHkgJ0NJRCcg
aXMgbWVudGlvbmVkIGhlcmU/DQoNCj4gICAgbyAgQSBwb2ludC10by1wb2ludCBsaW5rIGJldHdl
ZW4gTVMgYW5kIEFSIGlzIGVzdGFibGlzaGVkLg0KDQpIb3cgZG8gdGhlIHR3byBzdGF0ZW1lbnRz
IGZpdCB0b2dldGhlcj8gSG93IGRvZXMgSVB2NCBDUyBlc3RhYmxpc2ggYSBwMnAgbGluaz8NCg0K
PiANCj4gNC4xLiAgSVB2NCBDUyBsaW5rIGVzdGFibGlzaG1lbnQNCj4gDQo+ICAgIEluIG9yZGVy
IHRvIGVuYWJsZSB0aGUgc2VuZGluZyBhbmQgcmVjZWl2aW5nIG9mIElQdjQgcGFja2V0cyBiZXR3
ZWVuDQo+ICAgIHRoZSBNUyBhbmQgdGhlIEFSLCB0aGUgbGluayBiZXR3ZWVuIHRoZSBNUyBhbmQg
dGhlIEFSIHZpYSB0aGUgQlMNCj4gICAgbmVlZHMgdG8gYmUgZXN0YWJsaXNoZWQuICBUaGlzIHNl
Y3Rpb24gZXhwbGFpbnMgdGhlIGxpbmsNCj4gICAgZXN0YWJsaXNobWVudCBwcm9jZWR1cmVzIGZv
bGxvd2luZyBzZWN0aW9uIDYuMiBvZiBbUkZDNTEyMV0uICBTdGVwcw0KPiAgICAxLTQgYXJlIHNh
bWUgYXMgaW5kaWNhdGVkIGluIDYuMiBvZiBbUkZDNTEyMV0uICBJbiBzdGVwIDUsIHN1cHBvcnQN
Cj4gICAgZm9yIElQdjQgaXMgaW5kaWNhdGVkLiAgSW4gc3RlcCA2LCBhbiBpbml0aWFsIHNlcnZp
Y2UgZmxvdyBpcyBjcmVhdGVkDQoNCkluaXRpYWwgc2VydmljZSBmbG93PyBbUkZDNTEyMV0gZG9l
cyBub3Qgc3BlY2lmaWVzIGZ1cnRoZXIgc2VydmljZSBmbG93cy4NCg0KPiAgICB0aGF0IGNhbiBi
ZSB1c2VkIGZvciBleGNoYW5naW5nIElQIGxheWVyIHNpZ25hbGluZyBtZXNzYWdlcywgZS5nLg0K
PiAgICBhZGRyZXNzIGFzc2lnbm1lbnQgcHJvY2VkdXJlcyB1c2luZyBESENQLg0KPiANCj4gICAg
VGhlIGFkZHJlc3MgYXNzaWdubWVudCBwcm9jZWR1cmUgZGVwZW5kcyBvbiB0aGUgTVMgbW9kZSAt
IGksZS4NCj4gICAgd2hldGhlciBpdCBpcyBhY3RpbmcgYXMgYSBNb2JpbGUgSVB2NCBjbGllbnQg
b3IgYSBQcm94eSBNb2JpbGUgSVANCj4gICAgY2xpZW50IG9yIGEgU2ltcGxlIElQIGNsaWVudC4g
IEluIHRoZSBtb3N0IGNvbW1vbiBjYXNlLCB0aGUgTVMNCj4gICAgcmVxdWVzdHMgYW4gSVAgYWRk
cmVzcyB1c2luZyBESENQLg0KDQpXaGF0IGlzIHRoZSBkaWZmZXJlbmNlIGJldHdlZW4gYSBQcm94
eSBNSVAgY2xpZW50IGFuZCBhIFNpbXBsZSBJUCBjbGllbnQ/DQpEb2VzIHRoZSAnTVMnIHJlcXVl
c3QgYW4gSVAgYWRkcmVzcyBieSBESENQIGluIHRoZSBjYXNlIG9mIENsaWVudC1NSVA/DQoNCj4g
DQo+IDQuMi4gIEZyYW1lIEZvcm1hdCBmb3IgSVB2NCBQYWNrZXRzDQo+IA0KPiAgICBJUHY0IHBh
Y2tldHMgYXJlIHRyYW5zbWl0dGVkIGluIEdlbmVyaWMgSUVFRSA4MDIuMTYgTUFDIGZyYW1lcyBp
biB0aGUNCj4gICAgZGF0YSBwYXlsb2FkcyBvZiB0aGUgODAyLjE2IFBEVSAoIHNlZSBzZWN0aW9u
IDMuMiBvZiBbUkZDNTE1NF0gKS4NCj4gDQo+IA0KPiANCj4gDQo+IA0KPiANCj4gDQo+IE1hZGFu
YXBhbGxpLCBldCBhbC4gICAgICAgRXhwaXJlcyBBcHJpbCA0LCAyMDA5ICAgICAgICAgICAgICAg
ICBbUGFnZSA0XQ0KPiAMDQo+IEludGVybmV0LURyYWZ0ICAgICAgICBJUHY0IG92ZXIgSUVFRSA4
MDIuMTYncyBJUCBDUyAgICAgICAgIE9jdG9iZXIgMjAwOA0KPiANCj4gDQo+ICAgICAgICAgICAg
ICAgICAgICAgICAgIDAgICAgICAgICAgICAgICAgICAgMQ0KPiAgICAgICAgICAgICAgICAgICAg
ICAgICAwIDEgMiAzIDQgNSA2IDcgOCA5IDAgMSAyIDMgNCA1DQo+ICAgICAgICAgICAgICAgICAg
ICAgICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rDQo+ICAgICAgICAgICAgICAg
ICAgICAgICAgfEh8RXwgICBUWVBFICAgIHxSfEN8RUtTfFJ8TEVOICB8DQo+ICAgICAgICAgICAg
ICAgICAgICAgICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rDQo+ICAgICAgICAg
ICAgICAgICAgICAgICAgfCAgICBMRU4gTFNCICAgIHwgICAgQ0lEIE1TQiAgICB8DQo+ICAgICAg
ICAgICAgICAgICAgICAgICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rDQo+ICAg
ICAgICAgICAgICAgICAgICAgICAgfCAgICBDSUQgTFNCICAgIHwgICAgSENTICAgICAgICB8DQo+
ICAgICAgICAgICAgICAgICAgICAgICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
DQo+ICAgICAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICBJUHY0ICAgICAgICAgICAg
ICB8DQo+ICAgICAgICAgICAgICAgICAgICAgICAgKy0gICAgICAgICAgICAgICAgICAgICAgICAg
ICAgIC0rDQo+ICAgICAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgIGhlYWRlciAgICAg
ICAgICAgICB8DQo+ICAgICAgICAgICAgICAgICAgICAgICAgKy0gICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIC0rDQo+ICAgICAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICBhbmQg
ICAgICAgICAgICAgICB8DQo+ICAgICAgICAgICAgICAgICAgICAgICAgKy0gICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIC0rDQo+ICAgICAgICAgICAgICAgICAgICAgICAgLyAgICAgICAgICAg
IHBheWxvYWQgICAgICAgICAgIC8NCj4gICAgICAgICAgICAgICAgICAgICAgICArLSAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgLSsNCj4gICAgICAgICAgICAgICAgICAgICAgICB8ICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIHwNCj4gICAgICAgICAgICAgICAgICAgICAgICArLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsNCj4gICAgICAgICAgICAgICAgICAgICAgICB8
Q1JDIChvcHRpb25hbCkgfA0KPiAgICAgICAgICAgICAgICAgICAgICAgICstKy0rLSstKy0rLSst
Ky0rDQo+IA0KPiANCj4gICAgICAgICAgRmlndXJlIDE6IElFRUUgODAyLjE2IE1BQyBGcmFtZSBG
b3JtYXQgZm9yICBJUHY0IFBhY2tldHMNCj4gDQo+ICAgICAgIEg6IEhlYWRlciBUeXBlICgxIGJp
dCkuICBTaGFsbCBiZSBzZXQgdG8gemVybyBpbmRpY2F0aW5nIHRoYXQgaXQNCj4gICAgICAgaXMg
YSBHZW5lcmljIE1BQyBQRFUuDQo+ICAgICAgIEU6IEVuY3J5cHRpb24gQ29udHJvbC4gMCA9IFBh
eWxvYWQgaXMgbm90IGVuY3J5cHRlZDsgMSA9IFBheWxvYWQNCj4gICAgICAgaXMgZW5jcnlwdGVk
Lg0KPiAgICAgICBSOiBSZXNlcnZlZC4gIFNoYWxsIGJlIHNldCB0byB6ZXJvLg0KPiAgICAgICBD
OiBDUkMgSW5kaWNhdG9yLiAxID0gQ1JDIGlzIGluY2x1ZGVkLCAwID0gMSBObyBDUkMgaXMgaW5j
bHVkZWQNCj4gICAgICAgRUtTOiBFbmNyeXB0aW9uIEtleSBTZXF1ZW5jZQ0KPiAgICAgICBMRU46
IFRoZSBMZW5ndGggaW4gYnl0ZXMgb2YgdGhlIE1BQyBQRFUgaW5jbHVkaW5nIHRoZSBNQUMgaGVh
ZGVyDQo+ICAgICAgIGFuZCB0aGUgQ1JDIGlmIHByZXNlbnQgKDExIGJpdHMpDQo+ICAgICAgIENJ
RDogQ29ubmVjdGlvbiBJZGVudGlmaWVyICgxNiBiaXRzKQ0KPiAgICAgICBIQ1M6IEhlYWRlciBD
aGVjayBTZXF1ZW5jZSAoOCBiaXRzKQ0KPiAgICAgICBDUkM6IEFuIG9wdGlvbmFsIDgtYml0IGZp
ZWxkLiAgQ1JDIGFwcGVuZGVkIHRvIHRoZSBQRFUgYWZ0ZXINCj4gICAgICAgZW5jcnlwdGlvbi4N
Cj4gICAgICAgVFlQRTogVGhpcyBmaWVsZCBpbmRpY2F0ZXMgdGhlIHN1YmhlYWRlcnMgKE1lc2gg
c3ViaGVhZGVyLA0KPiAgICAgICBGcmFnbWVudGF0aW9uIFN1YmhlYWRlciwgUGFja2luZyBzdWJo
ZWFkZXIgZXRjIGFuZCBzcGVjaWFsIHBheWxvYWQNCj4gICAgICAgdHlwZXMgKEFSUSkgcHJlc2Vu
dCBpbiB0aGUgbWVzc2FnZSBwYXlsb2FkDQo+IA0KPiA0LjMuICBNYXhpbXVtIFRyYW5zbWlzc2lv
biBVbml0DQo+IA0KPiAgICAgICBUaGUgTVRVIHZhbHVlIGZvciBJUHY0IHBhY2tldHMgb24gYW4g
SUVFRSA4MDIuMTYgbGluayBpcw0KPiAgICBjb25maWd1cmFibGUuICBUaGUgZGVmYXVsdCBNVFUg
Zm9yIElQdjQgcGFja2V0cyBvdmVyIGFuIElFRUUgODAyLjE2DQoNCidpcyBjb25maWd1cmFibGUn
Pz8gSG93LCBieSB3aGljaCBtZWFucz8/DQoNCj4gICAgICAgbGluayBTSE9VTEQgYmUgMTUwMCBv
Y3RldHMuDQo+IA0KPiANCj4gDQo+IA0KPiBNYWRhbmFwYWxsaSwgZXQgYWwuICAgICAgIEV4cGly
ZXMgQXByaWwgNCwgMjAwOSAgICAgICAgICAgICAgICAgW1BhZ2UgNV0NCj4gDA0KPiBJbnRlcm5l
dC1EcmFmdCAgICAgICAgSVB2NCBvdmVyIElFRUUgODAyLjE2J3MgSVAgQ1MgICAgICAgICBPY3Rv
YmVyIDIwMDgNCj4gDQo+IA0KPiAgICBQZXIgW1JGQzUxMjFdIHNlY3Rpb24gNi4zLCB0aGUgSVAg
TVRVIGNhbiB2YXJ5IHRvIGJlIGxhcmdlciBvcg0KPiAgICBzbWFsbGVyIHRoYW4gMTUwMCBvY3Rl
dHMuDQo+IA0KPiAgICBpZiBhbiBNUyB0cmFuc21pdHMgMTUwMC1vY3RldCBwYWNrZXRzIGluIGEg
ZGVwbG95bWVudCB3aXRoIGEgc21hbGxlcg0KPiAgICBNVFUsIHBhY2tldHMgZnJvbSB0aGUgTVMg
bWF5IGJlIGRyb3BwZWQgYXQgdGhlIGxpbmstbGF5ZXIgc2lsZW50bHkuDQo+ICAgIFVubGlrZSBJ
UHY2LCBpbiB3aGljaCBkZXBhcnR1cmVzIGZyb20gdGhlIGRlZmF1bHQgTVRVIGFyZSByZWFkaWx5
DQo+ICAgIGFkdmVydGlzZWQgdmlhIHRoZSBNVFUgb3B0aW9uIGluIE5laWdoYm9yIERpc2NvdmVy
eSwgdGhlcmUgaXMgbm8NCj4gICAgc2ltaWxhcmx5IHJlbGlhYmxlIG1lY2hhbmlzbSBpbiBJUHY0
LCBhcyB0aGUgbGVnYWN5IElQdjQgY2xpZW50DQo+ICAgIGltcGxlbWVudGF0aW9ucyBkbyBub3Qg
ZGV0ZXJtaW5lIHRoZSBsaW5rIE1UVSBieSBkZWZhdWx0IGJlZm9yZQ0KPiAgICBzZW5kaW5nIHBh
Y2tldHMuICBFdmVuIHRob3VnaCB0aGVyZSBpcyBhIERIQ1Agb3B0aW9uIHRvIGFjY29tcGxpc2gN
Cj4gICAgdGhpcywgREhDUCBzZXJ2ZXJzIGFyZSByZXF1aXJlZCB0byBwcm92aWRlIHRoZSBNVFUg
aW5mb3JtYXRpb24gb25seQ0KPiAgICB3aGVuIHJlcXVlc3RlZC4NCj4gDQo+ICAgIERpc2NvdmVy
eSBhbmQgY29uZmlndXJhdGlvbiBvZiB0aGUgcHJvcGVyIGxpbmsgTVRVIHZhbHVlIGVuc3VyZXMN
Cj4gICAgYWRlcXVhdGUgdXNhZ2Ugb2YgdGhlIG5ldHdvcmsgYmFuZHdpZHRoIGFuZCByZXNvdXJj
ZXMuICBBY2NvcmRpbmdseSwNCj4gICAgZGVwbG95bWVudHMgc2hvdWxkIGF2b2lkIHBhY2tldCBs
b3NzIGR1ZSB0byBhIG1pc21hdGNoIGJldHdlZW4gdGhlDQo+ICAgIGRlZmF1bHQgTVRVIGFuZCB0
aGUgY29uZmlndXJlZCBsaW5rIE1UVXMuDQo+IA0KPiAgICAgICBTb21lIG9mIHRoZSBtZWNoYW5p
c21zIGF2YWlsYWJsZSBmb3IgdGhlIElQdjQgQ1MgaG9zdCB0byBmaW5kIG91dA0KPiAgICB0aGUg
bGluaydzIE1UVSB2YWx1ZSBhbmQgbWl0aWdhdGUgTVRVLXJlbGF0ZWQgaXNzdWVzIGFyZToNCj4g
DQo+ICAgIG8gIFRoZSBJRUVFIGlzIGN1cnJlbnRseSByZXZpc2luZyA4MDIuMTYgKHNlZSA4MDIu
MTZSZXYyDQoNCklFRUU4MDIuMTYgaGFzIHJldmlzZWQgdGhlIHNwZWNpZmljYXRpb24uIFVwZGF0
ZSB0aGUgcmVmZXJlbmNlLg0KDQo+ICAgICAgIFs4MDJfMTZSRVYyXSkgdG8gKGFtb25nIG90aGVy
IHRoaW5ncykgYWxsb3cgcHJvdmlkaW5nIHRoZSBTZXJ2aWNlDQo+ICAgICAgIERhdGEgVW5pdCBv
ciBNQUMgTVRVIGluIHRoZSBJRUVFIDgwMi4xNiBTQkMtUkVRL1NCQy1SU1AgcGhhc2UsDQo+ICAg
ICAgIHN1Y2ggdGhhdCBmdXR1cmUgSUVFRSA4MDIuMTYgY29tcGxpYW50IGNsaWVudHMgY2FuIGlu
ZmVyIGFuZA0KPiAgICAgICBjb25maWd1cmUgdGhlIG5lZ290aWF0ZWQgTVRVIHNpemUgZm9yIHRo
ZSBJUHY0IENTIGxpbmsuICBIb3dldmVyLA0KPiAgICAgICB0aGUgaW1wbGVtZW50YXRpb24gbXVz
dCBjb21tdW5pY2F0ZSB0aGUgbmVnb3RpYXRlZCBNVFUgdmFsdWUgdG8NCj4gICAgICAgdGhlIElQ
IGxheWVyIHRvIGFkanVzdCB0aGUgSVAgTWF4aW11bSBwYXlsb2FkIHNpemUgZm9yIHByb3Blcg0K
PiAgICAgICBoYW5kbGluZyBvZiBmcmFnbWVudGF0aW9uLiAgTm90ZSB0aGF0IHRoaXMgbWV0aG9k
IGlzIHVzZWZ1bCBvbmx5DQo+ICAgICAgIHdoZW4gTVMgaXMgZGlyZWN0bHkgY29ubmVjdGVkIHRv
IHRoZSBCUy4NCj4gICAgbyAgQ29uZmlndXJhdGlvbiBhbmQgbmVnb3RpYXRpb24gb2YgTVRVIHNp
emUgYXQgdGhlIG5ldHdvcmsgbGF5ZXIgYnkNCj4gICAgICAgdXNpbmcgdGhlIERIQ1AgaW50ZXJm
YWNlIE1UVSBvcHRpb24gW1JGQzIxMzJdLg0KPiANCj4gICAgVGhpcyBkb2N1bWVudCByZWNvbW1l
bmRzIHRoYXQgYWxsIGZ1dHVyZSBpbXBsZW1lbnRhdGlvbnMgb2YgSVB2NCBhbmQNCg0KV2h5ICdm
dXR1cmUnPw0KDQo+ICAgIElQdjQgQ1MgY2xpZW50cyBTSE9VTEQgaW1wbGVtZW50IHRoZSBESENQ
IGludGVyZmFjZSBNVFUgb3B0aW9uDQo+ICAgIFtSRkMyMTMyXSBpbiBvcmRlciB0byBjb25maWd1
cmUgaXRzIGludGVyZmFjZSBNVFUgYWNjb3JkaW5nbHkuDQo+IA0KPiAgICBJbiB0aGUgYWJzZW5j
ZSBvZiBESENQIE1UVSBjb25maWd1cmF0aW9uLCB0aGUgY2xpZW50IG5vZGUgKE1TKSBoYXMNCj4g
ICAgdHdvIGFsdGVybmF0aXZlczogMSkgdXNlIHRoZSBkZWZhdWx0IE1UVSAoMTUwMCBieXRlcykg
b3IgMikgZGV0ZXJtaW5lDQo+ICAgIHRoZSBNVFUgYnkgdGhlIG1ldGhvZHMgZGVzY3JpYmVkIGlu
IFs4MDJfMTZSRVYyXS4NCg0KQ2FuIE1TIHJlbHkgb24gdGhlIElFRUU4MDIuMTYgbWV0aG9kcz8g
TWFuZGF0b3J5IGZvciBhbGwgSUVFRTgwMi4xNiBpbXBsZW1lbnRhdGlvbnM/DQoNCj4gICAgQWRk
aXRpb25hbGx5LCB0aGUgY2xpZW50cyBhcmUgZW5jb3VyYWdlZCB0byBydW4gUE1UVVtSRkMgMTE5
MV0gb3INCj4gICAgUFBNVFVEW1JGQyA0ODIxXS4gIEhvd2V2ZXIsIHRoZSBQTVRVIG1lY2hhbmlz
bSBoYXMgaW5oZXJlbnQgcHJvYmxlbXMNCj4gICAgb2YgcGFja2V0IGxvc3MgZHVlIHRvIElDTVAg
bWVzc2FnZXMgbm90IHJlYWNoaW5nIHRoZSBzZW5kZXIgYW5kIElQdjQNCj4gICAgcm91dGVycyBu
b3QgZnJhZ21lbnRpbmcgdGhlIHBhY2tldHMgZHVlIHRvIHRoZSBERiBiaXQgYmVpbmcgc2V0IGlu
DQo+ICAgIHRoZSBJUCBwYWNrZXQuICBUaGUgYWJvdmUgbWVudGlvbmVkIHBhdGggTVRVIG1lY2hh
bmlzbXMgd2lsbCB0YWtlDQo+ICAgIGNhcmUgb2YgdGhlIE1UVSBzaXplIGJldHdlZW4gdGhlIE1T
IGFuZCBpdHMgY29ycmVzcG9uZGVudCBub2RlIGFjcm9zcw0KPiAgICBkaWZmZXJlbnQgZmxhdm9y
cyBvZiBjb252ZXJnZW5jZSBsYXllcnMgaW4gdGhlIGFjY2VzcyBuZXR3b3Jrcy4NCj4gDQo+IA0K
PiANCj4gTWFkYW5hcGFsbGksIGV0IGFsLiAgICAgICBFeHBpcmVzIEFwcmlsIDQsIDIwMDkgICAg
ICAgICAgICAgICAgIFtQYWdlIDZdDQo+IAwNCj4gSW50ZXJuZXQtRHJhZnQgICAgICAgIElQdjQg
b3ZlciBJRUVFIDgwMi4xNidzIElQIENTICAgICAgICAgT2N0b2JlciAyMDA4DQo+IA0KPiANCj4g
NS4gIFN1Ym5ldCBNb2RlbCBhbmQgSVB2NCBBZGRyZXNzIEFzc2lnbm1lbnQNCj4gDQo+ICAgIFRo
ZSBTdWJuZXQgTW9kZWwgcmVjb21tZW5kZWQgZm9yIElQdjQgb3ZlciBJRUVFIDgwMi4xNiB1c2lu
ZyBJUCBDUyBpcw0KPiAgICBiYXNlZCBvbiB0aGUgcG9pbnQtdG8tcG9pbnQgbGluayBiZXR3ZWVu
IE1TIGFuZCBBUiBbUkZDNDk2OF0sIGhlbmNlDQo+ICAgIGVhY2ggTVMgc2hhbGwgYmUgYXNzaWdu
ZWQgYW4gYWRkcmVzcyB3aXRoIDMyYml0IHByZWZpeC1sZW5ndGggb3INCj4gICAgc3VibmV0LW1h
c2suICBUaGUgcG9pbnQtdG8tcG9pbnQgbGluayBiZXR3ZWVuIE1TIGFuZCBBUiBpcyBhY2hpZXZl
ZA0KPiAgICB1c2luZyBhIHNldCBvZiBJRUVFIDgwMi4xNiBNQUMgY29ubmVjdGlvbnMgKGlkZW50
aWZpZWQgYnkgQ0lEcykgYW5kDQo+ICAgIGFuIEwyIHR1bm5lbCAoZS5nLiwgYSBHUkUgdHVubmVs
KSBwZXIgTVMgYmV0d2VlbiBCUyBhbmQgQVIuICBJZiB0aGUNCj4gICAgQVIgaXMgY28tbG9jYXRl
ZCB3aXRoIHRoZSBCUywgdGhlbiB0aGUgc2V0IG9mIElFRUUgODAyLjE2IE1BQw0KPiAgICBjb25u
ZWN0aW9ucyBiZXR3ZWVuIHRoZSBNUyBhbmQgQlMvQVIgcmVwcmVzZW50IHRoZSBwb2ludC10by0g
cG9pbnQNCj4gICAgY29ubmVjdGlvbi4NCj4gDQo+IDUuMS4gIElQdjQgVW5pY2FzdCBBZGRyZXNz
IEFzc2lnbm1lbnQgYW5kIFJvdXRlciBEaXNjb3ZlcnkNCj4gDQo+ICAgIERIQ1AgW1JGQzIxMzFd
IFNIT1VMRCBiZSB1c2VkIGZvciBhc3NpZ25pbmcgSVB2NCBhZGRyZXNzIGZvciB0aGUgTVMuDQo+
ICAgIERIQ1AgbWVzc2FnZXMgYXJlIHRyYW5zcG9ydGVkIG92ZXIgdGhlIElFRUUgODAyLjE2IE1B
QyBjb25uZWN0aW9uIHRvDQo+ICAgIGFuZCBmcm9tIHRoZSBCUyBhbmQgcmVsYXllZCB0byB0aGUg
QVIuICBJbiBjYXNlIHRoZSBESENQIHNlcnZlciBkb2VzDQo+ICAgIG5vdCByZXNpZGUgaW4gdGhl
IEFSLCB0aGUgQVIgU0hPVUxEIGltcGxlbWVudCBESENQIHJlbGF5IEFnZW50DQo+ICAgIFtSRkMx
NTQyXS4NCj4gDQo+ICAgIEFsdGhvdWdoIERIQ1AgaXMgdGhlIHJlY29tbWVuZGVkIG1ldGhvZCBv
ZiBhZGRyZXNzIGFzc2lnbm1lbnQsIGl0IGlzDQo+ICAgIHBvc3NpYmxlIHRoYXQgdGhlIE1TIGNv
dWxkIGJlIGEgcHVyZSBNb2JpbGUgSVB2NCBbUkZDMzM0NF0gZGV2aWNlDQo+ICAgIHdoaWNoIHdp
bGwgYmUgb2ZmZXJlZCBhbiBJUCBhZGRyZXNzIGZyb20gaXRzIGhvbWUgbmV0d29yayBhZnRlcg0K
PiAgICBzdWNjZXNzZnVsIE1vYmlsZSBJUCBbUkZDMzM0NF0gcmVnaXN0cmF0aW9uLiAgSW4gc3Vj
aCBzaXR1YXRpb25zLCB0aGUNCj4gICAgbW9iaWxlIGhvc3QgU0hPVUxEIHVzZSB0aGUgZGVmYXVs
dCBsaW5rIE1UVSBpbiBvcmRlciB0byBhdm9pZCBhbnkNCj4gICAgbGluay1sYXllciBwYWNrZXQg
bG9zcyBkdWUgdG8gbGFyZ2VyIHRoYW4gc3VwcG9ydGVkIHBhY2tldCBzaXplIGluDQo+ICAgIHRo
ZSBJUCBDUyBsaW5rLg0KPiANCj4gICAgUm91dGVyIGRpc2NvdmVyeSBtZXNzYWdlcyBbUkZDMTI1
Nl0gY29udGFpbiByb3V0ZXIgc29saWNpdGF0aW9uIGFuZA0KPiAgICByb3V0ZXIgYWR2ZXJ0aXNl
bWVudHMuICBUaGUgUm91dGVyIHNvbGljaXRhdGlvbiBtZXNzYWdlcyAobXVsdGljYXN0DQo+ICAg
IG9yIGJyb2FkY2FzdCkgZnJvbSB0aGUgTVMgYXJlIGRlbGl2ZXJlZCB0byB0aGUgQVIgdmlhIHRo
ZSBCUyB0aHJvdWdoDQo+ICAgIHRoZSBwb2ludC10by1wb2ludCBsaW5rLiAgVGhlIEJTIFNIT1VM
RCBtYXAgdGhlIGFsbC1yb3V0ZXJzIG11bHRpY2FzdA0KPiAgICBub2RlcyBvciBicm9hZGNhc3Qg
bm9kZXMgZm9yIHJvdXRlciBkaXNjb3ZlcnkgdG8gdGhlIEFSJ3MgSVAgYWRkcmVzcw0KPiAgICBh
bmQgZGVsaXZlciBkaXJlY3RseSB0byB0aGUgQVIuICBTaW1pbGFybHkgYSByb3V0ZXIgYWR2ZXJ0
aXNlbWVudCB0bw0KPiAgICB0aGUgYWxsLW5vZGVzIG11bHRpY2FzdCBub2RlcyB3aWxsIGJlIGVp
dGhlciB1bmljYXN0IHRvIGVhY2ggTVMgYnkNCj4gICAgdGhlIEJTIHNlcGFyYXRlbHkgb3IgcHV0
IG9udG8gYSBtdWx0aWNhc3QgY29ubmVjdGlvbiB0byB3aGljaCBhbGwgTVNzDQo+ICAgIGFyZSBs
aXN0ZW5pbmcgdG8uICBJZiBubyBtdWx0aWNhc3QgY29ubmVjdGlvbiBleGlzdHMsIGFuZCB0aGUg
QlMgZG9lcw0KPiAgICBub3QgaGF2ZSB0aGUgY2FwYWJpbGl0eSB0byBhZ2dyZWdhdGUgYW5kIGRp
c2FnZ3JlZ2F0ZSB0aGUgbWVzc2FnZXMgdG8NCj4gICAgYW5kIGZyb20gdGhlIE1TIGhvc3RzLCB0
aGVuIHRoZSBBUiBpbXBsZW1lbnRhdGlvbiBtdXN0IGVuc3VyZSB0aGF0DQo+ICAgIHVuaWNhc3Qg
bWVzc2FnZXMgYXJlIHNlbnQgdG8gdGhlIGNvcnJlc3BvbmRpbmcgaW5kaXZpZHVhbCBNUyBob3N0
cw0KPiAgICB3aXRoaW4gdGhlIHNldCBvZiBicm9hZGNhc3Qgb3IgbXVsdGljYXN0IHJlY2lwaWVu
dHMuICBUaGlzDQo+ICAgIHNwZWNpZmljYXRpb24gc2ltcGx5IGFzc3VtZXMgdGhhdCB0aGUgbXVs
dGljYXN0IHNlcnZpY2UgaXMgcHJvdmlkZWQuDQo+ICAgIEhvdyB0aGUgbXVsdGljYXN0IHNlcnZp
Y2UgaXMgaW1wbGVtZW50ZWQgaW4gYW4gSUVFRSA4MDIuMTYgUGFja2V0IENTDQo+ICAgIGRlcGxv
eW1lbnQgaXMgb3V0IG9mIHNjb3BlIG9mIHRoaXMgZG9jdW1lbnQuDQo+IA0KPiAgICBUaGUgJ05l
eHQgaG9wJyBJUCBhZGRyZXNzIG9mIHRoZSBJUCBDUyBNUyBpcyBhbHdheXMgdGhlIElQIGFkZHJl
c3Mgb2YNCj4gICAgdGhlIEFSLCBiZWNhdXNlIE1TIGFuZCBBUiBhcmUgYXR0YWNoZWQgdmlhIGEg
cG9pbnQtdG8tcG9pbnQgbGluay4NCj4gDQo+IA0KPiANCj4gDQo+IE1hZGFuYXBhbGxpLCBldCBh
bC4gICAgICAgRXhwaXJlcyBBcHJpbCA0LCAyMDA5ICAgICAgICAgICAgICAgICBbUGFnZSA3XQ0K
PiAMDQo+IEludGVybmV0LURyYWZ0ICAgICAgICBJUHY0IG92ZXIgSUVFRSA4MDIuMTYncyBJUCBD
UyAgICAgICAgIE9jdG9iZXIgMjAwOA0KPiANCj4gDQo+IDUuMi4gIEFkZHJlc3MgUmVzb2x1dGlv
biBQcm90b2NvbA0KPiANCj4gICAgVGhlIElQIENTIGRvZXMgbm90IGFsbG93IGZvciB0cmFuc21p
c3Npb24gb2YgQVJQIFtSRkMwODI2XSBwYWNrZXRzLg0KPiAgICBGdXJ0aGVybW9yZSwgaW4gYSBw
b2ludC10by1wb2ludCBsaW5rIG1vZGVsLCBhZGRyZXNzIHJlc29sdXRpb24gaXMNCj4gICAgbm90
IG5lZWRlZC4NCj4gDQo+IDUuMy4gIElQIE11bHRpY2FzdCBBZGRyZXNzIE1hcHBpbmcNCj4gDQo+
ICAgIElQdjQgbXVsdGljYXN0IHBhY2tldHMgYXJlIGNhcnJpZWQgb3ZlciB0aGUgcG9pbnQtdG8t
cG9pbnQgbGluaw0KPiAgICBiZXR3ZWVuIHRoZSBBUiBhbmQgdGhlIE1TICh2aWEgdGhlIEJTKS4g
IFRoZSBJUHY0IG11bHRpY2FzdCBwYWNrZXRzDQo+ICAgIGFyZSBjbGFzc2lmaWVkIG5vcm1hbGx5
IGF0IHRoZSBJUCBDUyBpZiB0aGUgSUVFRSA4MDIuMTYgTUFDDQo+ICAgIGNvbm5lY3Rpb24gaGFz
IGJlZW4gc2V0IHVwIHdpdGggYSBtdWx0aWNhc3QgSVAgYWRkcmVzcyBhcyBhDQo+ICAgIGNsYXNz
aWZpY2F0aW9uIHBhcmFtZXRlciBmb3IgdGhlIGRlc3RpbmF0aW9uIElQIGFkZHJlc3MuICBUaGUg
SVB2NA0KPiAgICBtdWx0aWNhc3QgYWRkcmVzcyBtYXkgYmUgbWFwcGVkIGludG8gYSBtdWx0aWNh
c3QgQ0lEIGFzIGRlZmluZWQgaW4NCj4gICAgdGhlIElFRUUgODAyLjE2IHNwZWNpZmljYXRpb24u
ICBUaGUgbWFwcGluZyBtZWNoYW5pc20gYXQgdGhlIEJTIG9yDQo+ICAgIHRoZSByZWxhdGl2ZSBl
ZmZpY2llbmN5IG9mIHVzaW5nIGEgbXVsdGljYXN0IENJRCBhcyBvcHBvc2VkIHRvDQo+ICAgIHNp
bXVsYXRpbmcgbXVsdGljYXN0IGJ5IGdlbmVyYXRpbmcgbXVsdGlwbGUgdW5pY2FzdCBtZXNzYWdl
cyBhcmUgb3V0DQo+ICAgIG9mIHNjb3BlIG9mIHRoaXMgZG9jdW1lbnQuICBGb3IgZnVydGhlciBj
b25zaWRlcmF0aW9ucyBvbiB0aGUgdXNlIG9mDQo+ICAgIG11bHRpY2FzdCBDSURzIHNlZSBbRVRI
Q1NdLg0KPiANCj4gDQo+IDYuICBTZWN1cml0eSBDb25zaWRlcmF0aW9ucw0KPiANCj4gICAgVGhp
cyBkb2N1bWVudCBzcGVjaWZpZXMgdHJhbnNtaXNzaW9uIG9mIElQdjQgcGFja2V0cyBvdmVyIElF
RUUgODAyLjE2DQo+ICAgIG5ldHdvcmtzIHdpdGggSVB2NCBDb252ZXJnZW5jZSBTdWJsYXllciBh
bmQgZG9lcyBub3QgaW50cm9kdWNlIGFueQ0KPiAgICBuZXcgdnVsbmVyYWJpbGl0aWVzIHRvIElQ
djQgc3BlY2lmaWNhdGlvbnMgb3Igb3BlcmF0aW9uLiAgVGhlDQo+ICAgIHNlY3VyaXR5IG9mIHRo
ZSBJRUVFIDgwMi4xNiBhaXIgaW50ZXJmYWNlIGlzIHRoZSBzdWJqZWN0IG9mDQo+ICAgIFtJRUVF
ODAyXzE2XS4gIEluIGFkZGl0aW9uLCB0aGUgc2VjdXJpdHkgaXNzdWVzIG9mIHRoZSBuZXR3b3Jr
DQo+ICAgIGFyY2hpdGVjdHVyZSBzcGFubmluZyBiZXlvbmQgdGhlIElFRUUgODAyLjE2IGJhc2Ug
c3RhdGlvbnMgaXMgdGhlDQo+ICAgIHN1YmplY3Qgb2YgdGhlIGRvY3VtZW50cyBkZWZpbmluZyBz
dWNoIGFyY2hpdGVjdHVyZXMsIHN1Y2ggYXMgV2lNQVgNCj4gICAgTmV0d29yayBBcmNoaXRlY3R1
cmUgW1dNRl0uDQo+IA0KPiANCj4gNy4gIElBTkEgQ29uc2lkZXJhdGlvbnMNCj4gDQo+ICAgIFRo
aXMgZG9jdW1lbnQgaGFzIG5vIGFjdGlvbnMgZm9yIElBTkEuDQo+IA0KPiANCj4gOC4gIEFja25v
d2xlZGdlbWVudHMNCj4gDQo+ICAgIFRoZSBhdXRob3JzIHdvdWxkIGxpa2UgdG8gYWNrbm93bGVk
Z2UgdGhlIGNvbnRyaWJ1dGlvbnMgb2YgQmVybmFyZA0KPiAgICBBYm9iYSwgRGF2ZSBUaGFsZXIs
IEphcmkgQXJra28sIEJhY2hldCBTYXJpa2F5YSwgQmFzYXZhcmFqIFBhdGlsLA0KPiAgICBQYW9s
byBOYXJ2YWV6LCBhbmQgQnJ1bm8gU291c2EgZm9yIHRoZWlyIHJldmlldyBhbmQgY29tbWVudHMu
ICBUaGUNCj4gICAgd29ya2luZyBncm91cCBtZW1iZXJzIEJ1cmNhayBCZXNlciwgV2VzbGV5IEdl
b3JnZSwgTWF4IFJpZWdlbCBhbmQgREoNCj4gICAgSm9obnN0b24gaGVscGVkIHNoYXBlIHRoZSBN
VFUgZGlzY3Vzc2lvbiBmb3IgSVB2NCBDUyBsaW5rLiAgVGhhbmtzIHRvDQo+ICAgIG1hbnkgb3Ro
ZXIgbWVtYmVycyBvZiB0aGUgMTZuZyB3b3JraW5nIGdyb3VwIHdobyBjb21tZW50ZWQgb24gdGhp
cw0KPiAgICBkb2N1bWVudCB0byBtYWtlIGl0IGJldHRlci4NCj4gDQo+IA0KPiANCj4gDQo+IE1h
ZGFuYXBhbGxpLCBldCBhbC4gICAgICAgRXhwaXJlcyBBcHJpbCA0LCAyMDA5ICAgICAgICAgICAg
ICAgICBbUGFnZSA4XQ0KPiAMDQo+IEludGVybmV0LURyYWZ0ICAgICAgICBJUHY0IG92ZXIgSUVF
RSA4MDIuMTYncyBJUCBDUyAgICAgICAgIE9jdG9iZXIgMjAwOA0KPiANCj4gDQo+IDkuICBSZWZl
cmVuY2VzDQo+IA0KPiA5LjEuICBOb3JtYXRpdmUgUmVmZXJlbmNlcw0KPiANCj4gICAgW1JGQzIx
MTldICBCcmFkbmVyLCBTLiwgIktleSB3b3JkcyBmb3IgdXNlIGluIFJGQ3MgdG8gSW5kaWNhdGUN
Cj4gICAgICAgICAgICAgICBSZXF1aXJlbWVudCBMZXZlbHMiLCBCQ1AgMTQsIFJGQyAyMTE5LCBN
YXJjaCAxOTk3Lg0KPiANCj4gICAgW1JGQzA3OTFdICBQb3N0ZWwsIEouLCAiSW50ZXJuZXQgUHJv
dG9jb2wiLCBTVEQgNSwgUkZDIDc5MSwNCj4gICAgICAgICAgICAgICBTZXB0ZW1iZXIgMTk4MS4N
Cj4gDQo+ICAgIFtSRkMwODI2XSAgUGx1bW1lciwgRC4sICJFdGhlcm5ldCBBZGRyZXNzIFJlc29s
dXRpb24gUHJvdG9jb2w6IE9yDQo+ICAgICAgICAgICAgICAgY29udmVydGluZyBuZXR3b3JrIHBy
b3RvY29sIGFkZHJlc3NlcyB0byA0OC5iaXQgRXRoZXJuZXQNCj4gICAgICAgICAgICAgICBhZGRy
ZXNzIGZvciB0cmFuc21pc3Npb24gb24gRXRoZXJuZXQgaGFyZHdhcmUiLCBTVEQgMzcsDQo+ICAg
ICAgICAgICAgICAgUkZDIDgyNiwgTm92ZW1iZXIgMTk4Mi4NCj4gDQo+ICAgIFtSRkMyMTMxXSAg
RHJvbXMsIFIuLCAiRHluYW1pYyBIb3N0IENvbmZpZ3VyYXRpb24gUHJvdG9jb2wiLA0KPiAgICAg
ICAgICAgICAgIFJGQyAyMTMxLCBNYXJjaCAxOTk3Lg0KPiANCj4gICAgW1JGQzE1NDJdICBXaW1l
ciwgVy4sICJDbGFyaWZpY2F0aW9ucyBhbmQgRXh0ZW5zaW9ucyBmb3IgdGhlDQo+ICAgICAgICAg
ICAgICAgQm9vdHN0cmFwIFByb3RvY29sIiwgUkZDIDE1NDIsIE9jdG9iZXIgMTk5My4NCj4gDQo+
ICAgIFtSRkM1MTIxXSAgUGF0aWwsIEIuLCBYaWEsIEYuLCBTYXJpa2F5YSwgQi4sIENob2ksIEpI
LiwgYW5kIFMuDQo+ICAgICAgICAgICAgICAgTWFkYW5hcGFsbGksICJUcmFuc21pc3Npb24gb2Yg
SVB2NiB2aWEgdGhlIElQdjYNCj4gICAgICAgICAgICAgICBDb252ZXJnZW5jZSBTdWJsYXllciBv
dmVyIElFRUUgODAyLjE2IE5ldHdvcmtzIiwgUkZDIDUxMjEsDQo+ICAgICAgICAgICAgICAgRmVi
cnVhcnkgMjAwOC4NCj4gDQo+ICAgIFtSRkM1MTU0XSAgSmVlLCBKLiwgTWFkYW5hcGFsbGksIFMu
LCBhbmQgSi4gTWFuZGluLCAiSVAgb3ZlciBJRUVFDQo+ICAgICAgICAgICAgICAgODAyLjE2IFBy
b2JsZW0gU3RhdGVtZW50IGFuZCBHb2FscyIsIFJGQyA1MTU0LCBBcHJpbCAyMDA4Lg0KPiANCj4g
ICAgW1JGQzQ5NjhdICBNYWRhbmFwYWxsaSwgUy4sICJBbmFseXNpcyBvZiBJUHY2IExpbmsgTW9k
ZWxzIGZvciA4MDIuMTYNCj4gICAgICAgICAgICAgICBCYXNlZCBOZXR3b3JrcyIsIFJGQyA0OTY4
LCBBdWd1c3QgMjAwNy4NCj4gDQo+IDkuMi4gIEluZm9ybWF0aXZlIFJlZmVyZW5jZXMNCj4gDQo+
ICAgIFtSRkMxMTkxXSAgTW9ndWwsIEouIGFuZCBTLiBEZWVyaW5nLCAiUGF0aCBNVFUgZGlzY292
ZXJ5IiwgUkZDIDExOTEsDQo+ICAgICAgICAgICAgICAgTm92ZW1iZXIgMTk5MC4NCj4gDQo+ICAg
IFtSRkM0ODIxXSAgTWF0aGlzLCBNLiBhbmQgSi4gSGVmZm5lciwgIlBhY2tldGl6YXRpb24gTGF5
ZXIgUGF0aCBNVFUNCj4gICAgICAgICAgICAgICBEaXNjb3ZlcnkiLCBSRkMgNDgyMSwgTWFyY2gg
MjAwNy4NCj4gDQo+ICAgIFtSRkMyMTMyXSAgQWxleGFuZGVyLCBTLiBhbmQgUi4gRHJvbXMsICJE
SENQIE9wdGlvbnMgYW5kIEJPT1RQIFZlbmRvcg0KPiAgICAgICAgICAgICAgIEV4dGVuc2lvbnMi
LCBSRkMgMjEzMiwgTWFyY2ggMTk5Ny4NCj4gDQo+ICAgIFtSRkM0ODQwXSAgQWJvYmEsIEIuLCBE
YXZpZXMsIEUuLCBhbmQgRC4gVGhhbGVyLCAiTXVsdGlwbGUNCj4gICAgICAgICAgICAgICBFbmNh
cHN1bGF0aW9uIE1ldGhvZHMgQ29uc2lkZXJlZCBIYXJtZnVsIiwgUkZDIDQ4NDAsDQo+ICAgICAg
ICAgICAgICAgQXByaWwgMjAwNy4NCj4gDQo+ICAgIFtSRkMzMzQ0XSAgUGVya2lucywgQy4sICJJ
UCBNb2JpbGl0eSBTdXBwb3J0IGZvciBJUHY0IiwgUkZDIDMzNDQsDQo+IA0KPiANCj4gDQo+IE1h
ZGFuYXBhbGxpLCBldCBhbC4gICAgICAgRXhwaXJlcyBBcHJpbCA0LCAyMDA5ICAgICAgICAgICAg
ICAgICBbUGFnZSA5XQ0KPiAMDQo+IEludGVybmV0LURyYWZ0ICAgICAgICBJUHY0IG92ZXIgSUVF
RSA4MDIuMTYncyBJUCBDUyAgICAgICAgIE9jdG9iZXIgMjAwOA0KPiANCj4gDQo+ICAgICAgICAg
ICAgICAgQXVndXN0IDIwMDIuDQo+IA0KPiAgICBbUkZDMTI1Nl0gIERlZXJpbmcsIFMuLCAiSUNN
UCBSb3V0ZXIgRGlzY292ZXJ5IE1lc3NhZ2VzIiwgUkZDIDEyNTYsDQo+ICAgICAgICAgICAgICAg
U2VwdGVtYmVyIDE5OTEuDQo+IA0KPiAgICBbRVRIQ1NdICAgIEplb24sIEguLCBSaWVnZWwsIE0u
LCBhbmQgUy4gSmVvbmcsICJUcmFuc21pc3Npb24gb2YgSVANCj4gICAgICAgICAgICAgICBvdmVy
IEV0aGVybmV0IG92ZXIgSUVFRSA4MDIuMTYgTmV0d29ya3MiLCBBcHJpbCAyMDA4LA0KPiAgICAg
ICAgICAgICAgIDxodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy8NCj4gICAgICAg
ICAgICAgICBkcmFmdC1pZXRmLTE2bmctaXAtb3Zlci1ldGhlcm5ldC1vdmVyLTgwMi4xNi0wNi50
eHQ+Lg0KPiANCj4gICAgWzgwMl8xNlJFVjJdDQo+ICAgICAgICAgICAgICAgSm9obnN0b24sIEQu
LCAiU0RVIE1UVSBDYXBhYmlsaXR5IERlY2xhcmF0aW9uIiwNCj4gICAgICAgICAgICAgICBNYXJj
aCAyMDA4LCA8aHR0cDovL3d3dy5pZWVlLm9yZy8xNj4uDQo+IA0KPiAgICBbSUVFRTgwMl8xNl0N
Cj4gICAgICAgICAgICAgICAiSUVFRSA4MDIuMTZlLCBJRUVFIHN0YW5kYXJkIGZvciBMb2NhbCBh
bmQgbWV0cm9wb2xpdGFuDQo+ICAgICAgICAgICAgICAgYXJlYSBuZXR3b3JrcywgUGFydCAxNjpB
aXIgSW50ZXJmYWNlIGZvciBmaXhlZCBhbmQgTW9iaWxlDQo+ICAgICAgICAgICAgICAgYnJvYWRi
YW5kIHdpcmVsZXNzIGFjY2VzcyBzeXN0ZW1zIiwgT2N0b2JlciAyMDA1Lg0KDQpJRUVFODAyLjE2
LTIwMDkgaXMgcmVsZWFzZWQgYW5kIHN1cGVyc2VkZXMgMTZlIGFzIHdlbGwgYXMgUkVWMi4NCldo
eSBpcyB0aGUgSUVFRTgwMi4xNiBzcGVjaWZpY2F0aW9uIGxpc3RlZCB1bmRlciBpbmZvcm1hdGl2
ZT8NCg0KPiAgICBbV01GXSAgICAgICJXaU1BWCBFbmQtdG8tRW5kIE5ldHdvcmsgU3lzdGVtcyBB
cmNoaXRlY3R1cmUgU3RhZ2UgMi0zDQo+ICAgICAgICAgICAgICAgUmVsZWFzZSAxLjIsDQo+ICAg
ICAgICAgICAgICAgaHR0cDovL3d3dy53aW1heGZvcnVtLm9yZy90ZWNobm9sb2d5L2RvY3VtZW50
cyIsDQo+ICAgICAgICAgICAgICAgSmFudWFyeSAyMDA4Lg0KPiANCj4gDQo+IEFwcGVuZGl4IEEu
ICBNdWx0aXBsZSBDb252ZXJnZW5jZSBMYXllcnMgLSBJbXBhY3Qgb24gU3VibmV0IE1vZGVsDQo+
IA0KPiAgICBUd28gZGlmZmVyZW50IE1TcyB1c2luZyB0d28gZGlmZmVyZW50IGNvbnZlcmdlbmNl
IHN1YmxheWVycyAoZS5nLiBhbg0KPiAgICBNUyB1c2luZyBFdGhlcm5ldCBDUyBvbmx5IGFuZCBh
bm90aGVyIE1TIHVzaW5nIElQIENTIG9ubHkpIGNhbm5vdA0KPiAgICBjb21tdW5pY2F0ZSBhdCBk
YXRhIGxpbmsgbGF5ZXIgYW5kIHJlcXVpcmVzIGludGVyd29ya2luZyBhdCBJUCBsYXllci4NCj4g
ICAgRm9yIHRoaXMgcmVhc29uLCB0aGVzZSB0d28gbm9kZXMgbXVzdCBiZSBjb25maWd1cmVkIHRv
IGJlIG9uIHR3bw0KPiAgICBkaWZmZXJlbnQgc3VibmV0cy4gIEZvciBtb3JlIGluZm9ybWF0aW9u
IHJlZmVyIHRvIFtSRkM0ODQwXS4NCj4gDQo+IA0KPiBBcHBlbmRpeCBCLiAgU2VuZGluZyBhbmQg
UmVjZWl2aW5nIElQdjQgUGFja2V0cw0KPiANCj4gICAgSUVFRSA4MDIuMTYgTUFDIGlzIGEgcG9p
bnQtdG8tbXVsdGlwb2ludCBjb25uZWN0aW9uIG9yaWVudGVkIGFpci0NCj4gICAgaW50ZXJmYWNl
LCBhbmQgdGhlIHByb2Nlc3Mgb2Ygc2VuZGluZyBhbmQgcmVjZWl2aW5nIG9mIElQdjQgcGFja2V0
cw0KPiAgICBpcyBkaWZmZXJlbnQgZnJvbSBtdWx0aWNhc3QtY2FwYWJsZSBzaGFyZWQgbWVkaXVt
IHRlY2hub2xvZ2llcyBsaWtlDQo+ICAgIEV0aGVybmV0Lg0KPiANCj4gICAgQmVmb3JlIGFueSBw
YWNrZXRzIGFyZSB0cmFuc21pdHRlZCwgYSBJRUVFIDgwMi4xNiB0cmFuc3BvcnQNCj4gICAgY29u
bmVjdGlvbiBtdXN0IGJlIGVzdGFibGlzaGVkLiAgVGhpcyBjb25uZWN0aW9uIGNvbnNpc3RzIG9m
IElFRUUNCj4gICAgODAyLjE2IE1BQyB0cmFuc3BvcnQgY29ubmVjdGlvbiBiZXR3ZWVuIE1TIGFu
ZCBCUyBhbmQgYW4gTDIgdHVubmVsDQo+ICAgIGJldHdlZW4gQlMgYW5kIEFSIChpZiB0aGVzZSB0
d28gYXJlIG5vdCBjby1sb2NhdGVkKS4gIFRoaXMgSUVFRQ0KPiAgICA4MDIuMTYgdHJhbnNwb3J0
IGNvbm5lY3Rpb24gcHJvdmlkZXMgYSBwb2ludC10by1wb2ludCBsaW5rIGJldHdlZW4NCj4gICAg
dGhlIE1TIGFuZCBBUi4gIEFsbCB0aGUgcGFja2V0cyBvcmlnaW5hdGVkIGF0IHRoZSBNUyBhbHdh
eXMgcmVhY2ggdGhlDQo+ICAgIEFSIGJlZm9yZSBiZWluZyB0cmFuc21pdHRlZCB0byB0aGUgZmlu
YWwgZGVzdGluYXRpb24uDQo+IA0KPiANCj4gDQo+IE1hZGFuYXBhbGxpLCBldCBhbC4gICAgICAg
RXhwaXJlcyBBcHJpbCA0LCAyMDA5ICAgICAgICAgICAgICAgIFtQYWdlIDEwXQ0KPiAMDQo+IElu
dGVybmV0LURyYWZ0ICAgICAgICBJUHY0IG92ZXIgSUVFRSA4MDIuMTYncyBJUCBDUyAgICAgICAg
IE9jdG9iZXIgMjAwOA0KPiANCj4gDQo+ICAgIElQdjQgcGFja2V0cyBhcmUgY2FycmllZCBkaXJl
Y3RseSBpbiB0aGUgcGF5bG9hZCBvZiBJRUVFIDgwMi4xNg0KPiAgICBmcmFtZXMgd2hlbiB0aGUg
SVB2NCBDUyBpcyB1c2VkLiAgSVB2NCBDUyBjbGFzc2lmaWVzIHRoZSBwYWNrZXQgYmFzZWQNCj4g
ICAgb24gdXBwZXIgbGF5ZXIgKElQIGFuZCB0cmFuc3BvcnQgbGF5ZXJzKSBoZWFkZXIgZmllbGRz
IHRvIHBsYWNlIHRoZQ0KPiAgICBwYWNrZXQgb24gb25lIG9mIHRoZSBhdmFpbGFibGUgY29ubmVj
dGlvbnMgaWRlbnRpZmllZCBieSB0aGUgQ0lELg0KPiAgICBUaGUgY2xhc3NpZmllcnMgZm9yIHRo
ZSBJUHY0IENTIGFyZSBzb3VyY2UgYW5kIGRlc3RpbmF0aW9uIElQdjQNCj4gICAgYWRkcmVzc2Vz
LCBzb3VyY2UgYW5kIGRlc3RpbmF0aW9ucyBwb3J0cywgVHlwZS1vZi1TZXJ2aWNlIGFuZCBJUA0K
PiAgICBwcm90b2NvbCBmaWVsZC4gIFRoZSBDUyBtYXkgZW1wbG95IFBhY2tldCBIZWFkZXIgU3Vw
cHJlc3Npb24gKFBIUykNCj4gICAgYWZ0ZXIgdGhlIGNsYXNzaWZpY2F0aW9uLg0KPiANCj4gICAg
VGhlIEJTIG9wdGlvbmFsbHkgcmVjb25zdHJ1Y3RzIHRoZSBwYXlsb2FkIGhlYWRlciBpZiBQSFMg
aXMgaW4gdXNlLg0KPiAgICBJdCB0aGVuIHR1bm5lbHMgdGhlIHBhY2tldCB0aGF0IGhhcyBiZWVu
IHJlY2VpdmVkIG9uIGEgcGFydGljdWxhciBNQUMNCj4gICAgY29ubmVjdGlvbiB0byB0aGUgQVIu
ICBTaW1pbGFybHkgdGhlIHBhY2tldHMgcmVjZWl2ZWQgb24gYSB0dW5uZWwNCj4gICAgaW50ZXJm
YWNlIGZyb20gdGhlIEFSLCB3b3VsZCBiZSBtYXBwZWQgdG8gYSBwYXJ0aWN1bGFyIENJRCB1c2lu
ZyB0aGUNCj4gICAgSVB2NCBjbGFzc2lmaWNhdGlvbiBtZWNoYW5pc20uDQo+IA0KPiAgICBBUiBw
ZXJmb3JtcyBub3JtYWwgcm91dGluZyBmb3IgdGhlIHBhY2tldHMgdGhhdCBpdCByZWNlaXZlcywN
Cj4gICAgcHJvY2Vzc2luZyB0aGVtIHBlciBpdHMgZm9yd2FyZGluZyB0YWJsZS4gIEhvd2V2ZXIs
IHRoZSBESENQIHJlbGF5DQo+ICAgIGFnZW50IGluIHRoZSBBUiBNVVNUIG1haW50YWluIHRoZSB0
dW5uZWwgaW50ZXJmYWNlIG9uIHdoaWNoIGl0DQo+ICAgIHJlY2VpdmVzIERIQ1AgcmVxdWVzdHMg
c28gdGhhdCBpdCBjYW4gcmVsYXkgdGhlIERIQ1AgcmVzcG9uc2VzIHRvIHRoZQ0KPiAgICBjb3Jy
ZWN0IE1TLiAgT25lIHdheSBvZiBkb2luZyB0aGlzIGlzIHRvIGhhdmUgYSBtYXBwaW5nIGJldHdl
ZW4gTUFDDQo+ICAgIGFkZHJlc3MgYW5kIFR1bm5lbCBJZGVudGlmaWVyLg0KDQpXaGljaCBNQUMg
YWRkcmVzcz8NCg0KPiANCj4gQXBwZW5kaXggQy4gIFdpTUFYIElQQ1MgTVRVIHNpemUNCj4gDQo+
ICAgIFdpTUFYIChXb3JsZHdpZGUgSW50ZXJvcGVyYWJpbGl0eSBmb3IgTWljcm93YXZlIEFjY2Vz
cykgZm9ydW0gaGFzDQo+ICAgIGRlZmluZWQgYSBuZXR3b3JrIGFyY2hpdGVjdHVyZVtXTUZdLiAg
RnVydGhlcm1vcmUsIFdpTUFYIGhhcw0KPiAgICBzcGVjaWZpZWQgSVB2NCBDUyBzdXBwb3J0IGZv
ciB0cmFuc21pc3Npb24gb2YgSVB2NCBwYWNrZXRzIGJldHdlZW4gTVMNCj4gICAgYW5kIEJTIG92
ZXIgdGhlIElFRUUgODAyLjE2IGxpbmsuICBUaGUgV2lNQVggSVB2NCBDUyBhbmQgdGhpcw0KPiAg
ICBzcGVjaWZpY2F0aW9uIGFyZSBzaW1pbGFyLiAgT25lIHNpZ25pZmljYW50IGRpZmZlcmVuY2Us
IGhvd2V2ZXIsIGlzDQo+ICAgIHRoYXQgdGhlIFdpTUFYIEZvcnVtIFtXTUZdIGhhcyBzcGVjaWZp
ZWQgdGhlIElQIE1UVSBhcyAxNDAwIG9jdGV0cw0KPiAgICBbV01GXSBhcyBvcHBvc2VkIHRvIDE1
MDAgaW4gdGhpcyBzcGVjaWZpY2F0aW9uLg0KPiANCj4gICAgSGVuY2UgaWYgYW4gSVB2NCBDUyBN
UyBjb25maWd1cmVkIHdpdGggYW4gTVRVIG9mIDE1MDAgb2N0ZXQgZW50ZXJzIGENCj4gICAgV2lN
QVggbmV0d29yaywgc29tZSBvZiB0aGUgaXNzdWVzIG1lbnRpb25lZCBpbiB0aGlzIHNwZWNpZmlj
YXRpb24gbWF5DQo+ICAgIGFyaXNlLiAgQXMgbWVudGlvbmVkIGluIHNlY3Rpb24gNC4zLCB0aGUg
cG9zc2libGUgbWVjaGFuaXNtcyBhcmUgbm90DQo+ICAgIGd1YXJhbnRlZWQgdG8gd29yay4gIEZ1
cnRoZXJtb3JlLCBhbiBJUHY0IENTIGNsaWVudCBpcyBub3QgY2FwYWJsZSBvZg0KPiAgICBkb2lu
ZyBBUlAgcHJvYmluZyB0byBmaW5kIG91dCB0aGUgbGluayBNVFUuICBPbiB0aGUgb3RoZXIgaGFu
ZCwgaXQgaXMNCj4gICAgaW1wZXJhdGl2ZSBmb3IgYW4gTVMgdG8ga25vdyB0aGUgbGluayBNVFUg
c2l6ZS4gIEluIHByYWN0aWNlLCBNUw0KPiAgICBzaG91bGQgYmUgYWJsZSB0byBzZW5zZSBvciBk
ZWR1Y2UgdGhlIGZhY3QgdGhhdCB0aGV5IGFyZSBvcGVyYXRpbmcNCj4gICAgd2l0aGluIGEgV2lN
QVggbmV0d29yayAoZS5nLiwgZ2l2ZW4gdGhlIFdpTUFYLXNwZWNpZmljDQo+ICAgIHBhcnRpY3Vs
YXJpdGllcyBvZiB0aGUgYXV0aGVudGljYXRpb24gYW5kIG5ldHdvcmsgZW50cnkgcHJvY2VkdXJl
cyksDQo+ICAgIGFuZCBhZGp1c3QgdGhlaXIgTVRVIHNpemUgYWNjb3JkaW5nbHkuICBUaGlzIGRv
Y3VtZW50IG1ha2VzIG5vDQo+ICAgIGZ1cnRoZXIgYXNzdW1wdGlvbnMgaW4gdGhpcyByZXNwZWN0
Lg0KDQpBcHBlbmRpeCBDIHNob3VsZCBiZSByZW1vdmVkLg0KT25seSBXaU1BWCBkZXZpY2VzIHdp
bGwgZW50ZXIgV2lNQVggbmV0d29ya3MsIGFuZCBXaU1BWCBkZXZpY2VzIGtub3cgYWJvdXQgdGhl
IE1UVSBzaXplIGluIFdpTUFYIG5ldHdvcmtzLg0KDQo+IA0KPiANCj4gDQo+IA0KPiANCj4gDQo+
IE1hZGFuYXBhbGxpLCBldCBhbC4gICAgICAgRXhwaXJlcyBBcHJpbCA0LCAyMDA5ICAgICAgICAg
ICAgICAgIFtQYWdlIDExXQ0KPiAMDQo+IEludGVybmV0LURyYWZ0ICAgICAgICBJUHY0IG92ZXIg
SUVFRSA4MDIuMTYncyBJUCBDUyAgICAgICAgIE9jdG9iZXIgMjAwOA0KPiANCj4gDQo+IEFwcGVu
ZGl4IEQuICBUaG91Z2h0cyBvbiBoYW5kbGluZyBtdWx0aWNhc3QtYnJvYWRjYXN0IElQIHBhY2tl
dHMNCj4gDQo+ICAgIEFsdGhvdWdoIHRoaXMgZG9jdW1lbnQgZG9lcyBub3QgZGlyZWN0bHkgc3Bl
Y2lmeSBkZXRhaWxzIG9mIG11bHRpY2FzdA0KPiAgICBvciBicm9hZGNhc3QgcGFja2V0IGhhbmRs
aW5nLCBoZXJlIGFyZSBzb21lIHN1Z2dlc3Rpb25zOg0KPiANCj4gICAgV2hpbGUgdXBsaW5rIGNv
bm5lY3Rpb25zIGZyb20gdGhlIE1TcyB0byB0aGUgQlMgcHJvdmlkZSBvbmx5IHVuaWNhc3QNCj4g
ICAgdHJhbnNtaXNzaW9uIGNhcGFiaWxpdGllcywgZG93bmxpbmsgY29ubmVjdGlvbnMgY2FuIGJl
IHVzZWQgZm9yDQo+ICAgIG11bHRpY2FzdCB0cmFuc21pc3Npb24gdG8gYSBncm91cCBvZiBNU3Mg
YXMgd2VsbCBhcyB1bmljYXN0DQo+ICAgIHRyYW5zbWlzc2lvbiBmcm9tIHRoZSBCUyB0byBhIHNp
bmdsZSBNUy4gIEZvciBhbGwtbm9kZSBJUCBhZGRyZXNzZXMsDQo+ICAgIHRoZSBBUiBvciBCUyBz
aG91bGQgaGF2ZSBzcGVjaWFsIG1hcHBpbmcgYW5kIHRoZSBwYWNrZXRzIHNob3VsZCBiZQ0KPiAg
ICBkaXN0cmlidXRlZCB0byBhbGwgYWN0aXZlIHBvaW50LXRvLXBvaW50IGNvbm5lY3Rpb25zIGJ5
IHRoZSBBUiBvciBieQ0KPiAgICB0aGUgQlMuICBBbGwtcm91dGVyIG11bHRpY2FzdCBwYWNrZXRz
IGFuZCBhbnkgYnJvYWRjYXN0IHBhY2tldHMgZnJvbQ0KPiAgICBhIE1TIHdpbGwgYmUgZm9yd2Fy
ZGVkIHRvIHRoZSBBUiBieSB0aGUgQlMuICBJZiBCUyBhbmQgTVMgYXJlIGNvLQ0KPiAgICBsb2Nh
dGVkLCB0aGVuIHRoZSBmaXJzdCBhcHByb2FjaCBpcyBtb3JlIHVzZWZ1bC4gIElmIHRoZSBBUiBh
bmQgQlMNCj4gICAgYXJlIGxvY2F0ZWQgc2VwYXJhdGVseSB0aGVuIHRoZSBzZWNvbmQgYXBwcm9h
Y2ggc2hvdWxkIGJlDQo+ICAgIGltcGxlbWVudGVkLiAgQW4gaW5pdGlhbCBjYXBhYmlsaXR5IGV4
Y2hhbmdlIG1lc3NhZ2Ugc2hvdWxkIGJlDQo+ICAgIHBlcmZvcm1lZCBiZXR3ZWVuIEJTIGFuZCBB
UiAoaWYgdGhleSBhcmUgbm90IGNvLWxvY2F0ZWQpIHRvIGRldGVybWluZQ0KPiAgICB3aG8gd291
bGQgcGVyZm9ybSB0aGUgZGlzdHJpYnV0aW9uIG9mIG11bHRpY2FzdC9icm9hZGNhc3QgcGFja2V0
cy4NCj4gICAgU3VjaCBtZWNoYW5zaW0gc2hvdWxkIGJlIHBhcnQgb2YgTDIgZXhjaGFuZ2UgZHVy
aW5nIHRoZSBjb25uZWN0aW9uDQo+ICAgIHNldHVwIGFuZCBpcyBvdXQgb2Ygc2NvcGUgb2YgdGhp
cyBkb2N1bWVudC4gIEluIG9yZGVyIHRvIHNhdmUgZW5lcmd5DQo+ICAgIG9mIHRoZSB3aXJlbGVz
cyBlbmQgZGV2aWNlcyBpbiB0aGUgSUVFRSA4MDIuMTYgd2lyZWxlc3MgbmV0d29yaywgaXQNCj4g
ICAgaXMgcmVjb21tZW5lZCB0aGF0IHRoZSBtdWx0aWNhc3QgYW5kIGJyb2FkY2FzdCBmcm9tIG5l
dHdvcmsgc2lkZSB0bw0KPiAgICBkZXZpY2Ugc2lkZSBzaG91bGQgYmUgcmVkdWNlZC4gIE9ubHkg
REhDUCwgSUdNUCwgUm91dGVyIGFkdmVydGlzZW1uZXQNCj4gICAgcGFja2V0cyBhcmUgYWxsb3dl
ZCBvbiB0aGUgZG93bmxpbmsgZm9yIG11bHRpY2FzdCBhbmQgYnJvYWRjYXN0IElQDQo+ICAgIGFk
ZHJlc3Nlcy4gIE90aGVyIHByb3RvY29scyB1c2luZyBtdWx0aWNhc3QgYW5kIGJyb2FkY2FzdCBJ
UA0KPiAgICBhZGRyZXNzZXMgc2hvdWxkIGJlIHBlcm1pdHRlZCB0aHJvdWdoIGxvY2FsIEFSL0JT
IGNvbmZpZ3VyYXRpb24uDQo+IA0KPiANCj4gQXV0aG9ycycgQWRkcmVzc2VzDQo+IA0KPiAgICBT
eWFtIE1hZGFuYXBhbGxpDQo+ICAgIE9yZHluIFRlY2hub2xvZ2llcw0KPiAgICAxc3QgRmxvb3Is
IENyZWF0b3IgQnVpbGRpbmcsIElUUEwNCj4gICAgQmFuZ2Fsb3JlIC0gNTYwMDY2DQo+ICAgIElu
ZGlhDQo+IA0KPiAgICBFbWFpbDogc21hZGFuYXBhbGxpQGdtYWlsLmNvbQ0KPiANCj4gDQo+ICAg
IFNvb2hvbmcgRGFuaWVsIFBhcmsNCj4gICAgU2Ftc3VuZyBFbGVjdHJvbmljcw0KPiAgICA0MTYg
TWFldGFuLTNkb25nLCBZZW9uZ3RvbmctZ3UNCj4gICAgU3V3b24gNDQyLTc0Mg0KPiAgICBLb3Jl
YQ0KPiANCj4gICAgRW1haWw6IHNvb2hvbmcucGFya0BzYW1zdW5nLmNvbQ0KPiANCj4gDQo+IA0K
PiANCj4gDQo+IE1hZGFuYXBhbGxpLCBldCBhbC4gICAgICAgRXhwaXJlcyBBcHJpbCA0LCAyMDA5
ICAgICAgICAgICAgICAgIFtQYWdlIDEyXQ0KPiAMDQo+IEludGVybmV0LURyYWZ0ICAgICAgICBJ
UHY0IG92ZXIgSUVFRSA4MDIuMTYncyBJUCBDUyAgICAgICAgIE9jdG9iZXIgMjAwOA0KPiANCj4g
DQo+ICAgIFNhbWl0YSBDaGFrcmFiYXJ0aQ0KPiAgICBJUCBJbmZ1c2lvbg0KPiAgICAxMTg4IEFy
cXVlcyBBdmVudWUNCj4gICAgU3Vubnl2YWxlLCBDQQ0KPiAgICBVU0ENCj4gDQo+ICAgIEVtYWls
OiBzYW1pdGFjQGlwaW5mdXNpb24uY29tDQo+IA0KPiANCj4gICAgR2FicmllbCBNb250ZW5lZ3Jv
DQo+ICAgIE1pY3Jvc29mdCBDb3Jwb3JhdGlvbg0KPiAgICBSZWRtb25kLCBXYXNoaW5ndG9uDQo+
ICAgIFVTQQ0KPiANCj4gICAgRW1haWw6IGdhYnJpZWwubW9udGVuZWdyb0BtaWNyb3NvZnQuY29t
DQo+IA0KDQo=

------_=_NextPart_001_01C9E567.F6FDBBD2--

From g_e_montenegro@yahoo.com  Tue Jun  9 09:32:26 2009
Return-Path: <g_e_montenegro@yahoo.com>
X-Original-To: 16ng@core3.amsl.com
Delivered-To: 16ng@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B62623A6A0E for <16ng@core3.amsl.com>; Tue,  9 Jun 2009 09:32:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ldG5W3OEy9+8 for <16ng@core3.amsl.com>; Tue,  9 Jun 2009 09:32:25 -0700 (PDT)
Received: from web82605.mail.mud.yahoo.com (web82605.mail.mud.yahoo.com [68.142.201.122]) by core3.amsl.com (Postfix) with SMTP id 2E04C3A69F9 for <16ng@ietf.org>; Tue,  9 Jun 2009 09:32:25 -0700 (PDT)
Received: (qmail 14275 invoked by uid 60001); 9 Jun 2009 16:32:29 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1244565149; bh=cSWsbWPCnvDhygeJH22cBp4ih964i7BIGsu9izYqMg0=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=FIJyzR7nJIQB2x9yOocAzysuY2NHXjnZdo793IGwCpjVsImGZ+qCkmyLE2p2raF4GUoYALu+EL+Kt5oa/8GSVTwnQ/w2IlxNISsa30ly2qBDpHFazpK34l5JmmVSubXcNgt88GvVC89gdOtbO9YQdIkQ7tKf0oGz1rPWp5BwipM=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=Y3Y8clkQYiW17NsVC8gPZ9Th7Wy3ctmga4Q0gLiREp6oaKbbpDA8pqdqbE4bavcZ3QRXWmGJcIJH4QG4DkEiZWLjxqLs0F7dfhPICoRMbzS57XAJkHq7EKNYEyfhCtv2cXSkKXltkqAfDYpyiZm2wOreflkT1x8fA3y4seZf0kM=;
Message-ID: <396856.9733.qm@web82605.mail.mud.yahoo.com>
X-YMail-OSG: xF9sENgVM1m7KHm0XRjcuuPuYXThNChP78yuUJpeqH6KhOA62LEeNpl0fwkTeN1d6qkoMfr85rXOCG4xUjHAY9yX9i9I8ELZqUek_B6Ej14sxlama6rYcUdONjmiUP2h6qDXXKMrUxzk3S2tEpVNP3E70FicPuXR4mwPPLEoh_24GuRys0OrlYk6C9ZTmF4MZ1XR.epRoSQaGnL41qYHIAdseV4ngqSTy4eOcHe4B5z1cdBdysAlI6Kt54z8dpwCLmfcfK2vAEQQdW5RFVpi2GIToeEO45J7J4yv909et8j74fTtsirtZ3GJbEXzC2Mg8sP44HenhXXrRFm0084-
Received: from [24.16.92.42] by web82605.mail.mud.yahoo.com via HTTP; Tue, 09 Jun 2009 09:32:29 PDT
X-Mailer: YahooMailRC/1277.43 YahooMailWebService/0.7.289.10
References: <20090130191502.0168F28C19D@core3.amsl.com> <15265f0b0905140011h4f64e82bna28efea61205656c@mail.gmail.com>
Date: Tue, 9 Jun 2009 09:32:29 -0700 (PDT)
From: gabriel montenegro <g_e_montenegro@yahoo.com>
To: Hongseok Jeon <hongseok.jeon@gmail.com>, Daniel Park <soohongp@gmail.com>
In-Reply-To: <15265f0b0905140011h4f64e82bna28efea61205656c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-109229363-1244565149=:9733"
Cc: 16ng@ietf.org
Subject: Re: [16NG] Fwd: I-D ACTION:draft-ietf-16ng-ip-over-ethernet-over-802-dot-16-08.txt
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jun 2009 16:32:26 -0000

--0-109229363-1244565149=:9733
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Sorry for the delay on this. We had a recent teleconf discussion with the A=
Ds on 16ng status.=0AI've told them that I believe this document has addres=
sed the AD comments (Jari) as well as=0Athe request for feedback from DSL p=
erpsective. =0A=0AThe plan is that I will advance this to IESG (again) soon=
 (will need a few more days to=0Ado the proto write-up).=0A=0AGabriel=0A=0A=
=0A=0A________________________________=0AFrom: Hongseok Jeon <hongseok.jeon=
@gmail.com>=0ATo: Daniel Park <soohongp@gmail.com>; g_e_montenegro@yahoo.co=
m=0ACc: 16ng@ietf.org; "Riegel, Maximilian" <maximilian.riegel@nsn.com>; Sa=
ngjin Jeong <sjjeong@gmail.com>=0ASent: Thursday, May 14, 2009 12:11:43 AM=
=0ASubject: Fwd: [16NG] I-D ACTION:draft-ietf-16ng-ip-over-ethernet-over-80=
2-dot-16-08.txt=0A=0A=0ADear chairs,=A0=0A=0AI am Hongseok Jeon, one of aut=
hors of IPoEth CS document.=A0=0AWe have submitted the IPoEth CS document i=
n January as below email=A0=0Abut no response was found=A0until now.=A0=0A=
=0AOf course, I don't think no response means that the document is ready to=
 move on.=A0=0ABut, I want to clarify what we are waiting for to move this =
document forward.=A0=0A=0APlease clarify remaining steps.=0A=0AThank you in=
 advance.=0A=0ABest Regards,=0AHongseok Jeon=0A=0A---------- Forwarded mess=
age ----------=0AFrom: <Internet-Drafts@ietf.org>=0ADate: 2009/1/31=0ASubje=
ct: [16NG] I-D ACTION:draft-ietf-16ng-ip-over-ethernet-over-802-dot-16-08.t=
xt=0ATo: i-d-announce@ietf.org=0ACc: 16ng@ietf.org=0A=0A=0AA New Internet-D=
raft is available from the on-line Internet-Drafts=0Adirectories.=0AThis dr=
aft is a work item of the IP over IEEE 802.16 Networks Working Group of the=
 IETF.=0A=0A=A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : Transmission of IP o=
ver Ethernet over IEEE 802.16 Networks=0A=A0 =A0 =A0 =A0Author(s) =A0 =A0 =
=A0 : M. Riegel, S. Jeong, H. Jeon=0A=A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =
=A0: draft-ietf-16ng-ip-over-ethernet-over-802-dot-16-08.txt=0A=A0 =A0 =A0 =
=A0Pages =A0 =A0 =A0 =A0 =A0 : 19=0A=A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0=
 =A0: 2009-1-30=0A=0AThis document describes the transmission of IPv4 over =
Ethernet as=0A=A0 well as IPv6 over Ethernet in an access network deploying=
 the IEEE=0A=A0 802.16 cellular radio transmission technology. =A0The Ether=
net on top=0A=A0 of IEEE 802.16 is realized by bridging connections which t=
he IEEE=0A=A0 802.16 provides between a base station and its associated sub=
scriber=0A=A0 stations. =A0Due to the resource constraints of radio transmi=
ssion=0A=A0 systems and the limitations of the IEEE 802.16 MAC functionalit=
y for=0A=A0 the realization of an Ethernet, the transmission of IP over Eth=
ernet=0A=A0 over IEEE 802.16 may considerably benefit by adding IP specific=
=0A=A0 support functions in the Ethernet over IEEE 802.16 while maintaining=
=0A=A0 full compatibility with standard IP over Ethernet behavior.=0A=0AA U=
RL for this Internet-Draft is:=0Ahttp://www.ietf.org/internet-drafts/draft-=
ietf-16ng-ip-over-ethernet-over-802-dot-16-08.txt=0A=0AInternet-Drafts are =
also available by anonymous FTP at:=0Aftp://ftp.ietf.org/internet-drafts/=
=0A=0ABelow is the data which will enable a MIME compliant mail reader=0Aim=
plementation to automatically retrieve the ASCII version of the=0AInternet-=
Draft.=0A=0A=0A_______________________________________________=0A16NG maili=
ng list=0A16NG@ietf.org=0Ahttps://www.ietf.org/mailman/listinfo/16ng
--0-109229363-1244565149=:9733
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:Courier New, courier, monaco, monospace,=
 sans-serif;font-size:10pt"><DIV>Sorry for the delay on this. We had a rece=
nt teleconf discussion with the ADs on 16ng status.</DIV>=0A<DIV>I've told =
them that I believe this document has addressed the AD comments (Jari) as w=
ell as</DIV>=0A<DIV>the request for feedback from DSL perpsective. </DIV>=
=0A<DIV>&nbsp;</DIV>=0A<DIV>The plan is that I will advance this to IESG (a=
gain) soon (will need a few more days to</DIV>=0A<DIV>do the proto write-up=
).<BR></DIV>=0A<DIV>Gabriel</DIV>=0A<DIV style=3D"FONT-FAMILY: Courier New,=
 courier, monaco, monospace, sans-serif; FONT-SIZE: 10pt"><BR>=0A<DIV style=
=3D"FONT-FAMILY: times new roman, new york, times, serif; FONT-SIZE: 12pt">=
<FONT size=3D2 face=3DTahoma>=0A<HR SIZE=3D1>=0A<B><SPAN style=3D"FONT-WEIG=
HT: bold">From:</SPAN></B> Hongseok Jeon &lt;hongseok.jeon@gmail.com&gt;<BR=
><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Daniel Park &lt;soohon=
gp@gmail.com&gt;; g_e_montenegro@yahoo.com<BR><B><SPAN style=3D"FONT-WEIGHT=
: bold">Cc:</SPAN></B> 16ng@ietf.org; "Riegel, Maximilian" &lt;maximilian.r=
iegel@nsn.com&gt;; Sangjin Jeong &lt;sjjeong@gmail.com&gt;<BR><B><SPAN styl=
e=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Thursday, May 14, 2009 12:11:43 AM=
<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Fwd: [16NG] I-=
D ACTION:draft-ietf-16ng-ip-over-ethernet-over-802-dot-16-08.txt<BR></FONT>=
<BR>=0A<DIV>Dear chairs,&nbsp;</DIV>=0A<DIV><BR></DIV>=0A<DIV>I am Hongseok=
 Jeon, one of authors of IPoEth CS document.&nbsp;</DIV>=0A<DIV>We have sub=
mitted the IPoEth CS document in January as below email&nbsp;</DIV>=0A<DIV>=
but no response was found&nbsp;until now.&nbsp;</DIV>=0A<DIV><BR></DIV>=0A<=
DIV>Of course, I don't think no response means that the document is ready t=
o move on.&nbsp;</DIV>=0A<DIV>But, I want to clarify what we are waiting fo=
r to move this document forward.&nbsp;</DIV>=0A<DIV><BR></DIV>=0A<DIV>Pleas=
e clarify remaining steps.</DIV>=0A<DIV><BR></DIV>=0A<DIV>Thank you in adva=
nce.</DIV>=0A<DIV><BR></DIV>=0A<DIV>Best Regards,</DIV>=0A<DIV>Hongseok Jeo=
n</DIV><BR>=0A<DIV class=3Dgmail_quote>---------- Forwarded message -------=
---<BR>From: <B class=3Dgmail_sendername></B><SPAN dir=3Dltr>&lt;<A href=3D=
"mailto:Internet-Drafts@ietf.org" rel=3Dnofollow target=3D_blank ymailto=3D=
"mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</A>&gt;</SPAN><B=
R>Date: 2009/1/31<BR>Subject: [16NG] I-D ACTION:draft-ietf-16ng-ip-over-eth=
ernet-over-802-dot-16-08.txt<BR>To: <A href=3D"mailto:i-d-announce@ietf.org=
" rel=3Dnofollow target=3D_blank ymailto=3D"mailto:i-d-announce@ietf.org">i=
-d-announce@ietf.org</A><BR>Cc: <A href=3D"mailto:16ng@ietf.org" rel=3Dnofo=
llow target=3D_blank ymailto=3D"mailto:16ng@ietf.org">16ng@ietf.org</A><BR>=
<BR><BR>A New Internet-Draft is available from the on-line Internet-Drafts<=
BR>directories.<BR>This draft is a work item of the IP over IEEE 802.16 Net=
works Working Group of the IETF.<BR><BR>&nbsp; &nbsp; &nbsp; &nbsp;Title &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; : Transmission of IP over Ethernet over IE=
EE 802.16 Networks<BR>&nbsp; &nbsp;
 &nbsp; &nbsp;Author(s) &nbsp; &nbsp; &nbsp; : M. Riegel, S. Jeong, H. Jeon=
<BR>&nbsp; &nbsp; &nbsp; &nbsp;Filename &nbsp; &nbsp; &nbsp; &nbsp;: draft-=
ietf-16ng-ip-over-ethernet-over-802-dot-16-08.txt<BR>&nbsp; &nbsp; &nbsp; &=
nbsp;Pages &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 19<BR>&nbsp; &nbsp; &nbsp; =
&nbsp;Date &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: 2009-1-30<BR><BR>This=
 document describes the transmission of IPv4 over Ethernet as<BR>&nbsp; wel=
l as IPv6 over Ethernet in an access network deploying the IEEE<BR>&nbsp; 8=
02.16 cellular radio transmission technology. &nbsp;The Ethernet on top<BR>=
&nbsp; of IEEE 802.16 is realized by bridging connections which the IEEE<BR=
>&nbsp; 802.16 provides between a base station and its associated subscribe=
r<BR>&nbsp; stations. &nbsp;Due to the resource constraints of radio transm=
ission<BR>&nbsp; systems and the limitations of the IEEE 802.16 MAC functio=
nality for<BR>&nbsp; the realization of an Ethernet, the
 transmission of IP over Ethernet<BR>&nbsp; over IEEE 802.16 may considerab=
ly benefit by adding IP specific<BR>&nbsp; support functions in the Etherne=
t over IEEE 802.16 while maintaining<BR>&nbsp; full compatibility with stan=
dard IP over Ethernet behavior.<BR><BR>A URL for this Internet-Draft is:<BR=
>http://www.ietf.org/internet-drafts/draft-ietf-16ng-ip-over-ethernet-over-=
802-dot-16-08.txt<BR><BR>Internet-Drafts are also available by anonymous FT=
P at:<BR><A href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3Dnofollow tar=
get=3D_blank>ftp://ftp.ietf.org/internet-drafts/</A><BR><BR>Below is the da=
ta which will enable a MIME compliant mail reader<BR>implementation to auto=
matically retrieve the ASCII version of the<BR>Internet-Draft.<BR><BR><BR>_=
______________________________________________<BR>16NG mailing list<BR><A h=
ref=3D"mailto:16NG@ietf.org" rel=3Dnofollow target=3D_blank ymailto=3D"mail=
to:16NG@ietf.org">16NG@ietf.org</A><BR><A
 href=3D"https://www.ietf.org/mailman/listinfo/16ng" rel=3Dnofollow target=
=3D_blank>https://www.ietf.org/mailman/listinfo/16ng</A><BR><BR></DIV><BR><=
/DIV></DIV></div></body></html>
--0-109229363-1244565149=:9733--

From g_e_montenegro@yahoo.com  Tue Jun  9 09:38:10 2009
Return-Path: <g_e_montenegro@yahoo.com>
X-Original-To: 16ng@core3.amsl.com
Delivered-To: 16ng@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E16C3A67D7 for <16ng@core3.amsl.com>; Tue,  9 Jun 2009 09:38:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HP8EwP5ry5dL for <16ng@core3.amsl.com>; Tue,  9 Jun 2009 09:38:03 -0700 (PDT)
Received: from web82604.mail.mud.yahoo.com (web82604.mail.mud.yahoo.com [68.142.201.121]) by core3.amsl.com (Postfix) with SMTP id 9A49D3A6B77 for <16ng@ietf.org>; Tue,  9 Jun 2009 09:38:03 -0700 (PDT)
Received: (qmail 88797 invoked by uid 60001); 9 Jun 2009 16:38:07 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1244565487; bh=ravSINdpzGy2c+VwbwSk8O8bXy74zaQ3dYwKWYbyMOs=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Br1TNgaJzeqnL0G7rx6su+y8GOgT5dz3l6YMBQibADDx/+Tw+OWV5m+y/HaLidySILZikbw3XAnRnnpiZsJpDa9u1Zbcl3BxyJyka1bE9F1IKLFU5uk6hppomFSHmBsX360b0xA+70XV/RVFdwptzSYAEG93WTiQMXoJ6qDnOco=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=HI+6MV2fUZeHZBpbXUQ6btOVS1X8eLFj4+PRLiDnmS+IicUrLaHogvhBCZ/dcJ8dXnW4V6d3aiBSoj5PKbjPKZ4/RMLfL82w+oh3gNWNAMC/JUwePJUCZI5NJV4tI/FE6AJahsdCAEt0rutHzjy1/PbqsBW++b1o+rqIA2uzST0=;
Message-ID: <553392.88380.qm@web82604.mail.mud.yahoo.com>
X-YMail-OSG: Kjn_C1gVM1ngZPjf.LkU09VChTaI3ffZspiX7_o4bKIcSH9UmCn7D2KXMcFrTE02zGZA.djkf769hRSEgc784ynGqK4.Dl4_CzRGWtA282hTMYAOSawNLMZRha4rNVTShb.uWijRYk7ycfCbtiJSLcG_i7cXy6ROJqjpsuRHPrTV0tMwJQLXxTgXuJtQfQcyQ4Nj52I7j8T7DeZUbsHI4X5uNPTbk_G_4rZKyYTjtrI7QEsVooL4OYkuEY8HBBo3QOCnMFCnQ1m91iXWRIT3X0Bd7h4ZlUvfMJ8aLmy0OJkjVKSFQqInJWDPTh3qUPnWmpCS.xBGFmnwIAocIZU-
Received: from [24.16.92.42] by web82604.mail.mud.yahoo.com via HTTP; Tue, 09 Jun 2009 09:38:07 PDT
X-Mailer: YahooMailRC/1277.43 YahooMailWebService/0.7.289.10
References: <2828BDE8DC61004E8104C78E82A0B39710B25385F2@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com><BC27158B99D3064A955ADE084783900C01B5CBC8@DEMUEXC014.nsn-intra.net> <Pine.GSO.4.64.0905151247200.12703@tin>, <046201c9d589$267cf8d0$7376ea70$@com> <BAA9BC6C-6B59-4BA6-B63D-E09C26E0194B@mimectl> <BC27158B99D3064A955ADE084783900C020F18E5@DEMUEXC014.nsn-intra.net> <056601c9d7e8$b8be17e0$2a3a47a0$@com> <556994.50253.qm@web82604.mail.mud.yahoo.com> <06ab01c9d8cd$079cc660$16d65320$@com> <BC27158B99D3064A955ADE084783900C020F26B5@DEMUEXC014.nsn-intra.net> <916575.77425.qm@web82607.mail.mud.yahoo.com> <570230.22436.qm@web82606.mail.mud.yahoo.com> <Pine.GSO.4.64.0906040915000.16060@tin>
Date: Tue, 9 Jun 2009 09:38:07 -0700 (PDT)
From: gabriel montenegro <g_e_montenegro@yahoo.com>
To: Wesley George <wgeorge@sprint.net>
In-Reply-To: <Pine.GSO.4.64.0906040915000.16060@tin>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ext Alper Yegin <alper.yegin@yegin.org>, 16ng@ietf.org, Pekka Savola <pekkas@netcore.fi>
Subject: Re: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jun 2009 16:38:10 -0000

Hi George, thanks for the comments.=0A=0AAbout your suggestion for text to =
mitigate fragmentation in the presence of tunneling:=0AI discussed this rec=
ently with the ADs. Jari's comment was that given that the issue is=0Agener=
al for tunneling, and not specific to 802.16, we don't actually need to say=
 anything.=0AThat seemed to be his preference. It is mine too, as we've lea=
rned that saying less is=0Aoften times better. =0A=0AIf anything, I would r=
ather add a relevant *informative* reference instead of adding any text tha=
t may=0Abe inconclusive.=0A=0AFor example, one could think of referring int=
erested readers to:=0A=A0=0AMTU and Fragmentation Issues with In-the-Networ=
k Tunneling=0Ahttp://tools.ietf.org/html/rfc4459=A0=0ABut I don't even know=
 if that is the more appropriate text one would want to point at.=0AI'm cc-=
ing the author, Pekka Savola, as he may have some more current info for us.=
=0A=A0=0AGabriel=0A=0A=0A=0A----- Original Message ----=0A> From: Wesley Ge=
orge <wgeorge@sprint.net>=0A> To: gabriel montenegro <g_e_montenegro@yahoo.=
com>=0A> Cc: "Riegel, Maximilian (NSN - DE/Munich)" <maximilian.riegel@nsn.=
com>; ext Samita Chakrabarti <samitac@ipinfusion.com>; ext Alper Yegin <alp=
er.yegin@yegin.org>; 16ng@ietf.org=0A> Sent: Thursday, June 4, 2009 6:24:37=
 AM=0A> Subject: Re: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draf=
t=0A> =0A> Gabriel - this looks good to me. The only point/recommendation I=
 might=0A> make for the MTU section is that currently, it focuses only on s=
olutions=0A> that enable the End Host to determine or be advised of the pat=
h MTU. It=0A> would be good to also recommend something regarding the under=
lying network=0A> between the MS and the BS.=0A> What I mean by this is, if=
 the implementor of the 802.16 network either=0A> knows or has control over=
 the MTU of the transport method between the BS=0A> and the MS, they should=
 be able to either set the MTU on the transport=0A> network so that it is h=
igher than 1500 + any encapsulation overhead, or=0A> ensure that it fragmen=
ts larger PDUs properly. Obviously, the latter will=0A> not work if the DF =
bit is set, so perhaps we leave out the discussion of=0A> fragmentation alt=
ogether, but I do think it's worth mentioning that=0A> raising the MTU of t=
he transport network is a viable alternative to using=0A> some means to com=
municate a non-default MTU to the MS.=0A> =0A> Perhaps right before "Some o=
f the mechanisms..." you could add=0A> something like this:=0A> =0A> With a=
n end host MTU of 1500 bytes, the underlying network between the BS and =0A=
> the MS MUST support an MTU of at least 1500 bytes plus the overhead of an=
y =0A> chosen encapsulation method between the BS and MS. For ease of stand=
ardization, =0A> the underlying network SHOULD support an MTU of at least 1=
00 bytes larger than =0A> the chosen host MTU value, as this is large enoug=
h to ensure that there is no =0A> dropping or fragmentation of oversize pac=
kets regardless of the encapsulation =0A> method.=0A> If it is not possible=
 to change the MTU of the network segments between the BS =0A> and the MS, =
then a lower-than-default MTU must be used and communicated to the =0A> IPv=
4 CS host.=0A> =0A> (then, "Some of the mechanisms available...")=0A> =0A> =
Thanks,=0A> Wes=0A> =0A> _________________________________________=0A> =A0 =
Wesley George=0A> =A0=A0=A0 Sprint IP Engineering=0A> =A0 703-689-7505 (O)=
=A0 703-864-4902 (PCS)=0A> =A0 =A0 =A0 =A0 http://www.sprint.net=0A> ______=
___________________________________=0A> =0A> =0A> On Wed, 3 Jun 2009, gabri=
el montenegro wrote:=0A> =0A> > The new rev has appeared:=0A> http://tools.=
ietf.org/html/draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05=0A> =0A> This is=
 a summary of changes:=0A> =0A> Editorial changes throughout.=0A> =0A> Got =
rid of all mention of WiMAX in the main text.=0A> =0A> Section 3 on network=
 architecture: deleted much text, instead referring to the=0A> relevant sec=
tions in IEEE802.16, 5121 and 5154. No need to repeat text that =0A> appear=
s elsewhere.=0A> =0A> Section 4.3 on MTU: simplified to say not much more t=
han RFC5121 says.=0A> =0A> Section 6 on handling multicast. Got rid of it. =
It repeats stuff already in=0A> both 5.3 and 5.1.=0A> =0A> Appendix on WiMA=
X MTU.=0A> Got rid of:=0A> =A0=A0 The addressing and operation of IPv4 CS d=
escribed in this=0A> =A0=A0 document are applicable to the WiMAX networks a=
s well.=A0=0A> Got rid of recommendation that WiMAX adopt this specificatio=
n.=0A> =0A> But your favorite diff tool is your best bet, e.g.:=0A> =0A> ht=
tp://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-16ng-ipv4-over-802-dot-16-ipc=
s-05.txt=0A> =0A> Please look it over. Hopefully, the remaining issues are =
manageable and less in =0A> number.=0A> =0A> thanks,=0A> =0A> Gabriel=0A> =
=0A> =0A> =0A> ________________________________=0A> From: gabriel montenegr=
o =0A> To: "Riegel, Maximilian (NSN - DE/Munich)" ; ext =0A> Samita Chakrab=
arti ; Wesley George =0A> Cc: ext Alper Yegin ; 16ng@ietf.org=0A> Sent: Wed=
nesday, May 20, 2009 8:41:46 AM=0A> Subject: Re: [16NG] [nwg-chair] NWG fee=
dback on 16ng's IPv4 CS draft=0A> =0A> =0A> Let's wait till the next versio=
n appears (ETA: end of this month) as hopefully =0A> that version=0A> will =
require less fixes.=0A> =0A> =0A> =0A> =0A> _______________________________=
_=0A> From: "Riegel, Maximilian (NSN - DE/Munich)" =0A> To: ext Samita Chak=
rabarti ; gabriel montenegro =0A> ; Wesley George =0A> Cc: ext Alper Yegin =
; 16ng@ietf.org=0A> Sent: Wednesday, May 20, 2009 2:11:31 AM=0A> Subject: R=
e: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft=0A> =0A> =0A> My=
 point is not the MTU size, I am concerned about the quality of the current=
 =0A> document. There are=A0a number of=A0ambiguities and misconceptions, w=
hich would =0A> require some efforts for resolving. I once did an approach =
to create a =0A> submission to the mailing list and gave up after an hour s=
eeing that it requires =0A> more=A0text to explain the issues in the docume=
nt than just rephrasing the text.=0A> =A0=0A> Would it be possible to held =
a conference call to discuss the readiness of the =0A> IPv4-CS I-D?=0A> =A0=
=0A> Bye=0A> Max=0A> =0A> =0A> ________________________________=0A> From: e=
xt Samita Chakrabarti [mailto:samitac@ipinfusion.com] Sent: Tuesday, May =
=0A> 19, 2009 11:59 PM=0A> To: 'gabriel montenegro'; Riegel, Maximilian (NS=
N - DE/Munich); 'Wesley George'=0A> Cc: 'ext Alper Yegin'; 16ng@ietf.org=0A=
> Subject: RE: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft=0A> =
=0A> =0A> Agreed. Default MTU is 1500 =A0- if WiMAX does not want to update=
 their SPEC or =0A> does not want to conform to this IETF draft, it is SDO =
business. Thus we can =0A> move forward =A0independently.=0A> =A0=0A> Thank=
s,=0A> -Samita=0A> =A0=0A> From:gabriel montenegro [mailto:g_e_montenegro@y=
ahoo.com] Sent: Tuesday, May 19, =0A> 2009 9:39 AM=0A> To: Samita Chakrabar=
ti; Riegel, Maximilian (NSN - DE/Munich); Wesley George=0A> Cc: ext Alper Y=
egin; 16ng@ietf.org=0A> Subject: Re: [16NG] [nwg-chair] NWG feedback on 16n=
g's IPv4 CS draft=0A> =A0=0A> I think what we need (my intention) is not mo=
re details, but less. I agree that =0A> there is=0A> some overlap with the =
WiMAX spec. We should simply refer to WiMAX for the =0A> WiMAX-specifics, a=
nd drop the recommendation that WiMAX should adopt this spec. =0A> Given th=
e difference in=A0MTU,=0A> I won't hold my breath for them to do so, but it=
's really their business. =A0=0A> =0A> ________________________________=0A>=
 =0A> From:Samita Chakrabarti =0A> To: "Riegel, Maximilian (NSN - DE/Munich=
)" ; ext =0A> Gabriel Montenegro ; Wesley George =0A> =0A> Cc: ext Alper Ye=
gin ; 16ng@ietf.org=0A> Sent: Monday, May 18, 2009 11:44:47 AM=0A> Subject:=
 Re: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft=0A> Hi Max,=0A=
> =A0=0A> As I understand from NWG feedback that they did not like IETF to =
recommend 1500 =0A> byte MTU size (Appendix section) for future revision of=
 NWG Wimax specs.=A0 Other =0A> than that there are minor editorial changes=
 that we want to do to polish the =0A> draft. =A0=0A> Here is the summary f=
rom NWG feedback:=0A> > > In particular the influence of tunneling inside t=
he network should be=0A> > > carefully discussed.=0A> > > In addition we wo=
uld kindly ask to either remove whole Appendix C on=0A> > > the WiMAX MTU s=
ize or revise the text explaining the real issues in=0A> > > the WiMAX arch=
itecture. In particular the statements on the=0A> > > applicability of the =
I-D on the WiMAX architecture and the=0A> > > recommendation on future modi=
fications in the WiMAX architecture seem=0A> > > not to be very appropriate=
 to us.=0A> What is your suggestion on updating Appendix C? =A0=0A> Thanks,=
=0A> -Samita=0A> =A0=0A> =A0=0A> From:Riegel, Maximilian (NSN - DE/Munich) =
[mailto:maximilian.riegel@nsn.com] =0A> Sent: Monday, May 18, 2009 12:19 AM=
=0A> To: ext Gabriel Montenegro; Samita Chakrabarti; Wesley George=0A> Cc: =
ext Alper Yegin; 16ng@ietf.org=0A> Subject: RE: [16NG] [nwg-chair] NWG feed=
back on 16ng's IPv4 CS draft=0A> =A0=0A> Is there really a demand to work o=
n an update of the IPv4-CS I-D?=0A> Which details would require/qualify for=
=A0an IETF specification?=0A> The current architectural model closely resem=
bles the WiMAX architecture, and =0A> WiMAX provides a comprehensive specif=
ication for it.=0A> =A0=0A> Bye=0A> Max=0A> =A0=0A> =0A> __________________=
______________=0A> =0A> From:ext Gabriel Montenegro [mailto:Gabriel.Montene=
gro@microsoft.com] Sent: =0A> Friday, May 15, 2009 8:21 PM=0A> To: Samita C=
hakrabarti; 'Wesley George'; Riegel, Maximilian (NSN - DE/Munich)=0A> Cc: '=
ext Alper Yegin'; 16ng@ietf.org=0A> Subject: RE: [16NG] [nwg-chair] NWG fee=
dback on 16ng's IPv4 CS draft=0A> yes, I've been delinquently holding to th=
e pen.=0A> Lets shoot for end of the month at the latest.=0A> =0A> ________=
________________________=0A> =0A> From:Samita Chakrabarti [samitac@ipinfusi=
on.com]=0A> Sent: Friday, May 15, 2009 11:15 AM=0A> To: 'Wesley George'; 'R=
iegel, Maximilian (NSN - DE/Munich)'=0A> Cc: 'ext Alper Yegin'; Gabriel Mon=
tenegro; 16ng@ietf.org=0A> Subject: RE: [16NG] [nwg-chair] NWG feedback on =
16ng's IPv4 CS draft=0A> Hi Wes,=0A> =0A> Yes, there will be an updated dra=
ft before Stockholm. Gabriel was working on=0A> the updates.=0A> =0A> I am =
expecting that we will soon have a revision to review.=0A> =0A> Thanks,=0A>=
 -Samita=0A> =0A> > -----Original Message-----=0A> > From: 16ng-bounces@iet=
f.org [mailto:16ng-bounces@ietf.org] On Behalf Of=0A> > Wesley George=0A> >=
 Sent: Friday, May 15, 2009 9:54 AM=0A> > To: Riegel, Maximilian (NSN - DE/=
Munich)=0A> > Cc: ext Alper Yegin; ext Gabriel Montenegro; 16ng@ietf.org=0A=
> > Subject: Re: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft=0A=
> > =0A> > Is someone working on an updated version of this draft to be rev=
iewed in=0A> > Stockholm since we did not meet in SFO? I believe that one o=
f the first=0A> > times that I submitted objections to the MTU language, I =
provided a=0A> proposed=0A> > text that would cover some of the concerns ra=
ised below, not all of which=0A> > was included in subsequent drafts.=0A> >=
 http://www.ietf.org/mail-archive/web/16ng/current/msg00824.html=0A> > =0A>=
 > Thanks,=0A> > Wes=0A> > =0A> > _________________________________________=
=0A> > =A0=A0=A0 Wesley George=0A> > =A0=A0=A0=A0=A0=A0=A0 Sprint IP Engine=
ering=0A> > =A0=A0=A0 703-689-7505 (O)=A0 703-864-4902 (PCS)=0A> > =A0=A0=
=A0=A0=A0=A0=A0=A0=A0 http://www.sprint.net/=0A> > ________________________=
_________________=0A> > =0A> > =0A> > On Thu, 12 Feb 2009, Riegel, Maximili=
an (NSN - DE/Munich) wrote:=0A> > =0A> > > Gabriel,=0A> > >=0A> > > The WiM=
AX Forum NWG reviewed section 4-3 and Appendix C of=0A> > > draft-ietf-16ng=
-ipv4-over-802-dot-16-ipcs-04.txt and would like to=0A> > > make a couple o=
f remarks on the MTU issue:=0A> > >=0A> > > - The I-D is not very clear abo=
ut the MTU issues appearing in an IPv4=0A> > > over IEEE 802.16 transmissio=
n system. The ambiguities mainly result=0A> > > out of the vague definition=
 of the IEEE 802.16 link comprising both=0A> > > the radio part of the link=
 as well as the part of the link between BS=0A> > > and AR, when the functi=
ons are located in different entities.=0A> > >=0A> > > - Section 4.3 in par=
ticular misses the discussion of the dependencies=0A> > > between MTU size =
and the tunneling protocol deployed between BS and AR.=0A> > >=0A> > > - Se=
ction 4.3 also misses, that there is no packet loss when the MTU=0A> > > si=
ze limitation is caused by the encapsulation overhead on the link=0A> > > b=
etween BS and AR. E.g. when GRE is used for the tunnel between BS and=0A> >=
 > AR, the transport IP layer can fragment the GRE packets to fit the=0A> >=
 > transport MTU on the link between BS and AR. Reassembly in the tunnel=0A=
> > > endpoint at the AR will re-establish the original user IP packet.=0A>=
 > >=0A> > > - Please note that the reason of the WiMAX NWG to limit the MT=
U going=0A> > > over IPv4-CS to 1400 Bytes was to avoid fragmentation on th=
e link=0A> > > between BS and ASN-GW as well as on the link between ASN-GW =
and CSN=0A> > > (MIP tunnel). Fragmentation and re-assembly require conside=
rable=0A> > > processing power in the network elements.=0A> > >=0A> > > - A=
ppendix C makes statements which would require more detailed review=0A> > >=
 of the I-D by WiMAX NWG. In particular 'The addressing and operation=0A> >=
 > of IPv4-CS described in this document are applicable to the WiMAX=0A> > =
> networks as well' has not been verified yet.=0A> > > Furthermore 'Thus, W=
iMAX MS nodes should use this default (1400) MTU=0A> > > value per the curr=
ent specification [WMF].=A0 However, due to reasons=0A> > > specified in se=
ction 4.3 above, it is strongly recommended that future=0A> > > WiMAX MS no=
des support a default MTU of 1500 bytes, and that they=0A> > > implement MT=
U negotiation capabilities as mentioned in this document.'=0A> > > makes re=
commendations to WiMAX without understanding the real reasons=0A> > > for t=
he limitation of the MTU size in Mobile WiMAX.=0A> > >=0A> > > We would rec=
ommend to 16ng to revise the sections on MTU size to=0A> > > better explain=
 the underlying issues leading to restrictions in the MTU=0A> > size.=0A> >=
 > In particular the influence of tunneling inside the network should be=0A=
> > > carefully discussed.=0A> > > In addition we would kindly ask to eithe=
r remove whole Appendix C on=0A> > > the WiMAX MTU size or revise the text =
explaining the real issues in=0A> > > the WiMAX architecture. In particular=
 the statements on the=0A> > > applicability of the I-D on the WiMAX archit=
ecture and the=0A> > > recommendation on future modifications in the WiMAX =
architecture seem=0A> > > not to be very appropriate to us.=0A> > >=0A> > >=
=0A> > > Bye=0A> > > Max=0A> > > Vize Chair NWG=0A> > >=0A> > >=0A> > > ___=
_____________________________=0A> > >=0A> > > From: ext Gabriel Montenegro =
[mailto:Gabriel.Montenegro@microsoft.com]=0A> > > Sent: Monday, November 03=
, 2008 11:59 AM=0A> > > To: nwg-chair@list.wimaxforum.org=0A> > > Cc: 'Dani=
el Soohong Park'=0A> > > Subject: [nwg-chair] NWG feedback on 16ng's IPv4 C=
S draft=0A> > >=0A> > >=0A> > >=0A> > > Prakash, Max and Yong Chang,=0A> > =
>=0A> > >=0A> > > The IETF 16ng WG has published a revision of this draft:=
=0A> > >=0A> > > "Transmission of IPv4 packets over IEEE 802.16's IP Conver=
gence=0A> > > Sublayer"=0A> > >=0A> > > Per this announcement:=0A> > >=0A> =
> > http://www.ietf.org/mail-archive/web/16ng/current/msg00863.html=0A> > >=
 =0A> > >=0A> > > We understand that this specification currently is not no=
rmative to=0A> > > NWG (as opposed to RFC5121 on IPv6 CS). Nevertheless, gi=
ven its=0A> > > relevance, and with the hope it may become normative to NWG=
 in some=0A> > > future revision, the 16ng WG would like to solicit feedbac=
k from NWG=0A> > > on this draft.=0A> > >=0A> > > In particular, please not=
e that this draft specifies a default MTU of=0A> > > 1500,=A0 which is diff=
erent from the WiMAX-specified MTU of 1400 (per=0A> > > the recently approv=
ed R1_V1.3.0-Stage-3=A0 NWG specifications).=A0 For MTU=0A> > > discussion,=
 please refer to these sections:=0A> > >=0A> > > http://tools.ietf.org/html=
/draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-0=0A> > > 4#=0A> > > section-4.3=
=0A> > > > > > 04=0A> > > #section-4.3>=0A> > > http://tools.ietf.org/html/=
draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-0=0A> > > 4#=0A> > > appendix-C=
=0A> > > > > > 04=0A> > > #appendix-C>=0A> > >=0A> > > The 16ng WG will nex=
t meet on Nov 18 during the IETF in Minneapolis=0A> > > (https://datatracke=
r.ietf.org/meeting/73/agenda.html). If at all=0A> > > possible, it would be=
 best if comments were received before that date=0A> > > in order for the W=
G to discuss them during the meeting.=0A> > >=0A> > > Please send your comm=
ents to the 16ng@ietf.org =0A> > > mailing list.=0A> > >=0A> > > Thanks,=0A=
> > >=0A> > > Gabriel and Daniel=0A> > > 16ng co-chairs=0A> > >=0A> > >=0A>=
 > >=0A> > >=0A> > _______________________________________________=0A> > 16=
NG mailing list=0A> > 16NG@ietf.org=0A> > https://www.ietf.org/mailman/list=
info/16ng=0A

From g_e_montenegro@yahoo.com  Tue Jun  9 09:48:54 2009
Return-Path: <g_e_montenegro@yahoo.com>
X-Original-To: 16ng@core3.amsl.com
Delivered-To: 16ng@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 871FF28C10D for <16ng@core3.amsl.com>; Tue,  9 Jun 2009 09:48:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[AWL=-0.900, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, J_CHICKENPOX_45=0.6, J_CHICKENPOX_63=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DeHfLMowtLd3 for <16ng@core3.amsl.com>; Tue,  9 Jun 2009 09:48:45 -0700 (PDT)
Received: from web82601.mail.mud.yahoo.com (web82601.mail.mud.yahoo.com [68.142.201.118]) by core3.amsl.com (Postfix) with SMTP id 35ACE3A68FD for <16ng@ietf.org>; Tue,  9 Jun 2009 09:48:45 -0700 (PDT)
Received: (qmail 16301 invoked by uid 60001); 9 Jun 2009 16:48:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1244566131; bh=l9dNUrVKeeUeCsXhQVzqWYsfN9NgqOnRHnlvczZz8Bc=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=xLiX3BtcIVF9jfzfeeQ3NiK/HOsgzS8tTtbMBa9oNfdMj9S1S2jJyGqqG0ojqieSiv+nGY+l9fwpiI9NjXuhsp7OdG4DRU71CpZGs8oXPv0FNECzWBbjAF+W2h/hsClKXeGGyrXMGhJg6Z2gIZRnWoqITAsr+uGmCbda0KsyHXo=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=JKy6BRkriSKQGsszaK4WfThvkqonnDuj0K2uk3TWoX5bpFiWkdxjTOuWxKUkqCGvb92MD41O6Z7X8KOockHIAMs/mJ0Cla1mpuE2T1r5RRZcW5YsnQvw+KxQNez7nd9knN+ZS3+2CpYSPqOmSyCoXl4McXcmVBTCfiwt1f46Qfc=;
Message-ID: <279552.13378.qm@web82601.mail.mud.yahoo.com>
X-YMail-OSG: SwB4aMEVM1lagQIgkzaPZQeJRmHrUBi.aRUNH2x5j1l8VsUa25DR_ALp9nAVIO2_YzRjqqZe1zDd_1053wHhDfuTCjBxuNSto4Ho7JNZZVFd24ZyUWPvDBYBDtnQT8bQslOZkgHDN4F1djq4hR2XnwNJ_iplQ.khF2XcIammgOW.3iiLtW0mpTi6Xp8Fkanv6NvDj9YyontATVI5cHhH3NupiNmF3kNgMgbEKI7op0U78Mz0HO7Irw5CmyiGzG.IJINI7aX2KKQZEdok1xg6pfeCs440MSa.ozbKObiiPWrZKKlQRR.bO96dCCTIXhy5Q_sfGLhvkRVJYZrDkdhuiLiYc2ytGPLi
Received: from [24.16.92.42] by web82601.mail.mud.yahoo.com via HTTP; Tue, 09 Jun 2009 09:48:47 PDT
X-Mailer: YahooMailRC/1277.43 YahooMailWebService/0.7.289.10
References: <20090603154501.B0C963A6CBB@core3.amsl.com> <BC27158B99D3064A955ADE084783900C021E70E1@DEMUEXC014.nsn-intra.net> <BC27158B99D3064A955ADE084783900C021E70E2@DEMUEXC014.nsn-intra.net>
Date: Tue, 9 Jun 2009 09:48:47 -0700 (PDT)
From: gabriel montenegro <g_e_montenegro@yahoo.com>
To: "Riegel, Maximilian \(NSN - DE/Munich\)" <maximilian.riegel@nsn.com>, 16ng@ietf.org
In-Reply-To: <BC27158B99D3064A955ADE084783900C021E70E2@DEMUEXC014.nsn-intra.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ext Alper Yegin <alper.yegin@yegin.org>
Subject: Re: [16NG] I-DAction:draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05.txt
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jun 2009 16:48:54 -0000

Thanks Max, the attached version is better! I'm still going through the com=
ments.=0AWill respond later on.=0A=0A=0A----- Original Message ----=0A> Fro=
m: "Riegel, Maximilian (NSN - DE/Munich)" <maximilian.riegel@nsn.com>=0A> T=
o: "Riegel, Maximilian (NSN - DE/Munich)" <maximilian.riegel@nsn.com>; 16ng=
@ietf.org=0A> Cc: ext Alper Yegin <alper.yegin@yegin.org>; ext gabriel mont=
enegro <g_e_montenegro@yahoo.com>=0A> Sent: Thursday, June 4, 2009 3:58:26 =
PM=0A> Subject: Re: [16NG] I-DAction:draft-ietf-16ng-ipv4-over-802-dot-16-i=
pcs-05.txt=0A> =0A> Please find attached the txt document with my comments,=
 in the case your=0A> screen looks as awful as mine (word wrapping did a ho=
rrible job)=0A> =0A> Bye=0A> Max=0A> =0A> -----Original Message-----=0A> Fr=
om: 16ng-bounces@ietf.org [mailto:16ng-bounces@ietf.org] On Behalf Of=0A> e=
xt Riegel, Maximilian (NSN - DE/Munich)=0A> Sent: Friday, June 05, 2009 12:=
50 AM=0A> To: 16ng@ietf.org=0A> Cc: ext Alper Yegin; ext gabriel montenegro=
=0A> Subject: Re: [16NG]=0A> I-DAction:draft-ietf-16ng-ipv4-over-802-dot-16=
-ipcs-05.txt=0A> =0A> I went through the document and found a couple of iss=
ues, which I would=0A> like to see in a better shape.=0A> Please find my co=
mments inline:=0A> =0A> Bye=0A> Max=0A> =0A> > 16ng Working Group=A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 S.=
=0A> Madanapalli=0A> > Internet-Draft=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Ordyn=0A> Technologies=0A> > In=
tended status: Standards Track=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 Soohong D.=0A> Park=0A> > Expires: April 4, 2009=A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Samsung=0A> =0A> =0A> =0A> -----Inline=
 Attachment Follows-----=0A> =0A> > 16ng Working Group=A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 S. Madanapalli=
=0A> > Internet-Draft=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 Ordyn Technologies=0A> > Intended status: Stand=
ards Track=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Soohong D. Park=
=0A> > Expires: April 4, 2009=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 Samsung Electronics=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 S. Chakrabarti=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 IP Infusion=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 G. Mont=
enegro=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Microsoft Corporation=0A> >=A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 October 2008=0A> > =0A> > =0A> > Tr=
ansmission of IPv4 packets over IEEE 802.16's IP Convergence Sublayer=0A> >=
=A0 =A0 =A0 =A0 =A0 =A0 draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05.txt=0A=
> > =0A> > Status of this Memo=0A> > =0A> >=A0 =A0 By submitting this Inter=
net-Draft, each author represents that any=0A> >=A0 =A0 applicable patent o=
r other IPR claims of which he or she is aware=0A> >=A0 =A0 have been or wi=
ll be disclosed, and any of which he or she becomes=0A> >=A0 =A0 aware will=
 be disclosed, in accordance with Section 6 of BCP 79.=0A> > =0A> >=A0 =A0 =
Internet-Drafts are working documents of the Internet Engineering=0A> >=A0 =
=A0 Task Force (IETF), its areas, and its working groups.=A0 Note that=0A> =
>=A0 =A0 other groups may also distribute working documents as Internet-=0A=
> >=A0 =A0 Drafts.=0A> > =0A> >=A0 =A0 Internet-Drafts are draft documents =
valid for a maximum of six months=0A> >=A0 =A0 and may be updated, replaced=
, or obsoleted by other documents at any=0A> >=A0 =A0 time.=A0 It is inappr=
opriate to use Internet-Drafts as reference=0A> >=A0 =A0 material or to cit=
e them other than as "work in progress."=0A> > =0A> >=A0 =A0 The list of cu=
rrent Internet-Drafts can be accessed at=0A> >=A0 =A0 http://www.ietf.org/i=
etf/1id-abstracts.txt. =0A> > =0A> >=A0 =A0 The list of Internet-Draft Shad=
ow Directories can be accessed at=0A> >=A0 =A0 http://www.ietf.org/shadow.h=
tml. =0A> > =0A> >=A0 =A0 This Internet-Draft will expire on April 4, 2009.=
=0A> > =0A> > Abstract=0A> > =0A> >=A0 =A0 IEEE 802.16 is an air interface =
specification for wireless broadband=0A> >=A0 =A0 access.=A0 IEEE 802.16 ha=
s specified multiple service specific=0A> >=A0 =A0 convergence sublayers fo=
r transmitting upper layer protocols.=A0 The=0A> >=A0 =A0 packet CS (Packet=
 Convergence Sublayer) is used for the transport of=0A> >=A0 =A0 all packet=
-based protocols such as Internet Protocol (IP), IEEE 802.3=0A> >=A0 =A0 (E=
thernet) and IEEE 802.1Q (VLAN).=A0 The IP-specific part of the=0A> =0A> Me=
anwhile the IEEE802.16-2009 (was REV2) specification has been released.=0A>=
 IEEE802.16-2009 does not know anymore about the IEEE 802.1Q (VLAN) CS.=0A>=
 =0A> >=A0 =A0 Packet CS enables the transport of IPv4 packets directly ove=
r the=0A> > =0A> > =0A> > =0A> > Madanapalli, et al.=A0 =A0 =A0 Expires Apr=
il 4, 2009=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 [Page 1]=0A> > =0A> > Internet-Dr=
aft=A0 =A0 =A0 =A0 IPv4 over IEEE 802.16's IP CS=A0 =A0 =A0 =A0 October 200=
8=0A> > =0A> > =0A> >=A0 =A0 IEEE 802.16 MAC.=0A> > =0A> >=A0 =A0 This docu=
ment specifies the frame format, the Maximum Transmission=0A> >=A0 =A0 Unit=
 (MTU) and address assignment procedures for transmitting IPv4=0A> >=A0 =A0=
 packets over the IP-specific part of the Packet Convergence Sublayer=0A> >=
=A0 =A0 of IEEE 802.16.=0A> > =0A> > =0A> > Table of Contents=0A> > =0A> >=
=A0 =A0 1.=A0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . =
.=A0 3=0A> >=A0 =A0 2.=A0 Terminology=A0 . . . . . . . . . . . . . . . . . =
. . . . . . . .=A0 3=0A> >=A0 =A0 3.=A0 Typical Network Architecture for IP=
v4 over IEEE 802.16 . . . .=A0 3=0A> >=A0 =A0 =A0 3.1.=A0 IEEE 802.16 IPv4 =
Convergence sub-layer support . . . . . .=A0 3=0A> >=A0 =A0 4.=A0 IPv4 CS l=
ink in 802.16 Networks=A0 . . . . . . . . . . . . . . .=A0 4=0A> >=A0 =A0 =
=A0 4.1.=A0 IPv4 CS link establishment . . . . . . . . . . . . . . . .=A0 4=
=0A> >=A0 =A0 =A0 4.2.=A0 Frame Format for IPv4 Packets=A0 . . . . . . . . =
. . . . . .=A0 4=0A> >=A0 =A0 =A0 4.3.=A0 Maximum Transmission Unit=A0 . . =
. . . . . . . . . . . . . .=A0 5=0A> >=A0 =A0 5.=A0 Subnet Model and IPv4 A=
ddress Assignment . . . . . . . . . . .=A0 7=0A> >=A0 =A0 =A0 5.1.=A0 IPv4 =
Unicast Address Assignment and Router Discovery . . .=A0 7=0A> >=A0 =A0 =A0=
 5.2.=A0 Address Resolution Protocol=A0 . . . . . . . . . . . . . . .=A0 8=
=0A> >=A0 =A0 =A0 5.3.=A0 IP Multicast Address Mapping . . . . . . . . . . =
. . . . .=A0 8=0A> >=A0 =A0 6.=A0 Security Considerations=A0 . . . . . . . =
. . . . . . . . . . . .=A0 8=0A> >=A0 =A0 7.=A0 IANA Considerations=A0 . . =
. . . . . . . . . . . . . . . . . . .=A0 8=0A> >=A0 =A0 8.=A0 Acknowledgeme=
nts . . . . . . . . . . . . . . . . . . . . . . .=A0 8=0A> >=A0 =A0 9.=A0 R=
eferences . . . . . . . . . . . . . . . . . . . . . . . . . .=A0 9=0A> >=A0=
 =A0 =A0 9.1.=A0 Normative References . . . . . . . . . . . . . . . . . . .=
=A0 9=0A> >=A0 =A0 =A0 9.2.=A0 Informative References . . . . . . . . . . .=
 . . . . . . .=A0 9=0A> >=A0 =A0 Appendix A.=A0 Multiple Convergence Layers=
 - Impact on Subnet=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Model . . . . . . =
. . . . . . . . . . . . . . . . . . 10=0A> >=A0 =A0 Appendix B.=A0 Sending =
and Receiving IPv4 Packets=A0 . . . . . . . . . 10=0A> >=A0 =A0 Appendix C.=
=A0 WiMAX IPCS MTU size . . . . . . . . . . . . . . . . . 11=0A> >=A0 =A0 A=
ppendix D.=A0 Thoughts on handling multicast-broadcast IP=0A> >=A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 packets . . . . . . . . . . . . . . . . . . . . . . . 1=
2=0A> >=A0 =A0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . .=
 . . . 12=0A> >=A0 =A0 Intellectual Property and Copyright Statements . . .=
 . . . . . . . 14=0A> > =0A> > =0A> > =0A> > =0A> > =0A> > =0A> > =0A> > =
=0A> > =0A> > =0A> > =0A> > =0A> > =0A> > =0A> > =0A> > Madanapalli, et al.=
=A0 =A0 =A0 Expires April 4, 2009=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 [Page 2]=
=0A> > =0A> > Internet-Draft=A0 =A0 =A0 =A0 IPv4 over IEEE 802.16's IP CS=
=A0 =A0 =A0 =A0 October 2008=0A> > =0A> > =0A> > 1.=A0 Introduction=0A> > =
=0A> >=A0 =A0 IEEE 802.16 [IEEE802_16] is a connection oriented access tech=
nology=0A> >=A0 =A0 for the last mile.=A0 The IEEE 802.16 specification inc=
ludes the PHY=0A> >=A0 =A0 and MAC layers.=A0 The MAC includes various conv=
ergence sublayers (CS)=0A> >=A0 =A0 for transmitting higher layer packets i=
ncluding IPv4 packets=0A> >=A0 =A0 [RFC5154].=0A> > =0A> >=A0 =A0 The scope=
 of this specification is limited to the operation of IPv4=0A> >=A0 =A0 ove=
r the IP-specific part of the packet CS (referred to as "IPv4 CS"=0A> >=A0 =
=A0 or simply "IP CS" in this document).=0A> =0A> IPv4 CS should be used th=
roughout the document to prevent mixing it up with the =0A> IPv6 CS specifi=
cation. There is nothing like IP CS in the IEEE802.16 =0A> specification, t=
here is only IPv4 CS and IPv6 CS.=0A> BTW: there is now a single ETH CS car=
rying IPv4 as well as IPv6 payload.=0A> =0A> >=A0 =A0 This document specifi=
es a method for encapsulating and transmitting=0A> >=A0 =A0 IPv4 [RFC0791] =
packets over the IP CS of IEEE 802.16.=A0 This document=0A> =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ^IPv4 CS=0A> >=A0 =
=A0 also specifies the MTU and address assignment method for the IEEE=0A> =
=0A> Which MTU, which address assignment? More concise wording would help.=
=0A> =0A> >=A0 =A0 802.16 based networks using IP CS.=0A> =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ^IPv4 CS=0A> > =0A> >=A0 =
=A0 This document also discusses ARP (Address Resolution Protocol) and=0A> =
>=A0 =A0 Multicast Address Mapping whose operation is similar to any other=
=0A> >=A0 =A0 point-to-point link model.=0A> =0A> What do you mean with thi=
s sentence?=0A> =0A> >=A0 =A0 The key words "MUST", "MUST NOT", "REQUIRED",=
 "SHALL", "SHALL NOT",=0A> >=A0 =A0 "SHOULD", "SHOULD NOT", "RECOMMENDED", =
"MAY", and "OPTIONAL" in this=0A> >=A0 =A0 document are to be interpreted a=
s described in [RFC2119].=0A> > =0A> > =0A> > 2.=A0 Terminology=0A> > =0A> =
>=A0 =A0 The terminology in this document is based on the definitions in=0A=
> >=A0 =A0 [RFC5154].=0A> > =0A> > =0A> > 3.=A0 Typical Network Architectur=
e for IPv4 over IEEE 802.16=0A> > =0A> >=A0 =A0 The network architecture fo=
llows what is described in [RFC5154] and=0A> >=A0 =A0 [RFC5121].=A0 In a nu=
tshell, each MS is attached to an Access Router=0A> =0A> Please clarify 'MS=
'; according to IEEE802.16 it only covers PHY and MAC.=0A> According to IEE=
E802.16 the MS is not a 'host'.=0A> =0A> >=A0 =A0 (AR) through a Base Stati=
on (BS), a layer 2 entity (from the=0A> >=A0 =A0 perspective of the IPv6 li=
nk between the MS and access router (AR)).=0A> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 ^IPv4??? Copy&Paste mistake?=0A> > =0A> >=A0 =A0 For fu=
rther information on the typical network architecture, see=0A> >=A0 =A0 [RF=
C5121] section 5.=0A> > =0A> > 3.1.=A0 IEEE 802.16 IPv4 Convergence sub-lay=
er support=0A> > =0A> >=A0 =A0 As described in [RFC5154] section 3.3., an I=
P specific subpart=0A> >=A0 =A0 classifier carries either IPv4 or IPv6 payl=
oads.=A0 In this document,=0A> >=A0 =A0 we are focusing on the IPv4 over IP=
 Convergence Sublayer.=0A> =0A> Section 3.3 of [RFC5154] is outdated! IEEE8=
02.16-2009 introduced a refined CS =0A> structure. IMHO, we shouldn't make =
references to outdated specifications, but =0A> base the work on the most r=
ecent IEEE802.16 specification.=0A> =0A> > =0A> > =0A> > =0A> > =0A> > Mada=
napalli, et al.=A0 =A0 =A0 Expires April 4, 2009=A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 [Page 3]=0A> > =0A> > Internet-Draft=A0 =A0 =A0 =A0 IPv4 over IEEE 802=
.16's IP CS=A0 =A0 =A0 =A0 October 2008=0A> > =0A> > =0A> >=A0 =A0 For furt=
her information on the IEEE 802.16 Convergence Sublayer and=0A> >=A0 =A0 en=
capsulation of IP packets, see [RFC5121] section 4 and [RFC5154]=0A> >=A0 =
=A0 section 3.3.=0A> =0A> As [RFC5154] is outdated, I would propose to prov=
ide an updated section 3.3. as =0A> part of the IPv4 CS document.=0A> =0A> =
> 4.=A0 IPv4 CS link in 802.16 Networks=0A> > =0A> >=A0 =A0 This document d=
efines the IPv4 CS link as a point-to-point link=0A> >=A0 =A0 between the M=
S and the AR using a set of service flows consisting of=0A> =0A> MS is not =
the host. What is a link between a L2 device (MS) and a L3 device =0A> (AR)=
?=0A> =0A> >=A0 =A0 MAC transport connections between a MS and BS, and L2 t=
unnel(s)=0A> >=A0 =A0 between between a BS and AR.=A0 It is recommended tha=
t a tunnel be=0A> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 ^is=0A> >=A0 =A0 established between the AR and a BS based on 'per MS' or =
'per service=0A> >=A0 =A0 flow' (An MS can have multiple service flows each=
 of which are=0A> =0A> What is a tunnel between BS and AR based on 'per MS'=
? It seems, some GRE =0A> functionality is assumed here without spelling it=
 out.=0A> =0A> >=A0 =A0 identified by a unique service flow ID).=A0 Then th=
e tunnel(s) for an=0A> >=A0 =A0 MS, in combination with the MS's MAC transp=
ort connections, forms a=0A> >=A0 =A0 single point-to-point link.=A0 Each M=
S belongs to a different link and=0A> =0A> How does this work - multiple tu=
nnels between two endpoints forming a single =0A> link? I would assume, tha=
t there must be some classification in place, which is =0A> part of the BS =
according to IEEE802.16, not part of the AR, like the authors =0A> assume i=
n the sentence.=0A> =0A> >=A0 =A0 is assigned an unique IPv4 address per re=
commendations in [RFC4968].=0A> > =0A> >=A0 =A0 To summarize:=0A> > =0A> >=
=A0 =A0 o=A0 IPv4 CS uses the IPv4 header fields to classify the packets an=
d=0A> >=A0 =A0 =A0 map to the appropriate CID.=0A> =0A> The previous text t=
alks about service flows; why 'CID' is mentioned here?=0A> =0A> >=A0 =A0 o=
=A0 A point-to-point link between MS and AR is established.=0A> =0A> How do=
 the two statements fit together? How does IPv4 CS establish a p2p link?=0A=
> =0A> > =0A> > 4.1.=A0 IPv4 CS link establishment=0A> > =0A> >=A0 =A0 In o=
rder to enable the sending and receiving of IPv4 packets between=0A> >=A0 =
=A0 the MS and the AR, the link between the MS and the AR via the BS=0A> >=
=A0 =A0 needs to be established.=A0 This section explains the link=0A> >=A0=
 =A0 establishment procedures following section 6.2 of [RFC5121].=A0 Steps=
=0A> >=A0 =A0 1-4 are same as indicated in 6.2 of [RFC5121].=A0 In step 5, =
support=0A> >=A0 =A0 for IPv4 is indicated.=A0 In step 6, an initial servic=
e flow is created=0A> =0A> Initial service flow? [RFC5121] does not specifi=
es further service flows.=0A> =0A> >=A0 =A0 that can be used for exchanging=
 IP layer signaling messages, e.g.=0A> >=A0 =A0 address assignment procedur=
es using DHCP.=0A> > =0A> >=A0 =A0 The address assignment procedure depends=
 on the MS mode - i,e.=0A> >=A0 =A0 whether it is acting as a Mobile IPv4 c=
lient or a Proxy Mobile IP=0A> >=A0 =A0 client or a Simple IP client.=A0 In=
 the most common case, the MS=0A> >=A0 =A0 requests an IP address using DHC=
P.=0A> =0A> What is the difference between a Proxy MIP client and a Simple =
IP client?=0A> Does the 'MS' request an IP address by DHCP in the case of C=
lient-MIP?=0A> =0A> > =0A> > 4.2.=A0 Frame Format for IPv4 Packets=0A> > =
=0A> >=A0 =A0 IPv4 packets are transmitted in Generic IEEE 802.16 MAC frame=
s in the=0A> >=A0 =A0 data payloads of the 802.16 PDU ( see section 3.2 of =
[RFC5154] ).=0A> > =0A> > =0A> > =0A> > =0A> > =0A> > =0A> > =0A> > Madanap=
alli, et al.=A0 =A0 =A0 Expires April 4, 2009=A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 [Page 4]=0A> > =0A> > Internet-Draft=A0 =A0 =A0 =A0 IPv4 over IEEE 802.=
16's IP CS=A0 =A0 =A0 =A0 October 2008=0A> > =0A> > =0A> >=A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 1=0A> =
>=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 0 1 2 3 4 5 6 7 8 9 0 1 2 =
3 4 5=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+-+=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |H|E=
|=A0 TYPE=A0 =A0 |R|C|EKS|R|LEN=A0 |=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=0A> >=A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 |=A0 =A0 LEN LSB=A0 =A0 |=A0 =A0 CID MSB=A0 =A0=
 |=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |=A0 =
=A0 CID LSB=A0 =A0 |=A0 =A0 HCS=A0 =A0 =A0 =A0 |=0A> >=A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=0A> >=A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |=A0 =A0 =A0 =A0 =A0 =A0 IPv4=A0 =
=A0 =A0 =A0 =A0 =A0 =A0 |=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 +-=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 -+=0A> >=A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |=A0 =A0 =A0 =A0 =A0 =A0 header=
=A0 =A0 =A0 =A0 =A0 =A0 |=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 +-=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 -+=0A> >=A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |=A0 =A0 =A0 =A0 =A0 =A0 and=A0=
 =A0 =A0 =A0 =A0 =A0 =A0 |=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 +-=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 -+=0A> >=A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 /=A0 =A0 =A0 =A0 =A0 =A0 payloa=
d=A0 =A0 =A0 =A0 =A0 /=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 +-=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 -+=0A> >=A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 |=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 |CRC (optional) |=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 +-+-+-+-+-+-+-+-+=0A> > =0A> > =0A> >=A0 =A0 =A0 =A0 =A0 Fi=
gure 1: IEEE 802.16 MAC Frame Format for=A0 IPv4 Packets=0A> > =0A> >=A0 =
=A0 =A0 H: Header Type (1 bit).=A0 Shall be set to zero indicating that it=
=0A> >=A0 =A0 =A0 is a Generic MAC PDU.=0A> >=A0 =A0 =A0 E: Encryption Cont=
rol. 0 =3D Payload is not encrypted; 1 =3D Payload=0A> >=A0 =A0 =A0 is encr=
ypted.=0A> >=A0 =A0 =A0 R: Reserved.=A0 Shall be set to zero.=0A> >=A0 =A0 =
=A0 C: CRC Indicator. 1 =3D CRC is included, 0 =3D 1 No CRC is included=0A>=
 >=A0 =A0 =A0 EKS: Encryption Key Sequence=0A> >=A0 =A0 =A0 LEN: The Length=
 in bytes of the MAC PDU including the MAC header=0A> >=A0 =A0 =A0 and the =
CRC if present (11 bits)=0A> >=A0 =A0 =A0 CID: Connection Identifier (16 bi=
ts)=0A> >=A0 =A0 =A0 HCS: Header Check Sequence (8 bits)=0A> >=A0 =A0 =A0 C=
RC: An optional 8-bit field.=A0 CRC appended to the PDU after=0A> >=A0 =A0 =
=A0 encryption.=0A> >=A0 =A0 =A0 TYPE: This field indicates the subheaders =
(Mesh subheader,=0A> >=A0 =A0 =A0 Fragmentation Subheader, Packing subheade=
r etc and special payload=0A> >=A0 =A0 =A0 types (ARQ) present in the messa=
ge payload=0A> > =0A> > 4.3.=A0 Maximum Transmission Unit=0A> > =0A> >=A0 =
=A0 =A0 The MTU value for IPv4 packets on an IEEE 802.16 link is=0A> >=A0 =
=A0 configurable.=A0 The default MTU for IPv4 packets over an IEEE 802.16=
=0A> =0A> 'is configurable'?? How, by which means??=0A> =0A> >=A0 =A0 =A0 l=
ink SHOULD be 1500 octets.=0A> > =0A> > =0A> > =0A> > =0A> > Madanapalli, e=
t al.=A0 =A0 =A0 Expires April 4, 2009=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 [Page=
 5]=0A> > =0A> > Internet-Draft=A0 =A0 =A0 =A0 IPv4 over IEEE 802.16's IP C=
S=A0 =A0 =A0 =A0 October 2008=0A> > =0A> > =0A> >=A0 =A0 Per [RFC5121] sect=
ion 6.3, the IP MTU can vary to be larger or=0A> >=A0 =A0 smaller than 1500=
 octets.=0A> > =0A> >=A0 =A0 if an MS transmits 1500-octet packets in a dep=
loyment with a smaller=0A> >=A0 =A0 MTU, packets from the MS may be dropped=
 at the link-layer silently.=0A> >=A0 =A0 Unlike IPv6, in which departures =
from the default MTU are readily=0A> >=A0 =A0 advertised via the MTU option=
 in Neighbor Discovery, there is no=0A> >=A0 =A0 similarly reliable mechani=
sm in IPv4, as the legacy IPv4 client=0A> >=A0 =A0 implementations do not d=
etermine the link MTU by default before=0A> >=A0 =A0 sending packets.=A0 Ev=
en though there is a DHCP option to accomplish=0A> >=A0 =A0 this, DHCP serv=
ers are required to provide the MTU information only=0A> >=A0 =A0 when requ=
ested.=0A> > =0A> >=A0 =A0 Discovery and configuration of the proper link M=
TU value ensures=0A> >=A0 =A0 adequate usage of the network bandwidth and r=
esources.=A0 Accordingly,=0A> >=A0 =A0 deployments should avoid packet loss=
 due to a mismatch between the=0A> >=A0 =A0 default MTU and the configured =
link MTUs.=0A> > =0A> >=A0 =A0 =A0 Some of the mechanisms available for the=
 IPv4 CS host to find out=0A> >=A0 =A0 the link's MTU value and mitigate MT=
U-related issues are:=0A> > =0A> >=A0 =A0 o=A0 The IEEE is currently revisi=
ng 802.16 (see 802.16Rev2=0A> =0A> IEEE802.16 has revised the specification=
. Update the reference.=0A> =0A> >=A0 =A0 =A0 [802_16REV2]) to (among other=
 things) allow providing the Service=0A> >=A0 =A0 =A0 Data Unit or MAC MTU =
in the IEEE 802.16 SBC-REQ/SBC-RSP phase,=0A> >=A0 =A0 =A0 such that future=
 IEEE 802.16 compliant clients can infer and=0A> >=A0 =A0 =A0 configure the=
 negotiated MTU size for the IPv4 CS link.=A0 However,=0A> >=A0 =A0 =A0 the=
 implementation must communicate the negotiated MTU value to=0A> >=A0 =A0 =
=A0 the IP layer to adjust the IP Maximum payload size for proper=0A> >=A0 =
=A0 =A0 handling of fragmentation.=A0 Note that this method is useful only=
=0A> >=A0 =A0 =A0 when MS is directly connected to the BS.=0A> >=A0 =A0 o=
=A0 Configuration and negotiation of MTU size at the network layer by=0A> >=
=A0 =A0 =A0 using the DHCP interface MTU option [RFC2132].=0A> > =0A> >=A0 =
=A0 This document recommends that all future implementations of IPv4 and=0A=
> =0A> Why 'future'?=0A> =0A> >=A0 =A0 IPv4 CS clients SHOULD implement the=
 DHCP interface MTU option=0A> >=A0 =A0 [RFC2132] in order to configure its=
 interface MTU accordingly.=0A> > =0A> >=A0 =A0 In the absence of DHCP MTU =
configuration, the client node (MS) has=0A> >=A0 =A0 two alternatives: 1) u=
se the default MTU (1500 bytes) or 2) determine=0A> >=A0 =A0 the MTU by the=
 methods described in [802_16REV2].=0A> =0A> Can MS rely on the IEEE802.16 =
methods? Mandatory for all IEEE802.16 =0A> implementations?=0A> =0A> >=A0 =
=A0 Additionally, the clients are encouraged to run PMTU[RFC 1191] or=0A> >=
=A0 =A0 PPMTUD[RFC 4821].=A0 However, the PMTU mechanism has inherent probl=
ems=0A> >=A0 =A0 of packet loss due to ICMP messages not reaching the sende=
r and IPv4=0A> >=A0 =A0 routers not fragmenting the packets due to the DF b=
it being set in=0A> >=A0 =A0 the IP packet.=A0 The above mentioned path MTU=
 mechanisms will take=0A> >=A0 =A0 care of the MTU size between the MS and =
its correspondent node across=0A> >=A0 =A0 different flavors of convergence=
 layers in the access networks.=0A> > =0A> > =0A> > =0A> > Madanapalli, et =
al.=A0 =A0 =A0 Expires April 4, 2009=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 [Page 6=
]=0A> > =0A> > Internet-Draft=A0 =A0 =A0 =A0 IPv4 over IEEE 802.16's IP CS=
=A0 =A0 =A0 =A0 October 2008=0A> > =0A> > =0A> > 5.=A0 Subnet Model and IPv=
4 Address Assignment=0A> > =0A> >=A0 =A0 The Subnet Model recommended for I=
Pv4 over IEEE 802.16 using IP CS is=0A> >=A0 =A0 based on the point-to-poin=
t link between MS and AR [RFC4968], hence=0A> >=A0 =A0 each MS shall be ass=
igned an address with 32bit prefix-length or=0A> >=A0 =A0 subnet-mask.=A0 T=
he point-to-point link between MS and AR is achieved=0A> >=A0 =A0 using a s=
et of IEEE 802.16 MAC connections (identified by CIDs) and=0A> >=A0 =A0 an =
L2 tunnel (e.g., a GRE tunnel) per MS between BS and AR.=A0 If the=0A> >=A0=
 =A0 AR is co-located with the BS, then the set of IEEE 802.16 MAC=0A> >=A0=
 =A0 connections between the MS and BS/AR represent the point-to- point=0A>=
 >=A0 =A0 connection.=0A> > =0A> > 5.1.=A0 IPv4 Unicast Address Assignment =
and Router Discovery=0A> > =0A> >=A0 =A0 DHCP [RFC2131] SHOULD be used for =
assigning IPv4 address for the MS.=0A> >=A0 =A0 DHCP messages are transport=
ed over the IEEE 802.16 MAC connection to=0A> >=A0 =A0 and from the BS and =
relayed to the AR.=A0 In case the DHCP server does=0A> >=A0 =A0 not reside =
in the AR, the AR SHOULD implement DHCP relay Agent=0A> >=A0 =A0 [RFC1542].=
=0A> > =0A> >=A0 =A0 Although DHCP is the recommended method of address ass=
ignment, it is=0A> >=A0 =A0 possible that the MS could be a pure Mobile IPv=
4 [RFC3344] device=0A> >=A0 =A0 which will be offered an IP address from it=
s home network after=0A> >=A0 =A0 successful Mobile IP [RFC3344] registrati=
on.=A0 In such situations, the=0A> >=A0 =A0 mobile host SHOULD use the defa=
ult link MTU in order to avoid any=0A> >=A0 =A0 link-layer packet loss due =
to larger than supported packet size in=0A> >=A0 =A0 the IP CS link.=0A> > =
=0A> >=A0 =A0 Router discovery messages [RFC1256] contain router solicitati=
on and=0A> >=A0 =A0 router advertisements.=A0 The Router solicitation messa=
ges (multicast=0A> >=A0 =A0 or broadcast) from the MS are delivered to the =
AR via the BS through=0A> >=A0 =A0 the point-to-point link.=A0 The BS SHOUL=
D map the all-routers multicast=0A> >=A0 =A0 nodes or broadcast nodes for r=
outer discovery to the AR's IP address=0A> >=A0 =A0 and deliver directly to=
 the AR.=A0 Similarly a router advertisement to=0A> >=A0 =A0 the all-nodes =
multicast nodes will be either unicast to each MS by=0A> >=A0 =A0 the BS se=
parately or put onto a multicast connection to which all MSs=0A> >=A0 =A0 a=
re listening to.=A0 If no multicast connection exists, and the BS does=0A> =
>=A0 =A0 not have the capability to aggregate and disaggregate the messages=
 to=0A> >=A0 =A0 and from the MS hosts, then the AR implementation must ens=
ure that=0A> >=A0 =A0 unicast messages are sent to the corresponding indivi=
dual MS hosts=0A> >=A0 =A0 within the set of broadcast or multicast recipie=
nts.=A0 This=0A> >=A0 =A0 specification simply assumes that the multicast s=
ervice is provided.=0A> >=A0 =A0 How the multicast service is implemented i=
n an IEEE 802.16 Packet CS=0A> >=A0 =A0 deployment is out of scope of this =
document.=0A> > =0A> >=A0 =A0 The 'Next hop' IP address of the IP CS MS is =
always the IP address of=0A> >=A0 =A0 the AR, because MS and AR are attache=
d via a point-to-point link.=0A> > =0A> > =0A> > =0A> > =0A> > Madanapalli,=
 et al.=A0 =A0 =A0 Expires April 4, 2009=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 [Pa=
ge 7]=0A> > =0A> > Internet-Draft=A0 =A0 =A0 =A0 IPv4 over IEEE 802.16's IP=
 CS=A0 =A0 =A0 =A0 October 2008=0A> > =0A> > =0A> > 5.2.=A0 Address Resolut=
ion Protocol=0A> > =0A> >=A0 =A0 The IP CS does not allow for transmission =
of ARP [RFC0826] packets.=0A> >=A0 =A0 Furthermore, in a point-to-point lin=
k model, address resolution is=0A> >=A0 =A0 not needed.=0A> > =0A> > 5.3.=
=A0 IP Multicast Address Mapping=0A> > =0A> >=A0 =A0 IPv4 multicast packets=
 are carried over the point-to-point link=0A> >=A0 =A0 between the AR and t=
he MS (via the BS).=A0 The IPv4 multicast packets=0A> >=A0 =A0 are classifi=
ed normally at the IP CS if the IEEE 802.16 MAC=0A> >=A0 =A0 connection has=
 been set up with a multicast IP address as a=0A> >=A0 =A0 classification p=
arameter for the destination IP address.=A0 The IPv4=0A> >=A0 =A0 multicast=
 address may be mapped into a multicast CID as defined in=0A> >=A0 =A0 the =
IEEE 802.16 specification.=A0 The mapping mechanism at the BS or=0A> >=A0 =
=A0 the relative efficiency of using a multicast CID as opposed to=0A> >=A0=
 =A0 simulating multicast by generating multiple unicast messages are out=
=0A> >=A0 =A0 of scope of this document.=A0 For further considerations on t=
he use of=0A> >=A0 =A0 multicast CIDs see [ETHCS].=0A> > =0A> > =0A> > 6.=
=A0 Security Considerations=0A> > =0A> >=A0 =A0 This document specifies tra=
nsmission of IPv4 packets over IEEE 802.16=0A> >=A0 =A0 networks with IPv4 =
Convergence Sublayer and does not introduce any=0A> >=A0 =A0 new vulnerabil=
ities to IPv4 specifications or operation.=A0 The=0A> >=A0 =A0 security of =
the IEEE 802.16 air interface is the subject of=0A> >=A0 =A0 [IEEE802_16].=
=A0 In addition, the security issues of the network=0A> >=A0 =A0 architectu=
re spanning beyond the IEEE 802.16 base stations is the=0A> >=A0 =A0 subjec=
t of the documents defining such architectures, such as WiMAX=0A> >=A0 =A0 =
Network Architecture [WMF].=0A> > =0A> > =0A> > 7.=A0 IANA Considerations=
=0A> > =0A> >=A0 =A0 This document has no actions for IANA.=0A> > =0A> > =
=0A> > 8.=A0 Acknowledgements=0A> > =0A> >=A0 =A0 The authors would like to=
 acknowledge the contributions of Bernard=0A> >=A0 =A0 Aboba, Dave Thaler, =
Jari Arkko, Bachet Sarikaya, Basavaraj Patil,=0A> >=A0 =A0 Paolo Narvaez, a=
nd Bruno Sousa for their review and comments.=A0 The=0A> >=A0 =A0 working g=
roup members Burcak Beser, Wesley George, Max Riegel and DJ=0A> >=A0 =A0 Jo=
hnston helped shape the MTU discussion for IPv4 CS link.=A0 Thanks to=0A> >=
=A0 =A0 many other members of the 16ng working group who commented on this=
=0A> >=A0 =A0 document to make it better.=0A> > =0A> > =0A> > =0A> > =0A> >=
 Madanapalli, et al.=A0 =A0 =A0 Expires April 4, 2009=A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 [Page 8]=0A> > =0A> > Internet-Draft=A0 =A0 =A0 =A0 IPv4 over I=
EEE 802.16's IP CS=A0 =A0 =A0 =A0 October 2008=0A> > =0A> > =0A> > 9.=A0 Re=
ferences=0A> > =0A> > 9.1.=A0 Normative References=0A> > =0A> >=A0 =A0 [RFC=
2119]=A0 Bradner, S., "Key words for use in RFCs to Indicate=0A> >=A0 =A0 =
=A0 =A0 =A0 =A0 =A0 Requirement Levels", BCP 14, RFC 2119, March 1997.=0A> =
> =0A> >=A0 =A0 [RFC0791]=A0 Postel, J., "Internet Protocol", STD 5, RFC 79=
1,=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 September 1981.=0A> > =0A> >=A0 =A0 [RF=
C0826]=A0 Plummer, D., "Ethernet Address Resolution Protocol: Or=0A> >=A0 =
=A0 =A0 =A0 =A0 =A0 =A0 converting network protocol addresses to 48.bit Eth=
ernet=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 address for transmission on Ethernet=
 hardware", STD 37,=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 RFC 826, November 1982=
.=0A> > =0A> >=A0 =A0 [RFC2131]=A0 Droms, R., "Dynamic Host Configuration P=
rotocol",=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 RFC 2131, March 1997.=0A> > =0A>=
 >=A0 =A0 [RFC1542]=A0 Wimer, W., "Clarifications and Extensions for the=0A=
> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 Bootstrap Protocol", RFC 1542, October 1993.=
=0A> > =0A> >=A0 =A0 [RFC5121]=A0 Patil, B., Xia, F., Sarikaya, B., Choi, J=
H., and S.=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 Madanapalli, "Transmission of I=
Pv6 via the IPv6=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 Convergence Sublayer over=
 IEEE 802.16 Networks", RFC 5121,=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 February=
 2008.=0A> > =0A> >=A0 =A0 [RFC5154]=A0 Jee, J., Madanapalli, S., and J. Ma=
ndin, "IP over IEEE=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 802.16 Problem Stateme=
nt and Goals", RFC 5154, April 2008.=0A> > =0A> >=A0 =A0 [RFC4968]=A0 Madan=
apalli, S., "Analysis of IPv6 Link Models for 802.16=0A> >=A0 =A0 =A0 =A0 =
=A0 =A0 =A0 Based Networks", RFC 4968, August 2007.=0A> > =0A> > 9.2.=A0 In=
formative References=0A> > =0A> >=A0 =A0 [RFC1191]=A0 Mogul, J. and S. Deer=
ing, "Path MTU discovery", RFC 1191,=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 Novem=
ber 1990.=0A> > =0A> >=A0 =A0 [RFC4821]=A0 Mathis, M. and J. Heffner, "Pack=
etization Layer Path MTU=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 Discovery", RFC 4=
821, March 2007.=0A> > =0A> >=A0 =A0 [RFC2132]=A0 Alexander, S. and R. Drom=
s, "DHCP Options and BOOTP Vendor=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 Extensio=
ns", RFC 2132, March 1997.=0A> > =0A> >=A0 =A0 [RFC4840]=A0 Aboba, B., Davi=
es, E., and D. Thaler, "Multiple=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 Encapsula=
tion Methods Considered Harmful", RFC 4840,=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =
=A0 April 2007.=0A> > =0A> >=A0 =A0 [RFC3344]=A0 Perkins, C., "IP Mobility =
Support for IPv4", RFC 3344,=0A> > =0A> > =0A> > =0A> > Madanapalli, et al.=
=A0 =A0 =A0 Expires April 4, 2009=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 [Page 9]=
=0A> > =0A> > Internet-Draft=A0 =A0 =A0 =A0 IPv4 over IEEE 802.16's IP CS=
=A0 =A0 =A0 =A0 October 2008=0A> > =0A> > =0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0=
 August 2002.=0A> > =0A> >=A0 =A0 [RFC1256]=A0 Deering, S., "ICMP Router Di=
scovery Messages", RFC 1256,=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 September 199=
1.=0A> > =0A> >=A0 =A0 [ETHCS]=A0 =A0 Jeon, H., Riegel, M., and S. Jeong, "=
Transmission of IP=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 over Ethernet over IEEE=
 802.16 Networks", April 2008,=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 > >=A0 =A0 =
=A0 =A0 =A0 =A0 =A0 draft-ietf-16ng-ip-over-ethernet-over-802.16-06.txt>.=
=0A> > =0A> >=A0 =A0 [802_16REV2]=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 Johnston=
, D., "SDU MTU Capability Declaration",=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 Ma=
rch 2008, .=0A> > =0A> >=A0 =A0 [IEEE802_16]=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =
=A0 "IEEE 802.16e, IEEE standard for Local and metropolitan=0A> >=A0 =A0 =
=A0 =A0 =A0 =A0 =A0 area networks, Part 16:Air Interface for fixed and Mobi=
le=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 broadband wireless access systems", Oct=
ober 2005.=0A> =0A> IEEE802.16-2009 is released and supersedes 16e as well =
as REV2.=0A> Why is the IEEE802.16 specification listed under informative?=
=0A> =0A> >=A0 =A0 [WMF]=A0 =A0 =A0 "WiMAX End-to-End Network Systems Archi=
tecture Stage 2-3=0A> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 Release 1.2,=0A> >=A0 =
=A0 =A0 =A0 =A0 =A0 =A0 http://www.wimaxforum.org/technology/documents",=0A=
> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 January 2008.=0A> > =0A> > =0A> > Appendix A=
.=A0 Multiple Convergence Layers - Impact on Subnet Model=0A> > =0A> >=A0 =
=A0 Two different MSs using two different convergence sublayers (e.g. an=0A=
> >=A0 =A0 MS using Ethernet CS only and another MS using IP CS only) canno=
t=0A> >=A0 =A0 communicate at data link layer and requires interworking at =
IP layer.=0A> >=A0 =A0 For this reason, these two nodes must be configured =
to be on two=0A> >=A0 =A0 different subnets.=A0 For more information refer =
to [RFC4840].=0A> > =0A> > =0A> > Appendix B.=A0 Sending and Receiving IPv4=
 Packets=0A> > =0A> >=A0 =A0 IEEE 802.16 MAC is a point-to-multipoint conne=
ction oriented air-=0A> >=A0 =A0 interface, and the process of sending and =
receiving of IPv4 packets=0A> >=A0 =A0 is different from multicast-capable =
shared medium technologies like=0A> >=A0 =A0 Ethernet.=0A> > =0A> >=A0 =A0 =
Before any packets are transmitted, a IEEE 802.16 transport=0A> >=A0 =A0 co=
nnection must be established.=A0 This connection consists of IEEE=0A> >=A0 =
=A0 802.16 MAC transport connection between MS and BS and an L2 tunnel=0A> =
>=A0 =A0 between BS and AR (if these two are not co-located).=A0 This IEEE=
=0A> >=A0 =A0 802.16 transport connection provides a point-to-point link be=
tween=0A> >=A0 =A0 the MS and AR.=A0 All the packets originated at the MS a=
lways reach the=0A> >=A0 =A0 AR before being transmitted to the final desti=
nation.=0A> > =0A> > =0A> > =0A> > Madanapalli, et al.=A0 =A0 =A0 Expires A=
pril 4, 2009=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 [Page 10]=0A> > =0A> > Internet=
-Draft=A0 =A0 =A0 =A0 IPv4 over IEEE 802.16's IP CS=A0 =A0 =A0 =A0 October =
2008=0A> > =0A> > =0A> >=A0 =A0 IPv4 packets are carried directly in the pa=
yload of IEEE 802.16=0A> >=A0 =A0 frames when the IPv4 CS is used.=A0 IPv4 =
CS classifies the packet based=0A> >=A0 =A0 on upper layer (IP and transpor=
t layers) header fields to place the=0A> >=A0 =A0 packet on one of the avai=
lable connections identified by the CID.=0A> >=A0 =A0 The classifiers for t=
he IPv4 CS are source and destination IPv4=0A> >=A0 =A0 addresses, source a=
nd destinations ports, Type-of-Service and IP=0A> >=A0 =A0 protocol field.=
=A0 The CS may employ Packet Header Suppression (PHS)=0A> >=A0 =A0 after th=
e classification.=0A> > =0A> >=A0 =A0 The BS optionally reconstructs the pa=
yload header if PHS is in use.=0A> >=A0 =A0 It then tunnels the packet that=
 has been received on a particular MAC=0A> >=A0 =A0 connection to the AR.=
=A0 Similarly the packets received on a tunnel=0A> >=A0 =A0 interface from =
the AR, would be mapped to a particular CID using the=0A> >=A0 =A0 IPv4 cla=
ssification mechanism.=0A> > =0A> >=A0 =A0 AR performs normal routing for t=
he packets that it receives,=0A> >=A0 =A0 processing them per its forwardin=
g table.=A0 However, the DHCP relay=0A> >=A0 =A0 agent in the AR MUST maint=
ain the tunnel interface on which it=0A> >=A0 =A0 receives DHCP requests so=
 that it can relay the DHCP responses to the=0A> >=A0 =A0 correct MS.=A0 On=
e way of doing this is to have a mapping between MAC=0A> >=A0 =A0 address a=
nd Tunnel Identifier.=0A> =0A> Which MAC address?=0A> =0A> > =0A> > Appendi=
x C.=A0 WiMAX IPCS MTU size=0A> > =0A> >=A0 =A0 WiMAX (Worldwide Interopera=
bility for Microwave Access) forum has=0A> >=A0 =A0 defined a network archi=
tecture[WMF].=A0 Furthermore, WiMAX has=0A> >=A0 =A0 specified IPv4 CS supp=
ort for transmission of IPv4 packets between MS=0A> >=A0 =A0 and BS over th=
e IEEE 802.16 link.=A0 The WiMAX IPv4 CS and this=0A> >=A0 =A0 specificatio=
n are similar.=A0 One significant difference, however, is=0A> >=A0 =A0 that=
 the WiMAX Forum [WMF] has specified the IP MTU as 1400 octets=0A> >=A0 =A0=
 [WMF] as opposed to 1500 in this specification.=0A> > =0A> >=A0 =A0 Hence =
if an IPv4 CS MS configured with an MTU of 1500 octet enters a=0A> >=A0 =A0=
 WiMAX network, some of the issues mentioned in this specification may=0A> =
>=A0 =A0 arise.=A0 As mentioned in section 4.3, the possible mechanisms are=
 not=0A> >=A0 =A0 guaranteed to work.=A0 Furthermore, an IPv4 CS client is =
not capable of=0A> >=A0 =A0 doing ARP probing to find out the link MTU.=A0 =
On the other hand, it is=0A> >=A0 =A0 imperative for an MS to know the link=
 MTU size.=A0 In practice, MS=0A> >=A0 =A0 should be able to sense or deduc=
e the fact that they are operating=0A> >=A0 =A0 within a WiMAX network (e.g=
., given the WiMAX-specific=0A> >=A0 =A0 particularities of the authenticat=
ion and network entry procedures),=0A> >=A0 =A0 and adjust their MTU size a=
ccordingly.=A0 This document makes no=0A> >=A0 =A0 further assumptions in t=
his respect.=0A> =0A> Appendix C should be removed.=0A> Only WiMAX devices =
will enter WiMAX networks, and WiMAX devices know about the =0A> MTU size i=
n WiMAX networks.=0A> =0A> > =0A> > =0A> > =0A> > =0A> > =0A> > =0A> > Mada=
napalli, et al.=A0 =A0 =A0 Expires April 4, 2009=A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 [Page 11]=0A> > =0A> > Internet-Draft=A0 =A0 =A0 =A0 IPv4 over IEEE 80=
2.16's IP CS=A0 =A0 =A0 =A0 October 2008=0A> > =0A> > =0A> > Appendix D.=A0=
 Thoughts on handling multicast-broadcast IP packets=0A> > =0A> >=A0 =A0 Al=
though this document does not directly specify details of multicast=0A> >=
=A0 =A0 or broadcast packet handling, here are some suggestions:=0A> > =0A>=
 >=A0 =A0 While uplink connections from the MSs to the BS provide only unic=
ast=0A> >=A0 =A0 transmission capabilities, downlink connections can be use=
d for=0A> >=A0 =A0 multicast transmission to a group of MSs as well as unic=
ast=0A> >=A0 =A0 transmission from the BS to a single MS.=A0 For all-node I=
P addresses,=0A> >=A0 =A0 the AR or BS should have special mapping and the =
packets should be=0A> >=A0 =A0 distributed to all active point-to-point con=
nections by the AR or by=0A> >=A0 =A0 the BS.=A0 All-router multicast packe=
ts and any broadcast packets from=0A> >=A0 =A0 a MS will be forwarded to th=
e AR by the BS.=A0 If BS and MS are co-=0A> >=A0 =A0 located, then the firs=
t approach is more useful.=A0 If the AR and BS=0A> >=A0 =A0 are located sep=
arately then the second approach should be=0A> >=A0 =A0 implemented.=A0 An =
initial capability exchange message should be=0A> >=A0 =A0 performed betwee=
n BS and AR (if they are not co-located) to determine=0A> >=A0 =A0 who woul=
d perform the distribution of multicast/broadcast packets.=0A> >=A0 =A0 Suc=
h mechansim should be part of L2 exchange during the connection=0A> >=A0 =
=A0 setup and is out of scope of this document.=A0 In order to save energy=
=0A> >=A0 =A0 of the wireless end devices in the IEEE 802.16 wireless netwo=
rk, it=0A> >=A0 =A0 is recommened that the multicast and broadcast from net=
work side to=0A> >=A0 =A0 device side should be reduced.=A0 Only DHCP, IGMP=
, Router advertisemnet=0A> >=A0 =A0 packets are allowed on the downlink for=
 multicast and broadcast IP=0A> >=A0 =A0 addresses.=A0 Other protocols usin=
g multicast and broadcast IP=0A> >=A0 =A0 addresses should be permitted thr=
ough local AR/BS configuration.=0A> > =0A> > =0A> > Authors' Addresses=0A> =
> =0A> >=A0 =A0 Syam Madanapalli=0A> >=A0 =A0 Ordyn Technologies=0A> >=A0 =
=A0 1st Floor, Creator Building, ITPL=0A> >=A0 =A0 Bangalore - 560066=0A> >=
=A0 =A0 India=0A> > =0A> >=A0 =A0 Email: smadanapalli@gmail.com=0A> > =0A> =
> =0A> >=A0 =A0 Soohong Daniel Park=0A> >=A0 =A0 Samsung Electronics=0A> >=
=A0 =A0 416 Maetan-3dong, Yeongtong-gu=0A> >=A0 =A0 Suwon 442-742=0A> >=A0 =
=A0 Korea=0A> > =0A> >=A0 =A0 Email: soohong.park@samsung.com=0A> > =0A> > =
=0A> > =0A> > =0A> > =0A> > Madanapalli, et al.=A0 =A0 =A0 Expires April 4,=
 2009=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 [Page 12]=0A> > =0A> > Internet-Draft=
=A0 =A0 =A0 =A0 IPv4 over IEEE 802.16's IP CS=A0 =A0 =A0 =A0 October 2008=
=0A> > =0A> > =0A> >=A0 =A0 Samita Chakrabarti=0A> >=A0 =A0 IP Infusion=0A>=
 >=A0 =A0 1188 Arques Avenue=0A> >=A0 =A0 Sunnyvale, CA=0A> >=A0 =A0 USA=0A=
> > =0A> >=A0 =A0 Email: samitac@ipinfusion.com=0A> > =0A> > =0A> >=A0 =A0 =
Gabriel Montenegro=0A> >=A0 =A0 Microsoft Corporation=0A> >=A0 =A0 Redmond,=
 Washington=0A> >=A0 =A0 USA=0A> > =0A> >=A0 =A0 Email: gabriel.montenegro@=
microsoft.com=0A> > =0A

From pekkas@netcore.fi  Wed Jun 10 03:50:34 2009
Return-Path: <pekkas@netcore.fi>
X-Original-To: 16ng@core3.amsl.com
Delivered-To: 16ng@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D1D6328C105 for <16ng@core3.amsl.com>; Wed, 10 Jun 2009 03:50:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.532
X-Spam-Level: 
X-Spam-Status: No, score=-2.532 tagged_above=-999 required=5 tests=[AWL=0.067,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bzrEBAdM8vR0 for <16ng@core3.amsl.com>; Wed, 10 Jun 2009 03:50:33 -0700 (PDT)
Received: from netcore.fi (eunet-gw.ipv6.netcore.fi [IPv6:2001:670:86:3001::1]) by core3.amsl.com (Postfix) with ESMTP id 3E4F13A68FE for <16ng@ietf.org>; Wed, 10 Jun 2009 03:50:33 -0700 (PDT)
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.13.8/8.13.8) with ESMTP id n5AAoXNS019667 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Jun 2009 13:50:33 +0300
Received: from localhost (pekkas@localhost) by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id n5AAoTqP019663; Wed, 10 Jun 2009 13:50:29 +0300
Date: Wed, 10 Jun 2009 13:50:29 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: gabriel montenegro <g_e_montenegro@yahoo.com>
In-Reply-To: <553392.88380.qm@web82604.mail.mud.yahoo.com>
Message-ID: <alpine.LRH.2.00.0906101344500.19541@netcore.fi>
References: <2828BDE8DC61004E8104C78E82A0B39710B25385F2@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com><BC27158B99D3064A955ADE084783900C01B5CBC8@DEMUEXC014.nsn-intra.net> <Pine.GSO.4.64.0905151247200.12703@tin>, <046201c9d589$267cf8d0$7376ea70$@com> <BAA9BC6C-6B59-4BA6-B63D-E09C26E0194B@mimectl> <BC27158B99D3064A955ADE084783900C020F18E5@DEMUEXC014.nsn-intra.net> <056601c9d7e8$b8be17e0$2a3a47a0$@com> <556994.50253.qm@web82604.mail.mud.yahoo.com> <06ab01c9d8cd$079cc660$16d65320$@com> <BC27158B99D3064A955ADE084783900C020F26B5@DEMUEXC014.nsn-intra.net> <916575.77425.qm@web82607.mail.mud.yahoo.com> <570230.22436.qm@web82606.mail.mud.yahoo.com> <Pine.GSO.4.64.0906040915000.16060@tin> <553392.88380.qm@web82604.mail.mud.yahoo.com>
User-Agent: Alpine 2.00 (LRH 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="1589707168-1910595125-1244630933=:19541"
Content-ID: <alpine.LRH.2.00.0906101349010.19541@netcore.fi>
X-Virus-Scanned: clamav-milter 0.95.1 at otso.netcore.fi
X-Virus-Status: Clean
Cc: ext Alper Yegin <alper.yegin@yegin.org>, 16ng@ietf.org
Subject: Re: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jun 2009 10:50:34 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--1589707168-1910595125-1244630933=:19541
Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8BIT
Content-ID: <alpine.LRH.2.00.0906101349011.19541@netcore.fi>

On Tue, 9 Jun 2009, gabriel montenegro wrote:
> For example, one could think of referring interested readers to:
>  
> MTU and Fragmentation Issues with In-the-Network Tunneling
> http://tools.ietf.org/html/rfc4459 
> But I don't even know if that is the more appropriate text one would want to point at.
> I'm cc-ing the author, Pekka Savola, as he may have some more current info for us.

In developing a protocol, I personally think the protocol 
specification should decide a model to be adopted either in the 
protocol or in operating the protocol, or just explicitly leave the 
issue open. RFC4459 just lists some alternatives and their tradeoffs.

Apart from that there isn't much to add.  There's a bit more recent 00 
draft that also discusses tunnels from an architectural and less 
practical perspective, but I'm not sure if it provides any more 
information than the RFC above: draft-touch-intarea-tunnels-00.


-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
--1589707168-1910595125-1244630933=:19541--

From wgeorge@sprint.net  Wed Jun 10 09:57:45 2009
Return-Path: <wgeorge@sprint.net>
X-Original-To: 16ng@core3.amsl.com
Delivered-To: 16ng@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9AB063A6E88 for <16ng@core3.amsl.com>; Wed, 10 Jun 2009 09:57:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0M1VnD4ZaADr for <16ng@core3.amsl.com>; Wed, 10 Jun 2009 09:57:44 -0700 (PDT)
Received: from jay.sprintlink.net (jay.sprintlink.net [199.0.233.7]) by core3.amsl.com (Postfix) with ESMTP id B6E9228C22A for <16ng@ietf.org>; Wed, 10 Jun 2009 09:57:44 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAAqDL0rHAO3C/2dsb2JhbADRGIQNBQ
X-IronPort-AV: E=Sophos;i="4.41,342,1241409600"; d="scan'208";a="25687028"
Received: from iscone.res.sprintlink.net (HELO tin.res.sprintlink.net) ([199.0.237.194]) by jay.sprintlink.net with ESMTP; 10 Jun 2009 12:50:55 -0400
Received: from tin.res.sprintlink.net (localhost [127.0.0.1]) by tin.res.sprintlink.net (8.13.7+Sun/8.13.7) with ESMTP id n5AGvpjT024427; Wed, 10 Jun 2009 12:57:51 -0400 (EDT)
Received: from localhost (wgeorge@localhost) by tin.res.sprintlink.net (8.13.7+Sun/8.13.7/Submit) with ESMTP id n5AGvopx024423; Wed, 10 Jun 2009 12:57:50 -0400 (EDT)
X-Authentication-Warning: tin.res.sprintlink.net: wgeorge owned process doing -bs
Date: Wed, 10 Jun 2009 12:57:50 -0400 (EDT)
From: Wesley George <wgeorge@sprint.net>
X-X-Sender: wgeorge@tin
To: Pekka Savola <pekkas@netcore.fi>
In-Reply-To: <alpine.LRH.2.00.0906101344500.19541@netcore.fi>
Message-ID: <Pine.GSO.4.64.0906101255320.9230@tin>
References: <2828BDE8DC61004E8104C78E82A0B39710B25385F2@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com><BC27158B99D3064A955ADE084783900C01B5CBC8@DEMUEXC014.nsn-intra.net> <Pine.GSO.4.64.0905151247200.12703@tin>, <046201c9d589$267cf8d0$7376ea70$@com> <BAA9BC6C-6B59-4BA6-B63D-E09C26E0194B@mimectl> <BC27158B99D3064A955ADE084783900C020F18E5@DEMUEXC014.nsn-intra.net> <056601c9d7e8$b8be17e0$2a3a47a0$@com> <556994.50253.qm@web82604.mail.mud.yahoo.com> <06ab01c9d8cd$079cc660$16d65320$@com> <BC27158B99D3064A955ADE084783900C020F26B5@DEMUEXC014.nsn-intra.net> <916575.77425.qm@web82607.mail.mud.yahoo.com> <570230.22436.qm@web82606.mail.mud.yahoo.com> <Pine.GSO.4.64.0906040915000.16060@tin> <553392.88380.qm@web82604.mail.mud.yahoo.com> <alpine.LRH.2.00.0906101344500.19541@netcore.fi>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-851401618-1244653070=:9230"
Cc: ext Alper Yegin <alper.yegin@yegin.org>, gabriel montenegro <g_e_montenegro@yahoo.com>, 16ng@ietf.org
Subject: Re: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jun 2009 16:57:45 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---559023410-851401618-1244653070=:9230
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE

I can appreciate that approach. I didn't really consider that we might be=
=20
reinventing the wheel. *blush*
I think a reference to some issues that the implementor should be aware=20
of is better than no mention of them so probably since the below is still=
=20
in draft, the RFC is better than nothing.

Thanks,
Wes

On Wed, 10 Jun 2009, Pekka Savola wrote:

> On Tue, 9 Jun 2009, gabriel montenegro wrote:
>> For example, one could think of referring interested readers to:
>> =A0
>> MTU and Fragmentation Issues with In-the-Network Tunneling
>> http://tools.ietf.org/html/rfc4459=A0
>> But I don't even know if that is the more appropriate text one would wan=
t=20
>> to point at.
>> I'm cc-ing the author, Pekka Savola, as he may have some more current in=
fo=20
>> for us.
>
> In developing a protocol, I personally think the protocol specification=
=20
> should decide a model to be adopted either in the protocol or in operatin=
g=20
> the protocol, or just explicitly leave the issue open. RFC4459 just lists=
=20
> some alternatives and their tradeoffs.
>
> Apart from that there isn't much to add.  There's a bit more recent 00 dr=
aft=20
> that also discusses tunnels from an architectural and less practical=20
> perspective, but I'm not sure if it provides any more information than th=
e=20
> RFC above: draft-touch-intarea-tunnels-00.
>
>
> --=20
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
---559023410-851401618-1244653070=:9230--

From g_e_montenegro@yahoo.com  Wed Jun 10 10:31:56 2009
Return-Path: <g_e_montenegro@yahoo.com>
X-Original-To: 16ng@core3.amsl.com
Delivered-To: 16ng@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF6BB3A6B61 for <16ng@core3.amsl.com>; Wed, 10 Jun 2009 10:31:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.374
X-Spam-Level: 
X-Spam-Status: No, score=-2.374 tagged_above=-999 required=5 tests=[AWL=0.225,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VjKtCNHsSVVS for <16ng@core3.amsl.com>; Wed, 10 Jun 2009 10:31:51 -0700 (PDT)
Received: from web82603.mail.mud.yahoo.com (web82603.mail.mud.yahoo.com [68.142.201.120]) by core3.amsl.com (Postfix) with SMTP id 38D473A6A24 for <16ng@ietf.org>; Wed, 10 Jun 2009 10:31:51 -0700 (PDT)
Received: (qmail 94461 invoked by uid 60001); 10 Jun 2009 17:31:56 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1244655116; bh=Syj2MQ+Htmfw2azzzeMvco84Kzsx5znp+e/ShiAS+K8=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=xv8Y6FabMOamOeWYUlYMket1AoY0FSgAax8bEjS93ZOmtqjyL49f2Wa66neZFbOz80YLHdZAAC8Q8YZgaYROpFaXSYpRk/GjTKhOfwW1xQyqCDfYjG2VVhzuCCcp8p4Hd+usswDbQ+iuVJAAPWWIJ2F2+DBPDK1oWPv6Ba5F+GE=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=eMqNAX26cL8+mYwIzk65tRFzE8Mb8fh0tiz7hVlSICq41EHxG68Jfthm0vdpZs1nsRMoTYkZjGbySXWkvjD6HR2rTr+femuKR7Xuu2HjBK0BcI312Fq/mm8Wm/yIY3O7W/g8HapCy57MBTB0F9NIiDskmzNqge8A+yJTjFj4bBk=;
Message-ID: <284280.89779.qm@web82603.mail.mud.yahoo.com>
X-YMail-OSG: mQoj.E0VM1nXZksIwzKZT.JmuP3uGd_D.zewwnKAAyzDQmIRmsd_HAq60hBCHU_0L3hFYPrag6DW4UFUI9C8s1rcmJDFclR8kkj1kl94esnFuTakJUAZ2KDdSApP9ggfQ.g9axrAYaCLOv9vDfEtAr2CfmuaK0qeAx5ArMDoAmZdwxsLo8DCtF.EzILkaWGKsuRpsu9yAXOYeU.ZTYCXU5C2lGhFFmf7F3DrUA7LBJyOVTNj8jALrYOM25rtqZ4FGE.Ghm6dD_hGQYLjcCMUDDITeRrPGI8iRIVLxJOjFTs0l_MBShVxwxcxkGtJN5BI4hfnp1c_tIuEzOmPyKI-
Received: from [24.16.92.42] by web82603.mail.mud.yahoo.com via HTTP; Wed, 10 Jun 2009 10:31:56 PDT
X-Mailer: YahooMailRC/1277.43 YahooMailWebService/0.7.289.10
References: <2828BDE8DC61004E8104C78E82A0B39710B25385F2@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com><BC27158B99D3064A955ADE084783900C01B5CBC8@DEMUEXC014.nsn-intra.net> <Pine.GSO.4.64.0905151247200.12703@tin>, <046201c9d589$267cf8d0$7376ea70$@com> <BAA9BC6C-6B59-4BA6-B63D-E09C26E0194B@mimectl> <BC27158B99D3064A955ADE084783900C020F18E5@DEMUEXC014.nsn-intra.net> <056601c9d7e8$b8be17e0$2a3a47a0$@com> <556994.50253.qm@web82604.mail.mud.yahoo.com> <06ab01c9d8cd$079cc660$16d65320$@com> <BC27158B99D3064A955ADE084783900C020F26B5@DEMUEXC014.nsn-intra.net> <916575.77425.qm@web82607.mail.mud.yahoo.com> <570230.22436.qm@web82606.mail.mud.yahoo.com> <Pine.GSO.4.64.0906040915000.16060@tin> <553392.88380.qm@web82604.mail.mud.yahoo.com> <alpine.LRH.2.00.0906101344500.19541@netcore.fi> <Pine.GSO.4.64.0906101255320.9230@tin>
Date: Wed, 10 Jun 2009 10:31:56 -0700 (PDT)
From: gabriel montenegro <g_e_montenegro@yahoo.com>
To: Wesley George <wgeorge@sprint.net>, Pekka Savola <pekkas@netcore.fi>
In-Reply-To: <Pine.GSO.4.64.0906101255320.9230@tin>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ext Alper Yegin <alper.yegin@yegin.org>, 16ng@ietf.org
Subject: Re: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jun 2009 17:31:56 -0000

I'll add a reference to the RFC with language to the effect that it is just=
 one possible source of information.=0A=0A=0A=0A----- Original Message ----=
=0A> From: Wesley George <wgeorge@sprint.net>=0A> To: Pekka Savola <pekkas@=
netcore.fi>=0A> Cc: gabriel montenegro <g_e_montenegro@yahoo.com>; "Riegel,=
 Maximilian (NSN - DE/Munich)" <maximilian.riegel@nsn.com>; ext Samita Chak=
rabarti <samitac@ipinfusion.com>; ext Alper Yegin <alper.yegin@yegin.org>; =
16ng@ietf.org=0A> Sent: Wednesday, June 10, 2009 9:57:50 AM=0A> Subject: Re=
: [16NG] [nwg-chair] NWG feedback on 16ng's IPv4 CS draft=0A> =0A> I can ap=
preciate that approach. I didn't really consider that we might be =0A> rein=
venting the wheel. *blush*=0A> I think a reference to some issues that the =
implementor should be aware of is =0A> better than no mention of them so pr=
obably since the below is still in draft, =0A> the RFC is better than nothi=
ng.=0A> =0A> Thanks,=0A> Wes=0A> =0A> On Wed, 10 Jun 2009, Pekka Savola wro=
te:=0A> =0A> > On Tue, 9 Jun 2009, gabriel montenegro wrote:=0A> >> For exa=
mple, one could think of referring interested readers to:=0A> >> =A0=0A> >>=
 MTU and Fragmentation Issues with In-the-Network Tunneling=0A> >> http://t=
ools.ietf.org/html/rfc4459=A0=0A> >> But I don't even know if that is the m=
ore appropriate text one would want to =0A> point at.=0A> >> I'm cc-ing the=
 author, Pekka Savola, as he may have some more current info =0A> for us.=
=0A> > =0A> > In developing a protocol, I personally think the protocol spe=
cification should =0A> decide a model to be adopted either in the protocol =
or in operating the =0A> protocol, or just explicitly leave the issue open.=
 RFC4459 just lists some =0A> alternatives and their tradeoffs.=0A> > =0A> =
> Apart from that there isn't much to add.=A0 There's a bit more recent 00 =
draft =0A> that also discusses tunnels from an architectural and less pract=
ical =0A> perspective, but I'm not sure if it provides any more information=
 than the RFC =0A> above: draft-touch-intarea-tunnels-00.=0A> > =0A> > =0A>=
 > -- Pekka Savola=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 "You each name yourselves=
 king, yet the=0A> > Netcore Oy=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 king=
dom bleeds."=0A> > Systems. Networks. Security. -- George R.R. Martin: A Cl=
ash of Kings=0A

From hongseok.jeon@gmail.com  Thu Jun 11 23:00:13 2009
Return-Path: <hongseok.jeon@gmail.com>
X-Original-To: 16ng@core3.amsl.com
Delivered-To: 16ng@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2A7E33A688F for <16ng@core3.amsl.com>; Thu, 11 Jun 2009 23:00:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gs-paOey4dZA for <16ng@core3.amsl.com>; Thu, 11 Jun 2009 23:00:12 -0700 (PDT)
Received: from mail-ew0-f210.google.com (mail-ew0-f210.google.com [209.85.219.210]) by core3.amsl.com (Postfix) with ESMTP id 679863A63CB for <16ng@ietf.org>; Thu, 11 Jun 2009 23:00:11 -0700 (PDT)
Received: by ewy6 with SMTP id 6so2678917ewy.37 for <16ng@ietf.org>; Thu, 11 Jun 2009 23:00:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=9Gye7fvGsjZ/gXZvwoXrN/BvwAL6c77yJhHeBaJlJhc=; b=ZIAOfhybZjxAzVpj81moHTdHnfUzFxnYh5X8IUMWONuDe1PzVk+KRFsQKHaFy3m02V bl5g1teKfC0AnYGmL/+/LWtyx8BMUtHNPd7Md6Gru5ZEYHGIHr7D+WTMeUE3KzaHuvAi vAZWri9F2OET0mGnGz9c+Iy6DywbQ3/ZbzwTk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=OiocWH1dEIh6OpSdqiZuhbX3X2BvOGrHTTlNv2Uuilu9L5tEnVfE5b4vML6o88vkML ormvpywr9qfoRXUBYrObFigijFMxGN07FBz+wC1smR/Gzz9fAVK9TunXz2ZEr7HjkUYB 8klTd3pR7f9s4JYFoWSwxa4aS2lUORe4Zom8U=
MIME-Version: 1.0
Received: by 10.216.0.84 with SMTP id 62mr1175267wea.185.1244786416787; Thu,  11 Jun 2009 23:00:16 -0700 (PDT)
In-Reply-To: <396856.9733.qm@web82605.mail.mud.yahoo.com>
References: <20090130191502.0168F28C19D@core3.amsl.com> <15265f0b0905140011h4f64e82bna28efea61205656c@mail.gmail.com> <396856.9733.qm@web82605.mail.mud.yahoo.com>
Date: Fri, 12 Jun 2009 15:00:16 +0900
Message-ID: <15265f0b0906112300h6431a69cu8cc454c1e2df71f@mail.gmail.com>
From: Hongseok Jeon <hongseok.jeon@gmail.com>
To: gabriel montenegro <g_e_montenegro@yahoo.com>
Content-Type: multipart/alternative; boundary=001485f626b031a047046c206c7c
Cc: 16ng@ietf.org
Subject: Re: [16NG] Fwd: I-D ACTION:draft-ietf-16ng-ip-over-ethernet-over-802-dot-16-08.txt
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jun 2009 06:00:13 -0000

--001485f626b031a047046c206c7c
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi Gabriel,

Thank you for your reply. I look forward to advancing this document.

Best Regards,
Hongseok Jeon

On Wed, Jun 10, 2009 at 1:32 AM, gabriel montenegro <
g_e_montenegro@yahoo.com> wrote:

> Sorry for the delay on this. We had a recent teleconf discussion with the
> ADs on 16ng status.
> I've told them that I believe this document has addressed the AD comments
> (Jari) as well as
> the request for feedback from DSL perpsective.
>
> The plan is that I will advance this to IESG (again) soon (will need a few
> more days to
> do the proto write-up).
> Gabriel
>
>  ------------------------------
> *From:* Hongseok Jeon <hongseok.jeon@gmail.com>
> *To:* Daniel Park <soohongp@gmail.com>; g_e_montenegro@yahoo.com
> *Cc:* 16ng@ietf.org; "Riegel, Maximilian" <maximilian.riegel@nsn.com>;
> Sangjin Jeong <sjjeong@gmail.com>
> *Sent:* Thursday, May 14, 2009 12:11:43 AM
> *Subject:* Fwd: [16NG] I-D
> ACTION:draft-ietf-16ng-ip-over-ethernet-over-802-dot-16-08.txt
>
> Dear chairs,
>
> I am Hongseok Jeon, one of authors of IPoEth CS document.
> We have submitted the IPoEth CS document in January as below email
> but no response was found until now.
>
> Of course, I don't think no response means that the document is ready to
> move on.
> But, I want to clarify what we are waiting for to move this document
> forward.
>
> Please clarify remaining steps.
>
> Thank you in advance.
>
> Best Regards,
> Hongseok Jeon
>
> ---------- Forwarded message ----------
> From: <Internet-Drafts@ietf.org>
> Date: 2009/1/31
> Subject: [16NG] I-D
> ACTION:draft-ietf-16ng-ip-over-ethernet-over-802-dot-16-08.txt
> To: i-d-announce@ietf.org
> Cc: 16ng@ietf.org
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the IP over IEEE 802.16 Networks Working Group
> of the IETF.
>
>        Title           : Transmission of IP over Ethernet over IEEE 802.16
> Networks
>        Author(s)       : M. Riegel, S. Jeong, H. Jeon
>        Filename        :
> draft-ietf-16ng-ip-over-ethernet-over-802-dot-16-08.txt
>        Pages           : 19
>        Date            : 2009-1-30
>
> This document describes the transmission of IPv4 over Ethernet as
>   well as IPv6 over Ethernet in an access network deploying the IEEE
>   802.16 cellular radio transmission technology.  The Ethernet on top
>   of IEEE 802.16 is realized by bridging connections which the IEEE
>   802.16 provides between a base station and its associated subscriber
>   stations.  Due to the resource constraints of radio transmission
>   systems and the limitations of the IEEE 802.16 MAC functionality for
>   the realization of an Ethernet, the transmission of IP over Ethernet
>   over IEEE 802.16 may considerably benefit by adding IP specific
>   support functions in the Ethernet over IEEE 802.16 while maintaining
>   full compatibility with standard IP over Ethernet behavior.
>
> A URL for this Internet-Draft is:
>
> http://www.ietf.org/internet-drafts/draft-ietf-16ng-ip-over-ethernet-over-802-dot-16-08.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
>
> _______________________________________________
> 16NG mailing list
> 16NG@ietf.org
> https://www.ietf.org/mailman/listinfo/16ng
>
>
>

--001485f626b031a047046c206c7c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hi Gabriel,</div><div><br></div>Thank you for your reply.=A0<div>I loo=
k forward to advancing this document.=A0</div><div><br></div><div>Best Rega=
rds,</div><div>Hongseok Jeon<br><br><div class=3D"gmail_quote">On Wed, Jun =
10, 2009 at 1:32 AM, gabriel montenegro <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:g_e_montenegro@yahoo.com">g_e_montenegro@yahoo.com</a>&gt;</span> wrot=
e:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><div><div style=3D"font-family:Courier New,=
 courier, monaco, monospace, sans-serif;font-size:10pt"><div>Sorry for the =
delay on this. We had a recent teleconf discussion with the ADs on 16ng sta=
tus.</div>

<div>I&#39;ve told them that I believe this document has addressed the AD c=
omments (Jari) as well as</div>
<div>the request for feedback from DSL perpsective. </div>
<div>=A0</div>
<div>The plan is that I will advance this to IESG (again) soon (will need a=
 few more days to</div>
<div>do the proto write-up).<br></div><font color=3D"#888888">
<div>Gabriel</div>
</font><div style=3D"font-family:Courier New, courier, monaco, monospace, s=
ans-serif;font-size:10pt"><br><div class=3D"hm">
</div><div style=3D"font-family:times new roman, new york, times, serif;fon=
t-size:12pt"><div class=3D"hm"><font size=3D"2" face=3D"Tahoma">
<hr size=3D"1">
<b><span style=3D"font-weight:bold">From:</span></b> Hongseok Jeon &lt;<a h=
ref=3D"mailto:hongseok.jeon@gmail.com" target=3D"_blank">hongseok.jeon@gmai=
l.com</a>&gt;<br><b><span style=3D"font-weight:bold">To:</span></b> Daniel =
Park &lt;<a href=3D"mailto:soohongp@gmail.com" target=3D"_blank">soohongp@g=
mail.com</a>&gt;; <a href=3D"mailto:g_e_montenegro@yahoo.com" target=3D"_bl=
ank">g_e_montenegro@yahoo.com</a><br>
<b><span style=3D"font-weight:bold">Cc:</span></b> <a href=3D"mailto:16ng@i=
etf.org" target=3D"_blank">16ng@ietf.org</a>; &quot;Riegel, Maximilian&quot=
; &lt;<a href=3D"mailto:maximilian.riegel@nsn.com" target=3D"_blank">maximi=
lian.riegel@nsn.com</a>&gt;; Sangjin Jeong &lt;<a href=3D"mailto:sjjeong@gm=
ail.com" target=3D"_blank">sjjeong@gmail.com</a>&gt;<br>
<b><span style=3D"font-weight:bold">Sent:</span></b> Thursday, May 14, 2009=
 12:11:43 AM<br><b><span style=3D"font-weight:bold">Subject:</span></b> Fwd=
: [16NG] I-D ACTION:draft-ietf-16ng-ip-over-ethernet-over-802-dot-16-08.txt=
<br>
</font></div><div><div></div><div class=3D"h5"><br>
<div>Dear chairs,=A0</div>
<div><br></div>
<div>I am Hongseok Jeon, one of authors of IPoEth CS document.=A0</div>
<div>We have submitted the IPoEth CS document in January as below email=A0<=
/div>
<div>but no response was found=A0until now.=A0</div>
<div><br></div>
<div>Of course, I don&#39;t think no response means that the document is re=
ady to move on.=A0</div>
<div>But, I want to clarify what we are waiting for to move this document f=
orward.=A0</div>
<div><br></div>
<div>Please clarify remaining steps.</div>
<div><br></div>
<div>Thank you in advance.</div>
<div><br></div>
<div>Best Regards,</div>
<div>Hongseok Jeon</div><br>
<div class=3D"gmail_quote">---------- Forwarded message ----------<br>From:=
 <b class=3D"gmail_sendername"></b><span dir=3D"ltr">&lt;<a href=3D"mailto:=
Internet-Drafts@ietf.org" rel=3D"nofollow" target=3D"_blank">Internet-Draft=
s@ietf.org</a>&gt;</span><br>
Date: 2009/1/31<br>Subject: [16NG] I-D ACTION:draft-ietf-16ng-ip-over-ether=
net-over-802-dot-16-08.txt<br>To: <a href=3D"mailto:i-d-announce@ietf.org" =
rel=3D"nofollow" target=3D"_blank">i-d-announce@ietf.org</a><br>Cc: <a href=
=3D"mailto:16ng@ietf.org" rel=3D"nofollow" target=3D"_blank">16ng@ietf.org<=
/a><br>
<br><br>A New Internet-Draft is available from the on-line Internet-Drafts<=
br>directories.<br>This draft is a work item of the IP over IEEE 802.16 Net=
works Working Group of the IETF.<br><br>=A0 =A0 =A0 =A0Title =A0 =A0 =A0 =
=A0 =A0 : Transmission of IP over Ethernet over IEEE 802.16 Networks<br>
=A0 =A0
 =A0 =A0Author(s) =A0 =A0 =A0 : M. Riegel, S. Jeong, H. Jeon<br>=A0 =A0 =A0=
 =A0Filename =A0 =A0 =A0 =A0: draft-ietf-16ng-ip-over-ethernet-over-802-dot=
-16-08.txt<br>=A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 19<br>=A0 =A0 =A0 =
=A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2009-1-30<br><br>This document describes t=
he transmission of IPv4 over Ethernet as<br>
=A0 well as IPv6 over Ethernet in an access network deploying the IEEE<br>=
=A0 802.16 cellular radio transmission technology. =A0The Ethernet on top<b=
r>=A0 of IEEE 802.16 is realized by bridging connections which the IEEE<br>=
=A0 802.16 provides between a base station and its associated subscriber<br=
>
=A0 stations. =A0Due to the resource constraints of radio transmission<br>=
=A0 systems and the limitations of the IEEE 802.16 MAC functionality for<br=
>=A0 the realization of an Ethernet, the
 transmission of IP over Ethernet<br>=A0 over IEEE 802.16 may considerably =
benefit by adding IP specific<br>=A0 support functions in the Ethernet over=
 IEEE 802.16 while maintaining<br>=A0 full compatibility with standard IP o=
ver Ethernet behavior.<br>
<br>A URL for this Internet-Draft is:<br><a href=3D"http://www.ietf.org/int=
ernet-drafts/draft-ietf-16ng-ip-over-ethernet-over-802-dot-16-08.txt" targe=
t=3D"_blank">http://www.ietf.org/internet-drafts/draft-ietf-16ng-ip-over-et=
hernet-over-802-dot-16-08.txt</a><br>
<br>Internet-Drafts are also available by anonymous FTP at:<br><a href=3D"f=
tp://ftp.ietf.org/internet-drafts/" rel=3D"nofollow" target=3D"_blank">ftp:=
//ftp.ietf.org/internet-drafts/</a><br><br>Below is the data which will ena=
ble a MIME compliant mail reader<br>
implementation to automatically retrieve the ASCII version of the<br>Intern=
et-Draft.<br><br><br>_______________________________________________<br>16N=
G mailing list<br><a href=3D"mailto:16NG@ietf.org" rel=3D"nofollow" target=
=3D"_blank">16NG@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/16ng" rel=3D"nofollow" tar=
get=3D"_blank">https://www.ietf.org/mailman/listinfo/16ng</a><br><br></div>=
<br></div></div></div></div></div></div></blockquote></div><br></div>

--001485f626b031a047046c206c7c--

From g_e_montenegro@yahoo.com  Sun Jun 14 23:28:22 2009
Return-Path: <g_e_montenegro@yahoo.com>
X-Original-To: 16ng@core3.amsl.com
Delivered-To: 16ng@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3200928C0CF for <16ng@core3.amsl.com>; Sun, 14 Jun 2009 23:28:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.519
X-Spam-Level: 
X-Spam-Status: No, score=-1.519 tagged_above=-999 required=5 tests=[AWL=-0.720, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, J_CHICKENPOX_45=0.6, J_CHICKENPOX_63=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UcTk6cGfikE2 for <16ng@core3.amsl.com>; Sun, 14 Jun 2009 23:28:18 -0700 (PDT)
Received: from web82607.mail.mud.yahoo.com (web82607.mail.mud.yahoo.com [68.142.201.124]) by core3.amsl.com (Postfix) with SMTP id BABB03A69CB for <16ng@ietf.org>; Sun, 14 Jun 2009 23:28:17 -0700 (PDT)
Received: (qmail 77393 invoked by uid 60001); 15 Jun 2009 06:28:26 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1245047306; bh=t/YqKxlFHZlhdc6KLDlbVPolD0XDjS23qsLVTvkMzKE=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=s+imwGoNSYBpSIqvN4Bx/OzYna0vwZBxG7jjJYCF0WhVlhJ1hxz/ZmA/aeNwr7KUH6ZmSJRUOP4FkuUcJGUETFe3pXFJsljORQRPu3j5pgOPSJ8pewtjjQYFSlU9tTTV8dOFd/EwphvF3/u11Vr26pD6hQnmBrXdEeCp5kbUqng=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=LCLu4E/mOCNo1PmALNCNBJVu4YNF5XcpEHZh1MrtdaVHrivekFsazkiWYD3yScBgv+SXeX7hldYMQK2DG0Q/E3TUToiiAzCq9BDoeYZwEdtz/l6CSrc1+za4X5VDPxpxyi9bPp8qdRCX9vATO5i+T8xj+4owq9D2caz5XavC8/k=;
Message-ID: <54426.75175.qm@web82607.mail.mud.yahoo.com>
X-YMail-OSG: udsCWjsVM1lzSqCjCnzQ3PgjD5du3it7d1Uje4H82ZkbUGXjB6zuM3rLerAKhJJkd9.jzbI91JLLnBJExxeq9pxHdMa8IiIqYzO9tKeQ3qtEEhVmFQ1nkl3nKw86iO1T3AQjcAg2ztf6zc2ZpLD45i0vzf1TY8iG8RDIidfJEE_phO6yz3eR5Nqbsz5ljPusf6UusqFF6KSQNoLb1iBaiC4oT8dG6Pf_ZhDVehmR9wAH.nN6fyM9qUi50FY1scREdJt5FzcunHXaLkKNqGArtTL7zor7Wj.i7EL_vKB0U5sE3p4tBkGBJwlYdDoZnqqAj9wOa_xvmzOVftKroA8-
Received: from [24.16.92.42] by web82607.mail.mud.yahoo.com via HTTP; Sun, 14 Jun 2009 23:28:25 PDT
X-Mailer: YahooMailRC/1277.43 YahooMailWebService/0.7.289.10
References: <20090603154501.B0C963A6CBB@core3.amsl.com> <BC27158B99D3064A955ADE084783900C021E70E1@DEMUEXC014.nsn-intra.net> <BC27158B99D3064A955ADE084783900C021E70E2@DEMUEXC014.nsn-intra.net> <279552.13378.qm@web82601.mail.mud.yahoo.com>
Date: Sun, 14 Jun 2009 23:28:25 -0700 (PDT)
From: gabriel montenegro <g_e_montenegro@yahoo.com>
To: gabriel montenegro <g_e_montenegro@yahoo.com>, "Riegel, Maximilian \(NSN - DE/Munich\)" <maximilian.riegel@nsn.com>, 16ng@ietf.org
In-Reply-To: <279552.13378.qm@web82601.mail.mud.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ext Alper Yegin <alper.yegin@yegin.org>
Subject: Re: [16NG] I-DAction:draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05.txt
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jun 2009 06:28:22 -0000

Thanks Max for your comments. Below please find our response. I've submitte=
d a new draft 06 =0Amodified per comments received from both Max and Wesley=
.=0A=0AThanks Max, my responses below marked with "gab>".=0AI've elided tex=
t on which there is no comment.=0A> Abstract=0A> =0A>=A0=A0=A0 IEEE 802.16 =
is an air interface specification for wireless broadband=0A>=A0=A0=A0 acces=
s.=A0 IEEE 802.16 has specified multiple service specific=0A>=A0=A0=A0 conv=
ergence sublayers for transmitting upper layer protocols.=A0 The=0A>=A0=A0=
=A0 packet CS (Packet Convergence Sublayer) is used for the transport of=0A=
>=A0=A0=A0 all packet-based protocols such as Internet Protocol (IP), IEEE =
802.3=0A>=A0=A0=A0 (Ethernet) and IEEE 802.1Q (VLAN).=A0 The IP-specific pa=
rt of the=0AMeanwhile the IEEE802.16-2009 (was REV2) specification has been=
 released.=0AIEEE802.16-2009 does not know anymore about the IEEE 802.1Q (V=
LAN) CS.=0Agab> Thanks, will drop mention of it, and update the references =
to the new=0Aversion of .16. and drop 802.1Q CS (one more example of why sa=
ying too much=0Ais worse than saying what is necessary).=0A...=0A=0A> 1.=A0=
 Introduction=0A> =0A>=A0=A0=A0 IEEE 802.16 [IEEE802_16] is a connection or=
iented access technology=0A>=A0=A0=A0 for the last mile.=A0 The IEEE 802.16=
 specification includes the PHY=0A>=A0=A0=A0 and MAC layers.=A0 The MAC inc=
ludes various convergence sublayers (CS)=0A>=A0=A0=A0 for transmitting high=
er layer packets including IPv4 packets=0A>=A0=A0=A0 [RFC5154].=0A> =0A>=A0=
=A0=A0 The scope of this specification is limited to the operation of IPv4=
=0A>=A0=A0=A0 over the IP-specific part of the packet CS (referred to as "I=
Pv4 CS"=0A>=A0=A0=A0 or simply "IP CS" in this document).=0AIPv4 CS should =
be used throughout the document to prevent mixing it up with the IPv6 CS sp=
ecification. There is nothing like IP CS in the IEEE802.16 specification, t=
here is only IPv4 CS and IPv6 CS.=0ABTW: there is now a single ETH CS carry=
ing IPv4 as well as IPv6 payload.=0Agab> IP CS is a term defined in RFC5154=
 so we *could* use it, but I agree that it is better to =0Abe explicit.=0AH=
ave changed to IPv4 CS throughout.=0A>=A0=A0=A0 This document specifies a m=
ethod for encapsulating and transmitting=0A>=A0=A0=A0 IPv4 [RFC0791] packet=
s over the IP CS of IEEE 802.16.=A0 This document=0A=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0 ^IPv4 CS=0A>=A0=A0=A0 also specifies the MTU and address assig=
nment method for the IEEE=0AWhich MTU, which address assignment? More conci=
se wording would help.=0Agab> Changed it to: "...method for hosts using IPv=
4 CS."=0AAnd in the above paragraph on "scope of this specification" added =
this text=0Aextracted from RFC5121 to the end of that sentence: "for hosts =
served by a =0Anetwork that utilizes the IEEE Std 802.16 air interface"=0A>=
=A0=A0=A0 802.16 based networks using IP CS.=0A=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 ^IPv4=
 CS=0A> =0A>=A0=A0=A0 This document also discusses ARP (Address Resolution =
Protocol) and=0A>=A0=A0=A0 Multicast Address Mapping whose operation is sim=
ilar to any other=0A>=A0=A0=A0 point-to-point link model.=0AWhat do you mea=
n with this sentence?=0Agab> Not needed as there are details later on anywa=
y. =0ADeleted the last part starting with "whose operation...".=0A>=A0=A0=
=A0 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",=0A>=
=A0=A0=A0 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in t=
his=0A>=A0=A0=A0 document are to be interpreted as described in [RFC2119].=
=0A> =0A> =0A> 2.=A0 Terminology=0A> =0A>=A0=A0=A0 The terminology in this =
document is based on the definitions in=0A>=A0=A0=A0 [RFC5154].=0A> =0A> =
=0A> 3.=A0 Typical Network Architecture for IPv4 over IEEE 802.16=0A> =0A>=
=A0=A0=A0 The network architecture follows what is described in [RFC5154] a=
nd=0A>=A0=A0=A0 [RFC5121].=A0 In a nutshell, each MS is attached to an Acce=
ss Router=0APlease clarify 'MS'; according to IEEE802.16 it only covers PHY=
 and MAC.=0AAccording to IEEE802.16 the MS is not a 'host'.=0Agab> Terminol=
ogy here (as specified above) is as defined in 5154, which is more=0Ainform=
al. Added this text taken from RFC5121 (except for the last sentence, which=
=0AI added to hopefully address your concern.=0A>=A0=A0=A0 (AR) through a B=
ase Station (BS), a layer 2 entity (from the=0A>=A0=A0=A0 perspective of th=
e IPv6 link between the MS and access router (AR)).=0A=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 ^IPv4??? Copy&Paste mistak=
e?=0A> =0Agab> fixed.=0A>=A0=A0=A0 For further information on the typical n=
etwork architecture, see=0A>=A0=A0=A0 [RFC5121] section 5.=0A> =0A> 3.1.=A0=
 IEEE 802.16 IPv4 Convergence sub-layer support=0A> =0A>=A0=A0=A0 As descri=
bed in [RFC5154] section 3.3., an IP specific subpart=0A>=A0=A0=A0 classifi=
er carries either IPv4 or IPv6 payloads.=A0 In this document,=0A>=A0=A0=A0 =
we are focusing on the IPv4 over IP Convergence Sublayer.=0ASection 3.3 of =
[RFC5154] is outdated! IEEE802.16-2009 introduced a refined CS structure. I=
MHO, we shouldn't make references to outdated specifications, but base the =
work on the most recent IEEE802.16 specification.=0Agab> You were looking a=
t a preliminary version, I guess, as the draft already refers to =0A802.16 =
(which we'll update to say "802.16-2009"). =0A...=0A> =0A>=A0=A0=A0 For fur=
ther information on the IEEE 802.16 Convergence Sublayer and=0A>=A0=A0=A0 e=
ncapsulation of IP packets, see [RFC5121] section 4 and [RFC5154]=0A>=A0=A0=
=A0 section 3.3.=0AAs [RFC5154] is outdated, I would propose to provide an =
updated section 3.3. as part of the IPv4 CS document.=0Agab> I=A0 just drop=
ping 5154 and replaced it by a reference to 802.16-2009. =0AWe will not fix=
 5154 as that is merely informational and was a statement valid at a given=
=0Apoint in time. More concerning might be if RFC5121 (a standards-track do=
cument) were=0Asuddenly wrong. Is this the case? =0A> 4.=A0 IPv4 CS link in=
 802.16 Networks=0A> =0A>=A0=A0=A0 This document defines the IPv4 CS link a=
s a point-to-point link=0A>=A0=A0=A0 between the MS and the AR using a set =
of service flows consisting of=0AMS is not the host. What is a link between=
 a L2 device (MS) and a L3 device (AR)?=0Agab> "MS" here, in 5121 as well a=
s in draft-ietf-16ng-ip-over-ethernet-over-802-dot-16-08 =0A(where there's =
mention of SS's sending ARP requests, tying to bridges, etc)=0Ais a host, b=
ut I changed s/MS/host/=0A>=A0=A0=A0 MAC transport connections between a MS=
 and BS, and L2 tunnel(s)=0A>=A0=A0=A0 between between a BS and AR.=A0 It i=
s recommended that a tunnel be=0A=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0 ^is=0Agab> I believe "be" is correct.=0A>=A0=A0=A0 established betwe=
en the AR and a BS based on 'per MS' or 'per service=0A>=A0=A0=A0 flow' (An=
 MS can have multiple service flows each of which are=0AWhat is a tunnel be=
tween BS and AR based on 'per MS'? It seems, some GRE functionality is assu=
med here without spelling it out.=0Agab> As in RFC5121, nothing in this res=
pect is spelled out as it is not germane to the=0Aissue of IP-over-foo from=
 the host. We should not assume GRE, one could use a suite of other =0Atech=
nologies, so mentioning GRE is not always correct nor necessary.=0A>=A0=A0=
=A0 identified by a unique service flow ID).=A0 Then the tunnel(s) for an=
=0A>=A0=A0=A0 MS, in combination with the MS's MAC transport connections, f=
orms a=0A>=A0=A0=A0 single point-to-point link.=A0 Each MS belongs to a dif=
ferent link and=0AHow does this work - multiple tunnels between two endpoin=
ts forming a single link? I would assume, that there must be some classific=
ation in place, which is part of the BS according to IEEE802.16, not part o=
f the AR, like the authors assume in the sentence.=0Agab> This detail about=
 classification at the BS is in the appendix on=0A"Sending and Receiving IP=
v4 Packets".=0Agab> Have replaced the text above with text taken from 5121 =
for this same =0Adescription.=0A>=A0=A0=A0 is assigned an unique IPv4 addre=
ss per recommendations in [RFC4968].=0A> =0A>=A0=A0=A0 To summarize:=0A> =
=0A>=A0=A0=A0 o=A0 IPv4 CS uses the IPv4 header fields to classify the pack=
ets and=0A>=A0=A0=A0=A0=A0=A0 map to the appropriate CID.=0AThe previous te=
xt talks about service flows; why 'CID' is mentioned here?=0Agab> Good poin=
t, changed to service flow here as well as an instance above.=0A>=A0=A0=A0 =
o=A0 A point-to-point link between MS and AR is established.=0AHow do the t=
wo statements fit together? How does IPv4 CS establish a p2p link?=0Agab> I=
've deleted this (as the new text is enough).=0A> =0A> 4.1.=A0 IPv4 CS link=
 establishment=0A> =0A>=A0=A0=A0 In order to enable the sending and receivi=
ng of IPv4 packets between=0A>=A0=A0=A0 the MS and the AR, the link between=
 the MS and the AR via the BS=0A>=A0=A0=A0 needs to be established.=A0 This=
 section explains the link=0A>=A0=A0=A0 establishment procedures following =
section 6.2 of [RFC5121].=A0 Steps=0A>=A0=A0=A0 1-4 are same as indicated i=
n 6.2 of [RFC5121].=A0 In step 5, support=0A>=A0=A0=A0 for IPv4 is indicate=
d.=A0 In step 6, an initial service flow is created=0AInitial service flow?=
 [RFC5121] does not specifies further service flows.=0Agab> RFC5121 step 6 =
does talk about establishment of a "service flow" (no=0Amention of it being=
 "initial"). Deleted "initial". RFC5121 talks about=0Aan "initial service f=
low" and ISF in the appendix, however.=0A>=A0=A0=A0 that can be used for ex=
changing IP layer signaling messages, e.g.=0A>=A0=A0=A0 address assignment =
procedures using DHCP.=0A> =0A>=A0=A0=A0 The address assignment procedure d=
epends on the MS mode - i,e.=0A>=A0=A0=A0 whether it is acting as a Mobile =
IPv4 client or a Proxy Mobile IP=0A>=A0=A0=A0 client or a Simple IP client.=
=A0 In the most common case, the MS=0A>=A0=A0=A0 requests an IP address usi=
ng DHCP.=0AWhat is the difference between a Proxy MIP client and a Simple I=
P client?=0ADoes the 'MS' request an IP address by DHCP in the case of Clie=
nt-MIP?=0Agab> I've deleted this paragraph. An IP-over-foo document does no=
t talk about potential=0Aother uses with Mobile IP or any other such applic=
ation, only about the most=0Aessential business of transmitting and receivi=
ng packets on that link.=0AI've deleted all mention of Mobile IP as well as=
 the reference to RFC3344.=0A...=0A> =0A> =0A> 4.3.=A0 Maximum Transmission=
 Unit=0A> =0A>=A0=A0=A0=A0=A0=A0 The MTU value for IPv4 packets on an IEEE =
802.16 link is=0A>=A0=A0=A0 configurable.=A0 The default MTU for IPv4 packe=
ts over an IEEE 802.16=0A'is configurable'?? How, by which means??=0Agab> T=
here are several means to change it including manual, DHCP option, etc. =0A=
Added this in parentheses to clarify: (e.g., see the bottom of this section=
 for some possible=0Amechanisms). =0A>=A0=A0=A0=A0=A0=A0 link SHOULD be 150=
0 octets.=0A> =0A...=0A> =0A>=A0=A0=A0 o=A0 The IEEE is currently revising =
802.16 (see 802.16Rev2=0AIEEE802.16 has revised the specification. Update t=
he reference.=0Agab> done.=0A>=A0=A0=A0=A0=A0=A0 [802_16REV2]) to (among ot=
her things) allow providing the Service=0A>=A0=A0=A0=A0=A0=A0 Data Unit or =
MAC MTU in the IEEE 802.16 SBC-REQ/SBC-RSP phase,=0A>=A0=A0=A0=A0=A0=A0 suc=
h that future IEEE 802.16 compliant clients can infer and=0A>=A0=A0=A0=A0=
=A0=A0 configure the negotiated MTU size for the IPv4 CS link.=A0 However,=
=0A>=A0=A0=A0=A0=A0=A0 the implementation must communicate the negotiated M=
TU value to=0A>=A0=A0=A0=A0=A0=A0 the IP layer to adjust the IP Maximum pay=
load size for proper=0A>=A0=A0=A0=A0=A0=A0 handling of fragmentation.=A0 No=
te that this method is useful only=0A>=A0=A0=A0=A0=A0=A0 when MS is directl=
y connected to the BS.=0A>=A0=A0=A0 o=A0 Configuration and negotiation of M=
TU size at the network layer by=0A>=A0=A0=A0=A0=A0=A0 using the DHCP interf=
ace MTU option [RFC2132].=0A> =0A>=A0=A0=A0 This document recommends that a=
ll future implementations of IPv4 and=0AWhy 'future'?=0Agab> changed it: s/=
all future//=0A>=A0=A0=A0 IPv4 CS clients SHOULD implement the DHCP interfa=
ce MTU option=0A>=A0=A0=A0 [RFC2132] in order to configure its interface MT=
U accordingly.=0A> =0A>=A0=A0=A0 In the absence of DHCP MTU configuration, =
the client node (MS) has=0A>=A0=A0=A0 two alternatives: 1) use the default =
MTU (1500 bytes) or 2) determine=0A>=A0=A0=A0 the MTU by the methods descri=
bed in [802_16REV2].=0ACan MS rely on the IEEE802.16 methods? Mandatory for=
 all IEEE802.16 implementations?=0Agab> It cannot, just like it cannot rely=
 on the other mentioned mitigations =0A(DHCP option) and that is why the IP=
v4 situation is sub-optimal with respect to=0AIPv6.=0A>=A0=A0=A0 Additional=
ly, the clients are encouraged to run PMTU[RFC 1191] or=0A>=A0=A0=A0 PPMTUD=
[RFC 4821].=A0 However, the PMTU mechanism has inherent problems=0A>=A0=A0=
=A0 of packet loss due to ICMP messages not reaching the sender and IPv4=0A=
>=A0=A0=A0 routers not fragmenting the packets due to the DF bit being set =
in=0A>=A0=A0=A0 the IP packet.=A0 The above mentioned path MTU mechanisms w=
ill take=0A>=A0=A0=A0 care of the MTU size between the MS and its correspon=
dent node across=0A>=A0=A0=A0 different flavors of convergence layers in th=
e access networks.=0A> =0A...=0A> =0A>=A0=A0=A0 [IEEE802_16]=0A>=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 "IEEE 802.16e, IEEE standard for Local an=
d metropolitan=0A>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 area networks,=
 Part 16:Air Interface for fixed and Mobile=0A>=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 broadband wireless access systems", October 2005.=0AIEEE802=
.16-2009 is released and supersedes 16e as well as REV2.=0AWhy is the IEEE8=
02.16 specification listed under informative?=0Agab> 802.16-2009 is now the=
 *only* reference to 802.16, and moved to normative.=0A=0A...=0A=A0=0A> App=
endix B.=A0 Sending and Receiving IPv4 Packets=0A> =0A> =0A...=0A>=A0=A0=A0=
 AR performs normal routing for the packets that it receives,=0A>=A0=A0=A0 =
processing them per its forwarding table.=A0 However, the DHCP relay=0A>=A0=
=A0=A0 agent in the AR MUST maintain the tunnel interface on which it=0A>=
=A0=A0=A0 receives DHCP requests so that it can relay the DHCP responses to=
 the=0A>=A0=A0=A0 correct MS.=A0 One way of doing this is to have a mapping=
 between MAC=0A>=A0=A0=A0 address and Tunnel Identifier.=0AWhich MAC addres=
s?=0Agab> The assumption is that is the MAC address contained in the DHCP r=
equest.=0AAnother method would be to keep a correspondence between DHCP Tra=
nsaction ID=0Aand the incoming Tunnel ID. At any rate, this is not specific=
 to 802.16, so =0AI replaced the last sentence with:=0A"The particular meth=
od is out of scope of this specification=0Aas it need not depend on any par=
ticularities of IEEE 802.16."=0A> =0A> Appendix C.=A0 WiMAX IPCS MTU size=
=0A> =0A>=A0=A0=A0 WiMAX (Worldwide Interoperability for Microwave Access) =
forum has=0A>=A0=A0=A0 defined a network architecture[WMF].=A0 Furthermore,=
 WiMAX has=0A>=A0=A0=A0 specified IPv4 CS support for transmission of IPv4 =
packets between MS=0A>=A0=A0=A0 and BS over the IEEE 802.16 link.=A0 The Wi=
MAX IPv4 CS and this=0A>=A0=A0=A0 specification are similar.=A0 One signifi=
cant difference, however, is=0A>=A0=A0=A0 that the WiMAX Forum [WMF] has sp=
ecified the IP MTU as 1400 octets=0A>=A0=A0=A0 [WMF] as opposed to 1500 in =
this specification.=0A> =0A>=A0=A0=A0 Hence if an IPv4 CS MS configured wit=
h an MTU of 1500 octet enters a=0A>=A0=A0=A0 WiMAX network, some of the iss=
ues mentioned in this specification may=0A>=A0=A0=A0 arise.=A0 As mentioned=
 in section 4.3, the possible mechanisms are not=0A>=A0=A0=A0 guaranteed to=
 work.=A0 Furthermore, an IPv4 CS client is not capable of=0A>=A0=A0=A0 doi=
ng ARP probing to find out the link MTU.=A0 On the other hand, it is=0A>=A0=
=A0=A0 imperative for an MS to know the link MTU size.=A0 In practice, MS=
=0A>=A0=A0=A0 should be able to sense or deduce the fact that they are oper=
ating=0A>=A0=A0=A0 within a WiMAX network (e.g., given the WiMAX-specific=
=0A>=A0=A0=A0 particularities of the authentication and network entry proce=
dures),=0A>=A0=A0=A0 and adjust their MTU size accordingly.=A0 This documen=
t makes no=0A>=A0=A0=A0 further assumptions in this respect.=0AAppendix C s=
hould be removed.=0AOnly WiMAX devices will enter WiMAX networks, and WiMAX=
 devices know about the MTU size in WiMAX networks.=0Agab> That is actually=
 said right above, so you might agree it is useful info (since=0Ayou noted =
it yourself). The text above was already changed per your request to *NOT*=
=0Aissue any recommendation to WiMAX (even though per charter that would be=
 ok). =0AI don't see the harm and see some benefit in keeping it as informa=
tive text.=0A=0A=0A=A0=0A=0A=0A----- Original Message ----=0A> From: gabrie=
l montenegro <g_e_montenegro@yahoo.com>=0A> To: "Riegel, Maximilian (NSN - =
DE/Munich)" <maximilian.riegel@nsn.com>; 16ng@ietf.org=0A> Cc: ext Alper Ye=
gin <alper.yegin@yegin.org>=0A> Sent: Tuesday, June 9, 2009 9:48:47 AM=0A> =
Subject: Re: [16NG] I-DAction:draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05.=
txt=0A> =0A> =0A> Thanks Max, the attached version is better! I'm still goi=
ng through the =0A> comments.=0A> Will respond later on.=0A> =0A> =0A> ----=
- Original Message ----=0A> > From: "Riegel, Maximilian (NSN - DE/Munich)" =
=0A> > To: "Riegel, Maximilian (NSN - DE/Munich)" ; =0A> 16ng@ietf.org=0A> =
> Cc: ext Alper Yegin ; ext gabriel montenegro =0A> =0A> > Sent: Thursday, =
June 4, 2009 3:58:26 PM=0A> > Subject: Re: [16NG] I-DAction:draft-ietf-16ng=
-ipv4-over-802-dot-16-ipcs-05.txt=0A> > =0A> > Please find attached the txt=
 document with my comments, in the case your=0A> > screen looks as awful as=
 mine (word wrapping did a horrible job)=0A> > =0A> > Bye=0A> > Max=0A> > =
=0A> > -----Original Message-----=0A> > From: 16ng-bounces@ietf.org [mailto=
:16ng-bounces@ietf.org] On Behalf Of=0A> > ext Riegel, Maximilian (NSN - DE=
/Munich)=0A> > Sent: Friday, June 05, 2009 12:50 AM=0A> > To: 16ng@ietf.org=
=0A> > Cc: ext Alper Yegin; ext gabriel montenegro=0A> > Subject: Re: [16NG=
]=0A> > I-DAction:draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-05.txt=0A> > =
=0A> > I went through the document and found a couple of issues, which I wo=
uld=0A> > like to see in a better shape.=0A> > Please find my comments inli=
ne:=0A> > =0A> > Bye=0A> > Max=0A> > =0A> > > 16ng Working Group=A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 S.=0A>=
 > Madanapalli=0A> > > Internet-Draft=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Ordyn=0A> > Technologies=0A> > =
> Intended status: Standards Track=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 Soohong D.=0A> > Park=0A> > > Expires: April 4, 2009=A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Samsung=0A> > =0A> > =0A> > =
=0A> > -----Inline Attachment Follows-----=0A> > =0A> > > 16ng Working Grou=
p=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 S. Madanapalli=0A> > > Internet-Draft=A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Ordyn Technologies=0A> =
> > Intended status: Standards Track=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 Soohong D. Park=0A> > > Expires: April 4, 2009=A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Samsung Electronics=0A> > >=A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 S. Chakrabarti=0A> > >=A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 IP Infusion=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 G. Montenegro=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Mic=
rosoft Corporation=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Oct=
ober 2008=0A> > > =0A> > > =0A> > > Transmission of IPv4 packets over IEEE =
802.16's IP Convergence Sublayer=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 draft-ietf-=
16ng-ipv4-over-802-dot-16-ipcs-05.txt=0A> > > =0A> > > Status of this Memo=
=0A> > > =0A> > >=A0 =A0 By submitting this Internet-Draft, each author rep=
resents that any=0A> > >=A0 =A0 applicable patent or other IPR claims of wh=
ich he or she is aware=0A> > >=A0 =A0 have been or will be disclosed, and a=
ny of which he or she becomes=0A> > >=A0 =A0 aware will be disclosed, in ac=
cordance with Section 6 of BCP 79.=0A> > > =0A> > >=A0 =A0 Internet-Drafts =
are working documents of the Internet Engineering=0A> > >=A0 =A0 Task Force=
 (IETF), its areas, and its working groups.=A0 Note that=0A> > >=A0 =A0 oth=
er groups may also distribute working documents as Internet-=0A> > >=A0 =A0=
 Drafts.=0A> > > =0A> > >=A0 =A0 Internet-Drafts are draft documents valid =
for a maximum of six months=0A> > >=A0 =A0 and may be updated, replaced, or=
 obsoleted by other documents at any=0A> > >=A0 =A0 time.=A0 It is inapprop=
riate to use Internet-Drafts as reference=0A> > >=A0 =A0 material or to cit=
e them other than as "work in progress."=0A> > > =0A> > >=A0 =A0 The list o=
f current Internet-Drafts can be accessed at=0A> > >=A0 =A0 http://www.ietf=
.org/ietf/1id-abstracts.txt. =0A> > > =0A> > >=A0 =A0 The list of Internet-=
Draft Shadow Directories can be accessed at=0A> > >=A0 =A0 http://www.ietf.=
org/shadow.html. =0A> > > =0A> > >=A0 =A0 This Internet-Draft will expire o=
n April 4, 2009.=0A> > > =0A> > > Abstract=0A> > > =0A> > >=A0 =A0 IEEE 802=
.16 is an air interface specification for wireless broadband=0A> > >=A0 =A0=
 access.=A0 IEEE 802.16 has specified multiple service specific=0A> > >=A0 =
=A0 convergence sublayers for transmitting upper layer protocols.=A0 The=0A=
> > >=A0 =A0 packet CS (Packet Convergence Sublayer) is used for the transp=
ort of=0A> > >=A0 =A0 all packet-based protocols such as Internet Protocol =
(IP), IEEE 802.3=0A> > >=A0 =A0 (Ethernet) and IEEE 802.1Q (VLAN).=A0 The I=
P-specific part of the=0A> > =0A> > Meanwhile the IEEE802.16-2009 (was REV2=
) specification has been released.=0A> > IEEE802.16-2009 does not know anym=
ore about the IEEE 802.1Q (VLAN) CS.=0A> > =0A> > >=A0 =A0 Packet CS enable=
s the transport of IPv4 packets directly over the=0A> > > =0A> > > =0A> > >=
 =0A> > > Madanapalli, et al.=A0 =A0 =A0 Expires April 4, 2009=A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 [Page 1]=0A> > > =0A> > > Internet-Draft=A0 =A0 =A0 =A0=
 IPv4 over IEEE 802.16's IP CS=A0 =A0 =A0 =A0 October 2008=0A> > > =0A> > >=
 =0A> > >=A0 =A0 IEEE 802.16 MAC.=0A> > > =0A> > >=A0 =A0 This document spe=
cifies the frame format, the Maximum Transmission=0A> > >=A0 =A0 Unit (MTU)=
 and address assignment procedures for transmitting IPv4=0A> > >=A0 =A0 pac=
kets over the IP-specific part of the Packet Convergence Sublayer=0A> > >=
=A0 =A0 of IEEE 802.16.=0A> > > =0A> > > =0A> > > Table of Contents=0A> > >=
 =0A> > >=A0 =A0 1.=A0 Introduction . . . . . . . . . . . . . . . . . . . .=
 . . . . .=A0 3=0A> > >=A0 =A0 2.=A0 Terminology=A0 . . . . . . . . . . . .=
 . . . . . . . . . . . . .=A0 3=0A> > >=A0 =A0 3.=A0 Typical Network Archit=
ecture for IPv4 over IEEE 802.16 . . . .=A0 3=0A> > >=A0 =A0 =A0 3.1.=A0 IE=
EE 802.16 IPv4 Convergence sub-layer support . . . . . .=A0 3=0A> > >=A0 =
=A0 4.=A0 IPv4 CS link in 802.16 Networks=A0 . . . . . . . . . . . . . . .=
=A0 4=0A> > >=A0 =A0 =A0 4.1.=A0 IPv4 CS link establishment . . . . . . . .=
 . . . . . . . .=A0 4=0A> > >=A0 =A0 =A0 4.2.=A0 Frame Format for IPv4 Pack=
ets=A0 . . . . . . . . . . . . . .=A0 4=0A> > >=A0 =A0 =A0 4.3.=A0 Maximum =
Transmission Unit=A0 . . . . . . . . . . . . . . . .=A0 5=0A> > >=A0 =A0 5.=
=A0 Subnet Model and IPv4 Address Assignment . . . . . . . . . . .=A0 7=0A>=
 > >=A0 =A0 =A0 5.1.=A0 IPv4 Unicast Address Assignment and Router Discover=
y . . .=A0 7=0A> > >=A0 =A0 =A0 5.2.=A0 Address Resolution Protocol=A0 . . =
. . . . . . . . . . . . .=A0 8=0A> > >=A0 =A0 =A0 5.3.=A0 IP Multicast Addr=
ess Mapping . . . . . . . . . . . . . . .=A0 8=0A> > >=A0 =A0 6.=A0 Securit=
y Considerations=A0 . . . . . . . . . . . . . . . . . . .=A0 8=0A> > >=A0 =
=A0 7.=A0 IANA Considerations=A0 . . . . . . . . . . . . . . . . . . . . .=
=A0 8=0A> > >=A0 =A0 8.=A0 Acknowledgements . . . . . . . . . . . . . . . .=
 . . . . . . .=A0 8=0A> > >=A0 =A0 9.=A0 References . . . . . . . . . . . .=
 . . . . . . . . . . . . . .=A0 9=0A> > >=A0 =A0 =A0 9.1.=A0 Normative Refe=
rences . . . . . . . . . . . . . . . . . . .=A0 9=0A> > >=A0 =A0 =A0 9.2.=
=A0 Informative References . . . . . . . . . . . . . . . . . .=A0 9=0A> > >=
=A0 =A0 Appendix A.=A0 Multiple Convergence Layers - Impact on Subnet=0A> >=
 >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Model . . . . . . . . . . . . . . . . . .=
 . . . . . . 10=0A> > >=A0 =A0 Appendix B.=A0 Sending and Receiving IPv4 Pa=
ckets=A0 . . . . . . . . . 10=0A> > >=A0 =A0 Appendix C.=A0 WiMAX IPCS MTU =
size . . . . . . . . . . . . . . . . . 11=0A> > >=A0 =A0 Appendix D.=A0 Tho=
ughts on handling multicast-broadcast IP=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 packets . . . . . . . . . . . . . . . . . . . . . . . 12=0A> > >=A0 =
=A0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12=
=0A> > >=A0 =A0 Intellectual Property and Copyright Statements . . . . . . =
. . . . 14=0A> > > =0A> > > =0A> > > =0A> > > =0A> > > =0A> > > =0A> > > =
=0A> > > =0A> > > =0A> > > =0A> > > =0A> > > =0A> > > =0A> > > =0A> > > =0A=
> > > Madanapalli, et al.=A0 =A0 =A0 Expires April 4, 2009=A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 [Page 2]=0A> > > =0A> > > Internet-Draft=A0 =A0 =A0 =A0 IPv=
4 over IEEE 802.16's IP CS=A0 =A0 =A0 =A0 October 2008=0A> > > =0A> > > =0A=
> > > 1.=A0 Introduction=0A> > > =0A> > >=A0 =A0 IEEE 802.16 [IEEE802_16] i=
s a connection oriented access technology=0A> > >=A0 =A0 for the last mile.=
=A0 The IEEE 802.16 specification includes the PHY=0A> > >=A0 =A0 and MAC l=
ayers.=A0 The MAC includes various convergence sublayers (CS)=0A> > >=A0 =
=A0 for transmitting higher layer packets including IPv4 packets=0A> > >=A0=
 =A0 [RFC5154].=0A> > > =0A> > >=A0 =A0 The scope of this specification is =
limited to the operation of IPv4=0A> > >=A0 =A0 over the IP-specific part o=
f the packet CS (referred to as "IPv4 CS"=0A> > >=A0 =A0 or simply "IP CS" =
in this document).=0A> > =0A> > IPv4 CS should be used throughout the docum=
ent to prevent mixing it up with =0A> the =0A> > IPv6 CS specification. The=
re is nothing like IP CS in the IEEE802.16 =0A> > specification, there is o=
nly IPv4 CS and IPv6 CS.=0A> > BTW: there is now a single ETH CS carrying I=
Pv4 as well as IPv6 payload.=0A> > =0A> > >=A0 =A0 This document specifies =
a method for encapsulating and transmitting=0A> > >=A0 =A0 IPv4 [RFC0791] p=
ackets over the IP CS of IEEE 802.16.=A0 This document=0A> > =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ^IPv4 CS=0A> > =
>=A0 =A0 also specifies the MTU and address assignment method for the IEEE=
=0A> > =0A> > Which MTU, which address assignment? More concise wording wou=
ld help.=0A> > =0A> > >=A0 =A0 802.16 based networks using IP CS.=0A> > =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ^IPv4 CS=0A> >=
 > =0A> > >=A0 =A0 This document also discusses ARP (Address Resolution Pro=
tocol) and=0A> > >=A0 =A0 Multicast Address Mapping whose operation is simi=
lar to any other=0A> > >=A0 =A0 point-to-point link model.=0A> > =0A> > Wha=
t do you mean with this sentence?=0A> > =0A> > >=A0 =A0 The key words "MUST=
", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",=0A> > >=A0 =A0 "SHOULD", "=
SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this=0A> > >=A0 =A0 do=
cument are to be interpreted as described in [RFC2119].=0A> > > =0A> > > =
=0A> > > 2.=A0 Terminology=0A> > > =0A> > >=A0 =A0 The terminology in this =
document is based on the definitions in=0A> > >=A0 =A0 [RFC5154].=0A> > > =
=0A> > > =0A> > > 3.=A0 Typical Network Architecture for IPv4 over IEEE 802=
.16=0A> > > =0A> > >=A0 =A0 The network architecture follows what is descri=
bed in [RFC5154] and=0A> > >=A0 =A0 [RFC5121].=A0 In a nutshell, each MS is=
 attached to an Access Router=0A> > =0A> > Please clarify 'MS'; according t=
o IEEE802.16 it only covers PHY and MAC.=0A> > According to IEEE802.16 the =
MS is not a 'host'.=0A> > =0A> > >=A0 =A0 (AR) through a Base Station (BS),=
 a layer 2 entity (from the=0A> > >=A0 =A0 perspective of the IPv6 link bet=
ween the MS and access router (AR)).=0A> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 ^IPv4??? Copy&Paste mistake?=0A> > > =0A> > >=A0 =A0 For fu=
rther information on the typical network architecture, see=0A> > >=A0 =A0 [=
RFC5121] section 5.=0A> > > =0A> > > 3.1.=A0 IEEE 802.16 IPv4 Convergence s=
ub-layer support=0A> > > =0A> > >=A0 =A0 As described in [RFC5154] section =
3.3., an IP specific subpart=0A> > >=A0 =A0 classifier carries either IPv4 =
or IPv6 payloads.=A0 In this document,=0A> > >=A0 =A0 we are focusing on th=
e IPv4 over IP Convergence Sublayer.=0A> > =0A> > Section 3.3 of [RFC5154] =
is outdated! IEEE802.16-2009 introduced a refined CS =0A> > structure. IMHO=
, we shouldn't make references to outdated specifications, but =0A> > base =
the work on the most recent IEEE802.16 specification.=0A> > =0A> > > =0A> >=
 > =0A> > > =0A> > > =0A> > > Madanapalli, et al.=A0 =A0 =A0 Expires April =
4, 2009=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 [Page 3]=0A> > > =0A> > > Internet-D=
raft=A0 =A0 =A0 =A0 IPv4 over IEEE 802.16's IP CS=A0 =A0 =A0 =A0 October 20=
08=0A> > > =0A> > > =0A> > >=A0 =A0 For further information on the IEEE 802=
.16 Convergence Sublayer and=0A> > >=A0 =A0 encapsulation of IP packets, se=
e [RFC5121] section 4 and [RFC5154]=0A> > >=A0 =A0 section 3.3.=0A> > =0A> =
> As [RFC5154] is outdated, I would propose to provide an updated section 3=
.3. =0A> as =0A> > part of the IPv4 CS document.=0A> > =0A> > > 4.=A0 IPv4 =
CS link in 802.16 Networks=0A> > > =0A> > >=A0 =A0 This document defines th=
e IPv4 CS link as a point-to-point link=0A> > >=A0 =A0 between the MS and t=
he AR using a set of service flows consisting of=0A> > =0A> > MS is not the=
 host. What is a link between a L2 device (MS) and a L3 device =0A> > (AR)?=
=0A> > =0A> > >=A0 =A0 MAC transport connections between a MS and BS, and L=
2 tunnel(s)=0A> > >=A0 =A0 between between a BS and AR.=A0 It is recommende=
d that a tunnel be=0A> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 ^is=0A> > >=A0 =A0 established between the AR and a BS based on 'p=
er MS' or 'per service=0A> > >=A0 =A0 flow' (An MS can have multiple servic=
e flows each of which are=0A> > =0A> > What is a tunnel between BS and AR b=
ased on 'per MS'? It seems, some GRE =0A> > functionality is assumed here w=
ithout spelling it out.=0A> > =0A> > >=A0 =A0 identified by a unique servic=
e flow ID).=A0 Then the tunnel(s) for an=0A> > >=A0 =A0 MS, in combination =
with the MS's MAC transport connections, forms a=0A> > >=A0 =A0 single poin=
t-to-point link.=A0 Each MS belongs to a different link and=0A> > =0A> > Ho=
w does this work - multiple tunnels between two endpoints forming a single =
=0A> > link? I would assume, that there must be some classification in plac=
e, which =0A> is =0A> > part of the BS according to IEEE802.16, not part of=
 the AR, like the authors =0A> > assume in the sentence.=0A> > =0A> > >=A0 =
=A0 is assigned an unique IPv4 address per recommendations in [RFC4968].=0A=
> > > =0A> > >=A0 =A0 To summarize:=0A> > > =0A> > >=A0 =A0 o=A0 IPv4 CS us=
es the IPv4 header fields to classify the packets and=0A> > >=A0 =A0 =A0 ma=
p to the appropriate CID.=0A> > =0A> > The previous text talks about servic=
e flows; why 'CID' is mentioned here?=0A> > =0A> > >=A0 =A0 o=A0 A point-to=
-point link between MS and AR is established.=0A> > =0A> > How do the two s=
tatements fit together? How does IPv4 CS establish a p2p link?=0A> > =0A> >=
 > =0A> > > 4.1.=A0 IPv4 CS link establishment=0A> > > =0A> > >=A0 =A0 In o=
rder to enable the sending and receiving of IPv4 packets between=0A> > >=A0=
 =A0 the MS and the AR, the link between the MS and the AR via the BS=0A> >=
 >=A0 =A0 needs to be established.=A0 This section explains the link=0A> > =
>=A0 =A0 establishment procedures following section 6.2 of [RFC5121].=A0 St=
eps=0A> > >=A0 =A0 1-4 are same as indicated in 6.2 of [RFC5121].=A0 In ste=
p 5, support=0A> > >=A0 =A0 for IPv4 is indicated.=A0 In step 6, an initial=
 service flow is created=0A> > =0A> > Initial service flow? [RFC5121] does =
not specifies further service flows.=0A> > =0A> > >=A0 =A0 that can be used=
 for exchanging IP layer signaling messages, e.g.=0A> > >=A0 =A0 address as=
signment procedures using DHCP.=0A> > > =0A> > >=A0 =A0 The address assignm=
ent procedure depends on the MS mode - i,e.=0A> > >=A0 =A0 whether it is ac=
ting as a Mobile IPv4 client or a Proxy Mobile IP=0A> > >=A0 =A0 client or =
a Simple IP client.=A0 In the most common case, the MS=0A> > >=A0 =A0 reque=
sts an IP address using DHCP.=0A> > =0A> > What is the difference between a=
 Proxy MIP client and a Simple IP client?=0A> > Does the 'MS' request an IP=
 address by DHCP in the case of Client-MIP?=0A> > =0A> > > =0A> > > 4.2.=A0=
 Frame Format for IPv4 Packets=0A> > > =0A> > >=A0 =A0 IPv4 packets are tra=
nsmitted in Generic IEEE 802.16 MAC frames in the=0A> > >=A0 =A0 data paylo=
ads of the 802.16 PDU ( see section 3.2 of [RFC5154] ).=0A> > > =0A> > > =
=0A> > > =0A> > > =0A> > > =0A> > > =0A> > > =0A> > > Madanapalli, et al.=
=A0 =A0 =A0 Expires April 4, 2009=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 [Page 4]=
=0A> > > =0A> > > Internet-Draft=A0 =A0 =A0 =A0 IPv4 over IEEE 802.16's IP =
CS=A0 =A0 =A0 =A0 October 2008=0A> > > =0A> > > =0A> > >=A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 1=0A> > >=
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 0 1 2 3 4 5 6 7 8 9 0 1 2 3=
 4 5=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |=
H|E|=A0 TYPE=A0 =A0 |R|C|EKS|R|LEN=A0 |=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=0A> > >=A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |=A0 =A0 LEN LSB=A0 =A0 |=A0 =A0 CID MS=
B=A0 =A0 |=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+-+-+=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 |=A0 =A0 CID LSB=A0 =A0 |=A0 =A0 HCS=A0 =A0 =A0 =A0 |=0A> > >=A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |=A0 =A0 =A0 =A0 =
=A0 =A0 IPv4=A0 =A0 =A0 =A0 =A0 =A0 =A0 |=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 +-=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 -+=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |=A0 =A0 =
=A0 =A0 =A0 =A0 header=A0 =A0 =A0 =A0 =A0 =A0 |=0A> > >=A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 +-=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 -+=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |=A0 =
=A0 =A0 =A0 =A0 =A0 and=A0 =A0 =A0 =A0 =A0 =A0 =A0 |=0A> > >=A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +-=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 -+=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 /=
=A0 =A0 =A0 =A0 =A0 =A0 payload=A0 =A0 =A0 =A0 =A0 /=0A> > >=A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +-=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 -+=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |=
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |=0A> > >=A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |CRC (optional) |=
=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 +-+-+-+-+-+-+-+-+=
=0A> > > =0A> > > =0A> > >=A0 =A0 =A0 =A0 =A0 Figure 1: IEEE 802.16 MAC Fra=
me Format for=A0 IPv4 Packets=0A> > > =0A> > >=A0 =A0 =A0 H: Header Type (1=
 bit).=A0 Shall be set to zero indicating that it=0A> > >=A0 =A0 =A0 is a G=
eneric MAC PDU.=0A> > >=A0 =A0 =A0 E: Encryption Control. 0 =3D Payload is =
not encrypted; 1 =3D Payload=0A> > >=A0 =A0 =A0 is encrypted.=0A> > >=A0 =
=A0 =A0 R: Reserved.=A0 Shall be set to zero.=0A> > >=A0 =A0 =A0 C: CRC Ind=
icator. 1 =3D CRC is included, 0 =3D 1 No CRC is included=0A> > >=A0 =A0 =
=A0 EKS: Encryption Key Sequence=0A> > >=A0 =A0 =A0 LEN: The Length in byte=
s of the MAC PDU including the MAC header=0A> > >=A0 =A0 =A0 and the CRC if=
 present (11 bits)=0A> > >=A0 =A0 =A0 CID: Connection Identifier (16 bits)=
=0A> > >=A0 =A0 =A0 HCS: Header Check Sequence (8 bits)=0A> > >=A0 =A0 =A0 =
CRC: An optional 8-bit field.=A0 CRC appended to the PDU after=0A> > >=A0 =
=A0 =A0 encryption.=0A> > >=A0 =A0 =A0 TYPE: This field indicates the subhe=
aders (Mesh subheader,=0A> > >=A0 =A0 =A0 Fragmentation Subheader, Packing =
subheader etc and special payload=0A> > >=A0 =A0 =A0 types (ARQ) present in=
 the message payload=0A> > > =0A> > > 4.3.=A0 Maximum Transmission Unit=0A>=
 > > =0A> > >=A0 =A0 =A0 The MTU value for IPv4 packets on an IEEE 802.16 l=
ink is=0A> > >=A0 =A0 configurable.=A0 The default MTU for IPv4 packets ove=
r an IEEE 802.16=0A> > =0A> > 'is configurable'?? How, by which means??=0A>=
 > =0A> > >=A0 =A0 =A0 link SHOULD be 1500 octets.=0A> > > =0A> > > =0A> > =
> =0A> > > =0A> > > Madanapalli, et al.=A0 =A0 =A0 Expires April 4, 2009=A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 [Page 5]=0A> > > =0A> > > Internet-Draft=A0 =
=A0 =A0 =A0 IPv4 over IEEE 802.16's IP CS=A0 =A0 =A0 =A0 October 2008=0A> >=
 > =0A> > > =0A> > >=A0 =A0 Per [RFC5121] section 6.3, the IP MTU can vary =
to be larger or=0A> > >=A0 =A0 smaller than 1500 octets.=0A> > > =0A> > >=
=A0 =A0 if an MS transmits 1500-octet packets in a deployment with a smalle=
r=0A> > >=A0 =A0 MTU, packets from the MS may be dropped at the link-layer =
silently.=0A> > >=A0 =A0 Unlike IPv6, in which departures from the default =
MTU are readily=0A> > >=A0 =A0 advertised via the MTU option in Neighbor Di=
scovery, there is no=0A> > >=A0 =A0 similarly reliable mechanism in IPv4, a=
s the legacy IPv4 client=0A> > >=A0 =A0 implementations do not determine th=
e link MTU by default before=0A> > >=A0 =A0 sending packets.=A0 Even though=
 there is a DHCP option to accomplish=0A> > >=A0 =A0 this, DHCP servers are=
 required to provide the MTU information only=0A> > >=A0 =A0 when requested=
.=0A> > > =0A> > >=A0 =A0 Discovery and configuration of the proper link MT=
U value ensures=0A> > >=A0 =A0 adequate usage of the network bandwidth and =
resources.=A0 Accordingly,=0A> > >=A0 =A0 deployments should avoid packet l=
oss due to a mismatch between the=0A> > >=A0 =A0 default MTU and the config=
ured link MTUs.=0A> > > =0A> > >=A0 =A0 =A0 Some of the mechanisms availabl=
e for the IPv4 CS host to find out=0A> > >=A0 =A0 the link's MTU value and =
mitigate MTU-related issues are:=0A> > > =0A> > >=A0 =A0 o=A0 The IEEE is c=
urrently revising 802.16 (see 802.16Rev2=0A> > =0A> > IEEE802.16 has revise=
d the specification. Update the reference.=0A> > =0A> > >=A0 =A0 =A0 [802_1=
6REV2]) to (among other things) allow providing the Service=0A> > >=A0 =A0 =
=A0 Data Unit or MAC MTU in the IEEE 802.16 SBC-REQ/SBC-RSP phase,=0A> > >=
=A0 =A0 =A0 such that future IEEE 802.16 compliant clients can infer and=0A=
> > >=A0 =A0 =A0 configure the negotiated MTU size for the IPv4 CS link.=A0=
 However,=0A> > >=A0 =A0 =A0 the implementation must communicate the negoti=
ated MTU value to=0A> > >=A0 =A0 =A0 the IP layer to adjust the IP Maximum =
payload size for proper=0A> > >=A0 =A0 =A0 handling of fragmentation.=A0 No=
te that this method is useful only=0A> > >=A0 =A0 =A0 when MS is directly c=
onnected to the BS.=0A> > >=A0 =A0 o=A0 Configuration and negotiation of MT=
U size at the network layer by=0A> > >=A0 =A0 =A0 using the DHCP interface =
MTU option [RFC2132].=0A> > > =0A> > >=A0 =A0 This document recommends that=
 all future implementations of IPv4 and=0A> > =0A> > Why 'future'?=0A> > =
=0A> > >=A0 =A0 IPv4 CS clients SHOULD implement the DHCP interface MTU opt=
ion=0A> > >=A0 =A0 [RFC2132] in order to configure its interface MTU accord=
ingly.=0A> > > =0A> > >=A0 =A0 In the absence of DHCP MTU configuration, th=
e client node (MS) has=0A> > >=A0 =A0 two alternatives: 1) use the default =
MTU (1500 bytes) or 2) determine=0A> > >=A0 =A0 the MTU by the methods desc=
ribed in [802_16REV2].=0A> > =0A> > Can MS rely on the IEEE802.16 methods? =
Mandatory for all IEEE802.16 =0A> > implementations?=0A> > =0A> > >=A0 =A0 =
Additionally, the clients are encouraged to run PMTU[RFC 1191] or=0A> > >=
=A0 =A0 PPMTUD[RFC 4821].=A0 However, the PMTU mechanism has inherent probl=
ems=0A> > >=A0 =A0 of packet loss due to ICMP messages not reaching the sen=
der and IPv4=0A> > >=A0 =A0 routers not fragmenting the packets due to the =
DF bit being set in=0A> > >=A0 =A0 the IP packet.=A0 The above mentioned pa=
th MTU mechanisms will take=0A> > >=A0 =A0 care of the MTU size between the=
 MS and its correspondent node across=0A> > >=A0 =A0 different flavors of c=
onvergence layers in the access networks.=0A> > > =0A> > > =0A> > > =0A> > =
> Madanapalli, et al.=A0 =A0 =A0 Expires April 4, 2009=A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 [Page 6]=0A> > > =0A> > > Internet-Draft=A0 =A0 =A0 =A0 IPv4 ov=
er IEEE 802.16's IP CS=A0 =A0 =A0 =A0 October 2008=0A> > > =0A> > > =0A> > =
> 5.=A0 Subnet Model and IPv4 Address Assignment=0A> > > =0A> > >=A0 =A0 Th=
e Subnet Model recommended for IPv4 over IEEE 802.16 using IP CS is=0A> > >=
=A0 =A0 based on the point-to-point link between MS and AR [RFC4968], hence=
=0A> > >=A0 =A0 each MS shall be assigned an address with 32bit prefix-leng=
th or=0A> > >=A0 =A0 subnet-mask.=A0 The point-to-point link between MS and=
 AR is achieved=0A> > >=A0 =A0 using a set of IEEE 802.16 MAC connections (=
identified by CIDs) and=0A> > >=A0 =A0 an L2 tunnel (e.g., a GRE tunnel) pe=
r MS between BS and AR.=A0 If the=0A> > >=A0 =A0 AR is co-located with the =
BS, then the set of IEEE 802.16 MAC=0A> > >=A0 =A0 connections between the =
MS and BS/AR represent the point-to- point=0A> > >=A0 =A0 connection.=0A> >=
 > =0A> > > 5.1.=A0 IPv4 Unicast Address Assignment and Router Discovery=0A=
> > > =0A> > >=A0 =A0 DHCP [RFC2131] SHOULD be used for assigning IPv4 addr=
ess for the MS.=0A> > >=A0 =A0 DHCP messages are transported over the IEEE =
802.16 MAC connection to=0A> > >=A0 =A0 and from the BS and relayed to the =
AR.=A0 In case the DHCP server does=0A> > >=A0 =A0 not reside in the AR, th=
e AR SHOULD implement DHCP relay Agent=0A> > >=A0 =A0 [RFC1542].=0A> > > =
=0A> > >=A0 =A0 Although DHCP is the recommended method of address assignme=
nt, it is=0A> > >=A0 =A0 possible that the MS could be a pure Mobile IPv4 [=
RFC3344] device=0A> > >=A0 =A0 which will be offered an IP address from its=
 home network after=0A> > >=A0 =A0 successful Mobile IP [RFC3344] registrat=
ion.=A0 In such situations, the=0A> > >=A0 =A0 mobile host SHOULD use the d=
efault link MTU in order to avoid any=0A> > >=A0 =A0 link-layer packet loss=
 due to larger than supported packet size in=0A> > >=A0 =A0 the IP CS link.=
=0A> > > =0A> > >=A0 =A0 Router discovery messages [RFC1256] contain router=
 solicitation and=0A> > >=A0 =A0 router advertisements.=A0 The Router solic=
itation messages (multicast=0A> > >=A0 =A0 or broadcast) from the MS are de=
livered to the AR via the BS through=0A> > >=A0 =A0 the point-to-point link=
.=A0 The BS SHOULD map the all-routers multicast=0A> > >=A0 =A0 nodes or br=
oadcast nodes for router discovery to the AR's IP address=0A> > >=A0 =A0 an=
d deliver directly to the AR.=A0 Similarly a router advertisement to=0A> > =
>=A0 =A0 the all-nodes multicast nodes will be either unicast to each MS by=
=0A> > >=A0 =A0 the BS separately or put onto a multicast connection to whi=
ch all MSs=0A> > >=A0 =A0 are listening to.=A0 If no multicast connection e=
xists, and the BS does=0A> > >=A0 =A0 not have the capability to aggregate =
and disaggregate the messages to=0A> > >=A0 =A0 and from the MS hosts, then=
 the AR implementation must ensure that=0A> > >=A0 =A0 unicast messages are=
 sent to the corresponding individual MS hosts=0A> > >=A0 =A0 within the se=
t of broadcast or multicast recipients.=A0 This=0A> > >=A0 =A0 specificatio=
n simply assumes that the multicast service is provided.=0A> > >=A0 =A0 How=
 the multicast service is implemented in an IEEE 802.16 Packet CS=0A> > >=
=A0 =A0 deployment is out of scope of this document.=0A> > > =0A> > >=A0 =
=A0 The 'Next hop' IP address of the IP CS MS is always the IP address of=
=0A> > >=A0 =A0 the AR, because MS and AR are attached via a point-to-point=
 link.=0A> > > =0A> > > =0A> > > =0A> > > =0A> > > Madanapalli, et al.=A0 =
=A0 =A0 Expires April 4, 2009=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 [Page 7]=0A> >=
 > =0A> > > Internet-Draft=A0 =A0 =A0 =A0 IPv4 over IEEE 802.16's IP CS=A0 =
=A0 =A0 =A0 October 2008=0A> > > =0A> > > =0A> > > 5.2.=A0 Address Resoluti=
on Protocol=0A> > > =0A> > >=A0 =A0 The IP CS does not allow for transmissi=
on of ARP [RFC0826] packets.=0A> > >=A0 =A0 Furthermore, in a point-to-poin=
t link model, address resolution is=0A> > >=A0 =A0 not needed.=0A> > > =0A>=
 > > 5.3.=A0 IP Multicast Address Mapping=0A> > > =0A> > >=A0 =A0 IPv4 mult=
icast packets are carried over the point-to-point link=0A> > >=A0 =A0 betwe=
en the AR and the MS (via the BS).=A0 The IPv4 multicast packets=0A> > >=A0=
 =A0 are classified normally at the IP CS if the IEEE 802.16 MAC=0A> > >=A0=
 =A0 connection has been set up with a multicast IP address as a=0A> > >=A0=
 =A0 classification parameter for the destination IP address.=A0 The IPv4=
=0A> > >=A0 =A0 multicast address may be mapped into a multicast CID as def=
ined in=0A> > >=A0 =A0 the IEEE 802.16 specification.=A0 The mapping mechan=
ism at the BS or=0A> > >=A0 =A0 the relative efficiency of using a multicas=
t CID as opposed to=0A> > >=A0 =A0 simulating multicast by generating multi=
ple unicast messages are out=0A> > >=A0 =A0 of scope of this document.=A0 F=
or further considerations on the use of=0A> > >=A0 =A0 multicast CIDs see [=
ETHCS].=0A> > > =0A> > > =0A> > > 6.=A0 Security Considerations=0A> > > =0A=
> > >=A0 =A0 This document specifies transmission of IPv4 packets over IEEE=
 802.16=0A> > >=A0 =A0 networks with IPv4 Convergence Sublayer and does not=
 introduce any=0A> > >=A0 =A0 new vulnerabilities to IPv4 specifications or=
 operation.=A0 The=0A> > >=A0 =A0 security of the IEEE 802.16 air interface=
 is the subject of=0A> > >=A0 =A0 [IEEE802_16].=A0 In addition, the securit=
y issues of the network=0A> > >=A0 =A0 architecture spanning beyond the IEE=
E 802.16 base stations is the=0A> > >=A0 =A0 subject of the documents defin=
ing such architectures, such as WiMAX=0A> > >=A0 =A0 Network Architecture [=
WMF].=0A> > > =0A> > > =0A> > > 7.=A0 IANA Considerations=0A> > > =0A> > >=
=A0 =A0 This document has no actions for IANA.=0A> > > =0A> > > =0A> > > 8.=
=A0 Acknowledgements=0A> > > =0A> > >=A0 =A0 The authors would like to ackn=
owledge the contributions of Bernard=0A> > >=A0 =A0 Aboba, Dave Thaler, Jar=
i Arkko, Bachet Sarikaya, Basavaraj Patil,=0A> > >=A0 =A0 Paolo Narvaez, an=
d Bruno Sousa for their review and comments.=A0 The=0A> > >=A0 =A0 working =
group members Burcak Beser, Wesley George, Max Riegel and DJ=0A> > >=A0 =A0=
 Johnston helped shape the MTU discussion for IPv4 CS link.=A0 Thanks to=0A=
> > >=A0 =A0 many other members of the 16ng working group who commented on =
this=0A> > >=A0 =A0 document to make it better.=0A> > > =0A> > > =0A> > > =
=0A> > > =0A> > > Madanapalli, et al.=A0 =A0 =A0 Expires April 4, 2009=A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 [Page 8]=0A> > > =0A> > > Internet-Draft=A0 =A0=
 =A0 =A0 IPv4 over IEEE 802.16's IP CS=A0 =A0 =A0 =A0 October 2008=0A> > > =
=0A> > > =0A> > > 9.=A0 References=0A> > > =0A> > > 9.1.=A0 Normative Refer=
ences=0A> > > =0A> > >=A0 =A0 [RFC2119]=A0 Bradner, S., "Key words for use =
in RFCs to Indicate=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 Requirement Levels",=
 BCP 14, RFC 2119, March 1997.=0A> > > =0A> > >=A0 =A0 [RFC0791]=A0 Postel,=
 J., "Internet Protocol", STD 5, RFC 791,=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =
=A0 September 1981.=0A> > > =0A> > >=A0 =A0 [RFC0826]=A0 Plummer, D., "Ethe=
rnet Address Resolution Protocol: Or=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 con=
verting network protocol addresses to 48.bit Ethernet=0A> > >=A0 =A0 =A0 =
=A0 =A0 =A0 =A0 address for transmission on Ethernet hardware", STD 37,=0A>=
 > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 RFC 826, November 1982.=0A> > > =0A> > >=A0=
 =A0 [RFC2131]=A0 Droms, R., "Dynamic Host Configuration Protocol",=0A> > >=
=A0 =A0 =A0 =A0 =A0 =A0 =A0 RFC 2131, March 1997.=0A> > > =0A> > >=A0 =A0 [=
RFC1542]=A0 Wimer, W., "Clarifications and Extensions for the=0A> > >=A0 =
=A0 =A0 =A0 =A0 =A0 =A0 Bootstrap Protocol", RFC 1542, October 1993.=0A> > =
> =0A> > >=A0 =A0 [RFC5121]=A0 Patil, B., Xia, F., Sarikaya, B., Choi, JH.,=
 and S.=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 Madanapalli, "Transmission of IP=
v6 via the IPv6=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 Convergence Sublayer ove=
r IEEE 802.16 Networks", RFC 5121,=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 Febru=
ary 2008.=0A> > > =0A> > >=A0 =A0 [RFC5154]=A0 Jee, J., Madanapalli, S., an=
d J. Mandin, "IP over IEEE=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 802.16 Proble=
m Statement and Goals", RFC 5154, April 2008.=0A> > > =0A> > >=A0 =A0 [RFC4=
968]=A0 Madanapalli, S., "Analysis of IPv6 Link Models for 802.16=0A> > >=
=A0 =A0 =A0 =A0 =A0 =A0 =A0 Based Networks", RFC 4968, August 2007.=0A> > >=
 =0A> > > 9.2.=A0 Informative References=0A> > > =0A> > >=A0 =A0 [RFC1191]=
=A0 Mogul, J. and S. Deering, "Path MTU discovery", RFC 1191,=0A> > >=A0 =
=A0 =A0 =A0 =A0 =A0 =A0 November 1990.=0A> > > =0A> > >=A0 =A0 [RFC4821]=A0=
 Mathis, M. and J. Heffner, "Packetization Layer Path MTU=0A> > >=A0 =A0 =
=A0 =A0 =A0 =A0 =A0 Discovery", RFC 4821, March 2007.=0A> > > =0A> > >=A0 =
=A0 [RFC2132]=A0 Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor=
=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 Extensions", RFC 2132, March 1997.=0A> =
> > =0A> > >=A0 =A0 [RFC4840]=A0 Aboba, B., Davies, E., and D. Thaler, "Mul=
tiple=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 Encapsulation Methods Considered H=
armful", RFC 4840,=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 April 2007.=0A> > > =
=0A> > >=A0 =A0 [RFC3344]=A0 Perkins, C., "IP Mobility Support for IPv4", R=
FC 3344,=0A> > > =0A> > > =0A> > > =0A> > > Madanapalli, et al.=A0 =A0 =A0 =
Expires April 4, 2009=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 [Page 9]=0A> > > =0A> =
> > Internet-Draft=A0 =A0 =A0 =A0 IPv4 over IEEE 802.16's IP CS=A0 =A0 =A0 =
=A0 October 2008=0A> > > =0A> > > =0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 Augus=
t 2002.=0A> > > =0A> > >=A0 =A0 [RFC1256]=A0 Deering, S., "ICMP Router Disc=
overy Messages", RFC 1256,=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 September 199=
1.=0A> > > =0A> > >=A0 =A0 [ETHCS]=A0 =A0 Jeon, H., Riegel, M., and S. Jeon=
g, "Transmission of IP=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 over Ethernet ove=
r IEEE 802.16 Networks", April 2008,=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 > >=
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =0A> draft-ietf-16ng-ip-over-ethernet-over-802.=
16-06.txt>.=0A> > > =0A> > >=A0 =A0 [802_16REV2]=0A> > >=A0 =A0 =A0 =A0 =A0=
 =A0 =A0 Johnston, D., "SDU MTU Capability Declaration",=0A> > >=A0 =A0 =A0=
 =A0 =A0 =A0 =A0 March 2008, .=0A> > > =0A> > >=A0 =A0 [IEEE802_16]=0A> > >=
=A0 =A0 =A0 =A0 =A0 =A0 =A0 "IEEE 802.16e, IEEE standard for Local and metr=
opolitan=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 area networks, Part 16:Air Inte=
rface for fixed and Mobile=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 broadband wir=
eless access systems", October 2005.=0A> > =0A> > IEEE802.16-2009 is releas=
ed and supersedes 16e as well as REV2.=0A> > Why is the IEEE802.16 specific=
ation listed under informative?=0A> > =0A> > >=A0 =A0 [WMF]=A0 =A0 =A0 "WiM=
AX End-to-End Network Systems Architecture Stage 2-3=0A> > >=A0 =A0 =A0 =A0=
 =A0 =A0 =A0 Release 1.2,=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 http://www.wim=
axforum.org/technology/documents",=0A> > >=A0 =A0 =A0 =A0 =A0 =A0 =A0 Janua=
ry 2008.=0A> > > =0A> > > =0A> > > Appendix A.=A0 Multiple Convergence Laye=
rs - Impact on Subnet Model=0A> > > =0A> > >=A0 =A0 Two different MSs using=
 two different convergence sublayers (e.g. an=0A> > >=A0 =A0 MS using Ether=
net CS only and another MS using IP CS only) cannot=0A> > >=A0 =A0 communic=
ate at data link layer and requires interworking at IP layer.=0A> > >=A0 =
=A0 For this reason, these two nodes must be configured to be on two=0A> > =
>=A0 =A0 different subnets.=A0 For more information refer to [RFC4840].=0A>=
 > > =0A> > > =0A> > > Appendix B.=A0 Sending and Receiving IPv4 Packets=0A=
> > > =0A> > >=A0 =A0 IEEE 802.16 MAC is a point-to-multipoint connection o=
riented air-=0A> > >=A0 =A0 interface, and the process of sending and recei=
ving of IPv4 packets=0A> > >=A0 =A0 is different from multicast-capable sha=
red medium technologies like=0A> > >=A0 =A0 Ethernet.=0A> > > =0A> > >=A0 =
=A0 Before any packets are transmitted, a IEEE 802.16 transport=0A> > >=A0 =
=A0 connection must be established.=A0 This connection consists of IEEE=0A>=
 > >=A0 =A0 802.16 MAC transport connection between MS and BS and an L2 tun=
nel=0A> > >=A0 =A0 between BS and AR (if these two are not co-located).=A0 =
This IEEE=0A> > >=A0 =A0 802.16 transport connection provides a point-to-po=
int link between=0A> > >=A0 =A0 the MS and AR.=A0 All the packets originate=
d at the MS always reach the=0A> > >=A0 =A0 AR before being transmitted to =
the final destination.=0A> > > =0A> > > =0A> > > =0A> > > Madanapalli, et a=
l.=A0 =A0 =A0 Expires April 4, 2009=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 [Page 10=
]=0A> > > =0A> > > Internet-Draft=A0 =A0 =A0 =A0 IPv4 over IEEE 802.16's IP=
 CS=A0 =A0 =A0 =A0 October 2008=0A> > > =0A> > > =0A> > >=A0 =A0 IPv4 packe=
ts are carried directly in the payload of IEEE 802.16=0A> > >=A0 =A0 frames=
 when the IPv4 CS is used.=A0 IPv4 CS classifies the packet based=0A> > >=
=A0 =A0 on upper layer (IP and transport layers) header fields to place the=
=0A> > >=A0 =A0 packet on one of the available connections identified by th=
e CID.=0A> > >=A0 =A0 The classifiers for the IPv4 CS are source and destin=
ation IPv4=0A> > >=A0 =A0 addresses, source and destinations ports, Type-of=
-Service and IP=0A> > >=A0 =A0 protocol field.=A0 The CS may employ Packet =
Header Suppression (PHS)=0A> > >=A0 =A0 after the classification.=0A> > > =
=0A> > >=A0 =A0 The BS optionally reconstructs the payload header if PHS is=
 in use.=0A> > >=A0 =A0 It then tunnels the packet that has been received o=
n a particular MAC=0A> > >=A0 =A0 connection to the AR.=A0 Similarly the pa=
ckets received on a tunnel=0A> > >=A0 =A0 interface from the AR, would be m=
apped to a particular CID using the=0A> > >=A0 =A0 IPv4 classification mech=
anism.=0A> > > =0A> > >=A0 =A0 AR performs normal routing for the packets t=
hat it receives,=0A> > >=A0 =A0 processing them per its forwarding table.=
=A0 However, the DHCP relay=0A> > >=A0 =A0 agent in the AR MUST maintain th=
e tunnel interface on which it=0A> > >=A0 =A0 receives DHCP requests so tha=
t it can relay the DHCP responses to the=0A> > >=A0 =A0 correct MS.=A0 One =
way of doing this is to have a mapping between MAC=0A> > >=A0 =A0 address a=
nd Tunnel Identifier.=0A> > =0A> > Which MAC address?=0A> > =0A> > > =0A> >=
 > Appendix C.=A0 WiMAX IPCS MTU size=0A> > > =0A> > >=A0 =A0 WiMAX (Worldw=
ide Interoperability for Microwave Access) forum has=0A> > >=A0 =A0 defined=
 a network architecture[WMF].=A0 Furthermore, WiMAX has=0A> > >=A0 =A0 spec=
ified IPv4 CS support for transmission of IPv4 packets between MS=0A> > >=
=A0 =A0 and BS over the IEEE 802.16 link.=A0 The WiMAX IPv4 CS and this=0A>=
 > >=A0 =A0 specification are similar.=A0 One significant difference, howev=
er, is=0A> > >=A0 =A0 that the WiMAX Forum [WMF] has specified the IP MTU a=
s 1400 octets=0A> > >=A0 =A0 [WMF] as opposed to 1500 in this specification=
.=0A> > > =0A> > >=A0 =A0 Hence if an IPv4 CS MS configured with an MTU of =
1500 octet enters a=0A> > >=A0 =A0 WiMAX network, some of the issues mentio=
ned in this specification may=0A> > >=A0 =A0 arise.=A0 As mentioned in sect=
ion 4.3, the possible mechanisms are not=0A> > >=A0 =A0 guaranteed to work.=
=A0 Furthermore, an IPv4 CS client is not capable of=0A> > >=A0 =A0 doing A=
RP probing to find out the link MTU.=A0 On the other hand, it is=0A> > >=A0=
 =A0 imperative for an MS to know the link MTU size.=A0 In practice, MS=0A>=
 > >=A0 =A0 should be able to sense or deduce the fact that they are operat=
ing=0A> > >=A0 =A0 within a WiMAX network (e.g., given the WiMAX-specific=
=0A> > >=A0 =A0 particularities of the authentication and network entry pro=
cedures),=0A> > >=A0 =A0 and adjust their MTU size accordingly.=A0 This doc=
ument makes no=0A> > >=A0 =A0 further assumptions in this respect.=0A> > =
=0A> > Appendix C should be removed.=0A> > Only WiMAX devices will enter Wi=
MAX networks, and WiMAX devices know about the =0A> =0A> > MTU size in WiMA=
X networks.=0A> > =0A> > > =0A> > > =0A> > > =0A> > > =0A> > > =0A> > > =0A=
> > > Madanapalli, et al.=A0 =A0 =A0 Expires April 4, 2009=A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 [Page 11]=0A> > > =0A> > > Internet-Draft=A0 =A0 =A0 =A0 IP=
v4 over IEEE 802.16's IP CS=A0 =A0 =A0 =A0 October 2008=0A> > > =0A> > > =
=0A> > > Appendix D.=A0 Thoughts on handling multicast-broadcast IP packets=
=0A> > > =0A> > >=A0 =A0 Although this document does not directly specify d=
etails of multicast=0A> > >=A0 =A0 or broadcast packet handling, here are s=
ome suggestions:=0A> > > =0A> > >=A0 =A0 While uplink connections from the =
MSs to the BS provide only unicast=0A> > >=A0 =A0 transmission capabilities=
, downlink connections can be used for=0A> > >=A0 =A0 multicast transmissio=
n to a group of MSs as well as unicast=0A> > >=A0 =A0 transmission from the=
 BS to a single MS.=A0 For all-node IP addresses,=0A> > >=A0 =A0 the AR or =
BS should have special mapping and the packets should be=0A> > >=A0 =A0 dis=
tributed to all active point-to-point connections by the AR or by=0A> > >=
=A0 =A0 the BS.=A0 All-router multicast packets and any broadcast packets f=
rom=0A> > >=A0 =A0 a MS will be forwarded to the AR by the BS.=A0 If BS and=
 MS are co-=0A> > >=A0 =A0 located, then the first approach is more useful.=
=A0 If the AR and BS=0A> > >=A0 =A0 are located separately then the second =
approach should be=0A> > >=A0 =A0 implemented.=A0 An initial capability exc=
hange message should be=0A> > >=A0 =A0 performed between BS and AR (if they=
 are not co-located) to determine=0A> > >=A0 =A0 who would perform the dist=
ribution of multicast/broadcast packets.=0A> > >=A0 =A0 Such mechansim shou=
ld be part of L2 exchange during the connection=0A> > >=A0 =A0 setup and is=
 out of scope of this document.=A0 In order to save energy=0A> > >=A0 =A0 o=
f the wireless end devices in the IEEE 802.16 wireless network, it=0A> > >=
=A0 =A0 is recommened that the multicast and broadcast from network side to=
=0A> > >=A0 =A0 device side should be reduced.=A0 Only DHCP, IGMP, Router a=
dvertisemnet=0A> > >=A0 =A0 packets are allowed on the downlink for multica=
st and broadcast IP=0A> > >=A0 =A0 addresses.=A0 Other protocols using mult=
icast and broadcast IP=0A> > >=A0 =A0 addresses should be permitted through=
 local AR/BS configuration.=0A> > > =0A> > > =0A> > > Authors' Addresses=0A=
> > > =0A> > >=A0 =A0 Syam Madanapalli=0A> > >=A0 =A0 Ordyn Technologies=0A=
> > >=A0 =A0 1st Floor, Creator Building, ITPL=0A> > >=A0 =A0 Bangalore - 5=
60066=0A> > >=A0 =A0 India=0A> > > =0A> > >=A0 =A0 Email: smadanapalli@gmai=
l.com=0A> > > =0A> > > =0A> > >=A0 =A0 Soohong Daniel Park=0A> > >=A0 =A0 S=
amsung Electronics=0A> > >=A0 =A0 416 Maetan-3dong, Yeongtong-gu=0A> > >=A0=
 =A0 Suwon 442-742=0A> > >=A0 =A0 Korea=0A> > > =0A> > >=A0 =A0 Email: sooh=
ong.park@samsung.com=0A> > > =0A> > > =0A> > > =0A> > > =0A> > > =0A> > > M=
adanapalli, et al.=A0 =A0 =A0 Expires April 4, 2009=A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 [Page 12]=0A> > > =0A> > > Internet-Draft=A0 =A0 =A0 =A0 IPv4 over =
IEEE 802.16's IP CS=A0 =A0 =A0 =A0 October 2008=0A> > > =0A> > > =0A> > >=
=A0 =A0 Samita Chakrabarti=0A> > >=A0 =A0 IP Infusion=0A> > >=A0 =A0 1188 A=
rques Avenue=0A> > >=A0 =A0 Sunnyvale, CA=0A> > >=A0 =A0 USA=0A> > > =0A> >=
 >=A0 =A0 Email: samitac@ipinfusion.com=0A> > > =0A> > > =0A> > >=A0 =A0 Ga=
briel Montenegro=0A> > >=A0 =A0 Microsoft Corporation=0A> > >=A0 =A0 Redmon=
d, Washington=0A> > >=A0 =A0 USA=0A> > > =0A> > >=A0 =A0 Email: gabriel.mon=
tenegro@microsoft.com=0A> > > =0A> =0A> ___________________________________=
____________=0A> 16NG mailing list=0A> 16NG@ietf.org=0A> https://www.ietf.o=
rg/mailman/listinfo/16ng=0A

From root@core3.amsl.com  Sun Jun 14 23:30:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: 16ng@ietf.org
Delivered-To: 16ng@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id BCBE43A6970; Sun, 14 Jun 2009 23:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090615063001.BCBE43A6970@core3.amsl.com>
Date: Sun, 14 Jun 2009 23:30:01 -0700 (PDT)
Cc: 16ng@ietf.org
Subject: [16NG] I-D Action:draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-06.txt
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jun 2009 06:30:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IP over IEEE 802.16 Networks Working Group of the IETF.


	Title           : Transmission of IPv4 packets over IEEE 802.16's IP Convergence Sublayer
	Author(s)       : S. Madanapalli, et al.
	Filename        : draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-06.txt
	Pages           : 14
	Date            : 2009-06-14

IEEE 802.16 is an air interface specification for wireless broadband
access.  IEEE 802.16 has specified multiple service specific
Convergence Sublayers for transmitting upper layer protocols.  The
packet CS (Packet Convergence Sublayer) is used for the transport of
all packet-based protocols such as Internet Protocol (IP) and IEEE
802.3 (Ethernet).  The IP-specific part of the Packet CS enables the
transport of IPv4 packets directly over the IEEE 802.16 MAC.

This document specifies the frame format, the Maximum Transmission
Unit (MTU) and address assignment procedures for transmitting IPv4
packets over the IP-specific part of the Packet Convergence Sublayer
of IEEE 802.16.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-06.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-06-14232401.I-D@ietf.org>


--NextPart--

From g_e_montenegro@yahoo.com  Tue Jun 23 09:52:28 2009
Return-Path: <g_e_montenegro@yahoo.com>
X-Original-To: 16ng@core3.amsl.com
Delivered-To: 16ng@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 99B9C28C2FA for <16ng@core3.amsl.com>; Tue, 23 Jun 2009 09:52:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level: 
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[AWL=-0.178, BAYES_00=-2.599, SARE_MLH_Stock1=0.87]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9FvkT2-2ZMCn for <16ng@core3.amsl.com>; Tue, 23 Jun 2009 09:52:28 -0700 (PDT)
Received: from web82602.mail.mud.yahoo.com (web82602.mail.mud.yahoo.com [68.142.201.119]) by core3.amsl.com (Postfix) with SMTP id E73933A6829 for <16ng@ietf.org>; Tue, 23 Jun 2009 09:52:27 -0700 (PDT)
Received: (qmail 23505 invoked by uid 60001); 23 Jun 2009 16:52:41 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1245775961; bh=66Yk0NQIXITR82GfGZiXP0bB4aNU6ojgBa21arCVKKA=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=zUK6sSbgZE6WAvM5LruodcmhR13SARXTIHpOBhxfl5AUhKpA18K0WBJvNNn/MTh7p7nBkH5ONkET1XWDAURnE8F833T/f9+3I/RYnr6hFz0v8skX2ThT7w69MRxagUU06vrDix3Ggg/uFyT7wFbOOLLslF81HDOZNO+ihAFWMI0=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=PncCUKGfxUBzpD6PYT1VyjZitCwll8gEumAYRfDdSCDMPJ1ZbpJ0kskNyDCvP51bRmlbl9BUsuO9fjx8Q77d0dRNbPa5HdshKiiQLjO3BMr61RVaYL9e5Fas6k1oGYsMhSW1BFjpCoN/R5Box+XjptyhKIu3DY/mk8Io+oTL4Qc=;
Message-ID: <410005.21904.qm@web82602.mail.mud.yahoo.com>
X-YMail-OSG: u2a2AysVM1kgcWjJKmIBUvmw86DuAXq8p4ns4s1frVoxjyRrVmXidgTYzCZYzJHkCLNsgl9mWfMB2b_xCJypjiHdSnXuuXZc90yHnF6O506..Q2E6Trq1GPONO1M0QzTq1WxKqrpmNKN8gZHKwUZ5zi68qd_mM50pcUvkGowZCf9wNoL3jNHN24s0EnH5JC_Kn24WbAFOx3NUAh_ZoxqW2fWcMFFXLH_MwwDEMSTbvngdIzUPY5mlHzBc8DXlnxa__DrrDM9RRnxRYalfsx2VIwt8WY7pg7Rp5kqqZ8zwnpcCBnGZmVm.RC_cE7edfZOjQ--
Received: from [24.16.92.42] by web82602.mail.mud.yahoo.com via HTTP; Tue, 23 Jun 2009 09:52:41 PDT
X-Mailer: YahooMailRC/1277.43 YahooMailWebService/0.7.289.10
Date: Tue, 23 Jun 2009 09:52:41 -0700 (PDT)
From: gabriel montenegro <g_e_montenegro@yahoo.com>
To: 16ng@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [16NG] cancelled Stockholm meeting
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jun 2009 16:52:28 -0000

Hi,=0A=0ADaniel and I cancelled the 16ng meeting for Stockholm. There hasn'=
t been much activity on the alias, =0Aand our remaining documents are well =
on the way out of the WGs hands and into the IESG soon.=0AIPv4 CS was revis=
ed recently towards that goal, and (after a while of us chairs sitting on i=
t) ETH CS =0Ais just waiting on a new version that=0Auses the new required=
=A0boilerplate text in order to be re-submitted to the IESG.=0A=0AGabriel
