Re: [5gangip] New Version Notification for draft-xyzy-atick-gaps-00.txt
Tom Herbert <tom@herbertland.com> Wed, 30 May 2018 19:23 UTC
Return-Path: <tom@herbertland.com>
X-Original-To: 5gangip@ietfa.amsl.com
Delivered-To: 5gangip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A4BF126C22 for <5gangip@ietfa.amsl.com>; Wed, 30 May 2018 12:23:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.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 2P72I4ur4aiK for <5gangip@ietfa.amsl.com>; Wed, 30 May 2018 12:23:52 -0700 (PDT)
Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::229]) (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 88EA712D777 for <5gangip@ietf.org>; Wed, 30 May 2018 12:23:52 -0700 (PDT)
Received: by mail-qt0-x229.google.com with SMTP id j1-v6so24759126qtp.2 for <5gangip@ietf.org>; Wed, 30 May 2018 12:23:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=AE2KIbo0+S+tcKuqFRvMmYH1ZuG9+45VCp9aEAEbqXE=; b=LLY82LbBvopxXH3aHkEhQHcFPigFn+GX5VI20djM7ka8b3qikcDStDsaKr7tRwcsz4 BHqlofdB7JQPH6osnIxzSGNyGjhjm1wBEI/GmaWhbVhsGnjo/2PvbS5zIlnMe3RYny47 4TwW0nRecHIFF5u7spEV9GGwNciAiVt0xVXheettJy4HJlG5q9FfEYTbhhiUONiXNRzA 24qfB8+N9sLXPZyI+ovuewF8IzEzzvLVtJYXk4Ys6oy52LjCj7hsBNwRpOiKmPpUXIgA 1cTn2fQchR1bao1d57AFnfbvkKREu/bftl06fE0ik/sm+ggRB4OKFjoEXL371ZzpsZsd QFFQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=AE2KIbo0+S+tcKuqFRvMmYH1ZuG9+45VCp9aEAEbqXE=; b=bXooxwLTVhi7OUMgIUr7TdzO4G5usgYf8UCTZ2GEz8BtlYdAro+jUJDwEKXIlOuiiK dul1IaXvMi3zSetvxuAhHTYbKYHXL3VKEn+LsszPVDZx6h5fI6Exncx/mrUBAY0abh98 M1aOb3PUs/C8xBMbh44d8iEO7pZp/4w3zuXuS9IhJa2yDq35Btg3WgsPNJjYOVY2GYEZ Ow+KsVaRdpXJBhg4NIP1ZJZT1u1DN0J94Q0GrdpDQSzQkpIjFxO8uDdzqF0NsQSco6sd aS+8JEQZrkVBHwDmPkSeakO086qWVzllrrqfgvekRlMS1kxkyJCXN0XBgqP90/XB0j9v zDJg==
X-Gm-Message-State: APt69E07MSznTR3AGXS3Qe3o1g2N1Xi8wx94nsXOhOP7UOYS9dsiRYDS ZWAOidELsSanLKtlw9bFhnoWhotVSQ85TWRbVdNokw==
X-Google-Smtp-Source: ADUXVKKb9VCx6Jpzzjipe370DJqRaUq7gBQZqngAzmgf8YCuz39JG6OKgLUzCrqTqCLGvTLUk5ulHWFt2PqB9p9gZOs=
X-Received: by 2002:a0c:88e1:: with SMTP id 30-v6mr3834210qvo.73.1527708231352; Wed, 30 May 2018 12:23:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:aed:3042:0:0:0:0:0 with HTTP; Wed, 30 May 2018 12:23:50 -0700 (PDT)
In-Reply-To: <2F23E4CA-7571-48A5-9D69-4E15E7EE8A73@st-andrews.ac.uk>
References: <CAC8QAcfuk6e+JPuKC4sw=FPYSgO3Tkr5mjSRJeOzvjxUSc9xFw@mail.gmail.com> <B300114A-8838-4FE2-8FA9-95BA4CD07089@st-andrews.ac.uk> <C42C02FB-4452-4D4F-A826-F24D401BB76D@gigix.net> <45CC5F57-FD4B-4F5B-9852-93F97F08E81F@st-andrews.ac.uk> <AA3C010C-61B2-4214-ADBA-C0209E29A7C0@gigix.net> <CAC8QAcdpnUt-s=ohqQ5gmw2LPN7n17i6RVPRjzK324kNgNLtSg@mail.gmail.com> <CALx6S36HMf5B7cnatqmh2Sb_kK5NSG5BM_ynCkfCwJWHM88z-A@mail.gmail.com> <A66642D8-940A-4A6A-A183-565B170E20C0@st-andrews.ac.uk> <CY1PR15MB08746517938F92224DFE3634D06C0@CY1PR15MB0874.namprd15.prod.outlook.com> <CAC8QAcds7H8neBdVQngnAMe-UpZnb8_h1kc5ZgV8y_ZqgDqhKg@mail.gmail.com> <E2ADB823-2332-4431-806B-CA1CE029E357@st-andrews.ac.uk> <CALx6S34zM7DvJfxpFs3ZGQo64Cqo-7TMncFm+RKX=Za1V3YUvQ@mail.gmail.com> <2F23E4CA-7571-48A5-9D69-4E15E7EE8A73@st-andrews.ac.uk>
From: Tom Herbert <tom@herbertland.com>
Date: Wed, 30 May 2018 12:23:50 -0700
Message-ID: <CALx6S35RFvH-UfNYeBEmJ4s9p6thFHfttkon3tvEeV5in6vbnA@mail.gmail.com>
To: Saleem Bhatti <saleem@st-andrews.ac.uk>
Cc: Behcet Sarikaya <sarikaya@ieee.org>, David Allan I <david.i.allan@ericsson.com>, Luigi Iannone <ggx@gigix.net>, 5GANGIP <5gangip@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/5gangip/0dGAM6Xo0aYF1FOvGSZeZWJWaW0>
Subject: Re: [5gangip] New Version Notification for draft-xyzy-atick-gaps-00.txt
X-BeenThere: 5gangip@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of implications of the upcoming 5th Generation \(fixed and\) Mobile communication systems on IP protocols." <5gangip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/5gangip>, <mailto:5gangip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/5gangip/>
List-Post: <mailto:5gangip@ietf.org>
List-Help: <mailto:5gangip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/5gangip>, <mailto:5gangip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 May 2018 19:23:56 -0000
On Wed, May 30, 2018 at 12:08 PM, Saleem Bhatti <saleem@st-andrews.ac.uk> wrote: > > >> On 30 May 2018, at 20:01, Tom Herbert <tom@herbertland.com> wrote: >> >> On Wed, May 30, 2018 at 11:48 AM, Saleem Bhatti <saleem@st-andrews.ac.uk> wrote: >>> Behcet; >>> >>> On 30 May 2018, at 19:35, Behcet Sarikaya <sarikaya2012@gmail.com> wrote: >>> >>> >>> >>> On Wed, May 30, 2018 at 1:28 PM, David Allan I <david.i.allan@ericsson.com> >>> wrote: >>>> >>>> The only network upgrade for ILNP is DNS support for RFC 6742, which is >>>> believe is already deployed. >>>> >>> >>> I am not sure about deployed but maybe defined is better. >>> >>> >>> If you are running the most recent version of BIND, KnotDNS, or NSD, then >>> they support RFC6742 out-of-the-box, as far as I know. >>> >> The more relevant question would be which host OSes support ILNP. > > Currently, probably about the same number as the networks that support ILA ;-) > Saleem, I'm not sure how to interpret your response. ILA has been in upstream for a while and is begin deployed. I know that ILNP is not in Linux, but I don't know about other OSes. Tom > Cheers, > --/Saleem > > >> >> Tom >> >>> Cheers, >>> --/Saleem >>> >>> >>> However, DNS is not privacy enabled which is our main issue here. >>> >>> >>> Regards, >>> Behcet >>>> >>>> Cheers >>>> Dave >>>> >>>> -----Original Message----- >>>> From: 5gangip <5gangip-bounces@ietf.org> On Behalf Of Saleem Bhatti >>>> Sent: Wednesday, May 30, 2018 9:19 AM >>>> To: Tom Herbert <tom@herbertland.com> >>>> Cc: Luigi Iannone <ggx@gigix.net>; 5GANGIP <5gangip@ietf.org>; Behcet >>>> Sarikaya <sarikaya@ieee.org> >>>> Subject: Re: [5gangip] New Version Notification for >>>> draft-xyzy-atick-gaps-00.txt >>>> >>>> Tom; >>>> >>>>> On 30 May 2018, at 16:44, Tom Herbert <tom@herbertland.com> wrote: >>>>> >>>>> Behcet, >>>>> >>>>> The statement "For ILNP the basic deployment requires end-systems to >>>>> be updated." is unscoped. As written, this would imply that all hosts >>>>> on the Internet need to be updated to support ILNP. That is simply a >>>>> non-starter. >>>> >>>> Good catch - thanks. >>>> >>>>> If the idea is that ILNP can be deployed by networks then hosts within >>>>> that network can be updated. >>>> >>>> Only those end-systems that need to use ILNP need to be updated. ILNP >>>> nodes can work in networks with non-ILNP nodes - see Section 10.4 of >>>> RFC6741. >>>> >>>> >>>>> But, then the question >>>>> becomes how ILNP hosts are going to be able to talk non ILNP hosts >>>>> (say servers on the Internet). For that the an ILNP gateway or proxy >>>>> also must be deployed in the network. >>>> >>>> A gateway or proxy is not required. >>>> >>>> ILNPv6 can be seen as a superset of IPv6. ILNPv6 drops back to IPv6 when >>>> required - the process is described in Section 10.6 of RFC6741. >>>> >>>> Cheers, >>>> --/Saleem >>>> >>>> >>>>> >>>>> Tom >>>>> >>>>> On Wed, May 30, 2018 at 7:20 AM, Behcet Sarikaya >>>>> <sarikaya2012@gmail.com> wrote: >>>>>> Luigi, Saleem, >>>>>> >>>>>> What is the agreement now as to the revision of the draft? >>>>>> >>>>>> I had already added some text regarding UE being alone on the link, >>>>>> i.e. >>>>>> point-to-point link in wireless networks, that should make both sides >>>>>> happy? >>>>>> >>>>>> Regards, >>>>>> Behcet >>>>>> >>>>>> On Tue, May 29, 2018 at 7:25 AM, Luigi Iannone <ggx@gigix.net> wrote: >>>>>>> >>>>>>> Hi Saleem, >>>>>>> >>>>>>> On 29 May 2018, at 12:03, Saleem Bhatti <saleem@st-andrews.ac.uk> >>>>>>> wrote: >>>>>>> >>>>>>> Hello Luigi; >>>>>>> >>>>>>> Thanks for your comments - my responses are inline, below. >>>>>>> >>>>>>> On 29 May 2018, at 09:32, Luigi Iannone <ggx@gigix.net> wrote: >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> >>>>>>> On 28 May 2018, at 19:16, Saleem Bhatti <saleem@st-andrews.ac.uk> >>>>>>> wrote: >>>>>>> >>>>>>> There is some text which is incorrect - on page 4: >>>>>>> >>>>>>> ---- >>>>>>> Furthermore, ILNP demands a change in the way local (e.g., within a >>>>>>> LAN) communication is carried out, needing all of the devices to >>>>>>> support ILNP. This in turn may raise heavy deployability issues. >>>>>>> ---- >>>>>>> >>>>>>> This is not true - "all devices" do *not* need to be updated, but >>>>>>> only those end-systems that wish to use ILNPv6. Switches >>>>>>> >>>>>>> >>>>>>> Switches clearly do not need to be changed since they are L2. >>>>>>> >>>>>>> >>>>>>> Agreed. >>>>>>> >>>>>>> However, the text clearly says "all of the devices", which is >>>>>>> incorrect. >>>>>>> >>>>>>> >>>>>>> Agreed. >>>>>>> >>>>>>> >>>>>>> >>>>>>> and routers >>>>>>> >>>>>>> >>>>>>> You need to implement the ILCC in your first hop router. >>>>>>> >>>>>>> >>>>>>> No, that is not required. I have a testbed at St Andrews and we run >>>>>>> Linux routers that are not modified, and are not ILNP-aware. For >>>>>>> example, please see the testbed experiment described in this paper: >>>>>>> >>>>>>> IP without IP addresses >>>>>>> https://dl.acm.org/citation.cfm?doid=3012695.3012701 >>>>>>> >>>>>>> >>>>>>> Thanks for the pointer. :-) >>>>>>> >>>>>>> >>>>>>> Then you need new ICMP messages, and few other tricks here and there >>>>>>> in existing stuff. >>>>>>> >>>>>>> >>>>>>> The new ICMP messages, e.g. Locator Updates for ILNPv6, RFC6743, are >>>>>>> end-to-end - only the end hosts needs to be updated to generate >>>>>>> these messages. >>>>>>> >>>>>>> If any on-path routers wish to examine such messages, then yes, they >>>>>>> would need to be updated, but that is not required for ILNPv6 to work. >>>>>>> >>>>>>> >>>>>>> Ack. >>>>>>> >>>>>>> >>>>>>> Other solutions are more clear because introduce new entities and >>>>>>> protocol, so either you have it or you don’t. >>>>>>> >>>>>>> >>>>>>> Yet, may be the last sentence can be soften deleting “heavy”. >>>>>>> >>>>>>> >>>>>>> All new solutions will incur some sort of deployment overhead, so I >>>>>>> am not sure why such a comment should apply specifically and only to >>>>>>> ILNP. >>>>>>> >>>>>>> For ILNP the basic deployment requires end-systems to be updated. >>>>>>> Such updates would be deployed through over-the-air updates, as is >>>>>>> common today with many operating systems. DNS entries for ILNP nodes >>>>>>> would also be needed, and the new DNS RRs for ILNP (RFC6742) are >>>>>>> supported commercially (e.g. by BIND, NSD, and KnotDNS, and possibly >>>>>>> others).. >>>>>>> >>>>>>> For other solutions, other deployment issues exist, e.g. for ILA and >>>>>>> LISP, new network entities/functions need to be deployed and managed >>>>>>> for routing, and so, I guess, the existing network will need to be >>>>>>> reconfigured to integrate the new functionality. I am guessing some >>>>>>> operators may find that a "heavy" deployment burden, but it is best >>>>>>> that those operators comment on whether or not they see that is a >>>>>>> problem, as I have no experience with running large networks. >>>>>>> >>>>>>> >>>>>>> Updating end-systems is IMHO a real nightmare. You have no control >>>>>>> on who will update and when. Network history is full of such examples. >>>>>>> Yes, ILA and LISP has to be deployed by operators, but they can have >>>>>>> full control of what will happen in their own network (which they >>>>>>> usually like). >>>>>>> YMMV. >>>>>>> >>>>>>> In general, I may agree that deployment considerations for all of >>>>>>> the considered solutions can be improved and corrected. >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> L. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Cheers, >>>>>>> --/Saleem >>>>>>> >>>>>>> >>>>>>> Ciao >>>>>>> >>>>>>> L. >>>>>>> >>>>>>> >>>>>>> do not need to be updated, as ILNPv6 is backwards compatible with >>>>>>> IPv6. It is possible to run an ILNPv6 node in a LAN which also has >>>>>>> non-ILNPv6 nodes. >>>>>>> >>>>>>> Cheers, >>>>>>> --/Saleem >>>>>>> >>>>>>> >>>>>>> On 25 May 2018, at 15:50, Behcet Sarikaya <sarikaya2012@gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> We have submitted the gaps draft. Those who have contributed text >>>>>>> are listed as co-authors. >>>>>>> Please send your comments to the list. >>>>>>> >>>>>>> Regards, >>>>>>> Dirk& Behcet >>>>>>> >>>>>>> A new version of I-D, draft-xyzy-atick-gaps-00.txt has been >>>>>>> successfully submitted by Behcet Sarikaya and posted to the IETF >>>>>>> repository. >>>>>>> >>>>>>> Name: draft-xyzy-atick-gaps >>>>>>> Revision: 00 >>>>>>> Title: Gap and Solution Space Analysis for End to End Privacy >>>>>>> Enabled Mapping System >>>>>>> Document date: 2018-05-25 >>>>>>> Group: Individual Submission >>>>>>> Pages: 10 >>>>>>> URL: >>>>>>> https://www.ietf.org/internet-drafts/draft-xyzy-atick-gaps-00.txt >>>>>>> Status: >>>>>>> https://datatracker.ietf.org/doc/draft-xyzy-atick-gaps/ >>>>>>> Htmlized: https://tools.ietf.org/html/draft-xyzy-atick-gaps-00 >>>>>>> Htmlized: >>>>>>> https://datatracker.ietf.org/doc/html/draft-xyzy-atick-gaps >>>>>>> >>>>>>> >>>>>>> Abstract: >>>>>>> This document presents a gap and solution analysis for end-to-end >>>>>>> privacy enabled mapping systems. Each of the identifier locator >>>>>>> separation system has its own approach to mapping identifiers to the >>>>>>> locators. We analyse all these approaches and identify the gaps in >>>>>>> each of them and do a solution space analysis in an attempt to >>>>>>> identify a mapping system that can be end to end privacy enabled. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> 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 >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 5gangip mailing list >>>>>>> 5gangip@ietf.org >>>>>>> https://www.ietf.org/mailman/listinfo/5gangip >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 5gangip mailing list >>>>>>> 5gangip@ietf.org >>>>>>> https://www.ietf.org/mailman/listinfo/5gangip >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 5gangip mailing list >>>>>>> 5gangip@ietf.org >>>>>>> https://www.ietf.org/mailman/listinfo/5gangip >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 5gangip mailing list >>>>>> 5gangip@ietf.org >>>>>> https://www.ietf.org/mailman/listinfo/5gangip >>>>>> >>>>> >>>>> _______________________________________________ >>>>> 5gangip mailing list >>>>> 5gangip@ietf.org >>>>> https://www.ietf.org/mailman/listinfo/5gangip >>>> >>>> _______________________________________________ >>>> 5gangip mailing list >>>> 5gangip@ietf.org >>>> https://www.ietf.org/mailman/listinfo/5gangip >>> >>> >>> >
- Re: [5gangip] New Version Notification for draft-… FIGURELLE, TERRY F
- Re: [5gangip] New Version Notification for draft-… Luigi Iannone
- Re: [5gangip] New Version Notification for draft-… Luigi Iannone
- Re: [5gangip] New Version Notification for draft-… Luigi Iannone
- Re: [5gangip] New Version Notification for draft-… Dino Farinacci
- Re: [5gangip] New Version Notification for draft-… Saleem Bhatti
- Re: [5gangip] New Version Notification for draft-… Saleem Bhatti
- Re: [5gangip] New Version Notification for draft-… Saleem Bhatti
- Re: [5gangip] New Version Notification for draft-… Tom Herbert
- Re: [5gangip] New Version Notification for draft-… FIGURELLE, TERRY F
- Re: [5gangip] New Version Notification for draft-… Dino Farinacci
- Re: [5gangip] New Version Notification for draft-… FIGURELLE, TERRY F
- Re: [5gangip] New Version Notification for draft-… FIGURELLE, TERRY F
- Re: [5gangip] New Version Notification for draft-… Dino Farinacci
- Re: [5gangip] New Version Notification for draft-… Dino Farinacci
- Re: [5gangip] New Version Notification for draft-… FIGURELLE, TERRY F
- Re: [5gangip] New Version Notification for draft-… Rex Buddenberg
- Re: [5gangip] New Version Notification for draft-… FIGURELLE, TERRY F
- Re: [5gangip] New Version Notification for draft-… Dino Farinacci
- Re: [5gangip] New Version Notification for draft-… Dino Farinacci
- Re: [5gangip] New Version Notification for draft-… Tom Herbert
- Re: [5gangip] New Version Notification for draft-… Saleem Bhatti
- Re: [5gangip] New Version Notification for draft-… Luigi Iannone
- Re: [5gangip] New Version Notification for draft-… Luigi Iannone
- Re: [5gangip] New Version Notification for draft-… Luigi Iannone
- Re: [5gangip] New Version Notification for draft-… Dino Farinacci
- Re: [5gangip] New Version Notification for draft-… Tom Herbert
- Re: [5gangip] New Version Notification for draft-… Dino Farinacci
- Re: [5gangip] New Version Notification for draft-… FIGURELLE, TERRY F
- [5gangip] New Version Notification for draft-xyzy… Behcet Sarikaya
- Re: [5gangip] New Version Notification for draft-… Dirk.von-Hugo
- Re: [5gangip] New Version Notification for draft-… Saleem Bhatti
- Re: [5gangip] New Version Notification for draft-… Luigi Iannone
- Re: [5gangip] New Version Notification for draft-… Saleem Bhatti
- Re: [5gangip] New Version Notification for draft-… Luigi Iannone
- Re: [5gangip] New Version Notification for draft-… Saleem Bhatti
- Re: [5gangip] New Version Notification for draft-… Behcet Sarikaya
- Re: [5gangip] New Version Notification for draft-… Tom Herbert
- Re: [5gangip] New Version Notification for draft-… Saleem Bhatti
- Re: [5gangip] New Version Notification for draft-… Saleem Bhatti
- Re: [5gangip] New Version Notification for draft-… David Allan I
- Re: [5gangip] New Version Notification for draft-… Behcet Sarikaya
- Re: [5gangip] New Version Notification for draft-… Behcet Sarikaya
- Re: [5gangip] New Version Notification for draft-… Saleem Bhatti
- Re: [5gangip] New Version Notification for draft-… Saleem Bhatti
- Re: [5gangip] New Version Notification for draft-… Tom Herbert
- Re: [5gangip] New Version Notification for draft-… Saleem Bhatti
- Re: [5gangip] New Version Notification for draft-… Tom Herbert
- Re: [5gangip] New Version Notification for draft-… Dino Farinacci
- Re: [5gangip] New Version Notification for draft-… Saleem Bhatti
- Re: [5gangip] New Version Notification for draft-… Behcet Sarikaya
- Re: [5gangip] New Version Notification for draft-… Behcet Sarikaya
- Re: [5gangip] New Version Notification for draft-… Dino Farinacci
- Re: [5gangip] New Version Notification for draft-… Tom Herbert
- Re: [5gangip] New Version Notification for draft-… Saleem Bhatti
- Re: [5gangip] New Version Notification for draft-… Behcet Sarikaya
- Re: [5gangip] New Version Notification for draft-… Saleem Bhatti
- Re: [5gangip] New Version Notification for draft-… Behcet Sarikaya