Re: [CDNi] [E] Re: next steps with draft-ietf-cdni-request-routing-extensions-03.txt
sanjay.mishra@verizon.com Thu, 15 August 2019 02:53 UTC
Return-Path: <sanjay.mishra@verizon.com>
X-Original-To: cdni@ietfa.amsl.com
Delivered-To: cdni@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B313E120816 for <cdni@ietfa.amsl.com>; Wed, 14 Aug 2019 19:53:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=verizon.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 BCZOKnOOFhL0 for <cdni@ietfa.amsl.com>; Wed, 14 Aug 2019 19:53:40 -0700 (PDT)
Received: from smtpout2-tdc.verizon.com (smtpout2-tdc.verizon.com [137.188.104.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67A81120122 for <cdni@ietf.org>; Wed, 14 Aug 2019 19:53:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1565837620; x=1597373620; h=to:cc:subject:date:message-id:references:in-reply-to: mime-version:from; bh=sk1VXsO8Uz7tbdNJ5xMAUUPe7Sun68p+TWditBnyKRs=; b=dIxVhkvPoXR+mXM4MGaLBv6vkdlAro6TtBuUIuqzFhn7gSmEM1YWyfGY MkG9imbBWLQHByESjMPMsqHh2L+F53ayR+Htr3rUUwk14p5QVH5Jp1DEO f0bptLYG5WOA2aBBCKCk2bbBqWGckigbEpu3GJfJzlI+1DxMuzpRE0M3w A=;
From: sanjay.mishra@verizon.com
Received: from tbwexch03apd.uswin.ad.vzwcorp.com ([153.114.162.27]) by smtpout2-tdc.verizon.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA384; 15 Aug 2019 02:53:38 +0000
Received: from tbwexch02apd.uswin.ad.vzwcorp.com (153.114.162.26) by tbwexch03apd.uswin.ad.vzwcorp.com (153.114.162.27) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 14 Aug 2019 22:53:37 -0400
Received: from tbwexch02apd.uswin.ad.vzwcorp.com ([153.114.162.26]) by tbwexch02apd.uswin.ad.vzwcorp.com ([153.114.162.26]) with mapi id 15.00.1473.003; Wed, 14 Aug 2019 22:53:37 -0400
To: Kevin Ma <kevin.j.ma.ietf@gmail.com>, "Ori Finkelman (IETF)" <ori.finkelman.ietf@gmail.com>
CC: "cdni@ietf.org" <cdni@ietf.org>
Thread-Topic: [E] Re: [CDNi] next steps with draft-ietf-cdni-request-routing-extensions-03.txt
Thread-Index: AdUvRn+MBOCZrqgdTvSGRrR+KatoQwSvPl4AAAf3XwAC4ObEgAAjOIsAAAIlG4AAAFGDAAAam1IAARJXHIAACMIJEA==
Date: Thu, 15 Aug 2019 02:53:37 +0000
Message-ID: <6bdbdeea34d3411ca3597bb2dc941a82@tbwexch02apd.uswin.ad.vzwcorp.com>
References: <bb476a3ad2934dd6a8d6db4f2fc45202@tbwexch02apd.uswin.ad.vzwcorp.com> <CAMrHYE3yP+CKrPAFgfegt=svuKnK1rpy9d1=EkMVNw54_VA2Vw@mail.gmail.com> <CAM8emGXwySixUVXZfhDhVYnXuo0Ud==+HAYRsmKQnDTUMWWU+w@mail.gmail.com> <CAMrHYE26yNg9-_jVqdn2X+jp2XU3wZirbCYWZLtAi_RP_vYUXQ@mail.gmail.com> <CAM8emGXUxbzj4dEi=QG5Gv0w1SZaWsNMFhoC=B81Ek+GzOc4HA@mail.gmail.com> <5E60A6DC-8273-4548-93DC-DCFAFE9657D1@gmail.com> <CAM8emGX26QwCaauEUhg8N_xwQ_z9j8mw6koUtcU0gW1YMTahhw@mail.gmail.com> <CAM8emGWkwHGAwCBu0kgrgtA+iOpJJbFOgGhGOdCwob0g1up-TA@mail.gmail.com> <CAMrHYE1HFExEPMhigbP=Th-N0k2TdJkVZifUoNSKqmLkGWW1rA@mail.gmail.com>
In-Reply-To: <CAMrHYE1HFExEPMhigbP=Th-N0k2TdJkVZifUoNSKqmLkGWW1rA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.144.60.250]
Content-Type: multipart/alternative; boundary="_000_6bdbdeea34d3411ca3597bb2dc941a82tbwexch02apduswinadvzwc_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/cdni/mgxT8jXq5Ys0KkpTvjd2OdHBwKM>
Subject: Re: [CDNi] [E] Re: next steps with draft-ietf-cdni-request-routing-extensions-03.txt
X-BeenThere: cdni@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" <cdni.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cdni>, <mailto:cdni-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cdni/>
List-Post: <mailto:cdni@ietf.org>
List-Help: <mailto:cdni-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cdni>, <mailto:cdni-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2019 02:53:44 -0000
Thank you Kevin, Your guidance is truly appreciated. Thanks Sanjay From: Kevin Ma [mailto:kevin.j.ma.ietf@gmail.com] Sent: Wednesday, August 14, 2019 2:42 PM To: Ori Finkelman (IETF) <ori.finkelman.ietf@gmail.com> Cc: Mishra, Sanjay <sanjay.mishra@one.verizon.com>; cdni@ietf.org Subject: [E] Re: [CDNi] next steps with draft-ietf-cdni-request-routing-extensions-03.txt Hi Ori, I completed the shepherd writeup and have submitted the draft to the IESG. thanx! -- Kevin J. Ma On Fri, Aug 9, 2019 at 3:46 AM Ori Finkelman (IETF) <ori.finkelman.ietf@gmail.com<mailto:ori.finkelman.ietf@gmail.com>> wrote: Fixed, submitted version 05. Thanks, Ori On Thu, Aug 8, 2019 at 10:04 PM Ori Finkelman (IETF) <ori.finkelman.ietf@gmail.com<mailto:ori.finkelman.ietf@gmail.com>> wrote: ok, will change accordingly and resubmit. Thanks, Ori On Thu, Aug 8, 2019 at 9:55 PM Kevin J. Ma <kevin.j.ma.ietf@gmail.com<mailto:kevin.j.ma.ietf@gmail.com>> wrote: Hi Ori, Understood. I think for the purposes of this document .ucdn.example.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__ucdn.example.com&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=7RnD30s0nL3LGL9UMGnzIz3UgcE8uYKQalU1oeRKmu4&s=xOW8VzCEPYpEyal_TWQVWU_psI8zysE6lS84RZc3tTo&e=> and .dcdn.example.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__dcdn.example.com&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=7RnD30s0nL3LGL9UMGnzIz3UgcE8uYKQalU1oeRKmu4&s=yzVB3b8XXeZy6z_l2Gu5D4Df-bvCpcNhdfkPimDxoBk&e=> should be ok and make things simpler with not having to explain nits. thanx! -- Kevin J. Ma Sent from my iPhone On Aug 8, 2019, at 1:54 PM, Ori Finkelman (IETF) <ori.finkelman.ietf@gmail.com<mailto:ori.finkelman.ietf@gmail.com>> wrote: Hi Kevin, I am aware of that, the thing is that for this example we need two separate domains, one of the uCDN and the other of the dCDN, putting them both under the same domain example.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__example.com&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=7RnD30s0nL3LGL9UMGnzIz3UgcE8uYKQalU1oeRKmu4&s=8J4L7w2B9q1aF2wj_lNcGT-ysoN9xr2GpuWGqfHnnOo&e=> defeats the purpose. Maybe we can put them as ucdn.example.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__ucdn.example.com&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=7RnD30s0nL3LGL9UMGnzIz3UgcE8uYKQalU1oeRKmu4&s=xOW8VzCEPYpEyal_TWQVWU_psI8zysE6lS84RZc3tTo&e=> and dcdn.example.net<https://urldefense.proofpoint.com/v2/url?u=http-3A__dcdn.example.net&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=7RnD30s0nL3LGL9UMGnzIz3UgcE8uYKQalU1oeRKmu4&s=fLbp3Gr3Wog3PzTD2XsPOwpduoU5pulN6gym9qCzkRI&e=> ? Thanks, Ori On Thu, Aug 8, 2019 at 4:06 AM Kevin Ma <kevin.j.ma.ietf@gmail.com<mailto:kevin.j.ma.ietf@gmail.com>> wrote: Hi Ori, IDnits notes one issue: non-RFC2606-compliant FQDNs https://www6.ietf.org/tools/idnits?url=https://www.ietf.org/archive/id/draft-ietf-cdni-request-routing-extensions-04.txt<https://urldefense.proofpoint.com/v2/url?u=https-3A__www6.ietf.org_tools_idnits-3Furl-3Dhttps-3A__www.ietf.org_archive_id_draft-2Dietf-2Dcdni-2Drequest-2Drouting-2Dextensions-2D04.txt&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=7RnD30s0nL3LGL9UMGnzIz3UgcE8uYKQalU1oeRKmu4&s=ljF2rIJsQpiRbrPt6w7fXLwg2Bi3lmBgZivXvgFnt2A&e=> I'm guessing it's: service123.ucdn.example.dcdn.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__service123.ucdn.example.dcdn.com&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=7RnD30s0nL3LGL9UMGnzIz3UgcE8uYKQalU1oeRKmu4&s=W7An7qy2pi9IrndehUuMI5FgmbUmXvy3-yfWnCXzGms&e=>, which doesn't end in .example.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__example.com&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=7RnD30s0nL3LGL9UMGnzIz3UgcE8uYKQalU1oeRKmu4&s=8J4L7w2B9q1aF2wj_lNcGT-ysoN9xr2GpuWGqfHnnOo&e=> ? Do you think we can fix that? thanx! -- Kevin J. Ma On Wed, Jul 24, 2019 at 5:26 AM Ori Finkelman (IETF) <ori.finkelman.ietf@gmail.com<mailto:ori.finkelman.ietf@gmail.com>> wrote: Thanks Kevin. I will wait for group comments and will publish an updated version with the comments you have sent here. Best regards, Ori On Wed, Jul 24, 2019 at 8:38 AM Kevin Ma <kevin.j.ma.ietf@gmail.com<mailto:kevin.j.ma.ietf@gmail.com>> wrote: Hi Sanjay, The updates look good. Two final comments: - section 2.1: "non empty" -> "non-empty" - sections 6/7: if there are no acknowledgements or contributors, those two sections can just be removed. Those comments notwithstanding, I think we can start the WGLC. thanx.. -- Kevin J. Ma On Sun, Jun 30, 2019 at 9:20 AM <sanjay..mishra=40verizon.com@dmarc.ietf.org<mailto:40verizon.com@dmarc.ietf.org>> wrote: Since there is no CDNI meeting on the agenda, I wanted to ask if chairs have any additional questions or questions in the mailing list towards advancing draft-ietf-cdni-request-routing-extensions-03.txt to WGLC? Thanks Sanjay _______________________________________________ CDNi mailing list CDNi@ietf.org<mailto:CDNi@ietf.org> https://www.ietf.org/mailman/listinfo/cdni<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_cdni&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=7RnD30s0nL3LGL9UMGnzIz3UgcE8uYKQalU1oeRKmu4&s=2a92GQd1Yp0D8zEiGJw6oIAn6IP5whT1qo9lwyyRr8E&e=> _______________________________________________ CDNi mailing list CDNi@ietf.org<mailto:CDNi@ietf.org> https://www.ietf.org/mailman/listinfo/cdni<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_cdni&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=7RnD30s0nL3LGL9UMGnzIz3UgcE8uYKQalU1oeRKmu4&s=2a92GQd1Yp0D8zEiGJw6oIAn6IP5whT1qo9lwyyRr8E&e=>
- [CDNi] next steps with draft-ietf-cdni-request-ro… sanjay.mishra
- Re: [CDNi] next steps with draft-ietf-cdni-reques… Kevin Ma
- Re: [CDNi] next steps with draft-ietf-cdni-reques… Ori Finkelman (IETF)
- Re: [CDNi] [E] Re: next steps with draft-ietf-cdn… sanjay.mishra
- Re: [CDNi] next steps with draft-ietf-cdni-reques… Kevin Ma
- Re: [CDNi] next steps with draft-ietf-cdni-reques… Ori Finkelman (IETF)
- Re: [CDNi] next steps with draft-ietf-cdni-reques… Kevin J. Ma
- Re: [CDNi] next steps with draft-ietf-cdni-reques… Ori Finkelman (IETF)
- Re: [CDNi] next steps with draft-ietf-cdni-reques… Ori Finkelman (IETF)
- Re: [CDNi] next steps with draft-ietf-cdni-reques… Kevin Ma
- Re: [CDNi] next steps with draft-ietf-cdni-reques… Ori Finkelman (IETF)
- Re: [CDNi] [E] Re: next steps with draft-ietf-cdn… sanjay.mishra