Re: ppp - I'll stop discussing (was: [16NG] Re: multicast and IPv6 over ETHCS)

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

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H7F9n-0003na-Vl; Wed, 17 Jan 2007 13:05:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H7F9n-0003nV-Aa for 16ng@ietf.org; Wed, 17 Jan 2007 13:05:07 -0500
Received: from mail128.messagelabs.com ([216.82.250.131]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1H7F9l-00024t-Us for 16ng@ietf.org; Wed, 17 Jan 2007 13:05:07 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-6.tower-128.messagelabs.com!1169057104!11344662!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 31685 invoked from network); 17 Jan 2007 18:05:04 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-6.tower-128.messagelabs.com with SMTP; 17 Jan 2007 18:05:04 -0000
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l0HI50s9021013; Wed, 17 Jan 2007 11:05:00 -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 l0HI4xKQ012503; Wed, 17 Jan 2007 12:04:59 -0600 (CST)
Message-ID: <45AE654A.5080409@motorola.com>
Date: Wed, 17 Jan 2007 19:04:58 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Basavaraj Patil <basavaraj.patil@nokia.com>
Subject: Re: ppp - I'll stop discussing (was: [16NG] Re: multicast and IPv6 over ETHCS)
References: <C1D3BCF4.2C8C0%basavaraj.patil@nokia.com>
In-Reply-To: <C1D3BCF4.2C8C0%basavaraj.patil@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
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

Raj, thanks for the email.  I will not post further on this topic, not
because I don't want to reply to you, but because I've already got
private indication (from Chairs and AD) that I should stop ppp
discussion, there's nothing new or relevant to the IP-over-IP/ETHCS.

Alex

Basavaraj Patil wrote:
> The PPP that you are talking about is most likely not between your PC
>  card (that is implementing GPRS/HSDPA) and the GGSN.

I'm sorry but I don't care.  It's about my IP laptop and a certain
network.  IETF doesn't define what's GGSN nor SGSN.  I believe (not
sure) no deployment has strict GGSN/SGSN separation (separation
suggested by SDO and graduate textbooks).

> You could be doing PPP over a PDP context that is established between
>  the PC card and the GGSN. Question is, does the PPP terminate at the
>  GGSN? Of course not knowing what kind of service you are using or 
> details, I can only speculate.

YEs, I agree.  I no longer bother to even speculate, I'm torn down by
these speculations, too many traceroutes, too many pings, on every
operator's different topology.

I prefer to see it as a network into which I can ppp, with a certain
qos.  This is the typical point of view adopted by a end host.

>> Do you mean a SDO spec says that PDP context is set up?  And that 
>> that SDO document doesn't say 'ppp is used'?  I agree with this 
>> part.
> 
> PPP is an overhead and not required to transport IP packets in GPRS.

Well that's what many people do (see 'globally' interpreted at the end
of this message).  Not even Compression modules are used.  It works.

> PDP contexts are the mechanism used for carrying IP packets.

There's no IP-over-PDPcontext StdsTrack RFC, sorry.

I too run IPv6-over-RS232 w/o an RFC telling me how, it works, doesn't
upset anybody, and solves today's context sometimes (think really small
custom stuff).

SDO can do that too with its PDP contexts, unless it upsets somebody.

>>> PPPoE is NOT used in GPRS/UMTS or HSDPA.
>> What do you call a PPP ConfigReq within a MAC header with 48bits 
>> addresses, as displayed by Ethereal?  And with a pcmcia card saying
>>  hsdpa.
> 
> Your Ethereal may not really be have the drivers to read what is 
> being sent by the HSDPA card... I don't know.

WEll it does have necessary drivers telling me that.  It's enough for
making run the IPv6 stack, no more needed.

> As I said above, tell me where is PPP being terminated in the 
> network, i.e the GPRS core?

Sorry, I don't know precisely.  It terminates somewhere in the network.
  I could tell you all the experiments I've done to find that precise
question you ask, and how they were voided by simply connecting to
another operator.

>>> PDP context != PPP or PPPoE
>> I'm sorry.  PDP context is not something defined at IETF, a 
>> different beast, can't compare.
> 
> And I am not asking you to do so. I was just correcting a statement 
> about PPP usage that you made. And it appeared to be a globally 
> applicable statement to all GPRS/UMTS/HSDPA deployments.

Ok, what's globally applicable.  To me globally applicable is the
following: google APN name and find the name of operators that will
allow one to ppp into their cell networks.  One will find cell operators
all over the world.  I've personally tried a bunch of them in Europe and
the 2-3 available in US.  GPRS and UMTS and HSDPA.  Is this globally 
applicable to you?

Alex

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