[Hipsec-rg] Hierarchical HITs

[julien.laganier.ietf at googlemail.com (Julien Laganier)]

Sheng,

Sheng Jiang wrote:
>> This is exactly the point; If a HHIT has the limitation that:
>>
>> - it is bound with one entity in the hierarchy compared to a plain HIT
>> (like a DNS name is)
>>
>> - is not human readable compared to a DNS name (like a HIT is)
>>
>> Then why should I use a HHIT as a host identifier? I'm getting all of
>> the disadvantages of HIT (not readable) or DNS name (bound to an entity
>> in the hierarchy) but none of their respective advantages, i.e., not
>> being bound to an entity, or being readble...
> 
> I don't think bound to an entity in the hierarchy is a disadvantage at all.

You haven't replied to my previous question which was "My question was,
If my identifier is bound with one entity in the hierarchy, what would
be the advantage of using HHIT as host identifiers, compared to using
DNS names as host identifiers? "

Now if this is not a disadvantage, and if it's actually the
functionality that you're searching for, why can't you simply use domain
names as host identifiers. They have the advantage of being human
readable, and I do not see any domain name drawback to HHIT...

--julien