IETF Logo Mail Archive

Re: [6lowpan] Re: [RSN] The need for RSN

"Daniel Park" <soohongp@gmail.com> Sun, 24 June 2007 23:51 UTC

Return-path: <6lowpan-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I2brb-0005z5-UJ; Sun, 24 Jun 2007 19:51:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I2bra-0005yq-3F for 6lowpan@lists.ietf.org; Sun, 24 Jun 2007 19:51:26 -0400
Received: from py-out-1112.google.com ([64.233.166.181]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2brY-00013Z-TX for 6lowpan@lists.ietf.org; Sun, 24 Jun 2007 19:51:26 -0400
Received: by py-out-1112.google.com with SMTP id u77so1438179pyb for <6lowpan@lists.ietf.org>; Sun, 24 Jun 2007 16:51:24 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=cJGY7HEW4ZD1XRCj5uGySsiYhYOsV5pgZkTfy7QhLZRsA4ELvy81kaHCATedMpbSpXU0FEGlNB+ZnDtIWO3IUQOY9XwWaH/2SvgKCaw9jvkNGtOIjpeUAI+UY6eS5NA6vIYWXa2cd+xUoXVxsPa54oZa9Q/vXRceyEkepSzwGGo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Ouac64lGzE+60YSctnSt5YghWj7UGeyreKXmJ86RWqM2JYuWLSeaZ5iz+KAdiJtSPV6uLbY73QdJ5B9ItdDFmUwPo1sRMB7TmeO2r6rjqCL2Rrfq6ILKlu6jDfYAOK8a9ndVFMzZ59nRnlxg6s47x3T2P2IeNqJmqbtmZnAcJ6E=
Received: by 10.115.49.16 with SMTP id b16mr4931506wak.1182729083896; Sun, 24 Jun 2007 16:51:23 -0700 (PDT)
Received: by 10.115.94.7 with HTTP; Sun, 24 Jun 2007 16:51:23 -0700 (PDT)
Message-ID: <f7c7d76e0706241651y7f8c3wc21ac2f7d72818f2@mail.gmail.com>
Date: Mon, 25 Jun 2007 08:51:23 +0900
From: Daniel Park <soohongp@gmail.com>
To: JP Vasseur <jvasseur@cisco.com>
Subject: Re: [6lowpan] Re: [RSN] The need for RSN
In-Reply-To: <3AA57709-C2AB-477F-B398-813649DF97AE@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <1182473381.6218.137.camel@dellx1> <0JK000F4NOL629@mmp2.samsung.com> <77f1dba80706212323l77364169y6438cb86a81b44f0@mail.gmail.com> <3AA57709-C2AB-477F-B398-813649DF97AE@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: 6lowpan@lists.ietf.org, rsn@ietf.org
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/6lowpan>
List-Post: <mailto:6lowpan@ietf.org>
List-Help: <mailto:6lowpan-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=subscribe>
Errors-To: 6lowpan-bounces@ietf.org

> > We need to find out if we CAN take exisiting solutions or if we NEED
> > to design a new one. Clearly for me, to find out this answer is
> > 6lowpan's work.
> >
>
> As far as L3 routing is concerned, that task WOULD be the one of the
> POTENTIAL
> new WG work.

Well, those kinds of work can be taken place at the relevant WG in
advance. For example, one of MANET WG sessions for this issue. Than,
IETF can move it on if we can see any EXPLICIT

_______________________________________________
6lowpan mailing list
6lowpan@ietf.org
https://www1.ietf.org/mailman/listinfo/6lowpan

v2.36.0 | Report a Bug | By Email | System Status