Re: ENRP Peer Name Update

Thomas,

Thomas Dreibholz wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Dear all,
> 
> ENRP PEER_NAME_UPDATE contains the full Pool Element Parameter even in case of 
> deregistrations. ASAP DEREGISTRATION only uses a PE Identifier Parameter to 
> identify the PE. This is sufficient to identify and remove the PE. So, what 
> about defining to also use a PE Identifier parameter for deregistrations in 
> the PEER_NAME_UPDATE? That is, in case of registrations PEER_NAME_UPDATE 
> would contain a Pool Element Parameter and in case of deregistrations a PE 
> Identifier Parameter.

The advantage of using a single format for PEER_NAME_UPDATE is to make the implementation 
easier and to keep the number of messages small (remember we also have PE update in addition 
to add and remove). In the case of removal (I wouldn't call it de-reg, see below), we may 
allow the sender to only fill in the PE-id and leave other fields blank and allow the 
receiver to ignore the other fields. But I do not see the value of using different formats.

> 
> May be, it would be a good idea to split up PEER_NAME_UPDATE into a 
> PEER_NAME_REGISTRATION and PEER_NAME_DEREGISTRATION.  Then, it would be 
> consistent to ASAP's message types.

I think there is never an intention to match ASAP types here. Calling Peer-name-reg and 
peer-name-dereg is IMO misleading since the sending ENRP server is not doing a reg or de-reg 
with the receiving server. they are really updating each other.

regards,
-Qiaobing

> 
> 
> Best regards
> - -- 
> =======================================================================
>  Dipl.-Inform. Thomas Dreibholz
> 
>  University of Duisburg-Essen                    Room ES210
>  Inst. for Experimental Mathematics              Ellernstraße 29
>  Computer Networking Technology Group            D-45326 Essen/Germany
> - -----------------------------------------------------------------------
>  E-Mail:     [email protected]
>  Homepage:   http://www.exp-math.uni-essen.de/~dreibh
> =======================================================================
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> 
> iD8DBQFBBh6932BbsHYPLWURAg7UAKC4k1L1fC4kyMB/1cxkLeksxePL+QCePM78
> uDbdR+0wptVWbmoGNv5v60c=
> =g//Z
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> rserpool mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/rserpool
>