Re: [nmrg] FYI/Qs: liaison on ITU-T work on intent based networking (SG13-LS181)

Alexander Clemm <alex@futurewei.com> Thu, 01 October 2020 17:36 UTC

Return-Path: <alex@futurewei.com>
X-Original-To: nmrg@ietfa.amsl.com
Delivered-To: nmrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E2193A117E for <nmrg@ietfa.amsl.com>; Thu, 1 Oct 2020 10:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.09
X-Spam-Level:
X-Spam-Status: No, score=-2.09 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, RCVD_IN_MSPIKE_H2=-0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.com
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 5KxolUZVwfhO for <nmrg@ietfa.amsl.com>; Thu, 1 Oct 2020 10:36:12 -0700 (PDT)
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (mail-bn8nam11on2123.outbound.protection.outlook.com [40.107.236.123]) (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 44F6B3A117C for <nmrg@irtf.org>; Thu, 1 Oct 2020 10:36:12 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=HA7VYTfP9Sg6Z+6rydYdpn0Qpb2V+NdU0EuMY1eKDV+fsuyZ7FCzydxI8R+Qhi6eOiBVPoBvTVvyLm3GIKSZWxEOJE9RajKAQRfYptpMoJrIAHYitfpthUPChEo5r0IFECltL+8P2+q0x6p0NUBc9nqOXH85ntBrdfw6iHwwoX6S0H5KTyH5tYr/pgmG/3pfX0orN95eTzwbZEgJ+Ah6RIwjev7TybfVq16KLYIE4g8HP8MFQkg312tsU03uNIsBm+St/tm/b2+HrvqZZ9bJueKhtXVb+LYViywwQ66jpEC5IYQxnpgTHOKw1UfSvKqH0TPk2KMgK4VRXa33eA2BLQ==
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-SenderADCheck; bh=8hL0wOpbxdvq9LnpYBd0RqhaFrWPivRp2Kp6EOlX5Sg=; b=PRp642seAiN31FvbSvON33hGHFUCk1gaTNbZQtYx5tjtX1RTFthIdv3+iwHOKVAjBozdFzopxDx9yzH2H71tSLz/1wg6T/Rh/Tzs39cUJOVI8+Al6sIPCDT2JxrSbEQq13bAjhAGWNCg7DT6cK35qhM2xlOyLCAXWc5CaRj/bEjrPWA0zKFHR+D0NT6KIPjDNPXqjhs9uRmshY4oZYZMcFzIBcAmlSfIQcHzGGH7TXNwpa9FII7nsr1MkHvr9EQU3vvKJQpmGF5XjD7g19PYrgvZJWkj4If9T0YfrQyf/U3yqKX/Sn1WxU4rvtGx8iq0828MtvNGOs+R7eCxJHmrLw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=8hL0wOpbxdvq9LnpYBd0RqhaFrWPivRp2Kp6EOlX5Sg=; b=Vfi0Jhm8BeI0T542GCwW/t9OldlAh9latN0EJD4pdn99RRAG6rrMLYKocymHoBfUZeqEGHO68qZrNBCGFl1KSo3qUuo+BPWrQBKyZTtsciITcvPuGE35xMOfGlmcOLyg2Nzly5HYMSBFJPQmP6h133O6dm0xAnOFqE7/QM3hMfY=
Received: from BY5PR13MB3793.namprd13.prod.outlook.com (2603:10b6:a03:226::15) by BY5PR13MB3378.namprd13.prod.outlook.com (2603:10b6:a03:1a4::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.13; Thu, 1 Oct 2020 17:36:09 +0000
Received: from BY5PR13MB3793.namprd13.prod.outlook.com ([fe80::f0f3:2a3f:eaf2:6f26]) by BY5PR13MB3793.namprd13.prod.outlook.com ([fe80::f0f3:2a3f:eaf2:6f26%5]) with mapi id 15.20.3433.035; Thu, 1 Oct 2020 17:36:08 +0000
From: Alexander Clemm <alex@futurewei.com>
To: Scott Mansfield <scott.mansfield=40ericsson.com@dmarc.ietf.org>, Toerless Eckert <tte@cs.fau.de>, "nmrg@irtf.org" <nmrg@irtf.org>, "anima@ietf.org" <anima@ietf.org>
CC: "chair@ietf.org" <chair@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "zhangy88@chinatelecom.cn" <zhangy88@chinatelecom.cn>, "tsbsg13@itu.int" <tsbsg13@itu.int>
Thread-Topic: FYI/Qs: liaison on ITU-T work on intent based networking (SG13-LS181)
Thread-Index: AQHWl+uqvxSU+hTKs0eHPyGDBwebC6mC/0ZQ
Date: Thu, 01 Oct 2020 17:36:08 +0000
Message-ID: <BY5PR13MB3793463E22404F880CA4F741DB300@BY5PR13MB3793.namprd13.prod.outlook.com>
References: <20201001115730.GA38103@faui48f.informatik.uni-erlangen.de> <BL0PR1501MB413049DEF336344E748378908B300@BL0PR1501MB4130.namprd15.prod.outlook.com>
In-Reply-To: <BL0PR1501MB413049DEF336344E748378908B300@BL0PR1501MB4130.namprd15.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=futurewei.com;
x-originating-ip: [73.189.160.186]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ee1703bc-c202-4920-7d08-08d866307b80
x-ms-traffictypediagnostic: BY5PR13MB3378:
x-microsoft-antispam-prvs: <BY5PR13MB33784F96825A7C2413AEBF09DB300@BY5PR13MB3378.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: FVu0oa/IhchAoZbVttVuutxxc9u8oquFmBw48fDG1yr3rs4qJofrqZG4bxd8Yticn0ngXshqEvsIvv+IgSIxdc8CSxCQ0dxBsEPNRWb98Cl+c+BU4FLfQYCfPaQNO8gzfEIu8owfbFKiUMEmKgD6cQpaed8ejDG+j9dfbNrVxHTqhY8K7C4dODvae7DKFzrT6W/bnH1PBZUFw2a5zAbAg3Y2eZgByaIh4rceswuzEfTFipDXC4ZZJzaocJ5ocUk6Xq3/LlB6kgIlDQiejsKDWq7E+tm47OdbmtueLAmPrGTR619RegOXU9VicwLGAX5DoqBzbbK0FdEvuMLvikiZp9vBW83ZxfEcJyYbF5M8SnAQOwjezuZu+eFxkqxWLYOzBWTt5n9qVcRweQay8Kkkyg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BY5PR13MB3793.namprd13.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(396003)(366004)(346002)(39840400004)(136003)(376002)(71200400001)(64756008)(66556008)(66446008)(83080400001)(83380400001)(316002)(66476007)(54906003)(52536014)(66946007)(6506007)(110136005)(76116006)(478600001)(45080400002)(86362001)(5660300002)(55016002)(26005)(4326008)(7696005)(53546011)(186003)(2906002)(9686003)(8936002)(966005)(33656002)(8676002); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: QeF9rFf9nQJvCC0xs2wgXmKR+Iuhox9yAi3AXbNH3soAkHzuF9smUh9C81ayG/kT+SNmo6kx7J0wZgZqQp9sIcTp0+flZTyKUAipsRrNkKHYlmnqo8A6Le5WBGj2ivShv0CMp7xqQjHT8bBVTJ+9RbCj4YgSWde/rCqWAx9f4BGWYvXBfp2EWb1fVyQ9FHXR0/vOjLf6c+eLdfIQe8vCbl5xA0Xy3zTNdJxJu9TH//fV9z/Yh09RnZtqT2n+wgSTv6pILbslTgX/Z4PyqI5OmNuZuSvo3tAeYbIjsr2sE1Rr97oBUQepVyPwGSztwCzEwd/A1xWRr+XmlW+hOW/Cn1D+4rr3iy9wVFneEv3MUlxkdczXlEwpJNlHyVLjQLWeKjkknP87oRuOdcrDcPoLRnMko65AdMciob82qx/5Igq3TsVtRqwZuuJvol1nwUAcPsVPlB+CT1afUjWdy4M3jRvzDc6OdsBOx8bHV1PCPuKY2cbAqAImVc5mDFN7seW0My1UC+pgb4uqY/G3BDxFkgvJ6fVfUCdpmC9EhfypLZYvKHeND4VbKftuJMiKDm6C2I3BLlepHIYS/BsBaBVkr3hlWCxnegNGwPRSy99P5kmqQyP958eevi+sGEQIExLJoLGZceAgUCDKQqEEt8fn8A==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BY5PR13MB3793.namprd13.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ee1703bc-c202-4920-7d08-08d866307b80
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Oct 2020 17:36:08.7296 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: CwjtmQjYhU/GUIgGXx00CdpbIOcshBZ4CifAdumtrB2XGQLStgNVlhhvHOM4c+5ToZ/jNRkSnlaMYV+aCWfC2g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR13MB3378
Archived-At: <https://mailarchive.ietf.org/arch/msg/nmrg/y_pN2WAHWzvBEHtdlJpQIS7nxcE>
Subject: Re: [nmrg] FYI/Qs: liaison on ITU-T work on intent based networking (SG13-LS181)
X-BeenThere: nmrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Management Research Group discussion list <nmrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nmrg>, <mailto:nmrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nmrg/>
List-Post: <mailto:nmrg@irtf.org>
List-Help: <mailto:nmrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nmrg>, <mailto:nmrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Oct 2020 17:36:16 -0000

The attachment to the liaison statement refers to a draft that I am a coauthor of, and that is relevant to their work.  Clearly it would be great to have them engage, provide feedback, reach out to us to see if there are common interests to explore.  They could presumably do already simply using the author contact information that is given in the draft, but given this liaison route is taken instead, I am not sure of its purpose and what if any expectations to respond would be?  As Toerless indicates, the audience for this is in nmrg and anima, so it seems perhaps they should be simply directed to those working groups?
--- Alex

-----Original Message-----
From: nmrg <nmrg-bounces@irtf.org> On Behalf Of Scott Mansfield
Sent: Thursday, October 1, 2020 5:09 AM
To: Toerless Eckert <tte@cs.fau.de>; nmrg@irtf.org; anima@ietf.org
Cc: chair@ietf.org; iesg@ietf.org; zhangy88@chinatelecom.cn; tsbsg13@itu.int
Subject: Re: [nmrg] FYI/Qs: liaison on ITU-T work on intent based networking (SG13-LS181)

To answer the liaison question.

When liaisons from the ITU-T come in, I request suggestions about the groups they should be circulated to, if it isn't specific to a group.  If there is a desire for a response or coordination, the senders can directly contact me to help pull together/identify interested parties.  Same is true in the other direction.  If the IETF sends a liaison to the ITU-T, it is very important that an individual that is interested in the topic be available in the ITU-T meeting to present and coordinate action.  If the liaison is just for information, then there may be no need for that level of interaction.

The working methods of the ITU-T and the IETF are significantly different, but one thing is the same.  Results are driven by people that are motivated to get something done.  The liaison officers can help connect people, but there needs to be people that are experts in the subject matter to progress the work.

Regards,
-scott.

-----Original Message-----
From: Toerless Eckert <tte@cs.fau.de>
Sent: Thursday, October 1, 2020 7:58 AM
To: nmrg@irtf.org; anima@ietf.org
Cc: chair@ietf.org; iesg@ietf.org; Scott Mansfield <scott.mansfield@ericsson.com>; zhangy88@chinatelecom.cn; tsbsg13@itu.int
Subject: FYI/Qs: liaison on ITU-T work on intent based networking
(SG13-LS181)

FYI: anima, nmrg

  The ITU-T work about scenarios and requirements for intent based networking (SG13-LS181) might be
  of interest to participants to NMRG, ANIMA (if of RG/WG also work on this, pls. let me know and
  forward). I also just stumbled across it due to the following liaison statement posted on datatracker
  and did not have the time to read the work:

  https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fliaison%2F1696%2F&amp;data=02%7C01%7Calex%40futurewei.com%7C3c8cffeebbdb4c89efb708d86602cb45%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637371509493678189&amp;sdata=J03X6EhyIr4nqUnTk97OxwMlLiEdnIYORlmWezf2qhc%3D&amp;reserved=0

CC Q: (chair, IESG, Scott, Zhang):

  Q1: I am somewhat clueless about the liaison statement. I see some liasons being Cc'ed widely
  to interested parties in the IETF, whereas this liaison is not copied to any actual
  groups other than leadership. How is distribution and response responsibility being decided on ?

  Q2: IETF/IRTF has done / is doing work on intent and network archtiectures planning to suport
  intent, for example in NMRG and ANIMA (maybe other WGs as well). What is the appropriate way to
  let ITU-T know about this (if such dissemination of information is of interest to IETF at all... ?)

Cheers
    Toerless