struct {
uint8 CAtype = PRIVATE_EXTENSION;
uint8 CAlength;
opaque ns<>;
opaque localName<>;
opaque value<>
} ExtCAType
So the following XML values:
<A8 xmlns="ns1">value1</A8>
<A9 xmlns="ns2">value2</A9>
... would serialize to the following CAtypes
XX 0E 03 6E7331 02 4138 06 76616C756531
XX 0E 03 6E7332 02 4139 06 76616C756532
(where XX is the CAtype value)
The only problem you really run into here is length, which is what the namespace prefix bits in local-civic are intended to address.
I think it's also worth noting that this extension scheme works best if the extension schema has the same basic structure as the base civic address schema, i.e., if it's just a flat list of types. If you try to add complex types, this scheme doesn't really work. (I'm thinking of someone getting the idea to do something like xAL [1])
--Richard
[1] <http://www.oasis-open.org/committees/ciq/ciq.html#6>
On Dec 1, 2010, at 8:28 AM, Marc Linsner wrote:
> Brian,
>
>
>>
>> For the new namespace, LoST works already. Create one new DHCP option
>> with the namespace as the first parameter and the label (tag) as the
>> second.
>>
>
>
> What if someone wants to build a location with more than 2
> namespaces....maybe 3, 4, 5, 6.....?? Define DHCP to carry multiple
> namespaces concatenated into one CAtype?
>
> -Marc-
>
>
> _______________________________________________
> Geopriv mailing list
> Geopriv@ietf.org
> https://www.ietf.org/mailman/listinfo/geopriv
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
