Re: [lp-wan] I-D Action: draft-ietf-lpwan-overview-05.txt

"Patrick Wetterwald (pwetterw)" <pwetterw@cisco.com> Wed, 19 July 2017 11:42 UTC

Return-Path: <pwetterw@cisco.com>
X-Original-To: lp-wan@ietfa.amsl.com
Delivered-To: lp-wan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DC6E131CC7 for <lp-wan@ietfa.amsl.com>; Wed, 19 Jul 2017 04:42:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 lQmwLBo9DTOt for <lp-wan@ietfa.amsl.com>; Wed, 19 Jul 2017 04:42:06 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 439EE13178B for <lp-wan@ietf.org>; Wed, 19 Jul 2017 04:42:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6192; q=dns/txt; s=iport; t=1500464526; x=1501674126; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=zTgceiGc8NVsYN9QOdySjSI3R3uhYjBubcd1j9lH7NU=; b=jey5ScMrRTbEgZ4znf+w/5zrvt06UVQyWA6Jox9RM/5z5tdL0g/E6J/K q2jZHw4YYZboZNU88HmPZuTBKgBPp1OgFXqZ9Er/sc4IGXd7soWNkb3aW dYc7L1LuQZ5oZhCU0OLcfpTKh16XCuhNk/nV+pBJUR+ikkZn/jT8maC21 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DUAABbRW9Z/5ldJa1bGQEBAQEBAQEBAQEBBwEBAQEBgy0tZIEBEweOBJE+IpYEghEhC4UbAhqDRD8YAQIBAQEBAQEBayiFGAEBAQEDAQEhEToLDAQCAQgRAQMBAQMCERIDAgICJQsUAQIGCAIEDgUZihYQryWCJosGAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYELgh2DTYFhKwuCboMmgQ0dMSiCVDCCMQWXRId1AodJjE6CDFeEeIpUlVsBHziBCnUVHyoSAYcDdodGgQ0BAQE
X-IronPort-AV: E=Sophos;i="5.40,380,1496102400"; d="scan'208";a="271838388"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Jul 2017 11:41:56 +0000
Received: from XCH-RTP-004.cisco.com (xch-rtp-004.cisco.com [64.101.220.144]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v6JBfuqD032614 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <lp-wan@ietf.org>; Wed, 19 Jul 2017 11:41:56 GMT
Received: from xch-rtp-014.cisco.com (64.101.220.154) by XCH-RTP-004.cisco.com (64.101.220.144) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 19 Jul 2017 07:41:55 -0400
Received: from xch-rtp-014.cisco.com ([64.101.220.154]) by XCH-RTP-014.cisco.com ([64.101.220.154]) with mapi id 15.00.1210.000; Wed, 19 Jul 2017 07:41:55 -0400
From: "Patrick Wetterwald (pwetterw)" <pwetterw@cisco.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
CC: "lp-wan@ietf.org" <lp-wan@ietf.org>
Thread-Topic: [lp-wan] I-D Action: draft-ietf-lpwan-overview-05.txt
Thread-Index: AQHTAIQFxrpG3fjyxEupD15MmC7V9w==
Date: Wed, 19 Jul 2017 11:41:55 +0000
Message-ID: <4DA564CA-BF27-4364-96EF-1AFA685D93F5@cisco.com>
References: <149893334336.489.9442381469735966027@ietfa.amsl.com> <33B0795E-6CA0-4BB2-9469-61B5D60DED38@cisco.com> <665c265cd7e94dabb947c47707e6bcd0@XCH-RCD-001.cisco.com>
In-Reply-To: <665c265cd7e94dabb947c47707e6bcd0@XCH-RCD-001.cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.22.0.170515
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.215.129]
Content-Type: text/plain; charset="utf-8"
Content-ID: <F3253438D22E114E88E080A28E9D5681@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/5Sk2hz_UHZh7fI-hv0dNl6_vVW4>
Subject: Re: [lp-wan] I-D Action: draft-ietf-lpwan-overview-05.txt
X-BeenThere: lp-wan@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Low-Power Wide Area Networking \(LP-WAN\), also known as LPWA or Low-Rate WAN \(LR-WAN\)" <lp-wan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lp-wan>, <mailto:lp-wan-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lp-wan/>
List-Post: <mailto:lp-wan@ietf.org>
List-Help: <mailto:lp-wan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lp-wan>, <mailto:lp-wan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 11:42:08 -0000

