Hi Wim,
Youre welcome to shime whenever you want. I think it is important, in this discussion, to reflect that the service is not the realisation. For the main part, this document describes the service and, while it must allow for multiple realisations, it does not attempt detailed descriptions. Cheers, Adrian From: Teas <teas-boun...@ietf.org> On Behalf Of Henderickx, Wim (Nokia - BE/Antwerp) Sent: 22 March 2022 14:09 To: Greg Mirsky <gregimir...@gmail.com>; Med Boucadair <mohamed.boucad...@orange.com> Cc: Adrian Farrel <adr...@olddog.co.uk>; opsawg <opsawg@ietf.org>; TEAS WG <t...@ietf.org> Subject: Re: [Teas] A question on the definitions of SDP and SAP Sorry the shime in late in this thread but there is one thing still bothering or I wanted to highlight. Maybe we can do another thread if needed. Here is the thing I am struggling with in the current draft, which is what I call multiplexing or what I sometime call mapping. My understanding so far is we have SDP and connectivity construct to represent a slice In reality I believe or in my view: we have SDP a forwarder of some sort (it is dependent on the connectivity matrix) a connectivity matrix On top we have some multiplexing and mapping into these constructs. So in my view you can implement the slices in various ways. I am using 3GPP as the endpoints radio in this case And my examples are not exhaustive but I am using to show what I mean with multiplexing/mapping e.g. * Slice1 -> Radio vlan 1 sdp 1 fwd ctx 1 connectivity matrix 1 * Slice2 -> radio vlan 2 sdp 1 fwd ctx 2 connectivity matrix 2 Or * Slice1 -> Radio vlan 1 sdp 1 fwd ctx 1 connectivity matrix 1 * Slice2 -> radio vlan 2 sdp 1 fwd ctx 1 connectivity matrix 2 Or * Slice1 -> Radio flow label 1 sdp 1 fwd ctx 1 connectivity matrix 1 * Slice2 -> radio flow label 2 sdp 1 fwd ctx 2 connectivity matrix 2 Or * Slice1 -> Radio flow label 1 sdp 1 fwd ctx 1 connectivity matrix 1 * Slice2 -> radio flow label 2 sdp 1 fwd ctx 1 connectivity matrix 2 Also would be good to see if this is covered how this maps in the current framework. From: Teas <teas-boun...@ietf.org <mailto:teas-boun...@ietf.org> > on behalf of Greg Mirsky <gregimir...@gmail.com <mailto:gregimir...@gmail.com> > Date: Tuesday, 22 March 2022 at 14:50 To: Med Boucadair <mohamed.boucad...@orange.com <mailto:mohamed.boucad...@orange.com> > Cc: Adrian Farrel <adr...@olddog.co.uk <mailto:adr...@olddog.co.uk> >, opsawg <opsawg@ietf.org <mailto:opsawg@ietf.org> >, TEAS WG <t...@ietf.org <mailto:t...@ietf.org> > Subject: Re: [Teas] A question on the definitions of SDP and SAP Hi Med, thank you for the additional information. In my understanding, please correct me if it is off, L3 and L2 VPNs are technologies that can be used to realize an IETF Network Slice. If that is the case, then the SAP in, for example, an L3 VPN is also SDP of the IETF Network Slice. Am I missing something? Kind regards, Greg On Tue, Mar 22, 2022 at 5:43 AM < <mailto:mohamed.boucad...@orange.com> mohamed.boucad...@orange.com> wrote: Hi Greg, Other examples can be an L3 VPN network access (RFC9182) or L2 VPN network access (draft-ietf-opsawg-l2nm). FWIW, the SAP spec include these notes: (1) For example, this concept is used to decide where to attach and, thus, deliver the service in the Layer 3 VPN Service Model (L3SM) [RFC8299] and the Layer 2 VPN Service Model (L2SM) [RFC8466]. It can also be used to retrieve where services, such as the Layer 3 VPN Network Model (L3NM) [RFC9182], and the Layer 2 VPN Network Model (L2NM) [I-D.ietf-opsawg-l2nm], are delivered to customers. (2) For example, 'sap-id' may be the VPN network access identifier in Section 7.6 of [RFC9182]. An example to illustrate the use of this attribute during service creation is provided in Appendix D. Cheers, Med De : Greg Mirsky < <mailto:gregimir...@gmail.com> gregimir...@gmail.com> Envoyé : mardi 22 mars 2022 10:34 À : BOUCADAIR Mohamed INNOV/NET < <mailto:mohamed.boucad...@orange.com> mohamed.boucad...@orange.com> Cc : Adrian Farrel < <mailto:adr...@olddog.co.uk> adr...@olddog.co.uk>; TEAS WG < <mailto:t...@ietf.org> t...@ietf.org>; opsawg < <mailto:opsawg@ietf.org> opsawg@ietf.org> Objet : Re: A question on the definitions of SDP and SAP 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 < <mailto:mohamed.boucad...@orange.com> 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 < <mailto:gregimir...@gmail.com> gregimir...@gmail.com> Envoyé : lundi 21 mars 2022 12:17 À : Adrian Farrel < <mailto:adr...@olddog.co.uk> adr...@olddog.co.uk>; TEAS WG < <mailto:t...@ietf.org> t...@ietf.org>; opsawg < <mailto:opsawg@ietf.org> opsawg@ietf.org>; BOUCADAIR Mohamed INNOV/NET < <mailto:mohamed.boucad...@orange.com> mohamed.boucad...@orange.com> Objet : A question on the definitions of SDP and SAP Hi Adrian, I've read the <https://datatracker.ietf.org/doc/draft-ietf-teas-ietf-network-slices/> 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 <https://datatracker.ietf.org/doc/draft-ietf-opsawg-sap/> 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. ____________________________________________________________________________ _____________________________________________ 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
