Download presentation
Presentation is loading. Please wait.
Published byClarissa Henry Modified over 8 years ago
1
December 4th, 200716ng WG, IETF701 Junghoon Jee, ETRI IP over 802.16 Problem Statement and Goals draft-ietf-16ng-ps-goals-03
2
December 4th, 200716ng WG, IETF702 Table of Contents Area Director Review Technical Amendments Editorial Amendments Current Status
3
December 4th, 200716ng WG, IETF703 Area Director Review Area Director, Jari reviewed draft-ietf-16ng-ps- goals-02 Comments –Technical comments: 4 –Editorial comments: 6
4
December 4th, 200716ng WG, IETF704 Technical Amendments Section 4.1 Root Problem –Ethernet like link model part –Comment What’s the real problem in realizing the Ethernet like link model in case of the Ethernet CS? –Amendment Addition of the following sentence. –“There needs mechanisms like IEEE 802.1D to realize multicast and broadcast for Ethernet CS.”
5
December 4th, 200716ng WG, IETF705 Technical Amendments (2) Section 4.2 IP CS: Problems –Address Resolution part “Blocking ARP or the address resolution of NDP needs to be implemented by SS itself in an implementation manner.” –Comment No mention of such blocking in the ipv6-over-ipv6cs. Would blocking NDP packets break IPv6 NUD? –Amendment Separate problem description for each IPv4 and IPv6 Addition of the following sentences for IPv6 case. –“For IPv6, address resolution is the function of IP layer and the IP reachability state is maintained through neighbor discovery packets. Therefore, blocking neighbor discovery packets would break the neighbor unreachability detection model.”
6
December 4th, 200716ng WG, IETF706 Technical Amendments (3) Section 4.2 IP CS: Problems (cont.) –Nits are caused by the previous assumption of the shared prefix link model for IP CS. Router Discovery –Texts about source address inclusion in the RS Neighbor Unreachability Detection –Texts regarding multiple ARs existence –Amendment All related parts are deleted.
7
December 4th, 200716ng WG, IETF707 Editorial Amendments Overall –Reference correction to RFC4903 –Expand “SDU” to “Service Data Unit” –Deletion of the “Section 2. Requirements” Clarification and correction –Section 1. Introduction …(CS) is at the uppermost part of the MAC… –Section 4.2 IP CS: Problems …Implementation manner specific fashion… –Section 4.3 Ethernet CS: Problems However, if not filtered (e.g., [RFC4541]), this these multicast and broadcast packets results result in the problem of waking up the sleep/ idle [IEEE802.16e] SSs.
8
December 4th, 200716ng WG, IETF708 Current Status draft-ietf-16ng-ps-goals-03 was submitted reflecting the AD’s comments and resolution. AD passed this version to the IESG. Please send comments by 2007-12-10.
9
December 4th, 200716ng WG, IETF709 Authors and Acknowledgment Authors –Junghoon Jee, ETRI (Editor) –Syam Madanapalli, LogicaCMG –Jeff Mandin, Runcom –Gabriel Montenegro, Microsoft –Soohong Park, Samsung Electronics –Max Riegel, NSN Acknowledgment –David Johnston for amending the section 4, "Overview of the IEEE 802.16-2006 MAC layer" and carefully reviewing the entire document –Phil Roberts for suggesting the reorganization of the document depending on the baseline IP subnet models. –Jari Arkko for AD review by carefully reviewing the entire document. –HeeYoung Jung, Myung-Ki Shin, Eun-Kyoung Paik, Jaesun Cha and KWISF (Korea Wireless Internet Standardization Forum) for their contribution.
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.