IETF Logo Mail Archive

Re: [MIB-DOCTORS] Feedback regarding draft-ietf-jose-use-cases

Steve Waldbusser <waldbusser@nextbeacon.com> Thu, 19 December 2013 16:43 UTC

Return-Path: <waldbusser@nextbeacon.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A44F1AD672 for <mib-doctors@ietfa.amsl.com>; Thu, 19 Dec 2013 08:43:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_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 XfUz8BfuBNkF for <mib-doctors@ietfa.amsl.com>; Thu, 19 Dec 2013 08:43:24 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id C2BB41ACD00 for <mib-doctors@ietf.org>; Thu, 19 Dec 2013 08:43:23 -0800 (PST)
Received: from [127.0.0.1] (unknown [24.6.159.106]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 5DE5350A88 for <mib-doctors@ietf.org>; Thu, 19 Dec 2013 11:43:20 -0500 (EST)
Message-ID: <52B32227.30203@nextbeacon.com>
Date: Thu, 19 Dec 2013 08:43:19 -0800
From: Steve Waldbusser <waldbusser@nextbeacon.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: mib-doctors@ietf.org
References: <52B31ED4.2020906@cisco.com>
In-Reply-To: <52B31ED4.2020906@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 131218-2, 12/18/2013), Outbound message
X-Antivirus-Status: Clean
Subject: Re: [MIB-DOCTORS] Feedback regarding draft-ietf-jose-use-cases
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Dec 2013 16:43:25 -0000

Openflow is binary. I wouldn't call it an object encoding though even if 
it makes extensive use of TLV.

If they are just talking about object encodings, their point may 
generally be true.

Steve

On 12/19/2013 8:29 AM, Benoit Claise wrote:
> Dear all,
>
> I would like to get your feedback regarding this draft: 
> https://datatracker.ietf.org/doc/draft-ietf-jose-use-cases
> There are a couple of statements on ASN.1, XML, and JSON, such as ...
>
>    Over time, the use of binary object encodings such as ASN.1 has been
>    overtaken by text-based encodings, for example JavaScript Object
>    Notation.
>
>
> ... which I would like to validate with you.
> Also, sometimes, it's not clear whether the author speaks only about 
> the applications, or also the protocols.
>
> Your feedback is appreciated.
>
> Regards, Benoit
>
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors

v2.23.0 | Report a Bug | By Email