Re: [dhcwg] about v4configuration and co (1)

Ole Troan <otroan@employees.org> Tue, 06 August 2013 13:28 UTC

Return-Path: <otroan@employees.org>
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 3297921F9371 for <dhcwg@ietfa.amsl.com>; Tue, 6 Aug 2013 06:28:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.266
X-Spam-Level:
X-Spam-Status: No, score=-2.266 tagged_above=-999 required=5 tests=[AWL=-0.267, BAYES_00=-2.599, J_CHICKENPOX_16=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RhKnh7b4Ii6R for <dhcwg@ietfa.amsl.com>; Tue, 6 Aug 2013 06:28:24 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) by ietfa.amsl.com (Postfix) with ESMTP id 7FBFC21F9346 for <dhcwg@ietf.org>; Tue, 6 Aug 2013 06:28:24 -0700 (PDT)
Received: from dhcp-lys02-vla252-10-147-116-74.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id BD7915ECC; Tue, 6 Aug 2013 06:28:22 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CE26AD9D.82437%ian.farrer@telekom.de>
Date: Tue, 06 Aug 2013 15:28:20 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <04D56C82-85BC-4021-BEBE-AE24075DD3CF@employees.org>
References: <CE26AD9D.82437%ian.farrer@telekom.de>
To: ian.farrer@telekom.de
X-Mailer: Apple Mail (2.1508)
Cc: dhcwg@ietf.org, Francis.Dupont@fdupont.fr
Subject: Re: [dhcwg] about v4configuration and co (1)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 06 Aug 2013 13:28:30 -0000

Ian,

> [ian] In the introduction of the v4config draft, it says:
> "Although softwire mechanisms are currently the only use-case for DHCP
> based configuration of IPv4 parameters in IPv6 only networks, a suitable
> approach must not be limited to only supporting softwire configuration."
> 
> Putting it over the IPv4 data path is going to make this a pretty softwire
> dependant solution.

it would be dependent on a broadcast capable link-layer supporting IPv4,
that isn't softwire specific as such.

you aren't suggesting that there is a need to provision IPv4 on a node that has no way to send IPv4 packets?

cheers,
Ole