Last Call Review of draft-ietf-opsawg-capwap-alt-tunnel-08
review-ietf-opsawg-capwap-alt-tunnel-08-opsdir-lc-liu-2016-11-03-00
Request | Review of | draft-ietf-opsawg-capwap-alt-tunnel |
---|---|---|
Requested revision | No specific revision (document currently at 12) | |
Type | Last Call Review | |
Team | Ops Directorate (opsdir) | |
Deadline | 2016-10-25 | |
Requested | 2016-09-22 | |
Authors | Rong Zhang , Rajesh Pazhyannur , Sri Gundavelli , Zhen Cao , DENG Hui , Zongpeng Du | |
I-D last updated | 2016-11-03 | |
Completed reviews |
Genart Last Call review of -08
by Paul Kyzivat
(diff)
Genart Telechat review of -08 by Paul Kyzivat (diff) Secdir Last Call review of -08 by Catherine Meadows (diff) Opsdir Last Call review of -08 by Will (Shucheng) LIU (diff) Secdir Early review of -09 by Catherine Meadows (diff) Genart Last Call review of -10 by Paul Kyzivat (diff) Genart Telechat review of -11 by Paul Kyzivat (diff) |
|
Assignment | Reviewer | Will (Shucheng) LIU |
State | Completed | |
Request | Last Call review on draft-ietf-opsawg-capwap-alt-tunnel by Ops Directorate Assigned | |
Reviewed revision | 08 (document currently at 12) | |
Result | Ready | |
Completed | 2016-11-03 |
review-ietf-opsawg-capwap-alt-tunnel-08-opsdir-lc-liu-2016-11-03-00
Hi all, (Sorry for being late due to travelling. ) I have reviewed draft-ietf-opsawg-capwap-alt-tunnel-08 as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written with the intent of improving the operational aspects of the IETF drafts. Comments that are not addressed in last call may be included in AD reviews during the IESG review. Document editors and WG chairs should treat these comments just like any other last call comments. “Control and Provisioning of Wireless Access Points (CAPWAP) defines a specification to encapsulate a station's data frames between the Wireless Transmission Point (WTP) and Access Controller (AC). Specifically, the station's IEEE 802.11 data frames can be either locally bridged or tunneled to the AC. When tunneled, a CAPWAP data channel is used for tunneling. In many deployments encapsulating data frames to an entity other than the AC (for example to an Access Router (AR)) is desirable. Furthermore, it may also be desirable to use different tunnel encapsulation modes between the WTP and the Access Router. This document defines extension to CAPWAP protocol for supporting this capability and refers to it as alternate tunnel encapsulation. The alternate tunnel encapsulation allows 1) the WTP to tunnel non-management data frames to an endpoint different from the AC and 2) the WTP to tunnel using one of many known encapsulation types such as IP-IP, IP-GRE, CAPWAP. The WTP may advertise support for alternate tunnel encapsulation during the discovery or join process and AC may select one of the supported alternate tunnel encapsulation types while configuring the WTP.” I have also discussed with some of co-authors about some details of this draft. Some affiliations may need to be updated. J My overall view of the document is 'Ready' for publication. * Section 3.5, page 15: PMIPv6 is updated by RFC6543 and RFC7864. Authors may need to double check whether corresponding updates needed. Regards, Will (Shucheng LIU)