Re: [Softwires] Working group last call for draft-ietf-softwire-map-dhcp-07

Ole Troan <ot@cisco.com> Tue, 22 April 2014 13:07 UTC

Return-Path: <ot@cisco.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B18F1A0418 for <softwires@ietfa.amsl.com>; Tue, 22 Apr 2014 06:07:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.773
X-Spam-Level:
X-Spam-Status: No, score=-9.773 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 TTwrcGHBJ35N for <softwires@ietfa.amsl.com>; Tue, 22 Apr 2014 06:06:53 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8C0611A020E for <softwires@ietf.org>; Tue, 22 Apr 2014 06:06:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2572; q=dns/txt; s=iport; t=1398172001; x=1399381601; h=mime-version:subject:from:in-reply-to:date:cc:message-id: references:to; bh=ZU/F9YuN4rgbVdpkI2XQJSozjWQQo2721ZA1MkAWPKM=; b=RMJU6CnVRndRDGbWYkdUPIZXUEPrYZ9h/wDTf8W1tURVT8ea4KspuN4s rWcdeFFbtyWTcoYZDpjN7MHBA4CiG37fx8oYhEbTAq7EyRa0wk0x4SnPn 4HVulicPRWB/c7/Wn5h/wpcgaVfHFzvjAl4zKt/zEY58kdihxhId7+C4n U=;
X-Files: signature.asc : 496
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFABRoVlOQ/khR/2dsb2JhbABZgwbFPIEXFnSCJQEBAQMBHUoSBQsLRlcGLogeCMxJF41+WAeDJIEUAQOQb4gBklKDMzuBLA
X-IronPort-AV: E=Sophos; i="4.97,904,1389744000"; d="asc'?scan'208"; a="23928805"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-1.cisco.com with ESMTP; 22 Apr 2014 13:06:40 +0000
Received: from dhcp-10-61-103-98.cisco.com (dhcp-10-61-103-98.cisco.com [10.61.103.98]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s3MD6dpB001482 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 22 Apr 2014 13:06:39 GMT
Content-Type: multipart/signed; boundary="Apple-Mail=_388E2E22-6689-4338-9FEA-816C1F37EB9D"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ole Troan <ot@cisco.com>
In-Reply-To: <37A243DD-5249-4070-AB19-6DFFCFE17AA7@gmx.com>
Date: Tue, 22 Apr 2014 15:07:10 +0200
Message-Id: <FF0C2589-2538-42BD-B8E5-92547D90F4FC@cisco.com>
References: <53422B8F.2020109@ericsson.com> <37A243DD-5249-4070-AB19-6DFFCFE17AA7@gmx.com>
To: Ian Farrer <ianfarrer@gmx.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/sp7B3FGoZHSFbnioAzH_Cgr9v4U
Cc: Softwires WG <softwires@ietf.org>, Yong Cui <cuiyong@tsinghua.edu.cn>
Subject: Re: [Softwires] Working group last call for draft-ietf-softwire-map-dhcp-07
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2014 13:07:04 -0000

Ian,

> Currently, OPTION_S46_BR is limited to only be a sub-option carried within one of the S46 container options (described in section 3). However, other softwire provisioning mechanisms also need this configuration parameter, for example if you’re using DHCPv4 over DHCPv6.
> 
> To re-use this parameter for DHCPv4o6 as it stands within the container would be very messy: A client needs to indicate its support for OPTION_S46_CONT_LW and DHCPv4o6 in the ORO, it then gets the parameter from one end of the softwire from DHCPv6 and the other end of the softwire using DHCPv4o6.

is the complete flow and options of how LW46 is provisioned with DHCPv4 described anywhere? half and half with DHCPv6 options and DHCPv4 options?

> Two solutions spring to mind:
> 
> 1, Loosen the restriction in this draft so that OPTION_S46_BR can be used outside of one of the S46 Containers. This would then allow the possibility of the client including the option within an ORO option in the DHCPV4-QUERY/RESPONSE messages in the DHCPv4o6 message flow.
> 2, Keep the restriction in the map-dhcp draft and create a new option for provisioning the BR specifically for softwire clients using DHCPv4o6.
> 
> The outcome of this may also have a knock on effect of what’s going to be possible if we ever resurrect the unified-cpe work.

if you need the OPTION_S46_BR option in particular, perhaps something else as well? I think the cleanest would be to specify a new container option for this "mode".

cheers,
Ole