Subject: RTSP: 2. Use of PEP for Require and Transport-Require

From: Rob Lanphier <[email-masked]>
Date: Thu, 17 Apr 1997 13:40:16 -0700

The Require field (see section 11.17 of the current
draft) provides a simple mechanism for capability
query.

A standard for providing this functionality (and
more) is PEP, an option negotiation method from the
HTTP working group.

The authors are mostly in agreement that PEP is/will
be a really good thing, and the only question is
whether it can immediately placed into the RTSP
specification, or whether there should be an
intermediate mechanism pending the completion of PEP.

The general feeling in Memphis was that people needed
more time to look at PEP, and make sure that some
such mechanism is needed. There would be more
deliberation on the mailing list on this topic before
any sort of decision one way or another is made.

Some folks thought of this as something that can be
added later, to which Henrik Frystyk Nielsen from the
W3C noted that there is a need for some option
negotiation core to the protocol, which was a lesson
learned from the original HTTP specification.

---
Rob Lanphier               Voice: (206)674-2322         Fax: (206)674-2699
Program Manager-Protocols                         Email: [email-masked]
Progressive Networ
s-Home of RealAudio            Web: http://www.real.com
For more information on firewalls:       http://www.real.com/firewall.html
For more information on RTSP:               http://www.real.com/prognet/rt