From 16ng-bounces@ietf.org Fri Jun 01 14:10:29 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HuBZx-0007qK-Pv; Fri, 01 Jun 2007 14:10:25 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1HuAWM-0001LC-VE
	for 16ng-confirm+ok@megatron.ietf.org; Fri, 01 Jun 2007 13:02:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HuAWM-0001Kx-L5; Fri, 01 Jun 2007 13:02:38 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HuAWM-0005bj-5Y; Fri, 01 Jun 2007 13:02:38 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l51H2Kn5006227; Fri, 1 Jun 2007 20:02:32 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 1 Jun 2007 20:02:27 +0300
Received: from daebe103.NOE.Nokia.com ([10.241.35.24]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 1 Jun 2007 12:02:13 -0500
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
Subject: RE: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE
	802.16eNetworks
Date: Fri, 1 Jun 2007 12:01:45 -0500
Message-ID: <3C33B44F3E969F4D8DE8D578078410C8CC81EC@daebe103.NOE.Nokia.com>
In-Reply-To: <013201c7a3cd$c1279b50$380c7c0a@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE
	802.16eNetworks
Thread-Index: AcejzaEB9X+H9FsMTcuJkc7r93vRUQAoCkOg
References: <0JIQ0097QCH1KD@mmp1.samsung.com>
	<013201c7a3cd$c1279b50$380c7c0a@china.huawei.com>
From: <rajeev.koodli@nsn.com>
To: <xiayangsong@huawei.com>, <soohong.park@samsung.com>
X-OriginalArrivalTime: 01 Jun 2007 17:02:13.0920 (UTC)
	FILETIME=[99EDBA00:01C7A46E]
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
X-Mailman-Approved-At: Fri, 01 Jun 2007 14:10:24 -0400
Cc: mipshop@ietf.org, 16ng@ietf.org
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org


Hi Frank,
=20
>
>The draft is based on RFC4068, and point-to-point link model=20
>is also recommended .
>RFC4068 is based on shared link model, and is not applicable=20
>for point-to-point link model without modification.
>So,  there are some basic conflicts in the draft.
>

At least that's not how I understood Bechet's presentation at Prague..=20
Now, I am confused.


>Formulation of  a prospective NCoA  is a main idea of  RFC4068.=20
>But in Point-to-Point link model, it is impossible to=20
>formulate the NCoA according to  RFC4068 because there is no=20
>proper prefix.
>

Well, you have the ability to return an NCoA in Hack from the NAR.=20
In this case, the MN does not formulate its own NCoA.

If there is something else we need to work on, please propose text=20
for the issue and what needs to be done.

Regards,

-Rajeev



>
>BR
>Frank
>
>
>----- Original Message -----=20
>From: "Daniel Park" <soohong.park@samsung.com>
>To: <mipshop@ietf.org>
>Cc: <16ng@ietf.org>
>Sent: Sunday, May 27, 2007 9:34 PM
>Subject: [16NG] FW: Call for Review on FMIP6 over IEEE 802.16e Networks
>
>
>> To MIPSHOP WG,=20
>>=20
>> Here is another expert review on "draft-ietf-mipshop-fh80216e-01",
>> particularly, IEEE 802.21 relevant texts in this draft.
>>=20
>> Reviewer (Yoshihiro Ohba) is a IETF official liaison from IEEE 802.21
>>=20
>> Thanks Yoshihiro and hope this helps...
>>=20
>>=20
>> ----
>>=20
>> Daniel Park & Gabriel Montenegro
>> Chairs, 16NG Working Group
>>=20
>
>
>---------------------------------------------------------------
>-----------------
>
>
>> _______________________________________________
>> 16NG mailing list
>> 16NG@ietf.org
>> https://www1.ietf.org/mailman/listinfo/16ng
>>=20
>
>_______________________________________________
>Mipshop mailing list
>Mipshop@ietf.org
>https://www1.ietf.org/mailman/listinfo/mipshop
>


_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng



From 16ng-bounces@ietf.org Sun Jun 03 21:15:58 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hv1An-0006J0-9K; Sun, 03 Jun 2007 21:15:53 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1Hv1Am-0006Iv-By
	for 16ng-confirm+ok@megatron.ietf.org; Sun, 03 Jun 2007 21:15:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hv1Am-0006In-2J
	for 16ng@ietf.org; Sun, 03 Jun 2007 21:15:52 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hv1Ak-00065e-Jr
	for 16ng@ietf.org; Sun, 03 Jun 2007 21:15:52 -0400
Received: from epmmp2 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0JJ300LI27IC43@mailout2.samsung.com> for 16ng@ietf.org;
	Mon, 04 Jun 2007 10:15:48 +0900 (KST)
Received: from daniel ([168.219.198.109])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0JJ300IZ57ICQF@mmp2.samsung.com> for
	16ng@ietf.org; Mon, 04 Jun 2007 10:15:48 +0900 (KST)
Date: Mon, 04 Jun 2007 10:15:41 +0900
From: Daniel Park <soohong.park@samsung.com>
To: 16ng@ietf.org
Message-id: <0JJ300IZ67ICQF@mmp2.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcekAaAFJ2DND7EyROqjPQ7aYmS7fACRDKmA
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Subject: [16NG] FW: Internet-Drafts Submission Cutoff Dates for the 69th IETF
 Meeting in Chicago, IL, USA
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org

FYI in case you missed it... 

> -----Original Message-----
> From: ietf-secretariat@ietf.org [mailto:ietf-secretariat@ietf.org] 
> Sent: Friday, June 01, 2007 1:00 PM
> To: ietf-announce@ietf.org
> Subject: Internet-Drafts Submission Cutoff Dates for the 69th 
> IETF Meeting in Chicago, IL, USA
> 
> 
> There are two (2) Internet-Draft cutoff dates for the 69th 
> IETF Meeting in Chicago, IL, USA:
> 
> July 2nd: Cutoff Date for Initial (i.e., version -00) 
> Internet-Draft Submissions 
> 
> All initial Internet-Drafts (version -00) must be submitted 
> by Monday, 
> July 2nd at 9:00 AM ET. As always, all initial submissions with a 
> filename beginning with "draft-ietf" must be approved by the 
> appropriate WG Chair before they can be processed or announced.  The 
> Secretariat would appreciate receiving WG Chair approval by Monday, 
> June 25th at 9:00 AM ET.
> 
> July 9th: Cutoff Date for Revised (i.e., version -01 and higher) 
> Internet-Draft Submissions 
> 
> All revised Internet-Drafts (version -01 and higher) must be 
> submitted 
> by Monday, July 9th at 9:00 AM ET.
> 
> Initial and revised Internet-Drafts received after their respective 
> cutoff dates will not be made available in the Internet-Drafts 
> directory or announced until on or after Monday, July 23rd at 9:00 
> AM ET, when Internet-Draft posting resumes.  Please do not wait until 
> the last minute to submit.
> 
> Thank you for your understanding and cooperation. If you have any 
> questions or concerns, then please send a message to 
> internet-drafts@ietf.org.
> 
> The IETF Secretariat
> 
> FYI: The Internet-Draft cutoff dates as well as other 
> significant dates
> for the 69th IETF Meeting can be found at 
> http://www.ietf.org/meetings/cutoff_dates_69.html.
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce
> 
> 



_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng



From 16ng-bounces@ietf.org Sun Jun 03 23:10:47 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hv2xz-0005tx-9I; Sun, 03 Jun 2007 23:10:47 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1Hv2xx-0005tp-7Q
	for 16ng-confirm+ok@megatron.ietf.org; Sun, 03 Jun 2007 23:10:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hv2xw-0005th-Ro; Sun, 03 Jun 2007 23:10:44 -0400
Received: from [202.99.23.227] (helo=people.com.cn)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1Hv2xt-0002Vv-Mv; Sun, 03 Jun 2007 23:10:44 -0400
Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id jm9b4663ec7f; Mon, 04 Jun 2007 11:18:36 +0800
Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC
	2.9.5.8) with SMTP id jm0465ca99e; Wed, 30 May 2007 04:38:14 +0800
Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC
	2.9.5.8) with SMTP id AISP action; Wed, 30 May 2007 04:38:14 +0800
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ht7is-00029G-CF; Tue, 29 May 2007 15:51:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ht7hj-0000YH-GH; Tue, 29 May 2007 15:50:03 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ht7hj-0006ht-2j; Tue, 29 May 2007 15:50:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id CC7D426E9E;
	Tue, 29 May 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Ht7hi-0007NI-K2; Tue, 29 May 2007 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Ht7hi-0007NI-K2@stiedprstage1.ietf.org>
Date: Tue, 29 May 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: i-d-announce-bounces@ietf.org
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: Internet-Drafts@ietf.org
X-Auto-Forward: jaglee@people.com.cn
 jag@kw.com.cn
X-Spam-Score: 2.2 (++)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Cc: 16ng@ietf.org
Subject: [16NG] I-D ACTION:draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-00.txt 
X-BeenThere: 16ng@ietf.org
Reply-To: internet-drafts@ietf.org
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org

--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-00.txt
	Pages		: 10
	Date		: 2007-5-29
	
   IEEE 802.16 is an air interface specification for wireless broadband
   access.  IEEE has specified the service specific convergence
   sublayers (CS) in the IEEE 802.16 MAC to be used by upper layer
   protocols.  Asynchronous Transfer Mode Convergence Sublayer (ATM CS)
   and Packet Convergence Sublayer (Packet CS) represent the two main
   service specific convergence sublayers for the IEEE 802.16.  The
   packet CS is used for transport for 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 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 IP Convergence Sublayer (IPCS) of the IEEE 802.16.  This
   document also provides the details of why the ARP cannot be sent over
   the IEEE 802.16 links using IPCS and a recommendation for this.



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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-5-29132404.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-00.txt

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

Content-Type: text/plain
Content-ID: <2007-5-29132404.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng

--NextPart--






From 16ng-bounces@ietf.org Mon Jun 04 00:44:47 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hv4Qx-00074s-IA; Mon, 04 Jun 2007 00:44:47 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1Hv4Qx-00074k-8j
	for 16ng-confirm+ok@megatron.ietf.org; Mon, 04 Jun 2007 00:44:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hv4Qw-00074c-Ux; Mon, 04 Jun 2007 00:44:46 -0400
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hv4Qv-0000mF-GT; Mon, 04 Jun 2007 00:44:46 -0400
Received: from ep_ms5_bk (mailout1.samsung.com [203.254.224.24])
	by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0JJ3004U9H5QFW@mailout1.samsung.com>; Mon,
	04 Jun 2007 13:44:14 +0900 (KST)
Received: from ep_spt01 (ms5.samsung.com [203.254.225.113])
	by ms5.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004)) with ESMTP id <0JJ300KWSH5QXU@ms5.samsung.com>; Mon,
	04 Jun 2007 13:44:14 +0900 (KST)
Content-return: prohibited
Date: Mon, 04 Jun 2007 04:44:14 +0000 (GMT)
From: Heejin Jang <heejin.jang@samsung.com>
Subject: Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE
	802.16e	Networks
To: Frank Xia <xiayangsong@huawei.com>
Message-id: <11362793.1303151180932254151.JavaMail.weblogic@ep_ml20>
MIME-version: 1.0
MIME-version: 1.0
X-Priority: 3
Msgkey: 20070604044414150@heejin.jang
X-MTR: 20070604044414150@heejin.jang
X-EPLocale: ko_KR.windows-1252
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
X-EPApproval-Locale: 
X-Spam-Score: 2.1 (++)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: "mipshop@ietf.org" <mipshop@ietf.org>, "16ng@ietf.org" <16ng@ietf.org>
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: heejin.jang@samsung.com
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1619852242=="
Errors-To: 16ng-bounces@ietf.org

--===============1619852242==
Content-return: prohibited
Content-type: text/plain; charset=windows-1252
Content-transfer-encoding: base64

SGksIEZyYW5rICYgRGFuaWVsLg0KIA0KUkZDNDA2OCBkZXNjcmliZXMgZmFzdCBITyBwcm9jZWR1
cmUgYmFzZWQgb24gcHJlZGljdGlvbiwgaW5jbHVkaW5nIE5Db0EgZm9ybXVsYXRpb24gaW4gYWR2
YW5jZS4NCkhvd2V2ZXIsIGhvdyB0byBhbGxvY2F0ZSB0aGUgcHJlZml4IHRvIE1OIGluIE5BUiAo
YmVmb3JlIGFjdHVhbCBITykgaXMgb3V0IG9mIHNjb3BlIGluIHRoaXMgZG9jdW1lbnQNCmFzIG1l
bnRpb25lZCBpbiBTZWN0aW9uIDQuIA0KIA0KIlRoZSBtZXRob2QgYnkgd2hpY2ggQWNjZXNzIFJv
dXRlcnMgZXhjaGFuZ2UgaW5mb3JtYXRpb24gYWJvdXQgdGhlaXIgbmVpZ2hib3JzLCBhbmQgdGhl
cmVieSBhbGxvdyANCiAgY29uc3RydWN0aW9uIG9mIFByb3h5IFJvdXRlciAgQWR2ZXJ0aXNlbWVu
dHMgd2l0aCBpbmZvcm1hdGlvbiBhYm91dCBuZWlnaGJvcmluZyBzdWJuZXRzIGlzIG91dHNpZGUN
CiAgdGhlIHNjb3BlIG9mIHRoaXMgZG9jdW1lbnQuIg0KIA0KRnVydGhlcm1vcmUsIHRoZSBwcm9i
bGVtIHlvdSBtZW50aW9uZWQgaW4gZHJhZnQteGlhLW1pcHNob3AtZm1pcC1wdHAtMDAgaXMgbm90
IGxpbWl0ZWQgb25seSB0byA4MDIuMTYgbmV0d29ya3MNCmJ1dCBoYXBwZW5zIGFsbCBuZXR3b3Jr
cyB3aGljaCBoYXZlIHBvaW50LXRvLXBvaW50IGxpbmsgc3VjaCBhcyAzR1BQMi4NCkkgdGhpbmsg
dGhhdCBpdCBpcyBwcm9wZXIgdG8gaGFuZGxlIHRoaXMgcHJvYmxlbSBzZXBhcmF0ZWx5Lg0KIA0K
VGhhbmtzIGZvciB5b3VyIG9waW5pb24uDQogDQotIFJlZ2FyZHMsIA0KSGVlamluDQoNCi0tLS0t
LS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLS0tDQpTZW5kZXIgOiBGcmFuayBYaWE8eGlheWFuZ3Nv
bmdAaHVhd2VpLmNvbT4NCkRhdGUgICA6IDIwMDctMDYtMDEgMDY6NTANClRpdGxlICA6IFtNaXBz
aG9wXSBSZTogWzE2TkddIEZXOiBDYWxsIGZvciBSZXZpZXcgb24gRk1JUDYgb3ZlciBJRUVFIDgw
Mi4xNmUJTmV0d29ya3MNCg0KSGkgRGFuaWVsDQoNCkhlcmUgaXMgbXkgdHdvIGNlbnRzLg0KDQpU
aGUgZHJhZnQgaXMgYmFzZWQgb24gUkZDNDA2OCwgYW5kIHBvaW50LXRvLXBvaW50IGxpbmsgbW9k
ZWwgaXMgYWxzbyByZWNvbW1lbmRlZCAuDQpSRkM0MDY4IGlzIGJhc2VkIG9uIHNoYXJlZCBsaW5r
IG1vZGVsLCBhbmQgaXMgbm90IGFwcGxpY2FibGUgZm9yIHBvaW50LXRvLXBvaW50IGxpbmsgbW9k
ZWwgd2l0aG91dCBtb2RpZmljYXRpb24uDQpTbywgIHRoZXJlIGFyZSBzb21lIGJhc2ljIGNvbmZs
aWN0cyBpbiB0aGUgZHJhZnQuDQoNCkZvcm11bGF0aW9uIG9mICBhIHByb3NwZWN0aXZlIE5Db0Eg
IGlzIGEgbWFpbiBpZGVhIG9mICBSRkM0MDY4LiANCkJ1dCBpbiBQb2ludC10by1Qb2ludCBsaW5r
IG1vZGVsLCBpdCBpcyBpbXBvc3NpYmxlIHRvIGZvcm11bGF0ZSB0aGUgTkNvQSANCmFjY29yZGlu
ZyB0byAgUkZDNDA2OCBiZWNhdXNlIHRoZXJlIGlzIG5vIHByb3BlciBwcmVmaXguDQoNCg0KQlIN
CkZyYW5rDQoNCg0KLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCkZyb206ICJEYW5pZWwg
UGFyayIgPHNvb2hvbmcucGFya0BzYW1zdW5nLmNvbT4NClRvOiA8bWlwc2hvcEBpZXRmLm9yZz4N
CkNjOiA8MTZuZ0BpZXRmLm9yZz4NClNlbnQ6IFN1bmRheSwgTWF5IDI3LCAyMDA3IDk6MzQgUE0N
ClN1YmplY3Q6IFsxNk5HXSBGVzogQ2FsbCBmb3IgUmV2aWV3IG9uIEZNSVA2IG92ZXIgSUVFRSA4
MDIuMTZlIE5ldHdvcmtzDQoNCg0KPiBUbyBNSVBTSE9QIFdHLCANCj4gDQo+IEhlcmUgaXMgYW5v
dGhlciBleHBlcnQgcmV2aWV3IG9uICJkcmFmdC1pZXRmLW1pcHNob3AtZmg4MDIxNmUtMDEiLA0K
PiBwYXJ0aWN1bGFybHksIElFRUUgODAyLjIxIHJlbGV2YW50IHRleHRzIGluIHRoaXMgZHJhZnQu
DQo+IA0KPiBSZXZpZXdlciAoWW9zaGloaXJvIE9oYmEpIGlzIGEgSUVURiBvZmZpY2lhbCBsaWFp
c29uIGZyb20gSUVFRSA4MDIuMjENCj4gDQo+IFRoYW5rcyBZb3NoaWhpcm8gYW5kIGhvcGUgdGhp
cyBoZWxwcy4uLg0KPiANCj4gDQo+IC0tLS0NCj4gDQo+IERhbmllbCBQYXJrICYgR2FicmllbCBN
b250ZW5lZ3JvDQo+IENoYWlycywgMTZORyBXb3JraW5nIEdyb3VwDQo+IA0KDQoNCi0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tDQoNCg0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXw0KPiAxNk5HIG1haWxpbmcgbGlzdA0KPiAxNk5HQGlldGYub3JnDQo+IGh0
dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvLzE2bmcNCj4gDQoNCl9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpNaXBzaG9wIG1haWxpbmcg
bGlzdA0KTWlwc2hvcEBpZXRmLm9yZw0KaHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vbWlwc2hvcA0KDQoNCg==





--===============1619852242==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng

--===============1619852242==--



From 16ng-bounces@ietf.org Mon Jun 04 14:28:05 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvHHf-0001xP-14; Mon, 04 Jun 2007 14:28:03 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1HvHHc-0001xE-W5
	for 16ng-confirm+ok@megatron.ietf.org; Mon, 04 Jun 2007 14:28:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvHHc-0001x6-MM; Mon, 04 Jun 2007 14:28:00 -0400
