date:20240209

Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg-incident-management-04

2024-02-09 Thread Wei Wang

Hi all,


     I support the adoption of this draft.


Best Regards,
Wei



---Original---
From: "Henk Birkholz"https://www.ietf.org/archive/id/draft-feng-opsawg-incident-management-04.html

ending on Thursday, February 22nd.

As a reminder, this I-D specifies a YANG Module for Incident Management. 
Incidents in this context are scoped to unexpected yet quantifiable 
adverse effects detected in a network service. The majority of the 
document provides background and motivation for the structure of the 
YANG Module that is in support of reporting, diagnosing, and mitigating 
the detected adverse effects.

The chairs acknowledge some positive feedback on the list and a positive 
poll result at IETF118. We would like to gather feedback from the WG if 
there is interest to further contribute and review.

Please reply with your support and especially any substantive comments 
you may have.


For the OPSAWG co-chairs,

Henk

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

Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg-incident-management-04

2024-02-09 Thread chong feng

Hi,
As an author, I support this adoption.

Henk Birkholz  于 2024年2月9日周五 上午4:44写道：

> Dear OPSAWG members,
>
> this email starts a call for Working Group Adoption of
>
> >
> https://www.ietf.org/archive/id/draft-feng-opsawg-incident-management-04.html
>
> ending on Thursday, February 22nd.
>
> As a reminder, this I-D specifies a YANG Module for Incident Management.
> Incidents in this context are scoped to unexpected yet quantifiable
> adverse effects detected in a network service. The majority of the
> document provides background and motivation for the structure of the
> YANG Module that is in support of reporting, diagnosing, and mitigating
> the detected adverse effects.
>
> The chairs acknowledge some positive feedback on the list and a positive
> poll result at IETF118. We would like to gather feedback from the WG if
> there is interest to further contribute and review.
>
> Please reply with your support and especially any substantive comments
> you may have.
>
>
> For the OPSAWG co-chairs,
>
> Henk
>
> ___
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

Re: [OPSAWG] 🔔 IPR Call for draft-feng-opsawg-incident-management-04

2024-02-09 Thread LUIS MIGUEL CONTRERAS MURILLO

Dear chairs,

No, I am not aware of any IPR related to this work.

Thanks

Best regards

Luis

-Mensaje original-
De: Henk Birkholz 
Enviado el: jueves, 8 de febrero de 2024 17:00
Para: OPSAWG ; draft-feng-opsawg-incident-managem...@ietf.org
Asunto: 🔔 IPR Call for draft-feng-opsawg-incident-management-04

Dear authors and contributors,

as a part of the adoption process, the chairs would also like to issue a first 
IPR call on the content of adoption candidates (there will also be a second IPR 
call after successful WGLC).

Please respond on-list as to whether or not you are aware of any IPR that 
pertains to draft-feng-opsawg-incident-management-04.

If you are aware of IPR, please also indicate whether or not this has been 
disclosed per IETF IPR rules (see RFCs 3669, 5378, and 8179).


For the OPAWG co-chairs,

Henk



Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede 
contener información privilegiada o confidencial y es para uso exclusivo de la 
persona o entidad de destino. Si no es usted. el destinatario indicado, queda 
notificado de que la lectura, utilización, divulgación y/o copia sin 
autorización puede estar prohibida en virtud de la legislación vigente. Si ha 
recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente 
por esta misma vía y proceda a su destrucción.

The information contained in this transmission is confidential and privileged 
information intended only for the use of the individual or entity named above. 
If the reader of this message is not the intended recipient, you are hereby 
notified that any dissemination, distribution or copying of this communication 
is strictly prohibited. If you have received this transmission in error, do not 
read it. Please immediately reply to the sender that you have received this 
communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode 
conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa 
ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica 
notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização 
pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem 
por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e 
proceda a sua destruição
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

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

2024-02-09 Thread mohamed . boucadair

Hi all, 

The main changes in this version are as follows: 

