Hi Tom, all, We already have the following in the Introduction:
A network may support multiple services, potentially of different types. Whether a SAP topology is dedicated to services of a specific service type, an individual service, or shared among many services of different types is deployment specific. This document supports all of these deployment schemes. Added this NEW text to the Abstract: One or multiple services can be bound to the same SAP. Thanks. Cheers, Med > -----Message d'origine----- > De : tom petch <ie...@btconnect.com> > Envoyé : lundi 19 décembre 2022 17:29 > À : Rob Wilton (rwilton) <rwil...@cisco.com>; BOUCADAIR Mohamed > INNOV/NET <mohamed.boucad...@orange.com> > Cc : draft-ietf-opsawg-sap....@ietf.org; opsawg@ietf.org > Objet : Re: AD review of draft-ietf-opsawg-sap-09 > > From: Rob Wilton (rwilton) <rwil...@cisco.com> > Sent: 19 December 2022 14:19 > > Hi Tom, > > My understanding is that service is the top list (i.e., > node/service) and the saps are in the per service child list: > > augment /nw:networks/nw:network/nw:node: > +--rw service* [service-type] > +--rw service-type identityref > +--rw sap* [sap-id] > > The text is section 5 states: > > 'sap-id': Includes an identifier that uniquely identifies a > SAP > within a node. > > The same SAP may appear under distinct service types. In > such a > case, the same identifier is used for these service types in > association. > > So, I think that the answer is yes, the same SAP can support > multiple services, but they are keyed by service then sap, rather > than the other way round, and some presumably common SAP > properties will appear duplicated per service. For SAP properties > that must be common across all services on the same SAP then I > think that the authors and WG considered have a separate per node > SAP list but presumably decided that aligning this under the > service made the model easier to use, particularly in the case > where there is only a single service per SAP. > > <tp> > Ah yes,I can see it now on page 10. I did not understand that > from Abstract or Introduction. > > Tom Petch > > Regards, > Rob > _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
