I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<

http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

Document: draft-ietf-tsvwg-sctp-strrst-12
Reviewer: Vijay K. Gurbani
Review Date: Nov-30-2011
IETF LC End Date: Unknown
IESG Telechat date: Dec-01-2011

Summary: This draft is ready as an Proposed Standard.

Major issues: 0
Minor issues: 1
Nits/editorial comments: 2

Minor issue:
- S5, second paragraph --- "The procedures outlined in this section are
 designed so that the incoming side will always reset their stream
 sequence number first before the outgoing side which means the re-
 configuration request must always originate from the outgoing side."

 Here, I am not sure what "incoming" and "outgoing" side mean.  Both
 SCTP server and client will have an "incoming" side and "outgoing"
 side. So, which peer's outgoing side are we talking about?


Nits:
- Abstract (and same text is repeated in S1: Introduction):
 s/to the upper layer that this has been/
 to the application layer that the reset has been/

- Abstract:
 s/The applications that want this/Applications requiring this/


Thanks,

- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg at {bell-labs.com,acm.org} / vijay.gurbani at alcatel-lucent.com
Web:   

http://ect.bell-labs.com/who/vkg/