Received: from szxga03-in.huawei.com ([61.144.161.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvHHa-0006y5-2l; Mon, 04 Jun 2007 14:28:00 -0400
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JJ400GVQJ9LY8@szxga03-in.huawei.com>; Tue,
	05 Jun 2007 02:27:21 +0800 (CST)
Received: from ny3104051930 ([10.124.12.56])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JJ400JV3J9DS6@szxga03-in.huawei.com>; Tue,
	05 Jun 2007 02:27:21 +0800 (CST)
Date: Mon, 04 Jun 2007 13:29:03 -0500
From: Frank Xia <xiayangsong@huawei.com>
Subject: Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE802.16e
	Networks
To: Rajeev Koodli <rajeev.koodli@nokia.com>, heejin.jang@samsung.com
Message-id: <004501c7a6d6$3c168730$380c7c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-Priority: 3
X-MSMail-priority: Normal
References: <C289A06E.12142%rajeev.koodli@nokia.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 1df8e4abc9851cb4adb45bd64d8514ae
Cc: mipshop@ietf.org, 16ng@ietf.org
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0533060900=="
Errors-To: 16ng-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0533060900==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_+lDK8UrmwiFQbMIPdTBiRA)"

This is a multi-part message in MIME format.

--Boundary_(ID_+lDK8UrmwiFQbMIPdTBiRA)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE802.16e NetworksHi Rajeev 

I just picked some texts from 4068bis.

Could you make it clear when when P-to-P link is applied?


1 "(AP-ID, AR-Info) tuple Contains an access router's L2 and IP addresses, and
  prefix valid on the interface to which the Access Point (identified by AP-ID) is attached.  
 The triplet [Router's  L2 address, Router's IP address and Prefix] is called "AR-Info"".

=> Here, prefix is AR's physical interface prefix is used for NCoA formulation.
  As you know, this prefix is useless for P-to-P link model.

2 " Through the RtSolPr and PrRtAdv messages, the MN also formulates a
    prospective new CoA (NCoA), when it is still present on the PAR's
    link.  Hence, the latency due to new prefix discovery subsequent to
    handover is eliminated.  Furthermore, this prospective address can
    be used immediately after attaching to the new subnet link (i.e.,
    NAR's link) when the MN has received a "Fast Binding Acknowledgment
    (FBack)" message prior to its movement.  In the event it moves
    without receiving an FBack, the MN can still start using NCoA
    after announcing its attachment through an unsolicited Neighbor
    Advertisement message (with the 'O' bit set to zero) message [8];
    NAR responds to to this UNA message in case the tentative address is
    already in use.  In this way, NCoA configuration latency is reduced"
=>is it meaningful for P-to-P?

...

In fact any parts related to the prefix is not proper for p-to-p link model.


BTW, From my understanding, your propsal is that the only way for MN getting it's CoA
MUST be requesting it from NAR for P-to-P link.



BR
Frank








 



  ----- Original Message ----- 
  From: Rajeev Koodli 
  To: heejin.jang@samsung.com ; Frank Xia 
  Cc: mipshop@ietf.org ; 16ng@ietf.org ; ??? 
  Sent: Monday, June 04, 2007 12:56 PM
  Subject: Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE802.16e Networks



  As far as I see, there is no problem here!

  It does not matter what you call the prefix advertised in PrRtAdv. RFC 4068 does not make assumptions about how the prefixes are assigned and managed on an AR's link. So, it is inaccurate to say as such in draft-xia-mipshop-fmip-ptp-00.txt. 

  So, if prefix A is advertised in PrRtAdv, and a MN formulates a prospective address IP-A and sends FBU, IP-A can be overridden by NAR in HAck.

  Section 6.2.2

                Code        3: Handover Accepted, NCoA assigned
                               (used in Assigned addressing)


  The supplied NCoA is provided in FBack or NAACK option.

  This is the way I understood the problem and the solution for ptp links.

  What am I missing?

  -Rajeev




  On 6/3/07 9:44 PM, "ext Heejin Jang" <heejin.jang@samsung.com> wrote:


    Hi, Frank & Daniel.

    RFC4068 describes fast HO procedure based on prediction, including NCoA formulation in advance.
    However, how to allocate the prefix to MN in NAR (before actual HO) is out of scope in this document
    as mentioned in Section 4.

    "The method by which Access Routers exchange information about their neighbors, and thereby allow
      construction of Proxy Router  Advertisements with information about neighboring subnets is outside
      the scope of this document."

    Furthermore, the problem you mentioned in draft-xia-mipshop-fmip-ptp-00 is not limited only to 802.16 networks
    but happens all networks which have point-to-point link such as 3GPP2.
    I think that it is proper to handle this problem separately.

    Thanks for your opinion.

    - Regards,
    Heejin

    ------- Original Message -------
    Sender : Frank Xia<xiayangsong@huawei.com>
    Date   : 2007-06-01 06:50
    Title  : [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE 802.16e    Networks

    Hi Daniel

    Here is my two cents.

    The draft is based on RFC4068, and point-to-point link model is also recommended .
    RFC4068 is based on shared link model, and is not applicable for point-to-point link model without modification.
    So,  there are some basic conflicts in the draft.

    Formulation of  a prospective NCoA  is a main idea of  RFC4068.
    But in Point-to-Point link model, it is impossible to formulate the NCoA
    according to  RFC4068 because there is no proper prefix.


    BR
    Frank


    ----- Original Message -----
    From: "Daniel Park" <soohong.park@samsung.com>
    To: <mipshop@ietf.org>
    Cc: <16ng@ietf.org>
    Sent: Sunday, May 27, 2007 9:34 PM
    Subject: [16NG] FW: Call for Review on FMIP6 over IEEE 802.16e Networks


    > To MIPSHOP WG,
    >
    > Here is another expert review on "draft-ietf-mipshop-fh80216e-01",
    > particularly, IEEE 802.21 relevant texts in this draft.
    >
    > Reviewer (Yoshihiro Ohba) is a IETF official liaison from IEEE 802.21
    >
    > Thanks Yoshihiro and hope this helps...
    >
    >
    > ----
    >
    > Daniel Park & Gabriel Montenegro
    > Chairs, 16NG Working Group
    >


    --------------------------------------------------------------------------------


    > _______________________________________________
    > 16NG mailing list
    > 16NG@ietf.org
    > https://www1.ietf.org/mailman/listinfo/16ng
    >

    _______________________________________________
    Mipshop mailing list
    Mipshop@ietf.org
    https://www1.ietf.org/mailman/listinfo/mipshop






  -- 
  http://people.nokia.net/~rajeev 



--Boundary_(ID_+lDK8UrmwiFQbMIPdTBiRA)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPjxUSVRMRT5SZTogW01pcHNob3BdIFJlOiBbMTZOR10gRlc6IENh
bGwgZm9yIFJldmlldyBvbiBGTUlQNiBvdmVyIElFRUU4MDIuMTZlIE5ldHdvcmtzPC9USVRMRT4N
CjxNRVRBIGh0dHAtZXF1aXY9Q29udGVudC1UeXBlIGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNl
dD1pc28tODg1OS0xIj4NCjxNRVRBIGNvbnRlbnQ9Ik1TSFRNTCA2LjAwLjI4MDAuMTU2MSIgbmFt
ZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9TVFlMRT4NCjwvSEVBRD4NCjxCT0RZIGJnQ29sb3I9I2Zm
ZmZmZj4NCjxESVY+PEZPTlQgZmFjZT0mIzIzNDM1OyYjMjAzMDc7IHNpemU9Mj5IaSBSYWplZXYg
PC9GT05UPjxGT05UIGZhY2U9JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+PC9GT05UPjwvRElWPg0K
PERJVj48Rk9OVCBmYWNlPSYjMjM0MzU7JiMyMDMwNzsgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJ
Vj4NCjxESVY+PEZPTlQgZmFjZT0mIzIzNDM1OyYjMjAzMDc7IHNpemU9Mj5JIGp1c3QgcGlja2Vk
IHNvbWUgdGV4dHMgZnJvbSA0MDY4YmlzLjwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT0m
IzIzNDM1OyYjMjAzMDc7IHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZh
Y2U9JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+Q291bGQgeW91IG1ha2UgaXQgY2xlYXIgd2hlbiZu
YnNwO3doZW4gUC10by1QIGxpbmsgaXMgDQphcHBsaWVkPzwvRk9OVD48L0RJVj4NCjxESVY+PEZP
TlQgZmFjZT0mIzIzNDM1OyYjMjAzMDc7IHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElW
PjxGT05UIGZhY2U9JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0K
PERJVj48Rk9OVCBmYWNlPSYjMjM0MzU7JiMyMDMwNzsgc2l6ZT0yPjEgIihBUC1JRCwgQVItSW5m
bykgdHVwbGUgQ29udGFpbnMgYW4gYWNjZXNzIHJvdXRlcidzIA0KTDIgYW5kIElQIGFkZHJlc3Nl
cywgYW5kPEJSPiZuYnNwOyBwcmVmaXggdmFsaWQgb24gdGhlIGludGVyZmFjZSB0byB3aGljaCB0
aGUgDQpBY2Nlc3MgUG9pbnQgKGlkZW50aWZpZWQgYnkgQVAtSUQpIGlzIGF0dGFjaGVkLiZuYnNw
OyA8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+
Jm5ic3A7VGhlIHRyaXBsZXQgW1JvdXRlcidzJm5ic3A7IEwyIGFkZHJlc3MsIFJvdXRlcidzIA0K
SVAgYWRkcmVzcyBhbmQgUHJlZml4XSBpcyBjYWxsZWQgIkFSLUluZm8iIi48L0ZPTlQ+PC9ESVY+
DQo8RElWPjxGT05UIGZhY2U9JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+PC9GT05UPiZuYnNwOzwv
RElWPg0KPERJVj48Rk9OVCBmYWNlPSYjMjM0MzU7JiMyMDMwNzsgc2l6ZT0yPj0mZ3Q7IEhlcmUs
IHByZWZpeCBpcyBBUidzIHBoeXNpY2FsIGludGVyZmFjZSBwcmVmaXggDQppcyB1c2VkIGZvciBO
Q29BIGZvcm11bGF0aW9uLjwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT0mIzIzNDM1OyYj
MjAzMDc7IHNpemU9Mj4mbmJzcDsgQXMgeW91IGtub3csIHRoaXMgcHJlZml4IGlzIHVzZWxlc3Mg
Zm9yIFAtdG8tUCANCmxpbmsgbW9kZWwuPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPSYj
MjM0MzU7JiMyMDMwNzsgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFj
ZT0mIzIzNDM1OyYjMjAzMDc7IHNpemU9Mj4yICImbmJzcDtUaHJvdWdoIHRoZSBSdFNvbFByIGFu
ZCBQclJ0QWR2IG1lc3NhZ2VzLCB0aGUgDQpNTiBhbHNvIGZvcm11bGF0ZXMgYTxCUj4mbmJzcDsm
bmJzcDsmbmJzcDsgcHJvc3BlY3RpdmUgbmV3IENvQSAoTkNvQSksIHdoZW4gaXQgDQppcyBzdGls
bCBwcmVzZW50IG9uIHRoZSBQQVInczxCUj4mbmJzcDsmbmJzcDsmbmJzcDsgbGluay4mbmJzcDsg
SGVuY2UsIHRoZSANCmxhdGVuY3kgZHVlIHRvIG5ldyBwcmVmaXggZGlzY292ZXJ5IHN1YnNlcXVl
bnQgdG88QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IGhhbmRvdmVyIA0KaXMgZWxpbWluYXRlZC4mbmJz
cDsgRnVydGhlcm1vcmUsIHRoaXMgcHJvc3BlY3RpdmUgYWRkcmVzcyANCmNhbjxCUj4mbmJzcDsm
bmJzcDsmbmJzcDsgYmUgdXNlZCBpbW1lZGlhdGVseSBhZnRlciBhdHRhY2hpbmcgdG8gdGhlIG5l
dyBzdWJuZXQgDQpsaW5rIChpLmUuLDxCUj4mbmJzcDsmbmJzcDsmbmJzcDsgTkFSJ3MgbGluaykg
d2hlbiB0aGUgTU4gaGFzIHJlY2VpdmVkIGEgIkZhc3QgDQpCaW5kaW5nIEFja25vd2xlZGdtZW50
PEJSPiZuYnNwOyZuYnNwOyZuYnNwOyAoRkJhY2spIiBtZXNzYWdlIHByaW9yIHRvIGl0cyANCm1v
dmVtZW50LiZuYnNwOyBJbiB0aGUgZXZlbnQgaXQgbW92ZXM8QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7
IHdpdGhvdXQgcmVjZWl2aW5nIGFuIA0KRkJhY2ssIHRoZSBNTiBjYW4gc3RpbGwgc3RhcnQgdXNp
bmcgTkNvQTxCUj4mbmJzcDsmbmJzcDsmbmJzcDsgYWZ0ZXIgYW5ub3VuY2luZyANCml0cyBhdHRh
Y2htZW50IHRocm91Z2ggYW4gdW5zb2xpY2l0ZWQgTmVpZ2hib3I8QlI+Jm5ic3A7Jm5ic3A7Jm5i
c3A7IA0KQWR2ZXJ0aXNlbWVudCBtZXNzYWdlICh3aXRoIHRoZSAnTycgYml0IHNldCB0byB6ZXJv
KSBtZXNzYWdlIA0KWzhdOzxCUj4mbmJzcDsmbmJzcDsmbmJzcDsgTkFSIHJlc3BvbmRzIHRvIHRv
IHRoaXMgVU5BIG1lc3NhZ2UgaW4gY2FzZSB0aGUgDQp0ZW50YXRpdmUgYWRkcmVzcyBpczxCUj4m
bmJzcDsmbmJzcDsmbmJzcDsgYWxyZWFkeSBpbiB1c2UuJm5ic3A7IEluIHRoaXMgd2F5LCANCk5D
b0EgY29uZmlndXJhdGlvbiBsYXRlbmN5IGlzIHJlZHVjZWQiPC9GT05UPjwvRElWPg0KPERJVj48
Rk9OVCBmYWNlPSYjMjM0MzU7JiMyMDMwNzsgc2l6ZT0yPj0mZ3Q7aXMgaXQmbmJzcDttZWFuaW5n
ZnVsIA0KZm9yJm5ic3A7UC10by1QPzwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT0mIzIz
NDM1OyYjMjAzMDc7IHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9
JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+Li4uPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNl
PSYjMjM0MzU7JiMyMDMwNzsgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQg
ZmFjZT0mIzIzNDM1OyYjMjAzMDc7IHNpemU9Mj5JbiBmYWN0IGFueSBwYXJ0cyByZWxhdGVkIHRv
IHRoZSBwcmVmaXggaXMgbm90IHByb3BlciANCmZvciZuYnNwO3AtdG8tcCBsaW5rIG1vZGVsLjwv
Rk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT0mIzIzNDM1OyYjMjAzMDc7IHNpemU9Mj48L0ZP
TlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+
PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPSYjMjM0MzU7JiMyMDMwNzsgc2l6
ZT0yPkJUVywgRnJvbSBteSB1bmRlcnN0YW5kaW5nLCB5b3VyIHByb3BzYWwgaXMgdGhhdCB0aGUg
DQpvbmx5IHdheSBmb3IgTU4gZ2V0dGluZyBpdCdzIENvQTwvRk9OVD48L0RJVj4NCjxESVY+PEZP
TlQgZmFjZT0mIzIzNDM1OyYjMjAzMDc7IHNpemU9Mj5NVVNUIGJlIHJlcXVlc3RpbmcgaXQgZnJv
bSBOQVIgZm9yIFAtdG8tUCANCmxpbmsuPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPSYj
MjM0MzU7JiMyMDMwNzsgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFj
ZT0mIzIzNDM1OyYjMjAzMDc7IHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05U
IGZhY2U9JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48
Rk9OVCBmYWNlPSYjMjM0MzU7JiMyMDMwNzsgc2l6ZT0yPkJSPC9GT05UPjwvRElWPg0KPERJVj48
Rk9OVCBmYWNlPSYjMjM0MzU7JiMyMDMwNzsgc2l6ZT0yPkZyYW5rPC9GT05UPjwvRElWPg0KPERJ
Vj48Rk9OVCBmYWNlPSYjMjM0MzU7JiMyMDMwNzsgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4N
CjxESVY+PEZPTlQgZmFjZT0mIzIzNDM1OyYjMjAzMDc7IHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9E
SVY+DQo8RElWPjxGT05UIGZhY2U9JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+PC9GT05UPiZuYnNw
OzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPSYjMjM0MzU7JiMyMDMwNzsgc2l6ZT0yPjwvRk9OVD4m
bmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT0mIzIzNDM1OyYjMjAzMDc7IHNpemU9Mj48L0ZP
TlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+
PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPSYjMjM0MzU7JiMyMDMwNzsgc2l6
ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT0mIzIzNDM1OyYjMjAzMDc7
IHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9JiMyMzQzNTsmIzIw
MzA3OyBzaXplPTI+Jm5ic3A7PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPSYjMjM0MzU7
JiMyMDMwNzsgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT0mIzIz
NDM1OyYjMjAzMDc7IHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9
JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPEJMT0NLUVVPVEUg
DQpzdHlsZT0iUEFERElORy1SSUdIVDogMHB4OyBQQURESU5HLUxFRlQ6IDVweDsgTUFSR0lOLUxF
RlQ6IDVweDsgQk9SREVSLUxFRlQ6ICMwMDAwMDAgMnB4IHNvbGlkOyBNQVJHSU4tUklHSFQ6IDBw
eCI+DQogIDxESVYgc3R5bGU9IkZPTlQ6IDlwdCAmIzIzNDM1OyYjMjAzMDc7Ij4tLS0tLSBPcmln
aW5hbCBNZXNzYWdlIC0tLS0tIDwvRElWPg0KICA8RElWIHN0eWxlPSJCQUNLR1JPVU5EOiAjZTRl
NGU0OyBGT05UOiA5cHQgJiMyMzQzNTsmIzIwMzA3OzsgZm9udC1jb2xvcjogYmxhY2siPjxCPkZy
b206PC9CPiANCiAgPEEgdGl0bGU9cmFqZWV2Lmtvb2RsaUBub2tpYS5jb20gaHJlZj0ibWFpbHRv
OnJhamVldi5rb29kbGlAbm9raWEuY29tIj5SYWplZXYgDQogIEtvb2RsaTwvQT4gPC9ESVY+DQog
IDxESVYgc3R5bGU9IkZPTlQ6IDlwdCAmIzIzNDM1OyYjMjAzMDc7Ij48Qj5Ubzo8L0I+IDxBIHRp
dGxlPWhlZWppbi5qYW5nQHNhbXN1bmcuY29tIA0KICBocmVmPSJtYWlsdG86aGVlamluLmphbmdA
c2Ftc3VuZy5jb20iPmhlZWppbi5qYW5nQHNhbXN1bmcuY29tPC9BPiA7IDxBIA0KICB0aXRsZT14
aWF5YW5nc29uZ0BodWF3ZWkuY29tIGhyZWY9Im1haWx0bzp4aWF5YW5nc29uZ0BodWF3ZWkuY29t
Ij5GcmFuayANCiAgWGlhPC9BPiA8L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVDogOXB0ICYjMjM0
MzU7JiMyMDMwNzsiPjxCPkNjOjwvQj4gPEEgdGl0bGU9bWlwc2hvcEBpZXRmLm9yZyANCiAgaHJl
Zj0ibWFpbHRvOm1pcHNob3BAaWV0Zi5vcmciPm1pcHNob3BAaWV0Zi5vcmc8L0E+IDsgPEEgdGl0
bGU9MTZuZ0BpZXRmLm9yZyANCiAgaHJlZj0ibWFpbHRvOjE2bmdAaWV0Zi5vcmciPjE2bmdAaWV0
Zi5vcmc8L0E+IDsgPEEgDQogIHRpdGxlPXNvb2hvbmcucGFya0BzYW1zdW5nLmNvbSBocmVmPSJt
YWlsdG86c29vaG9uZy5wYXJrQHNhbXN1bmcuY29tIj4/Pz88L0E+IA0KICA8L0RJVj4NCiAgPERJ
ViBzdHlsZT0iRk9OVDogOXB0ICYjMjM0MzU7JiMyMDMwNzsiPjxCPlNlbnQ6PC9CPiBNb25kYXks
IEp1bmUgMDQsIDIwMDcgMTI6NTYgUE08L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVDogOXB0ICYj
MjM0MzU7JiMyMDMwNzsiPjxCPlN1YmplY3Q6PC9CPiBSZTogW01pcHNob3BdIFJlOiBbMTZOR10g
Rlc6IENhbGwgDQogIGZvciBSZXZpZXcgb24gRk1JUDYgb3ZlciBJRUVFODAyLjE2ZSBOZXR3b3Jr
czwvRElWPg0KICA8RElWPjxCUj48L0RJVj48Rk9OVCBmYWNlPSJWZXJkYW5hLCBIZWx2ZXRpY2Es
IEFyaWFsIj48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTJweCI+PEJSPkFzIGZhciBhcyBJ
IHNlZSwgdGhlcmUgaXMgbm8gcHJvYmxlbSANCiAgaGVyZSE8QlI+PEJSPkl0IGRvZXMgbm90IG1h
dHRlciB3aGF0IHlvdSBjYWxsIHRoZSBwcmVmaXggYWR2ZXJ0aXNlZCBpbiANCiAgUHJSdEFkdi4g
UkZDIDQwNjggZG9lcyBub3QgbWFrZSBhc3N1bXB0aW9ucyBhYm91dCBob3cgdGhlIHByZWZpeGVz
IGFyZSANCiAgYXNzaWduZWQgYW5kIG1hbmFnZWQgb24gYW4gQVKScyBsaW5rLiBTbywgaXQgaXMg
aW5hY2N1cmF0ZSB0byBzYXkgYXMgc3VjaCBpbiANCiAgZHJhZnQteGlhLW1pcHNob3AtZm1pcC1w
dHAtMDAudHh0LiA8QlI+PEJSPlNvLCBpZiBwcmVmaXggQSBpcyBhZHZlcnRpc2VkIGluIA0KICBQ
clJ0QWR2LCBhbmQgYSBNTiBmb3JtdWxhdGVzIGEgcHJvc3BlY3RpdmUgYWRkcmVzcyBJUC1BIGFu
ZCBzZW5kcyBGQlUsIElQLUEgDQogIGNhbiBiZSBvdmVycmlkZGVuIGJ5IE5BUiBpbiBIQWNrLjxC
Uj48QlI+U2VjdGlvbiANCiAgNi4yLjI8QlI+PEJSPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
O0NvZGUgDQogICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzM6IEhh
bmRvdmVyIEFjY2VwdGVkLCBOQ29BIA0KICBhc3NpZ25lZDxCUj4mbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsodXNlZCANCiAgaW4gQXNz
aWduZWQgYWRkcmVzc2luZyk8QlI+PEJSPjxCUj5UaGUgc3VwcGxpZWQgTkNvQSBpcyBwcm92aWRl
ZCBpbiBGQmFjayBvciANCiAgTkFBQ0sgb3B0aW9uLjxCUj48QlI+VGhpcyBpcyB0aGUgd2F5IEkg
dW5kZXJzdG9vZCB0aGUgcHJvYmxlbSBhbmQgdGhlIHNvbHV0aW9uIA0KICBmb3IgcHRwIGxpbmtz
LjxCUj48QlI+V2hhdCBhbSBJIG1pc3Npbmc/PEJSPjxCUj4tUmFqZWV2PEJSPjxCUj48QlI+PEJS
PjxCUj5PbiANCiAgNi8zLzA3IDk6NDQgUE0sICJleHQgSGVlamluIEphbmciICZsdDtoZWVqaW4u
amFuZ0BzYW1zdW5nLmNvbSZndDsgDQogIHdyb3RlOjxCUj48QlI+PC9TUEFOPjwvRk9OVD4NCiAg
PEJMT0NLUVVPVEU+PEZPTlQgZmFjZT0iVmVyZGFuYSwgSGVsdmV0aWNhLCBBcmlhbCI+PFNQQU4g
DQogICAgc3R5bGU9IkZPTlQtU0laRTogMTJweCI+SGksIEZyYW5rICZhbXA7IERhbmllbC48QlI+
PEJSPlJGQzQwNjggZGVzY3JpYmVzIA0KICAgIGZhc3QgSE8gcHJvY2VkdXJlIGJhc2VkIG9uIHBy
ZWRpY3Rpb24sIGluY2x1ZGluZyBOQ29BIGZvcm11bGF0aW9uIGluIA0KICAgIGFkdmFuY2UuPEJS
Pkhvd2V2ZXIsIGhvdyB0byBhbGxvY2F0ZSB0aGUgcHJlZml4IHRvIE1OIGluIE5BUiAoYmVmb3Jl
IGFjdHVhbCANCiAgICBITykgaXMgb3V0IG9mIHNjb3BlIGluIHRoaXMgZG9jdW1lbnQ8QlI+YXMg
bWVudGlvbmVkIGluIFNlY3Rpb24gDQogICAgNC48QlI+PEJSPiJUaGUgbWV0aG9kIGJ5IHdoaWNo
IEFjY2VzcyBSb3V0ZXJzIGV4Y2hhbmdlIGluZm9ybWF0aW9uIGFib3V0IA0KICAgIHRoZWlyIG5l
aWdoYm9ycywgYW5kIHRoZXJlYnkgYWxsb3c8QlI+Jm5ic3A7Jm5ic3A7Y29uc3RydWN0aW9uIG9m
IFByb3h5IA0KICAgIFJvdXRlciAmbmJzcDtBZHZlcnRpc2VtZW50cyB3aXRoIGluZm9ybWF0aW9u
IGFib3V0IG5laWdoYm9yaW5nIHN1Ym5ldHMgaXMgDQogICAgb3V0c2lkZTxCUj4mbmJzcDsmbmJz
cDt0aGUgc2NvcGUgb2YgdGhpcyBkb2N1bWVudC4iPEJSPjxCUj5GdXJ0aGVybW9yZSwgdGhlIA0K
ICAgIHByb2JsZW0geW91IG1lbnRpb25lZCBpbiBkcmFmdC14aWEtbWlwc2hvcC1mbWlwLXB0cC0w
MCBpcyBub3QgbGltaXRlZCBvbmx5IA0KICAgIHRvIDgwMi4xNiBuZXR3b3JrczxCUj5idXQgaGFw
cGVucyBhbGwgbmV0d29ya3Mgd2hpY2ggaGF2ZSBwb2ludC10by1wb2ludCANCiAgICBsaW5rIHN1
Y2ggYXMgM0dQUDIuPEJSPkkgdGhpbmsgdGhhdCBpdCBpcyBwcm9wZXIgdG8gaGFuZGxlIHRoaXMg
cHJvYmxlbSANCiAgICBzZXBhcmF0ZWx5LjxCUj48QlI+VGhhbmtzIGZvciB5b3VyIG9waW5pb24u
PEJSPjxCUj4tIA0KICAgIFJlZ2FyZHMsPEJSPkhlZWppbjxCUj48QlI+LS0tLS0tLSBPcmlnaW5h
bCBNZXNzYWdlIC0tLS0tLS08QlI+U2VuZGVyIDogRnJhbmsgDQogICAgWGlhJmx0O3hpYXlhbmdz
b25nQGh1YXdlaS5jb20mZ3Q7PEJSPkRhdGUgJm5ic3A7Jm5ic3A7OiAyMDA3LTA2LTAxIA0KICAg
IDA2OjUwPEJSPlRpdGxlICZuYnNwOzogW01pcHNob3BdIFJlOiBbMTZOR10gRlc6IENhbGwgZm9y
IFJldmlldyBvbiBGTUlQNiANCiAgICBvdmVyIElFRUUgODAyLjE2ZSAmbmJzcDsmbmJzcDsmbmJz
cDtOZXR3b3JrczxCUj48QlI+SGkgRGFuaWVsPEJSPjxCUj5IZXJlIGlzIA0KICAgIG15IHR3byBj
ZW50cy48QlI+PEJSPlRoZSBkcmFmdCBpcyBiYXNlZCBvbiBSRkM0MDY4LCBhbmQgcG9pbnQtdG8t
cG9pbnQgbGluayANCiAgICBtb2RlbCBpcyBhbHNvIHJlY29tbWVuZGVkIC48QlI+UkZDNDA2OCBp
cyBiYXNlZCBvbiBzaGFyZWQgbGluayBtb2RlbCwgYW5kIGlzIA0KICAgIG5vdCBhcHBsaWNhYmxl
IGZvciBwb2ludC10by1wb2ludCBsaW5rIG1vZGVsIHdpdGhvdXQgbW9kaWZpY2F0aW9uLjxCUj5T
bywgDQogICAgJm5ic3A7dGhlcmUgYXJlIHNvbWUgYmFzaWMgY29uZmxpY3RzIGluIHRoZSBkcmFm
dC48QlI+PEJSPkZvcm11bGF0aW9uIG9mIA0KICAgICZuYnNwO2EgcHJvc3BlY3RpdmUgTkNvQSAm
bmJzcDtpcyBhIG1haW4gaWRlYSBvZiAmbmJzcDtSRkM0MDY4LjxCUj5CdXQgaW4gDQogICAgUG9p
bnQtdG8tUG9pbnQgbGluayBtb2RlbCwgaXQgaXMgaW1wb3NzaWJsZSB0byBmb3JtdWxhdGUgdGhl
IA0KICAgIE5Db0E8QlI+YWNjb3JkaW5nIHRvICZuYnNwO1JGQzQwNjggYmVjYXVzZSB0aGVyZSBp
cyBubyBwcm9wZXIgDQogICAgcHJlZml4LjxCUj48QlI+PEJSPkJSPEJSPkZyYW5rPEJSPjxCUj48
QlI+LS0tLS0gT3JpZ2luYWwgTWVzc2FnZSANCiAgICAtLS0tLTxCUj5Gcm9tOiAiRGFuaWVsIFBh
cmsiICZsdDtzb29ob25nLnBhcmtAc2Ftc3VuZy5jb20mZ3Q7PEJSPlRvOiANCiAgICAmbHQ7bWlw
c2hvcEBpZXRmLm9yZyZndDs8QlI+Q2M6ICZsdDsxNm5nQGlldGYub3JnJmd0OzxCUj5TZW50OiBT
dW5kYXksIE1heSANCiAgICAyNywgMjAwNyA5OjM0IFBNPEJSPlN1YmplY3Q6IFsxNk5HXSBGVzog
Q2FsbCBmb3IgUmV2aWV3IG9uIEZNSVA2IG92ZXIgSUVFRSANCiAgICA4MDIuMTZlIE5ldHdvcmtz
PEJSPjxCUj48QlI+Jmd0OyBUbyBNSVBTSE9QIFdHLDxCUj4mZ3Q7PEJSPiZndDsgSGVyZSBpcyAN
CiAgICBhbm90aGVyIGV4cGVydCByZXZpZXcgb24gImRyYWZ0LWlldGYtbWlwc2hvcC1maDgwMjE2
ZS0wMSIsPEJSPiZndDsgDQogICAgcGFydGljdWxhcmx5LCBJRUVFIDgwMi4yMSByZWxldmFudCB0
ZXh0cyBpbiB0aGlzIGRyYWZ0LjxCUj4mZ3Q7PEJSPiZndDsgDQogICAgUmV2aWV3ZXIgKFlvc2hp
aGlybyBPaGJhKSBpcyBhIElFVEYgb2ZmaWNpYWwgbGlhaXNvbiBmcm9tIElFRUUgDQogICAgODAy
LjIxPEJSPiZndDs8QlI+Jmd0OyBUaGFua3MgWW9zaGloaXJvIGFuZCBob3BlIHRoaXMgDQogICAg
aGVscHMuLi48QlI+Jmd0OzxCUj4mZ3Q7PEJSPiZndDsgLS0tLTxCUj4mZ3Q7PEJSPiZndDsgRGFu
aWVsIFBhcmsgJmFtcDsgDQogICAgR2FicmllbCBNb250ZW5lZ3JvPEJSPiZndDsgQ2hhaXJzLCAx
Nk5HIFdvcmtpbmcgDQogICAgR3JvdXA8QlI+Jmd0OzxCUj48QlI+PEJSPi0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tPEJSPjxCUj48QlI+Jmd0OyANCiAgICBfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXzxCUj4mZ3Q7IDE2TkcgbWFpbGluZyANCiAgICBsaXN0PEJS
PiZndDsgMTZOR0BpZXRmLm9yZzxCUj4mZ3Q7IA0KICAgIGh0dHBzOi8vd3d3MS5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvLzE2bmc8QlI+Jmd0OzxCUj48QlI+X19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX188QlI+TWlwc2hvcCANCiAgICBtYWlsaW5nIA0KICAg
IGxpc3Q8QlI+TWlwc2hvcEBpZXRmLm9yZzxCUj5odHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9taXBzaG9wPEJSPjxCUj48QlI+PEJSPjwvU1BBTj48L0ZPTlQ+PC9CTE9DS1FV
T1RFPjxGT05UIA0KICBmYWNlPSJWZXJkYW5hLCBIZWx2ZXRpY2EsIEFyaWFsIj48U1BBTiBzdHls
ZT0iRk9OVC1TSVpFOiAxMnB4Ij48QlI+PEJSPi0tIA0KICA8QlI+PEEgDQogIGhyZWY9Imh0dHA6
Ly9wZW9wbGUubm9raWEubmV0L35yYWplZXYiPmh0dHA6Ly9wZW9wbGUubm9raWEubmV0L35yYWpl
ZXY8L0E+IA0KICA8QlI+PEJSPjxCUj48L0JMT0NLUVVPVEU+PC9TUEFOPjwvRk9OVD48L0JPRFk+
PC9IVE1MPg0K

--Boundary_(ID_+lDK8UrmwiFQbMIPdTBiRA)--



--===============0533060900==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng

--===============0533060900==--





From 16ng-bounces@ietf.org Mon Jun 04 15:04:44 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvHrA-00016h-Dq; Mon, 04 Jun 2007 15:04:44 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1HvHr8-00016P-Lt
	for 16ng-confirm+ok@megatron.ietf.org; Mon, 04 Jun 2007 15:04:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvHr8-00016C-BC
	for 16ng@ietf.org; Mon, 04 Jun 2007 15:04:42 -0400
Received: from web84111.mail.mud.yahoo.com ([68.142.206.198])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HvHr6-0004vv-40
	for 16ng@ietf.org; Mon, 04 Jun 2007 15:04:42 -0400
Received: (qmail 47026 invoked by uid 60001); 4 Jun 2007 19:04:37 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID;
	b=ZS8puC17bI9FJJ4AjnVM2cm4PlAGe4qw+vFv2TVnY4iUXHBKlQ6e9rLPzKjRdd7MkmIwmduy1hlIj4sYeQvgZ5GU/UR1g8iXJfR1uQSMvjCWwfj5uS7dzqfvvtIniH5U7gXXdG3UmTHC46IVz53eTA/vObQ4jHB9LgRW7lSibUI=;
X-YMail-OSG: k85QERAVM1kAiZ_Vd3WFvDVEUTDMK9fVY.9TEpDhXsE8xdblX4x3Sq7CJ1pA8Op13DGaTM03Lw--
Received: from [206.16.17.212] by web84111.mail.mud.yahoo.com via HTTP;
	Mon, 04 Jun 2007 12:04:37 PDT
X-Mailer: YahooMailRC/651.23.1 YahooMailWebService/0.7.41.14
Date: Mon, 4 Jun 2007 12:04:37 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over
	IEEE802.16e Networks
To: Rajeev Koodli <rajeev.koodli@nokia.com>
MIME-Version: 1.0
Message-ID: <534356.46196.qm@web84111.mail.mud.yahoo.com>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Cc: mipshop@ietf.org, 16ng@ietf.org
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0365081966=="
Errors-To: 16ng-bounces@ietf.org

--===============0365081966==
Content-Type: multipart/alternative; boundary="0-138758543-1180983877=:46196"

--0-138758543-1180983877=:46196
Content-Type: text/plain; charset=iso-8859-7
Content-Transfer-Encoding: quoted-printable

Hi Rajeev,=0A  Please kindly see inline.=0A=0A--behcet=0A=0A----- Original =
Message ----=0AFrom: Rajeev Koodli <rajeev.koodli@nokia.com>=0ATo: heejin.j=
ang@samsung.com; Frank Xia <xiayangsong@huawei.com>=0ACc: mipshop@ietf.org;=
 16ng@ietf.org; ??? <soohong.park@samsung.com>=0ASent: Monday, June 4, 2007=
 12:56:46 PM=0ASubject: Re: [Mipshop] Re: [16NG] FW: Call for Review on FMI=
P6 over IEEE802.16e Networks=0A=0ARe: [Mipshop] Re: [16NG] FW: Call for Rev=
iew on FMIP6 over IEEE802.16e Networks=0A=0A=0A=0A=0A=0AAs far as I see, th=
ere is no problem here!=0A=0A=0A=0AIt does not matter what you call the pre=
fix advertised in PrRtAdv. RFC 4068 does not make assumptions about how the=
 prefixes are assigned and managed on an AR=A2s link. So, it is inaccurate =
to say as such in draft-xia-mipshop-fmip-ptp-00.txt. =0A=0A=0A=0ASo, if pre=
fix A is advertised in PrRtAdv, and a MN formulates a prospective address I=
P-A and sends FBU, IP-A can be overridden by NAR in HAck.=0A=0A=0A=0ASectio=
n 6.2.2=0A=0A=0A=0A              Code        3: Handover Accepted, NCoA ass=
igned=0A=0A                             (used in Assigned addressing)=0A=0A=
=0A=0A=0A=0AThe supplied NCoA is provided in FBack or NAACK option.=0A=0A=
=0A=0AThis is the way I understood the problem and the solution for ptp lin=
ks.=0A=0A=0A=0AWhat am I missing?=0A=0A=0A[behcet] Hi/Hack exchange is used=
 in predictive mode, not used in reactive mode. =0AEven for the predictive =
mode with Code 3, some changes are needed in the current text.=0A=0A=0A=0A-=
Rajeev=0A=0A=0A=0A=0A=0A=0A=0A=0A=0AOn 6/3/07 9:44 PM, "ext Heejin Jang" <h=
eejin.jang@samsung.com> wrote:=0A=0A=0A=0AHi, Frank & Daniel.=0A=0A=0A=0ARF=
C4068 describes fast HO procedure based on prediction, including NCoA formu=
lation in advance.=0A=0AHowever, how to allocate the prefix to MN in NAR (b=
efore actual HO) is out of scope in this document=0A=0Aas mentioned in Sect=
ion 4.=0A=0A=0A=0A"The method by which Access Routers exchange information =
about their neighbors, and thereby allow=0A=0A  construction of Proxy Route=
r  Advertisements with information about neighboring subnets is outside=0A=
=0A  the scope of this document."=0A=0A=0A=0AFurthermore, the problem you m=
entioned in draft-xia-mipshop-fmip-ptp-00 is not limited only to 802.16 net=
works=0A=0Abut happens all networks which have point-to-point link such as =
3GPP2.=0A=0AI think that it is proper to handle this problem separately.=0A=
=0A=0A=0AThanks for your opinion.=0A=0A=0A=0A- Regards,=0A=0AHeejin=0A=0A=
=0A=0A------- Original Message -------=0A=0ASender : Frank Xia<xiayangsong@=
huawei.com>=0A=0ADate   : 2007-06-01 06:50=0A=0ATitle  : [Mipshop] Re: [16N=
G] FW: Call for Review on FMIP6 over IEEE 802.16e    Networks=0A=0A=0A=0AHi=
 Daniel=0A=0A=0A=0AHere is my two cents.=0A=0A=0A=0AThe draft is based on R=
FC4068, and point-to-point link model is also recommended .=0A=0ARFC4068 is=
 based on shared link model, and is not applicable for point-to-point link =
model without modification.=0A=0ASo,  there are some basic conflicts in the=
 draft.=0A=0A=0A=0AFormulation of  a prospective NCoA  is a main idea of  R=
FC4068.=0A=0ABut in Point-to-Point link model, it is impossible to formulat=
e the NCoA=0A=0Aaccording to  RFC4068 because there is no proper prefix.=0A=
=0A=0A=0A=0A=0ABR=0A=0AFrank=0A=0A=0A=0A=0A=0A
--0-138758543-1180983877=:46196
Content-Type: text/html; charset=iso-8859-7
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:times new roman,new york,times,serif;fon=
t-size:14pt"><div style=3D"font-family: times new roman,new york,times,seri=
f; font-size: 14pt;">Hi Rajeev,<br>&nbsp; Please kindly see inline.<br><br>=
--behcet<br><br><div style=3D"font-family: times new roman,new york,times,s=
erif; font-size: 12pt;">----- Original Message ----<br>From: Rajeev Koodli =
&lt;rajeev.koodli@nokia.com&gt;<br>To: heejin.jang@samsung.com; Frank Xia &=
lt;xiayangsong@huawei.com&gt;<br>Cc: mipshop@ietf.org; 16ng@ietf.org; ??? &=
lt;soohong.park@samsung.com&gt;<br>Sent: Monday, June 4, 2007 12:56:46 PM<b=
r>Subject: Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE8=
02.16e Networks<br><br><title>Re: [Mipshop] Re: [16NG] FW: Call for Review =
on FMIP6 over IEEE802.16e Networks</title>=0A=0A=0A=0A<font face=3D"Verdana=
, Helvetica, Arial"><span style=3D"font-size: 12px;"><br>=0AAs far as I see=
, there is no problem here!<br>=0A<br>=0AIt does not matter what you call t=
he prefix advertised in PrRtAdv. RFC 4068 does not make assumptions about h=
ow the prefixes are assigned and managed on an AR=A2s link. So, it is inacc=
urate to say as such in draft-xia-mipshop-fmip-ptp-00.txt. <br>=0A<br>=0ASo=
, if prefix A is advertised in PrRtAdv, and a MN formulates a prospective a=
ddress IP-A and sends FBU, IP-A can be overridden by NAR in HAck.<br>=0A<br=
>=0ASection 6.2.2<br>=0A<br>=0A&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Code &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;3: Handover Accepted, NCoA assigned<br>=0A&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;(used in Assigned addressing)<br>=0A<br>=0A<br>=0AThe supplied NCoA is p=
rovided in FBack or NAACK option.<br>=0A<br>=0AThis is the way I understood=
 the problem and the solution for ptp links.<br>=0A<br>=0AWhat am I missing=
?<br>=0A<br><font style=3D"font-family: times new roman,new york,times,seri=
f;" size=3D"5">[behcet] Hi/Hack exchange is used in predictive mode, not us=
ed in reactive mode. <br>Even for the predictive mode with Code 3, some cha=
nges are needed in the current text.</font><br><br><br>=0A-Rajeev<br>=0A<br=
>=0A<br>=0A<br>=0A<br>=0AOn 6/3/07 9:44 PM, "ext Heejin Jang" &lt;heejin.ja=
ng@samsung.com&gt; wrote:<br>=0A<br>=0A</span></font><blockquote><font face=
=3D"Verdana, Helvetica, Arial"><span style=3D"font-size: 12px;">Hi, Frank &=
amp; Daniel.<br>=0A<br>=0ARFC4068 describes fast HO procedure based on pred=
iction, including NCoA formulation in advance.<br>=0AHowever, how to alloca=
te the prefix to MN in NAR (before actual HO) is out of scope in this docum=
ent<br>=0Aas mentioned in Section 4.<br>=0A<br>=0A"The method by which Acce=
ss Routers exchange information about their neighbors, and thereby allow<br=
>=0A&nbsp;&nbsp;construction of Proxy Router &nbsp;Advertisements with info=
rmation about neighboring subnets is outside<br>=0A&nbsp;&nbsp;the scope of=
 this document."<br>=0A<br>=0AFurthermore, the problem you mentioned in dra=
ft-xia-mipshop-fmip-ptp-00 is not limited only to 802.16 networks<br>=0Abut=
 happens all networks which have point-to-point link such as 3GPP2.<br>=0AI=
 think that it is proper to handle this problem separately.<br>=0A<br>=0ATh=
anks for your opinion.<br>=0A<br>=0A- Regards,<br>=0AHeejin<br>=0A<br>=0A--=
----- Original Message -------<br>=0ASender : Frank Xia&lt;xiayangsong@huaw=
ei.com&gt;<br>=0ADate &nbsp;&nbsp;: 2007-06-01 06:50<br>=0ATitle &nbsp;: [M=
ipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE 802.16e &nbsp;&nb=
sp;&nbsp;Networks<br>=0A<br>=0AHi Daniel<br>=0A<br>=0AHere is my two cents.=
<br>=0A<br>=0AThe draft is based on RFC4068, and point-to-point link model =
is also recommended .<br>=0ARFC4068 is based on shared link model, and is n=
ot applicable for point-to-point link model without modification.<br>=0ASo,=
 &nbsp;there are some basic conflicts in the draft.<br>=0A<br>=0AFormulatio=
n of &nbsp;a prospective NCoA &nbsp;is a main idea of &nbsp;RFC4068.<br>=0A=
But in Point-to-Point link model, it is impossible to formulate the NCoA<br=
>=0Aaccording to &nbsp;RFC4068 because there is no proper prefix.<br>=0A<br=
>=0A<br>=0ABR<br>=0AFrank<br>=0A<br></span></font></blockquote></div><br></=
div></div></body></html>
--0-138758543-1180983877=:46196--



--===============0365081966==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng

--===============0365081966==--





From 16ng-bounces@ietf.org Mon Jun 04 15:15:31 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvI1a-0003XP-U5; Mon, 04 Jun 2007 15:15:30 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1HvGn6-0003k0-0r
	for 16ng-confirm+ok@megatron.ietf.org; Mon, 04 Jun 2007 13:56:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvGn5-0003js-NX; Mon, 04 Jun 2007 13:56:27 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvGn3-00023y-SP; Mon, 04 Jun 2007 13:56:27 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l54HuEoe023248; Mon, 4 Jun 2007 20:56:19 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Jun 2007 20:56:16 +0300
Received: from daebe103.NOE.Nokia.com ([10.241.35.24]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Jun 2007 12:56:13 -0500
Received: from 10.241.32.11 ([10.241.32.11]) by daebe103.NOE.Nokia.com
	([10.241.35.24]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon,  4 Jun 2007 17:56:12 +0000
User-Agent: Microsoft-Entourage/11.2.4.060510
Date: Mon, 04 Jun 2007 10:56:46 -0700
Subject: Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over
	IEEE802.16e Networks
From: Rajeev Koodli <rajeev.koodli@nokia.com>
To: <heejin.jang@samsung.com>, Frank Xia <xiayangsong@huawei.com>
Message-ID: <C289A06E.12142%rajeev.koodli@nokia.com>
Thread-Topic: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over
	IEEE802.16e Networks
Thread-Index: AcemYyNP/RJ+lqlpScOhhb2yosYiQgAbpQox
In-Reply-To: <11362793.1303151180932254151.JavaMail.weblogic@ep_ml20>
Mime-version: 1.0
X-OriginalArrivalTime: 04 Jun 2007 17:56:13.0563 (UTC)
	FILETIME=[A42544B0:01C7A6D1]
X-Nokia-AV: Clean
X-Spam-Score: 0.5 (/)
X-Scan-Signature: a0ecb232550b38fd41a3cf6a312fbabc
X-Mailman-Approved-At: Mon, 04 Jun 2007 15:15:29 -0400
Cc: mipshop@ietf.org, 16ng@ietf.org
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0388043204=="
Errors-To: 16ng-bounces@ietf.org

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============0388043204==
Content-type: multipart/alternative;
	boundary="B_3263799407_30988169"

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3263799407_30988169
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable


As far as I see, there is no problem here!

It does not matter what you call the prefix advertised in PrRtAdv. RFC 4068
does not make assumptions about how the prefixes are assigned and managed o=
n
an AR=B9s link. So, it is inaccurate to say as such in
draft-xia-mipshop-fmip-ptp-00.txt.

So, if prefix A is advertised in PrRtAdv, and a MN formulates a prospective
address IP-A and sends FBU, IP-A can be overridden by NAR in HAck.

Section 6.2.2

              Code        3: Handover Accepted, NCoA assigned
                             (used in Assigned addressing)


The supplied NCoA is provided in FBack or NAACK option.

This is the way I understood the problem and the solution for ptp links.

What am I missing?

-Rajeev




On 6/3/07 9:44 PM, "ext Heejin Jang" <heejin.jang@samsung.com> wrote:

> Hi, Frank & Daniel.
>=20
> RFC4068 describes fast HO procedure based on prediction, including NCoA
> formulation in advance.
> However, how to allocate the prefix to MN in NAR (before actual HO) is ou=
t of
> scope in this document
> as mentioned in Section 4.
>=20
> "The method by which Access Routers exchange information about their
> neighbors, and thereby allow
>   construction of Proxy Router  Advertisements with information about
> neighboring subnets is outside
>   the scope of this document."
>=20
> Furthermore, the problem you mentioned in draft-xia-mipshop-fmip-ptp-00 i=
s not
> limited only to 802.16 networks
> but happens all networks which have point-to-point link such as 3GPP2.
> I think that it is proper to handle this problem separately.
>=20
> Thanks for your opinion.
>=20
> - Regards,
> Heejin
>=20
> ------- Original Message -------
> Sender : Frank Xia<xiayangsong@huawei.com>
> Date   : 2007-06-01 06:50
> Title  : [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE 802.=
16e
> Networks
>=20
> Hi Daniel
>=20
> Here is my two cents.
>=20
> The draft is based on RFC4068, and point-to-point link model is also
> recommended .
> RFC4068 is based on shared link model, and is not applicable for
> point-to-point link model without modification.
> So,  there are some basic conflicts in the draft.
>=20
> Formulation of  a prospective NCoA  is a main idea of  RFC4068.
> But in Point-to-Point link model, it is impossible to formulate the NCoA
> according to  RFC4068 because there is no proper prefix.
>=20
>=20
> BR
> Frank
>=20
>=20
> ----- Original Message -----
> From: "Daniel Park" <soohong.park@samsung.com>
> To: <mipshop@ietf.org>
> Cc: <16ng@ietf.org>
> Sent: Sunday, May 27, 2007 9:34 PM
> Subject: [16NG] FW: Call for Review on FMIP6 over IEEE 802.16e Networks
>=20
>=20
>> > To MIPSHOP WG,
>> >
>> > Here is another expert review on "draft-ietf-mipshop-fh80216e-01",
>> > particularly, IEEE 802.21 relevant texts in this draft.
>> >
>> > Reviewer (Yoshihiro Ohba) is a IETF official liaison from IEEE 802.21
>> >
>> > Thanks Yoshihiro and hope this helps...
>> >
>> >
>> > ----
>> >
>> > Daniel Park & Gabriel Montenegro
>> > Chairs, 16NG Working Group
>> >
>=20
>=20
> -------------------------------------------------------------------------=
-----
> --
>=20
>=20
>> > _______________________________________________
>> > 16NG mailing list
>> > 16NG@ietf.org
>> > https://www1.ietf.org/mailman/listinfo/16ng
>> >
>=20
> _______________________________________________
> Mipshop mailing list
> Mipshop@ietf.org
> https://www1.ietf.org/mailman/listinfo/mipshop
>=20
>=20
>=20


--=20
http://people.nokia.net/~rajeev




--B_3263799407_30988169
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE802.1=
6e Networks</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:12.0px'><BR>
As far as I see, there is no problem here!<BR>
<BR>
It does not matter what you call the prefix advertised in PrRtAdv. RFC 4068=
 does not make assumptions about how the prefixes are assigned and managed o=
n an AR&#8217;s link. So, it is inaccurate to say as such in draft-xia-mipsh=
op-fmip-ptp-00.txt. <BR>
<BR>
So, if prefix A is advertised in PrRtAdv, and a MN formulates a prospective=
 address IP-A and sends FBU, IP-A can be overridden by NAR in HAck.<BR>
<BR>
Section 6.2.2<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;Code &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3: Handover Accepted=
, NCoA assigned<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;(used in Assigned addressing)<BR>
<BR>
<BR>
The supplied NCoA is provided in FBack or NAACK option.<BR>
<BR>
This is the way I understood the problem and the solution for ptp links.<BR=
>
<BR>
What am I missing?<BR>
<BR>
-Rajeev<BR>
<BR>
<BR>
<BR>
<BR>
On 6/3/07 9:44 PM, &quot;ext Heejin Jang&quot; &lt;heejin.jang@samsung.com&=
gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'>Hi, Frank &amp; Daniel.<BR>
<BR>
RFC4068 describes fast HO procedure based on prediction, including NCoA for=
mulation in advance.<BR>
However, how to allocate the prefix to MN in NAR (before actual HO) is out =
of scope in this document<BR>
as mentioned in Section 4.<BR>
<BR>
&quot;The method by which Access Routers exchange information about their n=
eighbors, and thereby allow<BR>
&nbsp;&nbsp;construction of Proxy Router &nbsp;Advertisements with informat=
ion about neighboring subnets is outside<BR>
&nbsp;&nbsp;the scope of this document.&quot;<BR>
<BR>
Furthermore, the problem you mentioned in draft-xia-mipshop-fmip-ptp-00 is =
not limited only to 802.16 networks<BR>
but happens all networks which have point-to-point link such as 3GPP2.<BR>
I think that it is proper to handle this problem separately.<BR>
<BR>
Thanks for your opinion.<BR>
<BR>
- Regards,<BR>
Heejin<BR>
<BR>
------- Original Message -------<BR>
Sender : Frank Xia&lt;xiayangsong@huawei.com&gt;<BR>
Date &nbsp;&nbsp;: 2007-06-01 06:50<BR>
Title &nbsp;: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE 8=
02.16e &nbsp;&nbsp;&nbsp;Networks<BR>
<BR>
Hi Daniel<BR>
<BR>
Here is my two cents.<BR>
<BR>
The draft is based on RFC4068, and point-to-point link model is also recomm=
ended .<BR>
RFC4068 is based on shared link model, and is not applicable for point-to-p=
oint link model without modification.<BR>
So, &nbsp;there are some basic conflicts in the draft.<BR>
<BR>
Formulation of &nbsp;a prospective NCoA &nbsp;is a main idea of &nbsp;RFC40=
68.<BR>
But in Point-to-Point link model, it is impossible to formulate the NCoA<BR=
>
according to &nbsp;RFC4068 because there is no proper prefix.<BR>
<BR>
<BR>
BR<BR>
Frank<BR>
<BR>
<BR>
----- Original Message -----<BR>
From: &quot;Daniel Park&quot; &lt;soohong.park@samsung.com&gt;<BR>
To: &lt;mipshop@ietf.org&gt;<BR>
Cc: &lt;16ng@ietf.org&gt;<BR>
Sent: Sunday, May 27, 2007 9:34 PM<BR>
Subject: [16NG] FW: Call for Review on FMIP6 over IEEE 802.16e Networks<BR>
<BR>
<BR>
&gt; To MIPSHOP WG,<BR>
&gt;<BR>
&gt; Here is another expert review on &quot;draft-ietf-mipshop-fh80216e-01&=
quot;,<BR>
&gt; particularly, IEEE 802.21 relevant texts in this draft.<BR>
&gt;<BR>
&gt; Reviewer (Yoshihiro Ohba) is a IETF official liaison from IEEE 802.21<=
BR>
&gt;<BR>
&gt; Thanks Yoshihiro and hope this helps...<BR>
&gt;<BR>
&gt;<BR>
&gt; ----<BR>
&gt;<BR>
&gt; Daniel Park &amp; Gabriel Montenegro<BR>
&gt; Chairs, 16NG Working Group<BR>
&gt;<BR>
<BR>
<BR>
---------------------------------------------------------------------------=
-----<BR>
<BR>
<BR>
&gt; _______________________________________________<BR>
&gt; 16NG mailing list<BR>
&gt; 16NG@ietf.org<BR>
&gt; https://www1.ietf.org/mailman/listinfo/16ng<BR>
&gt;<BR>
<BR>
_______________________________________________<BR>
Mipshop mailing list<BR>
Mipshop@ietf.org<BR>
https://www1.ietf.org/mailman/listinfo/mipshop<BR>
<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:12.0px'><BR>
<BR>
-- <BR>
<a href=3D"http://people.nokia.net/~rajeev">http://people.nokia.net/~rajeev</=
a> <BR>
<BR>
<BR>
</SPAN></FONT>
</BODY>
</HTML>


--B_3263799407_30988169--




--===============0388043204==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng

--===============0388043204==--






From 16ng-bounces@ietf.org Mon Jun 04 15:39:57 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvIPD-0005vJ-5h; Mon, 04 Jun 2007 15:39:55 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1HvIPB-0005v9-LB
	for 16ng-confirm+ok@megatron.ietf.org; Mon, 04 Jun 2007 15:39:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvIPB-0005v1-BR; Mon, 04 Jun 2007 15:39:53 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvIP8-0001g7-Qj; Mon, 04 Jun 2007 15:39:53 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l54JdVoT017664; Mon, 4 Jun 2007 22:39:41 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Jun 2007 22:39:36 +0300
Received: from daebe103.NOE.Nokia.com ([10.241.35.24]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Jun 2007 14:39:18 -0500
Received: from 10.241.32.11 ([10.241.32.11]) by daebe103.NOE.Nokia.com
	([10.241.35.24]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon,  4 Jun 2007 19:39:18 +0000
User-Agent: Microsoft-Entourage/11.2.4.060510
Date: Mon, 04 Jun 2007 12:39:51 -0700
Subject: Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over
	IEEE802.16e Networks
From: Rajeev Koodli <rajeev.koodli@nokia.com>
To: ext Frank Xia <xiayangsong@huawei.com>, <heejin.jang@samsung.com>
Message-ID: <C289B897.1214F%rajeev.koodli@nokia.com>
Thread-Topic: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over
	IEEE802.16e Networks
Thread-Index: Acem1gK7bAfpXETnS0KVFpfFKfrAdQAChtJd
In-Reply-To: <004501c7a6d6$3c168730$380c7c0a@china.huawei.com>
Mime-version: 1.0
X-OriginalArrivalTime: 04 Jun 2007 19:39:18.0789 (UTC)
	FILETIME=[0AD3DB50:01C7A6E0]
X-Nokia-AV: Clean
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 78a8240bd7a9c0d7033035fffd7b84c6
Cc: mipshop@ietf.org, 16ng@ietf.org
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1983265740=="
Errors-To: 16ng-bounces@ietf.org

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============1983265740==
Content-type: multipart/alternative;
	boundary="B_3263805592_31265873"

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3263805592_31265873
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable


HI Frank,


On 6/4/07 11:29 AM, "ext Frank Xia" <xiayangsong@huawei.com> wrote:
> =20
> 1 "(AP-ID, AR-Info) tuple Contains an access router's L2 and IP addresses=
, and
>   prefix valid on the interface to which the Access Point (identified by
> AP-ID) is attached.
>  The triplet [Router's  L2 address, Router's IP address and Prefix] is ca=
lled
> "AR-Info"".
> =20
> =3D> Here, prefix is AR's physical interface prefix is used for NCoA
> formulation.
>   As you know, this prefix is useless for P-to-P link model.
>=20
> Rajeev:> you could interpret it that way, but you don=B9t have to. The poin=
t I
> am trying to make is that the current model works for the scenario you ar=
e
> enumerating.
>=20
> An AR may use per-mobile prefix and an aggregate prefix on the interface.=
 As I
> said, aggregate prefix could be what is advertised in PrRtAdv. The MN can
> formulate a prospective NCoA using that, but receive a different NCoA fro=
m
> NAR, based on the per-mobile prefix.
> =20
> I can imagine other ways to manage the prefix.
>=20
>=20
> 2 " Through the RtSolPr and PrRtAdv messages, the MN also formulates a
>     prospective new CoA (NCoA), when it is still present on the PAR's
>     link.  Hence, the latency due to new prefix discovery subsequent to
>     handover is eliminated.  Furthermore, this prospective address can
>     be used immediately after attaching to the new subnet link (i.e.,
>     NAR's link) when the MN has received a "Fast Binding Acknowledgment
>     (FBack)" message prior to its movement.  In the event it moves
>     without receiving an FBack, the MN can still start using NCoA
>     after announcing its attachment through an unsolicited Neighbor
>     Advertisement message (with the 'O' bit set to zero) message [8];
>     NAR responds to to this UNA message in case the tentative address is
>     already in use.  In this way, NCoA configuration latency is reduced"
>=20
> =3D>is it meaningful for P-to-P?
>=20
> Rajeev:> If your question is will it work with per-mobile prefix, yes. Ei=
ther
> FBack or NAACK can provide the NCoA that the NAR wants the MN to use.
>=20
> ...
> =20
> In fact any parts related to the prefix is not proper for p-to-p link mod=
el.
> =20
> Rajeev:> That=B9s a pretty broad statement. You should separate prefix
> management from the address formulation. If an address is formulated usin=
g an
> aggregate prefix (which NAR exchanges with PAR), then that address can be
> overridden from the NAR using a per-mobile prefix. RFC 4068 provides mean=
s to
> do this.=20
>=20
> =20
> BTW, From my understanding, your propsal is that the only way for MN gett=
ing
> it's CoA
> MUST be requesting it from NAR for P-to-P link.
> =20
> Rajeev:> I am just pointing out how the current model in 4068 can work fo=
r
> your scenario.=20
>=20
> -Rajeev
>=20
> =20
> =20
> BR
> Frank
> =20
> =20
> =20
> =20
> =20
> =20
> =20
> =20
> =20
> =20
> =20
> =20
>> =20
>> ----- Original Message -----
>> =20
>> From:  Rajeev  Koodli <mailto:rajeev.koodli@nokia.com>
>> =20
>> To: heejin.jang@samsung.com ; Frank  Xia <mailto:xiayangsong@huawei.com>
>> =20
>> Cc: mipshop@ietf.org ; 16ng@ietf.org ; ??? <mailto:soohong.park@samsung.=
com>
>> =20
>> Sent: Monday, June 04, 2007 12:56 PM
>> =20
>> Subject: Re: [Mipshop] Re: [16NG] FW: Call  for Review on FMIP6 over
>> IEEE802.16e Networks
>> =20
>>=20
>>=20
>> As far as I see, there is no problem  here!
>>=20
>> It does not matter what you call the prefix advertised in  PrRtAdv. RFC =
4068
>> does not make assumptions about how the prefixes are  assigned and manag=
ed on
>> an AR=B9s link. So, it is inaccurate to say as such in
>> draft-xia-mipshop-fmip-ptp-00.txt.
>>=20
>> So, if prefix A is advertised in  PrRtAdv, and a MN formulates a prospec=
tive
>> address IP-A and sends FBU, IP-A  can be overridden by NAR in HAck.
>>=20
>> Section  6.2.2
>>=20
>>               Code         3: Handover Accepted, NCoA  assigned
>>                              (used  in Assigned addressing)
>>=20
>>=20
>> The supplied NCoA is provided in FBack or  NAACK option.
>>=20
>> This is the way I understood the problem and the solution  for ptp links=
.
>>=20
>> What am I missing?
>>=20
>> -Rajeev
>>=20
>>=20
>>=20
>>=20
>> On  6/3/07 9:44 PM, "ext Heejin Jang" <heejin.jang@samsung.com>  wrote:
>>=20
>> =20
>>> Hi, Frank & Daniel.
>>>=20
>>> RFC4068 describes  fast HO procedure based on prediction, including NCo=
A
>>> formulation in  advance.
>>> However, how to allocate the prefix to MN in NAR (before actual  HO) is=
 out
>>> of scope in this document
>>> as mentioned in Section  4.
>>>=20
>>> "The method by which Access Routers exchange information about  their
>>> neighbors, and thereby allow
>>>   construction of Proxy  Router  Advertisements with information about
>>> neighboring subnets is  outside
>>>   the scope of this document."
>>>=20
>>> Furthermore, the  problem you mentioned in draft-xia-mipshop-fmip-ptp-0=
0 is
>>> not limited only  to 802.16 networks
>>> but happens all networks which have point-to-point  link such as 3GPP2.
>>> I think that it is proper to handle this problem  separately.
>>>=20
>>> Thanks for your opinion.
>>>=20
>>> -  Regards,
>>> Heejin
>>>=20
>>> ------- Original Message -------
>>> Sender : Frank  Xia<xiayangsong@huawei.com>
>>> Date   : 2007-06-01  06:50
>>> Title  : [Mipshop] Re: [16NG] FW: Call for Review on FMIP6  over IEEE
>>> 802.16e    Networks
>>>=20
>>> Hi Daniel
>>>=20
>>> Here is  my two cents.
>>>=20
>>> The draft is based on RFC4068, and point-to-point link  model is also
>>> recommended .
>>> RFC4068 is based on shared link model, and is  not applicable for
>>> point-to-point link model without modification.
>>> So,   there are some basic conflicts in the draft.
>>>=20
>>> Formulation of   a prospective NCoA  is a main idea of  RFC4068.
>>> But in  Point-to-Point link model, it is impossible to formulate the  N=
CoA
>>> according to  RFC4068 because there is no proper  prefix.
>>>=20
>>>=20
>>> BR
>>> Frank
>>>=20
>>>=20
>>> ----- Original Message  -----
>>> From: "Daniel Park" <soohong.park@samsung.com>
>>> To:  <mipshop@ietf.org>
>>> Cc: <16ng@ietf.org>
>>> Sent: Sunday, May  27, 2007 9:34 PM
>>> Subject: [16NG] FW: Call for Review on FMIP6 over IEEE  802.16e Network=
s
>>>=20
>>>=20
>>>> > To MIPSHOP WG,
>>>> >
>>>> > Here is  another expert review on "draft-ietf-mipshop-fh80216e-01",
>>>> >  particularly, IEEE 802.21 relevant texts in this draft.
>>>> >
>>>> >  Reviewer (Yoshihiro Ohba) is a IETF official liaison from IEEE  802=
.21
>>>> >
>>>> > Thanks Yoshihiro and hope this  helps...
>>>> >
>>>> >
>>>> > ----
>>>> >
>>>> > Daniel Park &  Gabriel Montenegro
>>>> > Chairs, 16NG Working  Group
>>>> >
>>>=20
>>>=20
>>> -----------------------------------------------------------------------=
-----
>>> ----
>>>=20
>>>=20
>>>> >  _______________________________________________
>>>> > 16NG mailing  list
>>>> > 16NG@ietf.org
>>>> >  https://www1.ietf.org/mailman/listinfo/16ng
>>>> >
>>>=20
>>> _______________________________________________
>>> Mipshop  mailing  list
>>> Mipshop@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mipshop
>>>=20
>>>=20
>>>=20
>>=20
>>=20
>> -- =20
>> http://people.nokia.net/~rajeev
>>=20
>>=20
>=20


--=20
http://people.nokia.net/~rajeev




--B_3263805592_31265873
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE802.1=
6e Networks</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:12.0px'><BR>
HI Frank,<BR>
<BR>
<BR>
On 6/4/07 11:29 AM, &quot;ext Frank Xia&quot; &lt;xiayangsong@huawei.com&gt=
; wrote:<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'> <BR>
1 &quot;(AP-ID, AR-Info) tuple Contains an access router's L2 and IP addres=
ses, and<BR>
&nbsp;&nbsp;prefix valid on the interface to which the Access Point (identi=
fied by AP-ID) is attached. &nbsp;<BR>
&nbsp;The triplet [Router's &nbsp;L2 address, Router's IP address and Prefi=
x] is called &quot;AR-Info&quot;&quot;.<BR>
&nbsp;<BR>
=3D&gt; Here, prefix is AR's physical interface prefix is used for NCoA formu=
lation.<BR>
&nbsp;&nbsp;As you know, this prefix is useless for P-to-P link model.<BR>
<BR>
Rajeev:&gt; you could interpret it that way, but you don&#8217;t have to. T=
he point I am trying to make is that the current model works for the scenari=
o you are enumerating.<BR>
<BR>
An AR may use per-mobile prefix and an aggregate prefix on the interface. A=
s I said, aggregate prefix could be what is advertised in PrRtAdv. The MN ca=
n formulate a prospective NCoA using that, but receive a different NCoA from=
 NAR, based on the per-mobile prefix. <BR>
&nbsp;<BR>
I can imagine other ways to manage the prefix. <BR>
<BR>
<BR>
2 &quot; Through the RtSolPr and PrRtAdv messages, the MN also formulates a=
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;prospective new CoA (NCoA), when it is still presen=
t on the PAR's<BR>
&nbsp;&nbsp;&nbsp;&nbsp;link. &nbsp;Hence, the latency due to new prefix di=
scovery subsequent to<BR>
&nbsp;&nbsp;&nbsp;&nbsp;handover is eliminated. &nbsp;Furthermore, this pro=
spective address can<BR>
&nbsp;&nbsp;&nbsp;&nbsp;be used immediately after attaching to the new subn=
et link (i.e.,<BR>
&nbsp;&nbsp;&nbsp;&nbsp;NAR's link) when the MN has received a &quot;Fast B=
inding Acknowledgment<BR>
&nbsp;&nbsp;&nbsp;&nbsp;(FBack)&quot; message prior to its movement. &nbsp;=
In the event it moves<BR>
&nbsp;&nbsp;&nbsp;&nbsp;without receiving an FBack, the MN can still start =
using NCoA<BR>
&nbsp;&nbsp;&nbsp;&nbsp;after announcing its attachment through an unsolici=
ted Neighbor<BR>
&nbsp;&nbsp;&nbsp;&nbsp;Advertisement message (with the 'O' bit set to zero=
) message [8];<BR>
&nbsp;&nbsp;&nbsp;&nbsp;NAR responds to to this UNA message in case the ten=
tative address is<BR>
&nbsp;&nbsp;&nbsp;&nbsp;already in use. &nbsp;In this way, NCoA configurati=
on latency is reduced&quot;<BR>
<BR>
=3D&gt;is it meaningful for P-to-P?<BR>
<BR>
Rajeev:&gt; If your question is will it work with per-mobile prefix, yes. E=
ither FBack or NAACK can provide the NCoA that the NAR wants the MN to use. =
<BR>
<BR>
...<BR>
&nbsp;<BR>
In fact any parts related to the prefix is not proper for p-to-p link model=
.<BR>
&nbsp;<BR>
Rajeev:&gt; That&#8217;s a pretty broad statement. You should separate pref=
ix management from the address formulation. If an address is formulated usin=
g an aggregate prefix (which NAR exchanges with PAR), then that address can =
be overridden from the NAR using a per-mobile prefix. RFC 4068 provides mean=
s to do this. <BR>
<BR>
&nbsp;<BR>
BTW, From my understanding, your propsal is that the only way for MN gettin=
g it's CoA<BR>
MUST be requesting it from NAR for P-to-P link.<BR>
&nbsp;<BR>
Rajeev:&gt; I am just pointing out how the current model in 4068 can work f=
or your scenario. <BR>
<BR>
-Rajeev<BR>
<BR>
&nbsp;<BR>
&nbsp;<BR>
BR<BR>
Frank<BR>
&nbsp;<BR>
&nbsp;<BR>
&nbsp;<BR>
&nbsp;<BR>
&nbsp;<BR>
&nbsp;<BR>
&nbsp;<BR>
&nbsp;<BR>
&nbsp;<BR>
&nbsp;<BR>
&nbsp;<BR>
&nbsp;<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'> <BR>
----- Original Message ----- <BR>
&nbsp;<BR>
<B>From:</B> &nbsp;Rajeev &nbsp;Koodli <a href=3D"mailto:rajeev.koodli@nokia.=
com">&lt;mailto:rajeev.koodli@nokia.com&gt;</a> &nbsp;<BR>
&nbsp;<BR>
<B>To:</B> heejin.jang@samsung.com ; Frank &nbsp;Xia <a href=3D"mailto:xiayan=
gsong@huawei.com">&lt;mailto:xiayangsong@huawei.com&gt;</a> &nbsp;<BR>
&nbsp;<BR>
<B>Cc:</B> mipshop@ietf.org ; 16ng@ietf.org ; ??? <a href=3D"mailto:soohong.p=
ark@samsung.com">&lt;mailto:soohong.park@samsung.com&gt;</a> &nbsp;&nbsp;<BR=
>
&nbsp;<BR>
<B>Sent:</B> Monday, June 04, 2007 12:56 PM<BR>
&nbsp;<BR>
<B>Subject:</B> Re: [Mipshop] Re: [16NG] FW: Call &nbsp;for Review on FMIP6=
 over IEEE802.16e Networks<BR>
&nbsp;<BR>
<BR>
<BR>
As far as I see, there is no problem &nbsp;here!<BR>
<BR>
It does not matter what you call the prefix advertised in &nbsp;PrRtAdv. RF=
C 4068 does not make assumptions about how the prefixes are &nbsp;assigned a=
nd managed on an AR&#8217;s link. So, it is inaccurate to say as such in &nb=
sp;draft-xia-mipshop-fmip-ptp-00.txt. <BR>
<BR>
So, if prefix A is advertised in &nbsp;PrRtAdv, and a MN formulates a prosp=
ective address IP-A and sends FBU, IP-A &nbsp;can be overridden by NAR in HA=
ck.<BR>
<BR>
Section &nbsp;6.2.2<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;Code &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3: Handover Ac=
cepted, NCoA &nbsp;assigned<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;(used &nbsp;in Assigned addressing)<BR>
<BR>
<BR>
The supplied NCoA is provided in FBack or &nbsp;NAACK option.<BR>
<BR>
This is the way I understood the problem and the solution &nbsp;for ptp lin=
ks.<BR>
<BR>
What am I missing?<BR>
<BR>
-Rajeev<BR>
<BR>
<BR>
<BR>
<BR>
On &nbsp;6/3/07 9:44 PM, &quot;ext Heejin Jang&quot; &lt;heejin.jang@samsun=
g.com&gt; &nbsp;wrote:<BR>
<BR>
&nbsp;<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'>Hi, Frank &amp; Daniel.<BR>
<BR>
RFC4068 describes &nbsp;fast HO procedure based on prediction, including NC=
oA formulation in &nbsp;advance.<BR>
However, how to allocate the prefix to MN in NAR (before actual &nbsp;HO) i=
s out of scope in this document<BR>
as mentioned in Section &nbsp;4.<BR>
<BR>
&quot;The method by which Access Routers exchange information about &nbsp;t=
heir neighbors, and thereby allow<BR>
&nbsp;&nbsp;construction of Proxy &nbsp;Router &nbsp;Advertisements with in=
formation about neighboring subnets is &nbsp;outside<BR>
&nbsp;&nbsp;the scope of this document.&quot;<BR>
<BR>
Furthermore, the &nbsp;problem you mentioned in draft-xia-mipshop-fmip-ptp-=
00 is not limited only &nbsp;to 802.16 networks<BR>
but happens all networks which have point-to-point &nbsp;link such as 3GPP2=
.<BR>
I think that it is proper to handle this problem &nbsp;separately.<BR>
<BR>
Thanks for your opinion.<BR>
<BR>
- &nbsp;Regards,<BR>
Heejin<BR>
<BR>
------- Original Message -------<BR>
Sender : Frank &nbsp;Xia&lt;xiayangsong@huawei.com&gt;<BR>
Date &nbsp;&nbsp;: 2007-06-01 &nbsp;06:50<BR>
Title &nbsp;: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 &nbsp;over =
IEEE 802.16e &nbsp;&nbsp;&nbsp;Networks<BR>
<BR>
Hi Daniel<BR>
<BR>
Here is &nbsp;my two cents.<BR>
<BR>
The draft is based on RFC4068, and point-to-point link &nbsp;model is also =
recommended .<BR>
RFC4068 is based on shared link model, and is &nbsp;not applicable for poin=
t-to-point link model without modification.<BR>
So, &nbsp;&nbsp;there are some basic conflicts in the draft.<BR>
<BR>
Formulation of &nbsp;&nbsp;a prospective NCoA &nbsp;is a main idea of &nbsp=
;RFC4068.<BR>
But in &nbsp;Point-to-Point link model, it is impossible to formulate the &=
nbsp;NCoA<BR>
according to &nbsp;RFC4068 because there is no proper &nbsp;prefix.<BR>
<BR>
<BR>
BR<BR>
Frank<BR>
<BR>
<BR>
----- Original Message &nbsp;-----<BR>
From: &quot;Daniel Park&quot; &lt;soohong.park@samsung.com&gt;<BR>
To: &nbsp;&lt;mipshop@ietf.org&gt;<BR>
Cc: &lt;16ng@ietf.org&gt;<BR>
Sent: Sunday, May &nbsp;27, 2007 9:34 PM<BR>
Subject: [16NG] FW: Call for Review on FMIP6 over IEEE &nbsp;802.16e Networ=
ks<BR>
<BR>
<BR>
&gt; To MIPSHOP WG,<BR>
&gt;<BR>
&gt; Here is &nbsp;another expert review on &quot;draft-ietf-mipshop-fh8021=
6e-01&quot;,<BR>
&gt; &nbsp;particularly, IEEE 802.21 relevant texts in this draft.<BR>
&gt;<BR>
&gt; &nbsp;Reviewer (Yoshihiro Ohba) is a IETF official liaison from IEEE &=
nbsp;802.21<BR>
&gt;<BR>
&gt; Thanks Yoshihiro and hope this &nbsp;helps...<BR>
&gt;<BR>
&gt;<BR>
&gt; ----<BR>
&gt;<BR>
&gt; Daniel Park &amp; &nbsp;Gabriel Montenegro<BR>
&gt; Chairs, 16NG Working &nbsp;Group<BR>
&gt;<BR>
<BR>
<BR>
---------------------------------------------------------------------------=
-----<BR>
<BR>
<BR>
&gt; &nbsp;_______________________________________________<BR>
&gt; 16NG mailing &nbsp;list<BR>
&gt; 16NG@ietf.org<BR>
&gt; &nbsp;https://www1.ietf.org/mailman/listinfo/16ng<BR>
&gt;<BR>
<BR>
_______________________________________________<BR>
Mipshop &nbsp;mailing &nbsp;list<BR>
Mipshop@ietf.org<BR>
https://www1.ietf.org/mailman/listinfo/mipshop<BR>
<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:12.0px'><BR>
<BR>
-- &nbsp;<BR>
<a href=3D"http://people.nokia.net/~rajeev">http://people.nokia.net/~rajeev</=
a> &nbsp;<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:12.0px'><BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:12.0px'><BR>
<BR>
-- <BR>
<a href=3D"http://people.nokia.net/~rajeev">http://people.nokia.net/~rajeev</=
a> <BR>
<BR>
<BR>
</SPAN></FONT>
</BODY>
</HTML>


--B_3263805592_31265873--




--===============1983265740==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng

--===============1983265740==--






From 16ng-bounces@ietf.org Mon Jun 04 15:43:55 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvIT5-0006ne-FE; Mon, 04 Jun 2007 15:43:55 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1HvIT4-0006lP-5G
	for 16ng-confirm+ok@megatron.ietf.org; Mon, 04 Jun 2007 15:43:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvIT3-0006kc-RJ; Mon, 04 Jun 2007 15:43:53 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvIT1-00027i-B2; Mon, 04 Jun 2007 15:43:53 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l54Jhg4T015952; Mon, 4 Jun 2007 22:43:48 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Jun 2007 22:43:43 +0300
Received: from daebe103.NOE.Nokia.com ([10.241.35.24]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Jun 2007 14:43:16 -0500
Received: from 10.241.32.11 ([10.241.32.11]) by daebe103.NOE.Nokia.com
	([10.241.35.24]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon,  4 Jun 2007 19:43:16 +0000
User-Agent: Microsoft-Entourage/11.2.4.060510
Date: Mon, 04 Jun 2007 12:43:50 -0700
Subject: Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over
	IEEE802.16e Networks
From: Rajeev Koodli <rajeev.koodli@nokia.com>
To: Behcet Sarikaya <sarikaya@ieee.org>,
	"Koodli Rajeev (NSN - US/Palo Alto)" <rajeev.koodli@nsn.com>
Message-ID: <C289B986.12153%rajeev.koodli@nokia.com>
Thread-Topic: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over
	IEEE802.16e Networks
Thread-Index: Acem2z/dMikKPiK2SMa5yxgecSCZVAABWycz
In-Reply-To: <534356.46196.qm@web84111.mail.mud.yahoo.com>
Mime-version: 1.0
X-OriginalArrivalTime: 04 Jun 2007 19:43:16.0694 (UTC)
	FILETIME=[98A14760:01C7A6E0]
X-Nokia-AV: Clean
X-Spam-Score: 0.3 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: mipshop@ietf.org, 16ng@ietf.org
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1300389053=="
Errors-To: 16ng-bounces@ietf.org

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============1300389053==
Content-type: multipart/alternative;
	boundary="B_3263805830_31235127"

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3263805830_31235127
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit


Hi Bechet,

On 6/4/07 12:04 PM, "ext Behcet Sarikaya" <behcetsarikaya@yahoo.com> wrote:

> [behcet] Hi/Hack exchange is used in predictive mode, not used in reactive
> mode. 
> 
> Rajeev:> HI/Hack exchange is not forbidden in reactive mode. Please point out
> any text suggesting this, and I will clarify.
> 
> Even for the predictive mode with Code 3, some changes are needed in the
> current text.
> 
> Rajeev:> It would be useful to point out what those changes are and discuss
> :-)
> 
> -Rajeev
> 
-- 
http://people.nokia.net/~rajeev




--B_3263805830_31235127
Content-type: text/html;
	charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE802.1=
6e Networks</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:12.0px'><BR>
Hi Bechet,<BR>
<BR>
On 6/4/07 12:04 PM, &quot;ext Behcet Sarikaya&quot; &lt;behcetsarikaya@yaho=
o.com&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><FONT SIZE=
=3D"6"><SPAN STYLE=3D'font-size:24.0px'>[behcet] Hi/Hack exchange is used in pre=
dictive mode, not used in reactive mode. <BR>
<BR>
</SPAN></FONT><SPAN STYLE=3D'font-size:12.0px'>Rajeev:&gt; HI/Hack exchange i=
s not forbidden in reactive mode. Please point out any text suggesting this,=
 and I will clarify. &nbsp;<BR>
</SPAN><FONT SIZE=3D"6"><SPAN STYLE=3D'font-size:24.0px'><BR>
Even for the predictive mode with Code 3, some changes are needed in the cu=
rrent text.<BR>
<BR>
</SPAN></FONT><SPAN STYLE=3D'font-size:12.0px'>Rajeev:&gt; It would be useful=
 to point out what those changes are and discuss :-)<BR>
<BR>
-Rajeev<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:12.0px'>-- <BR>
<a href=3D"http://people.nokia.net/~rajeev">http://people.nokia.net/~rajeev</=
a> <BR>
<BR>
<BR>
</SPAN></FONT>
</BODY>
</HTML>


--B_3263805830_31235127--




--===============1300389053==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng

--===============1300389053==--






From 16ng-bounces@ietf.org Mon Jun 04 16:39:20 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvJKh-0007pL-JY; Mon, 04 Jun 2007 16:39:19 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1HvJKg-0007pD-QZ
	for 16ng-confirm+ok@megatron.ietf.org; Mon, 04 Jun 2007 16:39:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvJKg-0007p5-GS; Mon, 04 Jun 2007 16:39:18 -0400
Received: from szxga04-in.huawei.com ([61.144.161.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvJKe-0003m8-42; Mon, 04 Jun 2007 16:39:18 -0400
Received: from huawei.com (szxga04-in [172.24.2.12])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JJ400DUNPCEEJ@szxga04-in.huawei.com>; Tue,
	05 Jun 2007 04:38:38 +0800 (CST)
Received: from ny3104051930 ([10.124.12.56])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JJ4005IZPC53B@szxga04-in.huawei.com>; Tue,
	05 Jun 2007 04:38:38 +0800 (CST)
Date: Mon, 04 Jun 2007 15:40:19 -0500
From: Frank Xia <xiayangsong@huawei.com>
Subject: Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE802.16e
	Networks
To: Rajeev Koodli <rajeev.koodli@nokia.com>, heejin.jang@samsung.com
Message-id: <001901c7a6e8$92a5ee80$380c7c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-Priority: 3
X-MSMail-priority: Normal
References: <C289B897.1214F%rajeev.koodli@nokia.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 08582f3b796126054df71137d5cb69f8
Cc: mipshop@ietf.org, 16ng@ietf.org
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1965355676=="
Errors-To: 16ng-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1965355676==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_66aTj510MVpgtG017jL78A)"

This is a multi-part message in MIME format.

--Boundary_(ID_66aTj510MVpgtG017jL78A)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE802.16e NetworksHi Rajeev


I am a little bit confused with you explanation.

Please see my inline comments.


BR
Frank
  ----- Original Message ----- 
  From: Rajeev Koodli 
  To: ext Frank Xia ; heejin.jang@samsung.com 
  Cc: mipshop@ietf.org ; 16ng@ietf.org ; ??? 
  Sent: Monday, June 04, 2007 2:39 PM
  Subject: Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE802.16e Networks



  HI Frank,


  On 6/4/07 11:29 AM, "ext Frank Xia" <xiayangsong@huawei.com> wrote:


    1 "(AP-ID, AR-Info) tuple Contains an access router's L2 and IP addresses, and
      prefix valid on the interface to which the Access Point (identified by AP-ID) is attached.  
     The triplet [Router's  L2 address, Router's IP address and Prefix] is called "AR-Info"".
     
    => Here, prefix is AR's physical interface prefix is used for NCoA formulation.
      As you know, this prefix is useless for P-to-P link model.

    Rajeev:> you could interpret it that way, but you don't have to. The point I am trying to make is that the current model works for the scenario you are enumerating.

    Frank=> don't you think the concept of the perfix is too flexible that different people can have their own different understanding?  In your draft, the prefix is definitely the prefix of AR physical interface. I think there is not ambiguous.


    An AR may use per-mobile prefix and an aggregate prefix on the interface. As I said, aggregate prefix could be what is advertised in PrRtAdv. The MN can formulate a prospective NCoA using that, but receive a different NCoA from NAR, based on the per-mobile prefix. 
    Frank =>In fact,  this is not big different from our propsoal in draft-xia-mipshop-fmip-ptp-00 

    I can imagine other ways to manage the prefix. 
    Frank => I  also have a revised document which elaborating other alternatives, and we can cooperate .



    2 " Through the RtSolPr and PrRtAdv messages, the MN also formulates a
        prospective new CoA (NCoA), when it is still present on the PAR's
        link.  Hence, the latency due to new prefix discovery subsequent to
        handover is eliminated.  Furthermore, this prospective address can
        be used immediately after attaching to the new subnet link (i.e.,
        NAR's link) when the MN has received a "Fast Binding Acknowledgment
        (FBack)" message prior to its movement.  In the event it moves
        without receiving an FBack, the MN can still start using NCoA
        after announcing its attachment through an unsolicited Neighbor
        Advertisement message (with the 'O' bit set to zero) message [8];
        NAR responds to to this UNA message in case the tentative address is
        already in use.  In this way, NCoA configuration latency is reduced"

    =>is it meaningful for P-to-P?

    Rajeev:> If your question is will it work with per-mobile prefix, yes. Either FBack or NAACK can provide the NCoA that the NAR wants the MN to use. 

    Frank => The exchange of RtSolPr and PrRtAdv is to formulate a new CoA while is useless in p-t-p model.  It is a waste of air interface resource.
    ...
     
    In fact any parts related to the prefix is not proper for p-to-p link model.
     
    Rajeev:> That's a pretty broad statement. You should separate prefix management from the address formulation. If an address is formulated using an aggregate prefix (which NAR exchanges with PAR), then that address can be overridden from the NAR using a per-mobile prefix. RFC 4068 provides means to do this. 

     
    BTW, From my understanding, your propsal is that the only way for MN getting it's CoA
    MUST be requesting it from NAR for P-to-P link.
     
    Rajeev:> I am just pointing out how the current model in 4068 can work for your scenario. 

    Frank => P-to-P scenario is adopted by WiMAX/3GPP2, while I have little idea about promising deployment of shared link model.
    IMHO, your simplified proposal can't solve the proplem very well.

    -Rajeev

     
     
    BR
    Frank
     
     
     
     
     
     
     
     
     
     
     
     


      ----- Original Message ----- 
       
      From:  Rajeev  Koodli <mailto:rajeev.koodli@nokia.com>  
       
      To: heejin.jang@samsung.com ; Frank  Xia <mailto:xiayangsong@huawei.com>  
       
      Cc: mipshop@ietf.org ; 16ng@ietf.org ; ??? <mailto:soohong.park@samsung.com>   
       
      Sent: Monday, June 04, 2007 12:56 PM
       
      Subject: Re: [Mipshop] Re: [16NG] FW: Call  for Review on FMIP6 over IEEE802.16e Networks
       


      As far as I see, there is no problem  here!

      It does not matter what you call the prefix advertised in  PrRtAdv. RFC 4068 does not make assumptions about how the prefixes are  assigned and managed on an AR's link. So, it is inaccurate to say as such in  draft-xia-mipshop-fmip-ptp-00.txt. 

      So, if prefix A is advertised in  PrRtAdv, and a MN formulates a prospective address IP-A and sends FBU, IP-A  can be overridden by NAR in HAck.

      Section  6.2.2

                    Code         3: Handover Accepted, NCoA  assigned
                                   (used  in Assigned addressing)


      The supplied NCoA is provided in FBack or  NAACK option.

      This is the way I understood the problem and the solution  for ptp links.

      What am I missing?

      -Rajeev




      On  6/3/07 9:44 PM, "ext Heejin Jang" <heejin.jang@samsung.com>  wrote:

       

        Hi, Frank & Daniel.

        RFC4068 describes  fast HO procedure based on prediction, including NCoA formulation in  advance.
        However, how to allocate the prefix to MN in NAR (before actual  HO) is out of scope in this document
        as mentioned in Section  4.

        "The method by which Access Routers exchange information about  their neighbors, and thereby allow
          construction of Proxy  Router  Advertisements with information about neighboring subnets is  outside
          the scope of this document."

        Furthermore, the  problem you mentioned in draft-xia-mipshop-fmip-ptp-00 is not limited only  to 802.16 networks
        but happens all networks which have point-to-point  link such as 3GPP2.
        I think that it is proper to handle this problem  separately.

        Thanks for your opinion.

        -  Regards,
        Heejin

        ------- Original Message -------
        Sender : Frank  Xia<xiayangsong@huawei.com>
        Date   : 2007-06-01  06:50
        Title  : [Mipshop] Re: [16NG] FW: Call for Review on FMIP6  over IEEE 802.16e    Networks

        Hi Daniel

        Here is  my two cents.

        The draft is based on RFC4068, and point-to-point link  model is also recommended .
        RFC4068 is based on shared link model, and is  not applicable for point-to-point link model without modification.
        So,   there are some basic conflicts in the draft.

        Formulation of   a prospective NCoA  is a main idea of  RFC4068.
        But in  Point-to-Point link model, it is impossible to formulate the  NCoA
        according to  RFC4068 because there is no proper  prefix.


        BR
        Frank


        ----- Original Message  -----
        From: "Daniel Park" <soohong.park@samsung.com>
        To:  <mipshop@ietf.org>
        Cc: <16ng@ietf.org>
        Sent: Sunday, May  27, 2007 9:34 PM
        Subject: [16NG] FW: Call for Review on FMIP6 over IEEE  802.16e Networks


        > To MIPSHOP WG,
        >
        > Here is  another expert review on "draft-ietf-mipshop-fh80216e-01",
        >  particularly, IEEE 802.21 relevant texts in this draft.
        >
        >  Reviewer (Yoshihiro Ohba) is a IETF official liaison from IEEE  802.21
        >
        > Thanks Yoshihiro and hope this  helps...
        >
        >
        > ----
        >
        > Daniel Park &  Gabriel Montenegro
        > Chairs, 16NG Working  Group
        >


        --------------------------------------------------------------------------------


        >  _______________________________________________
        > 16NG mailing  list
        > 16NG@ietf.org
        >  https://www1.ietf.org/mailman/listinfo/16ng
        >

        _______________________________________________
        Mipshop  mailing  list
        Mipshop@ietf.org
        https://www1.ietf.org/mailman/listinfo/mipshop






      --  
      http://people.nokia.net/~rajeev  







  -- 
  http://people.nokia.net/~rajeev 



--Boundary_(ID_66aTj510MVpgtG017jL78A)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPjxUSVRMRT5SZTogW01pcHNob3BdIFJlOiBbMTZOR10gRlc6IENh
bGwgZm9yIFJldmlldyBvbiBGTUlQNiBvdmVyIElFRUU4MDIuMTZlIE5ldHdvcmtzPC9USVRMRT4N
CjxNRVRBIGh0dHAtZXF1aXY9Q29udGVudC1UeXBlIGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNl
dD1pc28tODg1OS0xIj4NCjxNRVRBIGNvbnRlbnQ9Ik1TSFRNTCA2LjAwLjI4MDAuMTU2MSIgbmFt
ZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9TVFlMRT4NCjwvSEVBRD4NCjxCT0RZIGJnQ29sb3I9I2Zm
ZmZmZj4NCjxESVY+PEZPTlQgZmFjZT0mIzIzNDM1OyYjMjAzMDc7IHNpemU9Mj5IaSBSYWplZXY8
L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+PC9G
T05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPSYjMjM0MzU7JiMyMDMwNzsgc2l6ZT0y
PjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT0mIzIzNDM1OyYjMjAzMDc7IHNp
emU9Mj5JIGFtIGEgbGl0dGxlIGJpdCBjb25mdXNlZCB3aXRoIHlvdSANCmV4cGxhbmF0aW9uLjwv
Rk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT0mIzIzNDM1OyYjMjAzMDc7IHNpemU9Mj48L0ZP
TlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+
UGxlYXNlIHNlZSBteSBpbmxpbmUgY29tbWVudHMuPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBm
YWNlPSYjMjM0MzU7JiMyMDMwNzsgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZP
TlQgZmFjZT0mIzIzNDM1OyYjMjAzMDc7IHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElW
PjxGT05UIGZhY2U9JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+QlI8L0ZPTlQ+PC9ESVY+DQo8RElW
PjxGT05UIGZhY2U9JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+RnJhbms8L0ZPTlQ+PC9ESVY+DQo8
QkxPQ0tRVU9URSANCnN0eWxlPSJQQURESU5HLVJJR0hUOiAwcHg7IFBBRERJTkctTEVGVDogNXB4
OyBNQVJHSU4tTEVGVDogNXB4OyBCT1JERVItTEVGVDogIzAwMDAwMCAycHggc29saWQ7IE1BUkdJ
Ti1SSUdIVDogMHB4Ij4NCiAgPERJViBzdHlsZT0iRk9OVDogOXB0ICYjMjM0MzU7JiMyMDMwNzsi
Pi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0gPC9ESVY+DQogIDxESVYgc3R5bGU9IkJBQ0tH
Uk9VTkQ6ICNlNGU0ZTQ7IEZPTlQ6IDlwdCAmIzIzNDM1OyYjMjAzMDc7OyBmb250LWNvbG9yOiBi
bGFjayI+PEI+RnJvbTo8L0I+IA0KICA8QSB0aXRsZT1yYWplZXYua29vZGxpQG5va2lhLmNvbSBo
cmVmPSJtYWlsdG86cmFqZWV2Lmtvb2RsaUBub2tpYS5jb20iPlJhamVldiANCiAgS29vZGxpPC9B
PiA8L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVDogOXB0ICYjMjM0MzU7JiMyMDMwNzsiPjxCPlRv
OjwvQj4gPEEgdGl0bGU9eGlheWFuZ3NvbmdAaHVhd2VpLmNvbSANCiAgaHJlZj0ibWFpbHRvOnhp
YXlhbmdzb25nQGh1YXdlaS5jb20iPmV4dCBGcmFuayBYaWE8L0E+IDsgPEEgDQogIHRpdGxlPWhl
ZWppbi5qYW5nQHNhbXN1bmcuY29tIA0KICBocmVmPSJtYWlsdG86aGVlamluLmphbmdAc2Ftc3Vu
Zy5jb20iPmhlZWppbi5qYW5nQHNhbXN1bmcuY29tPC9BPiA8L0RJVj4NCiAgPERJViBzdHlsZT0i
Rk9OVDogOXB0ICYjMjM0MzU7JiMyMDMwNzsiPjxCPkNjOjwvQj4gPEEgdGl0bGU9bWlwc2hvcEBp
ZXRmLm9yZyANCiAgaHJlZj0ibWFpbHRvOm1pcHNob3BAaWV0Zi5vcmciPm1pcHNob3BAaWV0Zi5v
cmc8L0E+IDsgPEEgdGl0bGU9MTZuZ0BpZXRmLm9yZyANCiAgaHJlZj0ibWFpbHRvOjE2bmdAaWV0
Zi5vcmciPjE2bmdAaWV0Zi5vcmc8L0E+IDsgPEEgDQogIHRpdGxlPXNvb2hvbmcucGFya0BzYW1z
dW5nLmNvbSBocmVmPSJtYWlsdG86c29vaG9uZy5wYXJrQHNhbXN1bmcuY29tIj4/Pz88L0E+IA0K
ICA8L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVDogOXB0ICYjMjM0MzU7JiMyMDMwNzsiPjxCPlNl
bnQ6PC9CPiBNb25kYXksIEp1bmUgMDQsIDIwMDcgMjozOSBQTTwvRElWPg0KICA8RElWIHN0eWxl
PSJGT05UOiA5cHQgJiMyMzQzNTsmIzIwMzA3OyI+PEI+U3ViamVjdDo8L0I+IFJlOiBbTWlwc2hv
cF0gUmU6IFsxNk5HXSBGVzogQ2FsbCANCiAgZm9yIFJldmlldyBvbiBGTUlQNiBvdmVyIElFRUU4
MDIuMTZlIE5ldHdvcmtzPC9ESVY+DQogIDxESVY+PEJSPjwvRElWPjxGT05UIGZhY2U9IlZlcmRh
bmEsIEhlbHZldGljYSwgQXJpYWwiPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMnB4Ij48
QlI+SEkgRnJhbmssPEJSPjxCUj48QlI+T24gNi80LzA3IDExOjI5IEFNLCAiZXh0IA0KICBGcmFu
ayBYaWEiICZsdDs8QSANCiAgaHJlZj0ibWFpbHRvOnhpYXlhbmdzb25nQGh1YXdlaS5jb20iPnhp
YXlhbmdzb25nQGh1YXdlaS5jb208L0E+Jmd0OyANCiAgd3JvdGU6PEJSPjwvU1BBTj48L0ZPTlQ+
DQogIDxCTE9DS1FVT1RFPjxGT05UIGZhY2U9IlZlcmRhbmEsIEhlbHZldGljYSwgQXJpYWwiPjxT
UEFOIA0KICAgIHN0eWxlPSJGT05ULVNJWkU6IDEycHgiPg0KICAgIDxESVY+PEJSPjEgIihBUC1J
RCwgQVItSW5mbykgdHVwbGUgQ29udGFpbnMgYW4gYWNjZXNzIHJvdXRlcidzIEwyIGFuZCBJUCAN
CiAgICBhZGRyZXNzZXMsIGFuZDxCUj4mbmJzcDsmbmJzcDtwcmVmaXggdmFsaWQgb24gdGhlIGlu
dGVyZmFjZSB0byB3aGljaCB0aGUgDQogICAgQWNjZXNzIFBvaW50IChpZGVudGlmaWVkIGJ5IEFQ
LUlEKSBpcyBhdHRhY2hlZC4gJm5ic3A7PEJSPiZuYnNwO1RoZSB0cmlwbGV0IA0KICAgIFtSb3V0
ZXIncyAmbmJzcDtMMiBhZGRyZXNzLCBSb3V0ZXIncyBJUCBhZGRyZXNzIGFuZCBQcmVmaXhdIGlz
IGNhbGxlZCANCiAgICAiQVItSW5mbyIiLjxCUj4mbmJzcDs8QlI+PSZndDsgSGVyZSwgcHJlZml4
IGlzIEFSJ3MgcGh5c2ljYWwgaW50ZXJmYWNlIA0KICAgIHByZWZpeCBpcyB1c2VkIGZvciBOQ29B
IGZvcm11bGF0aW9uLjxCUj4mbmJzcDsmbmJzcDtBcyB5b3Uga25vdywgdGhpcyBwcmVmaXggDQog
ICAgaXMgdXNlbGVzcyBmb3IgUC10by1QIGxpbmsgbW9kZWwuPEJSPjxCUj5SYWplZXY6Jmd0OyB5
b3UgY291bGQgaW50ZXJwcmV0IGl0IA0KICAgIHRoYXQgd2F5LCBidXQgeW91IGRvbpJ0IGhhdmUg
dG8uIFRoZSBwb2ludCBJIGFtIHRyeWluZyB0byBtYWtlIGlzIHRoYXQgdGhlIA0KICAgIGN1cnJl
bnQgbW9kZWwgd29ya3MgZm9yIHRoZSBzY2VuYXJpbyB5b3UgYXJlIGVudW1lcmF0aW5nLjxCUj48
L0RJVj4NCiAgICA8RElWPjxGT05UIGZhY2U9JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+RnJhbms9
Jmd0OyBkb24ndCB5b3UgdGhpbmsgdGhlIGNvbmNlcHQgb2YgdGhlIA0KICAgIHBlcmZpeCBpcyB0
b28gZmxleGlibGUgdGhhdCBkaWZmZXJlbnQgcGVvcGxlIGNhbiBoYXZlIHRoZWlyIG93biBkaWZm
ZXJlbnQgDQogICAgdW5kZXJzdGFuZGluZz8mbmJzcDsgSW4geW91ciBkcmFmdCwgdGhlIHByZWZp
eCBpcyBkZWZpbml0ZWx5IHRoZSBwcmVmaXggb2YgDQogICAgQVIgcGh5c2ljYWwgaW50ZXJmYWNl
LiBJIHRoaW5rIHRoZXJlIGlzIG5vdCBhbWJpZ3VvdXMuPC9GT05UPjxCUj48L0RJVj4NCiAgICA8
RElWPiZuYnNwOzwvRElWPg0KICAgIDxESVY+QW4gQVIgbWF5IHVzZSBwZXItbW9iaWxlIHByZWZp
eCBhbmQgYW4gYWdncmVnYXRlIHByZWZpeCBvbiB0aGUgDQogICAgaW50ZXJmYWNlLiBBcyBJIHNh
aWQsIGFnZ3JlZ2F0ZSBwcmVmaXggY291bGQgYmUgd2hhdCBpcyBhZHZlcnRpc2VkIGluIA0KICAg
IFByUnRBZHYuIFRoZSBNTiBjYW4gZm9ybXVsYXRlIGEgcHJvc3BlY3RpdmUgTkNvQSB1c2luZyB0
aGF0LCBidXQgcmVjZWl2ZSBhIA0KICAgIGRpZmZlcmVudCBOQ29BIGZyb20gTkFSLCBiYXNlZCBv
biB0aGUgcGVyLW1vYmlsZSBwcmVmaXguJm5ic3A7PC9ESVY+DQogICAgPERJVj5GcmFuayA9Jmd0
O0luIGZhY3QsJm5ic3A7IHRoaXMgaXMgbm90IGJpZyBkaWZmZXJlbnQgZnJvbSBvdXIgcHJvcHNv
YWwgDQogICAgaW4gZHJhZnQteGlhLW1pcHNob3AtZm1pcC1wdHAtMDAgPEJSPjxCUj5JIGNhbiBp
bWFnaW5lIG90aGVyIHdheXMgdG8gbWFuYWdlIA0KICAgIHRoZSBwcmVmaXguIDwvRElWPg0KICAg
IDxESVY+PEZPTlQgZmFjZT0mIzIzNDM1OyYjMjAzMDc7IHNpemU9Mj5GcmFuayA9Jmd0OyBJJm5i
c3A7IGFsc28gaGF2ZSBhIHJldmlzZWQgZG9jdW1lbnQgDQogICAgd2hpY2ggZWxhYm9yYXRpbmcg
b3RoZXIgYWx0ZXJuYXRpdmVzLCBhbmQgd2UgY2FuIGNvb3BlcmF0ZSANCiAgICAuPC9GT05UPjwv
RElWPjxGT05UIGZhY2U9JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+PC9GT05UPg0KICAgIDxESVY+
PEZPTlQgZmFjZT0mIzIzNDM1OyYjMjAzMDc7IHNpemU9Mj48L0ZPTlQ+PEZPTlQgZmFjZT0mIzIz
NDM1OyYjMjAzMDc7IHNpemU9Mj48L0ZPTlQ+PEZPTlQgZmFjZT0mIzIzNDM1OyYjMjAzMDc7IA0K
ICAgIHNpemU9Mj48L0ZPTlQ+PEJSPjxCUj48QlI+MiAiIFRocm91Z2ggdGhlIFJ0U29sUHIgYW5k
IFByUnRBZHYgbWVzc2FnZXMsIHRoZSANCiAgICBNTiBhbHNvIGZvcm11bGF0ZXMgYTxCUj4mbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDtwcm9zcGVjdGl2ZSBuZXcgQ29BIChOQ29BKSwgDQogICAgd2hl
biBpdCBpcyBzdGlsbCBwcmVzZW50IG9uIHRoZSBQQVInczxCUj4mbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDtsaW5rLiANCiAgICAmbmJzcDtIZW5jZSwgdGhlIGxhdGVuY3kgZHVlIHRvIG5ldyBwcmVm
aXggZGlzY292ZXJ5IHN1YnNlcXVlbnQgDQogICAgdG88QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7aGFuZG92ZXIgaXMgZWxpbWluYXRlZC4gJm5ic3A7RnVydGhlcm1vcmUsIA0KICAgIHRoaXMg
cHJvc3BlY3RpdmUgYWRkcmVzcyBjYW48QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7YmUgdXNl
ZCBpbW1lZGlhdGVseSANCiAgICBhZnRlciBhdHRhY2hpbmcgdG8gdGhlIG5ldyBzdWJuZXQgbGlu
ayANCiAgICAoaS5lLiw8QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7TkFSJ3MgbGluaykgd2hl
biB0aGUgTU4gaGFzIHJlY2VpdmVkIGEgDQogICAgIkZhc3QgQmluZGluZyBBY2tub3dsZWRnbWVu
dDxCUj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsoRkJhY2spIiBtZXNzYWdlIA0KICAgIHByaW9y
IHRvIGl0cyBtb3ZlbWVudC4gJm5ic3A7SW4gdGhlIGV2ZW50IGl0IA0KICAgIG1vdmVzPEJSPiZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwO3dpdGhvdXQgcmVjZWl2aW5nIGFuIEZCYWNrLCB0aGUgTU4g
Y2FuIA0KICAgIHN0aWxsIHN0YXJ0IHVzaW5nIE5Db0E8QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7YWZ0ZXIgYW5ub3VuY2luZyBpdHMgDQogICAgYXR0YWNobWVudCB0aHJvdWdoIGFuIHVuc29s
aWNpdGVkIA0KICAgIE5laWdoYm9yPEJSPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO0FkdmVydGlz
ZW1lbnQgbWVzc2FnZSAod2l0aCB0aGUgJ08nIGJpdCANCiAgICBzZXQgdG8gemVybykgbWVzc2Fn
ZSBbOF07PEJSPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO05BUiByZXNwb25kcyB0byB0byB0aGlz
IA0KICAgIFVOQSBtZXNzYWdlIGluIGNhc2UgdGhlIHRlbnRhdGl2ZSBhZGRyZXNzIA0KICAgIGlz
PEJSPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO2FscmVhZHkgaW4gdXNlLiAmbmJzcDtJbiB0aGlz
IHdheSwgTkNvQSANCiAgICBjb25maWd1cmF0aW9uIGxhdGVuY3kgaXMgcmVkdWNlZCI8QlI+PEJS
Pj0mZ3Q7aXMgaXQgbWVhbmluZ2Z1bCBmb3IgDQogICAgUC10by1QPzxCUj48QlI+UmFqZWV2OiZn
dDsgSWYgeW91ciBxdWVzdGlvbiBpcyB3aWxsIGl0IHdvcmsgd2l0aCBwZXItbW9iaWxlIA0KICAg
IHByZWZpeCwgeWVzLiBFaXRoZXIgRkJhY2sgb3IgTkFBQ0sgY2FuIHByb3ZpZGUgdGhlIE5Db0Eg
dGhhdCB0aGUgTkFSIHdhbnRzIA0KICAgIHRoZSBNTiB0byB1c2UuIDwvRElWPg0KICAgIDxESVY+
Jm5ic3A7PC9ESVY+DQogICAgPERJVj48Rk9OVCBmYWNlPSYjMjM0MzU7JiMyMDMwNzs+PEZPTlQg
c2l6ZT0yPkZyYW5rID0mZ3Q7IFRoZSBleGNoYW5nZSBvZiA8Rk9OVCANCiAgICBmYWNlPVZlcmRh
bmE+UnRTb2xQciBhbmQgUHJSdEFkdiBpcyB0byBmb3JtdWxhdGUgYSBuZXcgQ29BIHdoaWxlIGlz
IHVzZWxlc3MgDQogICAgaW4gcC10LXAgbW9kZWwuJm5ic3A7IEl0IGlzIGEgd2FzdGUgb2YgYWly
IGludGVyZmFjZSANCiAgICByZXNvdXJjZS48L0ZPTlQ+PC9GT05UPjwvRk9OVD48QlI+Li4uPEJS
PiZuYnNwOzxCUj5JbiBmYWN0IGFueSBwYXJ0cyByZWxhdGVkIA0KICAgIHRvIHRoZSBwcmVmaXgg
aXMgbm90IHByb3BlciBmb3IgcC10by1wIGxpbmsgbW9kZWwuPEJSPiZuYnNwOzxCUj5SYWplZXY6
Jmd0OyANCiAgICBUaGF0knMgYSBwcmV0dHkgYnJvYWQgc3RhdGVtZW50LiBZb3Ugc2hvdWxkIHNl
cGFyYXRlIHByZWZpeCBtYW5hZ2VtZW50IGZyb20gDQogICAgdGhlIGFkZHJlc3MgZm9ybXVsYXRp
b24uIElmIGFuIGFkZHJlc3MgaXMgZm9ybXVsYXRlZCB1c2luZyBhbiBhZ2dyZWdhdGUgDQogICAg
cHJlZml4ICh3aGljaCBOQVIgZXhjaGFuZ2VzIHdpdGggUEFSKSwgdGhlbiB0aGF0IGFkZHJlc3Mg
Y2FuIGJlIG92ZXJyaWRkZW4gDQogICAgZnJvbSB0aGUgTkFSIHVzaW5nIGEgcGVyLW1vYmlsZSBw
cmVmaXguIFJGQyA0MDY4IHByb3ZpZGVzIG1lYW5zIHRvIGRvIHRoaXMuIA0KICAgIDxCUj48QlI+
Jm5ic3A7PEJSPkJUVywgRnJvbSBteSB1bmRlcnN0YW5kaW5nLCB5b3VyIHByb3BzYWwgaXMgdGhh
dCB0aGUgb25seSANCiAgICB3YXkgZm9yIE1OIGdldHRpbmcgaXQncyBDb0E8QlI+TVVTVCBiZSBy
ZXF1ZXN0aW5nIGl0IGZyb20gTkFSIGZvciBQLXRvLVAgDQogICAgbGluay48QlI+Jm5ic3A7PEJS
PlJhamVldjomZ3Q7IEkgYW0ganVzdCBwb2ludGluZyBvdXQgaG93IHRoZSBjdXJyZW50IG1vZGVs
IA0KICAgIGluIDQwNjggY2FuIHdvcmsgZm9yIHlvdXIgc2NlbmFyaW8uIDwvRElWPg0KICAgIDxE
SVY+PEZPTlQgZmFjZT0mIzIzNDM1OyYjMjAzMDc7IHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+
DQogICAgPERJVj48Rk9OVCBmYWNlPSYjMjM0MzU7JiMyMDMwNzsgc2l6ZT0yPkZyYW5rID0mZ3Q7
IFAtdG8tUCBzY2VuYXJpbyBpcyBhZG9wdGVkIGJ5IA0KICAgIFdpTUFYLzNHUFAyLCZuYnNwO3do
aWxlJm5ic3A7SSBoYXZlJm5ic3A7bGl0dGxlJm5ic3A7aWRlYSBhYm91dCBwcm9taXNpbmcgDQog
ICAgZGVwbG95bWVudCBvZiZuYnNwO3NoYXJlZCBsaW5rIG1vZGVsLjwvRk9OVD48L0RJVj4NCiAg
ICA8RElWPjxGT05UIGZhY2U9JiMyMzQzNTsmIzIwMzA3OyBzaXplPTI+SU1ITywgeW91ciBzaW1w
bGlmaWVkIHByb3Bvc2FsIGNhbid0IHNvbHZlIHRoZSANCiAgICBwcm9wbGVtIHZlcnkgd2VsbC48
L0ZPTlQ+PC9TUEFOPjwvRk9OVD48L0RJVj48L0JMT0NLUVVPVEU+DQogIDxCTE9DS1FVT1RFPjxG
T05UIGZhY2U9IlZlcmRhbmEsIEhlbHZldGljYSwgQXJpYWwiPjxTUEFOIA0KICAgIHN0eWxlPSJG
T05ULVNJWkU6IDEycHgiPg0KICAgIDxESVY+PEJSPi1SYWplZXY8QlI+PEJSPiZuYnNwOzxCUj4m
bmJzcDs8QlI+QlI8QlI+RnJhbms8QlI+Jm5ic3A7PEJSPiZuYnNwOzxCUj4mbmJzcDs8QlI+Jm5i
c3A7PEJSPiZuYnNwOzxCUj4mbmJzcDs8QlI+Jm5ic3A7PEJSPiZuYnNwOzxCUj4mbmJzcDs8QlI+
Jm5ic3A7PEJSPiZuYnNwOzxCUj4mbmJzcDs8QlI+PC9ESVY+PC9TUEFOPjwvRk9OVD4NCiAgICA8
QkxPQ0tRVU9URT48Rk9OVCBmYWNlPSJWZXJkYW5hLCBIZWx2ZXRpY2EsIEFyaWFsIj48U1BBTiAN
CiAgICAgIHN0eWxlPSJGT05ULVNJWkU6IDEycHgiPjxCUj4tLS0tLSBPcmlnaW5hbCBNZXNzYWdl
IC0tLS0tIA0KICAgICAgPEJSPiZuYnNwOzxCUj48Qj5Gcm9tOjwvQj4gJm5ic3A7UmFqZWV2ICZu
YnNwO0tvb2RsaSA8QSANCiAgICAgIGhyZWY9Im1haWx0bzpyYWplZXYua29vZGxpQG5va2lhLmNv
bSI+Jmx0O21haWx0bzpyYWplZXYua29vZGxpQG5va2lhLmNvbSZndDs8L0E+IA0KICAgICAgJm5i
c3A7PEJSPiZuYnNwOzxCUj48Qj5Ubzo8L0I+IGhlZWppbi5qYW5nQHNhbXN1bmcuY29tIDsgRnJh
bmsgJm5ic3A7WGlhIA0KICAgICAgPEEgDQogICAgICBocmVmPSJtYWlsdG86eGlheWFuZ3NvbmdA
aHVhd2VpLmNvbSI+Jmx0O21haWx0bzp4aWF5YW5nc29uZ0BodWF3ZWkuY29tJmd0OzwvQT4gDQog
ICAgICAmbmJzcDs8QlI+Jm5ic3A7PEJSPjxCPkNjOjwvQj4gbWlwc2hvcEBpZXRmLm9yZyA7IDE2
bmdAaWV0Zi5vcmcgOyA/Pz8gPEEgDQogICAgICBocmVmPSJtYWlsdG86c29vaG9uZy5wYXJrQHNh
bXN1bmcuY29tIj4mbHQ7bWFpbHRvOnNvb2hvbmcucGFya0BzYW1zdW5nLmNvbSZndDs8L0E+IA0K
ICAgICAgJm5ic3A7Jm5ic3A7PEJSPiZuYnNwOzxCUj48Qj5TZW50OjwvQj4gTW9uZGF5LCBKdW5l
IDA0LCAyMDA3IDEyOjU2IA0KICAgICAgUE08QlI+Jm5ic3A7PEJSPjxCPlN1YmplY3Q6PC9CPiBS
ZTogW01pcHNob3BdIFJlOiBbMTZOR10gRlc6IENhbGwgDQogICAgICAmbmJzcDtmb3IgUmV2aWV3
IG9uIEZNSVA2IG92ZXIgSUVFRTgwMi4xNmUgDQogICAgICBOZXR3b3JrczxCUj4mbmJzcDs8QlI+
PEJSPjxCUj5BcyBmYXIgYXMgSSBzZWUsIHRoZXJlIGlzIG5vIHByb2JsZW0gDQogICAgICAmbmJz
cDtoZXJlITxCUj48QlI+SXQgZG9lcyBub3QgbWF0dGVyIHdoYXQgeW91IGNhbGwgdGhlIHByZWZp
eCBhZHZlcnRpc2VkIA0KICAgICAgaW4gJm5ic3A7UHJSdEFkdi4gUkZDIDQwNjggZG9lcyBub3Qg
bWFrZSBhc3N1bXB0aW9ucyBhYm91dCBob3cgdGhlIA0KICAgICAgcHJlZml4ZXMgYXJlICZuYnNw
O2Fzc2lnbmVkIGFuZCBtYW5hZ2VkIG9uIGFuIEFSknMgbGluay4gU28sIGl0IGlzIA0KICAgICAg
aW5hY2N1cmF0ZSB0byBzYXkgYXMgc3VjaCBpbiAmbmJzcDtkcmFmdC14aWEtbWlwc2hvcC1mbWlw
LXB0cC0wMC50eHQuIA0KICAgICAgPEJSPjxCUj5TbywgaWYgcHJlZml4IEEgaXMgYWR2ZXJ0aXNl
ZCBpbiAmbmJzcDtQclJ0QWR2LCBhbmQgYSBNTiANCiAgICAgIGZvcm11bGF0ZXMgYSBwcm9zcGVj
dGl2ZSBhZGRyZXNzIElQLUEgYW5kIHNlbmRzIEZCVSwgSVAtQSAmbmJzcDtjYW4gYmUgDQogICAg
ICBvdmVycmlkZGVuIGJ5IE5BUiBpbiBIQWNrLjxCUj48QlI+U2VjdGlvbiANCiAgICAgICZuYnNw
OzYuMi4yPEJSPjxCUj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtDb2RlIA0KICAgICAgJm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7MzogSGFuZG92ZXIg
QWNjZXB0ZWQsIE5Db0EgDQogICAgICAmbmJzcDthc3NpZ25lZDxCUj4mbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsodXNlZCANCiAgICAg
ICZuYnNwO2luIEFzc2lnbmVkIGFkZHJlc3NpbmcpPEJSPjxCUj48QlI+VGhlIHN1cHBsaWVkIE5D
b0EgaXMgcHJvdmlkZWQgaW4gDQogICAgICBGQmFjayBvciAmbmJzcDtOQUFDSyBvcHRpb24uPEJS
PjxCUj5UaGlzIGlzIHRoZSB3YXkgSSB1bmRlcnN0b29kIHRoZSANCiAgICAgIHByb2JsZW0gYW5k
IHRoZSBzb2x1dGlvbiAmbmJzcDtmb3IgcHRwIGxpbmtzLjxCUj48QlI+V2hhdCBhbSBJIA0KICAg
ICAgbWlzc2luZz88QlI+PEJSPi1SYWplZXY8QlI+PEJSPjxCUj48QlI+PEJSPk9uICZuYnNwOzYv
My8wNyA5OjQ0IFBNLCAiZXh0IA0KICAgICAgSGVlamluIEphbmciICZsdDtoZWVqaW4uamFuZ0Bz
YW1zdW5nLmNvbSZndDsgDQogICAgICAmbmJzcDt3cm90ZTo8QlI+PEJSPiZuYnNwOzxCUj48L1NQ
QU4+PC9GT05UPg0KICAgICAgPEJMT0NLUVVPVEU+PEZPTlQgZmFjZT0iVmVyZGFuYSwgSGVsdmV0
aWNhLCBBcmlhbCI+PFNQQU4gDQogICAgICAgIHN0eWxlPSJGT05ULVNJWkU6IDEycHgiPkhpLCBG
cmFuayAmYW1wOyBEYW5pZWwuPEJSPjxCUj5SRkM0MDY4IGRlc2NyaWJlcyANCiAgICAgICAgJm5i
c3A7ZmFzdCBITyBwcm9jZWR1cmUgYmFzZWQgb24gcHJlZGljdGlvbiwgaW5jbHVkaW5nIE5Db0Eg
Zm9ybXVsYXRpb24gDQogICAgICAgIGluICZuYnNwO2FkdmFuY2UuPEJSPkhvd2V2ZXIsIGhvdyB0
byBhbGxvY2F0ZSB0aGUgcHJlZml4IHRvIE1OIGluIE5BUiANCiAgICAgICAgKGJlZm9yZSBhY3R1
YWwgJm5ic3A7SE8pIGlzIG91dCBvZiBzY29wZSBpbiB0aGlzIGRvY3VtZW50PEJSPmFzIA0KICAg
ICAgICBtZW50aW9uZWQgaW4gU2VjdGlvbiAmbmJzcDs0LjxCUj48QlI+IlRoZSBtZXRob2QgYnkg
d2hpY2ggQWNjZXNzIFJvdXRlcnMgDQogICAgICAgIGV4Y2hhbmdlIGluZm9ybWF0aW9uIGFib3V0
ICZuYnNwO3RoZWlyIG5laWdoYm9ycywgYW5kIHRoZXJlYnkgDQogICAgICAgIGFsbG93PEJSPiZu
YnNwOyZuYnNwO2NvbnN0cnVjdGlvbiBvZiBQcm94eSAmbmJzcDtSb3V0ZXIgDQogICAgICAgICZu
YnNwO0FkdmVydGlzZW1lbnRzIHdpdGggaW5mb3JtYXRpb24gYWJvdXQgbmVpZ2hib3Jpbmcgc3Vi
bmV0cyBpcyANCiAgICAgICAgJm5ic3A7b3V0c2lkZTxCUj4mbmJzcDsmbmJzcDt0aGUgc2NvcGUg
b2YgdGhpcyANCiAgICAgICAgZG9jdW1lbnQuIjxCUj48QlI+RnVydGhlcm1vcmUsIHRoZSAmbmJz
cDtwcm9ibGVtIHlvdSBtZW50aW9uZWQgaW4gDQogICAgICAgIGRyYWZ0LXhpYS1taXBzaG9wLWZt
aXAtcHRwLTAwIGlzIG5vdCBsaW1pdGVkIG9ubHkgJm5ic3A7dG8gODAyLjE2IA0KICAgICAgICBu
ZXR3b3JrczxCUj5idXQgaGFwcGVucyBhbGwgbmV0d29ya3Mgd2hpY2ggaGF2ZSBwb2ludC10by1w
b2ludCANCiAgICAgICAgJm5ic3A7bGluayBzdWNoIGFzIDNHUFAyLjxCUj5JIHRoaW5rIHRoYXQg
aXQgaXMgcHJvcGVyIHRvIGhhbmRsZSB0aGlzIA0KICAgICAgICBwcm9ibGVtICZuYnNwO3NlcGFy
YXRlbHkuPEJSPjxCUj5UaGFua3MgZm9yIHlvdXIgb3Bpbmlvbi48QlI+PEJSPi0gDQogICAgICAg
ICZuYnNwO1JlZ2FyZHMsPEJSPkhlZWppbjxCUj48QlI+LS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdl
IA0KICAgICAgICAtLS0tLS0tPEJSPlNlbmRlciA6IEZyYW5rIA0KICAgICAgICAmbmJzcDtYaWEm
bHQ7eGlheWFuZ3NvbmdAaHVhd2VpLmNvbSZndDs8QlI+RGF0ZSAmbmJzcDsmbmJzcDs6IDIwMDct
MDYtMDEgDQogICAgICAgICZuYnNwOzA2OjUwPEJSPlRpdGxlICZuYnNwOzogW01pcHNob3BdIFJl
OiBbMTZOR10gRlc6IENhbGwgZm9yIFJldmlldyBvbiANCiAgICAgICAgRk1JUDYgJm5ic3A7b3Zl
ciBJRUVFIDgwMi4xNmUgJm5ic3A7Jm5ic3A7Jm5ic3A7TmV0d29ya3M8QlI+PEJSPkhpIA0KICAg
ICAgICBEYW5pZWw8QlI+PEJSPkhlcmUgaXMgJm5ic3A7bXkgdHdvIGNlbnRzLjxCUj48QlI+VGhl
IGRyYWZ0IGlzIGJhc2VkIG9uIA0KICAgICAgICBSRkM0MDY4LCBhbmQgcG9pbnQtdG8tcG9pbnQg
bGluayAmbmJzcDttb2RlbCBpcyBhbHNvIHJlY29tbWVuZGVkIA0KICAgICAgICAuPEJSPlJGQzQw
NjggaXMgYmFzZWQgb24gc2hhcmVkIGxpbmsgbW9kZWwsIGFuZCBpcyAmbmJzcDtub3QgYXBwbGlj
YWJsZSANCiAgICAgICAgZm9yIHBvaW50LXRvLXBvaW50IGxpbmsgbW9kZWwgd2l0aG91dCBtb2Rp
ZmljYXRpb24uPEJSPlNvLCANCiAgICAgICAgJm5ic3A7Jm5ic3A7dGhlcmUgYXJlIHNvbWUgYmFz
aWMgY29uZmxpY3RzIGluIHRoZSANCiAgICAgICAgZHJhZnQuPEJSPjxCUj5Gb3JtdWxhdGlvbiBv
ZiAmbmJzcDsmbmJzcDthIHByb3NwZWN0aXZlIE5Db0EgJm5ic3A7aXMgYSANCiAgICAgICAgbWFp
biBpZGVhIG9mICZuYnNwO1JGQzQwNjguPEJSPkJ1dCBpbiAmbmJzcDtQb2ludC10by1Qb2ludCBs
aW5rIG1vZGVsLCANCiAgICAgICAgaXQgaXMgaW1wb3NzaWJsZSB0byBmb3JtdWxhdGUgdGhlICZu
YnNwO05Db0E8QlI+YWNjb3JkaW5nIHRvIA0KICAgICAgICAmbmJzcDtSRkM0MDY4IGJlY2F1c2Ug
dGhlcmUgaXMgbm8gcHJvcGVyIA0KICAgICAgICAmbmJzcDtwcmVmaXguPEJSPjxCUj48QlI+QlI8
QlI+RnJhbms8QlI+PEJSPjxCUj4tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIA0KICAgICAgICAmbmJz
cDstLS0tLTxCUj5Gcm9tOiAiRGFuaWVsIFBhcmsiIA0KICAgICAgICAmbHQ7c29vaG9uZy5wYXJr
QHNhbXN1bmcuY29tJmd0OzxCUj5UbzogDQogICAgICAgICZuYnNwOyZsdDttaXBzaG9wQGlldGYu
b3JnJmd0OzxCUj5DYzogJmx0OzE2bmdAaWV0Zi5vcmcmZ3Q7PEJSPlNlbnQ6IA0KICAgICAgICBT
dW5kYXksIE1heSAmbmJzcDsyNywgMjAwNyA5OjM0IFBNPEJSPlN1YmplY3Q6IFsxNk5HXSBGVzog
Q2FsbCBmb3IgDQogICAgICAgIFJldmlldyBvbiBGTUlQNiBvdmVyIElFRUUgJm5ic3A7ODAyLjE2
ZSBOZXR3b3JrczxCUj48QlI+PEJSPiZndDsgVG8gDQogICAgICAgIE1JUFNIT1AgV0csPEJSPiZn
dDs8QlI+Jmd0OyBIZXJlIGlzICZuYnNwO2Fub3RoZXIgZXhwZXJ0IHJldmlldyBvbiANCiAgICAg
ICAgImRyYWZ0LWlldGYtbWlwc2hvcC1maDgwMjE2ZS0wMSIsPEJSPiZndDsgJm5ic3A7cGFydGlj
dWxhcmx5LCBJRUVFIA0KICAgICAgICA4MDIuMjEgcmVsZXZhbnQgdGV4dHMgaW4gdGhpcyBkcmFm
dC48QlI+Jmd0OzxCUj4mZ3Q7ICZuYnNwO1Jldmlld2VyIA0KICAgICAgICAoWW9zaGloaXJvIE9o
YmEpIGlzIGEgSUVURiBvZmZpY2lhbCBsaWFpc29uIGZyb20gSUVFRSANCiAgICAgICAgJm5ic3A7
ODAyLjIxPEJSPiZndDs8QlI+Jmd0OyBUaGFua3MgWW9zaGloaXJvIGFuZCBob3BlIHRoaXMgDQog
ICAgICAgICZuYnNwO2hlbHBzLi4uPEJSPiZndDs8QlI+Jmd0OzxCUj4mZ3Q7IC0tLS08QlI+Jmd0
OzxCUj4mZ3Q7IERhbmllbCBQYXJrIA0KICAgICAgICAmYW1wOyAmbmJzcDtHYWJyaWVsIE1vbnRl
bmVncm88QlI+Jmd0OyBDaGFpcnMsIDE2TkcgV29ya2luZyANCiAgICAgICAgJm5ic3A7R3JvdXA8
QlI+Jmd0OzxCUj48QlI+PEJSPi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPEJSPjxCUj48QlI+Jmd0
OyANCiAgICAgICAgJm5ic3A7X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX188QlI+Jmd0OyAxNk5HIA0KICAgICAgICBtYWlsaW5nICZuYnNwO2xpc3Q8QlI+Jmd0
OyAxNk5HQGlldGYub3JnPEJSPiZndDsgDQogICAgICAgICZuYnNwO2h0dHBzOi8vd3d3MS5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvLzE2bmc8QlI+Jmd0OzxCUj48QlI+X19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188QlI+TWlwc2hvcCANCiAgICAgICAgJm5i
c3A7bWFpbGluZyANCiAgICAgICAgJm5ic3A7bGlzdDxCUj5NaXBzaG9wQGlldGYub3JnPEJSPmh0
dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21pcHNob3A8QlI+PEJSPjxCUj48
QlI+PC9TUEFOPjwvRk9OVD48L0JMT0NLUVVPVEU+PEZPTlQgDQogICAgICBmYWNlPSJWZXJkYW5h
LCBIZWx2ZXRpY2EsIEFyaWFsIj48U1BBTiBzdHlsZT0iRk9OVC1TSVpFOiAxMnB4Ij48QlI+PEJS
Pi0tIA0KICAgICAgJm5ic3A7PEJSPjxBIA0KICAgICAgaHJlZj0iaHR0cDovL3Blb3BsZS5ub2tp
YS5uZXQvfnJhamVldiI+aHR0cDovL3Blb3BsZS5ub2tpYS5uZXQvfnJhamVldjwvQT4gDQogICAg
ICAmbmJzcDs8QlI+PEJSPjxCUj48L1NQQU4+PC9GT05UPjwvQkxPQ0tRVU9URT48Rk9OVCANCiAg
ICBmYWNlPSJWZXJkYW5hLCBIZWx2ZXRpY2EsIEFyaWFsIj48U1BBTiANCiAgICBzdHlsZT0iRk9O
VC1TSVpFOiAxMnB4Ij48QlI+PC9TUEFOPjwvRk9OVD48L0JMT0NLUVVPVEU+PEZPTlQgDQogIGZh
Y2U9IlZlcmRhbmEsIEhlbHZldGljYSwgQXJpYWwiPjxTUEFOIHN0eWxlPSJGT05ULVNJWkU6IDEy
cHgiPjxCUj48QlI+LS0gDQogIDxCUj48QSANCiAgaHJlZj0iaHR0cDovL3Blb3BsZS5ub2tpYS5u
ZXQvfnJhamVldiI+aHR0cDovL3Blb3BsZS5ub2tpYS5uZXQvfnJhamVldjwvQT4gDQogIDxCUj48
QlI+PEJSPjwvQkxPQ0tRVU9URT48L1NQQU4+PC9GT05UPjwvQk9EWT48L0hUTUw+DQo=

--Boundary_(ID_66aTj510MVpgtG017jL78A)--



--===============1965355676==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng

--===============1965355676==--





From 16ng-bounces@ietf.org Mon Jun 04 17:08:22 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvJmo-0005wb-6D; Mon, 04 Jun 2007 17:08:22 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1HvJmm-0005rG-1v
	for 16ng-confirm+ok@megatron.ietf.org; Mon, 04 Jun 2007 17:08:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvJml-0005r8-OW; Mon, 04 Jun 2007 17:08:19 -0400
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvJmj-0007ox-VP; Mon, 04 Jun 2007 17:08:19 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l54L7grx014973; Tue, 5 Jun 2007 00:08:07 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 5 Jun 2007 00:08:05 +0300
Received: from daebe103.NOE.Nokia.com ([10.241.35.24]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Jun 2007 16:08:02 -0500
Received: from 10.241.32.11 ([10.241.32.11]) by daebe103.NOE.Nokia.com
	([10.241.35.24]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon,  4 Jun 2007 21:08:02 +0000
User-Agent: Microsoft-Entourage/11.2.4.060510
Date: Mon, 04 Jun 2007 14:08:36 -0700
Subject: Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over
	IEEE802.16e Networks
From: Rajeev Koodli <rajeev.koodli@nokia.com>
To: ext Frank Xia <xiayangsong@huawei.com>, <heejin.jang@samsung.com>
Message-ID: <C289CD64.12163%rajeev.koodli@nokia.com>
Thread-Topic: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over
	IEEE802.16e Networks
Thread-Index: Acem7IP5wnpjqBLfEdyeUQAWy5YJpw==
In-Reply-To: <001901c7a6e8$92a5ee80$380c7c0a@china.huawei.com>
Mime-version: 1.0
X-OriginalArrivalTime: 04 Jun 2007 21:08:02.0804 (UTC)
	FILETIME=[70301340:01C7A6EC]
X-Nokia-AV: Clean
X-Spam-Score: 0.5 (/)
X-Scan-Signature: bcd240e64c427d3d3617cfc704e7fd7f
Cc: mipshop@ietf.org, 16ng@ietf.org
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1142812905=="
Errors-To: 16ng-bounces@ietf.org

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============1142812905==
Content-type: multipart/alternative;
	boundary="B_3263810916_31484872"

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3263810916_31484872
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable


Hi Frank,

May be we are going in circles here.. I have not seen why the current model
cannot work for the scenario you have in mind. If there is an issue, the WG
process is to bring it up and propose text. It=B9s more productive that way. =
I
am willing to clarify in the bis version. Some more replies below..
=20
>>>=20
>>> 1 "(AP-ID, AR-Info) tuple Contains an access router's L2 and IP  addres=
ses,
>>> and
>>>   prefix valid on the interface to which the  Access Point (identified =
by
>>> AP-ID) is attached.
>>>  The triplet  [Router's  L2 address, Router's IP address and Prefix] is
>>> called  "AR-Info"".
>>> =20
>>> =3D> Here, prefix is AR's physical interface  prefix is used for NCoA
>>> formulation.
>>>   As you know, this prefix  is useless for P-to-P link model.
>>>=20
>>> Rajeev:> you could interpret it  that way, but you don=B9t have to. The p=
oint
>>> I am trying to make is that the  current model works for the scenario y=
ou
>>> are enumerating.
>>> =20
>>> Frank=3D> don't you think the concept of the  perfix is too flexible that
>>> different people can have their own different  understanding?  In your
>>> draft, the prefix is definitely the prefix of  AR physical interface. I
>>> think there is not ambiguous.
>>>=20
>>> Rajeev/2/:> First, it is not my draft; it is the WG document. Second, i=
t is
>>> not clear to me why you would equate the prefix to physical interface. =
4068
>>> only says it is the prefix valid on the interface the MN is attaching t=
o,
>>> and I am unable to see what=B9s the problem.
>>>=20
>>> If you are trying to map it to ptp model, that=B9s fine. But, please don=B9=
t
>>> make assumptions which not intended, nor are necessary.
>>> =20
>>> =20
>>> An AR may use per-mobile prefix and an aggregate prefix on the  interfa=
ce.
>>> As I said, aggregate prefix could be what is advertised in  PrRtAdv. Th=
e MN
>>> can formulate a prospective NCoA using that, but receive a  different N=
CoA
>>> from NAR, based on the per-mobile prefix.
>>> =20
>>> Frank =3D>In fact,  this is not big different from our propsoal  in
>>> draft-xia-mipshop-fmip-ptp-00
>>>=20
>>> Rajeev:/2/> I am not proposing a new model above. Just showing how the
>>> existing model can be used.
>>>=20
>>> I can imagine other ways to manage  the prefix.
>>> =20
>>> Frank =3D> I  also have a revised document  which elaborating other
>>> alternatives, and we can cooperate  .
>>>=20
>>> Rajeev:> If your question is will it work with per-mobile  prefix, yes.
>>> Either FBack or NAACK can provide the NCoA that the NAR wants  the MN t=
o
>>> use.=20
>>>   =20
>>> Frank =3D> The exchange of RtSolPr and PrRtAdv is to formulate a new CoA =
while
>>> is useless  in p-t-p model.  It is a waste of air interface  resource.
>>>=20
>>> Rajeev:/2/> That=B9s debatable, and is up to each technology that impleme=
nts
>>> FMIP.=20
>>> =20
>>> =20
>>> Frank =3D> P-to-P scenario is adopted by  WiMAX/3GPP2, while I have littl=
e
>>> idea about promising  deployment of shared link model.
>>>=20
>>> Rajeev:/2/> Good.  RFC 4068 is not about shared link only. It=B9s your
>>> interpretation.
>>> =20
>>> IMHO, your simplified proposal can't solve the  proplem very well.
> =20
>                Rajeev:/2/> You have not shown why my explanation on how t=
he
> current model can work will not  work. As I suggested earlier, if there i=
s any
> specific issue that needs to be addressed, it is productive to propose th=
e
> issue and text.=20
>=20
> -Rajeev
>=20
>> =20
>>=20
--=20
http://people.nokia.net/~rajeev




--B_3263810916_31484872
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE802.1=
6e Networks</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:12.0px'><BR>
Hi Frank,<BR>
<BR>
May be we are going in circles here.. I have not seen why the current model=
 cannot work for the scenario you have in mind. If there is an issue, the WG=
 process is to bring it up and propose text. It&#8217;s more productive that=
 way. I am willing to clarify in the bis version. Some more replies below..<=
BR>
&nbsp;<BR>
</SPAN></FONT><BLOCKQUOTE><BLOCKQUOTE><BLOCKQUOTE><FONT FACE=3D"Verdana, Helv=
etica, Arial"><SPAN STYLE=3D'font-size:12.0px'><BR>
1 &quot;(AP-ID, AR-Info) tuple Contains an access router's L2 and IP &nbsp;=
addresses, and<BR>
&nbsp;&nbsp;prefix valid on the interface to which the &nbsp;Access Point (=
identified by AP-ID) is attached. &nbsp;<BR>
&nbsp;The triplet &nbsp;[Router's &nbsp;L2 address, Router's IP address and=
 Prefix] is called &nbsp;&quot;AR-Info&quot;&quot;.<BR>
&nbsp;<BR>
=3D&gt; Here, prefix is AR's physical interface &nbsp;prefix is used for NCoA=
 formulation.<BR>
&nbsp;&nbsp;As you know, this prefix &nbsp;is useless for P-to-P link model=
.<BR>
<BR>
Rajeev:&gt; you could interpret it &nbsp;that way, but you don&#8217;t have=
 to. The point I am trying to make is that the &nbsp;current model works for=
 the scenario you are enumerating.<BR>
&nbsp;<BR>
Frank=3D&gt; don't you think the concept of the &nbsp;perfix is too flexible =
that different people can have their own different &nbsp;understanding? &nbs=
p;In your draft, the prefix is definitely the prefix of &nbsp;AR physical in=
terface. I think there is not ambiguous.<BR>
<BR>
Rajeev/2/:&gt; First, it is <I>not</I> my draft; it is the WG document. Sec=
ond, it is not clear to me why you would equate the prefix to physical inter=
face. 4068 only says it is the prefix valid on the interface the MN is attac=
hing to, and I am unable to see what&#8217;s the problem.<BR>
<BR>
If you are trying to map it to ptp model, that&#8217;s fine. But, please do=
n&#8217;t make assumptions which not intended, nor are necessary.<BR>
&nbsp;<BR>
&nbsp;<BR>
An AR may use per-mobile prefix and an aggregate prefix on the &nbsp;interf=
ace. As I said, aggregate prefix could be what is advertised in &nbsp;PrRtAd=
v. The MN can formulate a prospective NCoA using that, but receive a &nbsp;d=
ifferent NCoA from NAR, based on the per-mobile prefix. <BR>
&nbsp;<BR>
Frank =3D&gt;In fact, &nbsp;this is not big different from our propsoal &nbsp=
;in draft-xia-mipshop-fmip-ptp-00 <BR>
<BR>
Rajeev:/2/&gt; I am not proposing a new model above. Just showing how the e=
xisting model can be used.<BR>
<BR>
I can imagine other ways to manage &nbsp;the prefix. <BR>
&nbsp;<BR>
Frank =3D&gt; I &nbsp;also have a revised document &nbsp;which elaborating ot=
her alternatives, and we can cooperate &nbsp;.<BR>
<BR>
Rajeev:&gt; If your question is will it work with per-mobile &nbsp;prefix, =
yes. Either FBack or NAACK can provide the NCoA that the NAR wants &nbsp;the=
 MN to use. <BR>
&nbsp;&nbsp;&nbsp;<BR>
Frank =3D&gt; The exchange of RtSolPr and PrRtAdv is to formulate a new CoA w=
hile is useless &nbsp;in p-t-p model. &nbsp;It is a waste of air interface &=
nbsp;resource.<BR>
<BR>
Rajeev:/2/&gt; That&#8217;s debatable, and is up to each technology that im=
plements FMIP. <BR>
&nbsp;<BR>
&nbsp;<BR>
Frank =3D&gt; P-to-P scenario is adopted by &nbsp;WiMAX/3GPP2, while I have l=
ittle idea about promising &nbsp;deployment of shared link model.<BR>
<BR>
Rajeev:/2/&gt; Good. &nbsp;RFC 4068 is not about shared link only. It&#8217=
;s your interpretation. <BR>
&nbsp;<BR>
IMHO, your simplified proposal can't solve the &nbsp;proplem very well.<BR>
</SPAN></FONT></BLOCKQUOTE></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Ari=
al"><SPAN STYLE=3D'font-size:12.0px'> <BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;Rajeev:/2/&gt; You have not shown why my explanation on how t=
he current model can work will not &nbsp;work. As I suggested earlier, if th=
ere is any specific issue that needs to be addressed, it is productive to pr=
opose the issue and text. <BR>
<BR>
-Rajeev<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'> <BR>
<BR>
</SPAN></FONT></BLOCKQUOTE></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Ari=
al"><SPAN STYLE=3D'font-size:12.0px'>-- <BR>
<a href=3D"http://people.nokia.net/~rajeev">http://people.nokia.net/~rajeev</=
a> <BR>
<BR>
<BR>
</SPAN></FONT>
</BODY>
</HTML>


--B_3263810916_31484872--




--===============1142812905==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng

--===============1142812905==--






From 16ng-bounces@ietf.org Tue Jun 05 15:04:13 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HveKC-0003l9-PL; Tue, 05 Jun 2007 15:04:12 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1HveKB-0003l4-Lc
	for 16ng-confirm+ok@megatron.ietf.org; Tue, 05 Jun 2007 15:04:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HveKB-0003kw-C4
	for 16ng@ietf.org; Tue, 05 Jun 2007 15:04:11 -0400
Received: from an-out-0708.google.com ([209.85.132.248])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HveKA-0006NN-5i
	for 16ng@ietf.org; Tue, 05 Jun 2007 15:04:11 -0400
Received: by an-out-0708.google.com with SMTP id c17so442072anc
	for <16ng@ietf.org>; Tue, 05 Jun 2007 12:04:09 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=HabhD391ht7dyqheAFekBBWXasqu/s0O5nW7PT283txfnetIFL4dDbj7p8xom7SNhtDEevPtJ7HAohgmLrBaCe9AOs2U2QEET15Y9w1RHbHYWV14Nt8W3X8FXTELr7rh8sJV0VftO3egQH7Wo3GrXVzumm2FyVYXstDwpUoXL4A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=I5rLZHj7KWgScHqGewnOEFfliCRwxULURNAHw+qBQb36FUrzfOZNrTe2+K0B1BDqy7qDSfMEzGj1V9HZM9hMWb/vYwiO+CuOIwx8Juy5Xxc065PXGApldALK7+Lg+iGEDwTlkKGB5B2JyIgcJyCYkQHEHlPsC0HWFxl1ute39nc=
Received: by 10.100.32.1 with SMTP id f1mr3543856anf.1181070217930;
	Tue, 05 Jun 2007 12:03:37 -0700 (PDT)
Received: by 10.100.111.15 with HTTP; Tue, 5 Jun 2007 12:03:37 -0700 (PDT)
Message-ID: <dde9f3ed0706051203i2d907654v3fbbbeca3cd00de7@mail.gmail.com>
Date: Tue, 5 Jun 2007 15:03:37 -0400
From: "Denio Mariz" <deniomariz@gmail.com>
To: 16ng@ietf.org
In-Reply-To: <dde9f3ed0706051201i21879de2ic8ee3d2ea9a00e98@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <dde9f3ed0706051201i21879de2ic8ee3d2ea9a00e98@mail.gmail.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Subject: [16NG] IEEE 802.16 QoS parameters
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: denio@gprt.ufpe.br
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org

Hi,

IEEE 802.16-2004 document defines some QoS parameters for admitted
connections, which includes maximum latency and maximum jitter. They
are defined as:

=======
Maximum latency - The value of this parameter specifies the maximum
latency between the reception of a packet by the BS or SS on its
network interface and the forwarding of the packet to its RF
Interface.

Maximum Jitter - This parameter defines the maximum delay variation
(jitter) for the connection.
======

Assuming D1 and D2 as the delay measured for two consecutive packets,
it is common for end-to-end systems to compute the jitter J as
J=|D1-D2|.

I am studying a scheduling algorithms for the download, which must run
inside the BS. This means that D1 and D2 are not available (or must be
avoided, since it would depend on measuring them at the mobile
terminal). So I am assuming that the algorithm must only consider
information from inside the BS (more specifically from queue
statistics).

So, I am wondering if it is possible to compute correctly the jitter
for packets assuming you can not watch the receiving end of the stream
and only consider info from the sender side.

TIA,

Denio Mariz


_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng



From 16ng-bounces@ietf.org Tue Jun 05 16:02:42 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvfEm-0001NF-4o; Tue, 05 Jun 2007 16:02:40 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1HveHg-0002Wu-HW
	for 16ng-confirm+ok@megatron.ietf.org; Tue, 05 Jun 2007 15:01:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HveHg-0002Wm-7u
	for 16ng@ietf.org; Tue, 05 Jun 2007 15:01:36 -0400
Received: from wr-out-0506.google.com ([64.233.184.229])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HveHf-0005Nu-06
	for 16ng@ietf.org; Tue, 05 Jun 2007 15:01:36 -0400
Received: by wr-out-0506.google.com with SMTP id m59so1270291wrm
	for <16ng@ietf.org>; Tue, 05 Jun 2007 12:01:34 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:reply-to:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth;
	b=i9LmATr/atSONyqUAhWqKfNpeiVXY6pDSKhlgzBqHS90Crq0Ve83zJ8FAClbOVFy92SXdTTQdkIzjRanGIP0flWauCJ+89uV4x9prRFZzNemKGnUZxe7Ly2U3/C57L10blM11Wy8qBInwMcc2w0npbP3VDsPAMDCebzRsQJcTl8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:reply-to:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth;
	b=bp+F4yEXlPxg1pyPMzmpqkFiibs6898K6fMW9uLXKtM4gJ8aLX03ihxq+RCcSODmUBCfm61Wx4sQaffBxXqnuOdZSrdfYFTBV8GU7mHIMPFduh2RNn1msr7hwVI/qq0eVPjonYyZ1sZHNGnY4R4Ed+pHg3TSyhfSlNZiAnpej5s=
Received: by 10.100.132.16 with SMTP id f16mr3507893and.1181070094128;
	Tue, 05 Jun 2007 12:01:34 -0700 (PDT)
Received: by 10.100.111.15 with HTTP; Tue, 5 Jun 2007 12:01:33 -0700 (PDT)
Message-ID: <dde9f3ed0706051201i21879de2ic8ee3d2ea9a00e98@mail.gmail.com>
Date: Tue, 5 Jun 2007 15:01:33 -0400
From: "Denio Mariz" <denio@gprt.ufpe.br>
To: 16ng@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Google-Sender-Auth: ac07fa0e4ff1ac77
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
X-Mailman-Approved-At: Tue, 05 Jun 2007 16:02:39 -0400
Subject: [16NG] IEEE 802.16 QoS parameters
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: denio@gprt.ufpe.br
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org

Hi,

IEEE 802.16-2004 document defines some QoS parameters for admitted
connections, which includes maximum latency and maximum jitter. They
are defined as:

=======
Maximum latency - The value of this parameter specifies the maximum
latency between the reception of a packet by the BS or SS on its
network interface and the forwarding of the packet to its RF
Interface.

Maximum Jitter - This parameter defines the maximum delay variation
(jitter) for the connection.
======

Assuming D1 and D2 as the delay measured for two consecutive packets,
it is common for end-to-end systems to compute the jitter J as
J=|D1-D2|.

I am studying a scheduling algorithms for the download, which must run
inside the BS. This means that D1 and D2 are not available (or must be
avoided, since it would depend on measuring them at the mobile
terminal). So I am assuming that the algorithm must only consider
information from inside the BS (more specifically from queue
statistics).

So, I am wondering if it is possible to compute correctly the jitter
for packets assuming you can not watch the receiving end of the stream
and only consider info from the sender side.

TIA,

Denio Mariz


_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng



From 16ng-bounces@ietf.org Thu Jun 07 22:44:09 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwUSO-0007xm-JY; Thu, 07 Jun 2007 22:44:08 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1HwUSN-0007xZ-IF
	for 16ng-confirm+ok@megatron.ietf.org; Thu, 07 Jun 2007 22:44:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwUSN-0007xJ-68; Thu, 07 Jun 2007 22:44:07 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HwUSL-0002Nq-Ft; Thu, 07 Jun 2007 22:44:07 -0400
Received: from ep_ms5_bk (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0JJA00EXQQ9F2N@mailout2.samsung.com>; Fri,
	08 Jun 2007 11:44:03 +0900 (KST)
Received: from ep_spt01 (ms5.samsung.com [203.254.225.113])
	by ms5.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004)) with ESMTP id <0JJA0083RQ9FH8@ms5.samsung.com>; Fri,
	08 Jun 2007 11:44:03 +0900 (KST)
Content-return: prohibited
Date: Fri, 08 Jun 2007 02:44:03 +0000 (GMT)
From: Heejin Jang <heejin.jang@samsung.com>
Subject: Re: Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over
	IEEE802.16e Networks
To: Rajeev Koodli <rajeev.koodli@nokia.com>
Message-id: <19669439.2195001181270643561.JavaMail.weblogic@ep_ml24>
MIME-version: 1.0
MIME-version: 1.0
X-Priority: 3
Msgkey: 20070608024403559@heejin.jang
X-MTR: 20070608024403559@heejin.jang
X-EPLocale: ko_KR.windows-1252
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
X-EPApproval-Locale: 
X-Spam-Score: 2.1 (++)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: "mipshop@ietf.org" <mipshop@ietf.org>, "16ng@ietf.org" <16ng@ietf.org>
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: heejin.jang@samsung.com
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1480876244=="
Errors-To: 16ng-bounces@ietf.org

--===============1480876244==
Content-return: prohibited
Content-type: text/plain; charset=windows-1252
Content-transfer-encoding: base64

SGksIEZyYW5rDQoNCkkgYWdyZWUgd2l0aCBSYWplZXYuICAgIA0KICAgICANClJGQzQwNjggaXMg
bm90IGxpbWl0ZWQgb25seSB0byB0aGUgc2hhcmVkIGxpbmsgbW9kZWwgYmVjYXVzZSB0aGUgcDJw
IHByZWZpeCBhbGxvY2F0aW9uICAgICANCihwZXItTU4gcHJlZml4IG1vZGVsKSBjYW4gYmUgYXBw
bGllZCB3aXRob3V0IGFueSBtb2RpZmljYXRpb24gb2YgUkZDNDA2OCBpbiB0aGUgcG9pbnQtdG8t
cG9pbnQgbGluay4gICAgIA0KSXQgY2FuIGJlIGRvbmUgTkNvQSBhbGxvY2F0aW9uIHZpYSBCQWNr
ICYgTkFBQ0sgYXMgeW91IGFuZCBSYWplZXYgc3VnZ2VzdGVkLCBvciAgICAgDQpQQVIncyBBZG1p
bmlzdHJhdG9yIG1heSBkZWNpZGUgdG8gbWFuYWdlIGEgcGFydCBvZiAgSVB2NiBwcmVmaXggcG9v
bCBvZiBOQVIgZm9yIGFsbG9jYXRpb24gaWYgZmVhc2libGUuICAgIA0KKEkgdGhpbmsgdGhhdCdz
IG5vdCBhIHdhc3RlIG9mIHByZWZpeGVzIHdoZXJlIHRoZSBwcmVmaXggaXMgYXNzaWduZWQgInBl
ciBNTiIgaW4gdGhlIChJUHY2KSBwb2ludC10by1wb2ludCBsaW5rLjopICkgICAgDQogICAgIA0K
U29tZSBtZW50aW9uIG1heSBuZWVkIHRvIGJlIHJlZmxlY3RlZCBpbiA0MDY4LWJpcywgZm9yIGUu
Zy4sIDEpIFJ0U29sUHIgJiBQclJ0QWR2IGV4Y2hhbmdlcywNCjIpIFByb3h5aW5nIE5Db0Egd2l0
aCBwcm94eSBuZWlnaGJvciBjYWNoZSBlbnRyeSBpbiBOQVJhbmQgMykgREFEIGNoZWNrLCBzb21l
IG9yIGFsbCBvZiB0aGVzZSBwcm9jZWR1cmVzDQptYXkgYmUgb21pdHRlZCBpbiB0aGUgcG9pbnQt
dG8tcG9pbnQgbGluay4gICAgDQoNCkJ1dCBJIGRvbid0IHRoaW5rIGl0J3MgYSBuZXcgbW9kZWwg
YnV0IGEgd2F5IG9mIGhvdyB0aGUgZXhpc3RpbmcgZm1pcHY2IGNhbiBiZSBhcHBsaWVkIG92ZXIg
dGhlIHBvaW50LXRvLXBvaW50IGxpbmsuICAgICAgICAgDQogICAgIA0KLSBSZWdhcmRzLCANCkhl
ZWppbi4gDQoNCi0tLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLS0tDQpTZW5kZXIgOiBSYWpl
ZXYgS29vZGxpPHJhamVldi5rb29kbGlAbm9raWEuY29tPg0KRGF0ZSAgIDogMjAwNy0wNi0wNSAw
NjowOA0KVGl0bGUgIDogUmU6IFtNaXBzaG9wXSBSZTogWzE2TkddIEZXOiBDYWxsIGZvciBSZXZp
ZXcgb24gRk1JUDYgb3ZlciBJRUVFODAyLjE2ZSBOZXR3b3Jrcw0KDQoNCkhpIEZyYW5rLA0KDQpN
YXkgYmUgd2UgYXJlIGdvaW5nIGluIGNpcmNsZXMgaGVyZS4uIEkgaGF2ZSBub3Qgc2VlbiB3aHkg
dGhlIGN1cnJlbnQgbW9kZWwgY2Fubm90IHdvcmsgZm9yIHRoZSBzY2VuYXJpbyB5b3UgaGF2ZSBp
biBtaW5kLiBJZiB0aGVyZSBpcyBhbiBpc3N1ZSwgdGhlIFdHIHByb2Nlc3MgaXMgdG8gYnJpbmcg
aXQgdXAgYW5kIHByb3Bvc2UgdGV4dC4gSXQmIzgyMTc7cyBtb3JlIHByb2R1Y3RpdmUgdGhhdCB3
YXkuIEkgYW0gd2lsbGluZyB0byBjbGFyaWZ5IGluIHRoZSBiaXMgdmVyc2lvbi4gU29tZSBtb3Jl
IHJlcGxpZXMgYmVsb3cuLg0KIA0KDQoxICIoQVAtSUQsIEFSLUluZm8pIHR1cGxlIENvbnRhaW5z
IGFuIGFjY2VzcyByb3V0ZXIncyBMMiBhbmQgSVAgIGFkZHJlc3NlcywgYW5kDQogIHByZWZpeCB2
YWxpZCBvbiB0aGUgaW50ZXJmYWNlIHRvIHdoaWNoIHRoZSAgQWNjZXNzIFBvaW50IChpZGVudGlm
aWVkIGJ5IEFQLUlEKSBpcyBhdHRhY2hlZC4gIA0KIFRoZSB0cmlwbGV0ICBbUm91dGVyJ3MgIEwy
IGFkZHJlc3MsIFJvdXRlcidzIElQIGFkZHJlc3MgYW5kIFByZWZpeF0gaXMgY2FsbGVkICAiQVIt
SW5mbyIiLg0KIA0KPT4gSGVyZSwgcHJlZml4IGlzIEFSJ3MgcGh5c2ljYWwgaW50ZXJmYWNlICBw
cmVmaXggaXMgdXNlZCBmb3IgTkNvQSBmb3JtdWxhdGlvbi4NCiAgQXMgeW91IGtub3csIHRoaXMg
cHJlZml4ICBpcyB1c2VsZXNzIGZvciBQLXRvLVAgbGluayBtb2RlbC4NCg0KUmFqZWV2Oj4geW91
IGNvdWxkIGludGVycHJldCBpdCAgdGhhdCB3YXksIGJ1dCB5b3UgZG9uJiM4MjE3O3QgaGF2ZSB0
by4gVGhlIHBvaW50IEkgYW0gdHJ5aW5nIHRvIG1ha2UgaXMgdGhhdCB0aGUgIGN1cnJlbnQgbW9k
ZWwgd29ya3MgZm9yIHRoZSBzY2VuYXJpbyB5b3UgYXJlIGVudW1lcmF0aW5nLg0KIA0KRnJhbms9
PiBkb24ndCB5b3UgdGhpbmsgdGhlIGNvbmNlcHQgb2YgdGhlICBwZXJmaXggaXMgdG9vIGZsZXhp
YmxlIHRoYXQgZGlmZmVyZW50IHBlb3BsZSBjYW4gaGF2ZSB0aGVpciBvd24gZGlmZmVyZW50ICB1
bmRlcnN0YW5kaW5nPyAgSW4geW91ciBkcmFmdCwgdGhlIHByZWZpeCBpcyBkZWZpbml0ZWx5IHRo
ZSBwcmVmaXggb2YgIEFSIHBoeXNpY2FsIGludGVyZmFjZS4gSSB0aGluayB0aGVyZSBpcyBub3Qg
YW1iaWd1b3VzLg0KDQpSYWplZXYvMi86PiBGaXJzdCwgaXQgaXMgbm90IG15IGRyYWZ0OyBpdCBp
cyB0aGUgV0cgZG9jdW1lbnQuIFNlY29uZCwgaXQgaXMgbm90IGNsZWFyIHRvIG1lIHdoeSB5b3Ug
d291bGQgZXF1YXRlIHRoZSBwcmVmaXggdG8gcGh5c2ljYWwgaW50ZXJmYWNlLiA0MDY4IG9ubHkg
c2F5cyBpdCBpcyB0aGUgcHJlZml4IHZhbGlkIG9uIHRoZSBpbnRlcmZhY2UgdGhlIE1OIGlzIGF0
dGFjaGluZyB0bywgYW5kIEkgYW0gdW5hYmxlIHRvIHNlZSB3aGF0JiM4MjE3O3MgdGhlIHByb2Js
ZW0uDQoNCklmIHlvdSBhcmUgdHJ5aW5nIHRvIG1hcCBpdCB0byBwdHAgbW9kZWwsIHRoYXQmIzgy
MTc7cyBmaW5lLiBCdXQsIHBsZWFzZSBkb24mIzgyMTc7dCBtYWtlIGFzc3VtcHRpb25zIHdoaWNo
IG5vdCBpbnRlbmRlZCwgbm9yIGFyZSBuZWNlc3NhcnkuDQogDQogDQpBbiBBUiBtYXkgdXNlIHBl
ci1tb2JpbGUgcHJlZml4IGFuZCBhbiBhZ2dyZWdhdGUgcHJlZml4IG9uIHRoZSAgaW50ZXJmYWNl
LiBBcyBJIHNhaWQsIGFnZ3JlZ2F0ZSBwcmVmaXggY291bGQgYmUgd2hhdCBpcyBhZHZlcnRpc2Vk
IGluICBQclJ0QWR2LiBUaGUgTU4gY2FuIGZvcm11bGF0ZSBhIHByb3NwZWN0aXZlIE5Db0EgdXNp
bmcgdGhhdCwgYnV0IHJlY2VpdmUgYSAgZGlmZmVyZW50IE5Db0EgZnJvbSBOQVIsIGJhc2VkIG9u
IHRoZSBwZXItbW9iaWxlIHByZWZpeC4gDQogDQpGcmFuayA9PkluIGZhY3QsICB0aGlzIGlzIG5v
dCBiaWcgZGlmZmVyZW50IGZyb20gb3VyIHByb3Bzb2FsICBpbiBkcmFmdC14aWEtbWlwc2hvcC1m
bWlwLXB0cC0wMCANCg0KUmFqZWV2Oi8yLz4gSSBhbSBub3QgcHJvcG9zaW5nIGEgbmV3IG1vZGVs
IGFib3ZlLiBKdXN0IHNob3dpbmcgaG93IHRoZSBleGlzdGluZyBtb2RlbCBjYW4gYmUgdXNlZC4N
Cg0KSSBjYW4gaW1hZ2luZSBvdGhlciB3YXlzIHRvIG1hbmFnZSAgdGhlIHByZWZpeC4gDQogDQpG
cmFuayA9PiBJICBhbHNvIGhhdmUgYSByZXZpc2VkIGRvY3VtZW50ICB3aGljaCBlbGFib3JhdGlu
ZyBvdGhlciBhbHRlcm5hdGl2ZXMsIGFuZCB3ZSBjYW4gY29vcGVyYXRlICAuDQoNClJhamVldjo+
IElmIHlvdXIgcXVlc3Rpb24gaXMgd2lsbCBpdCB3b3JrIHdpdGggcGVyLW1vYmlsZSAgcHJlZml4
LCB5ZXMuIEVpdGhlciBGQmFjayBvciBOQUFDSyBjYW4gcHJvdmlkZSB0aGUgTkNvQSB0aGF0IHRo
ZSBOQVIgd2FudHMgIHRoZSBNTiB0byB1c2UuIA0KICAgDQpGcmFuayA9PiBUaGUgZXhjaGFuZ2Ug
b2YgUnRTb2xQciBhbmQgUHJSdEFkdiBpcyB0byBmb3JtdWxhdGUgYSBuZXcgQ29BIHdoaWxlIGlz
IHVzZWxlc3MgIGluIHAtdC1wIG1vZGVsLiAgSXQgaXMgYSB3YXN0ZSBvZiBhaXIgaW50ZXJmYWNl
ICByZXNvdXJjZS4NCg0KUmFqZWV2Oi8yLz4gVGhhdCYjODIxNztzIGRlYmF0YWJsZSwgYW5kIGlz
IHVwIHRvIGVhY2ggdGVjaG5vbG9neSB0aGF0IGltcGxlbWVudHMgRk1JUC4gDQogDQogDQpGcmFu
ayA9PiBQLXRvLVAgc2NlbmFyaW8gaXMgYWRvcHRlZCBieSAgV2lNQVgvM0dQUDIsIHdoaWxlIEkg
aGF2ZSBsaXR0bGUgaWRlYSBhYm91dCBwcm9taXNpbmcgIGRlcGxveW1lbnQgb2Ygc2hhcmVkIGxp
bmsgbW9kZWwuDQoNClJhamVldjovMi8+IEdvb2QuICBSRkMgNDA2OCBpcyBub3QgYWJvdXQgc2hh
cmVkIGxpbmsgb25seS4gSXQmIzgyMTc7cyB5b3VyIGludGVycHJldGF0aW9uLiANCiANCklNSE8s
IHlvdXIgc2ltcGxpZmllZCBwcm9wb3NhbCBjYW4ndCBzb2x2ZSB0aGUgIHByb3BsZW0gdmVyeSB3
ZWxsLg0KIA0KICAgICAgICAgICAgICAgUmFqZWV2Oi8yLz4gWW91IGhhdmUgbm90IHNob3duIHdo
eSBteSBleHBsYW5hdGlvbiBvbiBob3cgdGhlIGN1cnJlbnQgbW9kZWwgY2FuIHdvcmsgd2lsbCBu
b3QgIHdvcmsuIEFzIEkgc3VnZ2VzdGVkIGVhcmxpZXIsIGlmIHRoZXJlIGlzIGFueSBzcGVjaWZp
YyBpc3N1ZSB0aGF0IG5lZWRzIHRvIGJlIGFkZHJlc3NlZCwgaXQgaXMgcHJvZHVjdGl2ZSB0byBw
cm9wb3NlIHRoZSBpc3N1ZSBhbmQgdGV4dC4gDQoNCi1SYWplZXYNCg0KIA0KDQotLSANCmh0dHA6
Ly9wZW9wbGUubm9raWEubmV0L35yYWplZXYgDQoNCg0K





--===============1480876244==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng

--===============1480876244==--



From 16ng-bounces@ietf.org Fri Jun 08 05:52:57 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hwb9K-00044y-IP; Fri, 08 Jun 2007 05:52:54 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1Hwb9J-00044Z-7n
	for 16ng-confirm+ok@megatron.ietf.org; Fri, 08 Jun 2007 05:52:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hwb9F-000426-Tt
	for 16ng@ietf.org; Fri, 08 Jun 2007 05:52:49 -0400
Received: from szxga03-in.huawei.com ([61.144.161.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hwb98-0006Dv-AM
	for 16ng@ietf.org; Fri, 08 Jun 2007 05:52:49 -0400
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JJB00HKCA2IXO@szxga03-in.huawei.com> for
	16ng@ietf.org; Fri, 08 Jun 2007 17:51:54 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JJB00GHOA2GDF@szxga03-in.huawei.com> for
	16ng@ietf.org; Fri, 08 Jun 2007 17:51:54 +0800 (CST)
Received: from z49950 ([10.121.32.173])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0JJB006QHA2CM2@szxml04-in.huawei.com> for
	16ng@ietf.org; Fri, 08 Jun 2007 17:51:52 +0800 (CST)
Date: Fri, 08 Jun 2007 17:51:48 +0800
From: "John.zhao" <john.zhao@huawei.com>
To: 16ng@ietf.org
Message-id: <00a201c7a9b2$a1ed1310$a864a8c0@china.huawei.com>
Organization: Huawei Technologies Co., LTD.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook 11
Thread-index: AcepsqF4+ZPrxQ1FQtS04lhfvQr82g==
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 7418200ea0c73569681eb45a76a492d4
Subject: [16NG] About MTU setting in IEEE802.16
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: john.zhao@huawei.com
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1470456554=="
Errors-To: 16ng-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1470456554==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_8bfGgX+JyO3+E3Emc/UZNw)"

This is a multi-part message in MIME format.

--Boundary_(ID_8bfGgX+JyO3+E3Emc/UZNw)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hi folks,

 

         May I ask a question, the MTU setting is a static value or a
dynamic value in IEEE802.16? And if will the MTU decide the practice
transmission size of frame over IEEE802.16?

 

         Best Rgds,

Thanks,

 

John.zhao


--Boundary_(ID_8bfGgX+JyO3+E3Emc/UZNw)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:\5B8B\4F53;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Dotum;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:\9ED1\4F53;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"MS UI Gothic";
	panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
	{font-family:DotumChe;
	panose-1:2 11 6 9 0 1 1 1 1 1;}
@font-face
	{font-family:\6977\4F53_GB2312;
	panose-1:2 1 6 9 3 1 1 1 1 1;}
@font-face
	{font-family:"\@\5B8B\4F53";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"\@Dotum";
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@MS UI Gothic";
	panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
	{font-family:"\@DotumChe";
	panose-1:2 11 6 9 0 1 1 1 1 1;}
@font-face
	{font-family:"\@\6977\4F53_GB2312";
	panose-1:2 1 6 9 3 1 1 1 1 1;}
@font-face
	{font-family:"\@\9ED1\4F53";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	line-height:150%;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";
	layout-grid-mode:line;}
h1
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:21.6pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-21.6pt;
	page-break-after:avoid;
	mso-list:l8 level1 lfo35;
	font-size:16.0pt;
	font-family:Arial;}
h2
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:28.8pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-28.8pt;
	page-break-after:avoid;
	mso-list:l8 level2 lfo35;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:normal;}
h3
	{margin-top:13.0pt;
	margin-right:0cm;
	margin-bottom:13.0pt;
	margin-left:36.0pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-36.0pt;
	line-height:173%;
	page-break-after:avoid;
	mso-list:l8 level3 lfo35;
	font-size:12.0pt;
	font-family:"Times New Roman";
	layout-grid-mode:line;
	font-weight:normal;}
p.MsoHeader, li.MsoHeader, div.MsoHeader
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	layout-grid-mode:char;
	font-size:9.0pt;
	font-family:Arial;}
p.MsoFooter, li.MsoFooter, div.MsoFooter
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:Arial;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.a, li.a, div.a
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:54.45pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:1.0gd;
	mso-para-margin-right:0cm;
	mso-para-margin-bottom:0cm;
	mso-para-margin-left:54.45pt;
	mso-para-margin-bottom:.0001pt;
	text-align:center;
	text-indent:-18.45pt;
	mso-list:l6 level9 lfo5;
	font-size:9.0pt;
	font-family:Arial;}
p.a0, li.a0, div.a0
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Arial;}
p.a1, li.a1, div.a1
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:center;
	font-size:10.5pt;
	font-family:Arial;
	font-weight:bold;}
p.a2, li.a2, div.a2
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:54.45pt;
	mso-para-margin-top:0cm;
	mso-para-margin-right:0cm;
	mso-para-margin-bottom:1.0gd;
	mso-para-margin-left:54.45pt;
	text-align:center;
	text-indent:-18.45pt;
	mso-list:l6 level8 lfo5;
	font-size:9.0pt;
	font-family:Arial;}
p.a3, li.a3, div.a3
	{margin-top:4.0pt;
	margin-right:0cm;
	margin-bottom:4.0pt;
	margin-left:0cm;
	text-align:center;
	line-height:150%;
	page-break-after:avoid;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";
	layout-grid-mode:line;}
p.a4, li.a4, div.a4
	{margin-top:15.0pt;
	margin-right:0cm;
	margin-bottom:15.0pt;
	margin-left:0cm;
	text-align:center;
	line-height:150%;
	text-autospace:none;
	font-size:18.0pt;
	font-family:Arial;
	layout-grid-mode:line;}
p.a5, li.a5, div.a5
	{margin:0cm;
	margin-bottom:.0001pt;
	line-height:150%;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";
	layout-grid-mode:line;}
p.a6, li.a6, div.a6
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	line-height:150%;
	text-autospace:none;
	border:none;
	padding:0cm;
	font-size:9.0pt;
	font-family:Arial;
	layout-grid-mode:line;}
p.a7, li.a7, div.a7
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:18.0pt;
	line-height:150%;
	text-autospace:none;
	border:none;
	padding:0cm;
	font-size:9.0pt;
	font-family:Arial;
	layout-grid-mode:line;}
p.a8, li.a8, div.a8
	{margin:0cm;
	margin-bottom:.0001pt;
	text-indent:21.0pt;
	line-height:150%;
	text-autospace:none;
	font-size:10.5pt;
	font-family:Arial;
	color:blue;
	layout-grid-mode:line;
	font-style:italic;}
span.a9
	{font-family:\5B8B\4F53;
	color:black;
	font-weight:bold;}
span.aa
	{font-family:\5B8B\4F53;
	color:black;
	font-weight:bold;}
span.EmailStyle33
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
 /* Page Definitions */
 @page
	{mso-endnote-separator:url("cid:header.htm\@01C7A9F5.AF83A370") es;
	mso-endnote-continuation-separator:url("cid:header.htm\@01C7A9F5.AF83A370") ecs;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:65.6pt 90.0pt 72.0pt 90.0pt;
	mso-footer:url("cid:header.htm\@01C7A9F5.AF83A370") f1;
	layout-grid:15.6pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:171800355;
	mso-list-template-ids:-1278163850;}
@list l0:level1
	{mso-level-text:%1;
	mso-level-tab-stop:21.6pt;
	mso-level-number-position:left;
	margin-left:21.6pt;
	text-indent:-21.6pt;}
@list l0:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:28.8pt;
	mso-level-number-position:left;
	margin-left:28.8pt;
	text-indent:-28.8pt;}
@list l0:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	margin-left:36.0pt;
	text-indent:-36.0pt;}
@list l0:level4
	{mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l0:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l0:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l0:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l0:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	margin-left:72.0pt;
	text-indent:-72.0pt;}
@list l0:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:79.2pt;
	mso-level-number-position:left;
	margin-left:79.2pt;
	text-indent:-79.2pt;}
@list l1
	{mso-list-id:191647984;
	mso-list-template-ids:345692754;}
@list l1:level1
	{mso-level-number-format:alpha-upper;
	mso-level-text:\9644\5F55%1;
	mso-level-tab-stop:64.15pt;
	mso-level-number-position:left;
	margin-left:64.15pt;
	text-indent:-21.6pt;}
@list l1:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:71.35pt;
	mso-level-number-position:left;
	margin-left:71.35pt;
	text-indent:-28.8pt;}
@list l1:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:78.55pt;
	mso-level-number-position:left;
	margin-left:78.55pt;
	text-indent:-36.0pt;}
@list l1:level4
	{mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:89.35pt;
	text-indent:-34.0pt;}
@list l1:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:89.35pt;
	text-indent:-34.0pt;}
@list l1:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:89.35pt;
	text-indent:-34.0pt;}
