Re: [httpwg/http-extensions] Serialization for structured headers. (#627)

HTTP issue updates <http-issues@ietf.org> Wed, 23 May 2018 23:52 UTC

Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.01
X-Spam-Level:
X-Spam-Status: No, score=-3.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Date: Wed, 23 May 2018 16:52:42 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527119562; bh=ATMzSFfdgM8KH+fL9dku7tlRRZKAueESvBs8EaM60jo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=O1OudF7WRwL8F86r5rnkahqdTRkUHEuwn5pDrzpwX2dBZHAqsWDm0MJTvIQS7iKW1 eOui+prC6vRTpOiTGATvzYdiWpJSPYlzisv46B5/nraTCDa845bq2BKTcqH2pYLWtH KfOvdnoVsKd576KzGrfD0UIaL3k91vT1GUGauL9A=
To: httpwg/http-extensions <http-extensions@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
In-Reply-To: <httpwg/http-extensions/issues/627@github.com>
References: <httpwg/http-extensions/issues/627@github.com>
Subject: Re: [httpwg/http-extensions] Serialization for structured headers. (#627)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b05feca4020e_63062b18c0642f5428161"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/http-issues/wOChOeP7_RpeD6R02_g5VUHvjVA>
Message-ID: <mailman.625.1527119565.2697.http-issues@ietf.org>
From: HTTP issue updates <http-issues@ietf.org>
Reply-To: http-issues@ietf.org
X-BeenThere: http-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: HTTP issue updates <http-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/http-issues>, <mailto:http-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/http-issues/>
List-Post: <mailto:http-issues@ietf.org>
List-Help: <mailto:http-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-issues>, <mailto:http-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 23:52:45 -0000

Makes sense, will do in the next round.

One hitch is that *eventually*, we want to be able to define alternative serialisations of the header field in new versions of HTTP, so we'll have to be careful in how we do this. Or just admit that there will be some residual hand-waving.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/issues/627#issuecomment-391539905