Re: [16NG] multiple encapsulation issue

Alexandru Petrescu <alexandru.petrescu@gmail.com> Wed, 14 March 2007 20:06 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 1HRZkJ-0006OG-1D; Wed, 14 Mar 2007 16:06:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRZkI-0006Np-7s for 16ng@ietf.org; Wed, 14 Mar 2007 16:06:50 -0400
Received: from mail119.messagelabs.com ([216.82.241.179]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HRZkG-0001xl-G7 for 16ng@ietf.org; Wed, 14 Mar 2007 16:06:50 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-11.tower-119.messagelabs.com!1173902807!17295790!1
X-StarScan-Version: 5.5.10.7.1; banners=.,-,-
X-Originating-IP: [144.189.100.103]
Received: (qmail 28152 invoked from network); 14 Mar 2007 20:06:47 -0000
Received: from motgate3.mot.com (HELO motgate3.mot.com) (144.189.100.103) by server-11.tower-119.messagelabs.com with SMTP; 14 Mar 2007 20:06:47 -0000
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234]) by motgate3.mot.com (8.12.11/Motorola) with ESMTP id l2EK6kBT007957; Wed, 14 Mar 2007 13:06:46 -0700 (MST)
Received: from az10vts04 (az10vts04.mot.com [10.64.251.245]) by az33exr04.mot.com (8.13.1/Vontu) with SMTP id l2EK6kWs023621; Wed, 14 Mar 2007 15:06:46 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117]) by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id l2EK6jba023604; Wed, 14 Mar 2007 15:06:45 -0500 (CDT)
Message-ID: <45F855D4.1090607@gmail.com>
Date: Wed, 14 Mar 2007 21:06:44 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Daniel Park <soohongp@gmail.com>
Subject: Re: [16NG] multiple encapsulation issue
References: <f7c7d76e0703140905q7c0251e7o36e01ad41ed89376@mail.gmail.com>
In-Reply-To: <f7c7d76e0703140905q7c0251e7o36e01ad41ed89376@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Vontu: Pass
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: 16ng@ietf.org
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

Daniel Park wrote:
> 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 ?

I like these kinds of documents.

> Question 1: Are you thinking that we need to do this in 16ng ?
> If yes, go to Question 2

I personally think yes.

> If no, let me know why
> 
> Question 2: How many folks are willing to work on that together ?

I.

> 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.

Sounds good.  There are two recommendations in  that draft that should 
sound very provokative, by my understanding of this WG:

draft-iab-link-encaps-08.txt:
>     When developing standards for encapsulating IP packets on a link
>       layer technology, it is desirable that only a single encapsulation
>       method should be standardized for each link layer technology;
[...]
>    Recommendations: Given these issues, it is strongly recommended that
>    only a single kind of CS supporting a single encapsulation method
>    should be usable on a particular link.

I mean knowing both ETHCS and IPCS are under specification this would 
sound like a need to join the two.  Or maybe separate one as ptp and the 
other as mcast... not sure I get this right.

But yes, I can contribute to this discussion.

Alex


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


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

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