[Capwap] FW: review of draft-ietf-capwap-dhc-ac-option-01.txt

["Romascanu, Dan (Dan)" <[e-mail]>]

Have Francis' comments been answered? 

Dan


-----Original Message-----
From: [e-mail] [mailto:[e-mail]] 
Sent: Friday, July 11, 2008 11:27 AM
To: [e-mail]
Cc: [e-mail]; Romascanu, Dan (Dan)
Subject: review of draft-ietf-capwap-dhc-ac-option-01.txt

I have been selected as the General Area Review Team (Gen-ART) reviewer
for this draft (for background on Gen-ART, please see
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).

Please resolve these comments along with any other Last Call comments
you may receive.


Document: draft-ietf-capwap-dhc-ac-option-01.txt
Reviewer: Francis Dupont
Review Date: 2008-07-10
IETF LC End Date: 2008-07-14
IESG Telechat date: unknown

Summary: Ready with nits

Comments: I have two general questions and the usual editioral things
(here editorial means they can be handled by the RFC Editor):

 - the first general question is about references to DHCP:
  * the whole document, including the Abstract, assumes the reader
   already knows what is DHCP. I have no concern about this but perhaps
   I should? I propose to keep this point closed until someone else
raises it
   (so it could enter into the any other LC comments)

  * 1.2 (Terminology) is only about CAPWAP, IMHO even you don't abuse of
   DHCP specific terms it is a good place to add DHCP references (the
   three at the beginning of the Security Considerations for instance).

 - the second question is about the use (or abuse) of 2119 keywords at
   unusual places, namely in the Introduction (i.e., before the 2119
   reference) and in the IANA Considerations. But it is only a question
   of usage/style...

 - in TOC and section 6: Acknowledgements -> Acknowledgments 

Regards

[e-mail]
_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap