Re: [v6ops] draft-smith-v6ops-larger-ipv6-loopback-prefix-04

Gyan Mishra <hayabusagsm@gmail.com> Mon, 02 November 2020 09:28 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 57EF73A0C38 for <v6ops@ietfa.amsl.com>; Mon, 2 Nov 2020 01:28:16 -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 waCQZu4ejPYh for <v6ops@ietfa.amsl.com>; Mon, 2 Nov 2020 01:28:14 -0800 (PST)
Received: from mail-vk1-xa2f.google.com (mail-vk1-xa2f.google.com [IPv6:2607:f8b0:4864:20::a2f]) (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 6D29D3A0C1F for <v6ops@ietf.org>; Mon, 2 Nov 2020 01:28:14 -0800 (PST)
Received: by mail-vk1-xa2f.google.com with SMTP id k125so2816160vka.11 for <v6ops@ietf.org>; Mon, 02 Nov 2020 01:28:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gfBB2+gka1XW6jYRG3yntsZTEL/QfyxB74f8UdBd8Fo=; b=Hoo5xYNedSznRuoZw3grUNtrsywuByERY0IP3krVYnFb6cT63gjQoDIBjXDe5gAajF S6XxjYEk6eNfGgis8rJSVUsmk/r6PtbZBcCTIJbXkzcxodiUmOSkZEZZNFnltspd5C6n Gr8z5kq/49qjTDavnFX3tmalqoI9sHRer75MapU2rahVPt2CTRO60EKydWiEGolQqej/ I3l8U9DiNd8pGATwqgxBZkU/PzGBF7fEdm/9CTYwp+BvgSMCZbRvh1SEgrw96g5SN4kT pkmTRST3Q+TMnk7slfPtK5lObbFVT5BxdqEpEeAQoyeJqtwwYNNwGqPu4tf1kgj5aZPE RFhA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gfBB2+gka1XW6jYRG3yntsZTEL/QfyxB74f8UdBd8Fo=; b=tyaV4Hk+ZLiVwjpcoVv2fcTYew5p64gv4gklsaQniY+x49JmAFRQ6ULLa/2qv2kS4M /jbDrjlGKw2G3gApy66mDWURWFNh6IEEkn3drLU/rF4g33AnhnIZVWgmabRDx0vRNB7H wJ72EW0BqKla26XqPiJ4y6IswXATWIHyijKGHgSX0dmlPAGvsrfXX3wSXB5ms9G2cEgW rq64/Ex56t3iGuGYYxoIFfpSMB1CDQ2cYcPsJqU0ErmOmFV1uijrNc6zeTuW1Zfb9nLo PhH3H7bJxsExqI1gOV+pei5eTA35bICG7G0bgzPMEbeA0roE/LRCBFpMr7m7mecNzEE2 hIRA==
X-Gm-Message-State: AOAM532V4ILZXEFp0RLSILzNVKFfQeeGwAFPgThyKumkQJDKcUrtyZ4u /MezlEyruEYXyfhTil8tPmAADLmoUqg079LfNOQ=
X-Google-Smtp-Source: ABdhPJymhOn0zoglNqt3u1lOdvsxwvrHTrtO8cZkcTqbgkOaRHLBX++8Ob5smKH7gcaWqXYIjz3KebnLrFyzOoVn2t8=
X-Received: by 2002:a1f:a791:: with SMTP id q139mr12278200vke.25.1604309293390; Mon, 02 Nov 2020 01:28:13 -0800 (PST)
MIME-Version: 1.0
References: <19EE82F7-8D52-4519-8087-0DF17435A3B8@gmail.com> <CAO42Z2zYftE7AxtDNOcCLCf6-5PNRaZ52tShDiq1kY7VP6xHrA@mail.gmail.com> <CABNhwV3JP4k-mf_NvuKAOnDfoH3PT0m6gKy5KfAfNv_NhWV0yA@mail.gmail.com> <CAO42Z2wjkayV-azkEnXd1EyL9QMRPGj8c41+aEx+E2uw9RQacA@mail.gmail.com> <CABNhwV0S0P=w-PqU1QF+_vjN8yhycDcdtmkYqdFTgzHxLz4GNg@mail.gmail.com> <CAO42Z2x5Yi_BAVf6urc=LiR5cP81kmx=0Bj74FHwMeWFebjbvQ@mail.gmail.com> <49AEE43E-3C39-4B85-AEB7-321BFF5ABBC6@gmail.com>
In-Reply-To: <49AEE43E-3C39-4B85-AEB7-321BFF5ABBC6@gmail.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Mon, 02 Nov 2020 04:28:02 -0500
Message-ID: <CABNhwV2AiTuSm+1P_VXK8LhEUK_+eWX1uSW70egnhy2REKd6GA@mail.gmail.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: Greg Mirsky <gregimirsky@gmail.com>, Jeff Tantsura <jefftant.ietf@gmail.com>, Mark Smith <markzzzsmith@gmail.com>, v6ops list <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008ade7505b31c5d7b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/vTyF5k3iGwiw1eJ9AyoZnNRr97Y>
Subject: Re: [v6ops] draft-smith-v6ops-larger-ipv6-loopback-prefix-04
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: Mon, 02 Nov 2020 09:28:16 -0000

On Mon, Nov 2, 2020 at 1:35 AM Fred Baker <fredbaker.ietf@gmail.com> wrote:

>
>
> > On Oct 29, 2020, at 1:42 AM, Mark Smith <markzzzsmith@gmail.com> wrote:
> >
> > I've thought that the use of Anycast would increase, and have thought
> that it would be useful to have a specially designated anycast prefix. It
> has also occurred to me that anycast has some of the properties of unicast
> as well as some of the properties of multicast, so could be seen to fit in
> between unicast and multicast (1:1 -> 1:Any -> 1:Many)
>
> That's a reasonable description of anycast as deployed.


   Gyan> Agreed

>
>
> My question in that would be exactly what you might want to change. We
> have some pretty widespread use of anycast today (
> https://www.iana.org/domains/root/servers https://root-servers.org), and
> to my knowledge it seems to work just fine. If we're going to replace
> existing anycast with some sort of anycast prefix, the first big change we
> have to make is in BGP; it can advertise a unicast prefix or address, but
> can't, today at least, advertise an anycast prefix.Then we have to tell
> hosts that they can send traffic to such addresses and should. I think we
> should have a good reason if we're going to boil the ocean.


   Gyan> Good point and as you mention services such as DNS, NTP
predominantly but even Syslog, snmp, netflow have gone the way of Anycast
VIP advertisement via a lb for proximity routing to unicast address for a
just about any service can be done the ASM way and works very well.

I think with IPv6 a lot of thought was put into the addressing schema I am
guessing like the built in Anycast range out of the GUI range without a use
case but hopes for if you build they will come which I guess never
happened.  So then I guess it never took of as it would require some
changes to BGP.  Working with BGP on parameters and codepoint development
in some of the other WGs, if there is a real gain or use case for an
Anycast BGP SAFI  I could author a draft to make it happen but I would need
to figure out the why and what gap is not being filled by the existing
Anycast capability via unicast today which has been widely  proliferated.

> --

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

*Gyan Mishra*

*Network Solutions A**rchitect *



*M 301 502-134713101 Columbia Pike *Silver Spring, MD