hack of VOEvent to include W3C signature

Steve Allen sla at ucolick.org
Tue Jan 10 17:34:22 PST 2006


On Tue 2006-01-10T14:52:43 -0800, Matthew Graham hath writ:
> Another alternate use case is that the data of the packet remains
> inviolate but subsequent signature elements are added by VOEvent packet
> relays when they pass the packet on: this would be the case when you are
> concerned about the whole transport history of a packet.

Doing a quick paraphrase of the relevant RFC, the typical MTA relay
information in SMTP is to include a bunch of lines of this form:

	Received: from some.smtp.relay.host (related DNS information)
		(various parenthetical information)
		by another.smtp.relay.host with some_protocol
		for some.user at some.machine; date_timestamp

If this sort of relay information is desirable in a VOEvent packet,
should there be a formal specification for that in the VOEvent schema?
Signature elements could be part of that.
Again, this is more complexity, albeit optional complexity.

--
Steve Allen                 <sla at ucolick.org>                WGS-84 (GPS)
UCO/Lick Observatory        Natural Sciences II, Room 165    Lat  +36.99858
University of California    Voice: +1 831 459 3046           Lng -122.06014
Santa Cruz, CA 95064        http://www.ucolick.org/~sla/     Hgt +250 m



More information about the voevent mailing list