Re: ASAP Handle Resolution Option
"Ong, Lyndon" <[email protected]> Wed, 19 Nov 2008 09:58:52 -0500
| Newsgroups | gmane.ietf.rserpool |
|---|---|
| Message-ID | <[email protected]> |
Hi Folks, Not to pass judgement one way or another on the handle resolution option, but I don't see our A-Ds favoring the creation of a new item on our charter. I believe the most likely direction forward on this is as an individual draft rather than a Working Group activity. I will check with Lars and Magnus, though. Best regards, Lyndon -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dirk Hoffstadt Sent: Wednesday, November 19, 2008 6:02 AM To: [email protected] Subject: [Rserpool] ASAP Handle Resolution Option -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear all, What about the draft draft-dreibholz-rserpool-asap-hropt-03 (http://tools.ietf.org/html/draft-dreibholz-rserpool-asap-hropt-03) on the ASAP Handle Resolution option to specify the requested number of PE entries to be selected? I think this is a quite useful extension and should also be moved forward. In our deployed RSerPool pool for SimProcTC, we do not need the PU-side handle resolution cache. Therefore, on a handle resolution, the ENRP server should exactly select one PE entry for the SimProcTC PU. ASAP as defined in RFC 5352 lacks of the possibility to specify this. The handle resolution option allows the PU to exactly tell this information to the ENRP server. So, the ENRP server can exactly select the one PE entry for our SimProcPC PU -- while it can provide more entries to PUs actually making use of the PU-side cache. I see a clear need for standardization of such an option, since its functionality is IMHO mandatory for efficient handle resolution. - -- Best regards, Dirk Hoffstadt - ------------------------------------------------------------------ M.Sc. Dirk Hoffstadt DH Datentechnik 45219 Essen Germany E-Mail: [email protected] Internet: http://www.dhdt.de PGP-PublicKey: https://dhdt.de/private/dirkhoffstadt_pubpgp.asc - ------------------------------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iQEcBAEBAgAGBQJJJBw+AAoJEAl0PP0XKTexS1oH/0V820ZYdH+vLZA8KbaNNY/7 XgJBXwL4D1FGVZUbhUSQtQpBxOB1dV95Wa5eU/c2gRd+TupmUXQB7BpBC/VEGqi+ wCrxmUpIpubSuVZfaZ341ZDnotgsBoXszjaPQWDTzR6UhOG7k67dalBgN53j2B66 qvGuryvRacGVhYT9QM3D5mftNPcUP7dzAJn7ioDBkfVAFkFercPwC8SrPFU/6Dan XCEhVzvS394+vIGN0EohDjsqMIDjQKQZ8NBAYgmXnm70Znyo4sSogHDH9i0QvzDE jWtz7QeBlu7bHrzare2EMNElKiq/v0FX4jUe+TszD+dbP3BE0ijo+FWez0kpaas= =Xreh -----END PGP SIGNATURE----- _______________________________________________ rserpool mailing list [email protected] https://www.ietf.org/mailman/listinfo/rserpool