Re: [OPSAWG] comment for draft-ietf-opsawg-sap-09

[[e-mail]]

Hi Asad,

Please see inline.

Cheers,
Med

De : Arafat, Asad (Nokia - DE/Stuttgart) <[e-mail]>
Envoyé : jeudi 22 septembre 2022 17:29
À : BOUCADAIR Mohamed INNOV/NET <[e-mail]>; [e-mail]
Cc : Arafat, Asad (Nokia - DE/Stuttgart) <[e-mail]>
Objet : Re: comment for draft-ietf-opsawg-sap-09

Thanks for the explanations Med..

It brings me to another questions

  *   Is there any standard method to augment some parameter that not included in service dataModel (L2NM/L3NM). Ie: dhcp snooping?
[Med] L2NM/L3Nm can be augmented following rfc7950#section-4.2.8. You can write an I-D with the proposed augmentations and share them with the list.


  *   Appendix A in the draft made me curious, is there any standard that define service stitching?
[Med] I'm not aware of a generic model and would be surprised to see as I guess this depends on the service.

It could be inter-as option A or even L2VPN-to-L3VPN?

Cheers/Asad

From: [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
Date: Thursday, 22. September 2022 at 16:52
To: Arafat, Asad (Nokia - DE/Stuttgart) <[e-mail]<mailto:[e-mail]>>, [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
Subject: RE: comment for draft-ietf-opsawg-sap-09
Hi Asad,

Thank you for the comment.

I hear you. It is tempting to include such details into the SAP network model but we tried to avoid interfering with other device models or other network models (L3NM/L2NM). That's is why we have the following note in the draft:

   Advanced interface-specific data nodes are not included in the SAP
   model.  The interface identifiers listed in the SAP model can be used
   as filters to set or get such data using device models (e.g.,
   [RFC7224]).

For the particular case of L2NM/L3NM we do have the following:


      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.

...which means that the attachment circuit configuration will be directly included into the L2NM/L3NM while sap-id=vpn-network-access-id is used to correlate between the two.

I understand you want to do it in the other way around.

Cheers,
Med

De : OPSAWG <[e-mail]<mailto:[e-mail]>> De la part de Arafat, Asad (Nokia - DE/Stuttgart)
Envoyé : jeudi 22 septembre 2022 16:31
À : [e-mail]<mailto:[e-mail]>
Objet : [OPSAWG] comment for draft-ietf-opsawg-sap-09

Hi draft-ietf-opsawg-sap-09 authors

I have several comment regarding the draft.

Since I don't see a placeholder for configuration object that can be configured in the service attachment point. I believe it would be better to enrich the SAP model with the popular attachment circuit configuration of l2vpn and l3vpn, such as:

  *   Multicast protocol like IGMP(snooping), MLD(snooping)
  *   DHCP (snooping)
  *   IP/mac filter
  *   QOS policy
  *   OAM
  *   IP address
  *   Some extra fields can be reserved for arbitrarily usage

The use case that I can think of is when a Controller wanna config a service with L2NM or L3NM the following path can be augmented with the detail of SAP model


  *   /l3nm:l3vpn-ntw/l3nm:vpn-services/l3nm:vpn-service/l3nm:vpn-nodes/l3nm:vpn-node/l3nm:vpn-network-accesses
  *   /l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services/l2vpn-ntw:vpn-service/l2vpn-ntw:vpn-nodes/l2vpn-ntw:vpn-node/l2vpn-ntw:vpn-network-accesses

Similar can also for the service configuration retrieval.


Cheers/Asad


_________________________________________________________________________________________________________________________

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.