[dhcwg] Regarding dhcpv4 client id

Venkataratnam Naidu <ratnameee@gmail.com> Mon, 05 October 2020 05:54 UTC

Return-Path: <ratnameee@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6A383A0D93 for <dhcwg@ietfa.amsl.com>; Sun, 4 Oct 2020 22:54:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dcmQkvfQGE8E for <dhcwg@ietfa.amsl.com>; Sun, 4 Oct 2020 22:54:06 -0700 (PDT)
Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 383B93A0D89 for <dhcwg@ietf.org>; Sun, 4 Oct 2020 22:54:06 -0700 (PDT)
Received: by mail-wm1-x336.google.com with SMTP id v12so7447173wmh.3 for <dhcwg@ietf.org>; Sun, 04 Oct 2020 22:54:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=msnLDzKwv1onpb3ZjgAlW5L3nhlPcXi9Gxa74H+IjPs=; b=N26mAckItw+oZysIVG309ykiikP4MUHRQO62jB4derWL8BciCYNzTEwDFPhYqtix1U lAdpaZYDXa+TgPqX661TWj5elY8rk9cv3gdOawR7uugAliXNH8XQJh3Aemm+5EeGhaAj 2NgVQ7EgJMwlu1m7bDKuvP5w4lQfbZ7ahV2RVI7B40DiC+SLNgX1Gj4vNAK9Fjfx1a+y erG0TDm3wtoEeIktP4TDUnTv1/I5YUWqPOYQXz7pAy4r6RzUGn3JWnpEWItVIw2hcn4N HnEqkz9wsr579YUyH57dwjxn33+EfVpMGUYLSJN3mNzA6NX+y+rJ9E4k/1oOBcq6swWs +r/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=msnLDzKwv1onpb3ZjgAlW5L3nhlPcXi9Gxa74H+IjPs=; b=ndqaIhePBE266VNINa7FGH/I9H0AISNotjngOMAo+PQ8hMMnzL29RfchdaFTEqosVC vteDUF+2OQZNCpeBsjtKHK422RLsynudHA3n09c3HMbSodk8xKgge44nffX6sXcbeSS5 snsJmIeRZEvsYois/uskfSNnoIt2u00V+VHIrEINbbNZSvrJAfDpYiMnF9c2RFLn1hsb qp6XL2TbNSN0GFxGjKuHzK3DveSs8lSGbxo6ZVNYlueLB5vtjVFn9g2L24cudVbG8p4P iNnTfWz9PpdLq8iRbyI3FSUJTil41Dg9nCRukVXwBD7RcAhIQyziX245rWD82uTsfn6L KQmg==
X-Gm-Message-State: AOAM532MoSEE1yVQLR7cAsIFq3gmIKnG3/5kKb1OJaE0W4QszdDzWoyP oeNs+Vafx9MfJ4eKmKcikCcHFTrSxELfsBFVSgR5UhBidQ==
X-Google-Smtp-Source: ABdhPJyk0ZTMCCkdtBXlUhKT/xrTBWaf+5yCRNJkqazV9TgTMwRCBqVUbuBTJ38O68ShPKDypr2kU+po/6Cx5COfeo8=
X-Received: by 2002:a1c:2dc6:: with SMTP id t189mr15425917wmt.92.1601877244359; Sun, 04 Oct 2020 22:54:04 -0700 (PDT)
MIME-Version: 1.0
From: Venkataratnam Naidu <ratnameee@gmail.com>
Date: Mon, 5 Oct 2020 11:23:53 +0530
Message-ID: <CANgMM_CQvWO4iARKt7apNQHFSzLmhCEcONVpueydfWEei1Gi2w@mail.gmail.com>
To: dhcwg@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001fb97805b0e61c14"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/638G45pLLPtbUNTlwY512FcoRBQ>
Subject: [dhcwg] Regarding dhcpv4 client id
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Oct 2020 05:54:08 -0000

Hi Experts,

I have a question on dhcpv4 client id that client sends in dhcp
discover/request msg.

when the client id is other than hardware address, is that mandatory to
encode "type 0" in client-identifier.
if client doesn't encode type 0, does this work in all dhcp server
implementations.


>From RFC:
   The client identifier MAY consist of type-value pairs similar to the
   'htype'/'chaddr' fields defined in [3]. For instance, it MAY consist
   of a hardware type and hardware address. In this case the type field
   SHOULD be one of the ARP hardware types defined in STD2 [22].  A
   hardware type of 0 (zero) should be used when the value field
   contains an identifier other than a hardware address (e.g. a fully
   qualified domain name).

Regards,
Venkat.