Hi Pascal.

So basically you agree with my comments :=)

Thanks,

Patrick


On 19/07/2017, 10:01, "Pascal Thubert (pthubert)" <pthubert@cisco.com> wrote:

    Hello Patrick:
    
    There is a match to be found between what Wi-Sun does and what LPWAN is chartered to cover.
    
    1) It is good to mention as an overview that Wi-Sun FAN can do mesh, has routing and 6LoWPAN. It would be good to very briefly position the profiles and which of those qualify as LPWAN.
    
    OTOH, LPWAN is explicitly chartered outside of routing and 6LoWPAN, so there should not be too much emphasis on this since this is not what the LPWAN reader is after. What the LPWAN reader is after is the edge between the low power end objects and the first router, which appears like a LPWAN star. This is where an intersection with LPWAN technology is hopefully to be found. And then we can use the needs expressed in the overview to derive the next charter items. 
    
    2) is very close to 1). After a brief description of the mesh where routing happens, focus should move to access where LPWAN operates by charter.
    
    Take care,
    
    Pascal
    
    -----Original Message-----
    From: lp-wan [mailto:lp-wan-bounces@ietf.org] On Behalf Of Patrick Wetterwald (pwetterw)
    Sent: mardi 18 juillet 2017 15:38
    To: internet-drafts@ietf.org; i-d-announce@ietf.org
    Cc: lp-wan@ietf.org
    Subject: Re: [lp-wan] I-D Action: draft-ietf-lpwan-overview-05.txt
    
    Hi Stephen,
    
    I have 2 comments regarding the draft.
    
    First one: Paragraph 3. “Generic terminology”. This paragraph should take into account the WI-SUN architecture (as one of the technology in the scope). WI-SUN architecture introduces the notion of border router, routers and leaf nodes. WI-SUN is not talking about gateways, radio gateways etc. One way to solve this is to add another diagram with the WI-SUN approach.
    
    Second: Paragraph 4.6 says that no routing protocol is needed. This is not correct. WI-SUN is using RPL as routing protocol and is based on a mesh topology. This should be reflected in this paragraph not as a gap but as existing technology.
    
    Many thanks,
    
    Patrick
    
    On 01/07/2017, 20:22, "lp-wan on behalf of internet-drafts@ietf.org" <lp-wan-bounces@ietf.org on behalf of internet-drafts@ietf.org> wrote:
    
        
        A New Internet-Draft is available from the on-line Internet-Drafts directories.
        This draft is a work item of the IPv6 over Low Power Wide-Area Networks of the IETF.
        
                Title           : LPWAN Overview
                Author          : Stephen Farrell
        	Filename        : draft-ietf-lpwan-overview-05.txt
        	Pages           : 41
        	Date            : 2017-07-01
        
        Abstract:
           Low Power Wide Area Networks (LPWAN) are wireless technologies with
           characteristics such as large coverage areas, low bandwidth, possibly
           very small packet and application layer data sizes and long battery
           life operation.  This memo is an informational overview of the set of
           LPWAN technologies being considered in the IETF and of the gaps that
           exist between the needs of those technologies and the goal of running
           IP in LPWANs.
        
        
        The IETF datatracker status page for this draft is:
        https://datatracker.ietf.org/doc/draft-ietf-lpwan-overview/
        
        There are also htmlized versions available at:
        https://tools.ietf.org/html/draft-ietf-lpwan-overview-05
        https://datatracker.ietf.org/doc/html/draft-ietf-lpwan-overview-05
        
        A diff from the previous version is available at:
        https://www.ietf.org/rfcdiff?url2=draft-ietf-lpwan-overview-05
        
        
        Please note that it may take a couple of minutes from the time of submission
        until the htmlized version and diff are available at tools.ietf.org.
        
        Internet-Drafts are also available by anonymous FTP at:
        ftp://ftp.ietf.org/internet-drafts/
        
        _______________________________________________
        lp-wan mailing list
        lp-wan@ietf.org
        https://www.ietf.org/mailman/listinfo/lp-wan
        
    
    _______________________________________________
    lp-wan mailing list
    lp-wan@ietf.org
    https://www.ietf.org/mailman/listinfo/lp-wan