
From nobody Mon Oct  2 19:54:15 2017
Return-Path: <suresh.krishnan@gmail.com>
X-Original-To: int-dir@ietfa.amsl.com
Delivered-To: int-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3450B1342FA; Mon,  2 Oct 2017 19:53:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 CxZDAknrCab8; Mon,  2 Oct 2017 19:53:48 -0700 (PDT)
Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::234]) (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 8CC481342F5; Mon,  2 Oct 2017 19:53:48 -0700 (PDT)
Received: by mail-qt0-x234.google.com with SMTP id b21so4733946qte.2; Mon, 02 Oct 2017 19:53:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=b1Uti1sHm8nCHQf24gwJuWB9MEBq4wvMkGqBp4H6Bgc=; b=umLp7oSAmBe2rJK++fJv5Bcf5x3DzFsZvfLWoHVoyADse8BF4uzDFnx1vEwHGed36m lRCWVCD/JmhkXZTdylwszT9IFCoKMT2LDVkFejAW7E3F89JwkdBbZK7ydeGw4JVckgjt d+Gl/RT2YAEH/wmpunuOjqr6id0XKmo2YYa1u6Bv+5VzkKC5NQBPxLIgq2VTkXzX/WTm pVHCLVlEfECJ+BCBuQ4Rp2M5YWtPRllmj3uszuLDQV8SLgaqqc8FKl+b8ol6N0/DGMVG 6BXFP9yulgOZ83FCtAo9etJosL9Km+IUWrdodj+LkIOSzrNdjFPSKhPNDN/NvTZQtgji WKqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=b1Uti1sHm8nCHQf24gwJuWB9MEBq4wvMkGqBp4H6Bgc=; b=DUq+zU0vqMpWMpaKJvunNreT7usxfr0tRE89Gjckvq3iLZBGWP66m4kt4reaVDHTFs UcZKPWq03H6yiAbmMiw0EvVBJC8EOBnrGvKPUlu2XDyyWWgP0HxrN99flPVfg1twkaf8 v7uQEVF3rSAQjJ4YKhjXSIy1AwZR+sJ2MS1L+8IA4RzPC/x+lVdUTHjpTQD3KwkdobIV jKQ1ud8OUOvT5HGzJOzlik+gG0nQQ2fhaj0XKC/rzZGmyUdh0JLjZlzpWVnF9pmPkqYQ bMQ3wL4WzdqeHSP+WeNve8kDwaCOM03Do69oMVFRrFJ48Kb8lN64GbWO7ncY7KjRZhAU FTPA==
X-Gm-Message-State: AHPjjUhd/p3pYCV8JH+B4X0GlPYWNDTDRN85KKr2KmGw06CMheSlvMxy muOC2xp9EypYv/vGrklMW8+Aoo18snc=
X-Google-Smtp-Source: AOwi7QBV+uzm3KcJwSwtK0/U7Wcy3PlmNMBEcjlOeAdkuDVKsNCiQUohCj5ICPZWGGXZdPmtU27gTQ==
X-Received: by 10.129.78.207 with SMTP id c198mr14223215ywb.121.1506999227029;  Mon, 02 Oct 2017 19:53:47 -0700 (PDT)
Received: from [10.0.0.12] (45-19-110-76.lightspeed.tukrga.sbcglobal.net. [45.19.110.76]) by smtp.gmail.com with ESMTPSA id h129sm4647621ywb.67.2017.10.02.19.53.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Oct 2017 19:53:46 -0700 (PDT)
From: Suresh Krishnan <suresh.krishnan@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Message-Id: <EF35AFF4-B2BA-4DB1-8C3D-6614A21A535B@gmail.com>
Date: Mon, 2 Oct 2017 22:53:45 -0400
To: 6lo@ietf.org, 6man WG <ipv6@ietf.org>, 6tisch@ietf.org, int-area <int-area@ietf.org>, int-dir@ietf.org, iot-dir@ietf.org, its@ietf.org, lp-wan@ietf.org, lwip@ietf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/vDKm_Qr1f_GBVc2aIUki9Qj8TPw>
Subject: [Int-dir] Liaison statement received from ITU-T regarding a "Reference Model of IPv6 Addressing Plan for Internet of Things Deployment"
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Oct 2017 02:53:50 -0000

Hi all,
  The IETF has received a liaison statement from the ITU-T that their =
Study Group SG20 is inviting inputs from the IETF regarding a work item =
titled "Reference Model of IPv6 Addressing Plan for Internet of Things
Deployment=E2=80=9D and the deadline for providing inputs is 2018/01/28. =
The statement can be found at=20

https://datatracker.ietf.org/liaison/1546/

I have no further info and I am trying to get access to the referenced =
documents. I just want to provide a heads up while that is in process.

Thanks
Suresh



From nobody Tue Oct  3 08:19:48 2017
Return-Path: <samitac.ietf@gmail.com>
X-Original-To: int-dir@ietfa.amsl.com
Delivered-To: int-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BD22134B7C; Tue,  3 Oct 2017 01:42:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 a8UJTZsjCbAH; Tue,  3 Oct 2017 01:42:23 -0700 (PDT)
Received: from mail-ua0-x236.google.com (mail-ua0-x236.google.com [IPv6:2607:f8b0:400c:c08::236]) (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 9DA4D132F3E; Tue,  3 Oct 2017 01:42:23 -0700 (PDT)
Received: by mail-ua0-x236.google.com with SMTP id i35so2107095uah.9; Tue, 03 Oct 2017 01:42:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2oLfJMVJk+OBVg8Au/bT6/U2CSf3PkxgQSFq/HxrNi0=; b=uWnSOr8cm3y1NSRI+J/pz6+wtxZAsmN3kmSQz55tWxd/arrfEGAdKEoVO2LbzUcKlB bsU6ZhJlhc6idmXOGmdV/k0SOHTBqPKVFLn0lJmoeSLLd3wgpCRdprNBQbxalS+v94uG 0Yg6CVV+5A6TWYJLZh69eOwxsmaHmFqEvXxA6R64nZh7KCOR2Obk7z2FCjSJMP7aU+w/ NG4jWbFQtAvJsRmSR7eS4oYrNrrHNyEgw5iov+pmGJbL8VMAHe0LRhku7H57nR9OvSeV vlwzFCWVUQvUO1mdcRSdvra/yhThrl7ZOHHaajqjrvMYS/sH+rE2UQPLWxt6lJlkW0PC ypiQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=2oLfJMVJk+OBVg8Au/bT6/U2CSf3PkxgQSFq/HxrNi0=; b=qnnyzMZOyCCPpZSNyFr7bpKCh9ubdIgaaql+Mt75ZxPa6Gsr712Qt9c7CLyR7DESKY F7Mbtv3nK4dqnnToJVE1YFzQ+glrgFz4F7weFekYTxIM4uyg269o9rahSmpwdxyGZc3w gMxY6FmzLXj9bozoJGrxTSfUOgY4yjCU542FuAR70vnpXbHgWAZ0ciRTex/ohuJa9L+r jyN8hDT3CmnvIkrAQszQj/fxNwslhA517mNXPpCqUXaTwh8/TSVQlcvSA6Q890sI/8Ws Dsh2wev7cJFdhT67FNQxTGvI0SGER+XsX5ppNKx7wBVQLyPgF1nRi0gOzFS9a79cNIyq RhnA==
X-Gm-Message-State: AHPjjUisfeR4V0fllef6S/Jy9UkFbMiotBlh8DR+lvocUC0aBngJHjS/ /h3bZl+HT437DZZ+HP0jRAM3Rb2u2qkpusQK6W0=
X-Google-Smtp-Source: AOwi7QCf8ThsbM5r4Ny7YD/Ef+qLl1jFxqUL+bphvkQFzwrNg5NjpGvlVqKlRU/x8Tl0YX19BiNUmChtrHEKi16wd3k=
X-Received: by 10.176.74.205 with SMTP id t13mr9056178uae.111.1507020142723; Tue, 03 Oct 2017 01:42:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.129.140 with HTTP; Tue, 3 Oct 2017 01:42:22 -0700 (PDT)
In-Reply-To: <EF35AFF4-B2BA-4DB1-8C3D-6614A21A535B@gmail.com>
References: <EF35AFF4-B2BA-4DB1-8C3D-6614A21A535B@gmail.com>
From: Samita Chakrabarti <samitac.ietf@gmail.com>
Date: Tue, 3 Oct 2017 01:42:22 -0700
Message-ID: <CAKmdBpdXerqW5mRzWWq7-FyZ9mF4k3+PGWq1G4pETvxGuFTv9A@mail.gmail.com>
To: Suresh Krishnan <suresh.krishnan@gmail.com>
Cc: lo <6lo@ietf.org>, 6man WG <ipv6@ietf.org>, 6tisch <6tisch@ietf.org>,  int-area <int-area@ietf.org>, int-dir@ietf.org, iot-dir <iot-dir@ietf.org>, its@ietf.org, lp-wan@ietf.org, lwip@ietf.org
Content-Type: multipart/alternative; boundary="f403045f8a4c46c781055aa0780a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/9kyqxXa18qfLkaN9rmlckDPm1rU>
X-Mailman-Approved-At: Tue, 03 Oct 2017 08:19:47 -0700
Subject: Re: [Int-dir] [6lo] Liaison statement received from ITU-T regarding a "Reference Model of IPv6 Addressing Plan for Internet of Things Deployment"
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Oct 2017 08:42:25 -0000

--f403045f8a4c46c781055aa0780a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks Suresh, for sharing the information. It looks quite relevant to 6lo
WG workarea. We, 6lo-chairs will contact Scott and the ITU-T contact person
provided in the liaison note.
Will discuss with you on a separate email regarding the steps to connect.

-Samita

On Mon, Oct 2, 2017 at 7:53 PM, Suresh Krishnan <suresh.krishnan@gmail.com>
wrote:

> Hi all,
>   The IETF has received a liaison statement from the ITU-T that their
> Study Group SG20 is inviting inputs from the IETF regarding a work item
> titled "Reference Model of IPv6 Addressing Plan for Internet of Things
> Deployment=E2=80=9D and the deadline for providing inputs is 2018/01/28. =
The
> statement can be found at
>
> https://datatracker.ietf.org/liaison/1546/
>
> I have no further info and I am trying to get access to the referenced
> documents. I just want to provide a heads up while that is in process.
>
> Thanks
> Suresh
>
>
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
> https://www.ietf.org/mailman/listinfo/6lo
>

--f403045f8a4c46c781055aa0780a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks Suresh, for sharing the information. It looks quite=
 relevant to 6lo WG workarea. We, 6lo-chairs will contact Scott and the ITU=
-T contact person provided in the liaison note.=C2=A0<div>Will discuss with=
 you on a separate email regarding the steps to connect.</div><div><br></di=
v><div>-Samita</div></div><div class=3D"gmail_extra"><br><div class=3D"gmai=
l_quote">On Mon, Oct 2, 2017 at 7:53 PM, Suresh Krishnan <span dir=3D"ltr">=
&lt;<a href=3D"mailto:suresh.krishnan@gmail.com" target=3D"_blank">suresh.k=
rishnan@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">H=
i all,<br>
=C2=A0 The IETF has received a liaison statement from the ITU-T that their =
Study Group SG20 is inviting inputs from the IETF regarding a work item tit=
led &quot;Reference Model of IPv6 Addressing Plan for Internet of Things<br=
>
Deployment=E2=80=9D and the deadline for providing inputs is 2018/01/28. Th=
e statement can be found at<br>
<br>
<a href=3D"https://datatracker.ietf.org/liaison/1546/" rel=3D"noreferrer" t=
arget=3D"_blank">https://datatracker.ietf.org/<wbr>liaison/1546/</a><br>
<br>
I have no further info and I am trying to get access to the referenced docu=
ments. I just want to provide a heads up while that is in process.<br>
<br>
Thanks<br>
Suresh<br>
<br>
<br>
______________________________<wbr>_________________<br>
6lo mailing list<br>
<a href=3D"mailto:6lo@ietf.org">6lo@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/6lo" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/6lo</a><br>
</blockquote></div><br></div>

--f403045f8a4c46c781055aa0780a--


From nobody Tue Oct  3 10:16:25 2017
Return-Path: <bob.hinden@gmail.com>
X-Original-To: int-dir@ietfa.amsl.com
Delivered-To: int-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF209134F2F; Tue,  3 Oct 2017 09:30:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 3m4l9zQJovPE; Tue,  3 Oct 2017 09:30:24 -0700 (PDT)
Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (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 9BEE7134F38; Tue,  3 Oct 2017 09:30:20 -0700 (PDT)
Received: by mail-wm0-x241.google.com with SMTP id q124so17910233wmb.0; Tue, 03 Oct 2017 09:30:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=X+xA+lmGX1wr6X0Vf47d1MVAcEkayVAU77OSTVpcngw=; b=SwyCYgIhbnZb2wkopQWSKhmtEjRjHwFEhpZETT9WfKcJE9ngOFgm3ftFVswmKHdjL1 lxFHKXS1QTZldsF8gcScEBj2FIvGwezril5VjwnxdhypY5ypvIvxiDZzjwDlwtSvXUKD 2rtn2Q+7O2elOmtT4R2DFX9EObF3g0qzoDc65EKhfL7Tw0gaoQFpTFIY1KPO+3CpjmTR Iw/F0IRTgG7Dct2vJm9x7fIJDIkhfauekVfEZRsi4kaCwzIoGYu8kPYGST04d1kaHfGI cd7s0Oq/5BRb5hm/Fc1QOXQ9OqUu75hYiFga5iOrcE+iNb4S3kk88L1o5DuxHtsONpZB WcJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=X+xA+lmGX1wr6X0Vf47d1MVAcEkayVAU77OSTVpcngw=; b=i4m4xwNMJFO6qIhyIL62irI43G9zZR0g2ESZN06NOvYjTKr21E41psO0GvDEW9IVKn t7Z1uqPwJHUThYy5Ogonggyo0FdxoR681fhamHByyXGJ9+iwFrM/pFVpMQabwBaDYhX1 kHR3HYBlb/A5cp2V0If/TrlPZlUIgVLBQ4ywn9HG68/wHNTH0ml5Irde6OopNuAp3nJ8 F4+ViYs8ZVLYoP7XMf+FZ+fnIYcZU8poCDwjl+Nx0NjP2CDlIf80l2VQYcQWZimaCp5j c8N4YkcwTxIv/J8wlmwpA5yUAW40RNNju5SpXB4yJ5vbig9E1r7fbnH+EEiB6sAo/inO W24Q==
X-Gm-Message-State: AHPjjUisNNQpAxUAHzheiyWaUi7LT9wIaZ6Wh3MR9GscggaOoN/+9eD8 0PhBGn2ziBrVZ4gtVnLNmjo=
X-Google-Smtp-Source: AOwi7QBWYAqt5WxmaM7PT924l//yF4ary1dzTFG+2+vC3e3gTJAYnyU8AeM/ze9x8qjtSOXm+fyCVw==
X-Received: by 10.28.134.18 with SMTP id i18mr15413184wmd.27.1507048219110; Tue, 03 Oct 2017 09:30:19 -0700 (PDT)
Received: from ?IPv6:2601:647:4d01:db10:513d:a67a:c717:2308? ([2601:647:4d01:db10:513d:a67a:c717:2308]) by smtp.gmail.com with ESMTPSA id 69sm14990882wmm.22.2017.10.03.09.30.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Oct 2017 09:30:16 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <9F2E96BD-F1C5-4DF4-95DB-0AF5CBB5B6AC@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_091AFA1F-AD88-42AA-AFB6-C6F45CB1560E"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 3 Oct 2017 09:30:10 -0700
In-Reply-To: <CAKmdBpdXerqW5mRzWWq7-FyZ9mF4k3+PGWq1G4pETvxGuFTv9A@mail.gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, Suresh Krishnan <suresh.krishnan@gmail.com>, int-area <int-area@ietf.org>, its@ietf.org, int-dir@ietf.org, lwip@ietf.org, iot-dir <iot-dir@ietf.org>, lo <6lo@ietf.org>, lp-wan@ietf.org, IPv6 List <ipv6@ietf.org>, 6tisch <6tisch@ietf.org>
To: Samita Chakrabarti <samitac.ietf@gmail.com>
References: <EF35AFF4-B2BA-4DB1-8C3D-6614A21A535B@gmail.com> <CAKmdBpdXerqW5mRzWWq7-FyZ9mF4k3+PGWq1G4pETvxGuFTv9A@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/9FB_qiPziZPesby13FbupzP0us4>
X-Mailman-Approved-At: Tue, 03 Oct 2017 10:16:22 -0700
Subject: Re: [Int-dir] [6lo] Liaison statement received from ITU-T regarding a "Reference Model of IPv6 Addressing Plan for Internet of Things Deployment"
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Oct 2017 16:30:26 -0000

--Apple-Mail=_091AFA1F-AD88-42AA-AFB6-C6F45CB1560E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

6man as well, depending on what is in the actual document.

Bob

> On Oct 3, 2017, at 1:42 AM, Samita Chakrabarti =
<samitac.ietf@gmail.com> wrote:
>=20
> Thanks Suresh, for sharing the information. It looks quite relevant to =
6lo WG workarea. We, 6lo-chairs will contact Scott and the ITU-T contact =
person provided in the liaison note.
> Will discuss with you on a separate email regarding the steps to =
connect.
>=20
> -Samita
>=20
> On Mon, Oct 2, 2017 at 7:53 PM, Suresh Krishnan =
<suresh.krishnan@gmail.com> wrote:
> Hi all,
>   The IETF has received a liaison statement from the ITU-T that their =
Study Group SG20 is inviting inputs from the IETF regarding a work item =
titled "Reference Model of IPv6 Addressing Plan for Internet of Things
> Deployment=E2=80=9D and the deadline for providing inputs is =
2018/01/28. The statement can be found at
>=20
> https://datatracker.ietf.org/liaison/1546/
>=20
> I have no further info and I am trying to get access to the referenced =
documents. I just want to provide a heads up while that is in process.
>=20
> Thanks
> Suresh
>=20
>=20
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
> https://www.ietf.org/mailman/listinfo/6lo
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_091AFA1F-AD88-42AA-AFB6-C6F45CB1560E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJZ07sTAAoJEK7rdBF357uozaQIALHzU4KrKx/zZk9jUN3v8mHm
Defrw+89CJQo14SGRitVIuXO/mO6kIxdK6b+JH1FZgB79Pom5yoWdUColheWBfcr
bma2/ziSa4+5D+4veFavuFJCuujxhXWZKdhXiyZvsh417z7DCPyrQYlpoEDIqMBj
YsHTR05bmYx9uW3TfRkPMA9h40wHf1JqJBMm2LxEFlqyfwVA8dK2Ye5feCFic6HV
Igpm/DT0gakW+tGPjh6/oZwg38CByGhSHvRYx1asj4hIs/HPIJJs3KWafNDon6qH
qwtMZSLWMI45kWS8n0w0x8euYp5dYzEVSKRMCj+mT5i7dOXjEO/5+NOVcAPPhK4=
=SZ3u
-----END PGP SIGNATURE-----

--Apple-Mail=_091AFA1F-AD88-42AA-AFB6-C6F45CB1560E--


From nobody Tue Oct  3 10:16:31 2017
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: int-dir@ietfa.amsl.com
Delivered-To: int-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3090F134F88; Tue,  3 Oct 2017 10:10:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 nQhkBIeUOPuS; Tue,  3 Oct 2017 10:09:59 -0700 (PDT)
Received: from mail-wr0-x229.google.com (mail-wr0-x229.google.com [IPv6:2a00:1450:400c:c0c::229]) (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 63628134F7A; Tue,  3 Oct 2017 10:09:59 -0700 (PDT)
Received: by mail-wr0-x229.google.com with SMTP id o44so5072924wrf.11; Tue, 03 Oct 2017 10:09:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=C/p1fQRRgDa7lJGOSMhqZ0h60vAMiOp1C+8cg9zGYGg=; b=ga74aNYXZ4561EfTF7AMuncOVJ4BbmNAAx10A+RdT08LmZMbOjJgpgfH0XvWIjQ7Zy Njnm8xo4KJE8TKXYUa8mjrKFdHuSCitAapyDhHQbC+fyO1c6v2dIHNhZVjef884HEmnb LCAWg+0gkAh4mCnCBHMpnSfTnkPqbyAaB6BGmTh6Pk4s/tB+nX7082/SnOXRHrUrP0Hv lYvBQQx0w/CFuoZvSLeCMLusXQSVjemAFh1fOLcYRLhJtofc2Ta2ox204IG9eUWzfX8I Wl5fTU4XB9PVXG27DDTClk0H2FUPGlFJ8ZeWPUTElRSA5cebQooI3CA7nPEIxS7P3qr7 ER2A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=C/p1fQRRgDa7lJGOSMhqZ0h60vAMiOp1C+8cg9zGYGg=; b=DjhPNR/4ldruOwHVrq//bVUf9YMY2auHAGo6zQIqJKtdiXW0oS7NlOFcdvEN62+dMV 5zMHcj3bOsWiSd1np1fqPureAbzKCpZ2Gh7s7buYHSv0cKOGaoRou6ugRbGCF35tTTRJ L3aV2CvQYH0cBpR1cN3c6jUtLfUsCliktERmi8jdAqrwpZpCyXhd8q0tysV/bNjYmUc6 VoGUcEYcO38pySuzARAHKd8BnUyd/PqGVpE5XGhfOFUkhIhLZUYd2Y9LlK8RHXz7VmYH 0BFE+GIn2RJ9ULTEDE0o2210tkidx2DCM0OPOWaoW901ImLCK34lEOqtg3xe3FKZ/Lpy e7eg==
X-Gm-Message-State: AMCzsaUjnCKCkFyuRqnV/mPfzBp2/qRnB1C+czJUbgWT9D3dVEfXAv8G 8Ldcfqw8+JeHxnsdlwJQ89mdSIXR
X-Google-Smtp-Source: AOwi7QBcFOD2y8a1qmRGLDMoGwIFIxJrzWgs1Cf+jVM+pt7GZN/pIkOj1u9aeED5bjsVU3n4i3CaYw==
X-Received: by 10.223.157.74 with SMTP id o10mr7060361wre.213.1507050597649; Tue, 03 Oct 2017 10:09:57 -0700 (PDT)
Received: from ?IPv6:2600:8802:5600:e::1ef9? ([2600:8802:5600:e::1ef9]) by smtp.gmail.com with ESMTPSA id 55sm25009972wrw.60.2017.10.03.10.09.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Oct 2017 10:09:56 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <BE1C7DF5-4520-49EB-B9C3-B49C798E13AE@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_AC7519D8-F1F8-4BBC-80B7-99E42407407D"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.2\))
Date: Tue, 3 Oct 2017 10:09:52 -0700
In-Reply-To: <EF35AFF4-B2BA-4DB1-8C3D-6614A21A535B@gmail.com>
Cc: 6lo@ietf.org, 6man WG <ipv6@ietf.org>, 6tisch@ietf.org, int-area <int-area@ietf.org>, int-dir@ietf.org, iot-dir@ietf.org, its@ietf.org, lp-wan@ietf.org, lwip@ietf.org
To: Suresh Krishnan <suresh.krishnan@gmail.com>
References: <EF35AFF4-B2BA-4DB1-8C3D-6614A21A535B@gmail.com>
X-Mailer: Apple Mail (2.3445.4.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/LznJ6VL9Xw5D8Fw5Ir3JWzItLBE>
X-Mailman-Approved-At: Tue, 03 Oct 2017 10:16:23 -0700
Subject: Re: [Int-dir] Liaison statement received from ITU-T regarding a "Reference Model of IPv6 Addressing Plan for Internet of Things Deployment"
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Oct 2017 17:10:01 -0000

--Apple-Mail=_AC7519D8-F1F8-4BBC-80B7-99E42407407D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Thanks. I would like to also get operational commentary from v6ops. Like =
you, when I search for the document, I come up to a paywall; the =
document is not openly available. Please forward either the document or =
the link when ITU decides to get serious about asking for comment.

A general comment: the model being followed in RFC 4861 and in the =
various IOT groups is fundamentally as follows. The IPv6 address =
consists of a prefix and an IID. In the general Internet, routing =
operates on prefixes, and a subnet is identified by a prefix. Within a =
subnet defined by WiFi, Bluetooth, IEEE 802.15.4/4g, Power Line =
Communication technologies, and the like, network elements generally use =
some form of host routing, whether source or distributed, on the =
presumption that topologies may be continuously changing or devices may =
be moving. 6LowPAN specifically has some recommendations on the =
structure of the address designed to minimize the actual size of an IPv6 =
header, and in many of them, that is treated as a lower layer problem. =
I'd like to believe that the work party is sufficiently clued in to not =
want to materially change that without discussing it with us (putting =
documents behind a paywall not being a great example of open =
discussion).

> On Oct 2, 2017, at 7:53 PM, Suresh Krishnan =
<suresh.krishnan@gmail.com> wrote:
>=20
> Hi all,
>  The IETF has received a liaison statement from the ITU-T that their =
Study Group SG20 is inviting inputs from the IETF regarding a work item =
titled "Reference Model of IPv6 Addressing Plan for Internet of Things
> Deployment=E2=80=9D and the deadline for providing inputs is =
2018/01/28. The statement can be found at
>=20
> https://datatracker.ietf.org/liaison/1546/
>=20
> I have no further info and I am trying to get access to the referenced =
documents. I just want to provide a heads up while that is in process.
>=20
> Thanks
> Suresh
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_AC7519D8-F1F8-4BBC-80B7-99E42407407D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEctjlJjQmVrp9uMq7EhdRnd2GP+AFAlnTxGAACgkQEhdRnd2G
P+AF5BAAj9UyZajt/xa+V+GsLX1GtdYWbxcK4uaE+IHh+uiMepuiO8GGsQDGS8gY
VVaReppQX78F0Kt1n6bY1h+zBQMZUsOiU6rd0iEJROGw+/3uWFwETlk6ilGXN7z4
ym/rdDuH7H8VdzU1J2Q4DMwNNTGOigckWH25mREzckV9kKpxe7trJaovcMG1GveT
x/Z3b25E9xkZ9fea5vBeEuyBYVec67WMdyE8nzcPNDf7dHxbrwFNw1Hj1e6VXoKY
sGDtHar8lF9jRncygnahMsJxoOY2bff0a1h3jhP3knCtoy2ohAlfEFD0g8tVCpKH
MMyJBfZb8e51NnP7ABfqb16wdoesFamLVxi9rE6Yb5/F+dhbc7UP8n/Mj5PY51mk
LzjPPXRAILEf/Gs4hmay6iWhHvyB+CQfgv1AbpwH5ObzU0oXl70QD9sthnleCg6R
lHla8TEKjU8iL0ah4bbEEz81/LAcsVQCHTv613YsdrYtnrOq28TNJmf5Shj4spMM
AfsGNyqrilfcN0kFcLdNjWWc45EJhrc2n0rbJffu/BKYrpExuRksenE1LRBsMTCx
V65kR4wpSz1c/WZeI9/YQ6p/C+f292fFIF832kt5kAIk4zhjC87GFw2xV9KMiIsp
qD6kF0lKMmRNx37tlIru5O/uNlK9AhH5ad89/4IisjEztMPK6RQ=
=85O7
-----END PGP SIGNATURE-----

--Apple-Mail=_AC7519D8-F1F8-4BBC-80B7-99E42407407D--


From nobody Sun Oct 22 04:54:31 2017
Return-Path: <carlesgo@entel.upc.edu>
X-Original-To: int-dir@ietfa.amsl.com
Delivered-To: int-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDCBE1386DE; Sun, 22 Oct 2017 04:54:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-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 Eje-pAy4roE0; Sun, 22 Oct 2017 04:54:14 -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 1D794138601; Sun, 22 Oct 2017 04:54:10 -0700 (PDT)
Received: from entelserver.upc.edu (entelserver.upc.es [147.83.39.4]) by dash.upc.es (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v9MBs5FB046601;  Sun, 22 Oct 2017 13:54:05 +0200
Received: from webmail.entel.upc.edu (webmail.entel.upc.edu [147.83.39.6]) by entelserver.upc.edu (Postfix) with ESMTP id 204981D53C1; Sun, 22 Oct 2017 13:54:04 +0200 (CEST)
Received: from 83.37.37.84 by webmail.entel.upc.edu with HTTP; Sun, 22 Oct 2017 13:54:01 +0200
Message-ID: <5a9c8563ee1e18ef36e3011da8d5f464.squirrel@webmail.entel.upc.edu>
In-Reply-To: <150094520677.26176.17525876529879529582@ietfa.amsl.com>
References: <150094520677.26176.17525876529879529582@ietfa.amsl.com>
Date: Sun, 22 Oct 2017 13:54:01 +0200
From: "Carles Gomez Montenegro" <carlesgo@entel.upc.edu>
To: "Bernie Volz" <volz@cisco.com>
Cc: int-dir@ietf.org, lwip@ietf.org, ietf@ietf.org, draft-ietf-lwig-energy-efficient.all@ietf.org
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.99.2 at dash
X-Virus-Status: Clean
X-Greylist: Delayed for 68:06:58 by milter-greylist-4.3.9 (dash.upc.es [147.83.2.50]); Sun, 22 Oct 2017 13:54:05 +0200 (CEST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/0375rIyZr0kRUVMXZ-vfSsLvEhw>
Subject: Re: [Int-dir] Intdir early review of draft-ietf-lwig-energy-efficient-07
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Oct 2017 11:54:17 -0000

Dear Bernie,

Thank you very much for your detailed review, and for the constructive
feedback provided.

We have updated the draft (now, -08). This version should hopefully
address your comments.

Should you have further comments, please let us know.

Cheers,

Carles

-----------------------
The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-lwig-energy-efficient/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-lwig-energy-efficient-08
https://datatracker.ietf.org/doc/html/draft-ietf-lwig-energy-efficient-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-lwig-energy-efficient-08
-----------------------




> Reviewer: Bernie Volz
> Review result: Ready with Nits
>
> I am an assigned INT directorate early reviewer for
> draft-ietf-lwig-energy-efficient-07. These comments were written primarily
> for
> the benefit of the Internet Area Directors.
>
> Document editors and shepherd(s) should treat these comments just like
> they
> would treat comments from any other IETF contributors and resolve them
> along
> with any other comments that have been received. For more details on the
> INT
> Directorate, see http://www.ietf.org/iesg/directorate.html.
>
> I found the document's information interesting, and it is document that is
> benefical to the IETF community in understanding the impact energy savings
> techniques (mostly related to radios for wireless communication) can have
> on
> protocols (both at lower and higher layers). It is going for Informational
> status, which I think is appropriate for this document.
>
> All my comments are fairly minor nits.
>
> In section 1, "Only few efforts focused on" should likely be "Only few
> efforts
> have focused on"? (Add have)
>
> In section 1.1, I think this section can be removed as there are no uses
> of the
> RFC 2119 keywords.
>
> In section 2, there are a few technologies listed here that might use
> references; some do appear later but not all. It is usually a good
> question as
> to where references are best added since this is overview material. Those
> without any references are ITU-T G.9959 and MS/TP-BACnet.
>
> Also in Figure 2, it is too bad that some power value for listening (when
> not
> "actively" expecting a packet) isn't included since there is a claim that
> this
> can use more energy than transmitting, but it would also be a uJ/<time>
> which
> is unlike the others. Though perhaps indicating a "listening (for X ms)"
> entry
> could work? Anyway, not a big issue.
>
> In section 3, I presume everyone knows what MAC is
> (draft-bormann-lwig-7228bis-01 does not define it). Also, might be good to
> indicate what RDC is as it is just used (in the MAC and Radio Duty Cycling
> section, so pretty obvious likely).
>
> Also in section 3, "take great care of the problem" is a bit strange
> wording.
> Perhaps "are at work on the problem"? Or something like that? And, "can
> work
> perfectly with them" would certainly be great, it may be a stretch of goal
> -
> "can work well with them" may be better?
>
> In section 3.2, "contributes to the packet overall delay" should be
> "contributes to the packet's overall delay" ('s).
>
> In section 3.3, "in some services this kind of networks, such as
> over-the-air"
> could be "for some services, such as over-the-air". I think for is better
> than
> in and not sure "these kinds of networks" (instead of this kind of
> networks) is
> really needed?
>
> Also, in this section, "that can achieved when" should be "that can be
> achieved
> when".
>
> In section 3.5.1, "extended sleep modes, traffic filtering" should likely
> be
> "extended sleep modes, and traffic filtering". (You may or may not prefer
> the
> last comma in a list, but the "and" should be there).
>
> And, in this section, in "upper layer protocols knows such capabilities
> provided" likely should be "upper layer protocols know such capabilities
> are
> provided".
>
> And, in this section, I don't think you need to define (STA) in several
> places;
> once (first time) should be sufficient?
>
> And, in this section, "by not forwarding individually addressed frames
> addresses to" perhaps this should drop "individually addressed"? But
> perhaps
> I'm not understanding why it is needed?
>
> And, "Upper layer protocols would better synchronize" perhaps could be
> "Upper
> layer protocols would best synchronize"? Or just "Upper layer protocols
> should
> synchronize"?
>
> In section 3.5.3, perhaps insert spaces between the 6LoWPAN references to
> make
> the formatting more flexible?
>
> And, in this section, should TDMA be defined (again a fairly common term,
> but
> not in draft-bormann-lwig-7228bis-01.
>
> In section 3.5.4, I think you would want to use "connectionless" instead
> of
> "connection less"?
>
> And, in this section, "data transfer reliability significant" should be
> "data
> transfer reliability significantly"?
>
> In section 4, "So they are quite ignorant" it isn't exactly clear what
> "they"
> are. Replace with "So higher level protocols are quite ignorant"?
>
> And, "but both the sender and receiver should spend" should likely be "but
> both
> the sender and receive will spend"?
>
> In section 6.2, a reference for oneM2M (perhaps to www.onem2m.org) could
> be
> added?
>
> In section 9, the "Thank Ted Lemon, Joel Jaeggli, and efforts to initiate
> this
> facilities" sounds more like notes than actual text? Perhaps something
> like
> "Thanks to Ted Lemon and Joel Jaeglli for initiating and facilitating this
> editing session."?
>
> In section 12.1, for the EN300 reference, there are double quotes that
> probably
> aren't needed (single would do)?
>
> Finally, thanks for writing the document!
>
> - Bernie Volz
>
>
>



From nobody Tue Oct 24 08:41:47 2017
Return-Path: <rolf.winter@hs-augsburg.de>
X-Original-To: int-dir@ietfa.amsl.com
Delivered-To: int-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BDFE13F6CF; Tue, 24 Oct 2017 08:41:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 F_yKDq-4uk0j; Tue, 24 Oct 2017 08:41:45 -0700 (PDT)
Received: from fly.RZ.HS-Augsburg.DE (fly.RZ.HS-Augsburg.DE [141.82.217.48]) (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 35F3213F6B0; Tue, 24 Oct 2017 08:41:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by fly.RZ.HS-Augsburg.DE (Postfix) with ESMTP id 8EE961D608E; Tue, 24 Oct 2017 17:41:33 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at hs-augsburg.de
Received: from fly.RZ.HS-Augsburg.DE ([127.0.0.1]) by localhost (fly.rz.hs-augsburg.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id pVOBtzwXw5zG; Tue, 24 Oct 2017 17:41:33 +0200 (CEST)
Received: from [192.168.1.147] (nightswatch.informatik.hs-augsburg.de [141.82.79.79]) by fly.RZ.HS-Augsburg.DE (Postfix) with ESMTPSA id BAA971D605D; Tue, 24 Oct 2017 17:41:32 +0200 (CEST)
To: Carlos Bernardos <cjbc@it.uc3m.es>, int-dir@ietf.org
Cc: int-area@ietf.org, draft-ietf-intarea-broadcast-consider.all@ietf.org, ietf@ietf.org
References: <150623836210.5031.17716199391295946656@ietfa.amsl.com>
From: Rolf Winter <rolf.winter@hs-augsburg.de>
Message-ID: <c33f7641-3a6b-5724-7189-f0ff130e4f27@hs-augsburg.de>
Date: Tue, 24 Oct 2017 17:41:42 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <150623836210.5031.17716199391295946656@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/zLBViRZic5lmDSkXJXDX0hNpumg>
Subject: Re: [Int-dir] Intdir early review of draft-ietf-intarea-broadcast-consider-04
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Oct 2017 15:41:46 -0000

Carlos,

thanks for the review and sorry for the belated reply. Please inline:

Am 24.09.17 um 09:32 schrieb Carlos Bernardos:
> Reviewer: Carlos Bernardos
> Review result: Ready with Nits
> 
> The document is well written and clear to follow. I have not found any major
> issue. I have some recommendations/questions for the authors:
> 
> * Page 3: RFC 7919 --> RFC 7819
Nice catch.

> 
> * It would be good to have a section (maybe an annex) in which authors describe
> the differences (if any) found in the experiments performed with IPv4 vs IPv6.
> Since IPv6 does not do broadcast, there may be important differences to
> highlight.
> 

We only had v4 networks at the time under observation. While v6 does not 
broadcast, it has the all nodes multicast address. I kind of fear to ask 
the IETF again to do the experiment on the v6 meeting network as, as you 
might remember, it was somewhat controversial :)

> * While I understand that the authors do not provide details about the apps
> analyzed, it would be good to include more information for example about the
> distribution of the frequency of broadcast/multicast messages found in the
> experiments. 

We mention multiple messages per minute. The highest frequency we 
observed was about 8 per minute for a given (popular) app.

> And it would also be nice (though I don't know if this would be
> feasible) to provide some recommended values for the frequencies to use (an app
> developer could benefit from some additional guidelines).

Impossible :)

> 
> * Page 5: "In that respect broadcast can be [...]" --> "In that respect,
> multicast can be [...]" or "In that respect, broadcast/multicast can be [...]".
> Note that the examples used are IPv6, so "broadcast" alone would not apply.
> 

Nice catch, thanks.


Best,

Rolf


From nobody Fri Oct 27 10:29:43 2017
Return-Path: <jeanmichel.combes@gmail.com>
X-Original-To: int-dir@ietf.org
Delivered-To: int-dir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ED0E13F5A2; Fri, 27 Oct 2017 10:29:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jean-Michel Combes <jeanmichel.combes@gmail.com>
To: <int-dir@ietf.org>
Cc: draft-ietf-intarea-probe.all@ietf.org, int-area@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150912536515.22228.10940363588216201270@ietfa.amsl.com>
Date: Fri, 27 Oct 2017 10:29:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/NCsPGXR3hcsX5ZKx1TBm_1GhF8g>
Subject: [Int-dir] Intdir early review of draft-ietf-intarea-probe-00
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Oct 2017 17:29:25 -0000

Reviewer: Jean-Michel Combes
Review result: Almost Ready

Hi,

I am an assigned INT directorate reviewer for draft-ietf-intarea-probe-06.
These comments were written primarily for the benefit of the Internet Area
Directors. Document editors and shepherd(s) should treat these comments just
like they would treat comments from any other IETF contributors and resolve
them along with any other Last Call comments that have been received. For more
details on the INT Directorate, see http://www.ietf.org/iesg/directorate.html.

                PROBE: A Utility For Probing Interfaces
                      draft-ietf-intarea-probe-06

<snip>

1.  Introduction

<snip>

If the probed interface resides on a node that is directly connected to the
probed node, PROBE reports that the interface is up if it appears in the IPv4
Address Resolution Protocol (ARP) table or the IPv6 Neighbor Cache. Otherwise,
it reports that the interface does not exist.

<JMC>
Comment:
Normative references to "IPv4 Address Resolution Protocol (ARP) table" (i.e.,
RFC 826) and "IPv6 Neighbor Cache" (i.e., RFC 4861) are missing. </JMC>

<snip>

2.  ICMP Extended Echo Request

<snip>

o  L (local) - The L-bit is set of the probed interface resides on the probed
node. The L-bit is clear if the probed interface is directly connected to the
probed node.

<JMC>
Typo:
s/"The L-bit is set of the probed interface resides on the probed node."/"The
L-bit is set if the probed interface resides on the probed node." </JMC>

<snip>

3.  ICMP Extended Echo Reply

<snip>

o  F (IPv4) - The F-bit is set if the A-bit is also set and IPv4 is running on
the probed interface.  Otherwise, the F-bit is clear.

o  S (IPv6) - The S-bit is set if the A-bit is also set and IPv6 is running on
the probed interface.  Otherwise, the S-bit is clear.

o  E (Ethernet) - The E-bit is set if the A-bit is also set and IPv4 is running
on the probed interface.  Otherwise, the E-bit is clear.

<JMC>
Question:
Why IPv4 must also run to have the E-bit set?
Question:
Why the E-bit is not set if IPv4 is not running and IPv6 is running?
</JMC>

4.  ICMP Message Processing

<snip>

   o  Set the Code field as described Section 4.1

   o  If the Code Field is equal to No Error (0) and the L-bit is clear,
      set the A-Bit.

   o  If the Code Field is equal to No Error (0) and the L-bit is set
      and the probed interface is active, set the A-bit.

<JMC>
Question:
Why the A-bit is not set when Code Field is equal to Multiple Interfaces
Satisfy Query (3) and the L-bit is clear? Question: Same question when L-bit is
set. </JMC>

<snip>

8.  Security Considerations

<snip>

In order to protect local resources, implementations SHOULD rate-limit incoming
ICMP Extended Echo Request messages.

<JMC>
Comment:
IMHO, the main security threat I see with this mechanism is to use it as
"reflection" scanning: to discover nodes "behind" the proxy interface, without
raising alarms from security probes watching the networks hosting these nodes.
So, rate-limit can help to mitigate this potential threat too. </JMC>

9.  References

9.1.  Normative References

<snip>

<JMC>
Comment:
Too add normative references to "IPv4 Address Resolution Protocol (ARP) table"
(i.e., RFC 826) and "IPv6 Neighbor Cache" (i.e., RFC 4861), as commented
previously. </JMC>

<snip>

Thanks in advance for your replies.

Best regards,

JMC.


From nobody Sun Oct 29 15:03:04 2017
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: int-dir@ietf.org
Delivered-To: int-dir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 638F813FC5F; Sun, 29 Oct 2017 15:03:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Tim Chown <tim.chown@jisc.ac.uk>
To: <int-dir@ietf.org>
Cc: lwip@ietf.org, ietf@ietf.org, draft-ietf-lwig-crypto-sensors.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150931458233.3515.10214190547457562395@ietfa.amsl.com>
Date: Sun, 29 Oct 2017 15:03:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/3gZFBnS1vELDhLkKj7ZmxTjyb1E>
Subject: [Int-dir] Intdir early review of draft-ietf-lwig-crypto-sensors-04
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Oct 2017 22:03:02 -0000

Reviewer: Tim Chown
Review result: Ready

Hi,

This Informational draft describes the challenges in securing
resource-constrained smart object / IoT devices, documenting the associated
tradeoffs, and discussing the availability of appropriate cryptographic
libraries for such devices.

I have reviewed this document, and overall find it generally ready for
publication, though I have some minor nits / comments for consideration below;
these are just suggested changes / improvements, and I would not object
strongly if all were ignored.

General comments:

The document is very easy and enjoyable to read, and the quality of the writing
is very good.  The authors have clear expertise in the field.

It may be worth considering teasing apart the evaluation and the architectural
aspects of the document; these are somewhat interwoven as currently written.

Related, there are some rather nice recommendations made throughout the
document; these could perhaps be summarised either at the start or perhaps
better the close of the document, e.g. on page 4 regarding selecting the
hardware after determining the security requirements for a device, and not
necessarily simply picking the most lightweight algorithm, or on page 7
regarding appropriate layers for tasks, or on page 9 regarding elliptic curve
vs RSA, or on page 11 on real deployments using 32-bit microcontrollers, or the
recommendation to the IETF community on page 14, or on planning for firmware
updates on page 16, etc.

Comments by page:

On page 5, in the first paragraph on provisioning, there is no hint of any
bootstrap process for identities; this follows later on page 6, but a hint
here, or just adding "as discussed on page 6 or in section x.y" might be nice.

Also on page 5, I'd be interested in seeing some brief text added on the
"remaining vulnerabilities" that are mentioned near the foot of the page.

On page 6, is it worth adding a little text on privacy somewhere?  We've been
doing some work through Christian Huitema and Daniel Kaiser on anonymous device
pairing in the DNSSD WG, and a similar requirement might be desirable in some
scenarios here?

On page 7, having said earlier you should pick the hardware after determining
requirements, you then decide to pick an Arduino platform and see what you can
manage to run on it. I fully understand why (and I'd be equally curious), but
you should probably clarify the "conflict" further.

On page 12, would a little more detail on RNG requirements, esp. for devices of
this type, be worthwhile?

On page 16, you're hardcoding the IP address?  Is it not possible to use RD? 
We've been comparing that and looking at interoperability with classic DNSSD in
the DNSSD WG.

On page 16, section 10 seems to have no content?  Or should sections 11 onwards
be subsections of section 10?

On page 17, at the end of section 11, should there also be some 'spin up' costs
for the radio?

Best wishes,
Tim


