Hi, Robert,
Spencer - I can't tell if you thought I was saying to hold moving
info-harmful forward until
we had better answers or not - I wasn't.
My bad. It wasn't obvious to me from your otherwise-excellent note whether
you were thinking of two separate documents.
I just wanted to make sure we would do something soon (at least measured in
IETF years). Given that saying "don't go there" has taken four years since
Jonathan's last update, I was concerned that saying "don't look here, look
over there" would take more time than I was willing to spend continuing to
point to an expired draft.
I have pointed this out previously in private e-mail, but
http://www.ietf.org/internet-drafts/draft-melanchuk-mediactrl-framework-00.txt
is having to put forward its own analysis of "why not INFO" in Section 5
("SIP Usage"), because Tim doesn't have anything we can refer to except an
expired individual draft. I'd rather rely on a document done here than text
in the MEDIACTRL framework document, just because I think the larger SIP
community would look at text done here more closely than in a MEDIACTRL
draft.
IMO, of course.
I'm saying we aren't done just by moving it forward.
Ack.
It will help on its own, but we'll have to get to the guidance part
quickly for it to really help much.
Double Ack.
RjS
Thanks for clarifying (so that I'm now clear :-).
Spencer
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
