Re: [CDNi] I-D Action: draft-ietf-cdni-media-type-01.txt
"Ali C. Begen" <acbegen@gmail.com> Wed, 30 September 2015 18:04 UTC
Return-Path: <acbegen@gmail.com>
X-Original-To: cdni@ietfa.amsl.com
Delivered-To: cdni@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 703DE1A8848 for <cdni@ietfa.amsl.com>; Wed, 30 Sep 2015 11:04:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 iNXFexzcyrqI for <cdni@ietfa.amsl.com>; Wed, 30 Sep 2015 11:04:21 -0700 (PDT)
Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (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 6E8FD1A8847 for <cdni@ietf.org>; Wed, 30 Sep 2015 11:04:21 -0700 (PDT)
Received: by oiww128 with SMTP id w128so27017044oiw.2 for <cdni@ietf.org>; Wed, 30 Sep 2015 11:04:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=FRMenSI1elt+g2DPjzdC6c4VFxOixcc/csL4PDUv0bg=; b=cPc6/PSRx2O0Pa2cApUsnwvBjO0fHYPIJ7HUNn6rrNjOJBrN3owJuDscSaggUI/l6y 3Bx7htRqIyVJ7N0k8Hf6JGrf9FtvFnc+iqh5fuvRk8LNEEBo4CIwYgJHnciYYoMMyI34 nRB66MyIp64F+jtaXL1LVT10+5tG1TNV/DulmZCjCJE1OxUHTbZddUDQsuSdkx9A5HcQ T61C0L9p8Cfckw4Lc/D4wYvsj/ELaK4rIp6QrVawA2HvunD5kw/pRT8pVuS0j+vZwHK5 VHevnRNfkKFqFpdgXunot587u3SEADKUIEzcphw+JUhfn56jIrJOY7Wm7gbiS/tRpDnM OSwQ==
MIME-Version: 1.0
X-Received: by 10.202.98.2 with SMTP id w2mr3084054oib.83.1443636260731; Wed, 30 Sep 2015 11:04:20 -0700 (PDT)
Received: by 10.202.213.83 with HTTP; Wed, 30 Sep 2015 11:04:20 -0700 (PDT)
In-Reply-To: <A419F67F880AB2468214E154CB8A556206B5595B@eusaamb103.ericsson.se>
References: <20150929145422.21119.20578.idtracker@ietfa.amsl.com> <A419F67F880AB2468214E154CB8A556206B5296B@eusaamb103.ericsson.se> <D2317868.32D15%d.malas@cablelabs.com> <A419F67F880AB2468214E154CB8A556206B5595B@eusaamb103.ericsson.se>
Date: Wed, 30 Sep 2015 21:04:20 +0300
Message-ID: <CAG371norBZ0A_UnjpLNq5JmqOsURrZ6YunYzAwvqeEOLVLUX0w@mail.gmail.com>
From: "Ali C. Begen" <acbegen@gmail.com>
To: Kevin Ma J <kevin.j.ma@ericsson.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/cdni/h-lRvmSkwTgbBc1CvCTOYcGb9fc>
Cc: "cdni@ietf.org" <cdni@ietf.org>
Subject: Re: [CDNi] I-D Action: draft-ietf-cdni-media-type-01.txt
X-BeenThere: cdni@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 30 Sep 2015 18:04:23 -0000
I think you might say "encoded data/message" instead of "JSON encoded data/message" On Wed, Sep 30, 2015 at 9:01 PM, Kevin Ma J <kevin.j.ma@ericsson.com> wrote: > Hi Daryl, > > We can change it. I think the encoding considerations text reads as informational: > > "The CDNI protocol suite includes interfaces with JSON encoded messages" > > Doesn't say it has to be JSON, just says that some are. I think the "8bit or binary" still works; pretty much covers everything. But we can remove "JSON encoded"; I don't think it hurts. > > In the security considerations case, the text could be overly restrictive in scope: > > "CDNI interfaces that return JSON encoded data may be (mis)interpreted" > > Really, any message may be misinterpreted, so I don't see any harm in removing "JSON encoded", though I don't read the text as placing any dependency on JSON. > > I'm open to any other opinions from the WG, but if no one dissents, I will remove "JSON encoded" from those two sections. > > thanx! > > -- Kevin J. Ma > >> -----Original Message----- >> From: Daryl Malas [mailto:D.Malas@cablelabs.com] >> Sent: Wednesday, September 30, 2015 1:34 PM >> To: Kevin Ma J; cdni@ietf.org >> Subject: Re: [CDNi] I-D Action: draft-ietf-cdni-media-type-01.txt >> >> Kevin, >> >> I have a question regarding the media-type draft. I recognize that you >> use JSON as an example in the introduction, which is fine. The current >> preferred implementations of the interfaces will likely use JSON. As I >> think through this, however, we should expect JSON to become obsolete in >> the next 5 years (or so); yet, the media types will still be relevant to >> some new language. In the ³encoding considerations² and the ³Security >> considerations,² should we remove specific references to using JSON? I¹m >> concerned we may somehow imply a dependency on JSON for CDNI in the >> future, which I think we would want to avoid. >> >> What are your thoughts? >> >> Thanks, >> >> Daryl >> >> On 9/29/15, 8:55 AM, "CDNi on behalf of Kevin Ma J" <cdni-bounces@ietf.org >> on behalf of kevin.j.ma@ericsson.com> wrote: >> >> >updated to address Francois's nits. >> > >> >> -----Original Message----- >> >> From: CDNi [mailto:cdni-bounces@ietf.org] On Behalf Of internet- >> >> drafts@ietf.org >> >> Sent: Tuesday, September 29, 2015 10:54 AM >> >> To: i-d-announce@ietf.org >> >> Cc: cdni@ietf.org >> >> Subject: [CDNi] I-D Action: draft-ietf-cdni-media-type-01.txt >> >> >> >> >> >> 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 Working Group of the IETF. >> >> >> >> Title : CDNI Media Type Registration >> >> Author : Kevin J. Ma >> >> Filename : draft-ietf-cdni-media-type-01.txt >> >> Pages : 6 >> >> Date : 2015-09-29 >> >> >> >> Abstract: >> >> This document defines the standard media type used by the Content >> >> Delivery Network Interconnection (CDNI) protocol suite, including >> the >> >> registration procedure and recommended usage of the required >> payload- >> >> type parameter . >> >> >> >> >> >> >> >> The IETF datatracker status page for this draft is: >> >> https://datatracker.ietf.org/doc/draft-ietf-cdni-media-type/ >> >> >> >> There's also a htmlized version available at: >> >> https://tools.ietf.org/html/draft-ietf-cdni-media-type-01 >> >> >> >> A diff from the previous version is available at: >> >> https://www.ietf.org/rfcdiff?url2=draft-ietf-cdni-media-type-01 >> >> >> >> >> >> 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 mailing list > CDNi@ietf.org > https://www.ietf.org/mailman/listinfo/cdni
- [CDNi] I-D Action: draft-ietf-cdni-media-type-01.… internet-drafts
- Re: [CDNi] I-D Action: draft-ietf-cdni-media-type… Kevin Ma J
- Re: [CDNi] I-D Action: draft-ietf-cdni-media-type… Daryl Malas
- Re: [CDNi] I-D Action: draft-ietf-cdni-media-type… Kevin Ma J
- Re: [CDNi] I-D Action: draft-ietf-cdni-media-type… Ali C. Begen
- Re: [CDNi] I-D Action: draft-ietf-cdni-media-type… Kevin Ma J
- Re: [CDNi] I-D Action: draft-ietf-cdni-media-type… Daryl Malas