Re: [STDS-802-16] Fwd: Updated Draft Charter: IP over IEEE 802.16 Networks(16ng)
Hi,
What wopuld be the content (PAR) proposal for this group. There is IP over Ethernet in CS and GPCS. Is the goal to to study IP closer than just from CVS/GPCS point of view?
Regards,
Eero Wallenius, Ph.D.
Senior Solution Manager
3G Business Team
Services Software Business
Nokia Corporation
Hatanpäänvaltatie 30
FI-33100, Tampere
P.O. Box 785, FI-33101 Tampere
FINLAND
Mobile:+358405004055
E-Mail: eero.wallenius@nokia.com
>-----Original Message-----
>From: ext Roger B. Marks [mailto:r.b.marks@ieee.org]
>Sent: 23 May, 2006 01:02
>To: STDS-802-16@listserv.ieee.org
>Subject: [STDS-802-16] Fwd: Updated Draft Charter: IP over
>IEEE 802.16 Networks(16ng)
>
>Please take note of this important announcement that IETF is
>considering creations of a new "IP over IEEE 802.16 Networks"
>Working Group (16ng).
>
>Note that comments are due by 24 May.
>
>I plan to submit comments. Please let me know if you have any.
>Free free to cc the reflector.
>
>Also, I am seeking volunteers to serve as the 802.16 WG's
>liaison official to IETF.
>
>Roger
>
>
>
>>-----Original Message-----
>>From: The IESG [mailto:iesg-secretary@ietf.org]
>>Sent: Friday, May 19, 2006 1:34 PM
>>To: new-work@ietf.org
>>Subject: [New-work] Updated Draft Charter: IP over IEEE 802.16
>>Networks(16ng)
>>
>>The Secretariat inadvertently failed to send the "WG Review: IP over
>>IEEE
>>802.16 Networks (16ng)" message to the new-work mailing list
>on May 2nd.
>>
>>Please accept our apology. However, the draft charter was not
>approved
>>by the IESG at the May 11th IESG teleconference, and an
>updated version
>>will be reviewed by the IESG on May 25th. The following revised draft
>>charter was submitted, and is provided for informational
>purposes only.
>>Please send your comments to the IESG mailing list (iesg@ietf.org) by
>>May 24th.
>>
>>+++
>>
>>
>>IP over IEEE 802.16 Networks (16ng)
>>===================================
>>
>>Current Status: Proposed Working Group
>>
>>Chair(s):
>>TBD
>>
>>Internet Area Director(s):
>>Jari Arkko <jari.arkko@piuha.net>
>>Mark Townsley <townsley@cisco.com>
>>
>>Technical Advisor(s):
>>TBD
>>
>>Mailing Lists:
>>General Discussion: 16ng@eeca16.sogang.ac.kr To Subscribe:
>>http://eeca16.sogang.ac.kr/mailman/listinfo/16ng
>>Archive: http://eeca16.sogang.ac.kr/pipermail/16ng
>>
>>
>>Description of Working Group:
>>
>>Broadband Wireless Access Networks address the inadequacies of low
>>bandwidth wireless communication for user requirements such as high
>>quality data/voice service, wide coverage, etc. The IEEE
>802.16 Working
>>Group on Broadband Wireless Access Standards develops standards and
>>recommended practices to support the development and deployment of
>>Broadband Wireless Metropolitan Area Networks.
>>
>>A particularity of IEEE 802.16
>>is that it does not include a rigid upper edge MAC service interface.
>>Instead, it provides multiple "convergence sublayers (CS)" with the
>>assumption that the choice and configuration of the upper
>edge will be
>>done in accordance with the needs of a specific deployment
>environment
>>(which might be DSL replacement, mobile access, 802.11 or
>CDMA backhaul
>>etc.).
>>
>>Specifically, immediately subsequent to network entry, an 802.16
>>subscriber station has no capability whatsoever for data (as
>opposed to
>>management) connectivity. Especially, in IP CS case, the criteria by
>>which the Base Station (or other headend elements) sets up the
>>802.16 MAC connections for data transport are not part of the 802.16
>>standard, and depend on the type of data services being
>offered (e.g.,
>>the set up of link layer connections will be different for IPv4 and
>>IPv6 services).
>>
>>Additionally - as IEEE 802.16 is a point-to-multipoint network - an
>>802.16 subscriber station is not capable of multicasting (e.g., for
>>neighbor discovery, ARP, IP multicasting services, etc.) or direct
>>communication to the other nodes attached to the same Base Station
>>within the same subnet (prefix).
>>
>>Unlike 3G or xDSL technologies, IEEE 802.16 is not part of an
>>end-to-end system definition. Currently, the WiMAX Forum, and, in
>>particular, its NWG (Network Working Group) is defining the
>IEEE 802.16
>>network architecture.
>>Also, other standards bodies are carrying out similar efforts (e.g.,
>>WiBro-Wireless Broadband in Korea).
>>
>>The principal objective of the 16ng working group is to specify the
>>operation of IPv4 and IPv6 over IEEE 802.16, taking into account the
>>IPv4, IPv6 and Ethernet Convergence Sublayers. The working group may
>>issue recommendations to IEEE 802.16 and WiMax aiming at improving
>>support for IP.
>>
>>The scope of this working group is as follows (WG Deliverables);
>>
>>- Produce "16ng Problem Statement, Goal and Requirement" to identify
>>the specific gaps in the 802.16 MAC for IPv4/IPv6 support, describe
>>possible network models (ie. point-to-point, broadcast etc.), and
>>provide 16ng related terminology to be used for the base guideline
>>while defining solution frameworks. [Informational RFC]
>>
>>- Produce "IPv6 over IEEE 802.16 Networks in conjunction with IPv6 CS"
>>to define IPv6 operation including the transmission of IPv6 over IEEE
>>802.16 link, Neighbor Discovery Protocol, Stateful (DHCPv6) and
>>Stateless Address Configuration, Broadcast, Multicast, etc.
>>[Proposed Standard RFC]
>>
>>- Produce "IPv6 over IEEE 802.16 Networks in conjunction with
>Ethernet
>>CS" to define IPv6 operation including the transmission of IPv6 over
>>IEEE 802.16 link, Neighbor Discovery Protocol, Stateful (DHCPv6) and
>>Stateless Address Configuration, Broadcast, Multicast, etc.
>>[Proposed Standard RFC]
>>
>>- Produce "IPv4 over IEEE 802.16 Networks in conjunction with IPv4 CS"
>>to define IPv4 operation including the transmission of IPv4 over IEEE
>>802.16 links, ARP operation, Stateful Address Configuration (DHCPv4),
>>Broadcast, Multicast, etc [Proposed Standard RFC]
>>
>>- Produce "IPv4 over IEEE 802.16 Networks in conjunction with
>Ethernet
>>CS" to define IPv4 operation including the transmission of IPv4 over
>>IEEE 802.16 links, ARP operation, Stateful Address Configuration
>>(DHCPv4), Broadcast, Multicast, etc [Proposed Standard RFC]
>>
>>- Produce "IP deployment over IEEE 802.16 Networks" to illustrate the
>>IP deployment scenarios including IP CS and Ethernet CS
>considerations
>>over IEEE
>>802.16 networks based on the WiMAX and WiBro.
>>[Informational RFC]
>>
>>16ng will not initially consider other work items than the
>ones listed
>>above; however, other works related to improved IP over 16ng
>may occur
>>in other relevant WGs, and 16ng will participate and help coordinate
>>with such efforts.
>>
>>This working group will take dual stack operation into account in its
>>specifications, and reuse existing specifications whenever reasonable
>>and possible.
>>
>>Goals and Milestones:
>>
>>Jul 06 Submit Internet-Draft on 16ng Problem Statement, Goal and
>> Requirement to the IESG for considerations of publication
>> as Informational RFC
>>
>>Sep 06 Submit Internet-Draft on IPv6 over IPv6 CS transmission over
>> IEEE 802.16 networks to the IESG for consideration of
>>publication
>>
>> as Proposed Standard RFC
>>
>>Oct 06 Submit Internet-Draft on IPv4 over IPv4 CS transmission over
>>IEEE
>>
>> 802.16 to the IESG for consideration of publication
>as Proposed
>> Standard RFC
>>
>>Nov 06 Submit Internet-Draft on IPv4 over Ethernet CS
>transmission over
>> IEEE 802.16 networks to the IESG for consideration of
>> publications as Proposed Standard RFC
>>
>>Dec 06 Submit Internet-Draft on IPv6 over Ethernet CS
>transmission over
>> IEEE 802.16 networks to the IESG for consideration of
>publication
>> as Proposed Standard RFC
>>
>>Feb 07 Submit Internet-Draft on IP deployment over IEEE 802.16
>> networks to the IESG for consideration of publication as
>> Informational RFC
>>
>>
>>
>>
>>_______________________________________________
>>New-work mailing list
>>New-work@ietf.org
>>https://www1.ietf.org/mailman/listinfo/new-work
>>
>>--
>