Re: [CCAMP] Drafted text for the ROADM architecture section (draft-ietf-ccamp-optical-impairment-topology-yang-02)

<esther.lerouzic@orange.com> Mon, 04 November 2019 09:12 UTC

Return-Path: <esther.lerouzic@orange.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86BA9120887 for <ccamp@ietfa.amsl.com>; Mon, 4 Nov 2019 01:12:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rpJRoejcBGKe for <ccamp@ietfa.amsl.com>; Mon, 4 Nov 2019 01:12:51 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B2CD120D6B for <ccamp@ietf.org>; Mon, 4 Nov 2019 01:12:51 -0800 (PST)
Received: from opfedar03.francetelecom.fr (unknown [xx.xx.xx.5]) by opfedar24.francetelecom.fr (ESMTP service) with ESMTP id 4766X1455Kz5wLw; Mon, 4 Nov 2019 10:12:49 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.54]) by opfedar03.francetelecom.fr (ESMTP service) with ESMTP id 4766X12kvRzCql7; Mon, 4 Nov 2019 10:12:49 +0100 (CET)
Received: from OPEXCAUBM42.corporate.adroot.infra.ftgroup ([fe80::1c8e:403e:fbea:5835]) by OPEXCAUBM7D.corporate.adroot.infra.ftgroup ([fe80::bcfe:4850:e646:f223%21]) with mapi id 14.03.0468.000; Mon, 4 Nov 2019 10:12:49 +0100
From: <esther.lerouzic@orange.com>
To: "Gabriele Maria Galimberti (ggalimbe)" <ggalimbe@cisco.com>, "Belotti, Sergio (Nokia - IT/Vimercate)" <sergio.belotti@nokia.com>, "Beller, Dieter (Nokia - DE/Stuttgart)" <dieter.beller@nokia.com>, "CCAMP (ccamp@ietf.org)" <ccamp@ietf.org>
Thread-Topic: [CCAMP] Drafted text for the ROADM architecture section (draft-ietf-ccamp-optical-impairment-topology-yang-02)
Thread-Index: AQHVkuVMW6i8QUsw/kCGlLWd0t0iGKd6uhSA
Date: Mon, 4 Nov 2019 09:12:49 +0000
Message-ID: <15357_1572858769_5DBFEB91_15357_276_1_BDD0E12FDA19534DA7B322C56B753E6D47CC2EBB@OPEXCAUBM42.corporate.adroot.infra.ftgroup>
References: <3D629098-F7C6-4EF3-98B0-0D3CA3D4A3D1@cisco.com>
In-Reply-To: <3D629098-F7C6-4EF3-98B0-0D3CA3D4A3D1@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: multipart/related; boundary="_004_BDD0E12FDA19534DA7B322C56B753E6D47CC2EBBOPEXCAUBM42corp_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/fqTmICVSTqGjpgnAlDtooInGKas>
Subject: Re: [CCAMP] Drafted text for the ROADM architecture section (draft-ietf-ccamp-optical-impairment-topology-yang-02)
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Nov 2019 09:12:59 -0000

Dear Dieter,

Thanks for the text, I am OK with it,

regards

Esther

De : CCAMP [mailto:ccamp-bounces@ietf.org] De la part de Gabriele Maria Galimberti (ggalimbe)
Envoyé : lundi 4 novembre 2019 08:56
À : Belotti, Sergio (Nokia - IT/Vimercate); Beller, Dieter (Nokia - DE/Stuttgart); CCAMP (ccamp@ietf.org)
Objet : Re: [CCAMP] Drafted text for the ROADM architecture section (draft-ietf-ccamp-optical-impairment-topology-yang-02)

Hi Dieter,

Thanks for the new text, I’m OK with it.

Best Regards,

Gabriele

