ENRP Name Server Takeover Problem

Thomas Dreibholz <[email protected]>
Newsgroups gmane.ietf.rserpool
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear all,

when a NS takes over the ownership of PEs owned by a failed NS, it sends an 
ENDPOINT_KEEP_ALIVE message to each of the PEs which change their ownership. 
As defined in KA2.4 of section 3.4 of the ASAP draft, the PE should adapt the 
sender of an ENDPOINT_KEEP_ALIVE message as its new NS.

But, how does the new NS know the PEs' ASAP endpoint, that is especially the 
SCTP port number the PE is listening on for ASAP ENDPOINT_KEEP_ALIVES? The 
old (failed) NS has this information, because the PE established an 
association to it. But the new NS does not know. Therefore, a specification 
of the PE's ASAP endpoint must be added to the Pool Element Parameter. Simply 
adding a field for the SCTP port number should already be sufficient. The 
addresses to be used can be assumed to be the same as specified in the User 
Transport parameter.


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
=======================================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBKd7Z32BbsHYPLWURAtToAKCrnGWS5cBOmqv/PNXPvkxKxVhWEACeNaM2
rLi5vLWX8fIYJ9py+2iO1MA=
=T53y
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.