Re: (M2PA) Question about the requirement "The same standard MUST be followed on both ends"

Jeffrey,

Being necessary for interoperability, "MUST" is appropriate
and it falls squarely inside the scope of the specification.

--brian

Craig, Jeffrey wrote:                                               (Wed, 01 Feb 2006 07:25:57)
> Hello Brian,
> 
> Thanks for your response.
> 
> In my view, your statements confirm that the requirement
> falls outside the scope of the M2PA RFC. M2PA has an 
> unbounded list of 'applicable' specification/standards, 
> since it states (note the 'SHOULD' and 'may include'):
> 
>    Except as modified in this document, M2PA SHOULD 
>    follow the requirements of the applicable MTP2
>    specification.  These may include [Q.703] or [T1.111].
>    The same standard MUST be followed on both ends
>    of the M2PA link.                                                    
> 
> If two different M2PA peers are able to pass an 
> implementer's/user's interoperability tests, then it does 
> not matter what the base MTP2 specification is for each 
> M2PA. If the cited MTP specifications already state a 
> 'same standard on both ends' requirement, then M2PA does 
> not also need to state the same requirement.
> 
> The last statement in the above RFC paragraph should either
> be deleted or changed to 'SHOULD'. If the statement remains,
> then it would have real value, if additional text is added 
> explaining, with some detail, why both M2PA peers SHOULD 
> conform to the same MTP2 specification.
> 
> Regards,
> 
> Jeff
> 

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