Re: [5gangip] New Version Notification for draft-xyzy-atick-gaps-00.txt
Saleem Bhatti <saleem@st-andrews.ac.uk> Thu, 07 June 2018 11:10 UTC
Return-Path: <saleem@st-andrews.ac.uk>
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 8CD6F1310CF for <5gangip@ietfa.amsl.com>; Thu, 7 Jun 2018 04:10:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=universityofstandrews907.onmicrosoft.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 1x6-hLz_QajC for <5gangip@ietfa.amsl.com>; Thu, 7 Jun 2018 04:10:24 -0700 (PDT)
Received: from mcgraw.st-andrews.ac.uk (mcgraw.st-andrews.ac.uk [138.251.8.95]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0192129C6B for <5gangip@ietf.org>; Thu, 7 Jun 2018 04:10:22 -0700 (PDT)
X-StAndrews-MailScanner-From: saleem@st-andrews.ac.uk
X-StAndrews-MailScanner-ID: w57BAGP5016703
X-StAndrews-MailScanner-Information: Please contact the ISP for more information
Received: from wallace.st-andrews.ac.uk (wallace.st-andrews.ac.uk [138.251.9.23]) by mcgraw.st-andrews.ac.uk (8.14.9/8.14.9/Debian-4~bpo0+uos) with ESMTP id w57BAGP5016703 (version=TLSv1/SSLv3 cipher=ADH-AES256-SHA bits=256 verify=NOT); Thu, 7 Jun 2018 11:10:17 GMT
X-StAndrews-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-1.889, required 5, autolearn=not spam, BAYES_00 -1.90, HTML_MESSAGE 0.00, T_DKIM_INVALID 0.01), not spam (whitelisted), SpamAssassin (not cached, score=-2.289, required 5, autolearn=not spam, HTML_MESSAGE 0.00, RCVD_IN_DNSWL_MED -2.30, T_DKIM_INVALID 0.01)
X-StAndrews-MailScanner: No virus detected, No virus detected
Received: from unimail.st-andrews.ac.uk (exch13-srv01.st-andrews.ac.uk [138.251.8.22]) by wallace.st-andrews.ac.uk (8.14.9/8.14.9/Debian-4~bpo0+uos) with ESMTP id w57BA54J031309 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 7 Jun 2018 11:10:06 GMT
Received: from exch13-srv03.st-andrews.ac.uk (138.251.9.20) by exch13-srv01.st-andrews.ac.uk (138.251.8.22) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 7 Jun 2018 12:10:05 +0100
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (213.199.154.246) by exch13-srv03.st-andrews.ac.uk (138.251.9.20) with Microsoft SMTP Server (TLS) id 15.0.1210.3 via Frontend Transport; Thu, 7 Jun 2018 12:10:05 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=UniversityofStAndrews907.onmicrosoft.com; s=selector1-standrews-ac-uk0e; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=lGd4pwtI7Au/hYPdzraaugjemCTleoth7J1sXhJCT0o=; b=NNlz5zMzNbYUzkL+GPhQn6d6IUYEq7udNuwxBTO2vXjobssAg4OgO6xIpYb/EI/ifRToFt/9GciqS4BOaPc+L2mPi8S9+0KwjoRENo4CnFU5X9ZEtQStrVAUBbdC5trDdw7yUcAQPt9Mxk37K19eHwveY0WygIcSOJU0chmQxq4=
Received: from VI1PR0602MB3615.eurprd06.prod.outlook.com (52.134.2.146) by VI1PR0602MB3422.eurprd06.prod.outlook.com (52.134.4.159) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.841.13; Thu, 7 Jun 2018 11:10:02 +0000
Received: from VI1PR0602MB3615.eurprd06.prod.outlook.com ([fe80::c870:d058:5b41:40ff]) by VI1PR0602MB3615.eurprd06.prod.outlook.com ([fe80::c870:d058:5b41:40ff%3]) with mapi id 15.20.0820.015; Thu, 7 Jun 2018 11:10:02 +0000
From: Saleem Bhatti <saleem@st-andrews.ac.uk>
To: Luigi Iannone <ggx@gigix.net>
CC: 5GANGIP <5gangip@ietf.org>
Thread-Topic: [5gangip] New Version Notification for draft-xyzy-atick-gaps-00.txt
Thread-Index: AQHT9DfNeemqhTJbEU2NM7JdoGcy9KRFZtqAgAD/5ICAABlegIAAJ50AgAGyeQCAABeoAIAACaKAgAAmU4CADANUgIAAEpQA
Date: Thu, 07 Jun 2018 11:10:02 +0000
Message-ID: <95EF1DB1-A51B-4638-B7E1-FD859ACB6BC8@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> <CAC8QAcf48-RPLz5E+tXt1smJPeWQ=DPtFvJJ=UNJ2pi3zcOOhw@mail.gmail.com> <76ED0791-7FB1-4300-8641-473BCB4B409A@gigix.net>
In-Reply-To: <76ED0791-7FB1-4300-8641-473BCB4B409A@gigix.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=saleem@st-andrews.ac.uk;
x-originating-ip: [138.251.195.76]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR0602MB3422; 7:vkBUuW4SDNuPaZ4YR9YFydGasTxOTJLqFz+LVGq8aANCocg+puUHQ6xiZ0r1fLyQ7BwCRTrfKYouJp8ISaZmf4xp+j81gdeSpUr8Pnr0nDGFcDWJu+89DtOnkcLxhbmg/6hPQkH6Un1RYhv5YnX+RNThOk1fD+ho7SyfZfe9jm9HCwPgATMQDQ5hmkVvtZ70OammKulln3B7/2z7lTB2po4D2vG6JJ1xZH4Hz0QTBZ3biTyeqcIAN3S9+1PWnyfI
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:(36968037445663); BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989080)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(8990040)(2017052603328)(7153060)(7193020); SRVR:VI1PR0602MB3422;
x-ms-traffictypediagnostic: VI1PR0602MB3422:
x-microsoft-antispam-prvs: <VI1PR0602MB3422D2AC1899C05D026D9001A7640@VI1PR0602MB3422.eurprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105)(85827821059158)(36968037445663)(101264311250101)(213716511872227);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3002001)(3231254)(944501410)(52105095)(10201501046)(93006095)(93001095)(149027)(150027)(6041310)(20161123564045)(20161123558120)(20161123560045)(20161123562045)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011)(7699016); SRVR:VI1PR0602MB3422; BCL:0; PCL:0; RULEID:; SRVR:VI1PR0602MB3422;
x-forefront-prvs: 06968FD8C4
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(39860400002)(346002)(366004)(39380400002)(396003)(51914003)(53754006)(199004)(189003)(53936002)(15650500001)(3846002)(59450400001)(186003)(2906002)(6116002)(229853002)(3280700002)(3660700001)(966005)(476003)(2616005)(26005)(446003)(5250100002)(53546011)(93886005)(106356001)(68736007)(478600001)(105586002)(7736002)(486006)(102836004)(6506007)(33656002)(6486002)(76176011)(10710500007)(99286004)(81156014)(81166006)(6436002)(786003)(316002)(86362001)(8936002)(14454004)(11346002)(6246003)(66066001)(8676002)(5660300001)(82746002)(97736004)(36756003)(25786009)(2900100001)(4326008)(606006)(6512007)(6916009)(236005)(6306002)(54896002)(2420400007)(7110500001)(74482002)(83716003); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR0602MB3422; H:VI1PR0602MB3615.eurprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:3; MX:3;
received-spf: None (protection.outlook.com: st-andrews.ac.uk does not designate permitted sender hosts)
x-microsoft-antispam-message-info: DBy7tKvrWG2h2iBtKbO8WRbxxvFlSQYa50PV4E6HrVwp3nseZLrfmGDsVhLjmaT4BBhRHbDhG4doy96fQtco/g4a/bLWo8ZxJfdi1TuU+seNQ95EMM1hqv7j+OegTe2xUtuHAB5HeVQc7jzWPoiSfqakDEBuIK0u9llQFgWaa915RWy8gOacpFHaE5SpHLvy
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_95EF1DB1A51B4638B7E1FD859ACB6BC8standrewsacuk_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 76d584a2-d3c6-40d9-9b72-08d5cc673729
X-MS-Exchange-CrossTenant-Network-Message-Id: 76d584a2-d3c6-40d9-9b72-08d5cc673729
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Jun 2018 11:10:02.0558 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f85626cb-0da8-49d3-aa58-64ef678ef01a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0602MB3422
Archived-At: <https://mailarchive.ietf.org/arch/msg/5gangip/qCAf-EHDPbRJ_No9Cfo9ewOSg6c>
Subject: Re: [5gangip] New Version Notification for draft-xyzy-atick-gaps-00.txt
X-BeenThere: 5gangip@ietf.org
X-Mailman-Version: 2.1.26
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: Thu, 07 Jun 2018 11:10:30 -0000
Luigi; On 07 Jun 2018, at 11:03, Luigi Iannone <ggx@gigix.net<mailto:ggx@gigix.net>> wrote: On 30 May 2018, at 20:36, Behcet Sarikaya <sarikaya2012@gmail.com<mailto:sarikaya2012@gmail.com>> wrote: On Wed, May 30, 2018 at 11:19 AM, Saleem Bhatti <saleem@st-andrews.ac.uk<mailto:saleem@st-andrews.ac.uk>> wrote: Tom; > On 30 May 2018, at 16:44, Tom Herbert <tom@herbertland.com<mailto: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. So then it is no longer ILNP. +1 Either you have both side speaking ILNPv6 or you are “stuck” with IPv6 pure and simple. Correct. ILNP is a "host-based" (end-system) solution and not a "network-based" solution. If the end-system is not updated to support ILNP, then ILNP cannot be used. I was wondering: assuming that you do not use DNS to contact a node, how do you know it supports ILNPv6? An IPv6 packet containing a Nonce Header (RFC6744) is sent. If the recipient does not respond with a Nonce Header, then it is assumed that ILNPv6 is not supported. The process is described in Section 10.6 of RFC6741. Cheers, --/Saleem Ciao L. Regards, Behcet Cheers, --/Saleem > > Tom > > On Wed, May 30, 2018 at 7:20 AM, Behcet Sarikaya <sarikaya2012@gmail.com<mailto: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<mailto:ggx@gigix.net>> wrote: >>> >>> Hi Saleem, >>> >>> On 29 May 2018, at 12:03, Saleem Bhatti <saleem@st-andrews.ac.uk<mailto: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<mailto:ggx@gigix.net>> wrote: >>> >>> Hi, >>> >>> >>> On 28 May 2018, at 19:16, Saleem Bhatti <saleem@st-andrews.ac.uk<mailto: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<mailto: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<http://tools.ietf.org/>. >>> >>> The IETF Secretariat >>> >>> >>> _______________________________________________ >>> 5gangip mailing list >>> 5gangip@ietf.org<mailto:5gangip@ietf.org> >>> https://www.ietf.org/mailman/listinfo/5gangip >>> >>> >>> _______________________________________________ >>> 5gangip mailing list >>> 5gangip@ietf.org<mailto:5gangip@ietf.org> >>> https://www.ietf.org/mailman/listinfo/5gangip >>> >>> >>> >>> _______________________________________________ >>> 5gangip mailing list >>> 5gangip@ietf.org<mailto:5gangip@ietf.org> >>> https://www.ietf.org/mailman/listinfo/5gangip >>> >> >> >> _______________________________________________ >> 5gangip mailing list >> 5gangip@ietf.org<mailto:5gangip@ietf.org> >> https://www.ietf.org/mailman/listinfo/5gangip >> > > _______________________________________________ > 5gangip mailing list > 5gangip@ietf.org<mailto: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