IETF Logo Mail Archive

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

Gyan Mishra <hayabusagsm@gmail.com> Sun, 30 January 2022 17:14 UTC

Return-Path: <hayabusagsm@gmail.com>
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 8226B3A17E8; Sun, 30 Jan 2022 09:14:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 k2AKHpl3yU7G; Sun, 30 Jan 2022 09:14:04 -0800 (PST)
Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C4183A181A; Sun, 30 Jan 2022 09:14:03 -0800 (PST)
Received: by mail-pl1-x631.google.com with SMTP id b15so10511778plg.3; Sun, 30 Jan 2022 09:14:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=oNuMLMQC7ERZnx18idy2wmmeeItUj9IrUjHNQ6DpLmI=; b=RIphbOFNz4qpIJ6eM5AeKkBD11STgy8QUBEmXFUw6/fTReuDLLp3uMnFM5ygQ0ZY6P nbdAMNHZ6MzMB0JPPcJEK4GRDcI7+DTUR3vLnQvinCjl6wnS0ndy8wJwUIeTLAbfgmAq 11l68xFJxRnp4uSyU27zegs8jOdpT7UNaruBzoHlTP3BsEGZXzGaK4KOI71fZmAdr4St LbVWaTTFHt18ACTW/jVC1Bla7bCM+fk6q0DQ74wbe15ZalEJ1eXjNCAMm5cOdBX7nRvl iAoBl3l4BHa1hZACcjLsev2ez08k0faAJfWElP6DjPvOyeGHvCHWiE3bl9QPJZyHdosS jrTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=oNuMLMQC7ERZnx18idy2wmmeeItUj9IrUjHNQ6DpLmI=; b=rN8z1erfZ0q3rStYtDoh7YoYhk85yPzvtT+oObABKziXy12s7ZIxgC8hkNzoJgOjPF GTfyrSmzXwXEukHiiNdXlWEK6LNYE7b4ki8cHD/aRKRNMAmmj3gyw3p2BvdGwLN3rTuk +GdrckdHZToeUznmrj6ztj2efWF39BbJ1okHZIxXOd8MMEc5NGwzxnJyj9Qiu6KV2GED Fhr1h9Jbalz4tOEvLtxxT+wFRimLFENlxEDhDXfWH7c/0QrYLWXUBtS/l/6oMEiBxXmc qEYAa8p09oVJjFthNYFJ3pcSWWegQ8zk76okPUyCP33r7rKD0MKPiJzBPK3QEOtHpG5v ECjQ==
X-Gm-Message-State: AOAM533LzfBss+D2TJxS4EZsrdfuok7qrKyRidBiDAgaEf3QNhDqLpSf ZuisNaBQ4sNm+UwNXQMF6FpYlo2OCd6Rn7VKRBIGpSUN
X-Google-Smtp-Source: ABdhPJx1dYbl4DblEMom7EGT97y31Hq5h7mxEJLy8cHizlOM8gzA+Wmyn/tGmNc7WyDm+Jkd03Xe6ZLW+Jyf3t4LWWU=
X-Received: by 2002:a17:902:ecc9:: with SMTP id a9mr17704467plh.58.1643562841753; Sun, 30 Jan 2022 09:14:01 -0800 (PST)
MIME-Version: 1.0
References: <164350909149.25132.16206084059279334692@ietfa.amsl.com> <94961E2C-DEFE-429B-BCEC-2228472747D7@chinatelecom.cn>
In-Reply-To: <94961E2C-DEFE-429B-BCEC-2228472747D7@chinatelecom.cn>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Sun, 30 Jan 2022 12:13:50 -0500
Message-ID: <CABNhwV1SWZ0aVehDhaK4+qrcPacu+PPZS6mQLDhHunFOc27rQg@mail.gmail.com>
To: Chongfeng Xie <xiechf@chinatelecom.cn>
Cc: V6Ops-Chairs <v6ops-chairs@ietf.org>, v6ops@ietf.org
Content-Type: multipart/alternative; boundary="00000000000059503805d6cfcb21"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/j-_q2oLHqDl7W_WX0YotU4yIOOg>
Subject: Re: [v6ops] Fwd: 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 17:14:10 -0000

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

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>
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
> Status:
> 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
>
>
> 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
> https://www.ietf.org/mailman/listinfo/v6ops
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*

v2.23.0 | Report a Bug | By Email