Re: [OPSAWG] WG Adoption Call for draft-dbwb-opsawg-sap-00

[liupeng...@outlook.com]

Hi WG,

I support the adoption.

Regards,
Peng Liu



liupeng...@outlook.com
 
From: Tianran Zhou
Date: 2022-01-05 10:12
To: opsawg@ietf.org
CC: opsawg-cha...@ietf.org
Subject: [OPSAWG] WG Adoption Call for draft-dbwb-opsawg-sap-00
Hi WG,
 
I assume most of you are back to work.
Hope you had a good holiday.
 
As a follow up action after IETF 111, this mail starts a working group adoption 
call for draft-dbwb-opsawg-sap-00.
https://datatracker.ietf.org/doc/draft-dbwb-opsawg-sap/
 
This document defines a YANG data model for representing an abstract view of 
the provider network topology containing the points from which its services can 
be attached (e.g., basic connectivity, VPN, network slices).
 
Please review and comment.
We will conclude this adoption call after two weeks.
 
Cheers,
Tianran
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

[OPSAWG] Iotdir early review of draft-ietf-opsawg-mud-iot-dns-considerations-02

[Dave Thaler via Datatracker]

Reviewer: Dave Thaler
Review result: On the Right Track

My detailed comments and in-line text suggestions can be found in the PDF file
at
https://www.microsoft.com/en-us/research/uploads/prod/2022/01/draft-ietf-opsawg-mud-iot-dns-considerations-02-DThalerReview.pdf

