Document: draft-herzog-setkey-03.txt
Reviewer: Francis Dupont
Review Date: 20110203
IETF LC End Date: 20110222
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: I have an ASN.1 question related to implicit tagging:
this can lead to encoding ambiguity with nested CHOICEs for instance,
it is something which could be addressed in specs, is the extension
mechanism an issue (i.e., the spec can be correct now but become
incorrect whene extended) and BTW is there a known tool to check
the syntax against this particular issue?

Nits/editorial comments:
 - ToC page 2 and 5 page 9: Acknowledgements -> Acknowledgments

 - 1.1 page 3 and 2 page 8: Becuase/becuase -> Because/because

 - 1.1 page 3: partipants -> participants

 - 1.2 page 5: futher -> further

 - 1.3 page 5: Heirarchy -> Hierarchy

 - 2 page 6 and A page 11 (twice): XX -> TBD? or TBD1/TBD2?
  (note this will be solved anyway by the assignment of a numerical
   value before publishing)

 - 2 page 7 (twice): SetKeyParticipentSet -> SetKeyParticipantSet

 - 2 page 7 (in intersection): if it is all -> if it is in all
                                                        ^^

 - 2 page 8: miniumum -> minimum

 - 2 page 8 (twice): freeform -> free form

 - 2 page 8: SubjectPublicKeyInfor -> SubjectPublicKeyInfo

 - 5 page 9: Housely -> Housley?

 - 6.1 page 10 (RFC6031): please use the 'RFC' abbrev