Capwap Mailing List: Re: Recap of current pending issues

[Pat Calhoun (pacalhou) (pcalhoun]

All,

We are now a little over a week past the IETF Last Call, and some
progress has been made, so I wanted to provide an update on the latest
issues. As you can see below, if there are no comments on any of the
issues below, I will publish the new text on 8/18, which will include
all of the issues identified through the IETF Last Call. This draft will
be ready to move to the IESG for publication.

ISSUES WAITING FOR PASI's REVIEW

Issue 159 (Question on CAPWAP control protocol). I have provided some
updated text to address Pasi's issues. I am waiting for his review.

Issue 166 (Various IANA Issues). Pasi had comments on my new IANA text,
and identified some real problems which I believe are now all addressed.
I am waiting to hear from him on the latest.

Issue 168 (DTLS and Retransmissions). I believe we are closed on this.
Scott has proposed new text, and I am waiting to hear from Pasi if he is
comfortable with the new text.

Issue 171 (Pasi nits on binding spec). We are now in the fourth round
trip, and I believe we are nearing the end. Waiting for Pasi to review
the latest.

ISSUES WAITING FOR WG FEEDBACK.

Issue 106 (WaitJoin may be unnecessary). Yes, this is an old one, but in
fixing 173 I realized that we never should have removed the WaitJoin
timer, but instead cleaned it up. This fix re-introduces the timer, but
it is enabled/disabled differently from the WaitDTLS timer. I am waiting
for WG feedback on this proposed change, and will close by 8/18 if no
comments are sent.

Issue 158 (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". I have
made the proposal to change to Expert Review and waiting for feedback.
Will close on 8/18 if no additional objections are received.

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. I have proposed that the
document will require the WTP to down-tag, as dropping the packet will
create unpleasant troubleshooting issues for customers. I will close on
8/18 if no additional objections are received.

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. I have provided a solution that is really the optimal one,
but it breaks interoperability with -10 and -11. I am waiting for WG
comments and will close on 8/18 if no additional objections are
received.

Issue 173 (Inconsistency in enabling DTLSWait timer). The text was
inconsistent in how it was making use of the WaitDTLS timer.
Specifically, there were two state transitions that referenced the
timer, when it would have been stopped already before reaching that
transition. I have already sent text and will close by 8/18 if no
additional comments are received.

Issue 175 (Retransmission clarification required). The text that
specifies how control messages are retransmitted needs some
clarification, specifically around the text that deals with congestion
control. I have proposed a change, and will close by 8/18 if no
additional comments are received.

PatC