[http://www.cisco.com/swa/i/logo.gif]


Gabriele Galimberti
Principal Engineer
Cisco Photonics Srl
Italy

via S.Maria Molgora, 48 C
20871 - Vimercate (MB)
Italy
www.cisco.com/global/IT/<http://www.cisco.com/global/IT/>

ggalimbe@cisco.com<mailto:ggalimbe@cisco.com>
Phone :+39 039 2091462
Mobile :+39 335 7481947
Fax :+39 039 2092049













From: CCAMP <ccamp-bounces@ietf.org>; on behalf of Sergio Belotti <sergio.belotti@nokia.com>;
Date: Saturday, 2 November 2019 at 12:05
To: Dieter Beller <dieter.beller@nokia.com>;, "CCAMP (ccamp@ietf.org)"; <ccamp@ietf.org>;
Subject: Re: [CCAMP] Drafted text for the ROADM architecture section (draft-ietf-ccamp-optical-impairment-topology-yang-02)

Hi Dieter,
Thanks for text, I’m fine with that.

Thanks
Sergio

From: CCAMP <ccamp-bounces@ietf.org>; On Behalf Of Beller, Dieter (Nokia - DE/Stuttgart)
Sent: Friday, November 1, 2019 2:12 PM
To: CCAMP (ccamp@ietf.org) <ccamp@ietf.org>;
Subject: [CCAMP] Drafted text for the ROADM architecture section (draft-ietf-ccamp-optical-impairment-topology-yang-02)

Hi all,

please find below the text I drafted for draft-ietf-ccamp-optical-impairment-topology-yang-02 describing the ROADM architectures discussed during our weekly calls.

The ascii-art figures will be provided by Gabriele.

Please send me your comments before Mon, Nov 4 – the submission deadline is rapidly approaching!


Thanks,
Dieter

________________________________

1.8. ROADM Node Architectures
The ROADM node architectures in today’s dense wavelength division multiplexing (DWDM) networks can be categorized as follows:

o  Integrated ROADM architecture with integrated optical transponders

o  Integrated ROADM architecture with integrated optical transponders and single channel add/drop ports for remote optical transponders

o   Disaggregated ROADM architecture where the ROADM is subdivided into degree, add/drop, and optical transponder subsystems handled as separate network elements
The TE topology YANG model augmentations including optical impairments for DWDM networks defined below intend to cover all the 3 categories of ROADM architectures listed above. In the case of a disaggregated ROADM architecture, it is assumed that optical domain controller already performs some form of abstraction and presents the TE-node representing the disaggregated ROADM in the same way as an integrated ROADM with integrated optical transponders if the optical transponder subsystems and the add/drop subsystems are collocated (short fiber links not imposing significant optical impairments).
The different ROADM architectures are briefly described and illustrated in the following subsections.
[Editor’s Note: The modeling of remote optical transponders located for example in the client device with a single channel link between the OT and the add/drop port of the ROADM requires further investigations and will be addressed in a future revision of this document.]

1.8.1. Integrated ROADM architecture with integrated transponders
Figure 2 and Figure <RA1> below show the typical architecture of an integrated ROADM node, which contains the optical transponders as an integral part of the ROADM node. Such an integrated ROADM node provides DWDM interfaces as external interfaces for interconnecting the device with its neighboring ROADMs (see OTS link above). The number of these interfaces denote also the degree of the ROADM. A degree 3 ROADM for example has 3 DWDM links that interconnect the ROADM node with 3 neighboring ROADMs. Additionally, the ROADM provides client interfaces for interconnecting the ROADM with client devices such as IP routers or Ethernet switches. These client interfaces are the client interfaces of the integrated optical transponders.

1.8.2. Integrated ROADMs with integrated optical transponders and single channel add/drop interfaces for remote optical transponders
Figure <RA2> below shows the extreme case where all optical transponders are not integral parts of the ROADM but are separate devices that are interconnected with add/drop ports of the ROADM. If the optical transponders and the ROADM are collocated and if short single channel fiber links are used to interconnect the optical transponders with an add/drop port of the ROADM, the optical domain controller may present these optical transponders in the same way as integrated optical transponders. If, however, the optical impairments of the single channel fiber link between the optical transponder and the add/drop port of the ROADM cannot be neglected, it is necessary to represent the fiber link with its optical impairments in the topology model This also implies that the optical transponders belong to a separate TE node [Editor’s Note: this requires further study].

1.8.3. Disaggregated ROADMs that are subdivided into degree, add/drop, and optical transponder subsystems
Recently, some DWDM network operators started demanding ROADM subsystems from their vendors. An example is the OpenROADM project where multiple operators and vendors are developing related YANG models. The subsystems of a disaggregated ROADM are: single degree subsystems, add/drop subsystems and optical transponder subsystems. These subsystems separate network elements and each network element provides a separate management and control interface. The subsystems are typically interconnected using short fiber patch cables and form together a disaggregated ROADM node. This disaggregated ROADM architecture is depicted in Figure <RA3> below.
As this document defines TE topology YANG model augmentations [TE-TOPO] for the TE topology YANG model provided at the north-bound interface of the optical domain controller, it is a valid assumption that the optical domain controller abstracts the subsystems of a disaggregated ROADM and presents the disaggregated ROADM in the same way as an integrated ROADM hiding all the interconnects that are not relevant from an external TE topology view.


_________________________________________________________________________________________________________________________

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.