Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 3812] New: Support for DHCID RR (RFC 4701)

Date: Wed, 5 Aug 2009 09:52:47 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3812

           Summary: Support for DHCID RR (RFC 4701)
           Product: Wireshark
           Version: 1.2.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: ivan_jr@xxxxxxxxx


Created an attachment (id=3462)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=3462)
Support for DHCID RR packet-dns.c

Build Information:
Version 1.3.0-mydev

Copyright 1998-2009 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
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 with GTK+ 2.16.2, with GLib 2.20.3, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.8,
with c-ares 1.6.0, with Lua 5.1, without Python, with GnuTLS 2.8.1, with Gcrypt
1.4.4, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built Aug  5
2009), with AirPcap.

Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1
beta5
(packet.dll version 4.1.0.1452), based on libpcap version 1.0.0, GnuTLS 2.8.1,
Gcrypt 1.4.4, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 30729

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

Check the man page and http://www.wireshark.org for more information.
--
Support for DHCID RR (RFC 4701)

Notes:
- see attached patch. created from tortoisesvn create patch
- only shows rdata section (see section 3.2), only the dhcp clients and servers
will use this.
- see attached packet capture
- tests ok
====================
                A DNS Resource Record (RR) for Encoding
   Dynamic Host Configuration Protocol (DHCP) Information (DHCID RR)

3.  The DHCID RR

   The DHCID RR is defined with mnemonic DHCID and type code 49.  The
   DHCID RR is only defined in the IN class.  DHCID RRs cause no
   additional section processing.

3.1.  DHCID RDATA Format

   The RDATA section of a DHCID RR in transmission contains RDLENGTH
   octets of binary data.  The format of this data and its
   interpretation by DHCP servers and clients are described below.

   DNS software should consider the RDATA section to be opaque.  DHCP
   clients or servers use the DHCID RR to associate a DHCP client's
   identity with a DNS name, so that multiple DHCP clients and servers
   may deterministically perform dynamic DNS updates to the same zone.
   From the updater's perspective, the DHCID resource record RDATA
   consists of a 2-octet identifier type, in network byte order,

   followed by a 1-octet digest type, followed by one or more octets
   representing the actual identifier:

           < 2 octets >    Identifier type code
           < 1 octet >     Digest type code
           < n octets >    Digest (length depends on digest type)

3.2.  DHCID Presentation Format

   In DNS master files, the RDATA is represented as a single block in
   base-64 encoding identical to that used for representing binary data
   in [8], Section 3.  The data may be divided up into any number of
   white-space-separated substrings, down to single base-64 digits,
   which are concatenated to form the complete RDATA.  These substrings
   can span lines using the standard parentheses.

...

   [8]   Josefsson, S., "The Base16, Base32, and Base64 Data Encodings",
         RFC 3548, July 2003.


-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.