Re: Ordering within RK parameter of M3UA

Sergey,

Logically, the repeated structure only needs to start with Destination
Point Code (to identify a new group of parameters).  The order of
the parameters other than DPC within the repeated structure is
unimportant.  Likely, Local-RK-Identifier and Traffic Mode should come
first, but they don't have to.

So, one would expect to find Local-RK-Identifier somewhere within the list
of parameters, and, optionally, a Traffic Mode somewhere within the list of
parameters, an at least one Destination Point Code somewhere within the list
of parameters.  The optional parameters associated with a given DPC would
occur between the DPC and either the next DPC or the end of the Routing Key.

Is this not obvious to you?

--brian

On Mon, 16 Jan 2006, Sergey Mikhailov wrote:

> Brian,
> 
> thank you for your reply.
> 
> Do you mean that the phrase "MAY be repeated as a grouping within the
> Routing Key parameter, in the structure shown above" (in that Note from
> 3.6.1) explicitly mandates (like mentioned in 3.2) the ordering? Or it has
> just illustrative meaning?
> 
> Regards,
> Sergey Mikhailov.
> 
> 
> 
> ----- Original Message ----- 
> From: "Brian F. G. Bidulock" <[email protected]>
> To: "Sergey Mikhailov" <[email protected]>
> Cc: "SIGTRAN" <[email protected]>
> Sent: Monday, January 16, 2006 1:06 PM
> Subject: Re: [Sigtran] Ordering within RK parameter of M3UA
> 
> 
> > Sergey,
> >
> > Read Section 3.2:
> >
> >  ...
> >
> >  Where more than one parameter is included in a message, the
> >  parameters may be in any order, except where explicitly mandated.  A
> >  receiver SHOULD accept the parameters in any order.
> >  ...
> >
> > --brian
> >
> > On Mon, 16 Jan 2006, Sergey Mikhailov wrote:
> >
> >>
> >>    Hi,
> >>
> >>
> >>
> >>    It   seems quite   open  to  interpretation (from  3.2  and  3.6.1  of
> >>    3332bis05),  whether  Destination  Point  Code, Service Indicators and
> >>    Originating  Point  Code  List  parameters (which may be repeated as a
> >>    grouping) must follow in exactly this order or not.
> >>
> >>
> >>
> >>    From 3.6.1:
> >>
> >>
> >>
> >>          Note: The Destination Point Code, Service Indicators, and
> >>          Originating Point Code List parameters MAY be repeated as a
> >>           grouping  within  the  Routing  Key parameter, in the structure
> >>    shown
> >>          above.
> >>    It  think  that  there  is  now requirement to their ordering inside a
> >>    grouping, but have to admit that this is just my interprertation.
> >>
> >>    Any opinions?
> >>
> >>
> >>
> >>
> >>
> >>    Best Regards,
> >>
> >>    Sergey Mikhailov.
> >
> >> _______________________________________________
> >> Sigtran mailing list
> >> [email protected]
> >> https://www1.ietf.org/mailman/listinfo/sigtran
> >
> >
> > -- 
> > Brian F. G. Bidulock    ¦ The reasonable man adapts himself to the ¦
> > [email protected]    ¦ world; the unreasonable one persists in  ¦
> > http://www.openss7.org/ ¦ trying  to adapt the  world  to himself. ¦
> >                        ¦ Therefore  all  progress  depends on the ¦
> >                        ¦ unreasonable man. -- George Bernard Shaw ¦
> >

-- 
Brian F. G. Bidulock    ¦ The reasonable man adapts himself to the ¦
[email protected]    ¦ world; the unreasonable one persists in  ¦
http://www.openss7.org/ ¦ trying  to adapt the  world  to himself. ¦
                        ¦ Therefore  all  progress  depends on the ¦
                        ¦ unreasonable man. -- George Bernard Shaw ¦