@list l1:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:89.35pt;
	text-indent:-34.0pt;}
@list l1:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:114.55pt;
	mso-level-number-position:left;
	margin-left:114.55pt;
	text-indent:-72.0pt;}
@list l1:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:121.75pt;
	mso-level-number-position:left;
	margin-left:121.75pt;
	text-indent:-79.2pt;}
@list l2
	{mso-list-id:541409008;
	mso-list-template-ids:-249166292;}
@list l2:level1
	{mso-level-number-format:alpha-upper;
	mso-level-text:\9644\5F55%1;
	mso-level-tab-stop:21.6pt;
	mso-level-number-position:left;
	margin-left:21.6pt;
	text-indent:-21.6pt;}
@list l2:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:28.8pt;
	mso-level-number-position:left;
	margin-left:28.8pt;
	text-indent:-28.8pt;}
@list l2:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	margin-left:36.0pt;
	text-indent:-36.0pt;}
@list l2:level4
	{mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l2:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l2:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l2:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l2:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	margin-left:72.0pt;
	text-indent:-72.0pt;}
@list l2:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:79.2pt;
	mso-level-number-position:left;
	margin-left:79.2pt;
	text-indent:-79.2pt;}
@list l3
	{mso-list-id:818422186;
	mso-list-template-ids:1344984950;}
