>> (Assuming
>> you meant an opaque vector like the built-in XDR opaque vector, with the
>> included encoded length).
>
> If we're defining a new builtin type, along the lines of UUID, it does not
> need to be something that can be composed from the existing types. The
> encoding for this on the wire ought to consist of an integer encoding the
> family, an integer encoding the size of the address data, and some number of
> octets encoding the address. For IPv4 and IPv6, the address data consists
> of a single address, transmitted in exactly the same way as in IP headers.
struct {
int addrtype;
int addrlen;
int addr<>
} rx_addr;
#define RX_ADDRTYPE_IPV4 1
#define RX_ADDRTYPE_IPV6 2
--
Derrick
_______________________________________________
AFS3-standardization mailing list
[email protected]
http://lists.openafs.org/mailman/listinfo/afs3-standardization
