NML group, Sorry I forgot to send these last week based on Freek's request. The point behind the attached slides was to get agreement of the formal use of the Switching Service element in NSI. I believe we all agreed on how it can be used when specifying the ports/portGroups within the SwitchingService itself, but people wanted clarity around default situations. #1 What is the behaviour when no switching service specified within the topology. #2 Can someone specify a default switching service with labelSwapping == true without listing all the ports within the SwitchingService? I think #1 is required and we basically follow the rule of all ports with the same encoding can be placed in a single switching service with labelSwapping set to false. I defined behaviours for #2 such that you could specify an empty switching service that changes the default to labelSwapping == true, however, a few of us question the value. Why not just list all the ports? There are concerns listing all the ports in a SwitchingService will be costly by making the documents bigger, but I am not sure this is a big issue given the verbosity of the overall solution. Adding additional complexity to default logic seems more costly to me. I am not sure it was clear there will be an equivalent cost in size by needing the encoding attribute added to all the ports so we can match the proper technologies. John