Jabber-NET 2010

This project is based on ffailla-jabber-net VS2010 fork of the original jabber-net library

.NET Framework

• Namespace naming follows C# coding guidelines
• .NET Framework 2.0 is still the base support except for Tests project which requires .NET Framework 4

Visual Studio 2010

• Projects were reorganized to follow Visual Studio 2010 Solution guidelines
• Each components and forms classes of JabberNet, Muzzle and SampleWinFormClient projects were added a .Designer.cs file where every stuff belonging to VS Designer has been moved
• Component designer icons were refreshed and added where missing
• Tests project uses Visual Studio Testing Framework instead of NUnit Framework
• NuGet 2.0 package manager is used to manage zlib and Rhino.Mocks libraries

XMPP Additions

• XEP-0083: Nested Roster Groups
• XEP-0199: XMPP Ping
• XEP-0166: Jingle coupled to a Jingle Manager for session management only
• XEP-0176: Jingle ICE-UDP Transport Method

STUN and extensions whose messages, attributes and errors are understood

• RFC 3489: STUN Classic deprecated in favor of RFC 5389 code elements of this RFC are annotated as deprecated.

RFC 3489bis-02: Some implementations like Vovida or MS-TURN uses value of 0x8020 for XOR-MAPPED-ADDRESS described in this draft only

• RFC 5389: Session Traversal Utilities for NAT (STUN) coupled to a minimal client that can request a STUN server for its reflexive address. IPv6 is not handled.
• RFC 5766: Traversal Using Relays around NAT (TURN)
• RFC 6062: Traversal Using Relays around NAT (TURN) Extensions for TCP Allocations
• RFC 6156: Traversal Using Relays around NAT (TURN) Extension for IPv6
• RFC 5245: Interactive Connectivity Establishment (ICE)

If you need a STUN/TURN server, I currently use turnserver to develop STUN/TURN features of this library

• it's lightweight
• can run as deamon with privileges drop
• support all the RFCs above except RFC3489 (Stun Classic) and RFC5245 (ICE). Do not have tested everything yet

ATTENTION Support dropped

• Visual Studio below 2010 and Mono support is dropped because I do not have time and resources to support them
• Specific Mono compiler directives remains in place for people needing it
• Project using the original ones won't be compatible with this project mainly because of the namespace refactoring