Re: Comments on the comparison document

Hi, Maureen,

[email protected] wrote:

...
> 4.2 ENRP
> 
>    Another important aspect of ENRP is that itself is fully distributed
>    and replicated. This is to avoid the name service itself becoming a
>    single point of failure in the system.
> 
> This wording has the potential for the reader erroneously concluding that ENRP servers have perfectly synchronized databases.  Also "fully distributed" might cause confusion as it leaves out the operational scope which is technically what ENRP is limited to.
> 
> How about this excellent wording taken directly from the ENRP internet draft abstract.  Then put your last sentence at the end.:
> 
> Within the operational
>    scope of Rserpool, ENRP defines the procedures and message formats of
>    a distributed, fault-tolerant registry service for storing,
>    bookkeeping, retrieving, and distributing pool operation and
>    membership information.  This is to avoid the name service itself becoming a
>    single point of failure in the system.

Agreed. 

....
>    ASAP supports the "keepalive" monitoring of PEs by the name server
>    and session failover, in which a set of application messages are
>    defined as a "session" and ASAP provides best-effort transmission of
>    all the messages in the "session" to the same PE in the destination
>    pool, and failover the remaining message in the "session" to the same
>    alternate PE if the first PE fails.
> 
> Failover is not provided for all classes of service.  Need to fix one word as well.  How about:
> 
>    and for some classes of service can provide failover *for* the remaining 
>    message in the "session" to *an* alternate PE if the first PE fails.

agreed.

> 
> 4.2 ENRP
> 
> ENRP itself is dynamically scalable, meaning that new ENRP servers
>    can be added and existing servers be removed as needed. This feature
>    can be used to achieve zero planned downtime upgrade of a system - an
>    often found requirement in many mission critical applications.
> 
> change to (* to help you find the word(s) to change):
> 
> ENRP itself is dynamically scalable, meaning that new ENRP servers
>    can be added and existing servers *can* be removed as needed. This feature
>    can be used to achieve zero planned downtime upgrade of a system - an
>    *common* requirement *for* many mission critical applications.
> 

agreed.

> I think this is it.  Thanks.

Thanks for the comments. Aron, please make these changes as well when
you update the draft.

regards,
-Qiaobing

> 
> -- maureen
> 
> _______________________________________________
> rserpool mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/rserpool