Re -organize section 6.

[fluffy]

I am proposing we reorder section 6 to look roughly like:

 6.1.  Parameters
   6.1.1.  Version Specific Parameters

 6.2.  Setup
   6.2.1.  Versions
   6.2.2.  Setup Parameters
   6.2.3.  CLIENT_SETUP
   6.2.4.  SERVER_SETUP
   6.2.5.  GOAWAY

 6.3.  Subscribe
   6.3.1.  Filter Types
   6.3.2.  SUBSCRIBE Format
   6.3.3.  SUBSCRIBE Request
   6.3.4.  SUBSCRIBE_OK
   6.3.5.  SUBSCRIBE_ERROR
   6.3.6.  MAX_SUBSCRIBE_ID
   6.3.7.  SUBSCRIBE_DONE
   6.3.8.  SUBSCRIBE_UPDATE
   6.3.9.  UNSUBSCRIBE

 6.4. Annouce
   6.4.1.  ANNOUNCE Request 
   6.4.2.  ANNOUNCE_OK
   6.4.3.  ANNOUNCE_ERROR
   6.4.4.  ANNOUNCE_CANCEL
   6.4.5.  UNANNOUNCE

 6.5. Track Status 
   6.5.1   TRACK_STATUS_REQUEST
   6.5.2   TRACK_STATUS

 6.6. Namespaces
   6.6.1.  SUBSCRIBE_NAMESPACE
   6.6.2.  SUBSCRIBE_NAMESPACE_OK
   6.6.3.  SUBSCRIBE_NAMESPACE_ERROR
   6.6.4.  UNSUBSCRIBE_NAMESPACE

[fluffy]

For comparison, it currently looks like

6. Control Messages 6.1. Parameters 6.1.1. Version Specific Parameters 6.2. CLIENT_SETUP and SERVER_SETUP 6.2.1. Versions 6.2.2. Setup Parameters 6.3. GOAWAY 6.4. SUBSCRIBE 6.4.1. Filter Types 6.4.2. SUBSCRIBE Format 6.5. SUBSCRIBE_UPDATE 6.6. UNSUBSCRIBE 6.7. ANNOUNCE_OK 6.8. ANNOUNCE_ERROR 6.9. ANNOUNCE_CANCEL 6.10. TRACK_STATUS_REQUEST 6.11. SUBSCRIBE_NAMESPACE 6.12. UNSUBSCRIBE_NAMESPACE 6.13. SUBSCRIBE_OK 6.14. SUBSCRIBE_ERROR 6.15. SUBSCRIBE_DONE 6.16. MAX_SUBSCRIBE_ID 6.17. ANNOUNCE 6.18. UNANNOUNCE 6.19. TRACK_STATUS 6.20. SUBSCRIBE_NAMESPACE_OK 6.21. SUBSCRIBE_NAMESPACE_ERROR

[afrind]

Chair Comment:

Any major reflow should take place when no other changes are in the draft. My recommendation is to wait until after we publish a new draft version (say draft-08), freeze merges, land the reorg and publish another draft version (-09). This way you can do an author-tools diff between -09 and -10 and see only the actual changes.

[fluffy]

That makes sense but I think it would be nice to get this done before Dublin IETF

[afrind]

That makes sense but I think it would be nice to get this done before Dublin IETF

Looking through the diff since -06, there's one subtle functional change - booleans other than 0/1 are now MUST close rather than SHOULD close. There's a note about how relays order GOAWAY and UNSUBSCRIBE, but I think everything else looks purely editorial.

I'm confident we want to isolate functional changes from editorial reorgs in drafts. FETCH is our primary functional change for the next draft before Dublin. If we need to get this reorg in, I propose we cut two drafts before 10/21. Either

1. Land this reorg right now, and cut draft-07 immediately, cut draft-08 with functional changes
2. We land FETCH and the other changes we want, cut draft-07, then land the reorg and cut draft-08

Ultimately this is up to @ianswett