just stumbled over the IP section based flags enhancements =:)
;S | INA[:IP-addres] ..... Flag sets the default Internet address used for ;S | any non-email based IP-flag that does not specify ;S | its own. ;S | ;S | INA-V6[:IP-addres] .. Flag sets the default Internet IPv6-address used ;S | for any non-email based IP-flag that does not ;S | specify its own. (RFC-6214) ;S | ;S | AVI4[:AABBCCDDEEFF] . Indicates Avian-IPv4 (RFC-1149 and RFC-2549) ;S | ;S | AVI6[:AABBCCDDEEFF] . Indicates Avian-IPv6 (RFC-6214) ;S | ;S | The [AABBCCDDEEFF] section, when present, indicates the coordinates ;S | for the homing-pidgeon to fly to in base-36 annotation: ;S | ;S | Longitude: AA = Degrees ;S | BB = Minutes ;S | CC = Seconds ;S | ;S | Lattitude: AA = Degrees ;S | BB = Minutes ;S | CC = Seconds
Is there a DynAVI server available, to whom I can send my real-time updates ?-) Whenever I'm going to my short weekend tour, flying mails never will touch my machines runway ... but instead will touch the ground where the machine was one day before located touching the ground and going through like neutrinos =:)
ok, for the frame format I propose to not only use legs, but to also use arms, the body and other upper and lower extremities. This will probably double or triple the frame size =:D
RFC 2549 probably requires an update too ... at least since June 2003 :-P
