Re: IPv4 traffic on "ietf-v6ONLY"

"Rajiv Asati (rajiva)" <rajiva@cisco.com> Thu, 16 November 2017 10:32 UTC

Return-Path: <rajiva@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92ED6127909 for <ipv6@ietfa.amsl.com>; Thu, 16 Nov 2017 02:32:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 fBFIFCJuJaYj for <ipv6@ietfa.amsl.com>; Thu, 16 Nov 2017 02:32:38 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 740551200CF for <ipv6@ietf.org>; Thu, 16 Nov 2017 02:32:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2098; q=dns/txt; s=iport; t=1510828358; x=1512037958; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=HltDUmPQwRjVMWjkjC2bovg13MurvwOpfWmA4SQlJqs=; b=h9fWOfLKoeg1XyGooDPC53wK+1tQNjuRkv5aMLtwOi/+Aa7P9O3DMTQw jlTwFrvIs0ZCJKjj/NQIRwS/gXQ0iHuxk/P5zvBXUTpBazggF/Xr980h9 SZXt9oEcEKLmkm2JfUYnU2dndf08HP90iDGxTz8t6sF+9x0jE2h5jF9TF I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DvAAACaQ1a/5ldJa1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYM2ZG4nB4N4ih+PIIF9ll+CEQoYC4UYAhqEez8YAQEBAQEBAQE?= =?us-ascii?q?BayiFHgEBAQEDAQEhEToXBAIBCA4DAwECAwImAgICJQsVCAgCBAESiiQQqWaCJ?= =?us-ascii?q?4sTAQEBAQEBAQEBAQEBAQEBAQEBAQEBGAWBD4IlggeBVYISgwKEZDSDFTGCMgW?= =?us-ascii?q?KNJgHApUIk0iWAwIRGQGBOAEfOIF0ehVJLQGCNoRfd4ocgREBAQE?=
X-IronPort-AV: E=Sophos;i="5.44,402,1505779200"; d="scan'208";a="32223848"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Nov 2017 10:32:21 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id vAGAWLUc012278 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 16 Nov 2017 10:32:21 GMT
Received: from xch-aln-005.cisco.com (173.36.7.15) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 16 Nov 2017 04:32:20 -0600
Received: from xch-aln-005.cisco.com ([173.36.7.15]) by XCH-ALN-005.cisco.com ([173.36.7.15]) with mapi id 15.00.1320.000; Thu, 16 Nov 2017 04:32:20 -0600
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: Philip Homburg <pch-ipv6-ietf-4@u-1.phicoh.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: IPv4 traffic on "ietf-v6ONLY"
Thread-Topic: IPv4 traffic on "ietf-v6ONLY"
Thread-Index: AQHTXg7aCDuXpAYsgk2hw+GoRJ/sAKMXNNOA
Date: Thu, 16 Nov 2017 10:32:20 +0000
Message-ID: <A6BA33CC-32F7-4EA0-A288-2C3B549BC9F0@cisco.com>
References: <f9805855-68cf-a3e8-a13f-c6ac31b09058@gmail.com> <bbd4e1d2-047f-6758-76f8-fd591c51dad7@gmail.com> <D631CE54.8C0F5%lee@asgard.org> <m1eEvEP-0000G3C@stereo.hq.phicoh.net> <0b565be0-e228-0879-ead5-3ba03e6d1c28@gmail.com> <m1eEwyn-0000GWC@stereo.hq.phicoh.net>
In-Reply-To: <m1eEwyn-0000GWC@stereo.hq.phicoh.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.27.0.171010
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.237.217]
Content-Type: text/plain; charset="utf-8"
Content-ID: <10A1F10E331A6E479E8985EE77844C34@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ijYbbbhefj2yIJmoUKOO2ujItPc>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Nov 2017 10:32:41 -0000

While I do agree to RA being better than DHCP(v6) for the purpose discussed here, I also agree with Philip wrt L-flag usage. PvD L-flag = 0 would not prohibit a host from using IPv4 on the access.

We might be better off defining a new flag that explicitly indicates for host to ‘Suppress IPv4’. 

-- 
Cheers,
Rajiv  

-----Original Message-----
From: ipv6 <ipv6-bounces@ietf.org> on behalf of Philip Homburg <pch-ipv6-ietf-4@u-1.phicoh.com>
Date: Wednesday, November 15, 2017 at 7:40 AM
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: IPv4 traffic on "ietf-v6ONLY" 

    >There's an L flag in draft-ietf-intarea-provisioning-domains
    >that says "DHCP(v4) on this network". So L=0 says "No DHCP(v4) on
    >this network".
    
    Maybe I'm reading the draft too strictly, but it seems that the L flag is used
    to tell which provisioning domain DHCPv4 information belongs to. Not to tell
    a host to avoid using DHCPv4 in the first place.
    
    If it does have the intention to make hosts avoid DHCPv4 requests then it
    has the same drawback as in sending a 'no IPv4' option in RA or DHCPv6:
    in an IPv4-only network that can be used to prevent hosts from connecting to
    the network.
    
    --------------------------------------------------------------------
    IETF IPv6 working group mailing list
    ipv6@ietf.org
    Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
    --------------------------------------------------------------------