@list l3:level1
	{mso-level-text:%1;
	mso-level-tab-stop:21.6pt;
	mso-level-number-position:left;
	margin-left:21.6pt;
	text-indent:-21.6pt;}
@list l3:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:28.8pt;
	mso-level-number-position:left;
	margin-left:28.8pt;
	text-indent:-28.8pt;}
@list l3:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	margin-left:36.0pt;
	text-indent:-36.0pt;}
@list l3:level4
	{mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l3:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l3:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l3:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l3:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	margin-left:72.0pt;
	text-indent:-72.0pt;}
@list l3:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:79.2pt;
	mso-level-number-position:left;
	margin-left:79.2pt;
	text-indent:-79.2pt;}
@list l4
	{mso-list-id:838886720;
	mso-list-template-ids:-819953982;}
@list l4:level1
	{mso-level-text:%1;
	mso-level-tab-stop:21.6pt;
	mso-level-number-position:left;
	margin-left:21.6pt;
	text-indent:-21.6pt;
	mso-ansi-font-size:18.0pt;
	mso-bidi-font-size:18.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l4:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:28.8pt;
	mso-level-number-position:left;
	margin-left:28.8pt;
	text-indent:-28.8pt;
	mso-ansi-font-size:15.0pt;
	mso-bidi-font-size:15.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l4:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	margin-left:36.0pt;
	text-indent:-36.0pt;
	mso-ansi-font-size:12.0pt;
	mso-bidi-font-size:12.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l4:level4
	{mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l4:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l4:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l4:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l4:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	margin-left:72.0pt;
	text-indent:-72.0pt;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l4:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:79.2pt;
	mso-level-number-position:left;
	margin-left:79.2pt;
	text-indent:-79.2pt;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l5
	{mso-list-id:942373150;
	mso-list-template-ids:67698717;}
@list l5:level1
	{mso-level-text:%1;
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l5:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:57.25pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-1.0cm;}
@list l5:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:96.55pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-1.0cm;}
@list l5:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:135.8pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l5:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:175.05pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l5:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:214.3pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-2.0cm;}
@list l5:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:253.55pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l5:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:292.8pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l5:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:332.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
@list l6
	{mso-list-id:1123964682;
	mso-list-template-ids:301907670;}
