Hilarie
That's how SDP's offer/answer work and its one of its disadvantages. The
authors themselves indicate that in RFC3264.
"
Since SDP has no way to indicate that the message is for
the purpose of capability indication, this is determined from the
context of the higher layer protocol. The ability of baseline SDP to
indicate capabilities is very limited. It cannot express allowed
parameter ranges or values, and can not be done in parallel with an
offer/answer itself. Extensions might address such limitations in
the future."
That's why I extended a little bit by adapting some ideas from PPP.
Regards,
Reinaldo
-----Original Message-----
From: The Purple Streak, Hilarie Orman
[mailto:ho(_at_)alum(_dot_)mit(_dot_)edu]
Sent: Thursday, April 17, 2003 4:53 PM
To: Penno, Reinaldo [BL60:0430:EXCH]
Cc: ietf-openproxy(_at_)imc(_dot_)org;
rousskov(_at_)measurement-factory(_dot_)com
Subject: Re: Capability Negotiation for OCP
"Channel" and "device" are not terms of reference that I've
seen for OPES before. What are they, how do they relate to
the architecture?
Why aren't two messages ("menu offer" and "menu selection")
sufficient? Many IETF protocols use this method and live happy lives.
Hilarie