Net Onnet represents a cornerstone of modern telecom infrastructure, defining the efficiency and cost dynamics of carrier-grade network traffic. At its core, this concept distinguishes between optimized internal routing and external transit, directly influencing performance, billing structures, and regulatory compliance. From peering agreements to latency-sensitive applications, understanding Net Onnet is essential for ISPs, network architects, and policymakers navigating the complexities of high-speed connectivity. This exploration dissects its technical underpinnings, financial implications, and architectural optimizations while addressing the regulatory frameworks that shape its implementation.
The distinction between Net Onnet and Net Offnet traffic transcends mere terminology—it dictates operational efficiency, revenue models, and service quality. By examining real-world deployments, billing disputes, and hardware configurations, this discussion equips stakeholders with actionable insights to align network strategies with both technical and commercial objectives. Whether optimizing routing protocols or mitigating compliance risks, the principles governing Net Onnet traffic demand precision and foresight in an increasingly interconnected digital landscape.
Technical Definition and Core Concepts of "Net Onnet"
The term "Net Onnet" refers to a fundamental routing and billing classification in telecommunications and carrier-grade networks, defining traffic that originates and terminates within the same network or between networks under a shared peering or interconnection agreement. Its origins trace back to the early days of telephony and data networking, where carriers optimized cost efficiency by prioritizing traffic within their own infrastructure or between trusted partners. Today, it remains a critical concept in Internet Exchange Points (IXPs), Mobile Virtual Network Operators (MVNOs), and Content Delivery Networks (CDNs), ensuring efficient traffic management, reduced latency, and cost-effective billing.
Net Onnet traffic is characterized by its direct routing path, predefined peering agreements, and mutual billing settlements between carriers. It contrasts sharply with Net Offnet traffic, which incurs higher costs due to indirect routing and third-party intermediaries. The distinction influences network performance, financial settlements, and service-level agreements (SLAs) across global telecom ecosystems.
Structural Breakdown: Net Onnet vs. Net Offnet
The following table compares Net Onnet and Net Offnet across key dimensions, highlighting their operational and financial implications in carrier networks.
Terminology
Traffic Type
Billing Implications
Network Path
Example Scenarios
Net Onnet
Traffic exchanged between:
Two nodes within the same carrier’s network (e.g., mobile core to base station).
Peered networks via direct agreements (e.g., AT&T and Verizon peering at an IXP).
Partners under roaming or MVNO agreements (e.g., Vodafone and a local MVNO in Europe).
No or minimal intercarrier settlement fees (settled via peering policies).
Costs borne internally or shared via predefined agreements.
May include reciprocal billing (e.g., "pay-as-you-go" peering).
Direct routing via internal backbone or peering links.
No third-party transit required.
Optimized for lowest latency and highest throughput.
A user on T-Mobile calling another T-Mobile subscriber.
Traffic between Google’s CDN and a peered ISP at DE-CIX.
Roaming data between Orange (France) and Digicel (Caribbean) under a bilateral agreement.
Net Offnet
Traffic routed between non-peered or non-affiliated networks, requiring intermediaries.
Cross-carrier calls (e.g., AT&T to Sprint without peering).
Transit-dependent traffic (e.g., a small ISP relying on Level 3 for global reach).
International roaming outside predefined agreements.
High intercarrier settlement fees (e.g., $0.05–$0.20 per minute for voice, variable for data).
Transit costs from third-party providers (e.g., $50–$500/Mbps for international transit).
Dynamic pricing based on demand and geography.
Indirect routing via transit providers or settlement-free peering fallbacks.
Potential for suboptimal paths (e.g., traffic detoured to reduce costs).
Higher latency and packet loss risk due to longer hops.
A user on Verizon calling a T-Mobile subscriber with no direct peering.
An African ISP routing traffic to Netflix via a European transit provider.
Emergency roaming on a carrier’s network outside its home region.
Key Insight:
Net Onnet traffic minimizes operational expenditure (OPEX) and capital expenditure (CAPEX) by leveraging direct paths, while Net Offnet traffic introduces financial and performance overheads that carriers seek to mitigate through strategic peering or transit optimization.
Role of Net Onnet in Carrier-Grade Networks
Net Onnet traffic underpins the efficiency of carrier-grade networks by enabling:
1. Direct Routing: Eliminates reliance on third-party transit, reducing dependency on external providers and associated costs.
2. Peering Agreements: Facilitates settlement-free peering at IXPs (e.g., AMS-IX, Equinix) or via private peering between carriers, ensuring traffic stays within optimized paths.
3. Interconnection Policies: Governs how carriers exchange traffic under bilateral agreements (e.g., roaming) or multilateral peering (e.g., IXP membership tiers).
4. Traffic Engineering: Allows carriers to prioritize Onnet traffic in Quality of Service (QoS) policies, ensuring critical services (e.g., VoIP, real-time gaming) maintain performance.
Critical Applications:
Mobile Core Networks: Traffic between an EPC (Evolved Packet Core) and RAN (Radio Access Network) is inherently Onnet, avoiding backhaul inefficiencies.
CDN and Edge Computing: Content delivery from a CDN’s edge server to a peered ISP bypasses transit costs, reducing latency for end-users.
Enterprise VPNs: Traffic between branch offices connected via a carrier’s MPLS network remains Onnet, ensuring consistent QoS.
Procedure for Identifying Net Onnet vs. Net Offnet Sessions
Determining whether a network session is Net Onnet or Net Offnet requires analyzing routing tables, peering agreements, and traffic metadata. The following step-by-step procedure ensures accurate classification:
1. Examine Source and Destination AS Numbers (ASNs)
Retrieve the Autonomous System (AS) numbers of the source and destination networks using tools like BGPmon or RIPEstat.
Onnet Condition: ASNs belong to the same carrier or are part of a peering agreement (e.g., both AS1234 and AS5678 are members of DE-CIX).
Offnet Condition: ASNs are unrelated, requiring transit or settlement.
2. Check PeeringDB or IXP Membership Lists
Consult PeeringDB (peeringdb.com) to verify if the ASNs have a direct peering relationship at an IXP.
Example: If AS1234 (AT&T) and AS5678 (Google) are both listed as peers at Equinix Chicago, traffic between them is Onnet.
3. Review BGP Route Attributes
Inspect BGP announcements for the AS_PATH attribute. A shorter AS_PATH (e.g., `[AS1234 AS5678]`) indicates direct peering, while a longer path (e.g., `[AS1234 AS9999 AS5678]`) suggests transit via a third party (AS9999).
Community Tags: Look for BGP communities like `65001:100` (indicating Onnet traffic in some carrier implementations).
4. Validate Roaming or MVNO Agreements
For mobile traffic, cross-reference with GSMA roaming agreements or MVNO wholesale contracts to confirm if the session falls under a predefined Onnet arrangement.
Example: A call from a T-Mobile MVNO to a T-Mobile subscriber is Onnet, but a call to Sprint may be Offnet unless peering exists.
5. Analyze Traffic Metadata in Network Probes
Use NetFlow, sFlow, or IPFIX data to trace the path taken by the session. Onnet traffic typically shows:
Direct hops between carrier
Billing and Cost Structures Associated with Net Onnet Traffic
The financial framework governing Net Onnet traffic reflects a complex interplay of pricing models, regulatory influences, and operational efficiencies. Unlike Net Offnet traffic, which typically incurs higher transit costs, Net Onnet traffic leverages direct peering agreements, internal cost-sharing mechanisms, and volume-based discounts to optimize revenue and reduce expenses. This section examines the billing structures, cost allocation methods, and financial incentives that shape carrier decisions in classifying and monetizing Net Onnet traffic.
Carriers employ distinct billing models for Net Onnet and Net Offnet traffic, with the former often benefiting from lower per-bit costs due to direct interconnection. However, discrepancies in classification, regulatory ambiguities, and disputes over cost-sharing have led to industry-wide challenges. Below is a comparative analysis of billing models, followed by operational insights into revenue calculation, routing optimization, and dispute resolution frameworks.
Comparison of Billing Models: Net Onnet vs. Net Offnet Traffic
The following table contrasts key billing components for Net Onnet and Net Offnet traffic, highlighting differences in pricing tiers, cost structures, and regulatory impacts.
Parameter
Net Onnet Traffic
Net Offnet Traffic
Pricing Tiers
Flat-rate or tiered pricing based on peering agreements (e.g., paid peering, settlement-free peering).
Costs often aligned with internal cost allocation (e.g., shared infrastructure, cross-subsidization).
May include reciprocal billing where both parties settle at a negotiated rate (e.g., 1:1, 2:1).
Transit-based pricing (e.g., per-Mbps, port-speed pricing, or 95th-percentile billing).
Higher costs due to third-party transit providers (e.g., Tier 1 ISPs charging $X per Gbps).
No reciprocal arrangements; costs borne entirely by the originating carrier.
Volume-Based Discounts
Discounts applied for high-volume peering (e.g., bulk peering deals with content providers).
Internal cost-sharing pools may reduce per-bit charges for large customers.
Examples: AIX (Advanced Internet eXchange) or regional peering forums offering tiered discounts.
Discounts limited to transit provider agreements (e.g., long-term contracts with reduced rates).
No direct volume benefits unless negotiated separately with transit carriers.
Example: A carrier paying $500/Mbps for transit may negotiate $400/Mbps after 12 months.
Peering vs. Transit Costs
Peering costs are often minimal or nonexistent (settlement-free) for high-traffic peers.
Internal routing optimization reduces reliance on expensive transit links.
Example: Netflix peering with Comcast at no cost due to mutual benefit.
Transit costs dominate, with providers like Cogent or Level 3 charging premium rates.
No cost-sharing; full payment to transit providers regardless of traffic origin.
Example: A regional ISP paying $0.01/Mb for transit to reach global audiences.
Regulatory Influences
Regulations may mandate fair cost allocation (e.g., EU’s Net Neutrality rules).
Local peering policies (e.g., India’s TRAI guidelines) may cap settlement rates.
Tax implications vary by region (e.g., VAT on peering fees in the EU).
Transit pricing regulated in some markets (e.g., FCC’s Title II rules in the U.S.).
Anti-discrimination laws may limit transit provider pricing power.
Google’s Peering Agreements: Settlement-free peering with major ISPs (e.g., AT&T, Verizon) reduces costs for mutual traffic.
Deutsche Telekom’s AIX Peering: Tiered discounts for high-volume European traffic.
Jio Platforms (India): Internal cost-sharing for domestic Net Onnet traffic, avoiding transit fees.
Cogent Communications: Offers low-cost transit but charges premium rates for Net Offnet routes.
Level 3 (Now Zayo): Global transit pricing with no Net Onnet discounts.
AfriNIC Peering Disputes: Regional ISPs pay high transit costs due to limited peering options.
Key Insight:
Net Onnet traffic reduces operational costs by 30–70% compared to Net Offnet, depending on peering efficiency and volume. Transit-dependent carriers often incur hidden costs from third-party providers, while peering-heavy models benefit from direct interconnection economies.
Revenue Calculation and Internal Cost Allocation for Net Onnet Traffic
Carriers generate revenue from Net Onnet traffic through a combination of peering settlements, internal cost recovery, and customer billing. The process involves classifying traffic, allocating infrastructure costs, and applying pricing models that align with peering agreements.
Steps in Revenue Calculation:
1. Traffic Classification:
Traffic is labeled as Net Onnet if it originates and terminates within the carrier’s peering ecosystem (e.g., IXPs, private peering, or internal networks). Misclassification (e.g., routing Net Onnet traffic over transit) triggers cost adjustments.
2. Cost Allocation Methods:
Carriers distribute infrastructure costs (e.g., backbone capacity, IXP port fees) across traffic types using:
Proportional Sharing: Costs split based on traffic volume (e.g., 60% Net Onnet, 40% Net Offnet).
Activity-Based Costing: Assigns costs to specific peering links (e.g., a dedicated 10Gbps link to Google).
Cross-Subsidization: High-margin Net Offnet traffic subsidizes lower-cost Net Onnet routes.
3. Peering Settlement Models:
Settlement-Free Peering: No direct costs (e.g., Netflix ↔ Comcast).
Paid Peering: One party pays for capacity (e.g., a small ISP paying a CDN for direct access).
Reciprocal Billing: Traffic exchanged at a negotiated ratio (e.g., 1:1, 2:1).
4. Customer Billing:
Wholesale Customers: Charged based on Net Onnet/Offnet ratios (e.g., a mobile operator paying less for domestic traffic).
Retail Customers: Often bundled under flat-rate plans, with Net Onnet traffic absorbing lower infrastructure costs.
Example Calculation:
A carrier with $1M in monthly infrastructure costs allocates:
70% to Net Onnet traffic (peering-heavy, low-cost).
30% to Net Offnet traffic (transit-dependent, high-cost).
If a customer generates 50% Net Onnet traffic, they are billed proportionally, reducing their effective cost by 35% compared to full transit pricing.
Decision-Making Flowchart for Classifying Net Onnet Traffic
The following text-based flowchart outlines how carriers determine whether traffic qualifies
Architectural Design for Net Onnet Optimization in Carrier-Grade Networks
Net Onnet optimization in carrier-grade networks requires a meticulously designed architecture that balances traffic efficiency, scalability, and cost-effectiveness. The goal is to minimize transit costs while ensuring low latency, high availability, and seamless peering for on-net traffic. This design leverages core-edge separation, strategic peering, Anycast for redundancy, and direct interconnects to create a resilient and performant network. Below is a high-level architectural framework, followed by implementation details for routing protocols, hardware/software comparisons, and lab simulation methodologies.
High-Level Network Architecture for Net Onnet Efficiency
The proposed architecture prioritizes direct traffic exchange between on-net peers while minimizing reliance on third-party transit. Key components include:
#### 1. Core vs. Edge Routing Segmentation
Core Network: Handles high-speed, low-latency traffic between major peering points and data centers. Uses MPLS/IP or Segment Routing for deterministic forwarding and traffic engineering.
Edge Network: Manages traffic entry/exit, including peering points, customer-facing routers, and direct interconnects. Implements BGP-based routing with fine-grained policy controls.
Key Design Principle:
On-net traffic should bypass transit networks entirely, entering the core only at designated peering hubs or direct interconnects.
2. Peering Points and Interconnect Strategies
Public Internet Exchange Points (IXPs): Deploy Anycast BGP to distribute traffic across multiple IXP locations (e.g., DE-CIX, AMS-IX, LINX). Reduces latency and improves redundancy.
Private Peering: Establish direct fiber or Ethernet interconnects with major on-net partners (e.g., via AARNet, CERN, or regional carrier alliances).
Hierarchical Peering: Use a two-tier peering model:
Tier 1: Direct peering with top-tier networks (e.g., Level 3, GTT, Cogent).
Tier 2: Regional peering via IXPs or private links for smaller on-net partners.
#### 3. Anycast and Load Balancing for Resilience
Anycast Deployment: Assign the same IP prefix to multiple edge routers (e.g., at IXPs or POPs). Traffic is routed to the nearest instance, reducing latency and congestion.
Global Load Balancing: Use BGP Anycast combined with ECMP (Equal-Cost Multi-Path) to distribute traffic across paths dynamically.
Example Configuration:
router bgp 65001
neighbor 192.0.2.1 remote-as 65002
neighbor 192.0.2.1 next-hop-self
neighbor 192.0.2.1 route-map ANYCAST_OUT out
!
route-map ANYCAST_OUT permit 10
match ip address prefix-list ANYCAST_PREFIX
set as-path prepend 65001 65001 65001 # Influence path selection
#### 4. Direct Interconnects for On-Net Traffic
Dedicated Links: Deploy dark fiber, DWDM, or Ethernet VPN (EVPN) between on-net partners to bypass transit entirely.
Software-Defined Interconnects (SDI): Use SD-WAN controllers (e.g., Cisco Viptela, VMware VeloCloud) to dynamically route on-net traffic over optimized paths.
Validation Check:
Ensure BGP communities (e.g., `65001:100` for "on-net preferred") are used to mark routes for direct interconnects, overriding transit paths.
Implementing Net Onnet Prioritization in BGP
BGP is the backbone of Net Onnet routing. Below are configuration steps to enforce on-net traffic prioritization using policy-based routing, community attributes, and AS path manipulation.
#### 1. Policy-Based Routing (PBR) for On-Net Traffic
PBR redirects traffic based on source/destination IP prefixes, ensuring on-net flows take direct paths.
Steps:
1. Define prefix lists for on-net ASes and IP ranges:
ip prefix-list ONNET_SETS seq 5 permit 192.0.2.0/24
ip prefix-list ONNET_SETS seq 10 permit 203.0.113.0/24
2. Create a route map to match on-net prefixes:
route-map ONNET_POLICY permit 10
match ip address prefix-list ONNET_SETS
set interface GigabitEthernet0/1 # Direct interconnect port
3. Apply PBR to the ingress interface:
interface GigabitEthernet0/0
ip policy route-map ONNET_POLICY
#### 2. BGP Community Attributes for Traffic Engineering
Communities tag routes to influence path selection. Example:
On-Net Community: `65001:100` (preferred path).
Transit Community: `65001:200` (fallback path).
Configuration:
router bgp 65001
neighbor 192.0.2.1 send-community both
neighbor 192.0.2.2 route-map SET_ONNET_COMMUNITY out
!
route-map SET_ONNET_COMMUNITY permit 10
match as-path 65001 # On-net AS
set community 65001:100
#### 3. AS Path Manipulation for Path Selection
Modify AS paths to influence route selection. Common techniques:
Prepend AS Path: Discourage transit by adding extra AS hops.
route-map PREFEND_ONNET permit 10
match as-path 65001
set as-path prepend 65001 65001
- AS Path Filtering: Block transit paths for on-net prefixes.
neighbor 193.0.3.1 route-map DENY_TRANSIT in
!
route-map DENY_TRANSIT deny 10
match as-path _65001_.* # Block routes from AS 65001 via transit
#### 4. Validation Checks for Net Onnet Routing
Route Leak Prevention: Verify no on-net prefixes are leaked to transit providers.
show ip bgp neighbors 193.0.3.1 advertised-routes | include 192.0.2.0
- Symmetry Check: Ensure return traffic follows the same path as ingress.
traceroute 192.0.2.100
- Community-Based Routing: Confirm communities are applied correctly.
show ip bgp community 65001:100
Hardware and Software Solutions for Net Onnet Optimization
Below is a comparative table of vendors/tools optimized for handling Net Onnet traffic, focusing on scalability, low latency, and BGP policy enforcement.
Vendor/Tool
Key Features
Performance Metrics
Deployment Complexity
Cisco ASR 9000 Series
High-performance BGP with 1M+ routes support.
Integrated Segment Routing for traffic engineering.
Hardware-accelerated Anycast BGP and ECMP.
Support for VXLAN-EVPN for SDI.
Throughput: 1.2 Tbps (ASR 9904).
BGP Convergence: <100ms (with NSR/NSF).
Latency: <500ns for L2/L3 forwarding.
High (requires expert configuration for advanced features).
Juniper MX Series
JunOS with native Anycast RHINO support.
BGP FlowSpec for DDoS mitigation on on-net paths
Regulatory and Policy Implications of "Net Onnet" Traffic
Regulatory frameworks governing "Net Onnet" traffic shape how carriers classify, prioritize, and bill for interconnection, directly influencing market competition, consumer rights, and network neutrality. These policies vary by region, with some jurisdictions enforcing strict transparency requirements while others rely on voluntary agreements between carriers. Misalignment in classification can lead to legal disputes, financial penalties, and reputational damage, particularly in markets where net neutrality principles are legally entrenched. The interplay between technical definitions of "Net Onnet" and regulatory expectations creates a complex landscape that demands rigorous compliance strategies.
The classification of traffic as "Net Onnet" intersects with broader debates on net neutrality, where proponents argue that such distinctions enable efficient routing and cost optimization, while critics contend they facilitate discriminatory practices under the guise of technical necessity. Legal risks arise when carriers exploit ambiguous definitions to manipulate billing or traffic management, potentially violating consumer protection laws or antitrust regulations.
Global Regulatory Frameworks Governing "Net Onnet" Traffic
Regulatory approaches to "Net Onnet" traffic differ significantly across regions, reflecting divergent priorities in competition policy, consumer protection, and infrastructure investment. Below is a comparative table summarizing key policies, their impact on carriers, enforcement mechanisms, and notable precedents.
Regulatory Context: Policies often emerge from telecommunications acts, competition laws, or net neutrality directives, with enforcement varying from administrative fines to legal injunctions. For example, the EU’s Electronic Communications Code (2018) mandates transparency in interconnection agreements, while the U.S. FCC’s 2015 Open Internet Order (later partially overturned) required disclosure of traffic management practices. Emerging markets may lack formal regulations, relying instead on industry self-governance or bilateral carrier agreements.
Region/Country
Key Regulations
Impact on Carriers
Enforcement Mechanisms
Notable Cases
European Union
Electronic Communications Code (2018)
Net Neutrality Regulation (2015/2120)
Article 10 of the Universal Service Directive (transparency in interconnection)
Mandates non-discriminatory treatment of traffic, including "Net Onnet" classifications.
Requires public disclosure of interconnection agreements and peering policies.
Prohibits zero-rating practices that could distort "Net Onnet" billing.
Fines up to 4% of annual revenue (e.g., €2.4M for Vodafone Italy in 2021 for non-compliance with traffic management rules).
BEREC (Body of European Regulators for Electronic Communications) oversight.
Deutsche Telekom vs. BNetzA (2019): German regulator ruled that DT’s "Net Onnet" prioritization for its own services violated net neutrality, ordering transparency in traffic management policies.
BEREC’s 2020 Guidance on Zero-Rating: Clarified that exempting "Net Onnet" traffic from data caps must not disadvantage competitors.
United States
Federal Communications Commission (FCC) Title II Classification (2015–2017)
Section 706 of the Telecommunications Act (promoting broadband deployment)
State-level net neutrality laws (e.g., California’s SB 822, 2018)
Post-2017 repeal of Title II, carriers face fewer federal restrictions but increased scrutiny under state laws.
"Net Onnet" traffic may be billed differently under "reasonable network management" exemptions.
Competition concerns arise if dominant carriers use "Net Onnet" to favor affiliated services (e.g., AT&T’s sponsorship of HBO Max).
FCC enforcement via complaint investigations (e.g., 2021 probe into Comcast’s "Data Caps").
State AG lawsuits (e.g., New York vs. Verizon for throttling "off-net" traffic).
FCC vs. Mozilla (2014): Mozilla challenged AT&T’s "Net Onnet" throttling of Skype, leading to a settlement requiring transparency in traffic management.
California’s 2020 Lawsuit Against Comcast: Alleged that Comcast’s "Net Onnet" prioritization for Xfinity Stream violated SB 822.
India
Telecom Regulatory Authority of India (TRAI) Regulations (2018 on Net Neutrality)
Section 66K of IT Act (prohibiting discriminatory traffic treatment)
TRAI’s 2018 ban on zero-rating and discriminatory "Net Onnet" pricing.
Carriers must disclose peering agreements, but enforcement is limited.
Dominant players (e.g., Reliance Jio) may use "Net Onnet" to subsidize bundled services.
TRAI can impose penalties up to ₹50 crore (~$6M) for violations.
Consumer complaints trigger investigations (e.g., 2021 probe into Airtel’s "Net Onnet" data usage claims).
TRAI vs. Airtel (2020): Ordered Airtel to refund customers after misrepresenting "Net Onnet" data savings in promotional offers.
China
Cyberspace Administration of China (CAC) Regulations (2019 on Data Localization)
Ministry of Industry and Information Technology (MIIT) peering policies
"Net Onnet" traffic is tightly controlled to prioritize domestic services (e.g., Baidu, Alibaba).
Foreign carriers must negotiate state-approved peering terms, often with mandatory traffic routing rules.
No public net neutrality laws, but CAC monitors "harmful" content, including "Net Onnet" traffic.
CAC can block services or impose fines for non-compliance (e.g., $4.8M fine for Tencent in 2021).
MIIT conducts audits of interconnection agreements.
China Mobile vs. Google (2017): Google accused China Mobile of throttling "off-net" YouTube traffic; resolved via private agreement.
Brazil
Anatel’s General Rule on Internet Access (2014)
Civil Rights Framework for the Internet (2014, "Marco Civil")
Strict net neutrality provisions prohibit "Net Onnet" discrimination.
Carriers must publish peering policies and justify traffic prioritization.
Zero-rating is banned unless it
Net Onnet is more than a technical classification—it is the linchpin of cost-effective, high-performance networking in carrier environments. From the granularity of BGP policy rules to the high-stakes realm of regulatory compliance, its mastery empowers organizations to reduce latency, enhance throughput, and secure competitive billing advantages. The interplay between architectural design, financial incentives, and policy adherence underscores its pivotal role in shaping the future of telecom infrastructure. As networks evolve, the ability to harness Net Onnet traffic will remain a defining factor in operational excellence and strategic innovation for carriers worldwide.
Leave a Comment
Comments are moderated before appearing. The data you submit is processed according to the Privacy Policy of Ns2.