Hi Med, thank you for pointing this out to me. I have a follow-up question. If I understand that note correctly, SDP is positioned as an example, a realization of SAP in IETF Network Slice. What could be other examples or realizations of SAP?
Regards, Greg On Mon, Mar 21, 2022 at 4:50 AM <mohamed.boucad...@orange.com> wrote: > Hi Greg, > > > > The slice draft already says the following: > > > > An SDP may be abstracted as a Service Attachment Point (SAP) > > [I-D.ietf-opsawg-sap] for the purpose generalizing the concept > > across multiple service types and representing it in management > > and configuration systems. > > > > Cheers, > > Med > > > > *De :* Greg Mirsky <gregimir...@gmail.com> > *Envoyé :* lundi 21 mars 2022 12:17 > *À :* Adrian Farrel <adr...@olddog.co.uk>; TEAS WG <t...@ietf.org>; > opsawg <opsawg@ietf.org>; BOUCADAIR Mohamed INNOV/NET < > mohamed.boucad...@orange.com> > *Objet :* A question on the definitions of SDP and SAP > > > > Hi Adrian, > > I've read the draft-ietf-teas-ietf-network-slices > <https://datatracker.ietf.org/doc/draft-ietf-teas-ietf-network-slices/> (many > thanks for all your work on it!) and I've got a question. It appears to me > that the definition of a Service Demarcation Point section 2.1) as the > point of where the IETF Network Slice service is delivered by the provider > to a customer is similar to the definition of a Service Attachment Point in > draft-ietf-opsawg-sap > <https://datatracker.ietf.org/doc/draft-ietf-opsawg-sap/> as an > "abstraction of the network reference points where network services can be > delivered to customers." Hence my question. Is there an intended difference > between SDP and SAP that is indicated by using different terms? > > > > Regards, > > Greg > > _________________________________________________________________________________________________________________________ > > 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
