Re: [OPSAWG] SAPs and Attachment Circuits Provisioning (was TR: I-D Action: draft-boro-opsawg-ntw-attachment-circuit-01.txt)

[[e-mail]]

Hi Moti, 

Thanks for the comments. 

Please see inline. 

Cheers,
Med

> -----Message d'origine-----
> De : Moti Morgenstern <[e-mail]>
> Envoyé : lundi 6 mars 2023 14:22
> À : BOUCADAIR Mohamed INNOV/NET <[e-mail]>;
> [e-mail]
> Cc : [e-mail]
> Objet : RE: SAPs and Attachment Circuits Provisioning (was TR: I-D
> Action: draft-boro-opsawg-ntw-attachment-circuit-01.txt)
> 
> Hi,
> 
> Here are my comments so far:
> 
> Introduction ("the same attachment circuit may be used to host
> multiple services") - The hierarchy is unclear.

[Med] What is meant here is the value added services that are delivered/supported via the AC; no the AC-as-Service per se. I agree that we need a better wording to better articulate this. 


 So far I knew that
> in a simple use-case we have a bearer channel that can carry one
> or several ACs and the traffic over each of them is delimited by
> single or double VLAN tags. It is also aligned with the definition
> of "Bearer" in the next chapter. If the sentence above is assumed
> then how do we call the logical connection associated with each
> single service? If not by VLAN(s), then how does the PE determine
> to which service a packet belongs?

[Med] When the same AC multiplexes N services, the classification/access control rules specified for each service will need to be followed. 

> 
> Figure 1:
> Top-Left: Who owns the block/device between PE1 and CE6?
> It cannot be the customer because otherwise both AC endpoints are
> owned by the customer.
> If it is the provider then the SAP is in practice located at the
> block. The customer is not aware to the internal topology of the
> provider's network
> 
> Top-Right: Assuming the AC connects the customer to the PE, it
> means the block is owned by the customer. It also means that the
> provider is not aware to CE2 and CE5. Each of the CEs is served
> separately by
> 

[Med] Good point. The intent was to reflect in the figure that some infrastructure may be in-between the PE/CE, but no need to complexify the figure. Replaced the box with lines.

> Bottom: Do we consider the pair of ACs between CE3 and the
> provider (same for CE4) as independent?

[Med] Yes. 

 If not, then there is a
> single AC that is specified on top of the two SAPs.

[Med] Agree. 

 For CE3 it
> looks like a MC-LAG (or an Ethernet Segment for the case of EVPN).
> For CE4 it looks like a LAG connectivity.
> 
> 4.1 "... an AC is uniquely identified within the scope of a node
> not a network." - What does it mean? Do we need a comma somewhere?

[Med] a comma is needed right before "not a network".

> "... a set of profiled can be defined at the network level" -
> maybe "profiles"?
> 

[Med] Yes. Fixed. Thanks.

> 4.2
> - replace svlan id and cvlan id with outer and inner vlan id,
> which is more generic and clear.

[Med] Agree, but we are trying to ease correlation with other models (rfc9182, rfc9291).

> - In practice, tag operations can be performed on both ingress and
> egress directions

[Med] Agree, however we went with the same simplification assumption as per L2NM: symmetric mode. If there are AC cases that would require asymmetric operations, then the full operation structure has to be modified, IMO.

> - tag1 and tag2 do not necessarily have the same push/pop
> operation.
> 

[Med] Are there cases that you think can't be covered with the current model?

==
             leaf tag-1 {
               when 'not(../pop)';
               type dot1q-types:vlanid;
               description
                 "A first tag to be used for push or translate
                  operations. This tag will be used as the outermost tag
                  as a result of the tag operation.";
             }
             leaf tag-1-type {
               type dot1q-types:dot1q-tag-type;
               default "dot1q-types:s-vlan";
               description
                 "Specifies a specific 802.1Q tag type of tag-1.";
             }
             leaf tag-2 {
               when '(../translate)';
               type dot1q-types:vlanid;
               description
                 "A second tag to be used for translation.";
             }
             leaf tag-2-type {
               type dot1q-types:dot1q-tag-type;
               default "dot1q-types:c-vlan";
               description
                 "Specifies a specific 802.1Q tag type of tag-2.";
             }
==

Thank you. 

> Regards,
> Moti
> -----Original Message-----
> From: OPSAWG <[e-mail]> On Behalf Of
> [e-mail]
> Sent: Wednesday, March 1, 2023 5:13 PM
> To: [e-mail]
> Cc: [e-mail]
> Subject: [EXTERNAL] [OPSAWG] SAPs and Attachment Circuits
> Provisioning (was TR: I-D Action: draft-boro-opsawg-ntw-
> attachment-circuit-01.txt)
> 
> Hi all,
> 
> Now that the base SAP spec is stable, we started exploring an
> augmentation that exposes the set of attachment circuits that are
> terminated by the SAP.
> 
> This network model is designed to ease the correlation between
> "Attachment Circuit-as-a-Service" request and the actual network
> provisioning. The model is also designed to accommodate various
> deployment schemes (a CE that maintains or multiple ACs with the
> same or distinct PEs, same AC terminated on the multiple SAPs,
> same AC terminated by more than one AC, etc.).
> 
> Please review and share comments. If you have an AC deployment
> case which is not covered by the proposed structure, please share
> it and let's discuss to see how to cover it. Thanks.
> 
> Cheers,
> Med
> 
> -----Message d'origine-----
> De : I-D-Announce <[e-mail]> De la part de
> [e-mail] Envoyé : mercredi 1 mars 2023 15:37 À :
> [e-mail] Objet : I-D Action: draft-boro-opsawg-ntw-
> attachment-circuit-01.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
> 
>         Title           : A Network YANG Data Model for Attachment
> Circuits
>         Authors         : Mohamed Boucadair
>                           Richard Roberts
>                           Oscar Gonzalez de Dios
>                           Samier Barguil Giraldo
>                           Bo Wu
>   Filename        : draft-boro-opsawg-ntw-attachment-circuit-
> 01.txt
>   Pages           : 75
>   Date            : 2023-03-01
> 
> Abstract:
>    This document specifies a network model for attachment
> circuits.  The
>    model can be used for the provisioning of attachment circuits
> prior
>    or during service provisioning (e.g., Network Slice Service).
> A
>    companion service model is specified in
>    [I-D.boro-opsawg-teas-attachment-circuit].
> 
>    The module augments the Service Attachment Point (SAP) model
> with the
>    detailed information for the provisioning of attachment
> circuits in
>    Provider Edges (PEs).
> 
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://clicktime.symantec.com/15t5jY75kXFiwoTTdLTdy?h=QEhrkbWUEsE
> M2oU5iK3WjBmJREvD2gKenIYlHFuMYeI=&u=https://clicktime.symantec.com
> /15t5jY75kbAy4u33ipvus?h=VnjAiocyXlKe_NJEavs_33UqH02HXl_KmiV31AEgZ
> Y8=&u=https://datatracker.ietf.org/doc/draft-boro-opsawg-ntw-
> attachment-circuit/
> 
> There is also an HTML version available at:
> https://clicktime.symantec.com/15t5pNJND8wKMkHPAtrnb?h=szl-
> OrcouWaUsAKFxRw4zoOH5NZxttx73q7TFDWFpJ0=&u=https://clicktime.syman
> tec.com/15t5pNJNDCrZUqryGPL4V?h=p1csu8q40grKPrDPX2pkHhaNZTz8BH-
> rLZemLB5ZDEg=&u=https://www.ietf.org/archive/id/draft-boro-opsawg-
> ntw-attachment-circuit-01.html
> 
> A diff from the previous version is available at:
> https://clicktime.symantec.com/15t5ehuoHua8XrdY5n4VM?h=wrIlzQ_Omyg
> 7M6uxNwR4r-
> cV39983q0j7BCDh3qiFVM=&u=https://clicktime.symantec.com/15t5ehuoHy
> VNexD8BGXmF?h=raz4QI_1SBC040migEE02bQrIeRa06ufOFEGDqNtiYQ=&u=https
> ://author-tools.ietf.org/iddiff?url2%253Ddraft-boro-opsawg-ntw-
> attachment-circuit-01
> 
> 
> Internet-Drafts are also available by rsync at
> rsync.ietf.org::internet-drafts
> 
> 
> _______________________________________________
> I-D-Announce mailing list
> [e-mail]
> https://clicktime.symantec.com/15t5uCVefkcumh7JiTFwD?h=J25hFzOG4z8
> hdqqYnIk6K9f8zT9TWxJBzkCvvuyMvnU=&u=https://clicktime.symantec.com
> /15t5uCVefpY9tngtowjD7?h=piClPOzV8NcUniRkHa5Qf-
> qGkaJKbozQKYkCzm03wQQ=&u=https://www.ietf.org/mailman/listinfo/i-
> d-announce
> Internet-Draft directories:
> https://clicktime.symantec.com/15t5ZsiWqHtY7uocYDfLj?h=e80hT1-
> zxhpqcb4gH9mQ_GZggwrDDrr7svWwifVoehM=&u=https://clicktime.symantec
> .com/15t5ZsiWqMonF1PCdi8cd?h=TJpqt3ZSiRSaDoXtP2Zj70JOMUrfdUs8xb_62
> hoT_Gk=&u=http://www.ietf.org/shadow.html or
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> __________________________________________________________________
> _______________________________________________________
> 
> 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
> [e-mail]
> https://clicktime.symantec.com/15t5z2gw8NJWBdwEG1f5q?h=uNiWkWNeLrN
> 4nq2JB6kwT525Y4bBPDp0a7i-
> 3dwOCnE=&u=https://clicktime.symantec.com/15t5z2gw8SDkJjWpMW8Mj?h=
> 5pw4WTDw4TWOH5fD8n5Hb41ZlPdMfRQFI1tvhjGMZiM=&u=https://www.ietf.or
> g/mailman/listinfo/opsawg
> 
> Notice: This e-mail together with any attachments may contain
> information of Ribbon Communications Inc. and its Affiliates that
> is confidential and/or proprietary for the sole use of the
> intended recipient. Any review, disclosure, reliance or
> distribution by others or forwarding without express permission is
> strictly prohibited. If you are not the intended recipient, please
> notify the sender immediately and then delete all copies,
> including any attachments.

_________________________________________________________________________________________________________________________

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.