Re: ASAP and ENRP drafts - suggested modifications

On Friday 17 December 2004 13:26, Goyal Anurag-A20942 wrote:
> I see the need for a server identifier  (Server_Id parameter could do the
> job) in the message ENDPOINT_KEEP_ALIVE(eka). This is required as the asap
> draft (version10, section 3.4 point KA2.4) says that, on receipt of this
> message, the PE should adopt the ENRP server as its home enrp server. The
> eka message currently has just one parameter namely 'Pool Handle
> Parameter', which does not carry any information about the ENRP server
> sending the message. Hence, it makes sense to send Server_Id as another
> parameter in eka.

Yes, this makes sense.

Furthermore, a Server_Id parameter should be added to the ASAP Server Announce 
to make it possible for a PE/PU to find out who the PR sending this announce 
is.


Best regards
-- 
=======================================================================
 Dipl.-Inform. Thomas Dreibholz

 University of 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
=======================================================================

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBBwt1P32BbsHYPLWURAl1QAKC+tqSk/Aicy020iFesL2yWM9vPxwCgqeqm
SOFN4IpxXqbvj1GuMVcYUEU=
=FsQ0
-----END PGP SIGNATURE-----