IETF Logo Mail Archive

[16NG] multiple encapsulation issue

"Daniel Park" <soohongp@gmail.com> Wed, 14 March 2007 16:05 UTC

Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRVz9-0000Jw-FN; Wed, 14 Mar 2007 12:05:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRVz8-0000Jo-Gr for 16ng@ietf.org; Wed, 14 Mar 2007 12:05:54 -0400
Received: from wr-out-0506.google.com ([64.233.184.232]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRVz7-0004o6-Am for 16ng@ietf.org; Wed, 14 Mar 2007 12:05:54 -0400
Received: by wr-out-0506.google.com with SMTP id 68so203827wra for <16ng@ietf.org>; Wed, 14 Mar 2007 09:05:53 -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:mime-version:content-type:content-transfer-encoding:content-disposition; b=fHRIILqOwjnvS7CK1yz4jWjFYfF4bYg9n+Y6dQ0D3vn/yJ41Ci+wsZh1Ue1NHQTVN3PkVdsmxaY70QKpygZBRolQ1bFXodBydY8Bxo8cE+qEHBqVtFMut6cx0DEjuT7W8Zu/qTdAdBVGhtBQxAnHjZxZle2L3yCZ84DMQoNZ3PA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=GNrwIai9jBxeaZXB6XczjJ1HcEOfJv8Y9dR1GdKhsRmb5cA1r8ZiIt8q+w5PqAvh5p2U92gfbczRQxgmDlT3oKoaHMrQdWHRWuNkdNHVtD4bOHs46QNJLqFNE5MTa/bpt7UJ1zlcjEBmlQ4F3T8sAZzbC+b3l04MVduUstksth4=
Received: by 10.114.161.11 with SMTP id j11mr2947816wae.1173888352244; Wed, 14 Mar 2007 09:05:52 -0700 (PDT)
Received: by 10.115.94.12 with HTTP; Wed, 14 Mar 2007 09:05:52 -0700 (PDT)
Message-ID: <f7c7d76e0703140905q7c0251e7o36e01ad41ed89376@mail.gmail.com>
Date: Thu, 15 Mar 2007 01:05:52 +0900
From: Daniel Park <soohongp@gmail.com>
To: 16ng@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Subject: [16NG] multiple encapsulation issue
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org

Folks,

As you are aware of, IAB is in the progress of spelling out multiple
encapsulation considerations. The latest publication is
draft-iab-link-encaps-08. It indicates lot of considerations to the
usage of 802.16 multiple convergence sublayers. I am thinking of
dealing with this issue in this list more detail and precise than now.
I believe it would be valuable effort at this stage prior to moving
this document forward.

What do you think ?

Question 1: Are you thinking that we need to do this in 16ng ?
If yes, go to Question 2
If no, let me know why

Question 2: How many folks are willing to work on that together ?
Most activities are to analyze IAB document first and make a clear
answer to all of considerations. If necessary, drafting would be good
for folks information.

Results will be shown at the next meeting in Chicago hopefully.

-- 


Daniel (Soohong Daniel Park)
Mobile Convergence Laboratory, SAMSUNG Electronics.

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng

v2.23.0 | Report a Bug | By Email