* Support of lag (bearer, level)
* Child bearers can be listed under a parent bearer (as read-only)
* A parent AC can list its child as read-only 
* bfd profile can be called at the routing level, not only centralized at the 
OAM level
* Add a new example

We are planning to add some other few examples to illustrate the use of the 
model. We hope to finalize those soon.

Please review and share your comments.

Cheers,
Med

> -Message d'origine-
> De : I-D-Announce  De la part de
> internet-dra...@ietf.org
> Envoyé : vendredi 9 février 2024 15:23
> À : i-d-annou...@ietf.org
> Cc : opsawg@ietf.org
> Objet : I-D Action: draft-ietf-opsawg-teas-attachment-circuit-06.txt
> 
> Internet-Draft draft-ietf-opsawg-teas-attachment-circuit-06.txt is now
> available. It is a work item of the Operations and Management Area
> Working Group (OPSAWG) WG of the IETF.
> 
>Title:   YANG Data Models for Bearers and 'Attachment Circuits'-as-
> a-Service (ACaaS)
>Authors: Mohamed Boucadair
> Richard Roberts
> Oscar Gonzalez de Dios
> Samier Barguil Giraldo
> Bo Wu
>Name:draft-ietf-opsawg-teas-attachment-circuit-06.txt
>Pages:   109
>Dates:   2024-02-09
> 
> Abstract:
> 
>This document specifies a YANG service data model for Attachment
>Circuits (ACs).  This model can be used for the provisioning of ACs
>before or during service provisioning (e.g., Network Slice
> Service).
>The document also specifies a service model for managing bearers
> over
>which ACs are established.
> 
>Also, the document specifies a set of reusable groupings.  Whether
>other service models reuse structures defined in the AC models or
>simply include an AC reference is a design choice of these service
>models.  Utilizing the AC service model to manage ACs over which a
>service is delivered has the advantage of decoupling service
>management from upgrading AC components to incorporate recent AC
>technologies or features.
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdata
> tracker.ietf.org%2Fdoc%2Fdraft-ietf-opsawg-teas-attachment-
> circuit%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C70d86eeb88e
> 041aa069e08dc297a9cc2%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638
> 430853790873527%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2
> luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=3xH43Nyh5%2FuS
> HzONkrWwbxb8qZBNp1TDYtQG9dcv8Yk%3D&reserved=0
> 
> There is also an HTML version available at:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> ietf.org%2Farchive%2Fid%2Fdraft-ietf-opsawg-teas-attachment-circuit-
> 06.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C70d86eeb88e041
> aa069e08dc297a9cc2%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638430
> 853790883602%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luM
> zIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=fxNyW0J6SQzZ26%2F
> xQdnmYH5OTUedwpdF3pUjb33xfsc%3D&reserved=0
> 
> A diff from the previous version is available at:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fauth
> or-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-opsawg-teas-attachment-
> circuit-
> 06&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C70d86eeb88e041aa069
> e08dc297a9cc2%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C63843085379
> 0891263%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLC
> JBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=0U36O2amtinHwKmr%2BkbQ
> cBdr4p1nDB7xlE4aLfDEMko%3D&reserved=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
https://www.ietf.org/mailman/listinfo/opsawg

[OPSAWG] I-D Action: draft-ietf-opsawg-teas-attachment-circuit-06.txt

2024-02-09 Thread internet-drafts

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

   Title:   YANG Data Models for Bearers and 'Attachment Circuits'-as-a-Service 
(ACaaS)
   Authors: Mohamed Boucadair
Richard Roberts
Oscar Gonzalez de Dios
Samier Barguil Giraldo
Bo Wu
   Name:draft-ietf-opsawg-teas-attachment-circuit-06.txt
   Pages:   109
   Dates:   2024-02-09