@list l6:level1
	{mso-level-suffix:none;
	mso-level-text:"%1  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:18.0pt;
	mso-bidi-font-size:18.0pt;
	font-family:Arial;
	mso-fareast-font-family:\9ED1\4F53;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l6:level2
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:15.0pt;
	mso-bidi-font-size:15.0pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l6:level3
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:12.0pt;
	mso-bidi-font-size:12.0pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l6:level4
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3\.%4  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l6:level5
	{mso-level-tab-stop:2.0cm;
	mso-level-number-position:left;
	margin-left:2.0cm;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l6:level6
	{mso-level-text:"%6\)";
	mso-level-tab-stop:2.0cm;
	mso-level-number-position:left;
	margin-left:2.0cm;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l6:level7
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:2.0cm;
	mso-level-number-position:left;
	margin-left:2.0cm;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l6:level8
	{mso-level-reset-level:level1;
	mso-level-style-link:\63D2\56FE\9898\6CE8;
	mso-level-suffix:space;
	mso-level-text:\56FE%8;
	mso-level-tab-stop:none;
	mso-level-number-position:center;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	font-family:Arial;
	mso-fareast-font-family:\9ED1\4F53;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l6:level9
	{mso-level-reset-level:level1;
	mso-level-style-link:\8868\683C\9898\6CE8;
	mso-level-suffix:space;
	mso-level-text:\8868%9;
	mso-level-tab-stop:none;
	mso-level-number-position:center;
	margin-left:0cm;
	text-indent:0cm;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	font-family:Arial;
	mso-fareast-font-family:\9ED1\4F53;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l7
	{mso-list-id:1380013528;
	mso-list-template-ids:-1435872280;}
@list l7:level1
	{mso-level-number-format:none;
	mso-level-text:"\9644\5F55A ";
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l7:level2
	{mso-level-text:"A\.%2";
	mso-level-tab-stop:49.6pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-1.0cm;}
@list l7:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-1.0cm;}
@list l7:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:99.2pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l7:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:127.55pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l7:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:163.0pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-2.0cm;}
@list l7:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:191.35pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l7:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:219.7pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l7:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:255.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
@list l8
	{mso-list-id:1666475049;
	mso-list-template-ids:-28945502;}
@list l8:level1
	{mso-level-style-link:"\6807\9898 1";
	mso-level-text:%1;
	mso-level-tab-stop:21.6pt;
	mso-level-number-position:left;
	margin-left:21.6pt;
	text-indent:-21.6pt;}
@list l8:level2
	{mso-level-style-link:"\6807\9898 2";
	mso-level-text:"%1\.%2";
	mso-level-tab-stop:28.8pt;
	mso-level-number-position:left;
	margin-left:28.8pt;
	text-indent:-28.8pt;}
@list l8:level3
	{mso-level-style-link:"\6807\9898 3";
	mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	margin-left:36.0pt;
	text-indent:-36.0pt;}
@list l8:level4
	{mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l8:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l8:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l8:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l8:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	margin-left:72.0pt;
	text-indent:-72.0pt;}
@list l8:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:79.2pt;
	mso-level-number-position:left;
	margin-left:79.2pt;
	text-indent:-79.2pt;}
@list l9
	{mso-list-id:1916042858;
	mso-list-template-ids:-648263936;}
@list l9:level1
	{mso-level-number-format:alpha-upper;
	mso-level-text:&#38468;&#24405;%1;
	mso-level-tab-stop:21.6pt;
	mso-level-number-position:left;
	margin-left:21.6pt;
	text-indent:-21.6pt;}
@list l9:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:28.8pt;
	mso-level-number-position:left;
	margin-left:28.8pt;
	text-indent:-28.8pt;}
@list l9:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	margin-left:36.0pt;
	text-indent:-36.0pt;}
@list l9:level4
	{mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l9:level5
	{mso-level-text:%5&#65289;;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l9:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6&#65289;;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l9:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:1.0cm;
	mso-level-number-position:left;
	margin-left:46.8pt;
	text-indent:-34.0pt;}
@list l9:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	margin-left:72.0pt;
	text-indent:-72.0pt;}
@list l9:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:79.2pt;
	mso-level-number-position:left;
	margin-left:79.2pt;
	text-indent:-79.2pt;}
