Wireshark-bugs: [Wireshark-bugs] [Bug 10451] New: Support for Named Data Networking (NDN)
Date: Sun, 07 Sep 2014 15:30:00 +0000
Bug ID 10451
Summary Support for Named Data Networking (NDN)
Product Wireshark
Version Git
Hardware All
OS All
Status UNCONFIRMED
Severity Enhancement
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter tyson.key@gmail.com

Build Information:
Version 1.99.0-1515-g7d81eab (v1.99.0-rc1-1515-g7d81eab from master)

Copyright 1998-2014 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (32-bit) with GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
WinPcap (4_1_3), with libz 1.2.5, with GLib 2.38.0, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, with GnuTLS 3.1.22, with Gcrypt 1.6.0, with MIT Kerberos,
with GeoIP, with PortAudio V19-devel (built Aug 24 2014), with AirPcap.

Running on 64-bit Windows 8, build 9200, with WinPcap version 4.1.3 (packet.dll
version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008),
with GnuTLS 3.1.22, with Gcrypt 1.6.0, without AirPcap.
AMD A6-5200 APU with Radeon(TM) HD Graphics     (with SSE4.2), with 3529MB of
physical memory.


Built using Microsoft Visual C++ 12.0 build 30501

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
Although I haven't got time to look into implementing this myself, right now,
it may be interesting to consider implementing support for the new Named Data
Networking protocol suite (http://named-data.net/doc/ndn-tlv/), at some stage.

Right now, it seems to operate over TCP, UDP, and at the Network Layer in place
of IP (unsure if the EtherType that they're using is registered officially with
IANA, though).

Since it seems that no-one else has spotted this new protocol, I'll try to set
things up under Ubuntu, so that I can produce some traces.


You are receiving this mail because:
  • You are watching all bug changes.