Re, Thanks Joe for sharing your thoughts.
A new entry appears now in -06: https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-sap-06 Cheers, Med > -----Message d'origine----- > De : Joe Clarke (jclarke) <jcla...@cisco.com> > Envoyé : mercredi 18 mai 2022 16:47 > À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com> > Cc : opsawg@ietf.org > Objet : Re: [OPSAWG] WG LC: draft-ietf-opsawg-sap > > On 5/18/22 09:50, mohamed.boucad...@orange.com wrote: > > Hi Joe, > > > > FWIW, rfc4026#section-6.1 defines AC as follows: > > > > == > > 6.1. Attachment Circuit (AC) > > > > In a Layer 2 VPN the CE is attached to PE via an Attachment > Circuit > > (AC). The AC may be a physical or logical link. > > == > > > > which we can generalize as: > > > > == > > 6.1. Attachment Circuit (AC) > > > > The CE is attached to PE via an Attachment Circuit > > (AC). The AC may be a physical or logical link. > > == > > > > We don't have an entry for AC because we thought that the > meaning is already conveyed in the CE/PE entries: > > > > == > > Customer Edge (CE): An equipment that is dedicated to a > particular > > customer and is directly connected to one or more Provider > Edges > > (PEs) via attachment circuits (ACs)... > > > > Provider Edge (PE): An equipment owned and managed by the > service > > provider that can support multiple services (e.g., VPNs) > for > > different customers. A PE is directly connected to one or > more > > CEs via ACs. > > == > > > > Please let us know if you still prefer having the entry added. > Thanks. > > It was this above I was "spot-reading" to see how you had changed > the text to clarify SAP. When I saw "AC" I had expected to see it > called out in terminology like PE is. I did find it as you show, > but I still thought it, being referenced in other places like > PE/CE, and in 6.1 would necessitate a separate terminology entry. > > Joe _________________________________________________________________________________________________________________________ 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
