Subject: [Simple] A omment to draft-olson-simple-publish-01

From: [email-masked]
Date: Tue, 29 Oct 2002 12:22:34 +0200

Hi,

Thanks for the much improved -01. One comment though:

Although the draft says that 489 (Bad Event) should be sent in case the composer doesn't understand the published event state, there is no mention of Allow-Events used in that case. Allow-Events is mandatory in 489 according to RFC 3265. If it is also mandatory for 489 to a PUBLISH, it would seem logical that it is also (optionally) used with OPTIONS (for one). Would then Allow-Events in a 2xx to OPTIONS indicate support for SUBSCRIBE/NOTIFY, or PUBLISH, or both?

Why not a new pair of headers, which share the event-type (for packages) namespace with Event/Allow-Events, something like what's described in

	http://www.ietf.org/internet-drafts/draft-niemi-simple-publish-framework-00.txt

AFAIK, we are not running out of space with header names ;)

Cheers,
Aki  

_______________________________________________
simple mailing list
[email-masked]
http://mailman.dynamicsoft.com/mailman/listinfo/simple