Re: [CDNi] I-D Action: draft-ietf-cdni-request-routing-extensions-02.txt
"Ori Finkelman (IETF)" <ori.finkelman.ietf@gmail.com> Sun, 05 May 2019 08:50 UTC
Return-Path: <orifinkelman@gmail.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 5F95612003F for <cdni@ietfa.amsl.com>; Sun, 5 May 2019 01:50:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 qVL77OddVF-r for <cdni@ietfa.amsl.com>; Sun, 5 May 2019 01:50:13 -0700 (PDT)
Received: from mail-vs1-xe34.google.com (mail-vs1-xe34.google.com [IPv6:2607:f8b0:4864:20::e34]) (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 6F5C0120021 for <cdni@ietf.org>; Sun, 5 May 2019 01:50:13 -0700 (PDT)
Received: by mail-vs1-xe34.google.com with SMTP id g187so6315626vsc.8 for <cdni@ietf.org>; Sun, 05 May 2019 01:50:13 -0700 (PDT)
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=FSWQaNgdn9oY8HwxYNaiC4xLnnm1Cp0SljmFsNt2Luk=; b=NE3zchApA5l1L7EYybsQ5AcASSBQvfKbi+KLvT3SvvJd6mGmiqLU+IlVaxRmP+5C4x 3wSKrb4pbui2zEkla1rXbGVtWM7VAcYVeGZ51/pVWasg489y2hR5ZH4tIn95vCAxlxmt HPW5D3qkOz/53bapyb18uTNzYhGUGA1T0pPmsdOVONoTgViGMjH7zDiplh4uUG2te2xW 3KCsgeoZBdGK/MU02X2o48YVMsEUZCTC7sM+DaeMhopBc/wSsDYPXfZbqVJcOfvqwwTP YKAIW9Bd5nc/NzNRDD2B6zRLT/nm03GoKNJ46yfQU0MrLudpte4ZrCS0M3DvcZWoXJez Q/Lw==
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=FSWQaNgdn9oY8HwxYNaiC4xLnnm1Cp0SljmFsNt2Luk=; b=BJcawC6b/Fz4/4p8NEM44W2JpnooSqP67mwvdJmD7BIsH5hEj5Koyficg8ZtG48YPc 6bYNRRJv43Ehn//uBY90dKoHpLtkgn5ve4Yrc39jHgiPIRgT9Pe9GXNFVZahhaE2dbrM rf6nrmCOdnzO0H7Zq9QKdSbfrbhS+jyKUHYIGU3zokvFu7ZNSadZqw30DJPBsdBzFBo6 bqQhJZYZmprGKJT8qKwdKhPoxs46RfG32h++ibx5J/OO9yDxLNWMyG7TpvB97o/UjyhH BnuqXPpU/ss2hegomglFdnB7l6ZRrnobkmuceukZ5dQ7IXx8FLJ7LUad7tlVkMrvVeeA cW3A==
X-Gm-Message-State: APjAAAUBfftpU6GQ8lbPMWnUZOPF8/usPIRBcN6bgmq8OoHxUPFlHBFu PpkJZuAr7wq16znInO2VJ9N//YZxPXleRjglRGY=
X-Google-Smtp-Source: APXvYqype0IqzZSJwSPzVRulehKAPwoDBWUUBg8bo45HLygabbk11ARfs3qlNPkAZhKf/C748dzOuHHD+F1Wn3yEG+8=
X-Received: by 2002:a67:c885:: with SMTP id v5mr10250284vsk.49.1557046212026; Sun, 05 May 2019 01:50:12 -0700 (PDT)
MIME-Version: 1.0
References: <155403318275.12273.17586391042919500029@ietfa.amsl.com> <CAMrHYE3DcF-H+PojXFAy+3_rfEVCNQWK=eCiOVywoGnW4CHAcw@mail.gmail.com>
In-Reply-To: <CAMrHYE3DcF-H+PojXFAy+3_rfEVCNQWK=eCiOVywoGnW4CHAcw@mail.gmail.com>
From: "Ori Finkelman (IETF)" <ori.finkelman.ietf@gmail.com>
Date: Sun, 05 May 2019 11:49:55 +0300
Message-ID: <CAM8emGWJeX-u9ZkuQUd1H8_tJKC3vuJkFogi99RFnk9sR2AbhQ@mail.gmail.com>
To: Kevin Ma <kevin.j.ma.ietf@gmail.com>
Cc: "<cdni@ietf.org>" <cdni@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005def0705882012fe"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cdni/F_VP_ihcY_IBUIyiVx6bhgN79LU>
Subject: Re: [CDNi] I-D Action: draft-ietf-cdni-request-routing-extensions-02.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: Sun, 05 May 2019 11:50:42 -0000
Thanks Kevin for the review and comments. I'll fix the draft accordingly and will wait for others to comment before submitting a fixed version. Best regards, Ori On Sun, May 5, 2019 at 7:25 AM Kevin Ma <kevin.j.ma.ietf@gmail.com> wrote: > Hi All, > > (as chair) I added a milestone after the last IETF to get this draft > submitted by June. I believe the contents are uncontroversial (though > please speak up if you disagree), and the proposed metadata and > capabilities submitted via WG draft are inline with the extensibility model > we sought to achieve for the MI and FCI interfaces. > > To that end, as is our custom, I've done a pre-shepherd review. I > encourage everyone to also give it a read and speak up if you have any > thoughts or concerns, as we try to move it forward. > > Ori/Sanjay: > > Please find my comments below. > > thanx! > > -- Kevin J. Ma > > - section 2: > - I would add a sentence before the property definitions (and possibly > make it a subsection): "The Redirect Target capability object consists of > the following three properties: > - I would make the json example its own section, referenced from section > 4.1.1 > - I would add the http-target json from section 2.2 to this full example. > - nits: > ", for example" -> ", for example," or ", e.g.," > ", for example" -> ", for example," or ", e.g.," > ", or due to network problems" -> " or network problems" > "Due to this variable" -> "Given the variable" > ", and a more dynamic," -> ". A more dynamic" > "may be using third party DNS resolver" -> "may be using a third party > DNS resolver" > "or it can be set" -> "or can be set" > "Redirect Target Capability" -> "Redirect Target capability" > "When dCDN is" -> "When a dCDN is" > "one of these uCDN hosts" -> "one of those uCDN hosts" > "DNS routers take routing decisions" -> "DNS routers make routing > decisions" > "URI to be used as a value of" -> "URI to be used as the value for" > "Example of Redirect Target Capability object" -> "The following is an > example of a Redirect Target capability object serialization" > "Target address for DNS A record" -> "Target address for a DNS A > record" > "No. but" -> "No, but" > "Target URI for HTTP redirect" -> "Target URI for a HTTP redirect" > > - section 2.1: > - nits: > "gives the instructions to construct the target address for the DNS > response for delegation" -> "gives the target address for the DNS response > to delegate" > > - section 2.2: > - nits: > "gives the instructions to construct the target Location URI for http > redirection" -> "gives the necessary information to construct the target > Location URI for HTTP redirection." > ", i.e." -> ", i.e.," > ", i.e." -> ", i.e.," > "In case this flag is true" -> "If set to true" > "In case this flag is true" -> "If set to true" > > - section 3: > - I would add a sentence before the property definition (and possibly > make it a subsection): "The MI.FallbackTarget Metadata object consists of > the following single property: > - I would make the json example its own section, referenced from section > 4.1.2 > - In the case of DNS redirect, would it be acceptable for the uCDN to > advertise a host with a port, and say the dCDN must ignore/drop the port? > or should there be two properties, one for DNS and one for HTTP, similar to > Redirect Target? > - nits: > "requires that the uCDN should provide" -> "requires that the uCDN > provide a" > "to the dCDN to be used" -> "to the dCDN, to be used" > "differnet than the original address at the uCDN" -> "different from > the original uCDN address" > "caches, or a client located outside" -> "caches or outside" > "DNS redirection mode" -> "DNS redirection" > "dCDN path-prefix and the uCDN host name" -> "dCDN path-prefix and/or > the uCDN hostname" > > - section 4.1: > "IANA CDNI Payload Type registry" -> "IANA \"CDNI Payload Types\" > registry" > > - section 5: > - I think you also need to add a "Privacy" section? > > > On Sun, Mar 31, 2019 at 7:53 AM <internet-drafts@ietf.org> wrote: > >> >> A New Internet-Draft is available from the on-line Internet-Drafts >> directories. >> This draft is a work item of the Content Delivery Networks >> Interconnection WG of the IETF. >> >> Title : CDNI Request Routing Extensions >> Authors : Ori Finkelman >> Sanjay Mishra >> Filename : >> draft-ietf-cdni-request-routing-extensions-02.txt >> Pages : 11 >> Date : 2019-03-31 >> >> Abstract: >> The Open Caching working group of the Streaming Video Alliance is >> focused on the delegation of video delivery requests from commercial >> CDNs to a caching layer at the ISP. In that aspect, Open Caching is >> a specific use case of CDNI, where the commercial CDN is the upstream >> CDN (uCDN) and the ISP caching layer is the downstream CDN (dCDN). >> The extensions specified in this document to the CDNI Metadata and >> FCI interfaces are derived from requirements raised by Open Caching >> but are applicable to CDNI use cases in general. >> >> >> >> The IETF datatracker status page for this draft is: >> >> https://datatracker.ietf..org/doc/draft-ietf-cdni-request-routing-extensions/ >> <https://datatracker.ietf.org/doc/draft-ietf-cdni-request-routing-extensions/> >> >> There are also htmlized versions available at: >> https://tools.ietf.org/html/draft-ietf-cdni-request-routing-extensions-02 >> >> https://datatracker.ietf.org/doc/html/draft-ietf-cdni-request-routing-extensions-02 >> >> A diff from the previous version is available at: >> >> https://www.ietf.org/rfcdiff?url2=draft-ietf-cdni-request-routing-extensions-02 >> >> >> 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. >> >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >> >> _______________________________________________ >> CDNi mailing list >> CDNi@ietf.org >> https://www.ietf.org/mailman/listinfo/cdni >> > _______________________________________________ > CDNi mailing list > CDNi@ietf.org > https://www.ietf.org/mailman/listinfo/cdni >
- [CDNi] I-D Action: draft-ietf-cdni-request-routin… internet-drafts
- Re: [CDNi] I-D Action: draft-ietf-cdni-request-ro… Kevin Ma
- Re: [CDNi] I-D Action: draft-ietf-cdni-request-ro… Ori Finkelman (IETF)