Re: correct Error code

Brian,

On 3/29/07, Brian F. G. Bidulock <[email protected]> wrote:
>
> Ankit,
>
> Ankit Kumar Sharma wrote:                          (Thu, 29 Mar 2007
> 14:33:50)
>
> >      Also, RFC 4666 says:
> >          - If the RC parameter is included in the ASP Active message and
> the
> >           corresponding RK has been previously defined (by either static
> >            configuration  or  dynamic  registration), the peer node MUST
> respond
> >            with  an  ASP  Active  Ack  message.  If for any local reason
> (e.g.,
> >            management lockout) the SGP responds to an ASP Active message
> with
> >           an Error message with reason "Refused Management Blocking".
> >
> >    I  think  RFC is talking about the case in which ASP active contains
> a
> >    VALID  RC value which is configured for the AS, whom this ASP wants
> to
> >    serve, at peer.
>
> The RC value is valid (there is a corresponding RK defined by static
> configuration).
>
> >
> >    Error  message  with  "Invalid  routing  context"  ecode seems to be
> a
> >    better option because it clearly shows the cause.
>
> But is forbidden by the RFC in this case.  Besides it is incorrect because
> the RC is valid, (just not permitted).


I somewhat agree with you but I still feel that 'valid' and 'configured' are
two different things. If a RC is configured for an AS then it is not valid
for any xyz ASP(which has to serve different AS) to send ASP-ACTIVE with
this RC.
Purpose of any error code is to let the user correct the cause of error
quickly. If i go by your words i.e reply with ecode "..Blocking" then
originator of ASP-AC could think that his message is perfect but for some,
unknown, local reason peer is not allowing this ASP to become active.
Whereas, if we reply with "inv...context" ecode then originator could
quickly check on the RC value to make it's ASP Active.

--brian
>
> --
> Brian F. G. Bidulock
> [email protected]
> http://www.openss7.org/
>

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