Re: [Slim] Allowing multiple values in an answer

Randall Gellens <rg+ietf@randy.pensive.org> Thu, 11 January 2018 22:04 UTC

Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: slim@ietfa.amsl.com
Delivered-To: slim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47F8A12DA72 for <slim@ietfa.amsl.com>; Thu, 11 Jan 2018 14:04:59 -0800 (PST)
X-Quarantine-ID: <coC5fKt4qAsK>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_OBFU_PDF_ATTACH=0.01, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 coC5fKt4qAsK for <slim@ietfa.amsl.com>; Thu, 11 Jan 2018 14:04:56 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 57EF312702E for <slim@ietf.org>; Thu, 11 Jan 2018 14:04:54 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Thu, 11 Jan 2018 14:05:25 -0800
Mime-Version: 1.0
Message-Id: <p06240606d67d8fbc9d90@[99.111.97.136]>
In-Reply-To: <p06240604d67d70904f55@[99.111.97.136]>
References: <151555808122.21584.8379796998643581181.idtracker@ietfa.amsl.com> <p06240602d67be148b9db@99.111.97.136> <2c49d430-3fb1-381f-d236-4bc5a6a38c27@omnitor.se> <CAOW+2dtDBKR5q_LO9=kTpgKQJR=P_hy4yzQC=iy8q_WgtH6hyw@mail.gmail.com> <p06240601d67d2f9e1693@[99.111.97.136]> <p06240603d67d6aa5ec31@[99.111.97.136]> <p06240604d67d70904f55@[99.111.97.136]>
X-Mailer: Eudora for Mac OS X
Date: Thu, 11 Jan 2018 14:04:49 -0800
To: Bernard Aboba <bernard.aboba@gmail.com>, Gunnar =?iso-8859-1?Q?Hellstr=F6m?= <gunnar.hellstrom@omnitor.se>
From: Randall Gellens <rg+ietf@randy.pensive.org>
Cc: slim@ietf.org
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="============_-696414206==_============"
Archived-At: <https://mailarchive.ietf.org/arch/msg/slim/dDO3s1w_juJ2hHwn_noN2snvSi0>
Subject: Re: [Slim] Allowing multiple values in an answer
X-BeenThere: slim@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Selection of Language for Internet Media <slim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/slim>, <mailto:slim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/slim/>
List-Post: <mailto:slim@ietf.org>
List-Help: <mailto:slim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/slim>, <mailto:slim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jan 2018 22:04:59 -0000

I realized an additional change was needed, to the discussion of the 
offer/answer model.  Attached is a revised diff.

At 11:57 AM -0800 1/11/18, Randall Gellens wrote:

>  The second of the two remaining open questions is if we should 
> allow an answer to contain multiple values.  I do not think this is 
> the intent of the text that has been in the draft for some time; 
> regardless, we could make such a change, but I question if we can 
> do so now, when we've essentially passed IESG review.
>
>  I edited a version of the draft that contains all remaining 
> clarifying editorial changes to also make this technical change and 
> attached is a diff showing what it would look like.  However, I 
> think we should not make the change since it could introduce 
> additional complexities or problems that we aren't considering.  I 
> think we could make such a change in a future extension or 
> revision.  I don't think we'd have an interoperability problem 
> since endpoints conformant with the more restrictive version will 
> not generate such answers, and would regard regard receiving such 
> answers as an error, but not one that would fail a call.
>
>  --
>  Randall Gellens
>  Opinions are personal;    facts are suspect;    I speak for myself only
>  -------------- Randomly selected tag: ---------------
>  [XML] is probably the worst format ever designed...it really 
> doesn't scale as a
>  file format, and it's generally a complete disaster. --Linus 
> Torvalds, 3/6/2014
>
>
>  Attachment converted: TiLand:diff-with-multiple 1.pdf (    /    ) (008B9E88)
>  _______________________________________________
>  SLIM mailing list
>  SLIM@ietf.org
>  https://www.ietf.org/mailman/listinfo/slim


-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Those were my children being slaughtered.
        --Donald Burr, on the death of People Express.