[Softwires] Fwd: Re: I-D Action: draft-ietf-softwire-lightweight-4over6-deployment-01.txt
Yannis Nikolopoulos <yanodd@otenet.gr> Wed, 09 August 2017 14:32 UTC
Return-Path: <yanodd@otenet.gr>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7149F13232C for <softwires@ietfa.amsl.com>; Wed, 9 Aug 2017 07:32:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham autolearn_force=no
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 IV6y_Jmw7Hly for <softwires@ietfa.amsl.com>; Wed, 9 Aug 2017 07:32:33 -0700 (PDT)
Received: from calypso.otenet.gr (calypso.otenet.gr [83.235.67.36]) by ietfa.amsl.com (Postfix) with ESMTP id A0F1E1321F1 for <softwires@ietf.org>; Wed, 9 Aug 2017 07:32:32 -0700 (PDT)
Received: from [192.168.1.3] (dusted.otenet.gr [195.167.126.245]) by calypso.otenet.gr (ESMTP) with ESMTPSA id 452931381D3 for <softwires@ietf.org>; Wed, 9 Aug 2017 17:32:31 +0300 (EEST)
References: <c140a889-2612-d468-0365-571e05f16048@otenet.gr>
To: Softwires WG <softwires@ietf.org>
From: Yannis Nikolopoulos <yanodd@otenet.gr>
X-Forwarded-Message-Id: <c140a889-2612-d468-0365-571e05f16048@otenet.gr>
Message-ID: <69e86eb2-c0a2-600a-1a8e-406204cf46a2@otenet.gr>
Date: Wed, 09 Aug 2017 17:32:31 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <c140a889-2612-d468-0365-571e05f16048@otenet.gr>
Content-Type: multipart/alternative; boundary="------------D8C9E7FE3C7C884903B47458"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/Twi9JNDv2l4guBsDXXESe4R2J00>
Subject: [Softwires] Fwd: Re: I-D Action: draft-ietf-softwire-lightweight-4over6-deployment-01.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Aug 2017 14:32:37 -0000
forwarding this to the list also, in case anyone cares to comment regards, Yannis -------- Forwarded Message -------- Subject: Re: [Softwires] I-D Action: draft-ietf-softwire-lightweight-4over6-deployment-01.txt Date: Sat, 8 Jul 2017 23:13:29 +0300 From: Yannis Nikolopoulos <yanodd@otenet.gr> To: yiu_lee@cable.comcast.com, xiechf@ctbri.com.cn, fibrib@gmail.com, tianxiang li <peter416733@gmail.com>, Farrer, Ian (DTAG) <ian.farrer@telekom.de> CC: Nikolopoulos Yannis <yanodd@otenet.gr> Dear authors , as I said in the past, I believe that this is a very useful draft. We, at OTE Greece are also deploying LW4o6 so if you need to enrich the draft's test cases let me know. Also, please find a few comments below: "1. intro The logging requirements to meet regulatory requirements may be reduced as it is only necessary to log when a subscriber is provisioned or de-provisioned in the lwAFTR. This relaxes the need for logging on a per-session, or per port block allocation." [YN]: One still cannot comply with regulatory requirements because of the A+P model (and because most servers on the internet do not log the client's port number).So, how are the regulatory requirements reduced? "3.1. IP Addressing and Routing In Lightweight 4over6, there is no inter-dependency between the IPv4 and IPv6 addressing schemes. This allows for complete flexibilty in addressing architecture." [YN]: although true, the above statement can be a bit misleading. I believe that it should be mentioned that a proper addressing scheme for IPv6 (lw4o6 esp.) should already be in place and ideally, IPv4 ranges should be predefined (for routing efficienncy, e.g contiguous ranges) "3.1.1. IPv4 Routing The IPv4 addresses/prefixes that are allocated to customer's lwB4s are advertised to the IPv4 Internet as being reachable via the lwAFTR(s). If multiple lwAFTRs are all serving the same set of lwB4s, all will advertise the same IPv4 reachable routes." YN: if multiple lwAFTRs, IPv4 prefixes could also be split, for routing efficiency. That all depends on operator's and operator's upstream topology and PoPs best regards, Yannis On 07/03/2017 06:58 PM, internet-drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Softwires of the IETF. > > Title : Deployment Considerations for Lightweight 4over6 > Authors : Qiong Sun > Chongfeng Xie > Yiu L. Lee > Maoke Chen > Tianxiang Li > Ian Farrer > Filename : draft-ietf-softwire-lightweight-4over6-deployment-01.txt > Pages : 23 > Date : 2017-07-03 > > Abstract: > Lightweight 4over6 is a mechanism for providing IPv4 services to > clients connected to a single-stack IPv6 network. The architecture > is similar to DS-Lite, but the network address translation function > is relocated from the tunnel concentrator to the tunnel client, hence > reducing the amount of state which must be maintained in the > concentrator to a per-customer level. This document discusses the > applicability, describes various deployment models and provides > deployment considerations for Lightweight 4over6. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-softwire-lightweight-4over6-deployment/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-softwire-lightweight-4over6-deployment-01 > https://datatracker.ietf.org/doc/html/draft-ietf-softwire-lightweight-4over6-deployment-01 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-lightweight-4over6-deployment-01 > > > 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. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > Softwires mailing list > Softwires@ietf.org > https://www.ietf.org/mailman/listinfo/softwires
- [Softwires] I-D Action: draft-ietf-softwire-light… internet-drafts
- [Softwires] Fwd: Re: I-D Action: draft-ietf-softw… Yannis Nikolopoulos
- Re: [Softwires] Fwd: Re: I-D Action: draft-ietf-s… mohamed.boucadair