[Softwires] Fwd: New Version Notification for draft-liu-softwire-lw4over6-dhcp-deployment-04.txt

Cong Liu <gnocuil@gmail.com> Wed, 23 July 2014 17:07 UTC

Return-Path: <gnocuil@gmail.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 62A9D1A014C for <softwires@ietfa.amsl.com>; Wed, 23 Jul 2014 10:07:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=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 KGtwytVd1pFx for <softwires@ietfa.amsl.com>; Wed, 23 Jul 2014 10:07:26 -0700 (PDT)
Received: from mail-oa0-x232.google.com (mail-oa0-x232.google.com [IPv6:2607:f8b0:4003:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37CFF1A012D for <softwires@ietf.org>; Wed, 23 Jul 2014 10:07:26 -0700 (PDT)
Received: by mail-oa0-f50.google.com with SMTP id g18so2035103oah.23 for <softwires@ietf.org>; Wed, 23 Jul 2014 10:07:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=2ky8Am1d8QtDyKiZMM+vtglcByICDNpNpgKwY0z6lJM=; b=EWlWp+KBkm6haNtMgn1zZ6YMrGrMpLr6FdRTo3epSsvPDIWsGWvx7Hg9lq4Pmd4pVc 50N+3ArWaR6yEngMxo2YiFstewaq9IErQ/jvmCJJCPVUSs6Od98P81hIVnaydMYPH6y9 VlagjT+vS10GAhhqGrgTJYnKETS5ANuSUevnVa7SzAb+DZEDYHfKUERxi0EwFKbeMBuI yxorRJZGAZQmilCLhL34Y1NKddR93XZYNkXOjAt1XuelQIjRptQ/3H+ZteGi0X26IyK1 0IRwUHUCGlgIdApwvuV4eMTxNFaJjP/ltgCqzUnsi4uH7qEtlSh3rRtwbOJpKlDEgOUD fjaA==
X-Received: by 10.60.176.10 with SMTP id ce10mr4255225oec.8.1406135245518; Wed, 23 Jul 2014 10:07:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.85.12 with HTTP; Wed, 23 Jul 2014 10:07:05 -0700 (PDT)
In-Reply-To: <20140723144832.13737.46667.idtracker@ietfa.amsl.com>
References: <20140723144832.13737.46667.idtracker@ietfa.amsl.com>
From: Cong Liu <gnocuil@gmail.com>
Date: Wed, 23 Jul 2014 13:07:05 -0400
Message-ID: <CAF+sHxGwJiByGm8FbJZe_TX7SqUuD4oF+QKz3=3r3sgMVGxiXQ@mail.gmail.com>
To: softwires <softwires@ietf.org>
Content-Type: multipart/alternative; boundary="089e0118313ad0bced04fedf5f99"
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/o0PFwP2Yp6R-GFkH9m1kREhEufE
Subject: [Softwires] Fwd: New Version Notification for draft-liu-softwire-lw4over6-dhcp-deployment-04.txt
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: Wed, 23 Jul 2014 17:07:30 -0000

Hi all,

I updated this draft to clarify its purpose. It is an informational memo
that describes
how dynamic provisioning mode of Lightweight 4over6 is organized by the
following drafts:
  IPv4 provisioning: I-D.ietf-dhc-dhcpv4-over-dhcpv6 (In RFC Ed queue)
  Port set option: I-D.ietf-dhc-dynamic-shared-v4allocation (will issue
WGLC)
  Tunnel source address option: I-D.fsc-softwire-dhcp4o6-saddr-opt

It is not a new provisioning method proposal, but just a description of an
existing thing.
As far as I know, it was the preferred method before IETF88, and was
changed due to the slow progress of port set draft.
I believe that it is why the dhcpv4o6 and port set draft were proposed.
Since these drafts seem to be in a good progress, I think it is worth be
documented.

Comments on the mailing list or softwire session are more than welcome.

Best Regards,
Cong



---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: 2014-07-23 10:48 GMT-04:00
Subject: New Version Notification for
draft-liu-softwire-lw4over6-dhcp-deployment-04.txt
To: Jianping Wu <jianping@cernet.edu.cn>, Cong Liu <gnocuil@gmail.com>, Qi
Sun <sunqi@csnet1.cs.tsinghua.edu.cn>



A new version of I-D, draft-liu-softwire-lw4over6-dhcp-deployment-04.txt
has been successfully submitted by Cong Liu and posted to the
IETF repository.

Name:           draft-liu-softwire-lw4over6-dhcp-deployment
Revision:       04
Title:          Dynamic IPv4 Provisioning for Lightweight 4over6
Document date:  2014-07-23
Group:          Individual Submission
Pages:          7
URL:
http://www.ietf.org/internet-drafts/draft-liu-softwire-lw4over6-dhcp-deployment-04.txt
Status:
https://datatracker.ietf.org/doc/draft-liu-softwire-lw4over6-dhcp-deployment/
Htmlized:
http://tools.ietf.org/html/draft-liu-softwire-lw4over6-dhcp-deployment-04
Diff:
http://www.ietf.org/rfcdiff?url2=draft-liu-softwire-lw4over6-dhcp-deployment-04

Abstract:
   Lightweight 4over6 [I-D.ietf-softwire-lw4over6] is an IPv4 over IPv6
   hub and spoke mechanism that provides overlay IPv4 services in an
   IPv6-only access network.  Provisioning IPv4 addresses and port set
   to customers is the core function of Lightweight 4over6 control
   plane.  [I-D.ietf-softwire-lw4over6] illustrates how to use DHCPv6
   for deterministic IPv4 provisioning.  This document discusses how to
   provision IPv4 parameters by using dynamic IPv4 provisioning
   protocols such as DHCPv4 over DHCPv6
   [I-D.ietf-dhc-dhcpv4-over-dhcpv6].  This document describes a dynamic
   IPv4 provisioning mode for Lightweight 4over6 that uses DHCPv4 over
   DHCPv6 [I-D.ietf-dhc-dhcpv4-over-dhcpv6] for IPv4 address
   provisioning.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat