[Detnet] Re: Mohamed Boucadair's No Objection on draft-ietf-detnet-controller-plane-framework-12: (with COMMENT)
Ketan Talaulikar <ketant.ietf@gmail.com> Mon, 08 September 2025 10:17 UTC
Return-Path: <ketant.ietf@gmail.com>
X-Original-To: detnet@mail2.ietf.org
Delivered-To: detnet@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 95F5F5F2E54D; Mon, 8 Sep 2025 03:17:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sx8mVIAijA2D; Mon, 8 Sep 2025 03:17:30 -0700 (PDT)
Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 499445F2E529; Mon, 8 Sep 2025 03:17:29 -0700 (PDT)
Received: by mail-pg1-x531.google.com with SMTP id 41be03b00d2f7-b4fa6cd2377so2706960a12.2; Mon, 08 Sep 2025 03:17:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1757326648; x=1757931448; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=KOznZaj+yg647PUWHOlto3jciBLdd7csnHh9JviG/UQ=; b=AW99TD9mks/WMX1QnTByNXJxZ0K/dcOt4BTkaQC+1LR7KgJ0EKI4q+oLP8QNWXfABg aDDUxYdpe82dMy1TGe2H+tT7txtgQyr7RipsBI7OCUHoZFaCYGlm2Edj12TmFJPmSRW5 FSi1NqB+RVqDn26udnTW/J+NCMpXj07hwxOfLhyxgLg7DFIUf4Pt80QX7FX6tZurY6wN XzKLq1kDGVr/KhJmE+XNLThDmipvA45grRRDEHbz8XABzQFSlcBb7espFJiy+3dh2OFc W56+7Clxqxg1jWggD0A0sMfz7TJV0bBHLgAZ6t3xKUX589adv1X0sa+GLFisaqspDSpf r+1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1757326648; x=1757931448; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=KOznZaj+yg647PUWHOlto3jciBLdd7csnHh9JviG/UQ=; b=Ag/22xSDefyowUv6WJ/yK2u+o0F0XNCJ1DbZlSbPx9k/1KgBNQQdAXYRxu5t9/k9AV acjKj46BmycNdpfReryIdnRWJBegGoWr7tZzaVHZ/TOIsfihcWBXtHIM0mFxZEQASdoF 3+RQQdWrnWAlOPy1UhzLTbnAwdiuBWD1WNbEBYqtxs0VKgbGtdjsgWttU83bpfnW5HL9 r3m/G5SEqzIFf78LudDUpNG4MVAd90yg1M4kZGlLRuNon2Yfl1RssaKmaOItpuBZ1S3U iEWJk+o1DnWu9l3YSJYM0qACVhLeUF/CiGsyNEnxPmR3doPWzxFF/5uLOb9N87E4HMDp /DtA==
X-Forwarded-Encrypted: i=1; AJvYcCW6vEdt4/GT6CLi4b1cbfgDL92IO+cKTkUIs76GTB55m5MbnaXP/iLeZoBtaMp/MLX8IPSp4FAc3DWaMdo04w5HE+A5PDvI3iAD0oM+y0DrVTHsqci0/jLhWPg/SE4=@ietf.org, AJvYcCWHGxqKyKzh3nocRtjQdtShztqpZDqmJr0Enq4WC5eMqi3/n8XaJnt1Io/uabZu9mKVCor50hO0@ietf.org, AJvYcCWXka+RI8w6ySGIgYf1Ed2okgDrk+A6q9LYX40Goj52iyBL3ENJvXJvnpjuayMAe/bhANbt0qeB4G1tN0Wo@ietf.org, AJvYcCXZuQH/ucdrw2tF5hA6uPjjKHfPH8zTWjrMXGhTIqStHWxomyywcTjJAcp4SXkyTRVaRUWWUQ==@ietf.org
X-Gm-Message-State: AOJu0YxDgzHOAQGihLM7V61ytCGL8u3gnCcr/epryrSNvq0V0tBLHBzg 5yMOK1iaii1d6I9mSlplGE3rNEfPlkW2nohQ/d2TIQN+qcMacIrutHzwoshL2e14lA5L9BFkp40 7Ca7+jsM3k01eNiG/heXv5HvFd6tcO+0=
X-Gm-Gg: ASbGnctDsCb8Y0pIb29r1DOY+lzqkyVvXyuc3VxoybvRPr0hMvnjEMkKp5Sku3Ch1uw 7frUozKhoKyFbK9D0KZyGcb5i3bbgz+ObOoxozicDLoalByHQG3zHSKQ8bRkRlRJy+DesfWKvNU RbxOxUVALiPfDRDFGimLmvyeFVgEwCYNWUcypG6i7tgcF5oUfmNV1gLkgHR6DKX8GXTM+HGLfxh iP2IXNfHeq4gybB3WnVuXYJju84v3B5UbPZsoXlEH2KY0rPRmk=
X-Google-Smtp-Source: AGHT+IFTmXvS1eMDcNYLL7JXML65mV9yjEf0zRL3uf+IyuJTapWTqPl+ZGpI33fp2eohhdvPiqTLgc6JzcwTubBleYw=
X-Received: by 2002:a17:902:eccf:b0:24c:b69f:e4be with SMTP id d9443c01a7336-2516e97ed9fmr113411025ad.6.1757326647894; Mon, 08 Sep 2025 03:17:27 -0700 (PDT)
MIME-Version: 1.0
References: <175394606617.345955.9112895964222856531@dt-datatracker-5bd446d5fd-c47nq> <CALypLp_h6SjJeVwrnOuoTMUjWHkDFG-4xT7hfXVBZrHJkQKsfw@mail.gmail.com> <PR0P264MB28858C774565BCF75867EDA98803A@PR0P264MB2885.FRAP264.PROD.OUTLOOK.COM>
In-Reply-To: <PR0P264MB28858C774565BCF75867EDA98803A@PR0P264MB2885.FRAP264.PROD.OUTLOOK.COM>
From: Ketan Talaulikar <ketant.ietf@gmail.com>
Date: Mon, 08 Sep 2025 15:47:17 +0530
X-Gm-Features: AS18NWBcMub6lwdq6C52Yy6SLLx4BWPDQsvi7lJuB-3kmJzysS-8wrOS-PEq5Tc
Message-ID: <CAH6gdPw6r8Lb=wWSkpQ8pJzL2iEQfrKNgqps1fHAc35KR7F8Ag@mail.gmail.com>
To: mohamed.boucadair@orange.com
Content-Type: multipart/alternative; boundary="0000000000009a2945063e477e5c"
Message-ID-Hash: G5MMN7MSRYEQPQ43NWFY3Q63455SAEAD
X-Message-ID-Hash: G5MMN7MSRYEQPQ43NWFY3Q63455SAEAD
X-MailFrom: ketant.ietf@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-detnet.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>, The IESG <iesg@ietf.org>, "draft-ietf-detnet-controller-plane-framework@ietf.org" <draft-ietf-detnet-controller-plane-framework@ietf.org>, "detnet-chairs@ietf.org" <detnet-chairs@ietf.org>, "detnet@ietf.org" <detnet@ietf.org>, "lberger@labn.net" <lberger@labn.net>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Detnet] Re: Mohamed Boucadair's No Objection on draft-ietf-detnet-controller-plane-framework-12: (with COMMENT)
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/pZACT9fXt1BI8tvBkxWdR7LNhCg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Owner: <mailto:detnet-owner@ietf.org>
List-Post: <mailto:detnet@ietf.org>
List-Subscribe: <mailto:detnet-join@ietf.org>
List-Unsubscribe: <mailto:detnet-leave@ietf.org>
Hi Med, Such an update sounds quite a big change to me. Note that many of them are normative references in this document and may create more confusion than help bring clarity. That said, I'll let the WG/authors/chairs chime in with their views. Thanks, Ketan On Fri, Sep 5, 2025 at 3:39 PM <mohamed.boucadair@orange.com> wrote: > Hi Carlos, > > > > Thanks for the follow-up and the changes made in -13. > > > > I really like the changes. > > > > One item to check is that now that we say: > > > > Therefore, this > > document should be considered as the authoritative reference to be > > considered if/when protocol work on the DetNet controller plane > > starts. > > > > Do we need to mark this document updating all the set of documents that > include portions of the CP requirements ([RFC8655] , [RFC8938], [RFC9551], > and [RFC9055])? > > > > I’m not pushing for any direction here. > > > > Cheers, > > Med > > > > *De :* CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es> > *Envoyé :* mercredi 27 août 2025 19:33 > *À :* BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com> > *Cc :* The IESG <iesg@ietf.org>; > draft-ietf-detnet-controller-plane-framework@ietf.org; > detnet-chairs@ietf.org; detnet@ietf.org; lberger@labn.net > *Objet :* Re: Mohamed Boucadair's No Objection on > draft-ietf-detnet-controller-plane-framework-12: (with COMMENT) > > > > Dear Med, > > > > Thanks a lot for your review and comments and apologies for the belated > reply (with the summer break it's taken longer than it should have). > > > > Please see inline our comments below. We have posted a new version that > hopefully addresses your points as explained below. > > > > On Thu, Jul 31, 2025 at 9:14 AM Mohamed Boucadair via Datatracker < > noreply@ietf.org> wrote: > > Mohamed Boucadair has entered the following ballot position for > draft-ietf-detnet-controller-plane-framework-12: No Objection > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > Please refer to > https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ > for more information about how to handle DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > > https://datatracker.ietf.org/doc/draft-ietf-detnet-controller-plane-framework/ > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Hi Andy, Xuesong, Mach, Balazs, and Carlos, > > Thank you for the effort put into this document. > > Also, thanks to Samier Barguil for the OPSDIR review. > > # Overall > > (1) Overlapping: The content is overlapping with what was already > published in > other RFCs, especially rfc8938#section 4, and DetNet Architecture, etc. > Some > guidance about which document(s) should be authoritative reference for > these > matters, should be clearly indicated here. > > > > [Carlos] We have modified the text in section 1. The updated text reads > now as follows: > > > > -8-<- > > While the DetNet Architecture and Data Plane documents are primarily > concerned with data plane operations, they do contain some > requirements, and considerations for functions that would be required > in order to automate DetNet service provisioning and monitoring via a > DetNet controller plane (e.g., section 4 of [RFC8938]). The purpose > of this document is to take these requirements and considerations > into a single document and extend and discuss how various possible > DetNet controller plane architectures could be used to satisfy these > requirements, while not providing the protocol details for a DetNet > controller plane solution. Such controller plane protocol solutions > will be the subject of subsequent documents. Therefore, this > document should be considered as the authoritative reference to be > considered if/when protocol work on the DetNet controller plane > starts. > > -8-<- > > > > > (2) (Lack of) Friendly consistency check: The text does not help readers > map > the requirements in the document with their origin specs, let alone tag new > ones (if any). An easy fix is to tag explicitly those that are inherited > from > existing specs. > > > > [Carlos] Thanks for the comment. We've added a explicit tag as you > suggested. > > > (3) (Lack of) DetNet specifics: Many of the requirements are provided in > generic terms that can be applicable to any TE scheme that includes path > computation, etc. Even PREOF discussion does not got into more specifics. > > > > [Carlos] The text is written assuming the DetNet framework and > architecture as a starting point and actually many requirements are > collected from such documents. We believe that going into more specifics > will deviate from the goal of this document. > > > # Detailed comments; major ones are marked with (*) > > ## At least RFC8655 is normative (*). Please double check the current > classification your references. > > > > [Carlos] This is now fixed, thanks. > > > > > ## This is about “a” framework, not “The” only framework that can be > considered > > I suggest to make that clear in the document title > > NEW: A Framework for Deterministic Networking (DetNet) Controller Plane > > > > [Carlos] I've done that change, assuming that our AD and WG chairs are > fine with that. > > > > > Better, I would include “Requirements” in the title > > > > [Carlos] I prefer not to do this change as the requirements are not the > main contribution of the document (many of them are actually collected from > other existing documents and included for completeness) > > > > > ## Introduction > > ### Consider citing 4.4.2 of rfc8655 for the following > > CURRENT; > DetNet overall architecture, the controller plane > includes what are more traditionally considered separate control and > management planes. > > > > [Carlos] This is now done, thanks. > > > > > ### Consider citing rfc6632#section-4.2 for the following > > CURRENT: > Traditionally, the management plane is primarily > involved with fault management, configuration management and > performance management (sometimes accounting management and security > management is also considered in the management plane, but not in the > > [Carlos] This is now done, thanks. > > > > ## Flow (*) > > CURRENT: > * Support the dynamic creation, modification, and deletion of DetNet > flows. > > I can’t parse this, given that DetNet flow is defined in rfc8655 as > follows: > > A sequence of packets that conforms uniquely to a flow identifier > ^^^^^^^^^^^^^^^^^^^^^^ > and to which the DetNet service is to be provided. It includes > any DetNet headers added to support the DetNet service and > forwarding sub-layers. > > For example, what does “deletion of DetNet flow” concretely mean from a > control > standpoint? Do we mean required state for the flow? > > > > [Carlos] I've replaced "creation" with "instantiation", which is the word > that is actually used in RFC8655 in this context, cited below: > > > > "Instantiate DetNet flows in a DetNet domain (which may, for example, > include some or all of the following: explicit path determination, link > bandwidth reservations, restricting flows to IEEE 802.1 TSN links, node > buffer and other resource reservations, specification of required queuing > disciplines along the path, ability to manage bidirectional flows, etc.) as > needed for a flow." > > > > > ## What about encapsulation-specific and metadata control? (*) > > A specific encapsulation scheme may be needed to carry some metadata, per > the > following from the base arch: > > The use of encapsulation is also required if additional information > (metadata) is needed by the DetNet data plane and either (1) there is > no ability to include it in the client data packet or (2) the > specification of the client data plane does not permit the > modification of the packet to include additional data. An example of > such metadata is the inclusion of a sequence number required by > PREOF. > > Do we need to cover explicitly: > * Discovery of encapsulation capabilities of underlying nodes? > * Discovery of metadata schemes supported by underlying nodes? > * Means to instruct nodes which encap to put in place and companion > metadata > for a given flow? > > > > [Carlos] This is actually a good point. I've added a short section (4.5. > Encapsulation and metadata support) to briefly reflect these considerations. > > > > 4.5. Encapsulation and metadata support > > To effectively manage DetNet flows, the controller plane will need > have a clear understanding of the encapsulation and metadata > capabilities of the underlying network nodes. This will require a > control mechanism that can discover, configure, and manage these > parameters for each flow. > > The controller plane needs to understand and manage the encapsulation > and metadata capabilities of the network nodes to provision DetNet > flows effectively. This process might need a discovery phase, in > which the controller discovers which encapsulation types (e.g., MPLS, > IP) and metadata schemes (e.g., sequencing, timestamping) each node > supports. After discovery, the controller might instruct nodes on > the specific encapsulation and companion metadata to apply for a > given flow. This ensures that DetNet packets are handled > > consistently across the network. For example, the controller might > instruct a node to use an MPLS header and add a sequence number for a > particular flow. > > > > > ## Centralized SDN Controller and Control Plane Implications (*) > > CURRENT: > * Allow flow instantiation requests to originate in an end > application (via an Application Programming Interface (API), via > static provisioning, or via a dynamic control plane, such as a > centralized SDN(Software-Defined Networking) > > I’m not sure there is a value in “characterizing” an SDN controller as > “centralized” here other than opening the door for discussion about single > point of failure issues, implications on the delay (which is key for > detenet) > when there no distributed mechanisms to react to local failure and > completely > rely on a controller to detect and react to failures. > > The base arch has the required references for SDN matters (where some of > this > is already discussed): > > This > echoes the composition of Figure 1 of "Software-Defined Networking > (SDN): Layers and Architecture Terminology" [RFC7426] and the > ^^^^^^^^^^ > controllers identified in [RFC8453] and [RFC7149]. > ^^^^^^^^^^ > > I suggest we simply delete the “centralized” mention (and fix some few > nits) > > > NEW: > * Allow flow instantiation requests to originate in an end > application (via an Application Programming Interface (API), via > static provisioning, or via a dynamic control plane, such as an > SDN (Software-Defined Networking) > > > > [Carlos] OK, thanks for the suggestion. > > > > > ## Time Synchronization > > CURRENT: > * Support queue control techniques defined in Section 4.5 of > [RFC8655] and [RFC9320] that require time synchronization among > network nodes. > > Wonder whether we can be more specific on the time synchronization, is it > only > between data plane nodes, or data planes and control planes, etc. > > > > [Carlos] As per RFC8655 this is between data plane nodes. I've made this > explicit. > > > > > ## Scaling > > CURRENT: > * Scale to handle the number of DetNet flows expected in a domain > (which may require per-flow signaling or provisioning). > > “Flows expected in a domain” is deployment-specific. Not sure how this can > be > useful for solution design. > > > > [Carlos] If the solution is designed for a specific deployment, this is > meaningful. Since we are not advocating for/designing any specific > solution, we believe it is useful to reflect that depending on the > deployment requirements, the solution might be different. > > > > > ## Provisioning-only (*) > > CURRENT: > * Provision flow identification information at each of the nodes > along the path. Flow identification may differ depending on the > location in the network and the DetNet functionality (e.g., transit > node vs. relay node). > > Shouldn’t we also cover retrieval of installed state that would impact > forwarding of a flow matching that same identifier? How conflicts are > detected/mitigated? Should there be some kind of priority/tie-break in > place? > > > > [Carlos] What is covered is that the control plane needs to convey that > information. Ensuring that the identifier is unique, etc is more > implementation dependent. > > > > > A companion management question to this CP requirement is whether support > means > to check the outcome of provisioned rule against a test packet? > > > > [Carlos] We consider this out of the scope for the framework document. > > > > > ## Scope of CC and CV (*) > > CURRENT: > * Support DetNet flow continuity check and connectivity verification > functions. > > What is the scope of these checks? For example, do we envision those to in > be > triggered from any source node (including data plane nodes) or is this > restricted to a controller? > > Also, do we envision that partial path check are covered? > > > > [Carlos] This is partially covered in the detnet-OAM document (RFC 9551), > and it can be generated by any Maintenance End Points (MEP), which I > believe could be any source node. By referencing RFC 9551, we believe this > point is covered. > > > > > ## DetNet and no-DetNet > > CURRENT: > * Operate in a converged network domain that contains both DetNet > and non-DetNet flows. > > This is fair for flows. However, are there specific CP requirements for > domains > where some nodes are not-DetNet? Or do we assume that the document assumes > that > the CP/MP is for DetNet domain with **ALL** nodes compliant with DetNet? > Please > clarify the assumption in the document. > > > > [Carlos] the document talks about detnet and non-detnet flows, not nodes. > We assume a detnet capable network as described in RFC8655, no difference > here, that should support both detnet demanding flows and non-detnet flows. > > > > > ## “3.2. SDN/Fully Centralized Control Plane” > > As indicated above, “fully centralized” has scalability, availability, > reactivity to failure, etc. implications that needs to be discussed. > > > > [Carlos] Those considerations would be implementation specific. The > document discusses how a controller plane framework might look like and > document possible high-level approaches, but we believe that the document > should stay at this level and not go into more details. > > > > > ## (Restriction to) YANG 1.1 > > OLD: > Network node configurations for DetNet flows are > performed by the controller using a protocol such as NETCONF > [RFC6241]/YANG [RFC6020] DetNet YANG [RFC9633] or PCE-CC [RFC8283]. > > NEW: > Network node configurations for DetNet flows are > performed by the controller using a protocol such as NETCONF > [RFC6241]/YANG [RFC6020][RFC7950] DetNet YANG [RFC9633] or PCE-CC > [RFC8283]. > ^^^^^^^^^^ > > [Carlos] Thanks, we have implemented this change. > > > > > > ## Topology assumptions: Single/Multi-attached End Systems (*) > > It seems to me that the architecture assumes that an end system is always > single attached (that is, packets from a host are only received by a SINGLE > ingress node and will be forwarded to SINGLE egress node). For example, the > document says: > > 3. Based on the calculation result, the Controller distributes flow > path information to the ingress edge node and configures network > nodes along the path with necessary DetNet information (e.g. for > replication/duplicate elimination). > > I’m afraid this is restrictive and that we should allow for having > multi-attachment cases. > > [Carlos] I see your point, but current DetNet architecture kind-of assumes > a single ingress node, and we followed the same assumption in the document. > In any case, the document does not preclude other scenarios, though they > are not considered specifically. > > > > ## Distraction :-) > > CURRENT: > As such, segment routing can be considered as a new data > plane for both MPLS and IP. > > I don’t think we need to include such statement as there are specific > variant > for MPLS and IP. I suggest we delete that sentence. > > [Carlos] Done. > > > > # Multi-domain Matters > > The current text is too generic. I’m not sure it adds much. > > If you keep it, it might be worth reminding DetNet scope: > > (RFC8655) > DetNet is for networks that are under a single > administrative control or within a closed group of administrative > control; these include campus-wide networks and private WANs. DetNet > is not for large groups of domains such as the Internet. > > > > [Carlos] I disagree with the limitation to multi-domain. RFC 8655 mentions > explicitly multiple domains in Figure 5 (DetNet Service Reference Model), > though no work has been adopted yet in the WG to tackle multi-domain > aspects. But note that this has been discussed in past meetings and there > is ongoing (individual drafts) work ongoing. The multi-domain aspect was > actually discussed in one meeting and adding the text was the consensus of > the WG. > > > > > # RAW > > CURRENT: > domains, e.g., PCEs need to discover each other, authenticate and > negotiate per-hop behaviors. Furthermore, in case of wireless > domains, the per-domain RAW specific functions like the PLRs have to > be also considered, e.g., in addition to the PCEs. > > Add a pointer to RAW arch spec. Thanks. > > > > [Carlos] This has been added, thanks. > > > > > Hope this helps. > > > > [Carlos] It helped a lot indeed. Thanks a lot for all your comments. > > > > Carlos > > > > > Cheers, > Med > > > ____________________________________________________________________________________________________________ > 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. > >
- [Detnet] Mohamed Boucadair's No Objection on draf… Mohamed Boucadair via Datatracker
- [Detnet] Re: Mohamed Boucadair's No Objection on … CARLOS JESUS BERNARDOS CANO
- [Detnet] Re: Mohamed Boucadair's No Objection on … mohamed.boucadair
- [Detnet] Re: Mohamed Boucadair's No Objection on … Ketan Talaulikar
- [Detnet] Re: Mohamed Boucadair's No Objection on … CARLOS JESUS BERNARDOS CANO