Re: [P1619-3] I18n of SO_GUID
While a URL may be the place to find a key the SO_GUID URI of the key is
what is important. Host name only impacts us for devices requesting
keys (gen, get, store, etc...).
In the URI namespace we only want the
"sub-domain2.sub-domain1.domain.TLD" (top level domain). The idea is
that we are not bound to a host or specific location to find a key.
This allows the first point the key is found to service a request in the
case of a get key operation. So having said that, we only care about
the IP address if we use certificate based authentication and the
certificate is assigned to the IP address instead of the host ID.
Does that answer the question or raise additional questions?
Bob L.
Robert A. (Bob) Lockhart
Sr. Solutions Architect
nCipher, Inc.
Luther Martin wrote:
> Another thought on this - the generic URL syntax allows the use of an IP address for a host, so that
>
> host = IP-literal / IPv4address / reg-name
>
> It looks like we've limited this to
>
> host = reg-name
>
> in our namespace model. Do we want to do this?
>
>
>> -----Original Message-----
>> From: Landon Curt Noll [mailto:p1619.3-mail@ASTHE.COM]
>> Sent: Wednesday, May 28, 2008 11:33 PM
>> To: P1619-3@LISTSERV.IEEE.ORG
>> Subject: Re: [P1619-3] I18n of SO_GUID
>>
>> On 2008-May-28, at 17:21, Landon Curt Noll wrote:
>>
>>
>>> On 2008-May-28, at 15:17, Luther Martin wrote:
>>>
>>>
>>>> OK, here's an attempt at the ABNF definition of the URL SOGUID that
>>>> allows UTF-8.
>>>>
>>>> I've validated the ABNF syntax.
>>>> <abnf with utf8.txt>
>>>>
>>> I do not recommend ...
>>>
>> Allow me to retract my previous suggestion ... it is not in a form
>> that is easily merged into the current draft anyway. (sorry!)
>>
>> Luther and I are working out the details of our proposal ... I think
>> we are thinking along similar lines. We will see if we can work out a
>> common ABNF to address UTF-8 stuff and both of our ideas.
>>
>> Stay tuned ...
>>
>> chongo () /\oo/\
>>
>
>
>