Re: [OPSAWG] [mpls] IOAM, iOAM, and oOAM abbreviations

[Italo Busi]

Loa, Greg,

I am not sure we really need abbreviations for in-band and out-of-band OAM 
since we have lived without these abbreviations for quite a long time. However, 
it does not harm to define those acronyms

While OOB is quite commonly used as an abbreviation for out-of-band, I do not 
recall to have ever seen an abbreviation for in-band ☹

My suggestion would be to use IB for in-band to have a consistent rule with the 
OOB acronym (i.e. ib-OAM and oob-OAM)

My 2 cents

Italo

From: Greg Mirsky 
Sent: mercoledì 13 dicembre 2023 04:13
To: DetNet WG ; mpls ; 6man WG ; 
IETF IPPM WG ; opsawg ; Pascal Thubert 
; Loa Andersson 
Subject: [mpls] IOAM, iOAM, and oOAM abbreviations

Dear All,
Loa and I have discussed these abbreviations to help us find a solution that 
avoids the confusion we found when we came across them. Firstly, what they 
stand for:

  *   IOAM - In-situ OAM (RFC 9197)
  *   iOAM - in-band OAM (RAW 
architecture)
  *   oOAM - out-of-band OAM (RAW 
architecture)
We discussed the issue with Pascal and came to slightly different abbreviations 
for the last two:

  *   inb-OAM
  *   oob-OAM
We also discord these abbreviations with the RFC Editor. Resulting from that, 
RFC Editor agreed to add IOAM to the RFC Editor Abbreviation 
List. The other two 
abbreviations cannot be added at this time. If that is needed, we can ask the 
RFC Editor to add them once the respective RFC is published.
We are seeking your feedback on the following:

  *   Do you see the benefit of introducing two new abbreviations for in-band 
OAM and out-of-band OAM?
  *   Which set of abbreviations (iOAM/oOAM vs. inb-OAM/oob-OAM) do you prefer 
for being used in IETF?
  *   Or would you propose another set of abbreviations?
Regards,
Loa and Greg

___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

Re: [OPSAWG] I-D Action: draft-ietf-opsawg-ntw-attachment-circuit-04.txt

[mohamed . boucadair]

Hi all,

The main change in this version is to optimize how ACs are bound in a node. 
They used to be repeated under the SAP level but now ACs are upleveled to the 
node level with references at the SAP level. The rationale for this change is 
also to better decorrelate the ACs from services (as SAPs are indexed per 
service). ACs can thus be listed even if they are not bound yet to any service.

Cheers,
Med

> -Message d'origine-
> De : I-D-Announce  De la part de
> internet-dra...@ietf.org
> Envoyé : jeudi 14 décembre 2023 11:54
> À : i-d-annou...@ietf.org
> Cc : opsawg@ietf.org
> Objet : I-D Action: draft-ietf-opsawg-ntw-attachment-circuit-
> 04.txt
> 
> Internet-Draft draft-ietf-opsawg-ntw-attachment-circuit-04.txt is
> now available. It is a work item of the Operations and Management
> Area Working Group (OPSAWG) WG of the IETF.
> 
>Title:   A Network YANG Data Model for Attachment Circuits
>Authors: Mohamed Boucadair
> Richard Roberts
> Oscar Gonzalez de Dios
> Samier Barguil Giraldo
> Bo Wu
>Name:draft-ietf-opsawg-ntw-attachment-circuit-04.txt
>Pages:   97
>Dates:   2023-12-14
> 
> 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.ietf-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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
> Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-opsawg-ntw-attachment-
> circuit%2F=05%7C02%7Cmohamed.boucadair%40orange.com%7C0210ed
> 9da6ab4813048b08dbfc930927%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0
> %7C0%7C638381480666502712%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjA
> wMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%
> 7C=%2BeLj1W6LrRq2exSxoJ7aaLylc4YEauLoO2MXLc%2BcOiE%3D
> ved=0
> 
> There is also an HTML version available at:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
> Fwww.ietf.org%2Farchive%2Fid%2Fdraft-ietf-opsawg-ntw-attachment-
> circuit-
> 04.html=05%7C02%7Cmohamed.boucadair%40orange.com%7C0210ed9da
> 6ab4813048b08dbfc930927%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C
> 0%7C638381480666502712%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD
> AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&
> sdata=jfBDKH%2B83EH7KatcyaIrBWBxUof5Z0y13USaYaVxG6c%3D=0
> 
> A diff from the previous version is available at:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
> Fauthor-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-opsawg-ntw-
> attachment-circuit-
> 04=05%7C02%7Cmohamed.boucadair%40orange.com%7C0210ed9da6ab48
> 13048b08dbfc930927%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6
> 38381480666502712%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJ
> QIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C
> =Od2NiHem6mCOF0pfpAoDv8FPxOiLs2JNQebIsf%2Fpeeg%3D=0
> 
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
> 
> 
> ___
> I-D-Announce mailing list
> i-d-annou...@ietf.org
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
> Fwww.ietf.org%2Fmailman%2Flistinfo%2Fi-d-
> announce=05%7C02%7Cmohamed.boucadair%40orange.com%7C0210ed9d
> a6ab4813048b08dbfc930927%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7
> C0%7C638381480666502712%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwM
> DAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C
> =CEBeUOxYut2Le32g2WFUQ6OLlPuZ4cVY4QoLuU2mUI8%3D=0


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

[OPSAWG] I-D Action: draft-ietf-opsawg-ac-lxsm-lxnm-glue-04.txt

[internet-drafts]

Internet-Draft draft-ietf-opsawg-ac-lxsm-lxnm-glue-04.txt is now available. It
is a work item of the Operations and Management Area Working Group (OPSAWG) WG
of the IETF.

   Title:   A YANG Data Model for Augmenting VPN Service and Network Models 
with Attachment Circuits
   Authors: Mohamed Boucadair
Richard Roberts
Samier Barguil Giraldo
Oscar Gonzalez de Dios
   Name:draft-ietf-opsawg-ac-lxsm-lxnm-glue-04.txt
   Pages:   28
   Dates:   2023-12-14

Abstract:

   The document specifies a module that updates existing service and
   network VPN modules with the required information to bind specific
   services to ACs that are created using the Attachment Circuit (AC)
   service and network models.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-ac-lxsm-lxnm-glue/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-opsawg-ac-lxsm-lxnm-glue-04.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-opsawg-ac-lxsm-lxnm-glue-04

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

[OPSAWG] I-D Action: draft-ietf-opsawg-ntw-attachment-circuit-04.txt

[internet-drafts]

Internet-Draft draft-ietf-opsawg-ntw-attachment-circuit-04.txt is now
available. It is a work item of the Operations and Management Area Working
Group (OPSAWG) WG of the IETF.

   Title:   A Network YANG Data Model for Attachment Circuits
   Authors: Mohamed Boucadair
Richard Roberts
Oscar Gonzalez de Dios
Samier Barguil Giraldo
Bo Wu
   Name:draft-ietf-opsawg-ntw-attachment-circuit-04.txt
   Pages:   97
   Dates:   2023-12-14

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.ietf-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://datatracker.ietf.org/doc/draft-ietf-opsawg-ntw-attachment-circuit/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-opsawg-ntw-attachment-circuit-04.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-opsawg-ntw-attachment-circuit-04

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg