[Nml-wg] hasService / hasInboundPort

Jeroen van der Ham vdham at uva.nl
Wed Mar 13 10:37:42 EDT 2013


Hi,

On 13 Mar 2013, at 10:07, Freek Dijkstra <Freek.Dijkstra at surfsara.nl> wrote:
> So I suggest we should make the second form a MUST, and the first a
> SHOULD NOT. (Admittedly, the first form does no harm at all, and is
> useful. The reason for the strong SHOULD NOT is that it brings a risk of
> incompatibility if one organisation uses the first form, and another
> organisation uses the second form)


That is already covered by the first MUST. The SHOULD NOT would mean that we change the inherited behaviour of the Switching Service. If we keep that as a SHOULD, and the hasInboundPort as MUST, things work out.

Jeroen.



More information about the nml-wg mailing list