embedlets-developer

[Embedlets-dev] Re: Naming

[Andrzej J. T. <an...@ch...>]

Chris suggests:

> It may actually make a lot of sense to use a DNS to keep a database of ips,
> since that is what they do. It would be especially useful in a large
> installation such as an oil refinery:

That's true...but the guys deploying the devices may not have the knowledge 
nor access to the corporate DNS servers. And the glass house guys probably 
won't want to implement DNS lookups for thousands of devices.

Be great if they did though. ;-)

> There should be a name AND an identity (you may have stated this but I just
> wanted to emphasize to point). The name is used for human consumption and can
> change, the identity is fixed for the life of the configuration and is used
> for internal reference.

Why not just use a string based identiy that can be used for both?

Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com

[Embedlets-dev] Re: Naming

[Andrzej J. T. <an...@ch...>]

Chris clarifies:

> Because you want to have a name or description that has meaning to an
> operator ('Crude Oil Feed - west tower'), may be changed to match local or
> variant situations or may need to support internationalization.

Ah.....I distinguish between a Name/ID (which I see as identical, a unique 
identifier for the component/container) versus a Description.  Both are good 
to have.

Another one of those miscommunications issues is all....we're in violent 
agreement.

Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com

Re: [Embedlets-dev] Re: Naming

[Holger B. <ho...@bi...>]

> Chris suggests:
>
>> It may actually make a lot of sense to use a DNS to keep a database 
>> of ips,
>> since that is what they do. It would be especially useful in a large
>> installation such as an oil refinery:
>
> That's true...but the guys deploying the devices may not have the 
> knowledge
> nor access to the corporate DNS servers. And the glass house guys 
> probably
> won't want to implement DNS lookups for thousands of devices.
>
> Be great if they did though. ;-)
>
>> There should be a name AND an identity (you may have stated this but 
>> I just
>> wanted to emphasize to point). The name is used for human consumption 
>> and can
>> change, the identity is fixed for the life of the configuration and 
>> is used
>> for internal reference.
>
> Why not just use a string based identiy that can be used for both?

Why do not use a SHA-1 value, use a PKI CA and X.509 certificates and 
you have with 20 bytes on the device a home-run, i think. Environments 
for this are already out there (ejbca at sf.net).

JAI

bax