[115209] in North American Network Operators' Group
Re: Traffic billing - L2 encap to include or not?
daemon@ATHENA.MIT.EDU (Renaud RAKOTOMALALA)
Fri Jun 12 09:48:53 2009
Date: Fri, 12 Jun 2009 15:48:37 +0200
From: Renaud RAKOTOMALALA <renaud@rakotomalala.com>
To: "Weber, Markus" <fvd@de.kpn-eurorings.net>
In-Reply-To: <sig.24142b5b8f.7707838BF569B24DBBDB8F54AB67B67F02CC58A2@foo.kpnqwest.de>
X-Assp-Envelope-From: renaud@rakotomalala.com
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Weber, Markus a écrit :
> We all have our billing systems for traffic (bought, downloaded or
> home made, volume based or usage). We all got hit by fancy SNMP
> bugs of various vendors and we all suffer from the fact, that SNMP
> counters do not carry a time stamp, when they had been taken from
> the ASICs, causing a slight derivation. [...]
>
> [../..]
> So, is L2 encapsulation (e.g. Ethernet) considered as framing characters
> or not?
> [../..]
>
Hello,
To my point of view, if you base your billing from L2 encapsulation you
gonna bill your customers on local networks problems like, problems on
L2 frames, padding (as you explain).
These kind of problematic (again to my point of view) is the problem of
the provider and not of the customer who buy IP traffic and not L2 traffic.
Renaud
