Capwap Mailing List: Re: Recap of current pending issues

[Pasi.Eronen (Pasi.Eronen]

Pat Calhoun wrote:
> All,
> 
> With the IETF Last Call ending in a few hours, I wanted to provide
> an updated list of the issues, and required actions. I have updated
> Tracker to reflect the current state of all issues. I would like to
> get review, and confirmation, that the changes I have proposed are
> satisfactory before I publish another rev of the spec. Assuming I
> get nothing from the list (which I hope does not happen), my plan
> would be to publish the specs next Monday. So in order to ensure we
> have a high quality spec, I would urge you to look at the proposed
> changes and make sure that we are good to do. The resulting three
> specs (DHCP, Base and Binding) would then be ready to move to the
> IESG for publication.
> 
>  
> 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.

This was probably nailed down in emails earlier today.

> 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.

The answer (you can't have multiple outstanding requests) really
needs to be in the spec. Also, the spec needs some more text about
how the receiver processes them -- e.g. does the receiver maintain
"last seen sequence number" counter, and silently drop (without
replying) requests older than this? 

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

I replied about this earlier today -- couple of bugs, and Standards
Action might not be the best policy for all registries.

> Issue 168 (DTLS and Retransmissions). Charles provided text 
> for section 2.4.1, but we need Pasi to provide clarification on 
> what he needed in section 2.4.3.

Also replied earlier today.

> 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

Also replied earlier today.

Best regards,
Pasi