IETF Logo Mail Archive

Re: more on ppp clarification ... [16NG] Re: multicast and IPv6 over ETHCS

Alexandru Petrescu <alexandru.petrescu@motorola.com> Wed, 17 January 2007 17:20 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H7ESy-0004kc-8m; Wed, 17 Jan 2007 12:20:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H7ESx-0004kU-60 for 16ng@ietf.org; Wed, 17 Jan 2007 12:20:51 -0500
Received: from mail119.messagelabs.com ([216.82.241.179]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1H7ESv-0003bi-UN for 16ng@ietf.org; Wed, 17 Jan 2007 12:20:51 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-2.tower-119.messagelabs.com!1169054449!13306430!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 25016 invoked from network); 17 Jan 2007 17:20:49 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-2.tower-119.messagelabs.com with SMTP; 17 Jan 2007 17:20:49 -0000
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l0HHKmKl008603; Wed, 17 Jan 2007 10:20:49 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117]) by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id l0HHKmum019038; Wed, 17 Jan 2007 11:20:48 -0600 (CST)
Message-ID: <45AE5AEF.2030206@motorola.com>
Date: Wed, 17 Jan 2007 18:20:47 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: more on ppp clarification ... [16NG] Re: multicast and IPv6 over ETHCS
References: <4BB931F00625F54DA8B8563E5A5CA25A013471AB@MCHP7I6A.ww002.siemens.net> <45AE570D.5010803@motorola.com>
In-Reply-To: <45AE570D.5010803@motorola.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
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

Alexandru Petrescu wrote:
>> If I am following your statement, PPP would not be in the scope of
>>  the IETF.
> 
> Right, that was solved by saying PPP is not link-layer but layer 2/3.
>  It doesn't build headers.  More recently one sees PANA (full UDP) 
> and EAP (independent of link-layer) and ppp doesn't get much upgrade
>  at  IETF.

Also, ppp-over-ethernet is informational.  But L2TP is what goes on
Standards Track, and L2TP+somePPPoE is informational while LCP+L2TP is
std track.

The second reason for mentioning this is that someone may think
something else than GRE could be used in a 802.16 deployment - it's the
case, so don't make GRE mandatory.

Alex


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

v2.8.7 | Report a Bug | By Email