This is include only the capacity element that is defined in the p2p schema as a standalone element for the purposed of modification. This is not including the full <p2ps> element and using optionality. It is including the <capacity> element. If you look at the p2p service schema this is parameter defined as modifiable in the p2p service (startTime and endTime are in the CS schema itself).
You may ask why it was done this way… It allowed us to have the original reservation request have mandatory elements for the service, but the modify to only contain those elements being changed.
The CS 2.1 document states in section 15.7 that only the elements to
be modified are included in a modify request. However, in the schema
the p2p parameters directionality,
capacity, sourceSTP and destSTP are not optional. As a result the
example modify requests in figure 154 and 155 will not pass schema
validation.
If the four parameters are made optional in the schema it will also
be possible to leave them out in the initial reserve request, which
will cause problems because all four of them belong to the minimum
set of parameters in this stage. Or the schema is left as is making
it mandatory to always send the minimum set of parameters in every
modify request, in this case section 15.7 should be updated to
reflect this.
Please advise how to proceed.
Cheers,
HansT.
_______________________________________________ nsi-wg mailing list nsi-wg@ogf.org https://www.ogf.org/mailman/listinfo/nsi-wg