Abstract:

   This document specifies a YANG service data model for Attachment
   Circuits (ACs).  This model can be used for the provisioning of ACs
   before or during service provisioning (e.g., Network Slice Service).
   The document also specifies a service model for managing bearers over
   which ACs are established.

   Also, the document specifies a set of reusable groupings.  Whether
   other service models reuse structures defined in the AC models or
   simply include an AC reference is a design choice of these service
   models.  Utilizing the AC service model to manage ACs over which a
   service is delivered has the advantage of decoupling service
   management from upgrading AC components to incorporate recent AC
   technologies or features.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-teas-attachment-circuit/

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

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

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

Re: [OPSAWG] 答复: 🔔 IPR Call for draft-feng-opsawg-incident-management-04

2024-02-09 Thread chong feng

Hi Chairs:
I am not aware of any IPR related to this work.

yuchaode  于 2024年2月10日周六 上午12:32写道：

> Hi Chairs:
> I am not aware of any IPR related to this work.
>
> -邮件原件-
> 发件人: Henk Birkholz [mailto:henk.birkholz@ietf.contact]
> 发送时间: 2024年2月9日 0:00
> 收件人: OPSAWG ;
> draft-feng-opsawg-incident-managem...@ietf.org
> 主题: 🔔 IPR Call for draft-feng-opsawg-incident-management-04
>
> Dear authors and contributors,
>
> as a part of the adoption process, the chairs would also like to issue a
> first IPR call on the content of adoption candidates (there will also be a
> second IPR call after successful WGLC).
>
> Please respond on-list as to whether or not you are aware of any IPR that
> pertains to draft-feng-opsawg-incident-management-04.
>
> If you are aware of IPR, please also indicate whether or not this has been
> disclosed per IETF IPR rules (see RFCs 3669, 5378, and 8179).
>
>
> For the OPAWG co-chairs,
>
> Henk
> ___
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

Re: [OPSAWG] I-D Action: draft-ietf-opsawg-teas-common-ac-05.txt

2024-02-09 Thread mohamed . boucadair

Hi all, 

The main change in -05 is adding a new identity for BGP capabilities, which we 
need at the network level in particular. 

We don't have any open issue of this spec.

Cheers,
Med

> -Message d'origine-
> De : OPSAWG  De la part de internet-
> dra...@ietf.org
> Envoyé : vendredi 9 février 2024 13:32
> À : i-d-annou...@ietf.org
> Cc : opsawg@ietf.org
> Objet : [OPSAWG] I-D Action: draft-ietf-opsawg-teas-common-ac-05.txt
> 
> Internet-Draft draft-ietf-opsawg-teas-common-ac-05.txt is now
> available. It is a work item of the Operations and Management Area
> Working Group (OPSAWG) WG of the IETF.
> 
>Title:   A Common YANG Data Model for Attachment Circuits
>Authors: Mohamed Boucadair
> Richard Roberts
> Oscar Gonzalez de Dios
> Samier Barguil Giraldo
> Bo Wu
>Name:draft-ietf-opsawg-teas-common-ac-05.txt
>Pages:   53
>Dates:   2024-02-09
> 
> Abstract:
> 
>The document specifies a common Attachment Circuits (ACs) YANG
>module, which is designed with the intent to be reusable by other
>models.  For example, this common model can be reused by service
>models to expose ACs as a service, service models that require
>binding a service to a set of ACs, network and device models to
>provision ACs, etc.
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdata
> tracker.ietf.org%2Fdoc%2Fdraft-ietf-opsawg-teas-common-
> ac%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Cdbbd71c3ee7640c7
> 091008dc296b1224%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C63843078
> 7049955855%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzI
> iLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=UfYHciXlSb7vqip7fka
> pU%2F0SGfPGvdUrxyA1VsCGd9M%3D&reserved=0
> 
> There is also an HTML version available at:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> ietf.org%2Farchive%2Fid%2Fdraft-ietf-opsawg-teas-common-ac-
> 05.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Cdbbd71c3ee7640
> c7091008dc296b1224%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638430
> 787049965108%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luM
> zIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=LBTNtig6sNFBNnFVa
> XoXixiNUjTgV%2BK8N1a2ijC1JMw%3D&reserved=0
> 
> A diff from the previous version is available at:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fauth
> or-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-opsawg-teas-common-ac-
> 05&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Cdbbd71c3ee7640c7091
> 008dc296b1224%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C63843078704
> 9971600%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLC
> JBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=PkY874LogJ0sYpu9hry4UD
> 5EzeX1CkJOrkJMdgR6cvI%3D&reserved=0
> 
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
> 
> 
> ___
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> ietf.org%2Fmailman%2Flistinfo%2Fopsawg&data=05%7C02%7Cmohamed.boucadai
> r%40orange.com%7Cdbbd71c3ee7640c7091008dc296b1224%7C90c7a20af34b40bfbc
> 48b9253b6f5d20%7C0%7C0%7C638430787049976425%7CUnknown%7CTWFpbGZsb3d8ey
> JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7
> C%7C%7C&sdata=ZbNOAJuSlLTvqbd9m7Pr84wz7SyE0pVKJDtDcDUEthA%3D&reserved=
> 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
https://www.ietf.org/mailman/listinfo/opsawg

