IETF Logo Mail Archive

Re: [dhcwg] RFC3315bis - Naming

Marcin Siodelski <msiodelski@gmail.com> Mon, 03 March 2014 14:07 UTC

Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D2891A017C for <dhcwg@ietfa.amsl.com>; Mon, 3 Mar 2014 06:07:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 YTFh9Zad06UX for <dhcwg@ietfa.amsl.com>; Mon, 3 Mar 2014 06:07:27 -0800 (PST)
Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id C8FC11A0188 for <dhcwg@ietf.org>; Mon, 3 Mar 2014 06:07:25 -0800 (PST)
Received: by mail-la0-f42.google.com with SMTP id ec20so4731016lab.29 for <dhcwg@ietf.org>; Mon, 03 Mar 2014 06:07:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hTL08ojcgPojXEz2FMkaJ4YKs1ff4syS/hA09ZAlSAc=; b=qJFvrxR06D0/jTil1bDBvWFZk5wQ0IKDqBe2qYEZQsLC+qIlKqYOXGuMOilyIpPWeM 4/RdfmGU8lCOiQ0hZ6VfhB9ul5oc+7r83vX/QdT9kcTOMD/YPeh7yoh+7iRHnMmukNFZ Fa8pZnf7yDp8eIuX8Q26/kQWUmcIlj21pYIFCrYvrF0PuOR2Z6iNb5bD5kF+p3yUFLYc 0xMYhO/YKGS5CUZZg5FnjO6Glw4OHku8aNuU+RHKrW4AeLr6T8oA+ndNSCdoNbVWV5tg QJ8yV56rGZPfiTYcSjk4FoI95YNUKwwLNkMiwmSMtk+7o93rT8mQ6ofczUF9rX2HL7cI eIZQ==
MIME-Version: 1.0
X-Received: by 10.152.116.43 with SMTP id jt11mr3556159lab.41.1393855641848; Mon, 03 Mar 2014 06:07:21 -0800 (PST)
Received: by 10.112.16.198 with HTTP; Mon, 3 Mar 2014 06:07:21 -0800 (PST)
In-Reply-To: <53148AAB.8000601@gmail.com>
References: <AF7019CB-8EEB-4E43-A5B0-4863D763B0E2@employees.org> <53148AAB.8000601@gmail.com>
Date: Mon, 03 Mar 2014 14:07:21 +0000
Message-ID: <CAFGoqUPCCBGu2e5Nw5vDS_3c_a30p=p2qc8xcM-+yWuEFtmGwA@mail.gmail.com>
From: Marcin Siodelski <msiodelski@gmail.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/U9vQMILKCbNiDLGLwsH5TztfzlQ
Cc: DHC WG <dhcwg@ietf.org>, "Ralph Droms (rdroms)" <rdroms@cisco.com>
Subject: Re: [dhcwg] RFC3315bis - Naming
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 03 Mar 2014 14:07:29 -0000

On Mon, Mar 3, 2014 at 1:59 PM, Tomek Mrugalski
<tomasz.mrugalski@gmail.com> wrote:
> On 03.03.2014, 09:28, Ole Troan wrote:
>> I don't see a new to maintain the separate terms. just use client,
>> relay and server.
> Hear hear. Unless folks who favor delegating/requesting router
> nomenclature appear in huge numbers soon, we'll go with the client,
> relay and server.
>

Current terminology for DHCP client and server in RFC3315 is:

DHCP client (or client):  A node that initiates requests on a link  to
obtain configuration parameters from one or more DHCP servers.
DHCP server (or server):  A node that responds to requests from
clients, and may or may not be on the same link as the client(s).

If we just stick to this terminology, there is nothing in it that
precludes it's use for PDs, as the node is a general term. So, I agree
that we should use client, server and relay for prefix delegation,
which would make editorial work way easier.

Marcin

v2.23.0 | Report a Bug | By Email