Re: [6lo] Initial version of the minutes from 6lo at IETF 113

Carles Gomez Montenegro <carlesgo@entel.upc.edu> Fri, 01 April 2022 10:07 UTC

Return-Path: <carlesgo@entel.upc.edu>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 213F53A0BD1 for <6lo@ietfa.amsl.com>; Fri, 1 Apr 2022 03:07:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 fzTHkjP_WcS2 for <6lo@ietfa.amsl.com>; Fri, 1 Apr 2022 03:06:56 -0700 (PDT)
Received: from dash.upc.es (dash.upc.es [147.83.2.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CC093A0C0B for <6lo@ietf.org>; Fri, 1 Apr 2022 03:06:55 -0700 (PDT)
Received: from entelserver.upc.edu (entelserver.upc.es [147.83.40.4]) by dash.upc.es (8.14.4/8.14.4/Debian-4.1ubuntu1.1) with ESMTP id 231A6eXR028746; Fri, 1 Apr 2022 12:06:40 +0200
Received: from webmail.entel.upc.edu (webmail.entel.upc.edu [147.83.40.6]) by entelserver.upc.edu (Postfix) with ESMTP id C020E1D53C1; Fri, 1 Apr 2022 12:06:39 +0200 (CEST)
Received: from 79.158.126.207 by webmail.entel.upc.edu with HTTP; Fri, 1 Apr 2022 12:06:41 +0200
Message-ID: <447d74dad1c69ecbd2dbf5bd010577ec.squirrel@webmail.entel.upc.edu>
In-Reply-To: <c95ea00ea1dd416fbb0d5551b3f6d6e4@huawei.com>
References: <b57462023c9a488b91400b6a591ab37d.squirrel@webmail.entel.upc.edu> <c95ea00ea1dd416fbb0d5551b3f6d6e4@huawei.com>
Date: Fri, 01 Apr 2022 12:06:41 +0200
From: Carles Gomez Montenegro <carlesgo@entel.upc.edu>
To: "Liguangpeng (Roc, Network Technology Laboratory)" <liguangpeng@huawei.com>
Cc: "6lo@ietf.org" <6lo@ietf.org>, Luigi IANNONE <luigi.iannone@huawei.com>
User-Agent: SquirrelMail/1.4.21-1.fc14
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: clamav-milter 0.103.5 at dash
X-Virus-Status: Clean
X-Greylist: Delayed for 24:03:50 by milter-greylist-4.3.9 (dash.upc.es [147.83.2.50]); Fri, 01 Apr 2022 12:06:40 +0200 (CEST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/0Wy_Xq3r6ExdZBX6lvfy-8oVceA>
Subject: Re: [6lo] Initial version of the minutes from 6lo at IETF 113
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2022 10:07:00 -0000

Dear Guangpeng,

Thanks for your message!

You are right.

After double checking the recording, we have updated the minutes as follows:

OLD:
     Carles: other additions needed to the draft?
     Guangpeng: security

NEW:
     Carles: is this technology for constrained devices?
     Guangpeng: used in industrial equipment

The new version of the minutes can be found here:
https://datatracker.ietf.org/meeting/113/materials/minutes-113-6lo-01.txt

Should you have further comments, please do not hesitate to let us know.

Cheers,

Shwetha and Carles





> Dear Chairs and all,
>
> Thanks chairs and minutes takers. Maybe it's fault of my pronunciation, I
> don't think we discussed any topic about security. If I remembered, in
> that time we discussed constrained devices and more general case, which
> one is the typical use cases of APL. Maybe we should correct the following
> lines a bit.
>
> [11:40] Native Short Address for LLN Expansion (Luigi Iannone ) 15 min
>
>     goes through changes since IETF112
>     applicability mostly in static deployment, otherwise, need to
> renumber.
>     next: will try to evaluate gain with this approach; will respond to
> latest comments.
>     then will consider asking for adoption
>     Carles: draft states applicability for static deployment of wired
> technologies. PLC?
>     Luigi: some others, will do literature review
>     Guangpeng: PLC, also APL (Advanced Physical Layer) which is extension
> of 802.3cg
>>    Carles: other additions needed to the draft?
>>    Guangpeng: security
>     Peng Liu: support this work
>
> Thanks,
> Guangpeng Li