@list l10
	{mso-list-id:2114861838;
	mso-list-template-ids:-433129230;}
@list l10:level1
	{mso-level-number-format:none;
	mso-level-text:"&#38468;&#24405;A ";
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l10:level2
	{mso-level-text:"A\.%2";
	mso-level-tab-stop:49.6pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-1.0cm;}
@list l10:level3
	{mso-level-text:"%1A\.%2\.%3";
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-1.0cm;}
@list l10:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:99.2pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l10:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:127.55pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l10:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:163.0pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-2.0cm;}
@list l10:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:191.35pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l10:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:219.7pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l10:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:255.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="3074" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="2" />
  <o:regrouptable v:ext="edit">
   <o:entry new="1" old="0" />
  </o:regrouptable>
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=ZH-CN link=blue vlink=purple style='text-justify-trim:punctuation'>

<div class=Section1 style='layout-grid:15.6pt'>

<p class=MsoNormal><font size=1 face=Arial><span lang=EN-US style='font-size:
9.0pt;line-height:150%;font-family:Arial'>Hi folks,<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=1 face=Arial><span lang=EN-US style='font-size:
9.0pt;line-height:150%;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=1 face=Arial><span lang=EN-US style='font-size:
9.0pt;line-height:150%;font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; May
I ask a question, the MTU setting is a static value or a dynamic value in
IEEE802.16? And if will the MTU decide the practice transmission size of frame
over IEEE802.16?<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=1 face=Arial><span lang=EN-US style='font-size:
9.0pt;line-height:150%;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=1 face=Arial><span lang=EN-US style='font-size:
9.0pt;line-height:150%;font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Best
Rgds,<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=1 face=Arial><span lang=EN-US style='font-size:
9.0pt;line-height:150%;font-family:Arial'>Thanks,<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=1 face=Arial><span lang=EN-US style='font-size:
9.0pt;line-height:150%;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=1 face=Arial><span lang=EN-US style='font-size:
9.0pt;line-height:150%;font-family:Arial'>John.zhao<o:p></o:p></span></font></p>

</div>

</body>

</html>

--Boundary_(ID_8bfGgX+JyO3+E3Emc/UZNw)--



--===============1470456554==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng

--===============1470456554==--





From 16ng-bounces@ietf.org Fri Jun 08 11:15:14 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwgBF-0003MU-S9; Fri, 08 Jun 2007 11:15:13 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1HwgBE-0003MK-SD
	for 16ng-confirm+ok@megatron.ietf.org; Fri, 08 Jun 2007 11:15:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwgBE-0003M9-IF
	for 16ng@ietf.org; Fri, 08 Jun 2007 11:15:12 -0400
Received: from web84102.mail.mud.yahoo.com ([68.142.206.189])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HwgBC-000764-QR
	for 16ng@ietf.org; Fri, 08 Jun 2007 11:15:12 -0400
Received: (qmail 4892 invoked by uid 60001); 8 Jun 2007 15:15:10 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID;
	b=h7ygUQsAA7P3LfFc70L2u3sAtUihlZtFLmqo8n5T2IAIbbjzbk/IbC6ddsqeb/S3R33B12mo9tM5KZmnXoaBnG65XzAHFlLLlV1q4OCkFplNajfVRsfGti4hWG1ooXvUzlbP2gPhJsIoa6QhTWeV+NiVMcQjU2hHU1XBQfI0ViA=;
X-YMail-OSG: t0w35gUVM1mdL0.3gFZfMDKkAvK_G7.KMNkjxK.rghTPrlSKSX8MAqljZf6T99WQ0Q--
Received: from [206.16.17.212] by web84102.mail.mud.yahoo.com via HTTP;
	Fri, 08 Jun 2007 08:15:10 PDT
X-Mailer: YahooMailRC/651.23.1 YahooMailWebService/0.7.41.14
Date: Fri, 8 Jun 2007 08:15:10 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over
	IEEE802.16e Networks
To: heejin.jang@samsung.com
MIME-Version: 1.0
Message-ID: <285400.4498.qm@web84102.mail.mud.yahoo.com>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 88b11fc64c1bfdb4425294ef5374ca07
Cc: "mipshop@ietf.org" <mipshop@ietf.org>, "16ng@ietf.org" <16ng@ietf.org>
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1291268633=="
Errors-To: 16ng-bounces@ietf.org

--===============1291268633==
Content-Type: multipart/alternative; boundary="0-211441574-1181315710=:4498"

--0-211441574-1181315710=:4498
Content-Type: text/plain; charset=ascii


Hi Heejin,
  Have you seen this draft:
http://tools.ietf.org/wg/mipshop/draft-xia-mipshop-fmip-ptp-00.txt which was presented in Prague?

4068bis needs a lot of changes in order to support per-mobile prefix model. We've been in contact with Rajeev on this. It has been interrupted because I think Rajeev is traveling.

A solution is expected to emerge soon.

Regards,

Behcet
----- Original Message ----
From: Heejin Jang <heejin.jang@samsung.com>
To: Rajeev Koodli <rajeev.koodli@nokia.com>
Cc: "mipshop@ietf.org" <mipshop@ietf.org>; "16ng@ietf.org" <16ng@ietf.org>
Sent: Thursday, June 7, 2007 9:44:03 PM
Subject: Re: Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE802.16e Networks

Hi, Frank



I agree with Rajeev.    

     

RFC4068 is not limited only to the shared link model because the p2p prefix allocation     

(per-MN prefix model) can be applied without any modification of RFC4068 in the point-to-point link.     

It can be done NCoA allocation via BAck & NAACK as you and Rajeev suggested, or     

PAR's Administrator may decide to manage a part of  IPv6 prefix pool of NAR for allocation if feasible.    

(I think that's not a waste of prefixes where the prefix is assigned "per MN" in the (IPv6) point-to-point link.:) )    

     

Some mention may need to be reflected in 4068-bis, for e.g., 1) RtSolPr & PrRtAdv exchanges,

2) Proxying NCoA with proxy neighbor cache entry in NARand 3) DAD check, some or all of these procedures

may be omitted in the point-to-point link.    



But I don't think it's a new model but a way of how the existing fmipv6 can be applied over the point-to-point link.         

     

- Regards, 

Heejin. 



------- Original Message -------

Sender : Rajeev Koodli<rajeev.koodli@nokia.com>

Date   : 2007-06-05 06:08

Title  : Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE802.16e Networks





Hi Frank,



May be we are going in circles here.. I have not seen why the current model cannot work for the scenario you have in mind. If there is an issue, the WG process is to bring it up and propose text. It&#8217;s more productive that way. I am willing to clarify in the bis version. Some more replies below..

 



1 "(AP-ID, AR-Info) tuple Contains an access router's L2 and IP  addresses, and

  prefix valid on the interface to which the  Access Point (identified by AP-ID) is attached.  

 The triplet  [Router's  L2 address, Router's IP address and Prefix] is called  "AR-Info"".

 

=> Here, prefix is AR's physical interface  prefix is used for NCoA formulation.

  As you know, this prefix  is useless for P-to-P link model.



Rajeev:> you could interpret it  that way, but you don&#8217;t have to. The point I am trying to make is that the  current model works for the scenario you are enumerating.

 

Frank=> don't you think the concept of the  perfix is too flexible that different people can have their own different  understanding?  In your draft, the prefix is definitely the prefix of  AR physical interface. I think there is not ambiguous.



Rajeev/2/:> First, it is not my draft; it is the WG document. Second, it is not clear to me why you would equate the prefix to physical interface. 4068 only says it is the prefix valid on the interface the MN is attaching to, and I am unable to see what&#8217;s the problem.



If you are trying to map it to ptp model, that&#8217;s fine. But, please don&#8217;t make assumptions which not intended, nor are necessary.

 

 

An AR may use per-mobile prefix and an aggregate prefix on the  interface. As I said, aggregate prefix could be what is advertised in  PrRtAdv. The MN can formulate a prospective NCoA using that, but receive a  different NCoA from NAR, based on the per-mobile prefix. 

 

Frank =>In fact,  this is not big different from our propsoal  in draft-xia-mipshop-fmip-ptp-00 



Rajeev:/2/> I am not proposing a new model above. Just showing how the existing model can be used.



I can imagine other ways to manage  the prefix. 

 

Frank => I  also have a revised document  which elaborating other alternatives, and we can cooperate  .



Rajeev:> If your question is will it work with per-mobile  prefix, yes. Either FBack or NAACK can provide the NCoA that the NAR wants  the MN to use. 

   

Frank => The exchange of RtSolPr and PrRtAdv is to formulate a new CoA while is useless  in p-t-p model.  It is a waste of air interface  resource.



Rajeev:/2/> That&#8217;s debatable, and is up to each technology that implements FMIP. 

 

 

Frank => P-to-P scenario is adopted by  WiMAX/3GPP2, while I have little idea about promising  deployment of shared link model.



Rajeev:/2/> Good.  RFC 4068 is not about shared link only. It&#8217;s your interpretation. 

 

IMHO, your simplified proposal can't solve the  proplem very well.

 

               Rajeev:/2/> You have not shown why my explanation on how the current model can work will not  work. As I suggested earlier, if there is any specific issue that needs to be addressed, it is productive to propose the issue and text. 



-Rajeev



 



-- 

http://people.nokia.net/~rajeev 






_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng





--0-211441574-1181315710=:4498
Content-Type: text/html; charset=ascii

<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:14pt"><div style="font-family: times new roman,new york,times,serif; font-size: 14pt;"><br>Hi Heejin,<br>&nbsp; Have you seen this draft:<br><span><a target="_blank" href="http://tools.ietf.org/wg/mipshop/draft-xia-mipshop-fmip-ptp-00.txt">http://tools.ietf.org/wg/mipshop/draft-xia-mipshop-fmip-ptp-00.txt</a> which was presented in Prague?</span><br><br>4068bis needs a lot of changes in order to support per-mobile prefix model. We've been in contact with Rajeev on this. It has been interrupted because I think Rajeev is traveling.<br><br>A solution is expected to emerge soon.<br><br>Regards,<br><br>Behcet<br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Heejin Jang &lt;heejin.jang@samsung.com&gt;<br>To: Rajeev Koodli
 &lt;rajeev.koodli@nokia.com&gt;<br>Cc: "mipshop@ietf.org" &lt;mipshop@ietf.org&gt;; "16ng@ietf.org" &lt;16ng@ietf.org&gt;<br>Sent: Thursday, June 7, 2007 9:44:03 PM<br>Subject: Re: Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE802.16e Networks<br><br><div>Hi, Frank<br><br><br><br>I agree with Rajeev.&nbsp;&nbsp;&nbsp;&nbsp;<br><br>&nbsp;&nbsp;&nbsp;&nbsp; <br><br>RFC4068 is not limited only to the shared link model because the p2p prefix allocation&nbsp;&nbsp;&nbsp;&nbsp; <br><br>(per-MN prefix model) can be applied without any modification of RFC4068 in the point-to-point link.&nbsp;&nbsp;&nbsp;&nbsp; <br><br>It can be done NCoA allocation via BAck &amp; NAACK as you and Rajeev suggested, or&nbsp;&nbsp;&nbsp;&nbsp; <br><br>PAR's Administrator may decide to manage a part of&nbsp;&nbsp;IPv6 prefix pool of NAR for allocation if feasible.&nbsp;&nbsp;&nbsp;&nbsp;<br><br>(I think that's not a waste of prefixes where the prefix is assigned "per MN" in the (IPv6)
 point-to-point link.:) )&nbsp;&nbsp;&nbsp;&nbsp;<br><br>&nbsp;&nbsp;&nbsp;&nbsp; <br><br>Some mention may need to be reflected in 4068-bis, for e.g., 1) RtSolPr &amp; PrRtAdv exchanges,<br><br>2) Proxying NCoA with proxy neighbor cache entry in NARand 3) DAD check, some or all of these procedures<br><br>may be omitted in the point-to-point link.&nbsp;&nbsp;&nbsp;&nbsp;<br><br><br><br>But I don't think it's a new model but a way of how the existing fmipv6 can be applied over the point-to-point link.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br><br>&nbsp;&nbsp;&nbsp;&nbsp; <br><br>- Regards, <br><br>Heejin. <br><br><br><br>------- Original Message -------<br><br>Sender : Rajeev Koodli&lt;rajeev.koodli@nokia.com&gt;<br><br>Date&nbsp;&nbsp; : 2007-06-05 06:08<br><br>Title&nbsp;&nbsp;: Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over IEEE802.16e Networks<br><br><br><br><br><br>Hi Frank,<br><br><br><br>May be we are going in circles here.. I have not seen why
 the current model cannot work for the scenario you have in mind. If there is an issue, the WG process is to bring it up and propose text. It&amp;#8217;s more productive that way. I am willing to clarify in the bis version. Some more replies below..<br><br> <br><br><br><br>1 "(AP-ID, AR-Info) tuple Contains an access router's L2 and IP&nbsp;&nbsp;addresses, and<br><br>&nbsp;&nbsp;prefix valid on the interface to which the&nbsp;&nbsp;Access Point (identified by AP-ID) is attached.&nbsp;&nbsp;<br><br> The triplet&nbsp;&nbsp;[Router's&nbsp;&nbsp;L2 address, Router's IP address and Prefix] is called&nbsp;&nbsp;"AR-Info"".<br><br> <br><br>=&gt; Here, prefix is AR's physical interface&nbsp;&nbsp;prefix is used for NCoA formulation.<br><br>&nbsp;&nbsp;As you know, this prefix&nbsp;&nbsp;is useless for P-to-P link model.<br><br><br><br>Rajeev:&gt; you could interpret it&nbsp;&nbsp;that way, but you don&amp;#8217;t have to. The point I am trying to make is that
 the&nbsp;&nbsp;current model works for the scenario you are enumerating.<br><br> <br><br>Frank=&gt; don't you think the concept of the&nbsp;&nbsp;perfix is too flexible that different people can have their own different&nbsp;&nbsp;understanding?&nbsp;&nbsp;In your draft, the prefix is definitely the prefix of&nbsp;&nbsp;AR physical interface. I think there is not ambiguous.<br><br><br><br>Rajeev/2/:&gt; First, it is not my draft; it is the WG document. Second, it is not clear to me why you would equate the prefix to physical interface. 4068 only says it is the prefix valid on the interface the MN is attaching to, and I am unable to see what&amp;#8217;s the problem.<br><br><br><br>If you are trying to map it to ptp model, that&amp;#8217;s fine. But, please don&amp;#8217;t make assumptions which not intended, nor are necessary.<br><br> <br><br> <br><br>An AR may use per-mobile prefix and an aggregate prefix on the&nbsp;&nbsp;interface. As I said, aggregate prefix could be
 what is advertised in&nbsp;&nbsp;PrRtAdv. The MN can formulate a prospective NCoA using that, but receive a&nbsp;&nbsp;different NCoA from NAR, based on the per-mobile prefix. <br><br> <br><br>Frank =&gt;In fact,&nbsp;&nbsp;this is not big different from our propsoal&nbsp;&nbsp;in draft-xia-mipshop-fmip-ptp-00 <br><br><br><br>Rajeev:/2/&gt; I am not proposing a new model above. Just showing how the existing model can be used.<br><br><br><br>I can imagine other ways to manage&nbsp;&nbsp;the prefix. <br><br> <br><br>Frank =&gt; I&nbsp;&nbsp;also have a revised document&nbsp;&nbsp;which elaborating other alternatives, and we can cooperate&nbsp;&nbsp;.<br><br><br><br>Rajeev:&gt; If your question is will it work with per-mobile&nbsp;&nbsp;prefix, yes. Either FBack or NAACK can provide the NCoA that the NAR wants&nbsp;&nbsp;the MN to use. <br><br>&nbsp;&nbsp; <br><br>Frank =&gt; The exchange of RtSolPr and PrRtAdv is to formulate a new CoA while is useless&nbsp;&nbsp;in p-t-p
 model.&nbsp;&nbsp;It is a waste of air interface&nbsp;&nbsp;resource.<br><br><br><br>Rajeev:/2/&gt; That&amp;#8217;s debatable, and is up to each technology that implements FMIP. <br><br> <br><br> <br><br>Frank =&gt; P-to-P scenario is adopted by&nbsp;&nbsp;WiMAX/3GPP2, while I have little idea about promising&nbsp;&nbsp;deployment of shared link model.<br><br><br><br>Rajeev:/2/&gt; Good.&nbsp;&nbsp;RFC 4068 is not about shared link only. It&amp;#8217;s your interpretation. <br><br> <br><br>IMHO, your simplified proposal can't solve the&nbsp;&nbsp;proplem very well.<br><br> <br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Rajeev:/2/&gt; You have not shown why my explanation on how the current model can work will not&nbsp;&nbsp;work. As I suggested earlier, if there is any specific issue that needs to be addressed, it is productive to propose the issue and text. <br><br><br><br>-Rajeev<br><br><br><br> <br><br><br><br>-- <br><br><a
 target="_blank" href="http://people.nokia.net/%7Erajeev">http://people.nokia.net/~rajeev</a> <br><br><br><br><br><br></div><div>_______________________________________________<br>16NG mailing list<br>16NG@ietf.org<br><a target="_blank" href="https://www1.ietf.org/mailman/listinfo/16ng">https://www1.ietf.org/mailman/listinfo/16ng</a><br></div></div><br></div></div></body></html>
--0-211441574-1181315710=:4498--



--===============1291268633==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng

--===============1291268633==--





From 16ng-bounces@ietf.org Sun Jun 10 22:01:44 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxZDy-0006tt-3k; Sun, 10 Jun 2007 22:01:42 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1HxZDw-0006tl-39
	for 16ng-confirm+ok@megatron.ietf.org; Sun, 10 Jun 2007 22:01:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxZDv-0006td-Nn; Sun, 10 Jun 2007 22:01:39 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HxZDs-0005s1-TH; Sun, 10 Jun 2007 22:01:39 -0400
Received: from ep_ms5_bk (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0JJG005Z68ANM7@mailout3.samsung.com>; Mon,
	11 Jun 2007 11:01:35 +0900 (KST)
Received: from ep_spt01 (ms5.samsung.com [203.254.225.113])
	by ms5.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004)) with ESMTP id <0JJG002BD8ANIL@ms5.samsung.com>; Mon,
	11 Jun 2007 11:01:35 +0900 (KST)
Content-return: prohibited
Date: Mon, 11 Jun 2007 02:01:35 +0000 (GMT)
From: =?euc-kr?B?wOXI8cH4?= <heejin.jang@samsung.com>
Subject: Re: Re: Re: [Mipshop] Re: [16NG] FW: Call for Review on FMIP6 over
	IEEE802.16e Networks
To: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Message-id: <0JJG002BE8ANIL@ms5.samsung.com>
MIME-version: 1.0
MIME-version: 1.0
X-Priority: 3
Msgkey: 20070611020134599@heejin.jang
X-MTR: 20070611020134599@heejin.jang
X-EPLocale: ko_KR.euc-kr
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
X-EPApproval-Locale: 
X-Generator: NamoMIME 6.0.0.8
X-Spam-Score: 3.3 (+++)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
Cc: "mipshop@ietf.org" <mipshop@ietf.org>, "16ng@ietf.org" <16ng@ietf.org>
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: heejin.jang@samsung.com
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0794305476=="
Errors-To: 16ng-bounces@ietf.org

--===============0794305476==
Content-return: prohibited
Content-type: text/html; charset=euc-kr
Content-transfer-encoding: base64

