[tcpm] Should draft-ietf-tcpm-sack-recovery-entry update RFC 3717 (SACK-TCP)

[Alexander Zimmermann <alexander.zimmermann at nets.rwth-aachen.de>]

Hi folks,

based on the fact that the draft "draft-ietf-tcpm-sack-recovery-entry"  
is adopted as WG item now and intended to be a "standards track"  
document, I would like to start a poll/discussion whether the draft  
should update RFC 3517 or not? Moreover, should we produce a separate  
document or an update of RFC 3517?

a) separate document, do not update RFC 3517
b) separate document, update RFC 3517
c) RFC3517bis, obsolete RFC 3517

//
// Dipl.-Inform. Alexander Zimmermann
// Department of Computer Science, Informatik 4
// RWTH Aachen University
// Ahornstr. 55, 52056 Aachen, Germany
// phone: (49-241) 80-21422, fax: (49-241) 80-22220
// email: zimmermann at cs.rwth-aachen.de
// web: http://www.umic-mesh.net
//