[standards-jig] JEP 0033, Packet Headers, Issues

Adam Theo theo at theoretic.com
Fri Jul 19 07:18:43 UTC 2002

Hi, all. Me again.

I have read JEP 0033, Packet Headers to figure out how it could be used 
by a generic pubsub spec as part of my Core Tool Protocol idea 

First, I wonderif needing to expressly send the multi-address packet to 
a "multicast component" is really necessary? If there are more than one 
intended recipient (through to, cc, or bcc fields), the packet must be 
addressed to a "multicast.your.domain" component, which will handle the 
forking of the message to all recipients. A question, then: will this 
multicast server have to be expressly specified by the sender, or can 
they address the packet to one of the "to" fields and have their server 
catch it and fork it automatically? Otherwise, this seems to add too 
much complexity on the hands of the sender. Not even normal Jabber users 
would know to do this, since it is not like email at all. I think an 
alternative needs to be found, such as the sender's server automatically 
checking for forking, instead of a specific multicast component.

Next, why not have all <address>, <field>, and <resent> elements as 
direct children of the <header> element. It's not like the <addresses>, 
<info>, and <trace> elements that are currently the direct children have 
any meta information of their own, so why not simplify things and remove 
an entire layer of nodes from the packets? No data would be lost since 
none of the elements needs any type of specific ordering to work. They 
could be easily "jumbled" together for the sake of not creating another 
layer that has to be traveled down.

That's all for now.

     /\  Adam Theo, Age 23, Tallahassee FL USA
    //\\   Email & Jabber: theo at theoretic.com
   //  \\  (Boycotting AOL, therefore no AIM or ICQ)
//  ||  \\  Theoretic Solutions: http://www.theoretic.com
     ||         "Building Ideas by Bringing them Together"
     ||      Jabber Protocol: http://www.jabber.org
     ||         "The Next Generation Communications Protocol"
     ||  "A Free-Market Socialist Patriotic American Buddhist"

More information about the Standards mailing list