PEhUTUw+PEhFQUQ+PHN0eWxlIHR5cGU9InRleHQvY3NzIj48IS0tIERJViB7bWFyZ2luOjBweDt9
IC0tPjwvc3R5bGU+PC9IRUFEPjxCT0RZPg0KPHAgYWxpZ249ImxlZnQiPkhpIEJlaGNldC48L3A+
DQo8cCBhbGlnbj0ibGVmdCI+SSd2ZSByZWFkIHRoYXQgZHJhZnQuIEJ1dCBpdCBkb2VzIG5vdCBk
ZXNjcmliZSBhbnkgcHJvYmxlbSBleGNlcHQgDQpwcmVmaXggYXNzaWdubWVudCBpbiBmbWlwL3Bv
aW50LXRvLXBvaW50IGxpbmsgd2hpY2ggY2FuIGJlIHNvbHZlZCBpbiBhIHdheSBhcyANClJhamVl
diBzdWdnZXN0ZWQuPC9wPg0KPHAgYWxpZ249ImxlZnQiPkFzIFJhamVldiBzYWlkIGluIHRoZSBm
b2xsb3dpbmcgZW1haWwsIEkgdGhpbmsgdGhhdCB5b3UgbmVlZCANCnRvIGNsYXJpZnkgd2h5IHRo
ZSBjdXJyZW50IG1vZGVsIGNhbm5vdCB3b3JrIHdpdGggdGhlIHBvaW50LXRvLXBvaW50IG1vZGVs
LCANCmFuZCB3aGljaCBpc3N1ZXMgaW4gcmZjNDA2OCBuZWVkIHRvIGJlIHJlc29sdmVkLjwvcD4N
CjxwIGFsaWduPSJsZWZ0Ij5JbiBteSB1bmRlcnN0YW5kaW5nLCB0aGUgZm9sbG93aW5nIGlzc3Vl
cyBhcmUgdGhvc2UgdGhpbmdzLCANCmJ1dCBJJ20gbm90IHN1cmUgaXQgZGVzZXJ2ZXMgdG8gYmUg
YSBuZXcgZG9jdW1lbnQuPC9wPg0KPHAgYWxpZ249ImxlZnQiPlNvbWUgb3IgYWxsIG9mIHRoZXNl
IHByb2NlZHVyZXMgbWF5IGJlIG9taXR0ZWQgaW4gdGhlIHBvaW50LXRvLXBvaW50IA0KbGluay4g
Jm5ic3A7Jm5ic3A7Jm5ic3A7PC9wPg0KPHAgYWxpZ249ImxlZnQiPjEpIFJ0U29sUHIgJmFtcDsg
UHJSdEFkdiBleGNoYW5nZXM8L3A+DQo8cCBhbGlnbj0ibGVmdCI+MikgUHJveHlpbmcgTkNvQSB3
aXRoIHByb3h5IG5laWdoYm9yIGNhY2hlIGVudHJ5IGluIE5BUjwvcD4NCjxwIGFsaWduPSJsZWZ0
Ij4zKSBEQUQgY2hlY2s8L3A+DQo8cCBhbGlnbj0ibGVmdCI+PGZvbnQgZmFjZT0iudnFwSI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMHB0OyI+Jm5ic3A7PC9zcGFuPjwvZm9udD48L3A+DQo8cCBh
bGlnbj0ibGVmdCI+LVJlZ2FyZHMsIDwvcD4NCjxwIGFsaWduPSJsZWZ0Ij5IZWVqaW4uPC9wPg0K
PHAgYWxpZ249ImxlZnQiPjxmb250IGZhY2U9IrnZxcEiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTBwdDsiPiZuYnNwOzwvc3Bhbj48L2ZvbnQ+PC9wPg0KPERJViBkaXI9bHRyIGFsaWduPWxlZnQ+
PGZvbnQgZmFjZT0iudnFwSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMHB0OyI+Jm5ic3A7PC9z
cGFuPjwvZm9udD48L0RJVj48cD4mbmJzcDs8L3A+PHA+Jm5ic3A7PC9wPjxicj48YnI+LS0tLS0t
LSA8Yj5PcmlnaW5hbCBNZXNzYWdlPC9iPiAtLS0tLS0tPGJyPjxiPlNlbmRlcjwvYj4gOiBCZWhj
ZXQgU2FyaWtheWEmbHQ7YmVoY2V0c2FyaWtheWFAeWFob28uY29tJmd0Ozxicj48Yj5EYXRlPC9i
PiAgIDogMjAwNy0wNi0wOSAwMDoxNTxicj48Yj5UaXRsZTwvYj4gIDogUmU6IFJlOiBbTWlwc2hv
cF0gUmU6IFsxNk5HXSBGVzogQ2FsbCBmb3IgUmV2aWV3IG9uIEZNSVA2IG92ZXINCiBJRUVFODAy
LjE2ZSBOZXR3b3Jrczxicj48YnI+DQogPGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6dGltZXMgbmV3
IHJvbWFuLG5ldyB5b3JrLHRpbWVzLHNlcmlmO2ZvbnQtc2l6ZToxNHB0Ij48ZGl2IHN0eWxlPSJm
b250LWZhbWlseTogdGltZXMgbmV3IHJvbWFuLG5ldyB5b3JrLHRpbWVzLHNlcmlmOyBmb250LXNp
emU6IDE0cHQ7Ij48YnI+SGkgSGVlamluLDxicj4mbmJzcDsgSGF2ZSB5b3Ugc2VlbiB0aGlzIGRy
YWZ0Ojxicj48c3Bhbj48YSB0YXJnZXQ9Il9ibGFuayIgaHJlZj0iaHR0cDovL3Rvb2xzLmlldGYu
b3JnL3dnL21pcHNob3AvZHJhZnQteGlhLW1pcHNob3AtZm1pcC1wdHAtMDAudHh0Ij5odHRwOi8v
dG9vbHMuaWV0Zi5vcmcvd2cvbWlwc2hvcC9kcmFmdC14aWEtbWlwc2hvcC1mbWlwLXB0cC0wMC50
eHQ8L2E+IHdoaWNoIHdhcyBwcmVzZW50ZWQgaW4gUHJhZ3VlPzwvc3Bhbj48YnI+PGJyPjQwNjhi
aXMgbmVlZHMgYSBsb3Qgb2YgY2hhbmdlcyBpbiBvcmRlciB0byBzdXBwb3J0IHBlci1tb2JpbGUg
cHJlZml4IG1vZGVsLiBXZSd2ZSBiZWVuIGluIGNvbnRhY3Qgd2l0aCBSYWplZXYgb24gdGhpcy4g
SXQgaGFzIGJlZW4gaW50ZXJydXB0ZWQgYmVjYXVzZSBJIHRoaW5rIFJhamVldiBpcyB0cmF2ZWxp
bmcuPGJyPjxicj5BIHNvbHV0aW9uIGlzIGV4cGVjdGVkIHRvIGVtZXJnZSBzb29uLjxicj48YnI+
UmVnYXJkcyw8YnI+PGJyPkJlaGNldDxicj48ZGl2IHN0eWxlPSJmb250LWZhbWlseTogdGltZXMg
bmV3IHJvbWFuLG5ldyB5b3JrLHRpbWVzLHNlcmlmOyBmb250LXNpemU6IDEycHQ7Ij4tLS0tLSBP
cmlnaW5hbCBNZXNzYWdlIC0tLS08YnI+RnJvbTogSGVlamluIEphbmcgJmx0O2hlZWppbi5qYW5n
QHNhbXN1bmcuY29tJmd0Ozxicj5UbzogUmFqZWV2IEtvb2RsaQ0KICZsdDtyYWplZXYua29vZGxp
QG5va2lhLmNvbSZndDs8YnI+Q2M6ICZxdW90O21pcHNob3BAaWV0Zi5vcmcmcXVvdDsgJmx0O21p
cHNob3BAaWV0Zi5vcmcmZ3Q7OyAmcXVvdDsxNm5nQGlldGYub3JnJnF1b3Q7ICZsdDsxNm5nQGll
dGYub3JnJmd0Ozxicj5TZW50OiBUaHVyc2RheSwgSnVuZSA3LCAyMDA3IDk6NDQ6MDMgUE08YnI+
U3ViamVjdDogUmU6IFJlOiBbTWlwc2hvcF0gUmU6IFsxNk5HXSBGVzogQ2FsbCBmb3IgUmV2aWV3
IG9uIEZNSVA2IG92ZXIgSUVFRTgwMi4xNmUgTmV0d29ya3M8YnI+PGJyPjxkaXY+SGksIEZyYW5r
PGJyPjxicj48YnI+PGJyPkkgYWdyZWUgd2l0aCBSYWplZXYuJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7PGJyPjxicj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgPGJyPjxicj5SRkM0MDY4IGlzIG5v
dCBsaW1pdGVkIG9ubHkgdG8gdGhlIHNoYXJlZCBsaW5rIG1vZGVsIGJlY2F1c2UgdGhlIHAycCBw
cmVmaXggYWxsb2NhdGlvbiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA8YnI+PGJyPihwZXItTU4g
cHJlZml4IG1vZGVsKSBjYW4gYmUgYXBwbGllZCB3aXRob3V0IGFueSBtb2RpZmljYXRpb24gb2Yg
UkZDNDA2OCBpbiB0aGUgcG9pbnQtdG8tcG9pbnQgbGluay4mbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsgPGJyPjxicj5JdCBjYW4gYmUgZG9uZSBOQ29BIGFsbG9jYXRpb24gdmlhIEJBY2sgJmFtcDsg
TkFBQ0sgYXMgeW91IGFuZCBSYWplZXYgc3VnZ2VzdGVkLCBvciZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyA8YnI+PGJyPlBBUidzIEFkbWluaXN0cmF0b3IgbWF5IGRlY2lkZSB0byBtYW5hZ2UgYSBw
YXJ0IG9mJm5ic3A7Jm5ic3A7SVB2NiBwcmVmaXggcG9vbCBvZiBOQVIgZm9yIGFsbG9jYXRpb24g
aWYgZmVhc2libGUuJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7PGJyPjxicj4oSSB0aGluayB0aGF0
J3Mgbm90IGEgd2FzdGUgb2YgcHJlZml4ZXMgd2hlcmUgdGhlIHByZWZpeCBpcyBhc3NpZ25lZCAm
cXVvdDtwZXIgTU4mcXVvdDsgaW4gdGhlIChJUHY2KQ0KIHBvaW50LXRvLXBvaW50IGxpbmsuOikg
KSZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzxicj48YnI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
IDxicj48YnI+U29tZSBtZW50aW9uIG1heSBuZWVkIHRvIGJlIHJlZmxlY3RlZCBpbiA0MDY4LWJp
cywgZm9yIGUuZy4sIDEpIFJ0U29sUHIgJmFtcDsgUHJSdEFkdiBleGNoYW5nZXMsPGJyPjxicj4y
KSBQcm94eWluZyBOQ29BIHdpdGggcHJveHkgbmVpZ2hib3IgY2FjaGUgZW50cnkgaW4gTkFSYW5k
IDMpIERBRCBjaGVjaywgc29tZSBvciBhbGwgb2YgdGhlc2UgcHJvY2VkdXJlczxicj48YnI+bWF5
IGJlIG9taXR0ZWQgaW4gdGhlIHBvaW50LXRvLXBvaW50IGxpbmsuJm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7PGJyPjxicj48YnI+PGJyPkJ1dCBJIGRvbid0IHRoaW5rIGl0J3MgYSBuZXcgbW9kZWwg
YnV0IGEgd2F5IG9mIGhvdyB0aGUgZXhpc3RpbmcgZm1pcHY2IGNhbiBiZSBhcHBsaWVkIG92ZXIg
dGhlIHBvaW50LXRvLXBvaW50IGxpbmsuJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7IDxicj48YnI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxicj48YnI+
LSBSZWdhcmRzLCA8YnI+PGJyPkhlZWppbi4gPGJyPjxicj48YnI+PGJyPi0tLS0tLS0gT3JpZ2lu
YWwgTWVzc2FnZSAtLS0tLS0tPGJyPjxicj5TZW5kZXIgOiBSYWplZXYgS29vZGxpJmx0O3JhamVl
di5rb29kbGlAbm9raWEuY29tJmd0Ozxicj48YnI+RGF0ZSZuYnNwOyZuYnNwOyA6IDIwMDctMDYt
MDUgMDY6MDg8YnI+PGJyPlRpdGxlJm5ic3A7Jm5ic3A7OiBSZTogW01pcHNob3BdIFJlOiBbMTZO
R10gRlc6IENhbGwgZm9yIFJldmlldyBvbiBGTUlQNiBvdmVyIElFRUU4MDIuMTZlIE5ldHdvcmtz
PGJyPjxicj48YnI+PGJyPjxicj48YnI+SGkgRnJhbmssPGJyPjxicj48YnI+PGJyPk1heSBiZSB3
ZSBhcmUgZ29pbmcgaW4gY2lyY2xlcyBoZXJlLi4gSSBoYXZlIG5vdCBzZWVuIHdoeQ0KIHRoZSBj
dXJyZW50IG1vZGVsIGNhbm5vdCB3b3JrIGZvciB0aGUgc2NlbmFyaW8geW91IGhhdmUgaW4gbWlu
ZC4gSWYgdGhlcmUgaXMgYW4gaXNzdWUsIHRoZSBXRyBwcm9jZXNzIGlzIHRvIGJyaW5nIGl0IHVw
IGFuZCBwcm9wb3NlIHRleHQuIEl0JmFtcDsjODIxNztzIG1vcmUgcHJvZHVjdGl2ZSB0aGF0IHdh
eS4gSSBhbSB3aWxsaW5nIHRvIGNsYXJpZnkgaW4gdGhlIGJpcyB2ZXJzaW9uLiBTb21lIG1vcmUg
cmVwbGllcyBiZWxvdy4uPGJyPjxicj4gPGJyPjxicj48YnI+PGJyPjEgJnF1b3Q7KEFQLUlELCBB
Ui1JbmZvKSB0dXBsZSBDb250YWlucyBhbiBhY2Nlc3Mgcm91dGVyJ3MgTDIgYW5kIElQJm5ic3A7
Jm5ic3A7YWRkcmVzc2VzLCBhbmQ8YnI+PGJyPiZuYnNwOyZuYnNwO3ByZWZpeCB2YWxpZCBvbiB0
aGUgaW50ZXJmYWNlIHRvIHdoaWNoIHRoZSZuYnNwOyZuYnNwO0FjY2VzcyBQb2ludCAoaWRlbnRp
ZmllZCBieSBBUC1JRCkgaXMgYXR0YWNoZWQuJm5ic3A7Jm5ic3A7PGJyPjxicj4gVGhlIHRyaXBs
ZXQmbmJzcDsmbmJzcDtbUm91dGVyJ3MmbmJzcDsmbmJzcDtMMiBhZGRyZXNzLCBSb3V0ZXIncyBJ
UCBhZGRyZXNzIGFuZCBQcmVmaXhdIGlzIGNhbGxlZCZuYnNwOyZuYnNwOyZxdW90O0FSLUluZm8m
cXVvdDsmcXVvdDsuPGJyPjxicj4gPGJyPjxicj49Jmd0OyBIZXJlLCBwcmVmaXggaXMgQVIncyBw
aHlzaWNhbCBpbnRlcmZhY2UmbmJzcDsmbmJzcDtwcmVmaXggaXMgdXNlZCBmb3IgTkNvQSBmb3Jt
dWxhdGlvbi48YnI+PGJyPiZuYnNwOyZuYnNwO0FzIHlvdSBrbm93LCB0aGlzIHByZWZpeCZuYnNw
OyZuYnNwO2lzIHVzZWxlc3MgZm9yIFAtdG8tUCBsaW5rIG1vZGVsLjxicj48YnI+PGJyPjxicj5S
YWplZXY6Jmd0OyB5b3UgY291bGQgaW50ZXJwcmV0IGl0Jm5ic3A7Jm5ic3A7dGhhdCB3YXksIGJ1
dCB5b3UgZG9uJmFtcDsjODIxNzt0IGhhdmUgdG8uIFRoZSBwb2ludCBJIGFtIHRyeWluZyB0byBt
YWtlIGlzIHRoYXQNCiB0aGUmbmJzcDsmbmJzcDtjdXJyZW50IG1vZGVsIHdvcmtzIGZvciB0aGUg
c2NlbmFyaW8geW91IGFyZSBlbnVtZXJhdGluZy48YnI+PGJyPiA8YnI+PGJyPkZyYW5rPSZndDsg
ZG9uJ3QgeW91IHRoaW5rIHRoZSBjb25jZXB0IG9mIHRoZSZuYnNwOyZuYnNwO3BlcmZpeCBpcyB0
b28gZmxleGlibGUgdGhhdCBkaWZmZXJlbnQgcGVvcGxlIGNhbiBoYXZlIHRoZWlyIG93biBkaWZm
ZXJlbnQmbmJzcDsmbmJzcDt1bmRlcnN0YW5kaW5nPyZuYnNwOyZuYnNwO0luIHlvdXIgZHJhZnQs
IHRoZSBwcmVmaXggaXMgZGVmaW5pdGVseSB0aGUgcHJlZml4IG9mJm5ic3A7Jm5ic3A7QVIgcGh5
c2ljYWwgaW50ZXJmYWNlLiBJIHRoaW5rIHRoZXJlIGlzIG5vdCBhbWJpZ3VvdXMuPGJyPjxicj48
YnI+PGJyPlJhamVldi8yLzomZ3Q7IEZpcnN0LCBpdCBpcyBub3QgbXkgZHJhZnQ7IGl0IGlzIHRo
ZSBXRyBkb2N1bWVudC4gU2Vjb25kLCBpdCBpcyBub3QgY2xlYXIgdG8gbWUgd2h5IHlvdSB3b3Vs
ZCBlcXVhdGUgdGhlIHByZWZpeCB0byBwaHlzaWNhbCBpbnRlcmZhY2UuIDQwNjggb25seSBzYXlz
IGl0IGlzIHRoZSBwcmVmaXggdmFsaWQgb24gdGhlIGludGVyZmFjZSB0aGUgTU4gaXMgYXR0YWNo
aW5nIHRvLCBhbmQgSSBhbSB1bmFibGUgdG8gc2VlIHdoYXQmYW1wOyM4MjE3O3MgdGhlIHByb2Js
ZW0uPGJyPjxicj48YnI+PGJyPklmIHlvdSBhcmUgdHJ5aW5nIHRvIG1hcCBpdCB0byBwdHAgbW9k
ZWwsIHRoYXQmYW1wOyM4MjE3O3MgZmluZS4gQnV0LCBwbGVhc2UgZG9uJmFtcDsjODIxNzt0IG1h
a2UgYXNzdW1wdGlvbnMgd2hpY2ggbm90IGludGVuZGVkLCBub3IgYXJlIG5lY2Vzc2FyeS48YnI+
PGJyPiA8YnI+PGJyPiA8YnI+PGJyPkFuIEFSIG1heSB1c2UgcGVyLW1vYmlsZSBwcmVmaXggYW5k
IGFuIGFnZ3JlZ2F0ZSBwcmVmaXggb24gdGhlJm5ic3A7Jm5ic3A7aW50ZXJmYWNlLiBBcyBJIHNh
aWQsIGFnZ3JlZ2F0ZSBwcmVmaXggY291bGQgYmUNCiB3aGF0IGlzIGFkdmVydGlzZWQgaW4mbmJz
cDsmbmJzcDtQclJ0QWR2LiBUaGUgTU4gY2FuIGZvcm11bGF0ZSBhIHByb3NwZWN0aXZlIE5Db0Eg
dXNpbmcgdGhhdCwgYnV0IHJlY2VpdmUgYSZuYnNwOyZuYnNwO2RpZmZlcmVudCBOQ29BIGZyb20g
TkFSLCBiYXNlZCBvbiB0aGUgcGVyLW1vYmlsZSBwcmVmaXguIDxicj48YnI+IDxicj48YnI+RnJh
bmsgPSZndDtJbiBmYWN0LCZuYnNwOyZuYnNwO3RoaXMgaXMgbm90IGJpZyBkaWZmZXJlbnQgZnJv
bSBvdXIgcHJvcHNvYWwmbmJzcDsmbmJzcDtpbiBkcmFmdC14aWEtbWlwc2hvcC1mbWlwLXB0cC0w
MCA8YnI+PGJyPjxicj48YnI+UmFqZWV2Oi8yLyZndDsgSSBhbSBub3QgcHJvcG9zaW5nIGEgbmV3
IG1vZGVsIGFib3ZlLiBKdXN0IHNob3dpbmcgaG93IHRoZSBleGlzdGluZyBtb2RlbCBjYW4gYmUg
dXNlZC48YnI+PGJyPjxicj48YnI+SSBjYW4gaW1hZ2luZSBvdGhlciB3YXlzIHRvIG1hbmFnZSZu
YnNwOyZuYnNwO3RoZSBwcmVmaXguIDxicj48YnI+IDxicj48YnI+RnJhbmsgPSZndDsgSSZuYnNw
OyZuYnNwO2Fsc28gaGF2ZSBhIHJldmlzZWQgZG9jdW1lbnQmbmJzcDsmbmJzcDt3aGljaCBlbGFi
b3JhdGluZyBvdGhlciBhbHRlcm5hdGl2ZXMsIGFuZCB3ZSBjYW4gY29vcGVyYXRlJm5ic3A7Jm5i
c3A7Ljxicj48YnI+PGJyPjxicj5SYWplZXY6Jmd0OyBJZiB5b3VyIHF1ZXN0aW9uIGlzIHdpbGwg
aXQgd29yayB3aXRoIHBlci1tb2JpbGUmbmJzcDsmbmJzcDtwcmVmaXgsIHllcy4gRWl0aGVyIEZC
YWNrIG9yIE5BQUNLIGNhbiBwcm92aWRlIHRoZSBOQ29BIHRoYXQgdGhlIE5BUiB3YW50cyZuYnNw
OyZuYnNwO3RoZSBNTiB0byB1c2UuIDxicj48YnI+Jm5ic3A7Jm5ic3A7IDxicj48YnI+RnJhbmsg
PSZndDsgVGhlIGV4Y2hhbmdlIG9mIFJ0U29sUHIgYW5kIFByUnRBZHYgaXMgdG8gZm9ybXVsYXRl
IGEgbmV3IENvQSB3aGlsZSBpcyB1c2VsZXNzJm5ic3A7Jm5ic3A7aW4gcC10LXANCiBtb2RlbC4m
bmJzcDsmbmJzcDtJdCBpcyBhIHdhc3RlIG9mIGFpciBpbnRlcmZhY2UmbmJzcDsmbmJzcDtyZXNv
dXJjZS48YnI+PGJyPjxicj48YnI+UmFqZWV2Oi8yLyZndDsgVGhhdCZhbXA7IzgyMTc7cyBkZWJh
dGFibGUsIGFuZCBpcyB1cCB0byBlYWNoIHRlY2hub2xvZ3kgdGhhdCBpbXBsZW1lbnRzIEZNSVAu
IDxicj48YnI+IDxicj48YnI+IDxicj48YnI+RnJhbmsgPSZndDsgUC10by1QIHNjZW5hcmlvIGlz
IGFkb3B0ZWQgYnkmbmJzcDsmbmJzcDtXaU1BWC8zR1BQMiwgd2hpbGUgSSBoYXZlIGxpdHRsZSBp
ZGVhIGFib3V0IHByb21pc2luZyZuYnNwOyZuYnNwO2RlcGxveW1lbnQgb2Ygc2hhcmVkIGxpbmsg
bW9kZWwuPGJyPjxicj48YnI+PGJyPlJhamVldjovMi8mZ3Q7IEdvb2QuJm5ic3A7Jm5ic3A7UkZD
IDQwNjggaXMgbm90IGFib3V0IHNoYXJlZCBsaW5rIG9ubHkuIEl0JmFtcDsjODIxNztzIHlvdXIg
aW50ZXJwcmV0YXRpb24uIDxicj48YnI+IDxicj48YnI+SU1ITywgeW91ciBzaW1wbGlmaWVkIHBy
b3Bvc2FsIGNhbid0IHNvbHZlIHRoZSZuYnNwOyZuYnNwO3Byb3BsZW0gdmVyeSB3ZWxsLjxicj48
YnI+IDxicj48YnI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IFJhamVldjovMi8mZ3Q7IFlv
dSBoYXZlIG5vdCBzaG93biB3aHkgbXkgZXhwbGFuYXRpb24gb24gaG93IHRoZSBjdXJyZW50IG1v
ZGVsIGNhbiB3b3JrIHdpbGwgbm90Jm5ic3A7Jm5ic3A7d29yay4gQXMgSSBzdWdnZXN0ZWQgZWFy
bGllciwgaWYgdGhlcmUgaXMgYW55IHNwZWNpZmljIGlzc3VlIHRoYXQgbmVlZHMgdG8gYmUgYWRk
cmVzc2VkLCBpdCBpcyBwcm9kdWN0aXZlIHRvIHByb3Bvc2UgdGhlIGlzc3VlIGFuZCB0ZXh0LiA8
YnI+PGJyPjxicj48YnI+LVJhamVldjxicj48YnI+PGJyPjxicj4gPGJyPjxicj48YnI+PGJyPi0t
IDxicj48YnI+PGENCiB0YXJnZXQ9Il9ibGFuayIgaHJlZj0iaHR0cDovL3Blb3BsZS5ub2tpYS5u
ZXQvJTdFcmFqZWV2Ij5odHRwOi8vcGVvcGxlLm5va2lhLm5ldC9+cmFqZWV2PC9hPiA8YnI+PGJy
Pjxicj48YnI+PGJyPjxicj4NCiAgICAgICAgICAgICAgICA8cD5fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4xNk5HIG1haWxpbmcgbGlzdDxicj4xNk5H
QGlldGYub3JnPGJyPjxhIHRhcmdldD0iX2JsYW5rIiBocmVmPSJodHRwczovL3d3dzEuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby8xNm5nIj5odHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby8xNm5nPC9hPjxicj48L2Rpdj48L2Rpdj48YnI+PC9kaXY+PC9kaXY+PC9ib2R5Pjwv
SFRNTD4=





--===============0794305476==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng

--===============0794305476==--



From 16ng-bounces@ietf.org Mon Jun 11 19:42:29 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxtWO-0005zz-OF; Mon, 11 Jun 2007 19:42:04 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1HxtWN-0005zq-BZ
	for 16ng-confirm+ok@megatron.ietf.org; Mon, 11 Jun 2007 19:42:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HxtWN-0005zi-0t
	for 16ng@ietf.org; Mon, 11 Jun 2007 19:42:03 -0400
Received: from web81904.mail.mud.yahoo.com ([68.142.207.183])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HxtWL-0007vU-Gu
	for 16ng@ietf.org; Mon, 11 Jun 2007 19:42:03 -0400
Received: (qmail 99784 invoked by uid 60001); 11 Jun 2007 23:42:01 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
	b=zxK4aPthaLLseySFYeJxy4NyNHkiOUpTB8KE0GsQKtxw1/DPsOJ+Pb9n3dLYsBvzB78OJjioABLNJZsGdAlZoEAbW4ljsMgXGTqhXL07mdY9UuIW5m5dyXKmZdBABuhvOgUlfp75daNGjy5xEw+312+M8Yfu5BP1QjpxWx4SmnE=;
X-YMail-OSG: 477W3gAVM1lZk0lSo1RUrNgJS1FWn8ebApEgu2ekPBgXowE0.7nElyBYz6EXDL1ty1hzdT_9ggymQHkaIKLfVuTDMGi3RLDjTAcDaCM_liESbvD.vFk-
Received: from [131.107.0.103] by web81904.mail.mud.yahoo.com via HTTP;
	Mon, 11 Jun 2007 16:42:00 PDT
X-Mailer: YahooMailRC/478 YahooMailWebService/0.7.41.14
Date: Mon, 11 Jun 2007 16:42:00 -0700 (PDT)
From: gabriel montenegro <g_e_montenegro@yahoo.com>
To: 16ng@ietf.org
MIME-Version: 1.0
Message-ID: <37127.97262.qm@web81904.mail.mud.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Subject: [16NG] fyi: Wimax Forum NWG 1.0.0 specification published
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1528114533=="
Errors-To: 16ng-bounces@ietf.org

--===============1528114533==
Content-Type: multipart/alternative; boundary="0-530777942-1181605320=:97262"

--0-530777942-1181605320=:97262
Content-Type: text/plain; charset=iso-8859-7
Content-Transfer-Encoding: quoted-printable

Folks,=0A=0AThe WiMAX forum has sent a liaison letter to the IETF to inform=
 of the publication of Release 1.0.0 of the NWG (network working group)=0As=
pecification. Below, I paste the ASCII equivalent of the content of the lia=
ison letter pointing at the URL for the specification. Additionally,=0Ather=
e is a "change request" (CR) process in place to fix bugs in release 1.0.0.=
 The expectation is that revisions of release 1.0.0 with=0Aincorporated CRs=
 will be published every 6 months or so.=0A=0Atnx,=0A=0A-gabriel=0A=0A-----=
--------------------------------------=0A=0A=0A=0A=0A=0A =0A=0A=0A =0A=0A=
=0A                                    June 10th,=0A2007=0A=0A=0A =0A=0A=0A=
To:       Russ Housley,=0AIETF chair=0A=0A=0A =0A=0A=0Acc:        Jari Arkk=
o,=0AInternet Area Director, IETF=0A=0A=0A            Mark=0ATownsley, Inte=
rnet Area Director, IETF=0A=0A=0A =0A=0A=0AFrom:   Prakash Iyer,=0AChair, W=
iMAX Forum Network Working Group (NWG), Intel Corporation=0A=0A=0A =0A=0A=
=0A =0A=0A=0ASubject:  WiMAX=0ANetwork Architecture Specification (Release =
1.0.0) published=0A=0A=0A =0A=0A=0A =0A=0A=0ADear Russ,=0A=0A=0A =0A=0A=0AT=
he WiMAX Forum=A2s =0ANetwork Working Group (NWG) would like to inform the =
IETF that NWG has=0Acompleted the first release of the WiMAX Network Archit=
ecture specification.=0AThe specification was approved by the WiMAX Forum B=
oard on April 19th=0A2007 and Forum-wide mandatory IPR review was completed=
 on June 2nd=0A2007. The specification, including all Stage 2 and 3 section=
s, is posted to the=0AWiMAX Forum website and publicly accessible via the f=
ollowing URL:=0A=0A=0A =0A=0A=0Ahttp://www.wimaxforum.org/technology/docume=
nts/WiMAXNetworkArchitectureStage2-3Rel1.0.0.zip=0A=0A=0A =0A=0A=0AWe=0Aloo=
k forward to receiving any comments that you may have on this specification=
.=0A=0A=0A =0A=0A=0ABest=0ARegards.=0A=0A=0A =0A=0A=0A =0A=0A=0A =0A=0A=0Ac=
c:        Bruce=0AHolloway, WiMAX Forum Counsel=0A=0A=0A            Alper=
=0AYegin, Samsung =0A=0A=0ARon Resnick, President WiMAX Forum,=0AIntel Corp=
oration=0A=0A=0AMax Riegel, Co-Chair, NWG, Siemens=0A=0A=0AYong Chang, Co-C=
hair, NWG, Samsung=0A=0A=0A =0A=0A=0A=0A=0A
--0-530777942-1181605320=:97262
Content-Type: text/html; charset=iso-8859-7
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:times new roman,new york,times,serif;fon=
t-size:12pt"><div>Folks,<br><br>The WiMAX forum has sent a liaison letter t=
o the IETF to inform of the publication of Release 1.0.0 of the NWG (networ=
k working group)<br>specification. Below, I paste the ASCII equivalent of t=
he content of the liaison letter pointing at the URL for the specification.=
 Additionally,<br>there is a "change request" (CR) process in place to fix =
bugs in release 1.0.0. The expectation is that revisions of release 1.0.0 w=
ith<br>incorporated CRs will be published every 6 months or so.<br><br>tnx,=
<br><br>-gabriel<br><br>-------------------------------------------<b style=
=3D""><span style=3D"font-family: &quot;Helvetica&quot;,&quot;sans-serif&qu=
ot;;"></span><o:p></o:p></b>=0A=0A<p class=3D"Originator" style=3D"margin-l=
eft: 3.75in;"><!--[if gte vml 1]><v:shapetype=0A id=3D"_x0000_t75" coordsiz=
e=3D"21600,21600" o:spt=3D"75" o:preferrelative=3D"t"=0A path=3D"m@4@5l@4@1=
1@9@11@9@5xe" filled=3D"f" stroked=3D"f">=0A <v:stroke joinstyle=3D"miter"/=
>=0A <v:formulas>=0A  <v:f eqn=3D"if lineDrawn pixelLineWidth 0"/>=0A  <v:f=
 eqn=3D"sum @0 1 0"/>=0A  <v:f eqn=3D"sum 0 0 @1"/>=0A  <v:f eqn=3D"prod @2=
 1 2"/>=0A  <v:f eqn=3D"prod @3 21600 pixelWidth"/>=0A  <v:f eqn=3D"prod @3=
 21600 pixelHeight"/>=0A  <v:f eqn=3D"sum @0 0 1"/>=0A  <v:f eqn=3D"prod @6=
 1 2"/>=0A  <v:f eqn=3D"prod @7 21600 pixelWidth"/>=0A  <v:f eqn=3D"sum @8 =
21600 0"/>=0A  <v:f eqn=3D"prod @7 21600 pixelHeight"/>=0A  <v:f eqn=3D"sum=
 @10 21600 0"/>=0A </v:formulas>=0A <v:path o:extrusionok=3D"f" gradientsha=
peok=3D"t" o:connecttype=3D"rect"/>=0A <o:lock v:ext=3D"edit" aspectratio=
=3D"t"/>=0A</v:shapetype><v:shape id=3D"_x0000_s1026" type=3D"#_x0000_t75" =
style=3D'position:absolute;=0A left:0;text-align:left;margin-left:-4pt;marg=
in-top:-1in;width:62.65pt;=0A height:67.8pt;z-index:-1' wrapcoords=3D"14312=
 0 6361 859 4240 1227 3975 2823 4108 4295 6361 5891 5566 6259 3843 7486 371=
0 8223 3710 9695 3843 10309 6626 11782 7553 11782 10601 13745 -133 15095 -1=
33 18532 9674 19636 3313 19636 2783 19759 2783 21477 18817 21477 18420 1963=
6 21467 18655 21600 18409 21070 17673 21600 15095 10734 13745 10204 11782 1=
0866 11782 14709 10064 14842 9818 16829 7855 17625 5891 18022 3927 17890 14=
73 16167 123 15372 0 14312 0">=0A <v:imagedata src=3D"file:///C:\Users\gmon=
te\AppData\Local\Temp\msohtmlclip1\01\clip_image001.wmz"=0A  o:althref=3D"f=
ile:///C:\Users\gmonte\AppData\Local\Temp\msohtmlclip1\01\clip_image002.pcz=
"=0A  o:title=3D"wmx_forum_color_logo"/>=0A <w:wrap type=3D"tight"/>=0A</v:=
shape><![endif]--><!--[if !vml]--><br><!--[endif]--></p>=0A=0A<p class=3D"O=
riginator" style=3D"margin-left: 3.75in;"><o:p>&nbsp;</o:p></p>=0A=0A<p cla=
ss=3D"Originator" style=3D"margin-left: 3.75in;"><o:p>&nbsp;</o:p></p>=0A=
=0A<p class=3D"Originator" style=3D"margin-left: 3.75in;"><span style=3D"">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>June 10=
<sup>th</sup>,=0A2007</p>=0A=0A<p class=3D"Originator"><o:p>&nbsp;</o:p></p=
>=0A=0A<p class=3D"MsoNormal">To:<span style=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; </span>Russ Housley,=0AIETF chair</p>=0A=0A<p class=3D"MsoNorma=
l"><o:p>&nbsp;</o:p></p>=0A=0A<p class=3D"MsoNormal">cc: <span style=3D"">&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Jari Arkko,=0AInternet Area Dire=
ctor, IETF</p>=0A=0A<p class=3D"MsoNormal"><span style=3D"">&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Mark=0ATownsley,=
 Internet Area Director, IETF</p>=0A=0A<p class=3D"MsoNormal"><o:p>&nbsp;</=
