s sufficient, note that TMF specification has
already been published by TMF. if you think necessary, I can consult with TMF
specification authors for clarification.
[Italo Busi] IMHO, after this document is adopted as WG item, we can send a LS
to TMF to get their feedbacks to make it sure the w
I support the adoption of this document
Italo
> -Original Message-
> From: Henk Birkholz
> Sent: giovedì 8 febbraio 2024 16:44
> To: OPSAWG
> Subject: [OPSAWG] WG Adoption Call for draft-feng-opsawg-incident-
> management-04
>
> Dear OPSAWG members,
>
> this email starts a call for
Hi Sasha,
IMHO, LSP ping and BFD are examples of in-band OAM which may have either an
in-band or an out-of-band return path (upstream OAM from the terminology below)
An example of out-of-band OAM can be the RSVP-TE notification messages. There
are other examples of out-of-band OAM mechanisms
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
Daniele & Qiufang,
I would like to request a slot to discuss the technical issues that need to be
addressed to evolve draft-ietf-ccamp-network-inventory-yang-02 to become the
network inventory base model, including how the overall network inventory model
can be modularized
If there is enough
My preference is option 1 to adopt draft-ietf-ccamp-network-inventory-yang-02
in IVY and evolve it to become the network inventory base model
I understand this draft does not cover all the items in the WG charter but IMHO
there is no need to cover all the IVY WG charter items into a
Hi Bo,
Regarding re-using RFC8345 for the mapping between physical (inventory) and
abstract (network topology) resources, I can see your point for the navigation
between the physical NEs (within the inventory) and the abstract nodes (within
network topologies). However, I am not sure you can
Hi OPSAWG,
no, I am not aware of any IPR that applies to this draft
Italo
> -Original Message-
> From: Joe Clarke (jclarke) [mailto:jcla...@cisco.com]
> Sent: lunedì 22 marzo 2021 14:33
> To: opsawg@ietf.org
> Subject: [OPSAWG] IPR CALL: draft-ietf-opsawg-vpn-common
>
> Authors,
eccare...@ericsson.com]
> Sent: martedì 23 febbraio 2021 15:51
> To: Italo Busi ; TEAS WG ; CCAMP
> ; opsawg
> Subject: RE: TE Topology profile (FW: I-D Action: draft-busi-teas-te-topology-
> profiles-01.txt)
>
> Hi Italo, authors,
>
> I thinks this draft is extremely us
;
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
> Title : Profiles for Traffic Engineering (TE) Topology Data
> Model
> Authors : Italo Busi
>
if we can keep the scope of its initial revision limited/focused to what
it is needed.
My 2 cents
Thanks, Italo
> -Original Message-
> From: mohamed.boucad...@orange.com
> [mailto:mohamed.boucad...@orange.com]
> Sent: giovedì 3 settembre 2020 09:02
> To: Italo Busi ; op
the module name to reflect a broader scope
of future revisions.
Thanks, Italo
> -Original Message-
> From: tom petch [mailto:ie...@btconnect.com]
> Sent: lunedì 24 agosto 2020 13:37
> To: Italo Busi ; Joe Clarke (jclarke)
> ; opsawg
> Subject: Re: [OPSAWG] CALL FOR AD
I support WG adoption of this document
I think the relationship between this model and the model in
draft-ietf-ccamp-client-signal-yang could be clarified by progressing this work
as a WG document
Italo
> -Original Message-
> From: Joe Clarke (jclarke) [mailto:jcla...@cisco.com]
>
petch [mailto:ie...@btconnect.com]
> Sent: venerdì 29 maggio 2020 12:48
> To: Italo Busi ; adr...@olddog.co.uk; 'Joe Clarke
> (jclarke)' ; 'Oscar González de Dios'
>
> Cc: 'opsawg'
> Subject: Re: [OPSAWG] Minutes of L3NM/L2NM module discussions
>
> From: Italo Busi
Hi all,
I support developing a separate module for the common types/groupings/...
This approach has worked quite well within TEAS and CCAMP WG.
I agree that there are some risks with this work: my suggestion is just be
aware of the risks and be careful to avoid them.
Working in parallel on
Hi Oscar,
Thanks a lot for opening the discussion.
I would like to join these calls.
Thanks, Italo
From: Oscar González de Dios [mailto:oscar.gonzalezded...@telefonica.com]
Sent: mercoledì 20 maggio 2020 16:06
To: opsawg
Subject: [OPSAWG] Invitation to participate in the L3NM/L2NM regular
16 matches
Mail list logo
