Re: [CDNi] I-D Action: draft-ietf-cdni-media-type-01.txt
Daryl Malas <D.Malas@cablelabs.com> Wed, 30 September 2015 18:09 UTC
Return-Path: <D.Malas@cablelabs.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 4F32B1A8833 for <cdni@ietfa.amsl.com>; Wed, 30 Sep 2015 11:09:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.226
X-Spam-Level:
X-Spam-Status: No, score=0.226 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 QfOvxxex_Kv5 for <cdni@ietfa.amsl.com>; Wed, 30 Sep 2015 11:09:37 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id CBB691A8823 for <cdni@ietf.org>; Wed, 30 Sep 2015 11:09:37 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.7/8.14.7) with ESMTP id t8UI9Zv7009293; Wed, 30 Sep 2015 12:09:35 -0600
Received: from exchange.cablelabs.com (10.5.0.19) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com); Wed, 30 Sep 2015 12:09:35 -0600 (MDT)
X-Virus-Status: clean(F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com)
Received: from EXCHANGE.cablelabs.com ([::1]) by EXCHANGE.cablelabs.com ([::1]) with mapi id 14.03.0224.002; Wed, 30 Sep 2015 12:09:32 -0600
From: Daryl Malas <D.Malas@cablelabs.com>
To: Kevin Ma J <kevin.j.ma@ericsson.com>, "cdni@ietf.org" <cdni@ietf.org>
Thread-Topic: [CDNi] I-D Action: draft-ietf-cdni-media-type-01.txt
Thread-Index: AQHQ+sa8k3+MMKgipkOWo5YkA0x1gZ5T/M+AgAFaKQCAAGwfgP//na0A
Date: Wed, 30 Sep 2015 18:09:32 +0000
Message-ID: <D2318132.32D34%d.malas@cablelabs.com>
References: <20150929145422.21119.20578.idtracker@ietfa.amsl.com> <A419F67F880AB2468214E154CB8A556206B5296B@eusaamb103.ericsson.se> <D2317868.32D15%d.malas@cablelabs.com> <A419F67F880AB2468214E154CB8A556206B5595B@eusaamb103.ericsson.se>
In-Reply-To: <A419F67F880AB2468214E154CB8A556206B5595B@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.5.150821
x-originating-ip: [10.5.0.27]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <2D652BF41B264045B092CAAF57E1ADCB@cablelabs.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/cdni/-E09V5Ujyfq2uVVyQ4ougNh0zOE>
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:09:39 -0000
Kevin, I think this approach works, and I agree with Ali’s perspective. I just want to avoid any implications of a dependency that may become obsolete, hopefully before CDNI implementations do. :-) Thanks, Daryl On 9/30/15, 12: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] 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