Subject: [AAA-WG]: [Issue] Error handling editorial changes

From: Jacques Caron <[email-masked]>
Date: Thu, 14 Jun 2001 18:21:34 +0200

Submitter name: Jacques Caron
Submitter email address: [email-masked]
Date first submitted: 13-Jun-2001
Reference:
Document: Base
Comment type: E
Priority: 1
Section: throughout
Rationale/Explanation of issue:

Error handling
- In 9.0, in the result-code AVPs that require Failed-AVPs, need a 
clarification whether this is done only by the home server, or by any 
proxy/relay on the way
- In 9.0, what about errors regarding invalid length (packet or AVP)? 
Especially for AVPs, since it will be difficult to include a correctly 
formatted AVP if length is wrong anyway?
- In 5.3.2/9.1, DIAMETER_REDIRECT_INDICATION is not defined.
- clarify the difference between UNABLE_TO_DELIVER and NOT_SERVED? i.e. in 
which case is which sent? -- "I know the domain, but cannot reach any 
servers" vs "I don't know the domain".
- any specific messages for DNS errors (transient such as timeouts, or 
permanent such as NXDOMAIN)? -- I'd prefer we not have any, buy if you feel 
it is necessary, please propose some text.
- the difference between AUTHORIZATION_REJECTED and AUTHORIZATION_FAILED 
is, er, unclear.
- NO_COMMON_APPLICATION and UNSUPPORTED_VERSION would be better off in 
Protocol errors? -- except that protocol errors MUST only be used in MRA... 
see the problem :)
- protocol errors should be usable in any non-'P' messages
- missing errors for message or AVP length errors
- missing errors for unknown not-proxiable commands?
- missing errors for incorrectly set proxiable/not-proxiable flag?
- missing errors for unknown application
- classification of transient/permanent/protocol errors to review

I will send in some text asap. Comments/suggestions welcome.

Jacques.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com