Some high level comments:
* While I think the document is on the right track and I agree it is good to do
this document, a number of the statements in the document are ones I disagree
with as phrased.  My belief is that the wording can be corrected and in many
instances I have proposed such changes in my reviewed copy. * Some of the
recommendations in the document are not sufficiently justified at present.  
They may still be the right recommendations, but it means that more work is
needed in the document to provide sufficient justification.  In my detailed
review I have called out a couple of counter examples which the document should
either address, or change the recommendations to accommodate, whatever the WG
can get consensus on. * A number of parts of the document still contain "todos"
(some marked with "XXX", some not), so will need another IoT-Directorate anyway
once it's complete. * The document needed an editorial English pass, which I
have done and provided a bunch of simple editorial suggestions in changed
tracked text. * There are several undefined terms in the document.  To broaden
readability since we want this to apply to IoT manufacturers with a wide
variety of backgrounds, technical expertise, and level of familiarity with the
English language, definitions or at least citations should be provided for such
terms unless they are removed.  I have called these out in the doc as well ("S3
bucket", "QuadX", "forced circuit proxy", etc.)


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

Re: [OPSAWG] WG Adoption Call for draft-dbwb-opsawg-sap-00

[Adrian Farrel]

Thanks Tianran,

 

I think that this is a good thing to be working on, and that this document
is a reasonable starting point.

 

I support adoption and promise to review the draft as it goes forward.

 

Adrian

 

From: OPSAWG  On Behalf Of Tianran Zhou
Sent: 05 January 2022 02:12
To: opsawg@ietf.org
Cc: opsawg-cha...@ietf.org
Subject: [OPSAWG] WG Adoption Call for draft-dbwb-opsawg-sap-00

 

Hi WG,

 

I assume most of you are back to work.

Hope you had a good holiday.

 

As a follow up action after IETF 111, this mail starts a working group
adoption call for draft-dbwb-opsawg-sap-00.

 
https://datatracker.ietf.org/doc/draft-dbwb-opsawg-sap/

 

This document defines a YANG data model for representing an abstract view of
the provider network topology containing the points from which its services
can be attached (e.g., basic connectivity, VPN, network slices).

 

Please review and comment.

We will conclude this adoption call after two weeks.

 

Cheers,

Tianran

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

Re: [OPSAWG] Shepherd write-up for draft-ietf-opsawg-l2nm

[Joe Clarke (jclarke)]

Happy new year!  Thank you, Adrian.  We appreciate this write-up as well
as your strong shepherding for all of these LxNM drafts.  I have
requested publication from the IESG.  This puts all of the LxNM docs in
the hopper.

Joe

On 12/29/21 07:46, Adrian Farrel wrote:
> Sorry for the delay: there was a lot of cross-checking to be done.
>
> The shepherd write-up is now posted and the chairs are free to continue the
> process.
>
> Best,
> Adrian
>
>


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

[OPSAWG] Publication has been requested for draft-ietf-opsawg-l2nm-12

[Joe Clarke via Datatracker]

Joe Clarke has requested publication of draft-ietf-opsawg-l2nm-12 as Proposed 
Standard on behalf of the OPSAWG working group.

Please verify the document's state at 
https://datatracker.ietf.org/doc/draft-ietf-opsawg-l2nm/


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

Re: [OPSAWG] WG Adoption Call for draft-dbwb-opsawg-sap-00

[Benoit Claise]

Hi,

I support the adoption.
This is a much needed functionality, required to provide a layered view 
of the network (the service layer in this case). I like the fact it's 
based on the I2RS topology model.


One clarification though.

From that standpoint, and considering the architecture
   depicted in Figure 1, the goal of this document is to provide a
   mechanism to show via a YANG-based interface an abstracted network
   view from the network controller to the service orchestration layer
   with a focus on where a service can be delivered to customers.

"can be delivered" or is delivered?

In this figure,

.---.
|CE2|
'-+-'
  |
 .---. .---. .---.  .---.   .-+-.
   +-|sap|-|sap|-|sap|-+  +-|sap|---|sap|-+
   | '---' '---' '---' |  | '---'   '---' |
  .---.  .---. |  |   |
  |CE1+--+sap|  PE1|  | PE2   |
  '---'  '---' |  |   |
   |   |  |   |
   +---+  +---+

   +---+  +---+
   |   |  |   |
   |   |  | .---.  .---.
   | PE3   |  |PE4  |sap+--+CE5|
   |   |  | '---'  '---'
   | .---. .---. .---. |  | .---. .---. .---. |
   +-|sap|-|sap|-|sap|-+  +-|sap|-|sap|-|sap|-+
 '---' '---' '-+-'  '---' '---' '---'
   ||
 .-+-..-+-.
 |CE3||CE4|
 '-+-''-+-'


1. Do we want to say that there are existing SAPs on PE routers, to 
which we can deploy new services?
2. Or do we want to say there is an existing service that connects CE2 
to a specific SAP on PE2?


1. implies that  we have to list all the potential SAP types that 
"could" be delivered. And I don't know yet which service type will be 
configured. So I potentially need the full list of the "service-type" 
derived identities

2. implies that only the existing configured SAP type needs to be documented

The figures and texts points to 1., but 2 would be useful to me.
So what's happening when a specific service type is configured on this 
CE2-facing SAP on PE2, the SAP-type goes a list to the unique configured 
SAP-type?
In other words, can I do a filter on my topology for all the L3VPN 
configured SAPs?


Regards, Benoit


On 1/5/2022 3:12 AM, Tianran Zhou wrote:


Hi WG,

I assume most of you are back to work.

Hope you had a good holiday.

As a follow up action after IETF 111, this mail starts a working group 
adoption call for draft-dbwb-opsawg-sap-00.


https://datatracker.ietf.org/doc/draft-dbwb-opsawg-sap/ 



This document defines a YANG data model for representing an abstract 
view of the provider network topology containing the points from which 
its services can be attached (e.g., basic connectivity, VPN, network 
slices).


Please review and comment.

We will conclude this adoption call after two weeks.

Cheers,

Tianran


___
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-dbwb-opsawg-sap-00

[daniel]

Hi Folks, 

(Strong) Support!

When I saw the adoption poll, it took me a few seconds to remember this I-D 
replaces:

A YANG Model for User-Network Interface (UNI) Topologies
draft-ogondio-opsawg-uni-topology

As an author of I-D(s) in TEAS and CCAMP related to draft-dbwb-opsawg-sap-00, 
it would be great to see this work progress as we will be referencing it. 
Additionally, some drafts still reference draft-ogondio-opsawg-uni-topology, so 
those authors will need to update their document(s) 
(https://datatracker.ietf.org/doc/draft-ogondio-opsawg-uni-topology/referencedby/)
 to the new I-D.

Furthermore, we are investigating to implement the described SAP function/model 
with (IETF) network slicing, within the EU project TeraFlow 
(https://www.teraflow-h2020.eu/) - there will be at least one vendor 
implementation. Once we have the implementation details, we will provide these 
to the authors of "draft-dbwb-opsawg-sap". 

BR, Dan.  
 
De : OPSAWG  De la part de Tianran Zhou
Envoyé : mercredi 5 janvier 2022 03:12
À : mailto:opsawg@ietf.org
Cc : mailto:opsawg-cha...@ietf.org
Objet : [OPSAWG] WG Adoption Call for draft-dbwb-opsawg-sap-00
 
Hi WG,
 
I assume most of you are back to work.
Hope you had a good holiday.
 
As a follow up action after IETF 111, this mail starts a working group adoption 
call for draft-dbwb-opsawg-sap-00.
https://datatracker.ietf.org/doc/draft-dbwb-opsawg-sap/
 
This document defines a YANG data model for representing an abstract view of 
the provider network topology containing the points from which its services can 
be attached (e.g., basic connectivity, VPN, network slices).
 
Please review and comment.
We will conclude this adoption call after two weeks.
 
Cheers,
Tianran
_
 
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] WG Adoption Call for draft-dbwb-opsawg-sap-00

[Wei Wang]

Hi Tianran,
    I support the adoption.


Best Regards,
Wei
-- Original --
From:   
 "Tianran Zhou" 
   
https://datatracker.ietf.org/doc/draft-dbwb-opsawg-sap/
 
 
 
This document defines a YANG data model for representing an abstract view of 
the provider network topology containing the points from which its services can 
be attached (e.g., basic connectivity, VPN, network slices).
 
 
 
Please review and comment.
 
We will conclude this adoption call after two weeks.
 
 
 
Cheers,
 
Tianran___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

Re: [OPSAWG] WG Adoption Call for draft-dbwb-opsawg-sap-00

[Qin Wu]

Support as coauthor, I am not aware of any IPR related to this I-D.

-Qin
发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 mohamed.boucad...@orange.com
发送时间: 2022年1月5日 15:32
收件人: Tianran Zhou ; opsawg@ietf.org
抄送: opsawg-cha...@ietf.org
主题: Re: [OPSAWG] WG Adoption Call for draft-dbwb-opsawg-sap-00

Hi Tianran, all,

I support adoption, obviously.

FWIW, I don’t have any IPR nor I’m aware of any related to this I-D.

Cheers,
Med

De : OPSAWG mailto:opsawg-boun...@ietf.org>> De la 
part de Tianran Zhou
Envoyé : mercredi 5 janvier 2022 03:12
À : opsawg@ietf.org
Cc : opsawg-cha...@ietf.org
Objet : [OPSAWG] WG Adoption Call for draft-dbwb-opsawg-sap-00

Hi WG,

I assume most of you are back to work.
Hope you had a good holiday.

As a follow up action after IETF 111, this mail starts a working group adoption 
call for draft-dbwb-opsawg-sap-00.
https://datatracker.ietf.org/doc/draft-dbwb-opsawg-sap/

This document defines a YANG data model for representing an abstract view of 
the provider network topology containing the points from which its services can 
be attached (e.g., basic connectivity, VPN, network slices).

Please review and comment.
We will conclude this adoption call after two weeks.

Cheers,
Tianran

_



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