[EMAIL PROTECTED] wrote:
After thinking about this some more, I'll retract my objection. In
principle, I think the problem still stands, but this case is simple
enough that no trouble can result.
Do note: You introduce the table in section 5, which is marked
non-normative. But you refer to the table 16 times in section 8,
which is marked normative, and furthermore you don't re-introduce the
table or its behavior. Which, unless I've overlooked something again,
means that the normative section 8 contains a prerequisite reference
to the non-normative section 5. I think you're going to have to
adjust that.
OK; that is reasonable.
I doubt harm can come from it, but I don't see the Posix programming
model as being one of the background domains for understanding SIP.
Suppose, for example, that one's SIP stack was written in Java...
Why, convert it to C/C++, of course ;-) But seriously, I will
add some text equating the alias descriptor to connection objects
found in other languages.
Thanks, Dale.
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: [EMAIL PROTECTED],bell-labs.com,acm.org}
WWW: http://www.alcatel-lucent.com/bell-labs
_______________________________________________
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
