Re: PEER_ERROR message

Thomas.. I have taken this
suggestion.

Next revision we will make PEER_ERROR the same
error number (0xe)

and then change all reference to ENRP_ERROR
to PEER_ERROR

R


Thomas Dreibholz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Monday 11 October 2004 22:46, Johnson Walter-CWJ002 wrote:
> 
>>Any reference to the PEER_ERROR message should be removed from the ASAP
>>protocol document since I believe it is not an ASAP message.
> 
> 
> It is useful to have this message type in ASAP, because e.g. a component (NS, 
> PE or PU) could receive a bad message via ASAP. Then, it can report the 
> sender that it does not understand/accept this message via a PEER_ERROR. This 
> is useful for debugging.
> 
> To make ASAP and ENRP PEER_ERROR more consistent, their definitions and 
> especially the message type number (currently: 0x0e or ASAP, 0x0b for ENRP) 
> could be unified. For example, the message number could be 0xff for both.
> 
> 
> 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)
> 
> iD8DBQFBa50632BbsHYPLWURAg5hAJwPJxLFPfWhNx0afzjntqKl/rmgagCdGO+G
> EDx/otU5qMtWX79xZKnCSxU=
> =K88g
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> rserpool mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/rserpool
> 
> 
>