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 C1145C151071; Mon, 23 Sep 2024 10:15:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.206 X-Spam-Level: X-Spam-Status: No, score=-4.206 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no 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 Z9VugPJQ7-Tp; Mon, 23 Sep 2024 10:15:41 -0700 (PDT) Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA072C14F694; Mon, 23 Sep 2024 10:15:41 -0700 (PDT) Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4XC8km6Yjrz6K78W; Tue, 24 Sep 2024 01:15:12 +0800 (CST) Received: from frapeml500004.china.huawei.com (unknown [7.182.85.22]) by mail.maildlp.com (Postfix) with ESMTPS id 0DE371400DB; Tue, 24 Sep 2024 01:15:39 +0800 (CST) Received: from frapeml500001.china.huawei.com (7.182.85.94) by frapeml500004.china.huawei.com (7.182.85.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Mon, 23 Sep 2024 19:15:38 +0200 Received: from frapeml500001.china.huawei.com ([7.182.85.94]) by frapeml500001.china.huawei.com ([7.182.85.94]) with mapi id 15.01.2507.039; Mon, 23 Sep 2024 19:15:38 +0200 From: Olga Havel To: "mohamed.boucadair@orange.com" , "nmop@ietf.org" Thread-Topic: (Concluded) RE: Call for adoption: draft-havel-nmop-digital-map-concept (Ends 23/09/2024) Thread-Index: AdsCu6AF+g6bzYnQSlONH26EXsdEfQKxLpTQABbhaLA= Date: Mon, 23 Sep 2024 17:15:38 +0000 Message-ID: <766fea3f7d664f04be0792ff9f4a5241@huawei.com> References: In-Reply-To: Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.206.138.71] Content-Type: multipart/alternative; boundary="_000_766fea3f7d664f04be0792ff9f4a5241huaweicom_" MIME-Version: 1.0 Message-ID-Hash: FFUBFSR24WZU37ZGI73VRRTUITWOTDWK X-Message-ID-Hash: FFUBFSR24WZU37ZGI73VRRTUITWOTDWK X-MailFrom: olga.havel@huawei.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-teas.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: "TEAS WG (teas@ietf.org)" , "nmop-chairs@ietf.org" , "draft-havel-nmop-digital-map-concept@ietf.org" X-Mailman-Version: 3.3.9rc4 Precedence: list Subject: =?utf-8?q?=5BTeas=5D_Re=3A_=28Concluded=29_RE=3A_Call_for_adoption=3A_draft-?= =?utf-8?q?havel-nmop-digital-map-concept_=28Ends_23/09/2024=29?= List-Id: Traffic Engineering Architecture and Signaling working group discussion list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --_000_766fea3f7d664f04be0792ff9f4a5241huaweicom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thanks Med, I will add access for other authors and we will submit the ietf= draft. Best regards, Olga From: mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com] Sent: Monday 23 September 2024 07:18 To: nmop@ietf.org Cc: TEAS WG (teas@ietf.org) ; nmop-chairs@ietf.org; draft-ha= vel-nmop-digital-map-concept@ietf.org Subject: (Concluded) RE: Call for adoption: draft-havel-nmop-digital-map-co= ncept (Ends 23/09/2024) Hi all, This message concludes this call for adoption. There was good support to proceed with adoption. There were also some few c= omments that we trust the authors will consider and address as appropriate.= Those are recorded in github as issues. @authors, please submit the draft as ** draft-ietf-nmop-digital-map-concept= ** with the same content as draft-havel-nmop-digital-map-concept-00. We ha= ve already pre-approved the submission. FWIW, we created a Github repo for this draft: https://github.com/ietf-wg-n= mop/draft-ietf-nmop-digital-map-concept. Olga, you have the admin rights fo= r this repo. Please make sure your co-authors/contributors have also access= . Thanks. Cheers, Med De : mohamed.boucadair@orange.com > Envoy=E9 : lundi 9 septembre 2024 15:28 =C0 : nmop@ietf.org Cc : TEAS WG (teas@ietf.org) >; nmop-chairs@ietf.org; draft-hav= el-nmop-digital-map-concept@ietf.org Objet : Call for adoption: draft-havel-nmop-digital-map-concept (Ends 23/09= /2024) Hi all, This message starts a 2-week call for adoption for https://datatracker.ietf= .org/doc/draft-havel-nmop-digital-map-concept/. Please reply to this message by indicating whether you support or not the a= doption of this draft. Comments to motivate your preference are highly appr= eciated. FWIW: * No IPR was disclosed for the draft [1] * There was fair support to adopt the doc per a poll in Vancouver [2] The call is also cced to TEAS; replies should be sent to NMOP. The call will run till 23 September 2024. Thank you Med [1] https://github.com/ietf-wg-nmop/Logistic/blob/main/ipr-poll-cfa/draft-h= avel-nmop-digital-map-concept.md [2] https://datatracker.ietf.org/doc/minutes-120-nmop-202407262000/ ___________________________________________________________________________= _________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles 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 el= ectroniques 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 inf= ormation 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 dele= te 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. ___________________________________________________________________________= _________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles 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 el= ectroniques 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 inf= ormation 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 dele= te 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. --_000_766fea3f7d664f04be0792ff9f4a5241huaweicom_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Thanks Med, I will add= access for other authors and we will submit the ietf draft.

 

