Re: [16NG] multiple encapsulation issue

"Daniel Park" <soohongp@gmail.com> Sun, 18 March 2007 19:55 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 1HT1Tb-0007ZD-Fg; Sun, 18 Mar 2007 15:55:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HT1Ta-0007Z7-1i for 16ng@ietf.org; Sun, 18 Mar 2007 15:55:34 -0400
Received: from ug-out-1314.google.com ([66.249.92.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HT1TY-0007QI-Oy for 16ng@ietf.org; Sun, 18 Mar 2007 15:55:34 -0400
Received: by ug-out-1314.google.com with SMTP id 72so1040153ugd for <16ng@ietf.org>; Sun, 18 Mar 2007 12:55:31 -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=FXiakUyyIlKyFVFT2KbGjNOf3LMrzxTlc+bpzn1eNsqULiqjFqsU1gH0gqblJETNNfgRE9VRb7MaKJDlnhWQ8r0b/9HCcmv7mHjYONF8BVIlFOR75a2g7uzGvE4Lu2NVPSOI4OMD26ax0EvMP3ZruD6KQsobeRwREIsASIdwrbM=
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=GzE8m4R3xB2HPz9NjXyikkPoXkmAWMj03wKvCAyyw1Obh3k6YahmpaO/kYwhDbRYhx233gQ7+KvZ7i09WaCGIZpNwe8FReBy4HylFek8ayFrpkjtEAaN1jys1Xs7f1KzV2m9gJFXNnSHKzMQ8o970qvnptftcsdwe3LFM7VFv0k=
Received: by 10.65.53.3 with SMTP id f3mr5846932qbk.1174247730909; Sun, 18 Mar 2007 12:55:30 -0700 (PDT)
Received: by 10.115.94.12 with HTTP; Sun, 18 Mar 2007 12:55:30 -0700 (PDT)
Message-ID: <f7c7d76e0703181255j46875865j21f67dc746f882ba@mail.gmail.com>
Date: Mon, 19 Mar 2007 04:55:30 +0900
From: "Daniel Park" <soohongp@gmail.com>
To: "Bruno Miguel Sousa" <bmsousa@dei.uc.pt>
Subject: Re: [16NG] multiple encapsulation issue
In-Reply-To: <45FD8536.2080902@dei.uc.pt>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <f7c7d76e0703140905q7c0251e7o36e01ad41ed89376@mail.gmail.com> <45FD8536.2080902@dei.uc.pt>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
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

> > 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.
> One more.
> Tomorrow I can present myself to Alexandru Petrescu and others volunteers
> to this work.

Are you saying tomorrow afternoon 16ng session ? Unfortunately, we
have more priority tomorrow. If you can speak about it in Friday
morning session, that would be great...

-- 


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

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