Re: [OPSAWG] Yangdoctors early review of draft-ietf-opsawg-ntw-attachment-circuit-04

2024-02-09 Thread mohamed . boucadair

Hi all, 

FWIW, the proposed changes are now implemented in the published version: 
https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-ntw-attachment-circuit-05.

Cheers,
Med

> -Message d'origine-
> De : BOUCADAIR Mohamed INNOV/NET
> Envoyé : jeudi 25 janvier 2024 13:46
> À : 'Martin Björklund' ; yang-doct...@ietf.org
> Cc : draft-ietf-opsawg-ntw-attachment-circuit@ietf.org;
> opsawg@ietf.org
> Objet : RE: Yangdoctors early review of draft-ietf-opsawg-ntw-
> attachment-circuit-04
> 
> Hi Martin,
> 
> Thanks for the review.
> 
> Please see inline.
> 
> Cheers,
> Med
> 
> > -Message d'origine-
> > De : Martin Björklund via Datatracker  Envoyé :
> > mercredi 24 janvier 2024 16:20 À : yang-doct...@ietf.org Cc :
> > draft-ietf-opsawg-ntw-attachment-circuit@ietf.org;
> > opsawg@ietf.org
> > Objet : Yangdoctors early review of draft-ietf-opsawg-ntw-
> attachment-
> > circuit-04
> >
> > Reviewer: Martin Björklund
> > Review result: Ready with Issues
> >
> > Here is my YANG doctor's review of draft-ietf-opsawg-ntw-attachment-
> > circuit-04.
> >
> > o  There are several typedefs defined on the form:
> >
> >   typedef attachment-circuit-reference {
> > type leafref {
> >   path "/nw:networks/nw:network/nw:node/ac-ntw:ac/ac-ntw:name";
> > }
> >
> >   Note that this path spans three lists (network, node, ac).  Unless
> >   it is guaranteed that the `ac-ntw:ame` value is unique within all
> >   networks and all nodes, this typedef won't work (or rather, it may
> >   refer to more than one ac).
> >
> 
> [Med] Good catch. We don't have that constraint on the "ac-ntw:name".
> Please see the candidate changes to fix this at: https://author-
> tools.ietf.org/api/iddiff?url_1=https://boucadair.github.io/attachment
> -circuit-model/draft-ietf-opsawg-ntw-attachment-
> circuit.txt&url_2=https://boucadair.github.io/attachment-circuit-
> model/boucadair-patch-5/draft-ietf-opsawg-ntw-attachment-circuit.txt.
> The use of groupings for references is consistent with the approach in
> RFC 8345.
> 
> >
> > o typedef ac-profile-reference {
> > type leafref {
> >   path "/nw:networks/nw:network/ac-profile/name";
> > }
> >
> >   The nodes should have prefixes:
> >
> >   path "/nw:networks/nw:network/ac-ntw:ac-profile/ac-ntw:name";
> >
> 
> [Med] Fixed.
> 
> >
> > o   leaf site-of-origin {
> >   when "../address-family = 'vpn-common:ipv4' "
> >  + "or 'vpn-common:dual-stack'" {
> >
> > leaf ipv6-site-of-origin {
> >   when "../address-family = 'vpn-common:ipv6' "
> >  + "or 'vpn-common:dual-stack'" {
> >
> >
> >Use 'derived-from-or-self' instead of comparison.
> >
> 
> [Med] Agree. Fixed.
> 
> >
> > o  Some lists have plural-names: routing-profiles, ipv4-lan-
> prefixes,
> >ipv6-lan-prefixes.  Usually lists should have singular names.
> >
> 
> [Med] Fixed.
> 
> > o typedef encryption-profile-reference {
> > ...
> > description
> >   "Defines a type to an encryption profile for referencing
> >purposes.";
> >   }
> >
> >   Perhaps "Defines a reference to an encryption profile"?
> >
> >   (Same for 4 more typedefs)
> >
> >
> 
> [Med] Works for me. Thanks.
> 
> >
> > /martin
> >


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

Re: [OPSAWG] Yangdoctors early review of draft-ietf-opsawg-ac-lxsm-lxnm-glue-04

2024-02-09 Thread mohamed . boucadair

Hi Martin, all, 

FWIW, the proposed changes are now implemented in the public version: 
https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-ac-lxsm-lxnm-glue-06.

Cheers,
Med 

> -Message d'origine-
> De : BOUCADAIR Mohamed INNOV/NET
> Envoyé : jeudi 25 janvier 2024 13:56
> À : 'Martin Björklund' 
> Cc : yang-doct...@ietf.org; draft-ietf-opsawg-ac-lxsm-lxnm-
> glue@ietf.org; opsawg@ietf.org
> Objet : RE: Yangdoctors early review of draft-ietf-opsawg-ac-lxsm-
> lxnm-glue-04
> 
> Hi Martin,
> 
> Thank you for the follow-up.
> 
> Fixed the nits in the yang file. Also updated the module to make use
> of the new groupings for referencing purposes instead of the broken
> typedefs in the ac-ntw:
> 
> https://author-tools.ietf.org/api/iddiff?iddiff?doc_1=draft-ietf-
> opsawg-ac-lxsm-lxnm-glue&url_2=https://boucadair.github.io/attachment-
> circuit-model/boucadair-patch-5/draft-ietf-opsawg-ac-lxsm-lxnm-
> glue.txt
> 
> Cheers,
> Med
> 
> > -Message d'origine-
> > De : Martin Björklund  Envoyé : mercredi 24
> janvier
> > 2024 16:52 À : BOUCADAIR Mohamed INNOV/NET
> >  Cc : yang-doct...@ietf.org;
> > draft-ietf-opsawg-ac-lxsm-lxnm- glue@ietf.org; opsawg@ietf.org
> > Objet : Re: Yangdoctors early review of draft-ietf-opsawg-ac-lxsm-
> > lxnm-glue-04
> >
> > mohamed.boucad...@orange.com wrote:
> > > Hi Martin,
> > >
> > > Thanks for the review.
> > >
> > > FWIW, a new version that fixes the nit you reported and other
> minor
> > pending we had is available online:
> > >
> >
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fauth
> > > or-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-opsawg-ac-lxsm-
> lxnm-
> > glu
> > > e-
> > 05&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C46a62fe529bd44020
> > >
> >
> 91308dc1cf473e7%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638417083
> > >
> >
> 964251050%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIi
> > >
> >
> LCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C41000%7C%7C%7C&sdata=ZWGtBagO6Z2BiYEH
> > > xG8yqYJwwzj72LPLDoUVEKRHM2U%3D&reserved=0
> >
> > That was quick!  However, the spelling error is still there, and I
> > think you introduced a new one ;-)
> >
> >
> > was provisionned using the ACaaS module.";
> > 
> >
> > Thansk to Martin Björklund for the yangdoctors review.
> > ^^
> >
> >
> >
> > /martin
> >
> >
> >
> >
> >
> >
> > >
> > > Cheers,
> > > Med
> > >
> > > > -Message d'origine-
> > > > De : Martin Björklund via Datatracker 
> Envoyé :
> > > > mercredi 24 janvier 2024 16:18 À : yang-doct...@ietf.org Cc :
> > > > draft-ietf-opsawg-ac-lxsm-lxnm-glue@ietf.org;
> opsawg@ietf.org
> > > > Objet : Yangdoctors early review of draft-ietf-opsawg-ac-lxsm-
> > lxnm-
> > > > glue-04
> > > >
> > > > Reviewer: Martin Björklund
> > > > Review result: Ready with Nits
> > > >
> > > > This is a very short, and from a YANG-perspective simple,
> module.
> > It
> > > > looks good, and I also found one nit:
> s/provisionned/provisioned/g
> > > >
> > > > /martin
> > > >
> > >
> > >
> >
> __
> > > __
> > > 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

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

2024-02-09 Thread internet-drafts

Internet-Draft draft-ietf-opsawg-ac-lxsm-lxnm-glue-06.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-06.txt
   Pages:   28
   Dates:   2024-02-09

Abstract:

   The document specifies a module that updates existing service and
   network Virtual Private 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-06.html

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

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-05.txt

2024-02-09 Thread internet-drafts

Internet-Draft draft-ietf-opsawg-ntw-attachment-circuit-05.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-05.txt
   Pages:   102
   Dates:   2024-02-09

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-05.html

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

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-teas-common-ac-05.txt

2024-02-09 Thread internet-drafts

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

   Title:   A Common YANG Data Model for Attachment Circuits
   Authors: Mohamed Boucadair
Richard Roberts
Oscar Gonzalez de Dios
Samier Barguil Giraldo
Bo Wu
   Name:draft-ietf-opsawg-teas-common-ac-05.txt
   Pages:   53
   Dates:   2024-02-09

Abstract:

   The document specifies a common Attachment Circuits (ACs) YANG
   module, which is designed with the intent to be reusable by other
   models.  For example, this common model can be reused by service
   models to expose ACs as a service, service models that require
   binding a service to a set of ACs, network and device models to
   provision ACs, etc.

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

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-opsawg-teas-common-ac-05.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-opsawg-teas-common-ac-05

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] 答复: 🔔 IPR Call for draft-feng-opsawg-incident-management-04

2024-02-09 Thread yuchaode

Hi Chairs: 
I am not aware of any IPR related to this work.

-邮件原件-
发件人: Henk Birkholz [mailto:henk.birkholz@ietf.contact] 
发送时间: 2024年2月9日 0:00
收件人: OPSAWG ; draft-feng-opsawg-incident-managem...@ietf.org
主题: 🔔 IPR Call for draft-feng-opsawg-incident-management-04

Dear authors and contributors,

as a part of the adoption process, the chairs would also like to issue a first 
IPR call on the content of adoption candidates (there will also be a second IPR 
call after successful WGLC).

Please respond on-list as to whether or not you are aware of any IPR that 
pertains to draft-feng-opsawg-incident-management-04.

If you are aware of IPR, please also indicate whether or not this has been 
disclosed per IETF IPR rules (see RFCs 3669, 5378, and 8179).


For the OPAWG co-chairs,

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

Re: [OPSAWG] [radext] [Technical Errata Reported] RFC2865 (6915)

2024-02-09 Thread Rob Wilton (rwilton)

Hi Alan,

Thanks for your help.  I’ve marked this as HFDU.

Regards,
Rob

From: radext  on behalf of Alan DeKok 

Date: Monday, 15 January 2024 at 14:20
To: Rob Wilton (rwilton) 
Cc: RFC Errata System , war...@kumari.net 
, opsawg@ietf.org , rad...@ietf.org 
, Paul Wouters 
Subject: Re: [radext] [OPSAWG] [Technical Errata Reported] RFC2865 (6915)
On Jan 15, 2024, at 7:14 AM, Rob Wilton (rwilton) 
 wrote:
> Hi RFC 2865 authors, OPSAWG,

  I've CC'd RADEXT, as that WG is currently active.  I've also removed the 2865 
authors email addresses.  I believe those became inactive decades ago.

> I think that this errata may be valid, but given the age of the RADIUS 
> protocol, and the fact that I'm not familiar with it and this is a change to 
> the protocol, then I'm somewhat concerned with verifying this errata, and 
> hence I propose to move it to "Held for Document Update".
>
> Does anyone have any comments on this proposed resolution?

  I think "hold for document update" is best.

  We've covered these issues in RFC 8044, which defines data types for RADIUS 
(octets, printable text, IPs, integers, etc).  There are no data types which 
permit zero-length values.

  The variable-length data types defined in Section 3.4 (printable strings) and 
3.5 (binary data) both say:

  Strings of length zero (0) MUST NOT be sent; omit the entire attribute 
instead.

 There is no _general_ prohibition on attributes having zero length values.  
But it is not currently permitted to define an attribute which has a 
zero-length value.

  As such, "hold for document update" is the reasonable conclusion.

   Alan DeKok.

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

Re: [OPSAWG] 🔔 IPR Call for draft-feng-opsawg-incident-management-04

2024-02-09 Thread Qin Wu

Hi Chairs:
I am not aware of any IPR related to this work.



吴钦 Wu Qin
Mobile：+86-13914734360(Mobile Number)
Email：bill...@huawei.com

发件人： Henk 
Birkholzmailto:henk.birkholz@ietf.contact>>
收件人： 
OPSAWGmailto:opsawg@ietf.org>>;draft-feng-opsawg-incident-managementmailto:draft-feng-opsawg-incident-managem...@ietf.org>>
主题： 🔔 IPR Call for draft-feng-opsawg-incident-management-04
时间： 2024-02-09 00:01:19

Dear authors and contributors,

as a part of the adoption process, the chairs would also like to issue a
first IPR call on the content of adoption candidates (there will also be
a second IPR call after successful WGLC).

Please respond on-list as to whether or not you are aware of any IPR
that pertains to draft-feng-opsawg-incident-management-04.

If you are aware of IPR, please also indicate whether or not this has
been disclosed per IETF IPR rules (see RFCs 3669, 5378, and 8179).


For the OPAWG co-chairs,

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

Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg-incident-management-04

Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg-incident-management-04

Re: [OPSAWG] 🔔 IPR Call for draft-feng-opsawg-incident-management-04

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

[OPSAWG] I-D Action: draft-ietf-opsawg-teas-attachment-circuit-06.txt

Re: [OPSAWG] 答复: 🔔 IPR Call for draft-feng-opsawg-incident-management-04

Re: [OPSAWG] I-D Action: draft-ietf-opsawg-teas-common-ac-05.txt

Re: [OPSAWG] Yangdoctors early review of draft-ietf-opsawg-ntw-attachment-circuit-04

Re: [OPSAWG] Yangdoctors early review of draft-ietf-opsawg-ac-lxsm-lxnm-glue-04

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

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

[OPSAWG] I-D Action: draft-ietf-opsawg-teas-common-ac-05.txt

[OPSAWG] 答复: 🔔 IPR Call for draft-feng-opsawg-incident-management-04

Re: [OPSAWG] [radext] [Technical Errata Reported] RFC2865 (6915)

Re: [OPSAWG] 🔔 IPR Call for draft-feng-opsawg-incident-management-04

15 matches

Site Navigation

Mail list logo

Footer information