Subject: [16ng] Comments 16NG PS Draft

From: Syam Madanapalli <[email-masked]>
Date: Tue, 4 Oct 2005 17:18:43 +0530

Hi,
Good to see this BoF coming up. And I have few comments/suggestions on the Problem Statement Draft
1. As many people in IETF unaware of 802.16, it maybe a good idea  to give a quick over view of 802.16.
Also the following document could be a good referencefor quick overview on 802.16IEEE Standard 802.16: A Technical Overview of theWirelessMAN™ Air Interface for Broadband Wireless Accesshttp://grouper.ieee.org/groups/802/16/docs/02/C80216-02_05.pdf
2. If you include a typical Network Architecture for802.16, then it may be easier to grasp problems inrunning the IETF protocols on 802.16 Networks.
e.g. Router Discovery, Next-hop resolution andRedirect may be trivial in scenario 1 whereas inScenario 3 these functions may need to be performed.
      SS0 ----|                 |     +-------+      SS1 ----|-----| BS/AR |-----                 |     +-------+      SSn ----|
               Scenario 1
      SS0 ----|                 |     +-------+         +-------+      SS1 ----|-----|  BS   |-------- |  AR   |                 |     +-------+         +-------+      SSn ----|
               Scenario 2

                                     |    +-------+                                     |--- |  AR1  |                                     |    +-------+      SS0 ----|                   |                 |     +-------+    |    +-------+      SS1 ----|-----|  BS   |----|--- |  AR2  |                 |     +-------+    |    +-------+      SSn ----|                   |                                     |    +-------+                                     |--- |  AR3  |                                     |    +-------+
               Scenario 3
Also we need to understand how the BS and ARs are connected.

3. A section on existing solutions for example RFC 2491(IPv6 over Non-Broadcast Multiple Access (NBMA) networks)and why such solutions do sufficient for 802.16 networks.One reason I see may be is that, generally NBMAtechnologies (ATM/Frame Relay) provides end to endnetwork, whereas 802.16 just specifies last mile (I amconsidering the mesh support is also part of last mile).I may be wrong somebody can correct me here.

4. It may also be a good idea to provide the goalsfor the solution space.
5. I think we should cover the IPv4 as well, I thinkthe WiMAX Forum NWG is currently focusing on IPv4as a mandatory protocol to support.

-Syam

----- Original Message -----From: <[email-masked]>To: <[email-masked]>Sent: Friday, September 30, 2005 1:20 AMSubject: I-D ACTION:draft-jee-16ng-problem-statement-01.txt

>A New Internet-Draft is available from the on-line Internet-Drafts directories.>>> Title : 16ng Problem Statement> Author(s) : J. Jee, et al.> Filename : draft-jee-16ng-problem-statement-01.txt> Pages : 7> Date : 2005-9-29>> This document describes the IPv6 over IEEE 802.16(e) networks (16ng)>   problem statement.>> A URL for this Internet-Draft is:> http://www.ietf.org/internet-drafts/draft-jee-16ng-problem-statement-01.txt>> To remove yourself from the I-D Announcement list, send a message to> [email-masked] 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-jee-16ng-problem-statement-01.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:> [email-masked].> In the body type:> "FILE /internet-drafts/draft-jee-16ng-problem-statement-01.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.>
>From [email-masked] Thu Oct  6 10:28:45 2005
Date: Thu, 06 Oct 2005 10:15:25 +0900
From: Soohong Daniel Park <[email-masked]>
Subject: Re: [16ng] Comments 16NG PS Draft
To: Syam Madanapalli <[email-masked]>, [email-masked]

Hi Syam

> 1. As many people in IETF unaware of 802.16, it maybe a good idea  to give a quick over view of 802.16.
> Also the following document could be a good referencefor quick overview on 802.16IEEE Standard 802.16: A Technical Overview of theWirelessMAN™ Air Interface for Broadband Wireless Accesshttp://grouper.ieee.org/groups/802/16/docs/02/C80216-02_05.pdf

Good reference to sense what 802.16 is...thanks.

> 2. If you include a typical Network Architecture for802.16, then it may be easier to grasp problems inrunning the IETF protocols on 802.16 Networks.
> e.g. Router Discovery, Next-hop resolution andRedirect may be trivial in scenario 1 whereas inScenario 3 these functions may need to be performed.
>       SS0 ----|                 |     +-------+      SS1 ----|-----| BS/AR |-----                 |     +-------+      SSn ----|
>                Scenario 1
>       SS0 ----|                 |     +-------+         +-------+      SS1 ----|-----|  BS   |-------- |  AR   |                 |     +-------+         +-------+      SSn ----|
>                Scenario 2
> 
>                                      |    +-------+                                     |--- |  AR1  |                                     |    +-------+      SS0 ----|                   |                 |     +-------+    |    +-------+      SS1 ----|-----|  BS   |----|--- |  AR2  |                 |     +-------+    |    +-------+      SSn ----|                   |                                     |    +-------+                                     |--- |  AR3  |                                     |    +-------+
>                Scenario 3
> Also we need to understand how the BS and ARs are connected.

It is a bit hard to understand...pls reformating and resending

> 3. A section on existing solutions for example RFC 2491(IPv6 over Non-Broadcast Multiple Access (NBMA) networks)and why such solutions do sufficient for 802.16 networks.One reason I see may be is that, generally NBMAtechnologies (ATM/Frame Relay) provides end to endnetwork, whereas 802.16 just specifies last mile (I amconsidering the mesh support is also part of last mile).I may be wrong somebody can correct me here.

I am not sure what you mean by last mile, but yes mesh architecture should be considered.

> 4. It may also be a good idea to provide the goalsfor the solution space.

Sure, 

> 5. I think we should cover the IPv4 as well, I thinkthe WiMAX Forum NWG is currently focusing on IPv4as a mandatory protocol to support.

Initial focus will be on IPv6 at this stage, but IPv4 would be interesting to at least document on an informational basis for IETF consumption how IPv4 is supported to work although IPv4 support is pretty much a done deal already by WiMAX Forum. Rechartering will be considered to take IPv4 support later if necessary...

Regards,

Daniel (Soohong Daniel Park)
Mobile Platform Laboratory, SAMSUNG Electronics.