Re: [lp-wan] I-D Action: draft-ietf-lpwan-ipv6-static-context-hc-03.txt
"weigengyu" <weigengyu@bupt.edu.cn> Sat, 13 May 2017 06:00 UTC
Return-Path: <weigengyu@bupt.edu.cn>
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 60392129B0F for <lp-wan@ietfa.amsl.com>; Fri, 12 May 2017 23:00:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.798
X-Spam-Level:
X-Spam-Status: No, score=0.798 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, 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 6cDp5I0Y83YH for <lp-wan@ietfa.amsl.com>; Fri, 12 May 2017 23:00:31 -0700 (PDT)
Received: from mx1.bupt.edu.cn (mx1.bupt.edu.cn [211.68.68.2]) by ietfa.amsl.com (Postfix) with ESMTP id 86B23129549 for <lp-wan@ietf.org>; Fri, 12 May 2017 22:57:59 -0700 (PDT)
Received: from WeiGengyuPC (unknown [114.254.89.114]) by mx1.bupt.edu.cn (AnyMacro(G7)) with ESMTPA id 9DAA619F374 for <lp-wan@ietf.org>; Sat, 13 May 2017 13:57:58 +0800 (HKT)
Message-ID: <BBE61941E67E454B81EADC1A89206FB4@WeiGengyuPC>
From: weigengyu <weigengyu@bupt.edu.cn>
To: lp-wan@ietf.org
References: <149400726585.8434.8654374640287295976@ietfa.amsl.com> <FFC4EB5EC49F421AA69F2803DD719D36@WeiGengyuPC>
In-Reply-To: <FFC4EB5EC49F421AA69F2803DD719D36@WeiGengyuPC>
Date: Sat, 13 May 2017 13:57:56 +0800
Organization: BUPT
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"; reply-type="response"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3528.331
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/uEotDiam4v3scWjWsxf78bErQDU>
Subject: Re: [lp-wan] I-D Action: draft-ietf-lpwan-ipv6-static-context-hc-03.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: Sat, 13 May 2017 06:00:34 -0000
HI, In draft-ietf-lpwan-ipv6-static-context-hc-03, 3. Static Context Header Compression Figure 1 based on [I-D.ietf-lpwan-overview] terminology represents the architecture for compression/decompression. In draft-farrell-lpwan-overview-04, 2.1. LoRaWAN [[Ed: Text here is from [I-D.farrell-lpwan-lora-overview]]] In draft-farrell-lpwan-lora-overview-01, 2. Terminology o End-device: a LoRa client device, sometimes called a mote. Communicates with gateways. o Classes A, B and C define different device capabilities and modes of operation for end-devices. End-devices can transmit uplink messages at any time in any mode of operation (so long as e.g., ISM band restrictions are honoured). An end-device in Class A can only receive downlink messages at predetermined timeslots after each uplink message transmission. Class B allows the end-device to receive downlink messages at periodically scheduled timeslots. Class C allows receipt of downlink messages at anytime. Class selection is based on the end-devices’ application use case and its power supply. (While Classes B and C are not further described here, readers may have seen those terms elsewhere so we include them for clarity.) Based on the descriptions above, it is not clear for me to see whether the end-device requires the UDP facilities. Regards, Gengyu WEI Network Technology Center School of Computer Beijing University of Posts and Telecommunications -----原始邮件----- From: weigengyu Sent: Saturday, May 13, 2017 11:42 AM To: lp-wan@ietf.org Subject: Re: [lp-wan] I-D Action: draft-ietf-lpwan-ipv6-static-context-hc-03.txt Hi all, There is a question, maybe a silly question. Does the end-device in Lora, Sigfox, or the like networks need the facilities of UDP protocol? It is heard that it generally is simple one function device, the port multiplexing is required or not? Regards, Gengyu WEI Network Technology Center School of Computer Beijing University of Posts and Telecommunications -----原始邮件----- From: internet-drafts@ietf.org Sent: Saturday, May 06, 2017 2:01 AM To: i-d-announce@ietf.org Cc: lp-wan@ietf.org Subject: [lp-wan] I-D Action: draft-ietf-lpwan-ipv6-static-context-hc-03.txt 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 Static Context Header Compression (SCHC) and fragmentation for IPv6 and UDP Authors : Ana Minaburo Laurent Toutain Carles Gomez Filename : draft-ietf-lpwan-ipv6-static-context-hc-03.txt Pages : 36 Date : 2017-05-05 Abstract: This document describes a header compression scheme and fragmentation functionality for IPv6/UDP protocols. These techniques are especially tailored for LPWAN (Low Power Wide Area Network) networks and could be extended to other protocol stacks. The Static Context Header Compression (SCHC) offers a great level of flexibility when processing the header fields. Static context means that information stored in the context which, describes field values, does not change during the packet transmission, avoiding complex resynchronization mechanisms, incompatible with LPWAN characteristics. In most of the cases, IPv6/UDP headers are reduced to a small identifier. This document describes the generic compression/decompression process and applies it to IPv6/UDP headers. Similar mechanisms for other protocols such as CoAP will be described in a separate document. Moreover, this document specifies fragmentation and reassembly mechanims for SCHC compressed packets exceeding the L2 pdu size and for the case where the SCHC compression is not possible then the IPv6/UDP packet is sent. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-lpwan-ipv6-static-context-hc/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-lpwan-ipv6-static-context-hc-03 https://datatracker.ietf.org/doc/html/draft-ietf-lpwan-ipv6-static-context-hc-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-lpwan-ipv6-static-context-hc-03 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
- [lp-wan] I-D Action: draft-ietf-lpwan-ipv6-static… internet-drafts
- Re: [lp-wan] I-D Action: draft-ietf-lpwan-ipv6-st… weigengyu
- Re: [lp-wan] I-D Action: draft-ietf-lpwan-ipv6-st… weigengyu
- Re: [lp-wan] I-D Action: draft-ietf-lpwan-ipv6-st… Juan Carlos Zuniga
- Re: [lp-wan] I-D Action: draft-ietf-lpwan-ipv6-st… weigengyu
- Re: [lp-wan] I-D Action: draft-ietf-lpwan-ipv6-st… Juan Carlos Zuniga
- Re: [lp-wan] I-D Action: draft-ietf-lpwan-ipv6-st… Juan Carlos Zuniga