Hi Eric, all,
I assume the main intent of the post is to determine whether to proceed
further on the INFO draft or not, and draw any significant early flames.
> If you like it, say so. If you hate it, say so.
I like it, and I hate it ;-)
But, to be slightly more specific, while hopefully vague enough for
misinterpretation...
I support the overall effort. It is certainly useful to write down and
clarify why INFO is bad in some regards. And it may be good in some other
regards of course. This would remove disinformation and add concrete
reasoning to any debates. Such debates have been fairly numerous, and for
the most part pointlessly vague.
I agree with most conclusions. BUT, looking especially at section 4,
there are other similar uses which are equally valid and equivalent to
SIP-T/QSig, notably transport of other end-end signalling such as DPNSS or
similar. I believe that the doc should allow for the class of similar
cases, ie say basically: "INFO is ok/good for its original intent, which
is to carry end-end signalling between ends that understand common
signalling other than SIP, and need it as part of their gateway (or other)
functions".
I also believe the document should be aimed at Informational, or possibly
BCP, since it gives context, explanation and advice. Don't see the value
in updating INFO Method RFC 2976, if that were to mean including the MUST
NOTs of sec 4 in a rev of that spec or anything functionally equivalent to
that. It could not be enforced in any way ("not the protocol police").
And besides the cat is already out of that bag anyway.
-- Peter
Eric Burger <[EMAIL PROTECTED]>
21.08.07 17:37
To: "'sip'" <[email protected]>
cc:
Subject: [Sip] INFO
Since list traffic is down, how about something to spice things up?
Any thoughts on
http://www.ietf.org/internet-drafts/draft-burger-sip-info-01.txt
???
If you like it, say so. If you hate it, say so.
Text welcome.
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this by
email and then delete it.
_______________________________________________
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
_______________________________________________
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
