IETF Logo Mail Archive

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

HTTP issue updates <http-issues@ietf.org> Thu, 24 May 2018 06:53 UTC

Delivered-To: http-issues@ietfa.amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] 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 23:53:37 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527144817; bh=Hhzzip+t67Q+NYPkYzE4UeicWeNWQnerFm+jA32zIYY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=X8Iam6NUOJ8DZw6vkUZZuircDeJ3E+aoL8UHE8rgwj2jweNZoW3s96bz5viG9/7e2 Ez0jBZK4euadVipMHZDef6d8DCt+jfIEzdWj2YdKMAgI4FwAWY5PNu0R7vrRXaYKID 4TFLBHk1868CR1NAPGrqr0pcwm3RPgOmZBFcACIg=
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_5b066171cf173_8cd3fe07ac7ef80344046"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/http-issues/ryqXVfoiTNsa8QaiULbL5_d_2Do>
Message-ID: <mailman.670.1527144821.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: Thu, 24 May 2018 06:53:41 -0000

> Makes sense, will do in the next round.

Thanks, no rush. :)

> 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.

Some level of hand-waving seems fine, though I'd prefer that it be constrained to this document, and not all the documents that wish to define structured headers. If we can end up with a single algorithm, no matter how complicated, that takes a structured header object and outputs a string, I'll be happy to use it!

-- 
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-391608799

v2.23.0 | Report a Bug | By Email