Capwap Mailing List: Recap of current pending issues

[Pat Calhoun (pacalhou) (pcalhoun]

All,

With the IETF Last Call ending next Tuesday, I thought it would be
useful to do a recap of where we are at with regards to the issues that
have been raised already. For those I mark as closed, I will wait until
the end of the IETF Last Call before I take the actual action in
tracker.

ISSUES WAITING FOR FEEDBACK.

Issue 150 (Allocation of WBIDs). There is no clear agreement on this
issue. The current spec requires a Standards Action to allocate a WBID,
but it doesn't look like EPCGlobal plans on submitting their protocol to
the IETF. So we either agree to keep the document as it (although we did
agree to remove 802.16), or change the IANA action from "Standards
Action" to something else, such as perhaps "Designated Expert". We need
clear resolution on this.

Issue 151 (MTU discovery doesn't look right). Pasi stated that the MTU
Discovery text was not sufficient, since we pointed to RFCs that
described MTU Discovery behavior, but no protocol specifics. So I had to
re-instate some old CAPWAP text (and new) to add protocol discovery. I
am waiting for feedback for this issue.

Issue 154 (Should we use IPv4 Multicast Address?). A request for a known
multicast address to be registered. I proposed we reject this issue, and
am waiting to make sure that we have consensus on this proposal.

Issue 155 (WTP/AC ACL Synchronization Issue). So this is another
interesting issue, and talking to the LWAPP developers it was introduced
to support a mode of operation that the CAPWAP standard does not
currently support. In the thread, I proposed we remove these message
elements, otherwise we will need to do much more specmanship in order to
support this new deployment requirement.

Issue 161 (NAT Inconsistencies). This is another issue that uncovered
some real problems in the CAPWAP protocol. Fixing it required some
changes that will create backward compatibility issues - but there was
no choice. The old text had two different possible ways of doing the
same thing, with little/no guidance that would clearly create issues.

Issue 165 (Image Download inconsistencies). This issue uncovered some
problems in the CAPWAP protocol's mechanism of downloading firmware to a
WTP. It required some changes to the protocol and I am waiting for
feedback from folks before I consider this closed. Note this new text
does possibly break backward compatibility, depending on how folks had
interpreted the original text.

Issue 169 (What to do with QoS tags exceeding maximum). Another one
where we have a potential interoperability issue, and we need to agree
on what behavior the WTP will take if it receives a packet whose QoS
marking violates the configured policy. Alternatives have been proposed
- waiting for feedback.

Issue 172 (How is the WTP Descriptor's Encryption Capabilities
defined?). This is a particularly thorny issue that can cause us to
break backward interoperability, or worse, severely limit the scope of
the protocol. We need a good resolution, and I have proposed a few
already. Waiting for feedback.


ISSUES WAITING FOR PASI's REVIEW

Issue 156 (Need more details on use of DNS for discovery). This was a
rather small change, but I got it wrong the first time. I am waiting for
confirmation that this time around we are good to go.

Issue 159 (Question on CAPWAP control protocol). This was a question,
which I have responded to. There was no need for change, unless Pasi
raises a specific issue. At this point, I consider this issue closed.

Issue 166 (Various IANA Issues). This issue has been addressed, but I am
waiting for Pasi's feedback.

Issue 171 (Pasi nits on binding spec). I believe this is done - I am
just waiting to see if Pasi has issues with any of the proposed
resolutions


CLOSED ISSUES

Issue 152 (Need crypto protocol agility). This issue has been addressed.
I will close it.

Issue 170 (Inconsistent WLAN ID length). This issue has been addressed.
I will close it.

Issue 160 (Use of Replay Protection). This issue has been addressed. I
will close it.

Issue 153( Linking of control and data channels). This issue has been
addressed. I will close it.

Issue 167 (Need to mention PSK Identity Hint). This issue has been
addressed. I will close it.

Issue 163 (R-MAC Info Field needs to be clarified and cleaned up). This
issue has been addressed. I will close it.

Issue 164 (Some bitfields need to be clarified). This issue has been
addressed. I will close it.

Issue 168 (DTLS and Retransmissions). I am waiting for either Scott or
Charles to opine on this issue.

Issue 157 (Issue with handling of cookies). This issue has been
addressed. I will close it.

Issue 149 (Incompatibility with message element numbering between drafts
10 and 11). This issue has been addressed. I will close it.

Issue 150 (binding doc. 802.11 wlan config req/resp msg type
valueissue). This issue has been addressed. I will close it.

Issue 144 (Invalid reference to message element field).  This issue has
been addressed. I will close it.

Issue 162 (Nits from Pasi's Review). Various NITs. This issue has been
addressed. I will close it.

PatC