Re: CTP and CARD Drafts

All,

Actually, there's been a little bit of misunderstanding of my message about the
CTP draft, which is easy to have happen, because we were all very busy during
the IETF week.  What I meant was that I had to talk with some ROHC people about CTP,
not that ROHC _WG_ review of the document would be required.  

Why is this?  It's due to some commitment that was made in the Vienna Seamoby 
meeting to deliver Seamoby with a use case, which I understood would probably be
header compression context.  The minutes show an action item to work with Carsten
Bormann to make this concrete.  We discussed the need for the use case that
would describe a context very well defined in IETF, with ROHC header compression
meeting that criterion.  If contexts for context transfer are just open-ended,
and there isn't an clear use case, it's hard to build support for this
protocol in the broader IETF (not only the IESG - we had a lot* of questions
about this charter item when the WG was formed).  

So, I've done a little talking and looking at the document.  The example of a
service that was supposed to be covered in Appendix C is missing.  There is no 
companion document describing a use case.  What's up?

Allison

http://www.ietf.org/proceedings/03jul/index.html