Re: [HOKEY] AD review of draft-ietf-hokey-arch-design

[Glen Zorn <[e-mail]>]

On 10/29/2011 10:25 PM, Glen Zorn wrote:
> On 10/23/2011 11:52 PM, Stephen Farrell wrote:
> 
> (pasted from the attachment)
> 
>> not quite nits:
>>
>> - I realise that this document references lots of others that define
>> things, but a bit of ascii art at the start would have been helpful.
>> Its not obvious where e.g. the "ER server" might live from the
>> current text.
> 
> Actually I removed the ASCII art that was there because I thought that
> it was way confusing.  I suppose that it can be put back.

Looking again at the ASCII art I removed, it doesn't appear to me to be
what you're asking for anyway; it it's necessary, it will take awhile
(i.e., > 1 hour to do...

...

>> - p8 - what is a "HOKEY server"?
> 
> I think that it is generic term for a server supporting hand-over keying
> -- could be a ER server or an AAK server, for example.
> 
>> should that be in the terminology
>> section?
> 
> Since it seems to appear only once, maybe we could just try to rephrase
> the sentence?

Here's a first cut:

OLD:
   To provide better deployment scalability, there should be no
   requirement for co-location of the HOKEY server and AAA servers or
   proxies.  Separation of these entities may cause problems with
   routing, but allows flexibility in deployment and implementation.

NEW:
   To provide better deployment scalability, there should be no
   requirement for co-location of entities proving handover keying
   services (e.g., ER servers) and AAA servers or proxies.  Separation
   of these entities may cause problems with routing, but allows greater
   flexibility in deployment and implementation.

...