o:p></p>=0A=0A<p class=3D"MsoNormal">From:<span style=3D"">&nbsp;&nbsp; </s=
pan>Prakash Iyer,=0AChair, WiMAX Forum Network Working Group (NWG), Intel C=
orporation</p>=0A=0A<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>=0A=0A<p cl=
ass=3D"MsoNormal"><o:p>&nbsp;</o:p></p>=0A=0A<p class=3D"MsoNormal">Subject=
:<span style=3D"">&nbsp; </span>WiMAX=0ANetwork Architecture Specification =
(Release 1.0.0) published</p>=0A=0A<p class=3D"MsoNormal"><o:p>&nbsp;</o:p>=
</p>=0A=0A<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>=0A=0A<p class=3D"Mso=
Normal">Dear Russ,</p>=0A=0A<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>=0A=
=0A<p class=3D"MsoNormal">The WiMAX Forum=A2s<span style=3D"">&nbsp;=0A</sp=
an>Network Working Group (NWG) would like to inform the IETF that NWG has=
=0Acompleted the first release of the WiMAX Network Architecture specificat=
ion.=0AThe specification was approved by the WiMAX Forum Board on April 19<=
sup>th</sup>=0A2007 and Forum-wide mandatory IPR review was completed on Ju=
ne 2<sup>nd</sup>=0A2007. The specification, including all Stage 2 and 3 se=
ctions, is posted to the=0AWiMAX Forum website and publicly accessible via =
the following URL:</p>=0A=0A<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>=0A=
=0A<p class=3D"MsoNormal"><a href=3D"http://www.wimaxforum.org/technology/d=
ocuments/WiMAXNetworkArchitectureStage2-3Rel1.0.0.zip">http://www.wimaxforu=
m.org/technology/documents/WiMAXNetworkArchitectureStage2-3Rel1.0.0.zip</a>=
</p>=0A=0A<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>=0A=0A<p class=3D"Mso=
Normal" style=3D"text-align: justify;"><span style=3D"" lang=3D"EN-GB">We=
=0Alook forward to receiving any comments that you may have on this specifi=
cation.<o:p></o:p></span></p>=0A=0A<p class=3D"MsoNormal" style=3D"text-ali=
gn: justify;"><span style=3D"" lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>=
=0A=0A<p class=3D"MsoNormal" style=3D"text-align: justify;"><span style=3D"=
" lang=3D"EN-GB">Best=0ARegards.<o:p></o:p></span></p>=0A=0A<p class=3D"Mso=
Normal" style=3D"text-align: justify;"><span style=3D"" lang=3D"EN-GB"><o:p=
>&nbsp;</o:p></span></p>=0A=0A<p class=3D"MsoNormal" style=3D"text-align: j=
ustify;"><span style=3D"" lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>=0A=0A=
<p class=3D"MsoNormal" style=3D"text-align: justify;"><span style=3D"" lang=
=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>=0A=0A<p class=3D"MsoNormal">cc:<spa=
n style=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Bruce=0AHoll=
oway, WiMAX Forum Counsel</p>=0A=0A<p class=3D"MsoNormal"><span style=3D"">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>A=
lper=0AYegin, Samsung </p>=0A=0A<p class=3D"MsoNormal" style=3D"text-indent=
: 0.5in;">Ron Resnick, President WiMAX Forum,=0AIntel Corporation</p>=0A=0A=
<p class=3D"MsoNormal" style=3D"text-indent: 0.5in;">Max Riegel, Co-Chair, =
NWG, Siemens</p>=0A=0A<p class=3D"MsoNormal" style=3D"text-indent: 0.5in;">=
Yong Chang, Co-Chair, NWG, Samsung</p>=0A=0A<p class=3D"MsoNormal" style=3D=
"text-align: justify;"><o:p>&nbsp;</o:p></p>=0A=0A<br></div></div></body></=
html>
--0-530777942-1181605320=:97262--



--===============1528114533==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng

--===============1528114533==--





From 16ng-bounces@ietf.org Wed Jun 13 21:17:27 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hydxm-0000BR-Tj; Wed, 13 Jun 2007 21:17:26 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1Hydxl-00007I-HH
	for 16ng-confirm+ok@megatron.ietf.org; Wed, 13 Jun 2007 21:17:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hydxl-00005b-70
	for 16ng@ietf.org; Wed, 13 Jun 2007 21:17:25 -0400
Received: from nz-out-0506.google.com ([64.233.162.236])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hydxj-0003RQ-Vk
	for 16ng@ietf.org; Wed, 13 Jun 2007 21:17:25 -0400
Received: by nz-out-0506.google.com with SMTP id z31so377939nzd
	for <16ng@ietf.org>; Wed, 13 Jun 2007 18:17:23 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=TggU7dzs8KZ+xOfukU80iaXCKGSkiG0gebdDclPwwf5+inYtJ0V7/autGpmlifAhVYuYbSHXJn5Xyf0YHvTx2L29RL3mI9/FYWzOFv0yGt5n9pXUv62Ezyi7mOwlMfNpu+0wjHlPngcc5YKjExcSR4IahiQ6uMrraYKOr4eeY9A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=bH7JJqI6Sh43PsAT4BPSauNUQTFVsVdV8uR26IaYd1rRcNqO0+MhWr3eEKB3wUbi/YgM8OOMc/74IEZrs/VCT6gDHELe387r9S8XLfSq8LBqW6OSS9aPy3TYsmEdAq+DBS1caIPx9fLqcNNJ+2IA0KhNGvCujPSifn1E+bi86tc=
Received: by 10.114.209.1 with SMTP id h1mr1278340wag.1181783843017;
	Wed, 13 Jun 2007 18:17:23 -0700 (PDT)
Received: by 10.114.134.4 with HTTP; Wed, 13 Jun 2007 18:17:22 -0700 (PDT)
Message-ID: <f7c7d76e0706131817h3953f8cfldfa53bb02bab9942@mail.gmail.com>
Date: Thu, 14 Jun 2007 10:17:22 +0900
From: "Daniel Park" <soohongp@gmail.com>
To: "16ng@ietf.org" <16ng@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.5 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: =?EUC-KR?B?sei7877w?= <sekim@kt.co.kr>
Subject: [16NG] Comments on IPv4CS subnet model and ARP
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org

I am forwardig these comments originally from Sangeun Kim at KT to 16ng list.

========================================

6.  Subnet Model and IPv4 Address Assignment

The Subnet Model recommended for IPv4 over IEEE 802.16 using IP CS is
based on point-to-point link between MS and AR, hence each MS will be
on different IP subnet.

Proposed Changes: The Subnet Model recommended for IPv4 over IEEE
802.16 using IP CS is based on point-to-point link between MS and AR.


7.  Address Resolution Protocol

The IEEE 802.16 frame header does not contain the source and
destination MAC addresses, instead it uses the Connection Identifier
(CID) for the delivery of MAC frames.  This makes classical Address
Resolution Protocol (ARP) [3] trivial and unnecessary. > Also, IEEE
802.16 IPCS cannot classify the ARP packets as ARP runs directly over
 Ethernet and does not contain IP header.  Thus ARP packets are not
transmitted over IEEE 802.16 air interface when using IPCS.

Proposed Changes: The IEEE 802.16 frame header does not contain the
source and destination MAC addresses, instead it uses the Connection
Identifier (CID) for the delivery of MAC frames.  This makes classical
Address Resolution Protocol (ARP) [3] trivial and unnecessary. Also,
IEEE 802.16 IPCS cannot classify the ARP packets as ARP runs directly
over Ethernet and does not contain IP header. Thus ARP packets are not
  transmitted over IEEE 802.16 air interface when using IPCS. However
MS requires to proxy ARP function compatible with legacy IP host.


-- Daniel Park


_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng



From 16ng-bounces@ietf.org Thu Jun 14 20:22:06 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyzZm-0002Lo-5c; Thu, 14 Jun 2007 20:22:06 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1HyzZl-0002Lj-R8
	for 16ng-confirm+ok@megatron.ietf.org; Thu, 14 Jun 2007 20:22:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyzZl-0002LU-0o
	for 16ng@ietf.org; Thu, 14 Jun 2007 20:22:05 -0400
Received: from mail2.azairenet.com ([207.47.15.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyzZj-0002FK-Lr
	for 16ng@ietf.org; Thu, 14 Jun 2007 20:22:04 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [16NG] Comments on IPv4CS subnet model and ARP
Date: Thu, 14 Jun 2007 17:22:02 -0700
Message-ID: <D4AE20519DDD544A98B3AE9235C8A4C2B48575@moe.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [16NG] Comments on IPv4CS subnet model and ARP
thread-index: AceuIdD5z4nKqmrcQg6vZMxWNt/eKAAv9LZw
From: "Samita Chakrabarti" <Samita.Chakrabarti@AzaireNet.com>
To: "Daniel Park" <soohongp@gmail.com>,
	<16ng@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: =?ks_c_5601-1987?B?sei7877w?= <sekim@kt.co.kr>
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org



Please see in-line.
[SC>]=20
I am forwardig these comments originally from Sangeun Kim at KT to 16ng =
list.

[SC>] Thanks.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

6.  Subnet Model and IPv4 Address Assignment

The Subnet Model recommended for IPv4 over IEEE 802.16 using IP CS is
based on point-to-point link between MS and AR, hence each MS will be
on different IP subnet.

Proposed Changes: The Subnet Model recommended for IPv4 over IEEE
802.16 using IP CS is based on point-to-point link between MS and AR.

[SC>] Fine by me.

7.  Address Resolution Protocol

The IEEE 802.16 frame header does not contain the source and
destination MAC addresses, instead it uses the Connection Identifier
(CID) for the delivery of MAC frames.  This makes classical Address
Resolution Protocol (ARP) [3] trivial and unnecessary. > Also, IEEE
802.16 IPCS cannot classify the ARP packets as ARP runs directly over
 Ethernet and does not contain IP header.  Thus ARP packets are not
transmitted over IEEE 802.16 air interface when using IPCS.

Proposed Changes: The IEEE 802.16 frame header does not contain the
source and destination MAC addresses, instead it uses the Connection
Identifier (CID) for the delivery of MAC frames.  This makes classical
Address Resolution Protocol (ARP) [3] trivial and unnecessary. Also,
IEEE 802.16 IPCS cannot classify the ARP packets as ARP runs directly
over Ethernet and does not contain IP header. Thus ARP packets are not
  transmitted over IEEE 802.16 air interface when using IPCS. However
MS requires to proxy ARP function compatible with legacy IP host.

[SC>] Let's discuss the last sentence. MS requires to proxy ARP function =
compatible with legacy IP host: What is the expected configuration of =
the scenario in this case? The legacy IP host will not be on the same =
Wimax IPCS
link; thus our assumption was that they would be on different subnets.
Please clarify.


Regards,
-Samita

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng


_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng



From 16ng-bounces@ietf.org Thu Jun 14 23:05:11 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hz27a-0008HT-NN; Thu, 14 Jun 2007 23:05:10 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1Hz27Z-0008HO-UC
	for 16ng-confirm+ok@megatron.ietf.org; Thu, 14 Jun 2007 23:05:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hz27Z-0008HC-I9
	for 16ng@ietf.org; Thu, 14 Jun 2007 23:05:09 -0400
Received: from wa-out-1112.google.com ([209.85.146.179])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hz27Y-00078h-9s
	for 16ng@ietf.org; Thu, 14 Jun 2007 23:05:09 -0400
Received: by wa-out-1112.google.com with SMTP id j5so1079893wah
	for <16ng@ietf.org>; Thu, 14 Jun 2007 20:05:07 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=ByaVsB6Rd5a6uVRF/kR98YqdosC57hh8u3H3ZHOP/9EF5i7waESAqorUhaPJ2qDbAsKV7S2PTgvePJSNU2ES53qeI/GhpPqvkWuykB32jSi9r+gQQsMykQwxTW4ug8M540fdvljirTVnOskPLyVzwU5vKE17JGrovgUsox1TJXA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=juK/nb/zGaWeH7NGA1AYPk0bhfqkUxmaIbzX3ORLdIa5AV5bxcp3xKQAJtW4v4j1xgKRT8eDfp1DpwGmn+XkZK/4TW/HEAhQOyY0cL7HV5eY7/FaSGTVO7DZKPOel63nAOdU/ADDKwp6I91bx7VUtPlNFZCegWR/eg8B8+tSIos=
Received: by 10.115.106.7 with SMTP id i7mr2566965wam.1181876707389;
	Thu, 14 Jun 2007 20:05:07 -0700 (PDT)
Received: by 10.114.134.4 with HTTP; Thu, 14 Jun 2007 20:05:07 -0700 (PDT)
Message-ID: <f7c7d76e0706142005g734f6e07jb4baa723395984b1@mail.gmail.com>
Date: Fri, 15 Jun 2007 12:05:07 +0900
From: "Daniel Park" <soohongp@gmail.com>
To: "16ng@ietf.org" <16ng@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: =?EUC-KR?B?sei7877w?= <sekim@kt.co.kr>
Subject: [16NG] Draft agenda for 69th IETF
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org

Draft agenda for 69th IETF is now available:

http://www3.ietf.org/proceedings/07jul/agenda/16ng.txt

To speakers (CC list): Please send your material to chairs till July
14th (or earlier). All material will be uploaded on the 69th IETF
official website for participants as well as non-participants
conveniences.

Thanks in advance,

-- Daniel Park


_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng



From 16ng-bounces@ietf.org Sat Jun 16 14:02:36 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzcbY-00040S-GT; Sat, 16 Jun 2007 14:02:32 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1HzcbW-00040M-Rb
	for 16ng-confirm+ok@megatron.ietf.org; Sat, 16 Jun 2007 14:02:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzcbT-0003ye-7a
	for 16ng@ietf.org; Sat, 16 Jun 2007 14:02:27 -0400
Received: from web81908.mail.mud.yahoo.com ([68.142.207.187])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HzcbS-000239-MX
	for 16ng@ietf.org; Sat, 16 Jun 2007 14:02:27 -0400
Received: (qmail 14252 invoked by uid 60001); 16 Jun 2007 18:02:26 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
	b=omqjLkL/y2XjwDGYJxvPVJ0UyEAEHWMm0tnzuSyzkxBqTQ5KlkJv256YJnhpFkcd++WrovJD5ccNfdpzccu8JInmQZ5WBoanAYhWR4S2qecCXh8nrLUNtNoedIjAjdH/Zr29zSfDaLYV5fQ7mkgbbZ4vcYs7J7ZNnW9ZHEO6lFw=;
X-YMail-OSG: gf9yIFwVM1nKIWh1Z4O8Hu7d9al89znm1m_sJiv.OVc0X0GChOrYQt0aZ70z4KJu5r7DDoGUz.sz3pVOTrqD14lnXu4UYkkjac7kl6iZgVO2ZSSaidQ-
Received: from [24.16.90.95] by web81908.mail.mud.yahoo.com via HTTP;
	Sat, 16 Jun 2007 11:02:26 PDT
X-Mailer: YahooMailRC/478 YahooMailWebService/0.7.41.14
Date: Sat, 16 Jun 2007 11:02:26 -0700 (PDT)
From: gabriel montenegro <gabriel_montenegro_2000@yahoo.com>
To: 16ng@ietf.org
MIME-Version: 1.0
Message-ID: <235768.10253.qm@web81908.mail.mud.yahoo.com>
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Subject: [16NG] Fw: Request to forward the Nomcom 2007-8 Announcement to
	lists you manage
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0916439869=="
Errors-To: 16ng-bounces@ietf.org

--===============0916439869==
Content-Type: multipart/alternative; boundary="0-1885416107-1182016946=:10253"

--0-1885416107-1182016946=:10253
Content-Type: text/plain; charset=ascii

Please consider volunteering for NomCom this year.

-gabriel

----- Forwarded Message ----
From: Lakshminath Dondeti <ldondeti@qualcomm.com>
To: wgchairs@ietf.org; irsg@isi.edu; bofchairs@ietf.org
Sent: Saturday, June 16, 2007 9:55:05 AM
Subject: Request to forward the Nomcom 2007-8 Announcement to lists you manage

Folks,

We have around 50 volunteers so far for Nomcom 2007-8 voting member 
selection.  We need a lot more!  Not everyone subscribes to the 
IETF-Announce list.  Could you please forward the announcement 
https://datatracker.ietf.org/public/show_nomcom_message.cgi?id=1234 to 
WG, RG, BoF, Area lists that you manage?

Thanks in advance.

best regards,
Lakshminath






--0-1885416107-1182016946=:10253
Content-Type: text/html; charset=ascii

<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">Please consider volunteering for NomCom this year.<br><br>-gabriel<br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Forwarded Message ----<br>From: Lakshminath Dondeti &lt;ldondeti@qualcomm.com&gt;<br>To: wgchairs@ietf.org; irsg@isi.edu; bofchairs@ietf.org<br>Sent: Saturday, June 16, 2007 9:55:05 AM<br>Subject: Request to forward the Nomcom 2007-8 Announcement to lists you manage<br><br><div>Folks,<br><br>We have around 50 volunteers so far for Nomcom 2007-8 voting member <br>selection.&nbsp;&nbsp;We need a lot more!&nbsp;&nbsp;Not everyone subscribes to the <br>IETF-Announce list.&nbsp;&nbsp;Could you please forward the announcement <br><a target="_blank"
 href="https://datatracker.ietf.org/public/show_nomcom_message.cgi?id=1234">https://datatracker.ietf.org/public/show_nomcom_message.cgi?id=1234</a> to <br>WG, RG, BoF, Area lists that you manage?<br><br>Thanks in advance.<br><br>best regards,<br>Lakshminath<br><br></div></div><br></div></div></body></html>
--0-1885416107-1182016946=:10253--



--===============0916439869==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng

--===============0916439869==--





From 16ng-bounces@ietf.org Mon Jun 18 12:19:34 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0Jwx-0004hU-Nu; Mon, 18 Jun 2007 12:19:31 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1I0Jwx-0004hP-5a
	for 16ng-confirm+ok@megatron.ietf.org; Mon, 18 Jun 2007 12:19:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0Jww-0004hH-SI
	for 16ng@ietf.org; Mon, 18 Jun 2007 12:19:30 -0400
Received: from web84102.mail.mud.yahoo.com ([68.142.206.189])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1I0Jww-0006cB-FX
	for 16ng@ietf.org; Mon, 18 Jun 2007 12:19:30 -0400
Received: (qmail 85925 invoked by uid 60001); 18 Jun 2007 15:54:09 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID;
	b=RuHLWtzS/kjqIBy4+WzMBh3sn3lqdVHLB9TUmyQy3MAme3ufZ4+9aCIThDdmFkjlGly+QxtTutVgAjSmcBVLOG5ADKOapnTcbSEZTSENqnh2y74y1TK4YoEpE2PsjyWs88bOgjyBdQUJjmRPsBKpzzARkiGe7+xS37438Tylmxs=;
X-YMail-OSG: naMv2SAVM1mw6m9ktdGxiPSWLuKhuX49tLzHtpGo7aFwZm5ySznUenRbNNoJ3enKVJ5KMrtkSw--
Received: from [206.16.17.212] by web84102.mail.mud.yahoo.com via HTTP;
	Mon, 18 Jun 2007 08:54:09 PDT
X-Mailer: YahooMailRC/651.23.1 YahooMailWebService/0.7.41.14
Date: Mon, 18 Jun 2007 08:54:09 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: [16NG] Comments on IPv4CS subnet model and ARP
To: Samita Chakrabarti <samita.chakrabarti@azairenet.com>
MIME-Version: 1.0
Message-ID: <183536.85214.qm@web84102.mail.mud.yahoo.com>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: "16ng@ietf.org" <16ng@ietf.org>
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0702673777=="
Errors-To: 16ng-bounces@ietf.org

--===============0702673777==
Content-Type: multipart/alternative; boundary="0-744028593-1182182049=:85214"

--0-744028593-1182182049=:85214
Content-Type: text/plain; charset=ascii

Hi Samita,
  Please see inline.
Please include behcetsarikaya@yahoo.com in your reply.

Regards,

Behcet

Please see in-line.
[SC>] 
I am forwarding these comments originally from Sangeun Kim at KT to 16ng list.

[SC>] Thanks.
========================================

6.  Subnet Model and IPv4 Address Assignment

The Subnet Model recommended for IPv4 over IEEE 802.16 using IP CS is
based on point-to-point link between MS and AR, hence each MS will be
on different IP subnet.

Proposed Changes: The Subnet Model recommended for IPv4 over IEEE
802.16 using IP CS is based on point-to-point link between MS and AR.

[SC>] Fine by me.

[behcet] What is the difference between the two? Why change the original text?


7.  Address Resolution Protocol

The IEEE 802.16 frame header does not contain the source and
destination MAC addresses, instead it uses the Connection Identifier
(CID) for the delivery of MAC frames.  This makes classical Address
Resolution Protocol (ARP) [3] trivial and unnecessary. > Also, IEEE
802.16 IPCS cannot classify the ARP packets as ARP runs directly over
 Ethernet and does not contain IP header.  Thus ARP packets are not
transmitted over IEEE 802.16 air interface when using IPCS.

Proposed Changes: The IEEE 802.16 frame header does not contain the
source and destination MAC addresses, instead it uses the Connection
Identifier (CID) for the delivery of MAC frames.  This makes classical
Address Resolution Protocol (ARP) [3] trivial and unnecessary. Also,
IEEE 802.16 IPCS cannot classify the ARP packets as ARP runs directly
over Ethernet and does not contain IP header. Thus ARP packets are not
  transmitted over IEEE 802.16 air interface when using IPCS. However
MS requires to proxy ARP function compatible with legacy IP host.

[SC>] Let's discuss the last sentence. MS requires to proxy ARP function compatible with legacy IP host: What is the expected configuration of the scenario in this case? The legacy IP host will not be on the same Wimax IPCS
link; thus our assumption was that they would be on different subnets.
Please clarify.


Regards,
-Samita




--0-744028593-1182182049=:85214
Content-Type: text/html; charset=ascii

<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:14pt"><div style="font-family: times new roman,new york,times,serif; font-size: 14pt;"><pre><span style="font-weight: bold;">Hi Samita,</span><br><span style="font-weight: bold;">  Please see inline.<br>Please include behcetsarikaya@yahoo.com in your reply.<br><br>Regards,<br><br>Behcet<br><br></span>Please see in-line.<br>[SC&gt;] <br>I am forwarding these comments originally from Sangeun Kim at KT to 16ng list.<br><br>[SC&gt;] Thanks.<br>========================================<br><br>6.  Subnet Model and IPv4 Address Assignment<br><br>The Subnet Model recommended for IPv4 over IEEE 802.16 using IP CS is<br>based on point-to-point link between MS and AR, hence each MS will be<br>on different IP subnet.<br><br>Proposed Changes: The Subnet Model recommended for IPv4 over IEEE<br>802.16 using IP CS is based on point-to-point
 link between MS and AR.<br><br>[SC&gt;] Fine by me.<br><br><span style="font-weight: bold;">[behcet] What is the difference between the two? Why change the original text?</span><br><br><br>7.  Address Resolution Protocol<br><br>The IEEE 802.16 frame header does not contain the source and<br>destination MAC addresses, instead it uses the Connection Identifier<br>(CID) for the delivery of MAC frames.  This makes classical Address<br>Resolution Protocol (ARP) [3] trivial and unnecessary. &gt; Also, IEEE<br>802.16 IPCS cannot classify the ARP packets as ARP runs directly over<br> Ethernet and does not contain IP header.  Thus ARP packets are not<br>transmitted over IEEE 802.16 air interface when using IPCS.<br><br>Proposed Changes: The IEEE 802.16 frame header does not contain the<br>source and destination MAC addresses, instead it uses the Connection<br>Identifier (CID) for the delivery of MAC frames.  This makes classical<br>Address Resolution Protocol (ARP) [3] trivial and
 unnecessary. Also,<br>IEEE 802.16 IPCS cannot classify the ARP packets as ARP runs directly<br>over Ethernet and does not contain IP header. Thus ARP packets are not<br>  transmitted over IEEE 802.16 air interface when using IPCS. However<br>MS requires to proxy ARP function compatible with legacy IP host.<br><br>[SC&gt;] Let's discuss the last sentence. MS requires to proxy ARP function compatible with legacy IP host: What is the expected configuration of the scenario in this case? The legacy IP host will not be on the same Wimax IPCS<br>link; thus our assumption was that they would be on different subnets.<br>Please clarify.<br><br><br>Regards,<br>-Samita</pre><br><br><br></div></div></body></html>
--0-744028593-1182182049=:85214--



--===============0702673777==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng

--===============0702673777==--





From 16ng-bounces@ietf.org Mon Jun 18 14:36:40 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0M5e-0003Qj-L7; Mon, 18 Jun 2007 14:36:38 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1I0M5d-0003OZ-Ua
	for 16ng-confirm+ok@megatron.ietf.org; Mon, 18 Jun 2007 14:36:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0M5d-0003OR-L2
	for 16ng@ietf.org; Mon, 18 Jun 2007 14:36:37 -0400
Received: from mail2.azairenet.com ([207.47.15.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0M5c-000297-2D
	for 16ng@ietf.org; Mon, 18 Jun 2007 14:36:37 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [16NG] Comments on IPv4CS subnet model and ARP
Date: Mon, 18 Jun 2007 11:36:34 -0700
Message-ID: <D4AE20519DDD544A98B3AE9235C8A4C2B487E1@moe.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [16NG] Comments on IPv4CS subnet model and ARP
thread-index: AcexxHNblRjBLAy5RcOIhlOT1hSh3AAEZNAQ
From: "Samita Chakrabarti" <Samita.Chakrabarti@AzaireNet.com>
To: "Behcet Sarikaya" <sarikaya@ieee.org>,
	<behcetsarikaya@yahoo.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 17e5edc4dfd335965c1d21372171c01c
Cc: 16ng@ietf.org
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1988170615=="
Errors-To: 16ng-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1988170615==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7B1D7.99656032"

This is a multi-part message in MIME format.

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

=20

=20

Hi Behcet,
=20
Please see below.



6.  Subnet Model and IPv4 Address Assignment



The Subnet Model recommended for IPv4 over IEEE 802.16 using IP CS is

based on point-to-point link between MS and AR, hence each MS will be

on different IP subnet.



Proposed Changes: The Subnet Model recommended for IPv4 over IEEE

802.16 using IP CS is based on point-to-point
 link between MS and AR.



[SC>] Fine by me.



[behcet] What is the difference between the two? Why change the original
text?
[SC>]  As far as I understand the proposed change is requesting an
editorial change. If the current text in the draft is already clear
enough and folks in wg feel that there is no change necessary, we will
do accordingly.
=20
Thanks for bringing it up.
-Samita
=20
=20















------_=_NextPart_001_01C7B1D7.99656032
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@Batang";
	panose-1:2 3 6 0 0 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div><pre><b><i><font size=3D2 color=3Dnavy face=3D"Courier New"><span
style=3D'font-size:10.0pt;color:navy;font-weight:bold;font-style:italic'>=
Hi Behcet,<o:p></o:p></span></font></i></b></pre><pre><b><i><font
size=3D2 color=3Dnavy face=3D"Courier New"><span =
style=3D'font-size:10.0pt;color:navy;
font-weight:bold;font-style:italic'><o:p>&nbsp;</o:p></span></font></i></=
b></pre><pre><b><i><font
size=3D2 color=3Dnavy face=3D"Courier New"><span =
style=3D'font-size:10.0pt;color:navy;
font-weight:bold;font-style:italic'>Please see =
below.</span></font></i><br>
</b><br>
6.&nbsp; Subnet Model and IPv4 Address Assignment<br>
<br>
The Subnet Model recommended for IPv4 over IEEE 802.16 using IP CS =
is<br>
based on point-to-point link between MS and AR, hence each MS will =
be<br>
on different IP subnet.<br>
<br>
Proposed Changes: The Subnet Model recommended for IPv4 over IEEE<br>
802.16 using IP CS is based on point-to-point<o:p></o:p></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'> link =
between MS and AR.<br>
<br>
[SC&gt;] Fine by me.<br>
<br>
<b><span style=3D'font-weight:bold'>[behcet] What is the difference =
between the two? Why change the original text?<font
color=3Dnavy><span =
style=3D'color:navy'><o:p></o:p></span></font></span></b></span></font></=
pre><pre><b><i><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy;font-weight:bold;font-style:italic'>[SC&gt;] &nbsp;As far as =
I understand the proposed change is requesting an editorial change. If =
the current text in the draft is already clear enough and folks in wg =
feel that there is no change necessary, we will do =
accordingly.<o:p></o:p></span></font></i></b></pre><pre><b><i><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy;font-weight:bold;font-style:italic'><o:p>&nbsp;</o:p></span></=
font></i></b></pre><pre><b><i><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy;font-weight:bold;font-style:italic'>Thanks for bringing it =
up.<o:p></o:p></span></font></i></b></pre><pre><b><i><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy;font-weight:bold;font-style:italic'>-Samita<o:p></o:p></span><=
/font></i></b></pre><pre><b><i><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy;font-weight:bold;font-style:italic'><o:p>&nbsp;</o:p></span></=
font></i></b></pre><pre><b><i><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy;font-weight:bold;font-style:italic'><o:p>&nbsp;</o:p></span></=
font></i></b></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'><br>
<br>
<br>
<br>
<o:p></o:p></span></font></pre>

<p class=3DMsoNormal style=3D'margin-bottom:14.0pt'><font size=3D4
face=3D"Times New Roman"><span style=3D'font-size:14.0pt'><br>
<br>
<o:p></o:p></span></font></p>

</div>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C7B1D7.99656032--



--===============1988170615==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng

--===============1988170615==--





From 16ng-bounces@ietf.org Tue Jun 19 05:30:13 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0a2O-0001Pm-Pk; Tue, 19 Jun 2007 05:30:12 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1I0a2N-0001Pe-VH
	for 16ng-confirm+ok@megatron.ietf.org; Tue, 19 Jun 2007 05:30:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0a2N-0001PW-KX
	for 16ng@ietf.org; Tue, 19 Jun 2007 05:30:11 -0400
Received: from revol2.enst.fr ([137.194.2.14] helo=smtp2.enst.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0a2M-0004y7-Aj
	for 16ng@ietf.org; Tue, 19 Jun 2007 05:30:11 -0400
Received: from localhost (localhost.enst.fr [127.0.0.1])
	by smtp2.enst.fr (Postfix) with ESMTP id BE6DFB8A79
	for <16ng@ietf.org>; Tue, 19 Jun 2007 11:30:09 +0200 (CEST)
X-Virus-Scanned: amavisd-new at enst.fr
Received: from infres.enst.fr (infres.enst.fr [137.194.192.1])
	by smtp2.enst.fr (Postfix) with ESMTP id 91475B8A78
	for <16ng@ietf.org>; Tue, 19 Jun 2007 11:30:09 +0200 (CEST)
Received: from VAIO.enst.fr (mechmech.enst.fr [137.194.164.56])
	by infres.enst.fr (Postfix) with ESMTP id 37B8413CBB
	for <16ng@ietf.org>; Tue, 19 Jun 2007 11:30:09 +0200 (MEST)
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 19 Jun 2007 11:30:01 +0200
To: 16ng@ietf.org
From: Pascal Urien <Pascal.Urien@enst.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-Id: <20070619093009.37B8413CBB@infres.enst.fr>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Subject: [16NG] draft-urien-16ng-security-api-00.txt
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org

Hi Everybody,

  A new internet draft is available at

http://www.ietf.org/internet-drafts/draft-urien-16ng-security-api-00.txt

That deals with the critical topic of Wimax security.

I will attend to the next IETF meeting in Chicago, and i am ready to 
present this draft.

Best Regards

Pascal Urien

Draft Summary.
===========

This document describes a security Application Programming Interface
  (API), which aims at supporting tamper resistant devices that
  perform collaborative tasks with the IEEE 802.16 security sublayer.

  The security sublayer provides operators with strong protection from
  theft of service This security API enables to transfer critical
  calculations or protocol processing to trusted computers, such as
  smart cards or trusted platform modules (TPMs). 




_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng



From 16ng-bounces@ietf.org Tue Jun 19 05:53:19 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0aOk-0007L0-2l; Tue, 19 Jun 2007 05:53:18 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1I0Yhv-0000gY-PM
	for 16ng-confirm+ok@megatron.ietf.org; Tue, 19 Jun 2007 04:04:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0Yhs-0000gG-9F
	for 16ng@ietf.org; Tue, 19 Jun 2007 04:04:56 -0400
Received: from revol2.enst.fr ([137.194.2.14] helo=smtp2.enst.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0Yhq-0001OC-UR
	for 16ng@ietf.org; Tue, 19 Jun 2007 04:04:56 -0400
Received: from localhost (localhost.enst.fr [127.0.0.1])
	by smtp2.enst.fr (Postfix) with ESMTP id 583FBB8141
	for <16ng@ietf.org>; Tue, 19 Jun 2007 10:04:54 +0200 (CEST)
X-Virus-Scanned: amavisd-new at enst.fr
Received: from infres.enst.fr (infres.enst.fr [137.194.192.1])
	by smtp2.enst.fr (Postfix) with ESMTP id 29008B803D
	for <16ng@ietf.org>; Tue, 19 Jun 2007 10:04:53 +0200 (CEST)
Received: from VAIO.enst.fr (mechmech.enst.fr [137.194.164.56])
	by infres.enst.fr (Postfix) with ESMTP id B5EB313CBB
	for <16ng@ietf.org>; Tue, 19 Jun 2007 10:04:53 +0200 (MEST)
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 19 Jun 2007 10:04:46 +0200
To: 16ng@ietf.org
From: Pascal Urien <Pascal.Urien@enst.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-Id: <20070619080453.B5EB313CBB@infres.enst.fr>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
X-Mailman-Approved-At: Tue, 19 Jun 2007 05:53:17 -0400
Subject: [16NG] draft-urien-16ng-security-api-00.txt
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org

Hi Everybody,

  A new internet draft is available at

http://www.ietf.org/internet-drafts/draft-urien-16ng-security-api-00.txt

That deals with the critical topic of Wimax security.

I will attend to the next IETF meeting in Chicago, and i am ready to 
present this draft.

Best Regards

Pascal Urien

Draft Summary.
===========

This document describes a security Application Programming Interface
  (API), which aims at supporting tamper resistant devices that
  perform collaborative tasks with the IEEE 802.16 security sublayer.

  The security sublayer provides operators with strong protection from
  theft of service This security API enables to transfer critical
  calculations or protocol processing to trusted computers, such as
  smart cards or trusted platform modules (TPMs). 




_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng



From 16ng-bounces@ietf.org Thu Jun 21 08:49:23 2007
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1M6C-0006YQ-Te; Thu, 21 Jun 2007 08:49:20 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43)
	id 1I1M6C-0006YL-9x
	for 16ng-confirm+ok@megatron.ietf.org; Thu, 21 Jun 2007 08:49:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1M69-0006Y8-4s
	for 16ng@ietf.org; Thu, 21 Jun 2007 08:49:17 -0400
Received: from wip-cdc-wd.wipro.com ([203.91.201.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1M67-0007zh-Bd
	for 16ng@ietf.org; Thu, 21 Jun 2007 08:49:17 -0400
Received: from wip-cdc-wd.wipro.com (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 5B5F61805F
	for <16ng@ietf.org>; Thu, 21 Jun 2007 18:19:15 +0530 (IST)
Received: from blr-ec-bh02.wipro.com (blr-ec-bh02.wipro.com [10.201.50.92])
	by wip-cdc-wd.wipro.com (Postfix) with ESMTP id 4737B18058
	for <16ng@ietf.org>; Thu, 21 Jun 2007 18:19:15 +0530 (IST)
Received: from DEL-GGN-MBX01.wipro.com ([10.105.51.181]) by
	blr-ec-bh02.wipro.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 21 Jun 2007 18:19:22 +0530
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
Subject: RE: [16NG] IEEE 802.16 QoS parameters
Date: Thu, 21 Jun 2007 18:19:35 +0530
Message-ID: <D607371E06E45641947B21A8E95746B801AA4526@DEL-GGN-MBX01.wipro.com>
In-Reply-To: <dde9f3ed0706051201i21879de2ic8ee3d2ea9a00e98@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [16NG] IEEE 802.16 QoS parameters
Thread-Index: AcenrIMC96ZGUvkHSaCyt6NyWk5KSwMUuBiA
From: <keshav.chawla@wipro.com>
To: <denio@gprt.ufpe.br>
X-OriginalArrivalTime: 21 Jun 2007 12:49:22.0406 (UTC)
	FILETIME=[97436860:01C7B402]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: 16ng@ietf.org
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
	<mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org


Hi,

Provision for maintaining the Jitter lies with the receiver of the
packets and only if
some feedback mechanism is there, receiver can inform the sender about
the jitter.

At the sender's end it may not be possible to calculate jitter(even
based on queue stats),=20
as even if packet has gone out of the sender's queue, does not guarantee
it reaching the receiver's side.=20
At the receiver, it can be that Packet might not have reached or reached
but dropped due to jitter threshold=20
being reached/jitter buffer being full.

I think all sender can do is to pump out data at a regular rate over
time at which receiver is able to receive=20
and rest lies with the receiver.


regards,
Keshav

-----Original Message-----
From: Denio Mariz [mailto:denio@gprt.ufpe.br]=20
Sent: Wednesday, June 06, 2007 12:32 AM
To: 16ng@ietf.org
Subject: [16NG] IEEE 802.16 QoS parameters

Hi,

IEEE 802.16-2004 document defines some QoS parameters for admitted
connections, which includes maximum latency and maximum jitter. They are
defined as:

=3D=3D=3D=3D=3D=3D=3D
Maximum latency - The value of this parameter specifies the maximum
latency between the reception of a packet by the BS or SS on its network
interface and the forwarding of the packet to its RF Interface.

Maximum Jitter - This parameter defines the maximum delay variation
(jitter) for the connection.
=3D=3D=3D=3D=3D=3D

Assuming D1 and D2 as the delay measured for two consecutive packets, it
is common for end-to-end systems to compute the jitter J as J=3D|D1-D2|.

I am studying a scheduling algorithms for the download, which must run
inside the BS. This means that D1 and D2 are not available (or must be
avoided, since it would depend on measuring them at the mobile
terminal). So I am assuming that the algorithm must only consider
information from inside the BS (more specifically from queue
statistics).

So, I am wondering if it is possible to compute correctly the jitter for
packets assuming you can not watch the receiving end of the stream and
only consider info from the sender side.

TIA,

Denio Mariz


_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng


_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng



