From 6lowpan-bounces@ietf.org Wed Jan 14 10:50:50 2009 Return-Path: <6lowpan-bounces@ietf.org> X-Original-To: 6lowpan-archive@megatron.ietf.org Delivered-To: ietfarch-6lowpan-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 583F028C19C; Wed, 14 Jan 2009 10:50:50 -0800 (PST) X-Original-To: 6lowpan@core3.amsl.com Delivered-To: 6lowpan@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB5BF3A6829 for <6lowpan@core3.amsl.com>; Mon, 12 Jan 2009 22:35:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.654 X-Spam-Level: X-Spam-Status: No, score=-3.654 tagged_above=-999 required=5 tests=[AWL=-0.650, BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, RELAY_IS_203=0.994] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K1ebTU+BKOgV for <6lowpan@core3.amsl.com>; Mon, 12 Jan 2009 22:35:30 -0800 (PST) Received: from mailout4.samsung.com (mailout4.samsung.com [203.254.224.34]) by core3.amsl.com (Postfix) with ESMTP id 1CBF93A67D1 for <6lowpan@ietf.org>; Mon, 12 Jan 2009 22:35:30 -0800 (PST) Received: from epmmp2 (mailout4.samsung.com [203.254.224.34]) by mailout4.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0KDE00L4CCYEQN@mailout4.samsung.com> for 6lowpan@ietf.org; Tue, 13 Jan 2009 15:35:02 +0900 (KST) Received: from jibin ([107.108.32.157]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTPA id <0KDE001I3CYCUS@mmp2.samsung.com> for 6lowpan@ietf.org; Tue, 13 Jan 2009 15:35:02 +0900 (KST) Date: Tue, 13 Jan 2009 12:04:17 +0530 From: Jibin K To: 6lowpan@ietf.org Message-id: <007b01c97548$f6e6dd70$9d206c6b@semco> Organization: Samsung Electro-Mechanics Co.,Ltd. MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-Priority: 3 X-MSMail-priority: Normal X-Mailman-Approved-At: Wed, 14 Jan 2009 10:50:49 -0800 Subject: [6lowpan] 6loWPAN UDP Receive timeout X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Jibin K List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2068230624==" Sender: 6lowpan-bounces@ietf.org Errors-To: 6lowpan-bounces@ietf.org This is a multi-part message in MIME format. --===============2068230624== Content-type: multipart/alternative; boundary="Boundary_(ID_Uv2/2YEaDRIyrCp3X2Rbzw)" This is a multi-part message in MIME format. --Boundary_(ID_Uv2/2YEaDRIyrCp3X2Rbzw) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Hi, 1.What is the maximum number of simultaneous UDP sockets supports in 6lowPAN. 2.What will be the timeout value for UDP to receive data from a remote node in 6loWPAN. regards, Jibin --Boundary_(ID_Uv2/2YEaDRIyrCp3X2Rbzw) Content-type: text/html; charset=iso-8859-1 Content-transfer-encoding: 7BIT

Hi,

1.What is the maximum number of simultaneous UDP sockets supports in 6lowPAN.

2.What will be the timeout value for UDP to receive data from a remote node in 6loWPAN.

regards,

Jibin

--Boundary_(ID_Uv2/2YEaDRIyrCp3X2Rbzw)-- --===============2068230624== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www.ietf.org/mailman/listinfo/6lowpan --===============2068230624==-- From 6lowpan-bounces@ietf.org Wed Jan 14 13:24:53 2009 Return-Path: <6lowpan-bounces@ietf.org> X-Original-To: 6lowpan-archive@megatron.ietf.org Delivered-To: ietfarch-6lowpan-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 23AC83A6833; Wed, 14 Jan 2009 13:24:53 -0800 (PST) X-Original-To: 6lowpan@core3.amsl.com Delivered-To: 6lowpan@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 86BAE3A6833 for <6lowpan@core3.amsl.com>; Wed, 14 Jan 2009 13:24:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.5 X-Spam-Level: X-Spam-Status: No, score=-2.5 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g2jkWpWyiHra for <6lowpan@core3.amsl.com>; Wed, 14 Jan 2009 13:24:50 -0800 (PST) Received: from server1.coslabs.com (grab.coslabs.com [199.233.92.34]) by core3.amsl.com (Postfix) with ESMTP id B7D8E3A67F9 for <6lowpan@ietf.org>; Wed, 14 Jan 2009 13:24:50 -0800 (PST) Received: from [199.233.92.20] (dev20.coslabs.com [199.233.92.20]) by server1.coslabs.com (8.13.6/8.13.6) with ESMTP id n0ELOXfr026771; Wed, 14 Jan 2009 14:24:34 -0700 (MST) From: Geoff Mulligan To: Jibin K In-Reply-To: <007b01c97548$f6e6dd70$9d206c6b@semco> References: <007b01c97548$f6e6dd70$9d206c6b@semco> Date: Wed, 14 Jan 2009 14:24:29 -0700 Message-Id: <1231968269.5954.1187.camel@DellX1> Mime-Version: 1.0 X-Mailer: Evolution 2.24.2 Cc: 6lowpan@ietf.org Subject: Re: [6lowpan] 6loWPAN UDP Receive timeout X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: 6lowpan-bounces@ietf.org Errors-To: 6lowpan-bounces@ietf.org Jibin, I think that both of these numbers are entirely implementation dependent. Perhaps some of the implementors might give us some idea of just what they have done. geoff On Tue, 2009-01-13 at 12:04 +0530, Jibin K wrote: > Hi, > > > 1.What is the maximum number of simultaneous UDP sockets supports in > 6lowPAN. > > 2.What will be the timeout value for UDP to receive data from a remote > node in 6loWPAN. > > > regards, > Jibin > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Thu Jan 15 08:56:41 2009 Return-Path: <6lowpan-bounces@ietf.org> X-Original-To: 6lowpan-archive@megatron.ietf.org Delivered-To: ietfarch-6lowpan-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C4483A6A2D; Thu, 15 Jan 2009 08:56:41 -0800 (PST) X-Original-To: 6lowpan@core3.amsl.com Delivered-To: 6lowpan@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD04E28C150 for <6lowpan@core3.amsl.com>; Thu, 15 Jan 2009 08:56:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.499 X-Spam-Level: X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FORGED_MUA_THEBAT_CS=1.15, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id shDPbLceeono for <6lowpan@core3.amsl.com>; Thu, 15 Jan 2009 08:56:38 -0800 (PST) Received: from mailrelay1.uni-rostock.de (mailrelay1.uni-rostock.de [139.30.8.201]) by core3.amsl.com (Postfix) with SMTP id 312B93A6962 for <6lowpan@ietf.org>; Thu, 15 Jan 2009 08:56:37 -0800 (PST) Received: from antivirus.exch.rz.uni-rostock.de (127.0.0.1) by antivirus.uni-rostock.de (127.0.0.1) with Microsoft SMTP Server id 8.1.336.0; Thu, 15 Jan 2009 17:56:17 +0100 Received: from antivirus.uni-rostock.de (unverified) by antivirus.exch.rz.uni-rostock.de (Clearswift SMTPRS 5.2.9) with ESMTP id for <6lowpan@ietf.org> (AUTH = <>); Thu, 15 Jan 2009 17:56:17 +0100 Received: from mail.uni-rostock.de (139.30.8.11) by antivirus.exch.rz.uni-rostock.de (139.30.8.12) with Microsoft SMTP Server id 8.1.336.0; Thu, 15 Jan 2009 17:56:17 +0100 Received: from schlappi.mshome.net ([139.30.201.156]) by mail2.uni-rostock.de (iPlanet Messaging Server 5.2 HotFix 2.17 (built Mar 28 2007)) with ESMTPS id <0KDI000GZS3KU7@mail.uni-rostock.de> for 6lowpan@ietf.org; Thu, 15 Jan 2009 16:52:32 +0100 (MET) Date: Thu, 15 Jan 2009 16:52:27 +0100 From: Guido Moritz To: 6lowpan@ietf.org Message-ID: <1796634622.20090115165227@uni-rostock.de> MIME-Version: 1.0 X-Mailer: The Bat! (v3.99.24) Professional X-Priority: 3 (Normal) Subject: [6lowpan] Multicast mapping X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Guido Moritz List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Sender: 6lowpan-bounces@ietf.org Errors-To: 6lowpan-bounces@ietf.org Hi, I found some documentation about compression of multicast headers. But I could not find information how multicast is mapped to 802.15.4. In a Beacon enabled network, does every endpoint (RFD) has to wake up and receive the message from the coordinator/router (FFD) before analyzing it on IP layer and detecting, that it don't wants to have it? So this is a quit big issue, because every multicast packet would flood the complete network. As I know IPv6 can define multicast groups and addresses which are even forwarded by routers (site-local and its successor?!). So even external multicasts can flood networks with 6LoWPAN?! Or are the routers/coordinators "intelligent" enough and an endpoint (RFD) can "advise" the router/coordinator to forward the specific multicast messages? Are any information for this somewhere to be found? Thank you for your help... Kind Regards Guido Moritz ------------------------- Dipl. Ing. Guido Moritz Universitaet Rostock, Fakultaet f. Informatik und Elektrotechnik Institut f. Angewandte Mikroelektronik und Datentechnik University of Rostock, Department of CS and EE Institute of Applied Microelectronics and Computer Engineering Richard-Wagner Str. 31, 18119 Rostock-Warnemuende Phone:=A0 +49 (0)381 498 - 7269 http://www.imd.uni-rostock.de http://www.aal-rostock.de _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Thu Jan 29 06:42:02 2009 Return-Path: <6lowpan-bounces@ietf.org> X-Original-To: 6lowpan-archive@megatron.ietf.org Delivered-To: ietfarch-6lowpan-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4AF6328C1AF; Thu, 29 Jan 2009 06:42:02 -0800 (PST) X-Original-To: 6lowpan@core3.amsl.com Delivered-To: 6lowpan@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 345B83A69B4 for <6lowpan@core3.amsl.com>; Thu, 29 Jan 2009 06:42:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.499 X-Spam-Level: X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FORGED_MUA_THEBAT_CS=1.15, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DVyU2a1gg2Ce for <6lowpan@core3.amsl.com>; Thu, 29 Jan 2009 06:42:00 -0800 (PST) Received: from mailrelay1.uni-rostock.de (mailrelay1.uni-rostock.de [139.30.8.201]) by core3.amsl.com (Postfix) with SMTP id E4B143A6858 for <6lowpan@ietf.org>; Thu, 29 Jan 2009 06:41:59 -0800 (PST) Received: from antivirus.exch.rz.uni-rostock.de (127.0.0.1) by antivirus.uni-rostock.de (127.0.0.1) with Microsoft SMTP Server id 8.1.336.0; Thu, 29 Jan 2009 15:41:30 +0100 Received: from antivirus.uni-rostock.de (unverified) by antivirus.exch.rz.uni-rostock.de (Clearswift SMTPRS 5.2.9) with ESMTP id for <6lowpan@ietf.org> (AUTH = <>); Thu, 29 Jan 2009 15:41:30 +0100 Received: from mail.uni-rostock.de (139.30.8.11) by antivirus.exch.rz.uni-rostock.de (139.30.8.12) with Microsoft SMTP Server id 8.1.336.0; Thu, 29 Jan 2009 15:41:29 +0100 Received: from schlappi.mshome.net ([139.30.201.156]) by mail2.uni-rostock.de (iPlanet Messaging Server 5.2 HotFix 2.17 (built Mar 28 2007)) with ESMTPS id <0KE800APYM556G@mail.uni-rostock.de> for 6lowpan@ietf.org; Thu, 29 Jan 2009 15:41:29 +0100 (MET) Date: Thu, 29 Jan 2009 15:41:27 +0100 From: Guido Moritz To: 6lowpan@ietf.org Message-ID: <5610139468.20090129154127@uni-rostock.de> MIME-Version: 1.0 X-Mailer: The Bat! (v3.99.24) Professional X-Priority: 3 (Normal) Subject: [6lowpan] Questions about RFC 4944 X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Guido Moritz List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Sender: 6lowpan-bounces@ietf.org Errors-To: 6lowpan-bounces@ietf.org Hello, I just finished going through RFC4944 and I have three questions left, I cannot understand. Maybe you can help me with that and provide me with a better understanding. 1. Section 8 The type field is 8 bit. Why is it so big? The length field is units of 8: I understand it as multiples of 8-bit. Why means value 1 16-bit and value 2 64-bit addresses? It should be 8-bit and 16-bit with the values 1 and 1?! 2. Section 9 What is the reason, that mulitcast address mapping only has to be supported in mesh-enabled networks? What is the concept behind that. Thank you for your answers. Kind Regards Guido Moritz ------------------------- Dipl. Ing. Guido Moritz Universitaet Rostock, Fakultaet f. Informatik und Elektrotechnik Institut f. Angewandte Mikroelektronik und Datentechnik University of Rostock, Department of CS and EE Institute of Applied Microelectronics and Computer Engineering Richard-Wagner Str. 31, 18119 Rostock-Warnemuende Phone:=A0 +49 (0)381 498 - 7269 http://www.imd.uni-rostock.de http://www.aal-rostock.de _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www.ietf.org/mailman/listinfo/6lowpan From 6lowpan-bounces@ietf.org Thu Jan 29 06:58:14 2009 Return-Path: <6lowpan-bounces@ietf.org> X-Original-To: 6lowpan-archive@megatron.ietf.org Delivered-To: ietfarch-6lowpan-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 89E1D3A69FD; Thu, 29 Jan 2009 06:58:14 -0800 (PST) X-Original-To: 6lowpan@core3.amsl.com Delivered-To: 6lowpan@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A8D713A69B4 for <6lowpan@core3.amsl.com>; Thu, 29 Jan 2009 06:58:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l9Wf7MJDTjf1 for <6lowpan@core3.amsl.com>; Thu, 29 Jan 2009 06:58:12 -0800 (PST) Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 3A9FF3A69FD for <6lowpan@ietf.org>; Thu, 29 Jan 2009 06:58:12 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,344,1231113600"; d="scan'208";a="32310336" Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 29 Jan 2009 14:57:53 +0000 Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n0TEvqA4006777; Thu, 29 Jan 2009 15:57:52 +0100 Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n0TEvrR1000585; Thu, 29 Jan 2009 14:57:53 GMT Received: from xmb-ams-33d.emea.cisco.com ([144.254.231.92]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 29 Jan 2009 15:57:52 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 29 Jan 2009 15:57:51 +0100 Message-ID: <38F26F36EAA981478A49D1F37F474A860291BC19@xmb-ams-33d.emea.cisco.com> In-Reply-To: <5610139468.20090129154127@uni-rostock.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6lowpan] Questions about RFC 4944 Thread-Index: AcmCH/E2+UfUHh+IRFixsJpoxhvQiwAAFpUQ References: <5610139468.20090129154127@uni-rostock.de> From: "Julien Abeille (jabeille)" To: "Guido Moritz" , <6lowpan@ietf.org> X-OriginalArrivalTime: 29 Jan 2009 14:57:52.0820 (UTC) FILETIME=[F5EC3740:01C98221] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2152; t=1233241072; x=1234105072; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jabeille@cisco.com; z=From:=20=22Julien=20Abeille=20(jabeille)=22=20 |Subject:=20RE=3A=20[6lowpan]=20Questions=20about=20RFC=204 944 |Sender:=20; bh=wFHseoTl4OXlGgLV0Z3DnVBR6AttmfjKjT2T1CtpDco=; b=S3Jm52cGLhwFRDGCY3dmfnSCyRmVbbk9rnFB2a7AUatlQ5aj3f59rRUknX sg5Wm333fmnhs5mCBZ27leqY4s1z5M7I+0LqAX2BgwG04cXHBFgINk93pPZP O8uQ1tzTs0; Authentication-Results: ams-dkim-1; header.From=jabeille@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; ); Subject: Re: [6lowpan] Questions about RFC 4944 X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: 6lowpan-bounces@ietf.org Errors-To: 6lowpan-bounces@ietf.org Hi Guido, Type and length fields in section 8 are defined in Neighbor Discovery. The = amount of ND options may not be that huge even in future extensions, but co= mpressing thiese fields is not in the charter for now. The length is in units of 8 bytes. For example, over Ethernet, length would= be 1 (type+length+6bytes Ethernet address->8bytes) With a 16-bit address, you will need 4 bytes (type + length + 2 bytes addre= ss), plus 4 bytes of padding to reach a multiple of 8, hence total is 8, le= ngth field is 1 With a 64-bit address, you will need 10 bytes (type + length + 8 bytes addr= ess), plus 6 bytes of padding, total is 16, length field is 2. Best, Julien -----Original Message----- From: 6lowpan-bounces@ietf.org [mailto:6lowpan-bounces@ietf.org] On Behalf = Of Guido Moritz Sent: jeudi 29 janvier 2009 15:41 To: 6lowpan@ietf.org Subject: [6lowpan] Questions about RFC 4944 Hello, I just finished going through RFC4944 and I have three questions left, I ca= nnot understand. Maybe you can help me with that and provide me with a bett= er understanding. 1. Section 8 The type field is 8 bit. Why is it so big? The length field is units of 8: I understand it as multiples of 8-bit. Why means value 1 16-bit and value 2 64-bit addresses? It should be 8-bit a= nd 16-bit with the values 1 and 1?! 2. Section 9 What is the reason, that mulitcast address mapping only has to be supported= in mesh-enabled networks? What is the concept behind that. Thank you for your answers. Kind Regards Guido Moritz ------------------------- Dipl. Ing. Guido Moritz Universitaet Rostock, Fakultaet f. Informatik und Elektrotechnik Institut f= . Angewandte Mikroelektronik und Datentechnik University of Rostock, Depart= ment of CS and EE Institute of Applied Microelectronics and Computer Engine= ering Richard-Wagner Str. 31, 18119 Rostock-Warnemuende Phone:=A0 +49 (0)381 498 - 7269 http://www.imd.uni-rostock.de http://www.aal-rostock.de _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www.ietf.org/mailman/listinfo/6lowpan