Re: [v6ops] New Version Notification for draft-xie-v6ops-reqirements-multi-domain-ipv6only-00.txt

Chongfeng Xie <xiechf@chinatelecom.cn> Sun, 30 January 2022 23:44 UTC

Return-Path: <xiechf@chinatelecom.cn>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C28E83A10F8; Sun, 30 Jan 2022 15:44:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=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 pRzeYVU8cEFC; Sun, 30 Jan 2022 15:44:22 -0800 (PST)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.226]) by ietfa.amsl.com (Postfix) with ESMTP id 8BEB63A10E9; Sun, 30 Jan 2022 15:44:20 -0800 (PST)
HMM_SOURCE_IP: 172.18.0.48:35310.1105686174
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-114.250.180.37 (unknown [172.18.0.48]) by chinatelecom.cn (HERMES) with SMTP id 8B444280029; Mon, 31 Jan 2022 07:44:15 +0800 (CST)
X-189-SAVE-TO-SEND: 66040161@chinatelecom.cn
Received: from ([172.18.0.48]) by app0024 with ESMTP id c7512001ebe94a0db2585b1925faa3ab for hayabusagsm@gmail.com; Mon, 31 Jan 2022 07:44:16 CST
X-Transaction-ID: c7512001ebe94a0db2585b1925faa3ab
X-Real-From: xiechf@chinatelecom.cn
X-Receive-IP: 172.18.0.48
X-MEDUSA-Status: 0
Sender: xiechf@chinatelecom.cn
From: Chongfeng Xie <xiechf@chinatelecom.cn>
Message-Id: <A6D9A2CA-6183-4C78-B07C-63C54F9F86B5@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="Apple-Mail=_62574B1C-3D46-428B-9C97-FEF9CFFAD54A"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Mon, 31 Jan 2022 07:44:13 +0800
In-Reply-To: <CABNhwV1SWZ0aVehDhaK4+qrcPacu+PPZS6mQLDhHunFOc27rQg@mail.gmail.com>
Cc: V6Ops-Chairs <v6ops-chairs@ietf.org>, v6ops@ietf.org
To: Gyan Mishra <hayabusagsm@gmail.com>
References: <164350909149.25132.16206084059279334692@ietfa.amsl.com> <94961E2C-DEFE-429B-BCEC-2228472747D7@chinatelecom.cn> <CABNhwV1SWZ0aVehDhaK4+qrcPacu+PPZS6mQLDhHunFOc27rQg@mail.gmail.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/rICtNSMNbKgTyv_v2mCB977Zv4Y>
Subject: Re: [v6ops] New Version Notification for draft-xie-v6ops-reqirements-multi-domain-ipv6only-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jan 2022 23:44:27 -0000

Hi,Gyan,
Thank you for introducing your draft and willing to provide input from IPv6-only PE design. I will add you as co-author in the next version.

Best regsrds
Chongfeng


> 2022年1月31日 上午1:13,Gyan Mishra <hayabusagsm@gmail.com> 写道:
> 
> 
> Hi Chongfeng
> 
> I have a draft that has been has been adopted by the BESS WG that is an IPv6-Only PE design that uses RFC 5565 Softwire mesh framework which is basically based on the concept of a single protocol core.  So a softwire is basically a tunnel of IPv4 edge packets over an IPv6 only  core or IPv6 packets over an IPv4 only core.  
> 
> The new innovative solution I am proposing is to help IXP peering points resolve IPv4 address depletion issues around the world by making the PE IPv6-Only eliminating all PE-CE IPv4 peering and carrying IPv4 prefixes over IPv6 next hop peer using RFC 8950 next hop encoding and forwarding IPV4 packets without PE-CE dual stack, basically processing the IPv4 packets and forwarding without having an IPv4 address configured on the PE-CE interface.
> 
> https://datatracker.ietf.org/doc/html/draft-ietf-bess-ipv6-only-pe-design-00 <https://datatracker.ietf.org/doc/html/draft-ietf-bess-ipv6-only-pe-design-00>
> I would be happy to collaborate as Co-author on your draft and provide input from my IPv6-Only PE design.
> 
> Kind Regards 
> 
> Gyan
> 
> On Sat, Jan 29, 2022 at 9:37 PM Chongfeng Xie <xiechf@chinatelecom.cn <mailto:xiechf@chinatelecom.cn>> wrote:
> 
> Hi, all,
> We have submitted a new draft as below. It mainly specifies requirements of multi-domain IPv6-only network from the perspective of operators.  Mutli-domain herein means a network is compose of multiple ASes and serves multiple scenarios, which is a common model for large-size operators.  This is only -00 draft and a start point, we are looking forward to receiving more comments and suggestions.   Thank you!
> 
> Best regards
> Chongfeng
> 
> 
> 
> 
> 
>> 
>> A new version of I-D, draft-xie-v6ops-reqirements-multi-domain-ipv6only-00.txt
>> has been successfully submitted by Chongfeng Xie and posted to the
>> IETF repository.
>> 
>> Name:		draft-xie-v6ops-reqirements-multi-domain-ipv6only
>> Revision:	00
>> Title:		Requirements to multi-domain IPv6-only network
>> Document date:	2022-01-29
>> Group:		Individual Submission
>> Pages:		13
>> URL:            https://www.ietf.org/archive/id/draft-xie-v6ops-reqirements-multi-domain-ipv6only-00.txt <https://www.ietf.org/archive/id/draft-xie-v6ops-reqirements-multi-domain-ipv6only-00.txt>
>> Status:         https://datatracker.ietf.org/doc/draft-xie-v6ops-reqirements-multi-domain-ipv6only/ <https://datatracker.ietf.org/doc/draft-xie-v6ops-reqirements-multi-domain-ipv6only/>
>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-xie-v6ops-reqirements-multi-domain-ipv6only <https://datatracker.ietf.org/doc/html/draft-xie-v6ops-reqirements-multi-domain-ipv6only>
>> 
>> 
>> Abstract:
>>   Dual-stack requires IPv4 and IPv6 are deployed in parallel, as it
>>   costs more to run two technologies than one.  IPv6-only is considered
>>   to be the next stage of IPv6 development from dual-stack.  This
>>   document specifies requirements when deploying IPv6-only in multi-
>>   domain networks.
>> 
>> 
>> 
>> 
>> The IETF Secretariat
>> 
>> 
>> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org <mailto:v6ops@ietf.org>
> https://www.ietf.org/mailman/listinfo/v6ops <https://www.ietf.org/mailman/listinfo/v6ops>
> -- 
>  <http://www.verizon.com/>
> Gyan Mishra
> Network Solutions Architect 
> Email gyan.s.mishra@verizon.com <mailto:gyan.s.mishra@verizon.com>
> M 301 502-1347
> 
>