[L2tpext] Regarding L2TP version 3 implementation with DEPI extentions
"Akshay" <akshay.ranjan@reliancemail.net> Fri, 01 February 2008 19:14 UTC
Return-Path: <l2tpext-bounces@ietf.org>
X-Original-To: ietfarch-l2tpext-archive@core3.amsl.com
Delivered-To: ietfarch-l2tpext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6267C28C4DD; Fri, 1 Feb 2008 11:14:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.314
X-Spam-Level: **
X-Spam-Status: No, score=2.314 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, MSGID_MULTIPLE_AT=1.449]
Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09iHA5VuLrot; Fri, 1 Feb 2008 11:14:19 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B36C28C641; Fri, 1 Feb 2008 11:12:06 -0800 (PST)
X-Original-To: l2tpext@core3.amsl.com
Delivered-To: l2tpext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 067D928C641 for <l2tpext@core3.amsl.com>; Fri, 1 Feb 2008 11:12:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uhGAESO2v2RA for <l2tpext@core3.amsl.com>; Fri, 1 Feb 2008 11:12:04 -0800 (PST)
Received: from P142XFEP01.ricmail.com (mx1.reliancemail.net [202.138.126.70]) by core3.amsl.com (Postfix) with ESMTP id 58E0928C7EC for <l2tpext@ietf.org>; Fri, 1 Feb 2008 11:05:52 -0800 (PST)
Received: from scorpio ([97.253.29.238]) by P142XFEP01.ricmail.com with ESMTP id <20080201190718.KIMA4328.P142XFEP01.ricmail.com@scorpio> for <l2tpext@ietf.org>; Sat, 2 Feb 2008 00:37:18 +0530
From: Akshay <akshay.ranjan@reliancemail.net>
To: l2tpext@ietf.org
Date: Sat, 02 Feb 2008 00:37:23 +0530
Message-ID: <003f01c86505$ad9a94d0$08cfbe70$@ranjan>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AchlBZzGj3lxlMD+RHi4M83tE7UMUQ==
Content-Language: en-us
x-cr-hashedpuzzle: Ajyk A9dN BWnw CWzL D7Qp E5TV FSrd FfIm HgGt IdaO I8Mm JYI9 KeSh Ke7u Khuw LCyy; 1; bAAyAHQAcABlAHgAdABAAGkAZQB0AGYALgBvAHIAZwA=; Sosha1_v1; 7; {DB9CF784-C45B-4759-9212-248F84D86A3E}; YQBrAHMAaABhAHkALgByAGEAbgBqAGEAbgBAAHIAZQBsAGkAYQBuAGMAZQBtAGEAaQBsAC4AbgBlAHQA; Fri, 01 Feb 2008 19:06:56 GMT; UgBlAGcAYQByAGQAaQBuAGcAIABMADIAVABQACAAdgBlAHIAcwBpAG8AbgAgADMAIABpAG0AcABsAGUAbQBlAG4AdABhAHQAaQBvAG4AIAB3AGkAdABoACAARABFAFAASQAgAGUAeAB0AGUAbgB0AGkAbwBuAHMA
x-cr-puzzleid: {DB9CF784-C45B-4759-9212-248F84D86A3E}
Subject: [L2tpext] Regarding L2TP version 3 implementation with DEPI extentions
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/l2tpext>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: l2tpext-bounces@ietf.org
Errors-To: l2tpext-bounces@ietf.org
Hi, Currently I am starting work on implementing a L2TP version 3 solution with DEPI extensions from scratch. I read the base 3931 rfc and understood that l2tp is still evolving and new pseudo wires, services and extensions are constantly been published. In order to successfully implement and test an rfc3931 solution, I may need to support all the additional rfcs that are published so far. I am thinking of implementing the solution as modules. The base module will be compliant to rf3931 while the other extensions can be added as 'profiles'. Lets call them as l2tp profiles. The profiles work more or less like plug-ins that extend the functionality of the base module. As a general idea, lets say I have following 'l2tp profiles', 1. l2tp version 2 - Contains all the mandatory and optional AVPs for tunnel setup teardown. 2. l2tp base - Contains all the mandatory and optional AVPs for tunnel setup and teardown. 3. l2tp atm - Contains all the mandatory and optional AVPs for tunneling ATM cells. The profiles will be hierarchical, as in if the l2tp atm extension is configured then the AVP set will contain AVPs from l2tp base as well as l2tp atm profiles. I would like suggestions on this idea, if it can prove beneficial in terms of implementation. FYI, my target platform is vxWorks. DEPI stands for DOCSIS External Phy Interface in DOCSIS 3.0 specifications. Thanx, Akshay. _______________________________________________ L2tpext mailing list L2tpext@ietf.org http://www.ietf.org/mailman/listinfo/l2tpext