From nobody Sat Jul 22 11:19:52 2023 Return-Path: X-Original-To: teas@ietfa.amsl.com Delivered-To: teas@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FB86C15154A; Sat, 22 Jul 2023 11:19:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.096 X-Spam-Level: X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=telefonica.com Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ftT8hZKwe0Jz; Sat, 22 Jul 2023 11:19:47 -0700 (PDT) Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-he1eur04on2130.outbound.protection.outlook.com [40.107.7.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59F5EC151539; Sat, 22 Jul 2023 11:19:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=QGGpCTiIALzvqEYhhs5/xs0I/QUpR0iSda1RI5JdonNYbqoxo9Ptjy/oapsByMr91nhVX0ZgxwTQ8ngkVLRiCw8v3PQ4o3CN0z1FLGVUWgFc5E150YAhbD0P2IVDwFDnY/2b4gAf/ISlQoDzattEuUa8oHa6j9lx7CoR1OPMK2Jlzvb5vXb3V6XDpWR3aJoA3riiUA6Sk9EvtoZKk18Hx5xq1G+hsIR3evTradHjAlgDgUG6Ak4qxYZn+ObHrOStkAyS4/UV3n3iUAVIpyQxo6lg8m98BguFtgU3/ggQqTpjY1/PYLfVokEtEHzBE9JuwhGm3dPlUs4h8H7Uf6Jehg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=CrmZRL4HJSknRVt4XUkmZpE9nHjGIDr6/MM3ZNPrRWw=; b=dHSHjUWc05FB6PDE6EkTf0mbt4bDQ0GuMygpZzn8Rx4XRqrs6+6eWCuwl1N8/GTic0FHcKMfv+xI9VEa490GjhuA7XATxQelDx5Jp6Aggmps34AA/iUJuBvfQG2EIEUHQ+bYgMVMiA9eXHrTIhDYEyuKRsfX4P2v7gqO5NE3dnhv8d4wKD2tR38L9IkIcEevcOHSa9SGvt9yxSq/PgXEHAP9WzXOFZek391M+hbl2YSor8kNBDU+BqSaL/hT3vus+qEOzG07PFSIP0PGNxZ853vPmCkHVdeKo9kTlD3qXK4P+Xku2fvKw7GMKEUkI29n/43npBSnsTC4PxPTZZzLzQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=telefonica.com; dmarc=pass action=none header.from=telefonica.com; dkim=pass header.d=telefonica.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telefonica.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=CrmZRL4HJSknRVt4XUkmZpE9nHjGIDr6/MM3ZNPrRWw=; b=fZ0HfpdTfg2ramPSAYDcqUZp/ORaZ6Lr7F76k7O7XwVv2R8VFY2cvhp0HVwO6LMk7Y2KYBAL1SIp+dyeB7JKSKCG486Ex4C7iwWK5XqHJJinpcFgg2Qxjy3K8ki66sQiqeXpJMUK+1MOdX1JEF/jh2hN91eRhMQXef52ew23Iy0= Received: from DB9PR06MB7915.eurprd06.prod.outlook.com (2603:10a6:10:291::14) by DB8PR06MB6554.eurprd06.prod.outlook.com (2603:10a6:10:129::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6609.29; Sat, 22 Jul 2023 18:19:41 +0000 Received: from DB9PR06MB7915.eurprd06.prod.outlook.com ([fe80::b653:b0de:e5ad:eae0]) by DB9PR06MB7915.eurprd06.prod.outlook.com ([fe80::b653:b0de:e5ad:eae0%4]) with mapi id 15.20.6609.026; Sat, 22 Jul 2023 18:19:41 +0000 From: LUIS MIGUEL CONTRERAS MURILLO To: Kiran Makhijani , Vishnu Pavan Beeram , TEAS WG CC: TEAS WG Chairs Thread-Topic: [Teas] WG adoption poll: draft-contreras-teas-slice-controller-models-05 Thread-Index: AQHZrq+6eGN6DwWC/EuNhz1cgFaqAa+1CHmAgBEpD9A= Date: Sat, 22 Jul 2023 18:19:41 +0000 Message-ID: References: In-Reply-To: Accept-Language: es-ES, en-US Content-Language: es-ES X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=telefonica.com; x-ms-publictraffictype: Email x-ms-traffictypediagnostic: DB9PR06MB7915:EE_|DB8PR06MB6554:EE_ x-ms-office365-filtering-correlation-id: 8f7989c8-6854-409d-92e2-08db8ae037ad x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: pNJNRvgtNSsBraxcEBkc87VLArNI5MGwhsYpL5dwG2k83qXEWJQd5Lcq1W+zQsm2JvWHzz3HvhmgtuBDWQPIlSm/nFssEAtOctjRNSP0pJ9RF9ZlU3SH7XcqOY/VDUlz24w7DoCPPgnxHf54wb8rd8r1bxe6AXCRp0mou9qoMfLM41GlENGw+ngshpfLw+mkLkEJUJtphPP5g1gEBfAqcp+cAnvm0UotwxCmk6A031bKt/rteUyEw+oWHTL8+3BJDCA0OXQilPCTZieB0PZQNXbdXvMmEf647aJsuRY/FNJR7zkBT0Vfj1z5pV67Q0XT3SZQD8Xn3oYLv0U8UJUy00e3rWgpDWccJVMVHUpCislU8DQBTu1Hhzb+ZozgRhsRU6TvTdyPKAdcm8H92zPCRN+7I6JFFhs97VbHen0Pxa5/bNtnF/Gjaqz4+OC3y8jaRyJ/NzONcJiv3jRnPovBSvQyItCWiN9DS/Dlu5GVKO1cjE+TYBdIsj45/w/0VOj29funF7vRFrHBL0Mrr+vca5Otzwo+jUssbgnn8CSFjQzbUdDTx8kSF4FsZtiwCEvvCtgKqA1upcakbjr+N0AsI8JS1xcCD9bWepFBx89M0gr0UNaK47XajuVY93Ltol8/w6ND9fB0g0nsSH4RvDfTQQPlcTn91v4ojZznylxdl+o= x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DB9PR06MB7915.eurprd06.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230028)(4636009)(376002)(396003)(346002)(366004)(39860400002)(136003)(451199021)(38100700002)(66899021)(55016003)(122000001)(166002)(53546011)(66574015)(83380400001)(8676002)(8936002)(5660300002)(52536014)(110136005)(478600001)(66556008)(66476007)(66446008)(64756008)(4326008)(316002)(66946007)(76116006)(41300700001)(186003)(6506007)(71200400001)(19627235002)(9686003)(7696005)(2906002)(33656002)(38070700005)(86362001)(82960400001)(9010500006)(15398625002); DIR:OUT; SFP:1102; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?nt/Dc1QByR/gpvIxGfkByq6UEP5OkSNtbTEbP4VrLzqal7BKFefnKw8yTN6X?= =?us-ascii?Q?90Vd/MDdpZO70B3BQyRdhd51VaasiybxZoIR/nzwuZzrEWhionnlWfPj1aa5?= =?us-ascii?Q?7n9AmFeBFbeopNY2fJNy3YJzPBQTZqeSVUgdYzOoL7x2szU5XvRaQ51nJY+D?= =?us-ascii?Q?lEFVfGS3XUR4ReaGRVRBDJRX0qfC4GCcH8pFCPzckfju/qX2cA2/oku2WYxm?= =?us-ascii?Q?BeMsCkBt0hTFkBLQ1jlsQ6bymX43q811CDPuwz6zI7fu98lENylWUnh3S61+?= =?us-ascii?Q?rpMNHMpaWy1+68WBD0bTHDkPWZi61HTSlWCFPjswJeJZpVnn5uuS7MraEaxr?= =?us-ascii?Q?O4qggB+4EgiPG5GaVFrguo9og2YubuBsbNJKwR/LAO4xb9fhaazJcKrcGAnX?= =?us-ascii?Q?vzEUEf1DpqYuIP7Mr23zNQTWh5XfqumO0+5bD+VP+SEaUFDvU4yiTXe6S+8d?= =?us-ascii?Q?vnbwJc1y6HTqAvTpZuD5PWwUMnVvjQta7iFNk9fsZWAFPgRxbtP/RcYp0nJj?= =?us-ascii?Q?/TPSOW/wkMgZ7VvGXnV+htYn/gjgaH7d/J1DLdrMnihLjVJ2cYuShLD05LEb?= =?us-ascii?Q?DQq/IbG530EEDp/c6gVZ1CvAcknXcxPEGP/Qo/2rwmR1SeMqBcmel7DnjE2C?= =?us-ascii?Q?DoGZR0CCJRlmFbC7W4lJmcVtO4kLF6T8wD4qReYmdhAZ+DIORBvrSA8LO9ur?= =?us-ascii?Q?Y/SS+ulwrN1XlZCkiJ3qZx7Uj8dIR4G9QwPPMJ/85TeT22cP5LTR7kSnvJ23?= =?us-ascii?Q?7rmZxQaVaa0zbWPo7FN+v2Hrm95u+9yGYp2Diy+VpZf2he98YPBNT831KFgd?= =?us-ascii?Q?ExtG2s/cbjwhg9UdoRwlUE07gpBSiZG7t3CcqkRT0XpYun3/oElkysyHR0GL?= =?us-ascii?Q?ymZ5YbtkfuLuNqjAZqKbpQySVSvqknbpHayEYB4+PM/O9+4+H5CashkcHQre?= =?us-ascii?Q?CCCtz5q63FFTGK45vwDl9tOnNLGkvJMpBvsZOxzGsk3PJK3VC7Eh4MXLevD8?= =?us-ascii?Q?ijWVm8tAQ/RlGqf3IswP6tXsOktUzbkqXp8KDDysuStjZLd44ra6ATN1zVEQ?= =?us-ascii?Q?qddS8w6+bnXTiDg6WBJQzqhZDLvwDODek7PccmGZmlEoRTlBtCKP9itCoHWI?= =?us-ascii?Q?C1rfHrkmgjTbzG90gprcfyM+W0OOEQe+mqhNyVlzA2IZDvLUXfAc1Qlljucl?= =?us-ascii?Q?NA/ju8w9GyczfMWXUA5dYFnmj2/KwEnLeHdDywcoX45WE4FwmsMCHmKupNDG?= =?us-ascii?Q?OObAB8k28q0EigUbbdohksPDKHaKwVwrcAX6A2HgtMzu8IgHnID26GtRd+Cq?= =?us-ascii?Q?Iyi7rtVDJLHnelZVdFW8jq/Mhb6iDrXarP5WraaxuXzhLHEwl6xiHWMzhTJu?= =?us-ascii?Q?s4+q7Fe0lRFNN2/5dzovyTeW+widLEORvHPVAfTDYw2/zH1gfGwrj1T7j8F6?= =?us-ascii?Q?x+blozGWVs6ff8n65JhXTrXiwj5z+ZYhbJOpyn0cyJGu3ViQS8LGMQJwKUG7?= =?us-ascii?Q?84n4yNGiP/a6m17DVe9+QKftN9fQ7MbWv8/fyoLeavd00L0Z66zmuzBP0Vjx?= =?us-ascii?Q?Farl6rGQtf2D6lNI0Zbq1GJh6bby1tlfKMUD0xBMjiz610IUNSX1NJFSw5+D?= =?us-ascii?Q?7AbrjRCs49LG0eTnXbXS22iNgH9e24gEIEhGchKzdgxOonXBiFhqtYoba+bx?= =?us-ascii?Q?5rbIVkDAtgnyUGDRf8tCdNMgg3mFwpzDogX1jBbxIB37bgnP?= Content-Type: multipart/alternative; boundary="_000_DB9PR06MB7915902CD266B48A6FCB15219E3CADB9PR06MB7915eurp_" MIME-Version: 1.0 X-OriginatorOrg: telefonica.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: DB9PR06MB7915.eurprd06.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 8f7989c8-6854-409d-92e2-08db8ae037ad X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jul 2023 18:19:41.4004 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 9744600e-3e04-492e-baa1-25ec245c6f10 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: CIjlqulZDnKfJmjYbEdL+zar+/vagM819Gf6nJEkv8cNAMbDJP8xqfiV5t7D11+QOLHqU9N66ex9npVxwhtw7Si1mKbx68XEyduLej+xev99zpUb6PZROJUOXQZCIpydZYvJTLfMFlxegdKsAd3o/Q== X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB8PR06MB6554 Archived-At: Subject: Re: [Teas] WG adoption poll: draft-contreras-teas-slice-controller-models-05 X-BeenThere: teas@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: Traffic Engineering Architecture and Signaling working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jul 2023 18:19:51 -0000 --_000_DB9PR06MB7915902CD266B48A6FCB15219E3CADB9PR06MB7915eurp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Kiran Thanks so much for your comments. Not answering to the internal interface comment since I have responded in t= hat respect to Swamy and Adrian's comments, please, check. Regarding your comment on the realizer building block. The reason for consi= dering such building block was to enable the transition from an IETF Networ= k Slice service request which is technology-agnostic, up to the point of be= ing able to use existing (or augmented) network models being supported by n= etwork controllers (please, see draft-barguil-teas-network-slices-instantat= ion for reference). That was the rationale of dividing the actions in those= two building blocks of mapper and realizer. For sure, some other options a= re possible, and the approach followed in this draft does not have the purp= ose of standardizing or constraining the implementation the IETF Network Sl= ice Controller. It only tries to describe a way of going from technology-ab= stracted request received by the NSC up to technology-specific network mode= l supported by a network controller. Respect to your reference to section 6.3, do you refer to the framework doc= ument? Not clear to me. Thanks again, Best regards Luis De: Teas En nombre de Kiran Makhijani Enviado el: martes, 11 de julio de 2023 13:05 Para: Vishnu Pavan Beeram ; TEAS WG CC: TEAS WG Chairs Asunto: Re: [Teas] WG adoption poll: draft-contreras-teas-slice-controller-= models-05 I quickly skimmed through the document and like that how it connects differ= ent pieces of work being done in the WG about network slices, we need somet= hing like this. Therefore, I support this document's adoption. It will hel= p with designing NSC interfaces in a standard way. Fair point raised that internal interface, should not be exposed. At the sa= me time - perhaps my information is outdated, I always thought that NSC sho= uld be technology agnostic and inclusion of realizer in NSC is not entirely= clear ( it could be anywhere - maybe with the network controller). In 6.3 = section of slices... we say a lot about mapping but nothing about the reali= zer. Perhaps, when the document is adopted - we can clarify these aspects. Cheers, Kiran From: Teas > on behalf = of Vishnu Pavan Beeram = > Date: Tuesday, July 4, 2023 at 12:42 PM To: TEAS WG > Cc: TEAS WG Chairs > Subject: [Teas] WG adoption poll: draft-contreras-teas-slice-controller-mod= els-05 All, This is start of a *two* week poll on making draft-contreras-teas-slice-controller-models-05 a TEAS working group docume= nt [https://datatracker.ietf.org/doc/html/draft-contreras-teas-slice-controlle= r-models-05]. Please send email to the list indicating "yes/support" or "no/do not suppor= t". If indicating no, please state your reservations with the document. If yes, please also feel free to provide comments you'd like to see addressed once the document is a WG document. The poll ends July 19th. Thank you, Pavan, Lou and Oscar ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener informaci?n privilegiada o confidencial y es para uso exclusiv= o de la persona o entidad de destino. Si no es usted. el destinatario indic= ado, queda notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia= sin autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente= . Si ha recibido este mensaje por error, le rogamos que nos lo comunique in= mediatamente por esta misma v?a y proceda a su destrucci?n. The information contained in this transmission is confidential and privileg= ed information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this co= mmunication is strictly prohibited. If you have received this transmission = in error, do not read it. Please immediately reply to the sender that you h= ave received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, = pode conter informa??o privilegiada ou confidencial e ? para uso exclusivo = da pessoa ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio in= dicado, fica notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia= sem autoriza??o pode estar proibida em virtude da legisla??o vigente. Se r= ecebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatament= e por esta mesma via e proceda a sua destrui??o ________________________________ Le informamos de que el responsable del tratamiento de sus datos es la enti= dad del Grupo Telef?nica vinculada al remitente, con la finalidad de manten= er el contacto profesional y gestionar la relaci?n establecida con el desti= natario o con la entidad a la que est? vinculado. Puede contactar con el re= sponsable del tratamiento y ejercitar sus derechos escribiendo a privacidad= .web@telefonica.com. Puede consultar = informaci?n adicional sobre el tratamiento de sus datos en nuestra Pol?tica= de Privacidad. We inform you that the data controller is the Telef?nica Group entity linke= d to the sender, for the purpose of maintaining professional contact and ma= naging the relationship established with the recipient or with the entity t= o which it is linked. You may contact the data controller and exercise your= rights by writing to privacidad.web@telefonica.com. You may consult additional information on the processing of= your data in our Privacy Policy. Informamos que o respons?vel pelo tratamento dos seus dados ? a entidade do= Grupo Telef?nica vinculada ao remetente, a fim de manter o contato profess= ional e administrar a rela??o estabelecida com o destinat?rio ou com a enti= dade ? qual esteja vinculado. Voc? pode entrar em contato com o respons?vel= do tratamento de dados e exercer os seus direitos escrevendo a privacidad.= web@telefonica.com. Voc? pode consult= ar informa??o adicional sobre o tratamento do seus dados na nossa Pol?tica = de Privacidade. --_000_DB9PR06MB7915902CD266B48A6FCB15219E3CADB9PR06MB7915eurp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Kiran

 

Thanks so much for your comments.

 

Not answering to the internal interface comment sinc= e I have responded in that respect to Swamy and Adrian’s comments, pl= ease, check.

 

Regarding your comment on the realizer building bloc= k. The reason for considering such building block was to enable the transit= ion from an IETF Network Slice service request which is technology-agnostic, up to the point of being able to use= existing (or augmented) network models being supported by network controll= ers (please, see draft-barguil-teas-network-slices-instantation for referen= ce). That was the rationale of dividing the actions in those two building blocks of mapper and realizer. For sure,= some other options are possible, and the approach followed in this draft does not h= ave the purpose of standardizing or constraining the implementation the IET= F Network Slice Controller. It only tries to describe a way of going from t= echnology-abstracted request received by the NSC up to technology-specific network model supported by a network = controller.

 

Respect to your reference to section 6.3, do you refer to the framewo= rk document? Not clear to me.

 

Thanks again,

 

Best regards

 

Luis

 

 

 

De: Teas <teas-bounces@ietf.org> En nombre de Kiran Makhijani
Enviado el: martes, 11 de julio de 2023 13:05
Para: Vishnu Pavan Beeram <vishnupavan@gmail.com>; TEAS WG <= ;teas@ietf.org>
CC: TEAS WG Chairs <teas-chairs@ietf.org>
Asunto: Re: [Teas] WG adoption poll: draft-contreras-teas-slice-cont= roller-models-05

 

I qu= ickly skimmed through the document and like that how it connects different = pieces of work being done in the WG about network slices, we need something= like this. Therefore, I support this document’s adoption.  It will help with designing NSC interface= s in a standard way.

 

Fair= point raised that internal interface, should not be exposed. At the same t= ime - perhaps my information is outdated, I always thought that NSC should = be technology agnostic and inclusion of realizer in NSC is not entirely clear ( it could be anywhere – maybe= with the network controller). In 6.3 section of slices… we say a lot= about mapping but nothing about the realizer.

 

Perh= aps, when the document is adopted – we can clarify these aspects.

Chee= rs,

Kira= n

 

From: Teas= <teas-bounces@ietf.org>= on behalf of Vishnu Pavan Beeram <vishnupavan@gmail.com>
Date: Tuesday, July 4, 2023 at 12:42 PM
To: TEAS WG <teas@ietf.org&g= t;
Cc: TEAS WG Chairs <teas-= chairs@ietf.org>
Subject: [Teas] WG adoption poll: draft-contreras-teas-slice-control= ler-models-05

All,=

This is start of a *two* week poll on making
draft-contreras-teas-slice-controller-models-05 a TEAS worki= ng group document


Please send email to the list indicating "yes/support" or "n= o/do not support".
If indicating no, please state your reservations with the document. If
yes, please also feel free to provide comments you'd like to see
addressed once the document is a WG&nb= sp;document.

The poll ends July 19th.

Thank you,
Pavan, Lou and Oscar



Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu= ede contener información privilegiada o confidencial y es para uso e= xclusivo de la persona o entidad de destino. Si no es usted. el destinatari= o indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorizaci&o= acute;n puede estar prohibida en virtud de la legislación vigente. S= i ha recibido este mensaje por error, le rogamos que nos lo comunique inmed= iatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is confidential and privileg= ed information intended only for the use of the individual or entity named = above. If the reader of this message is not the intended recipient, you are= hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If y= ou have received this transmission in error, do not read it. Please immedia= tely reply to the sender that you have received this communication in error= and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat&aacut= e;rio, pode conter informação privilegiada ou confidencial e = é para uso exclusivo da pessoa ou entidade de destino. Se não= é vossa senhoria o destinatário indicado, fica notificado de= que a leitura, utilização, divulgação e/ou có= pia sem autorização pode estar proibida em virtude da legisla= ção vigente. Se recebeu esta mensagem por erro, rogamos-lhe q= ue nos o comunique imediatamente por esta mesma via e proceda a sua destrui= ção


Le informamos de que el responsable del tratamiento de sus datos es la enti= dad del Grupo Telefónica vinculada al remitente, con la finalidad de= mantener el contacto profesional y gestionar la relación establecid= a con el destinatario o con la entidad a la que está vinculado. Puede contactar con el responsable del tratamiento = y ejercitar sus derechos escribiendo a privacidad.web@telefonica.= com. Puede consultar información adicional sobre el tratamiento = de sus datos en nuestra Política de Privacidad.

We inform you that the data controller is the Telefónica Group entit= y linked to the sender, for the purpose of maintaining professional contact= and managing the relationship established with the recipient or with the e= ntity to which it is linked. You may contact the data controller and exercise your rights by writing to privacidad.web@telefonica.com. You may consult additional information o= n the processing of your data in our Privacy Policy.

Informamos que o responsável pelo tratamento dos seus dados é= a entidade do Grupo Telefónica vinculada ao remetente, a fim de man= ter o contato professional e administrar a relação estabeleci= da com o destinatário ou com a entidade à qual esteja vincula= do. Você pode entrar em contato com o responsável do tratamento de dados e e= xercer os seus direitos escrevendo a privacidad.web@telefonica.= com. Você pode consultar informação adicional sobre= o tratamento do seus dados na nossa Política de Privacidade.

--_000_DB9PR06MB7915902CD266B48A6FCB15219E3CADB9PR06MB7915eurp_--