Re: [Inventory-yang] Nimby WG chartering

[Adrian Farrel <[e-mail]>]

Thanks for continuing to drive this, Rob.

I could live with your proposal. So, if in doubt, go ahead.

A possible "improvement" to tighten this up a bit, would be:

"Specification of how the inventory is maintained or structured, and the
mechanisms of how inventory content is used are outside the scope of the
Working Group, but the Working Group may develop informative examples
describing how the inventory data could be used."

Adrian
-----Original Message-----
From: Inventory-yang <[e-mail]> On Behalf Of Rob
Wilton (rwilton)
Sent: 18 April 2023 17:26
To: [e-mail]; Michael Richardson
<[e-mail]>; Daniele Ceccarelli <[e-mail]>
Cc: [e-mail]; JACQUENET Christian INNOV/NET
<[e-mail]>
Subject: Re: [Inventory-yang] Nimby WG chartering

Hi all,

Perhaps rather than:

" Details of how the inventory content is used is outside the scope of
the Working Group."

We could have:

"Work specifying the use of inventory content is outside the scope of the
Working Group,
but informative examples describing how the inventory data may be used is
within scope".

Would this be sufficient (alongside deleting the paragraph on capabilities)
to submit this version of the charter for IESG review?

Ideally, I would like to get this onto next week's telechat (which means
pushing the button on/before Thursday this week), so if we able to close on
this today/tomorrow then that would be really appreciated (and I appreciate
that I've also been slow here).

Regards,
Rob


-----Original Message-----
From: Inventory-yang <[e-mail]> On Behalf Of
[e-mail]
Sent: 14 April 2023 06:08
To: Michael Richardson <[e-mail]>; Daniele Ceccarelli
<[e-mail]>
Cc: [e-mail]; JACQUENET Christian INNOV/NET
<[e-mail]>
Subject: Re: [Inventory-yang] Nimby WG chartering

Hi Michael, 

> Do we ever tell operators what they have do? No.
> Should we say things like, "this enables an operator who wants to map
> their L1 circuits to L0 segments"? Yes.

This falls under means to ease correlation and zoom in/out. This is covered
by the proposed charter. 

This is distinct from the initial part you commented on about the use of the
inventory content. I don't think we have to dive into how (1) an
authoritative inventory is bootstrapped/maintained, (2) how the same data
model is used to structure data that is actually discovered from the
network/infrastructure, (3) how this is exposed to applications such as
planning, emulation tools, etc. 

BTW, I suggest that we make this change: 

NEW:
 Details of how the inventory content is fed and used are outside the scope
of
 
^^^^^^
 the Working Group.

Thanks.

Cheers,
Med

> -----Message d'origine-----
> De : Inventory-yang <[e-mail]> De la part de
> Michael Richardson
> Envoyé : jeudi 13 avril 2023 18:50
> À : Daniele Ceccarelli <[e-mail]>
> Cc : [e-mail]
> Objet : Re: [Inventory-yang] Nimby WG chartering
> 
> 
> Daniele Ceccarelli <[e-mail]> wrote:
>     > LMO is Lifecycle Management and Operations. (
>     > https://datatracker.ietf.org/doc/draft-palmero-opsawg-dmlmo/)
> 
>     > Layer 0 is the layer at which optical devices operate.
> 
> I see.  So layer 1 is that I have a 100G fiber from Chicago-DC1 to LA-DC8.
> Layer 0 is that there are five segments between DC1 and DC8 via four
> optical switches in St.Louis, Denver, Reno, SFO and LA.
> 
>     > Can you elaborate a bit? Providing example won't be banned,
> telling
>     > operators how they have to populate their inventories won't make
> them
>     > very happy.
> 
> Do we ever tell operators what they have do? No.
> Should we say things like, "this enables an operator who wants to map
> their L1 circuits to L0 segments"? Yes.
> 
> --
> ]               Never tell me the odds!                 | ipv6 mesh
networks [
> ]   Michael Richardson, Sandelman Software Works        |    IoT architect
> [
> ]     [e-mail]  http://www.sandelman.ca/        |   ruby on rails
> [


____________________________________________________________________________
_____________________________________________

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.

-- 
Inventory-yang mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/inventory-yang

-- 
Inventory-yang mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/inventory-yang