Best regards,

Olga=

 

From: mohamed.boucadair@orange.com [mailto:= mohamed.boucadair@orange.com]
Sent: Monday 23 September 2024 07:18
To: nmop@ietf.org
Cc: TEAS WG (teas@ietf.org) <teas@ietf.org>; nmop-chairs@ietf.= org; draft-havel-nmop-digital-map-concept@ietf.org
Subject: (Concluded) RE: Call for adoption: draft-havel-nmop-digital= -map-concept (Ends 23/09/2024)

 

= Hi all,

=  

= This message concludes this call for adoption.

=  

= There was good support to proceed with adoption. There were also some few c= omments that we trust the authors will consider and address as appropriate.= Those are recorded in github as issues.

=  

= @authors, please submit the draft as ** draft-ietf-nmop-digital-map-concept= ** with the same content as draft-havel-nmop-digital-map-concept-00. We ha= ve already pre-approved the submission.

=  

= FWIW, we created a Github repo for this draft: https://github.com/ietf-wg-nmop/draft-ietf-nmop-digital-map-concept. Olga, you have the admin rights for this repo. Please make sure your co-= authors/contributors have also access. Thanks.

=  

= Cheers,

= Med

=  

De : mohamed.boucadair@orange.co= m <mohamed.boucadair= @orange.com>
Envoy=E9 : lundi 9 septembre 2024 15:28
=C0 : nmop@ietf.org
Cc : TEAS WG (teas@ietf.org) <teas@ietf.org>; nmop-chairs@ietf.org; draft-havel-nmop-digital-map-concept@ietf.org
Objet : Call for adoption: draft-havel-nmop-digital-map-concept= (Ends 23/09/2024)

 

= Hi all,

=  

= This message starts a 2-week call for adoption for https://datatracker.ietf.org/doc/draft-havel-nmop-digital-map-concept/.=

=  

= Please reply to this message by indicating whether you support or not the a= doption of this draft. Comments to motivate your preference are highly appr= eciated.

=  

= FWIW:

=  

=   * No IPR was disclosed for the draft [1]

=   * There was fair support to adopt the doc per a poll in Vancouver [2= ]

=  

= The call is also cced to TEAS; replies should be sent to NMOP.

=  

= The call will run till 23 September 2024.

=  

= Thank you

= Med

=  

= [1] https://github.com/ietf-wg-nmop/Logistic/blob/main/ipr-poll-cfa/draft-havel= -nmop-digital-map-concept.md

= [2] https://datatracker.ietf.org/doc/minutes-120-nmop-202407262000/ 

____________________________________________________=
________________________________________________________<=
/pre>

Ce message et ses pieces jointes peuvent contenir de=
s informations confidentielles ou privilegiees et ne doivent donc


pas etre diffuses, exploites ou copies sans autorisa=
tion. Si vous avez recu ce message par erreur, veuillez le signaler


a l'expediteur et le detruire ainsi que les pieces j=
ointes. 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 confide=
ntial or privileged information that may be protected by law;


they should not be distributed, used or copied witho=
ut authorisation.


If you have received this email in error, please not=
ify the sender and delete this message and its attachments.


As emails may be altered, Orange is not liable for m=
essages that have been modified, changed or falsified.

Thank you.


____________________________________________________=
________________________________________________________<=
/pre>

Ce message et ses pieces jointes peuvent contenir de=
s informations confidentielles ou privilegiees et ne doivent donc


pas etre diffuses, exploites ou copies sans autorisa=
tion. Si vous avez recu ce message par erreur, veuillez le signaler


a l'expediteur et le detruire ainsi que les pieces j=
ointes. 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 confide=
ntial or privileged information that may be protected by law;


they should not be distributed, used or copied witho=
ut authorisation.


If you have received this email in error, please not=
ify the sender and delete this message and its attachments.


As emails may be altered, Orange is not liable for m=
essages that have been modified, changed or falsified.

Thank you.
--_000_766fea3f7d664f04be0792ff9f4a5241huaweicom_--