IETF Logo Mail Archive

[v6ops] Who implements the DHCP service?

Fred Baker <fredbaker.ietf@gmail.com> Mon, 20 November 2017 01:27 UTC

Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8490E1201F8 for <v6ops@ietfa.amsl.com>; Sun, 19 Nov 2017 17:27:55 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 JXuYQJdZS2Gr for <v6ops@ietfa.amsl.com>; Sun, 19 Nov 2017 17:27:53 -0800 (PST)
Received: from mail-ot0-x22a.google.com (mail-ot0-x22a.google.com [IPv6:2607:f8b0:4003:c0f::22a]) (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 E12571241FC for <v6ops@ietf.org>; Sun, 19 Nov 2017 17:27:52 -0800 (PST)
Received: by mail-ot0-x22a.google.com with SMTP id s4so6404182ote.4 for <v6ops@ietf.org>; Sun, 19 Nov 2017 17:27:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=NxSeyke2d740RcpMhQkywuCt2mRaMx0uEEkmKYwUzqQ=; b=rqZ/ClSBOSTRULJxVgw74u7TGD5cgr6Nu8JCmWHcwrMfrSqY9B8tVh7ph8Z++Oroid tHc8oKY/oD3KFmvbY0PIrhHfoaQIunrWSTP57oATemtRRR27TG50VskEbDX3zYCezrb1 fHzPLHs525KsCrXel9vAaPgfBWrNv578JK982iHgICLm/VaEtgW/4kb1E5sn0yc3WZTb kTc9WWgoreYeH+pN/IKSk6qYJGZHVBOSEW8zXIEiagTz3v4OGLFWlINjlrWDe7tmp9mN gk9nmlCiIeMkstGSA8TMFeLxJu5/GxHlL6Aq8EMz2O+Zkg4wB1+l4It+uSlrOkn5heEu xG3w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=NxSeyke2d740RcpMhQkywuCt2mRaMx0uEEkmKYwUzqQ=; b=IBTCEvCJ09maI5ozgaIdadhmDE1ppxp6SeBw04Z2VJyiQy03jSRfHi/AS7ErvqIP3T ibvL8xYT+QFUwJ7+zZ1oRgjd8EiMfUEVUWPcvzxxyjRQM3+j/OJTMlYClCarg4mdwekP egjaIAgG1rVvnqRNrG8ekRCwUHId8aFW8GYqKcYss6Fo6YZo9E03aXTsQVWcU3pGZEg0 odmHhHNlYmLsPTfD88n1O+34TT550Q2yfBCuEQtAhKHaGppeHVxzwQWIwjVaEUyDFJ/3 v89uE3mhS5665IfFUXlcF21wKFIp7IZJXordg0Aqh4UtAGL76P5T0I14V2/dFLHWyt5r 0R1w==
X-Gm-Message-State: AJaThX7jUUv4hL13/UXOfwFPqFwHYJPWBT6z3rg2ClQjdls3uhg8t3KD sX+UqvcPV1+HLJbqHWFiUI8=
X-Google-Smtp-Source: AGs4zMajoghW30j/nah/qLPIJnIBlhcZ2qtJEyyHSDqGuEV+OMRr8Oz0VUssjxj4t3uh41mVfA+PJQ==
X-Received: by 10.157.21.49 with SMTP id u46mr7132429otf.361.1511141272372; Sun, 19 Nov 2017 17:27:52 -0800 (PST)
Received: from ?IPv6:2600:8802:5600:f7a::1005? ([2600:8802:5600:f7a::1005]) by smtp.gmail.com with ESMTPSA id z96sm4354075ota.30.2017.11.19.17.27.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 19 Nov 2017 17:27:51 -0800 (PST)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <9FDA6FE7-C03C-4AA9-BED4-F0D7ED63FBBF@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_5E1DBB8E-7A64-4B78-86A8-A8243B4F481B"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Sun, 19 Nov 2017 17:27:49 -0800
In-Reply-To: <655879d9e7274da88ee2cd33a0202dd7@XCH15-06-08.nw.nos.boeing.com>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
To: Fred Templin <Fred.L.Templin@boeing.com>
References: <7FC2CA6E-8BF7-47BC-9164-1877FAF83FD0@gmail.com> <AM5PR0701MB283634D35008FC7AAF934B88E02E0@AM5PR0701MB2836.eurprd07.prod.outlook.com> <fd860e6c2af84c4d9774ce67f4468720@XCH15-06-08.nw.nos.boeing.com> <43186ad6-dc2f-c9d8-2884-db4a097f142d@gmail.com> <655879d9e7274da88ee2cd33a0202dd7@XCH15-06-08.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/_W-VQH0CCjxz5PHeaZwvbGY7WSw>
Subject: [v6ops] Who implements the DHCP service?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Nov 2017 01:27:55 -0000

One comment on the draft in question.

Looking at figure 1 (applies to all of the figures, but let me be specific for the purposes of a comment) I don't see any reason to believe that the node marked "Delegating Router" is in fact a router or is connected directly to the "Upstream Interface". AFAIK, given the relay capability present in RFC 3315, the common practice is to have a more central server respond to IA_NA and IA_PD requests, and simply have a router connected on the ISP link. That might get complex to draw in a figure, but I'd worry about any implicit assumption in the WG version of the document that only routers implemented the PD service.

v2.23.0 | Report a Bug | By Email